DS6000

IBM System Storage DS6000
Command-Line Interface Users Guide

V ersion 1 Release 2
GC26-7922-00
IBM System Storage DS6000
Command-Line Interface Users Guide

V ersion 1 Release 2
GC26-7922-00
Note: Before using this information and the product it supports, read the information in the Safety and environmental notices and Notices sections.
Second Edition (November 2006) This edition replaces GC26-7681-06 and all previous versions of GC26-7681. This edition also applies to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2004, 2006. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this guide . . . . . . . . . . vii Notices and publication information . . ix
Safety notices . . . . . . . . . . . . . . ix Environmental notices . . . . . . . . . . . ix Product recycling and disposal . . . . . . . ix Battery return program . . . . . . . . . . x Conventions used in this guide . . . . . . . . xi Related information . . . . . . . . . . . xii DS6000 series library . . . . . . . . . . xii Other IBM publications . . . . . . . . . xiii Ordering IBM publications . . . . . . . . xvii Web sites . . . . . . . . . . . . . . xviii How to send your comments . . . . . . . . xix Installing the DS CLI using the unattended (silent) mode . . . . . . . . . . . . . . . . Correcting the JVM-not-found error . . . . . . Installing DS CLI on an OpenVMS system . . . . Preparing to install the DS CLI on an OpenVMS System . . . . . . . . . . . . . . . Installing the DS CLI on your OpenVMS system Using the DS CLI on an OpenVMS system . . . Removing the DS CLI from an OpenVMS system Completing DS CLI postinstallation . . . . . . Using the DS CLI application . . . . . . . DS CLI command help . . . . . . . . . Obtaining and interpreting DS CLI exit codes . . Activating your machine and feature licenses using the DS CLI . . . . . . . . . . . Setting up user accounts using the DS CLI . . . Creating a default configuration setup with a profile file . . . . . . . . . . . . . . Configure support options using the DS CLI . . Registering for the My Support function . . . . Removing the DS Command Line Interface . . . . Removing the DS CLI from your system using graphical mode . . . . . . . . . . . . Removing the DS CLI using unattended (silent) mode . . . . . . . . . . . . . . . Removing the DS CLI using the console mode. . Removing the DS CLI from a System i system . . OpenVMS system integration . . . . . . . . Enhancing the command console LUN for DS CLI use . . . . . . . . . . . . . . . Enhancing the OpenVMS system messages . . . Enabling OpenVMS to use the DS CLI help . . Java Runtime Environment considerations for DS CLI . . . . . . . . . . . . . . . . Quota considerations for DS CLI . . . . . . 39 42 43 44 44 49 50 50 51 56 57 59 60 61 67 74 75 75 77 77 78 80 80 81 81 82 83
Summary of changes for GC26-7922-00 IBM System Storage DS6000 Command-Line Interface Users Guide . . . . . . . . . . . . xxi Chapter 1. Introduction to the IBM System Storage DS6000 series . . . . . 1
Overview of the DS6000 series models . . . . . DS6800 (Models 1750-511 and 1750-522) . . . DS6000 expansion enclosure (Models 1750-EX1 and 1750-EX2) . . . . . . . . . . . . Management console requirements . . . . . . Performance features . . . . . . . . . . RAID implementation . . . . . . . . . . RAID 5 overview . . . . . . . . . . . RAID 10 overview . . . . . . . . . . Licensed functions . . . . . . . . . . . DS6000 Interfaces . . . . . . . . . . . . IBM System Storage DS Storage Manager . . . The DS command-line interface. . . . . . DS open application programming interface . Host systems attachment overview . . . . . IBM System Storage Resiliency Family . . . . Disaster recovery using Copy Services . . . Comparison of licensed functions . . . . . Logical configuration overview . . . . . . . . 2 . 2 . 3 . 4 . 6 . 7 . 8 . 8 . 8 . 9 . 9 . 10 . 10 . 11 . 11 . 16 . 17 . 18
Chapter 4. Providing PE package and state save information . . . . . . . . 85

Providing problem determination information using FTP . . . . . . . . . . . . . . . . . Providing a management console only PE package Sending the PE package after the FTP transfer has failed . . . . . . . . . . . . . . . . Sending the statesave file after the FTP transfer has failed . . . . . . . . . . . . . . . . Providing problem determination information when FTP is not available. . . . . . . . . . . . 85 88 89 91 92
Chapter 2. Upgrading your system to use DS CLI . . . . . . . . . . . . . 21 Chapter 3. Installing and removing the CLI . . . . . . . . . . . . . . . . 23
Supported operating systems for the DS command-line interface . . . . . . . . DS CLI operational limitations . . . . . . Preparing for the DS CLI installation . . . . Installing the DS CLI using the graphical mode Installing the DS CLI using the console mode .
Copyright IBM Corp. 2004, 2006
. . . . .
. . . . .
23 23 24 27 33
Chapter 5. Configuring and managing logical storage . . . . . . . . . . . 95

Configuring new fixed block storage using the DS CLI . . . . . . . . . . . . . . . . . 95 Creating extent pools for fixed block volumes using the DS CLI . . . . . . . . . . . 95
iii
Creating arrays for fixed block volumes using the DS CLI . . . . . . . . . . . . . . . 97 Creating a rank using the DS CLI . . . . . . 98 Creating fixed block volumes using the DS CLI 99 Creating LUN volumes for System i systems 101 Correcting a fixed block configuration error . . 103 Creating fixed block volume groups using the DS CLI . . . . . . . . . . . . . . 103 Creating a volume group for System i systems 104 Configuring fibre-channel I/O ports using the DS CLI . . . . . . . . . . . . . . 106 Creating SCSI host port connections using DS CLI . . . . . . . . . . . . . . . . 107 Configuring new count key data storage using DS CLI . . . . . . . . . . . . . . . . . 109 Creating count key data extent pools using the DS CLI . . . . . . . . . . . . . . 110 Creating arrays for CKD volumes using the DS CLI . . . . . . . . . . . . . . . . 111 Creating a rank for CKD volumes using the DS CLI . . . . . . . . . . . . . . . . 112 Creating logical control units for CKD volumes using DS CLI . . . . . . . . . . . . 113 Creating count key data volumes using the DS CLI . . . . . . . . . . . . . . . . 115 Correcting a CKD volume configuration error 116 Configuring fibre-channel I/O ports using the DS CLI . . . . . . . . . . . . . . 117 Managing your logical storage configuration . . . 118 Using DS CLI commands on i5/OS . . . . . 118 Modifying an extent pool . . . . . . . . 121 Viewing extent pool status . . . . . . . . 121 Viewing extent pool properties and performance metrics . . . . . . . . . . . . . . 122 Deleting extent pools from a storage configuration . . . . . . . . . . . . 122 Viewing the array disk drive module status . . 123 Viewing array status . . . . . . . . . . 124 Viewing properties for one array . . . . . . 125 Removing arrays from a storage configuration or a rank assignment . . . . . . . . . . 125 Adding a rank to an extent pool . . . . . . 127 Modifying a rank . . . . . . . . . . . 127 Viewing rank status . . . . . . . . . . 129 Viewing properties for one rank . . . . . . 129 Correcting a rank-related configuration error 130 Removing ranks from a storage configuration 130 Modifying a logical control unit . . . . . . 131 Viewing logical control unit status . . . . . 132 Viewing properties for one logical control unit 133 Removing logical control units from a CKD storage configuration . . . . . . . . . . 133
Chapter 6. Copy Services functions

FlashCopy functions . . . . . . . . . Creating a FlashCopy relationship . . . Creating a persistent FlashCopy relationship Viewing information about FlashCopy relationships . . . . . . . . . . . Deleting FlashCopy relationships . . . . Creating remote FlashCopy transactions . . .
135
. 135 . 135 136 . 136 . 138 . 139
Resynchronizing FlashCopy relationships . . . Reversing a FlashCopy relationship . . . . . Applying the FlashCopy revertible option to existing FlashCopy relationships . . . . . . Starting a background copy of a FlashCopy relationship . . . . . . . . . . . . . Preventing write operations on FlashCopy target volumes . . . . . . . . . . . . . . Creating a FlashCopy target volume on an existing Metro Mirror source volume . . . . Discarding changes to FlashCopy target volumes . . . . . . . . . . . . . . Committing data to FlashCopy target volumes Metro Mirror functions . . . . . . . . . . Displaying the status of established paths . . . Displaying the WWNN of a storage unit . . . Creating remote mirror and copy paths. . . . Correcting a path-related configuration error Removing paths . . . . . . . . . . . Creating a Metro Mirror relationship . . . . Creating a Metro Mirror consistency group . . Resuming a Metro Mirror relationship . . . . Pausing a Metro Mirror relationship . . . . . Creating a Global Copy relationship . . . . . Deleting a Metro Mirror relationship . . . . Modifying logical subsystem timeout values . . Defining a path that has the consistency option enabled . . . . . . . . . . . . . . Monitoring Remote Mirror and Copy paths . . Performing a failback recovery operation . . . Performing a failover recovery operation . . . Viewing information about Metro Mirror relationships . . . . . . . . . . . . . Converting Global Copy volume pairs to synchronous . . . . . . . . . . . . . Determining which I/O ports are available for paths . . . . . . . . . . . . . . . Deleting a single volume Metro Mirror relationship . . . . . . . . . . . . . Copy Services functions across a 2105 and 1750 Creating a Metro Mirror volume pair between a 1750 and a 2105 . . . . . . . . . . . Global Mirror functions . . . . . . . . . . Adding volumes to a session (Global Mirror) Modifying the tuning parameters of a Global Mirror session . . . . . . . . . . . . Modifying the topology of a Global Mirror session . . . . . . . . . . . . . . Viewing a Global Mirror session . . . . . . Querying Global Mirror processing . . . . . Pausing Global Mirror processing . . . . . Resuming Global Mirror processing . . . . . Starting Global Mirror processing . . . . . Ending Global Mirror processing (script mode) Ending Global Mirror processing (no script) . . Setting up the Global Mirror Environment . . . Removing a Global Mirror environment . . .
140 141 142 143 144 145 146 147 148 148 148 149 150 151 152 153 154 155 156 157 157 161 161 162 162 163 164 164 166 167 167 169 170 171 172 174 175 175 176 176 177 177 178 184
. . .
Chapter 7. Recovering from a disaster using Global Mirror . . . . . . . . . 191
iv
DS6000 CLI Users Guide
Ending Global Mirror processing when a disaster occurs . . . . . . . . . . . . . . . . Checking Global Mirror transaction status in a disaster situation . . . . . . . . . . . . Initiating failover processing for B volumes to A volumes . . . . . . . . . . . . . . . Analyzing and validating the consistency group state . . . . . . . . . . . . . . . . Using the revertflash command to correct FlashCopy relationships . . . . . . . . . . Using the commitflash command to correct FlashCopy relationships . . . . . . . . . . Using fast reverse restore processing to create consistency . . . . . . . . . . . . . . Waiting for the background copy to complete . . Reestablishing the FlashCopy relationships between B volumes and C volumes . . . . . . Preparing to reinstate production at the local site Resynchronizing the volumes . . . . . . . . Querying, quiescing, and querying . . . . . . Reestablishing remote mirror and copy paths (site A to site B) . . . . . . . . . . . . . . Performing Global Copy failover processing to the A volumes . . . . . . . . . . . . . . Performing Global Copy failback processing for the A volumes . . . . . . . . . . . . . . Resuming Global Mirror processing at site A . . .
192 193 194 195 197 198 199 200 201 202 203 204 205 207 207 208
Chapter 8. CLI commands . . . . . . 211

About CLI commands . . . . . . . Understanding the syntax diagrams . . . List of commands . . . . . . . . . Command flags . . . . . . . . . Using hexadecimal values . . . . . . Command equivalents . . . . . . . Output field descriptions . . . . . . Framework command . . . . . . . dscli . . . . . . . . . . . . exit . . . . . . . . . . . . . help . . . . . . . . . . . . quit . . . . . . . . . . . . setoutput . . . . . . . . . . . User account and security commands . . chpass . . . . . . . . . . . . chuser . . . . . . . . . . . . lsuser . . . . . . . . . . . . managepwfile . . . . . . . . . mkuser . . . . . . . . . . . rmuser . . . . . . . . . . . setrmpw . . . . . . . . . . . showpass . . . . . . . . . . . showuser . . . . . . . . . . . Application key and version commands . applykey . . . . . . . . . . . lskey . . . . . . . . . . . . ver . . . . . . . . . . . . . Physical enclosure information commands. lsstgencl . . . . . . . . . . . Physical resource information commands . lsddm . . . . . . . . . . . . Storage unit configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 212 213 228 230 231 236 247 247 249 249 250 251 254 254 255 257 258 260 262 263 263 264 265 265 266 267 268 268 271 271 275
chsu . . . . . . . . . . . . . . . lssu. . . . . . . . . . . . . . . . showsu . . . . . . . . . . . . . . Storage image configuration commands . . . . chsi. . . . . . . . . . . . . . . . diagsi . . . . . . . . . . . . . . . lsserver . . . . . . . . . . . . . . lssi . . . . . . . . . . . . . . . . showsi . . . . . . . . . . . . . . I/O port and host connection configuration commands . . . . . . . . . . . . . . Storage image I/O port commands . . . . . Host connection commands . . . . . . . Storage configuration commands . . . . . . . Array site specific commands . . . . . . . Array specific commands . . . . . . . . Rank specific commands . . . . . . . . Extent pool specific commands . . . . . . Address group specific commands . . . . . Logical control unit specific commands . . . . CKD logical volume specific commands . . . Logical subsystem specific commands . . . . Fixed block logical volume specific commands Volume group specific commands . . . . . Advanced operation commands . . . . . . Copy Services commands . . . . . . . . . FlashCopy commands . . . . . . . . . Remote FlashCopy commands . . . . . . . Remote Mirror and Copy path commands . . . Remote Mirror and Copy pair commands . . . Global Mirror commands . . . . . . . . Global Mirror session commands . . . . . . Audit commands . . . . . . . . . . . . offloadauditlog . . . . . . . . . . . . DS6000 remote support and notification commands setplex . . . . . . . . . . . . . . showplex . . . . . . . . . . . . . . setdialhome . . . . . . . . . . . . . setsmtp . . . . . . . . . . . . . . setsnmp . . . . . . . . . . . . . . setsim . . . . . . . . . . . . . . . setcontactinfo . . . . . . . . . . . . showcontactinfo . . . . . . . . . . . testcallhome . . . . . . . . . . . . . DS6000 PE package commands . . . . . . . offloadss . . . . . . . . . . . . . . mkpe . . . . . . . . . . . . . . . sendss . . . . . . . . . . . . . . . sendpe . . . . . . . . . . . . . . lsss . . . . . . . . . . . . . . . . lspe . . . . . . . . . . . . . . . DS6000 problem log commands . . . . . . . closeproblem . . . . . . . . . . . . lsproblem . . . . . . . . . . . . .
275 276 278 281 281 282 283 285 287 289 290 298 319 320 325 333 344 353 355 363 383 387 407 417 418 418 437 454 466 496 510 518 518 521 522 523 526 526 527 528 529 541 542 542 543 544 547 547 548 550 551 551 552
Chapter 9. Command-line interface scenarios . . . . . . . . . . . . . 555

Modifying fixed block volume groups . Deleting data storage configurations . . Deleting a fixed block data storage configuration . . . . . . . . . . . . . . . . . . 555 . 556 . 556
Contents
Deleting a count key data storage configuration Processing remote FlashCopy (inband) transactions Metro Mirror test scenario: failback operation from local to remote site . . . . . . . . . . . Allowed remote mirror and copy volume pair conversions . . . . . . . . . . . . . .
560 563 564 566
Chapter 10. Messages in the CLI and management console server . . . . . 569 Accessibility . . . . . . . . . . . . 571 Notices . . . . . . . . . . . . . . 573
Terms and conditions . . . Trademarks . . . . . . Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . 574 . 575 . 576
Federal Communications Commission (FCC) statement . . . . . . . . . . . . . Industry Canada compliance statement . . . European community compliance statement . Japanese Voluntary Control Council for Interference (VCCI) class A statement . . . Korean Ministry of Information and Communication (MIC) statement . . . . . Taiwan class A compliance statement . . . Taiwan Contact Information . . . . . . .
. 576 . 576 . 576 . 577 . 578 . 578 . 578
Glossary . . . . . . . . . . . . . 579
. . . . . . . . . . . . . . . . . 579
Index . . . . . . . . . . . . . . . 607
vi
About this guide

This publication introduces the IBM System Storage DS Command-Line Interface application and provides instructions for installing it. This publication provides descriptions of the following components: v Each command-line interface command. v Each system message that appears in the command-line interface application. v Each system message that appears in the management console application. This publication is for the storage system administrator or the person who is responsible for installing and using the DS Command-Line Interface in your enterprise. It is written for a user who understands the concepts of a command-line interface application and writing scripts and who has a knowledge of the operating systems and the storage systems in your enterprise.
vii
viii
Notices and publication information

This section contains information about safety notices that are used in this guide, environmental notices for this product, publication information, and information about sending your comments to IBM.
Safety notices
Complete this task to find information about safety notices. To find the translated text for a danger or caution notice: 1. Look for the identification number at the end of each danger notice or each caution notice. In the following examples, the numbers 1000 and 1001 are the identification numbers. DANGER A danger notice indicates the presence of a hazard that has the potential of causing death or serious personal injury. 1000
CAUTION: A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury. 1001 2. Find the number that matches in the IBM System Storage Solutions Safety Notices for IBM Versatile Storage Server and IBM System Storage Enterprise Storage Server, GC26-7229.
Environmental notices
This section identifies the environmental guidelines that pertain to this product.
Product recycling and disposal

This unit contains recyclable materials. This unit must be recycled or discarded according to applicable local and national regulations. IBM encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. IBM offers a variety of product return programs and services in several countries to assist equipment owners in recycling their IT products. Information on IBM product recycling offerings can be found on IBMs Internet site at http://www.ibm.com/ ibm/environment/products/prp.shtml.
ix
Notice: This mark applies only to countries within the European Union (EU) and Norway. Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical and electronic equipment (WEEE). The Directive determines the framework for the return and recycling of used appliances as applicable throughout the European Union. This label is applied to various products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per this Directive. In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as unsorted municipal waste, but use the collection framework available to customers for the return, recycling and recovery of WEEE. Customer participation is important to minimize any potential effects of EEE on the environment and human health due to the potential presence of hazardous substances in EEE. For proper collection and treatment, contact your local IBM representative.
Battery return program

This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or lithium ion battery. Consult your user manual or service manual for specific battery information. The battery must be recycled or disposed of properly. Recycling facilities may not be available in your area. For information on disposal of batteries outside the United States, go to http://www.ibm.com/ibm/ environment/products/batteryrecycle.shtml or contact your local waste disposal facility. In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM Equipment. For information on proper disposal of these batteries, contact IBM at 1-800-426-4333. Please have the IBM part number listed on the battery available prior to your call. In the Netherlands the following applies:
f2c00425
For Taiwan:
Please recycle batteries.

svc00066
Conventions used in this guide

The following typefaces are used to show emphasis: boldface Text in boldface represents menu items and lowercase or mixed-case command names. italics Text in italics is used to emphasize a word. In command syntax, it is used for variables for which you supply actual values.
monospace Text in monospace identifies the data or commands that you type, samples of command output, or examples of program code or messages from the system.
svc00065
svc00064
xi
Related information
The tables in this section list and describe the following publications: v The publications that make up the IBM System Storage DS6000 series library v Other IBM publications that relate to the DS6000 series v Non-IBM publications that relate to the DS6000 series See Ordering IBM publications on page xvii for information about how to order publications in the IBM System Storage DS6000 series publication library. See How to send your comments on page xix for information about how to send comments about the publications.
DS6000 series library

These customer publications make up the DS6000 series library. Unless otherwise noted, these publications are available in Adobe portable document format (PDF) on a compact disc (CD) that comes with the storage unit. If you need additional copies of this CD, the order number is SK2T-8825. These publications are also available as PDF files by clicking on the Documentation link on the following Web site: http://www-1.ibm.com/servers/storage/support/disk See Ordering IBM publications on page xvii for information about ordering these and other IBM publications.
Title IBM System Storage DS: Command-Line Interface Users Guide Description Order Number
This guide describes the commands that you can use from the GC26-7681 command-line interface (CLI) for managing your DS6000 configuration (See Note.) and Copy Services relationships. The CLI application provides a set of commands that you can use to write customized scripts for a host system. The scripts initiate predefined tasks in a Copy Services server application. You can use the CLI commands to indirectly control Remote Mirror and Copy and FlashCopy configuration tasks within a Copy Services server group. This guide provides guidelines for attaching the DS6000 to your host system and for migrating to fibre-channel attachment from a small computer system interface. This guide introduces the DS6000 product and lists the features you can order. It also provides guidelines for planning the installation and configuration of the storage unit. This publication describes how to use the IBM Subsystem Device Driver (SDD) on open-systems hosts to enhance performance and availability on the DS6000. SDD creates single devices (vpaths) that consolidate redundant paths for logical unit numbers. SDD permits applications to run without interruption when path errors occur. It balances the workload across paths, and it transparently integrates with applications. This publication provides reference information for the IBM System Storage DS application programming interface (API) and provides instructions for installing the Common Information Model Agent, which implements the API. GC26-7680 (See Note.) GC26-7679
IBM System Storage DS6000: Host Systems Attachment Guide IBM System Storage DS6000: Introduction and Planning Guide IBM System Storage Multipath Subsystem Device Driver Users Guide
SC30-4096
IBM System Storage DS Application Programming Interface Reference
GC35-0493
xii
Title IBM System Storage DS6000 Messages Reference IBM System Storage DS6000 Installation, Troubleshooting, and Recovery Guide IBM System Storage DS6000 Quick Start Card
Description
Order Number
This publication provides explanations of error, information, and warning GC26-7682 messages that are issued from the DS6000 user interfaces. This publication provides reference information for installing and troubleshooting the DS6000. It also discusses disaster recovery using Copy Services. This is a quick start guide for use in installing and configuring the DS6000 series. GC26-7678
GC26-7685
Note: No hardcopy book is produced for this publication. However, a PDF file is available from the following Web site: http://www-1.ibm.com/servers/storage/support/disk
Other IBM publications

Other IBM publications contain additional information that is related to the DS product library. The following list is divided into categories to help you find publications that are related to specific topics. Some of the publications are listed under more than one category. See Ordering IBM publications on page xvii for information about ordering these and other IBM publications.
Title Description Data-copy services z/OS DFSMS Advanced Copy Services This publication helps you understand and use IBM Advanced Copy SC35-0428 Services functions. It describes three dynamic copy functions and several point-in-time copy functions. These functions provide backup and recovery of data if a disaster occurs to your data center. The dynamic copy functions are peer-to-peer remote copy, extended remote copy, and coupled extended remote copy. Collectively, these functions are known as remote copy. FlashCopy, SnapShot, and concurrent copy are the point-in-time copy functions. This publication, from the IBM International Technical Support Organization, introduces the Enterprise Storage Server and provides an understanding of its benefits. It also describes in detail the architecture, hardware, and functions, including the advanced copy functions, of the Enterprise Storage Server. This publication, from the IBM International Technical Support Organization, tells you how to install, customize, and configure Copy Services on an Enterprise Storage Server that is attached to an S/390 or zSeries host system. Copy Services functions include peer-to-peer remote copy (PPRC), extended remote copy (XRC), FlashCopy, and concurrent copy. This publication describes the functions, prerequisites, and corequisites and describes how to implement each function into your environment. SG24-5465 Order Number
IBM Enterprise Storage Server
Implementing Copy Services 0n S/390
SG24-5680
xiii
Title IBM TotalStorage ESS Implementing Copy Services in an Open Environment
Description
Order Number
This publication, from the IBM International Technical Support SG24-5757 Organization, tells you how to install, customize, and configure Copy Services on UNIX, Windows NT, Windows 2000, Sun Solaris, HP-UX, Tru64, OpenVMS, and iSeries host systems. The Copy Services functions that are described include peer-to-peer remote copy (PPRC) and FlashCopy. This publication describes the functions and shows you how to implement them into your environment. It also shows you how to implement these functions in a high-availability cluster multiprocessing environment. Fibre channel
Fibre Channel Connection (FICON) I/O Interface: Physical Layer
This publication provides information about the fibre-channel I/O interface. This book is also available as a PDF file from the following Web site: http://www.ibm.com/servers/resourcelink/
SA24-7172
Fibre Transport Services (FTS): Physical and Configuration Planning Guide IBM SAN Fibre Channel Switch: 2109 Model S08 Installation and Service Guide IBM SAN Fibre Channel Switch: 2109 Model S08 Users Guide IBM SAN Fibre Channel Switch: 2109 Model S16 Installation and Service Guide IBM SAN Fibre Channel Switch: 2109 Model S16 Users Guide Implementing Fibre Channel Attachment on the ESS
This publication provides information about fibre-optic and ESCON-trunking systems.
GA22-7234
This guide describes how to install and maintain the IBM SAN Fibre Channel Switch 2109 Model S08.
SC26-7350
This guide describes the IBM SAN Fibre Channel Switch and the IBM TotalStorage ESS Specialist. It provides information about the commands and how to manage the switch with Telnet and the Simple Network Management Protocol. This publication describes how to install and maintain the IBM SAN Fibre Channel Switch 2109 Model S16. It is intended for trained service representatives and service providers. This guide introduces the IBM SAN Fibre Channel Switch 2109 Model S16 and tells you how to manage and monitor the switch using zoning and how to manage the switch remotely. This publication, from the IBM International Technical Support Organization, helps you install, tailor, and configure fibre-channel attachment of open-systems hosts to the Enterprise Storage Server. It provides you with a broad understanding of the procedures that are involved and describes the prerequisites and requirements. It also shows you how to implement fibre-channel attachment. Open-systems hosts
SC26-7349
SC26-7352
SC26-7351
SG24-6113
ESS Solutions for Open This publication, from the IBM International Technical Support SG24-6119 Systems Storage: Compaq Organization, helps you install, tailor, and configure the Enterprise Storage AlphaServer, HP, and Sun Server when you attach Compaq AlphaServer (running Tru64 UNIX), HP, and Sun hosts. This book does not cover Compaq AlphaServer that is running the OpenVMS operating system. This book also focuses on the settings that are required to give optimal performance and on the settings for device driver levels. This book is for the experienced UNIX professional who has a broad understanding of storage concepts.
xiv
Title IBM TotalStorage ESS Implementing Copy Services in an Open Environment
Description
Order Number
This publication, from the IBM International Technical Support SG24-5757 Organization, tells you how to install, customize, and configure Copy Services on UNIX or Windows 2000 host systems. The Copy Services functions that are described include peer-to-peer remote copy and FlashCopy. This publication describes the functions and shows you how to implement them into your environment. It also shows you how to implement these functions in a high-availability cluster multiprocessing environment. This publication, from the IBM International Technical Support Organization, helps you install, tailor, and configure fibre-channel attachment of open-systems hosts to the Enterprise Storage Server. It gives you a broad understanding of the procedures that are involved and describes the prerequisites and requirements. It also shows you how to implement fibre-channel attachment. S/390 and zSeries hosts SG24-6113
Implementing Fibre Channel Attachment on the ESS
Device Support Facilities: Users Guide and Reference
This publication describes the IBM Device Support Facilities (ICKDSF) product that are used with IBM direct access storage device (DASD) subsystems. ICKDSF is a program that you can use to perform functions that are needed for the installation, the use, and the maintenance of IBM DASD. You can also use it to perform service functions, error detection, and media maintenance.
GC35-0033
z/OS Advanced Copy Services
This publication helps you understand and use IBM Advanced Copy SC35-0428 Services functions. It describes three dynamic copy functions and several point-in-time copy functions. These functions provide backup and recovery of data if a disaster occurs to your data center. The dynamic copy functions are peer-to-peer remote copy, extended remote copy, and coupled extended remote copy. Collectively, these functions are known as remote copy. FlashCopy, SnapShot, and concurrent copy are the point-in-time copy functions. SC35-0169 GA22-7234
DFSMS/MVS V1: Remote This publication provides guidelines for using remote copy functions with Copy Guide and Reference S/390 and zSeries hosts. Fibre Transport Services (FTS): Physical and Configuration Planning Guide Implementing ESS Copy Services on S/390 This publication provides information about fibre-optic and ESCON-trunking systems.
This publication, from the IBM International Technical Support Organization, tells you how to install, customize, and configure Copy Services on an Enterprise Storage Server that is attached to an S/390 or zSeries host system. Copy Services functions include peer-to-peer remote copy, extended remote copy, FlashCopy, and concurrent copy. This publication describes the functions, prerequisites, and corequisites and describes how to implement each function into your environment. This publication describes the Input/Output Configuration Program that supports the Enterprise Systems Connection (ESCON) architecture. It describes how to define, install, and configure the channels or channel paths, control units, and I/O devices on the ES/9000 processors and the IBM ES/3090 Processor Complex. This publication describes the Input/Output Configuration Program that supports the zSeries 800 and 900 servers. This publication is available in PDF format by accessing ResourceLink at the following Web site: www.ibm.com/servers/resourcelink/
SG24-5680
ES/9000, ES/3090: IOCP User Guide Volume A04
GC38-0097
IOCP Users Guide, IBM e(logo)server zSeries 800 and 900
SB10-7029
xv
Title IOCP Users Guide, IBM e(logo)server zSeries
Description This publication describes the Input/Output Configuration Program that supports the zSeries server. This publication is available in PDF format by accessing ResourceLink at the following Web site: www.ibm.com/servers/resourcelink/
Order Number SB10-7037
S/390: Input/Output This publication describes the Input/Output Configuration Program that Configuration Program supports ESCON architecture and the ESCON multiple image facility. Users Guide and ESCON Channel-to-Channel Reference IBM z/OS Hardware Configuration Definition Users Guide This guide provides conceptual and procedural information to help you use the z/OS Hardware Configuration Definition (HCD) application. It also explains: v How to migrate existing IOCP/MVSCP definitions v How to use HCD to dynamically activate a new configuration v How to resolve problems in conjunction with MVS/ESA HCD
GC38-0401
SC33-7988
OS/390: Hardware Configuration Definition Users Guide OS/390 V2R10.0: MVS System Messages Volume 1 (ABA - ASA) Using IBM 3390 Direct Access Storage in a VM Environment
This guide provides detailed information about the input/output definition SC28-1848 file and about how to configure parallel access volumes. This guide discusses how to use Hardware Configuration Definition for both OS/390 and z/OS V1R1. This publication lists OS/390 MVS system messages ABA to ASA. GC28-1784
This publication provides device-specific information for the various GG26-4575 models of the 3390 and describes methods you can use to manage storage efficiently using the VM operating system. It provides guidance on managing system performance, availability, and space through effective use of the direct access storage subsystem. This publication helps you use the 3390 in a VSE environment. It includes planning information for adding new 3390 units and instructions for installing devices, migrating data, and performing ongoing storage management activities. GC26-4576
Using IBM 3390 Direct Access Storage in a VSE Environment Using IBM 3390 Direct Access Storage in an MVS Environment
This publication helps you use the 3390 in an MVS environment. It GC26-4574 includes device-specific information for the various models of the 3390 and illustrates techniques for more efficient storage management. It also offers guidance on managing system performance, availability, and space utilization through effective use of the direct access storage subsystem. This publication provides a detailed definition of the z/Architecture. It is written as a reference for use primarily by assembler language programmers and describes each function at the level of detail needed to prepare an assembler language program that relies on a particular function. However, anyone concerned with the functional details of z/Architecture will find this publication useful. SAN SA22-7832
z/Architecture Principles of Operation
xvi
Title IBM OS/390 Hardware Configuration Definition Users Guide
Description This guide explains how to use the Hardware Configuration Data application to perform the following tasks: v Define new hardware configurations v View and modify existing hardware configurations v Activate configurations v Query supported hardware v Maintain input/output definition files (IODFs) v Compare two IODFs or compare an IODF with an actual configuration v Print reports of configurations v Create graphical reports of a configuration v Migrate existing configuration data
Order Number SC28-1848
IBM SAN Fibre Channel Switch: 2109 Model S08 Installation and Service Guide IBM SAN Fibre Channel Switch: 2109 Model S08 Users Guide IBM SAN Fibre Channel Switch: 2109 Model S16 Installation and Service Guide IBM SAN Fibre Channel Switch: 2109 Model S16 Users Guide Implementing Fibre Channel Attachment on the ESS
This guide describes how to install and maintain the IBM SAN Fibre Channel Switch 2109 Model S08.
SC26-7350
This guide describes the IBM SAN Fibre Channel Switch and the IBM TotalStorage ESS Specialist. It provides information about the commands and how to manage the switch with Telnet and the Simple Network Management Protocol (SNMP). This publication describes how to install and maintain the IBM SAN Fibre Channel Switch 2109 Model S16. It is intended for trained service representatives and service providers. This guide introduces the IBM SAN Fibre Channel Switch 2109 Model S16 and tells you how to manage and monitor the switch using zoning and how to manage the switch remotely. This publication, from the IBM International Technical Support Organization, helps you install, tailor, and configure fibre-channel attachment of open-systems hosts to the Enterprise Storage Server. It provides you with a broad understanding of the procedures that are involved and describes the prerequisites and requirements. It also shows you how to implement fibre-channel attachment. Storage management
SC26-7349
SC26-7352
SC26-7351
SG24-6113
Device Support Facilities: Users Guide and Reference
This publication describes the IBM Device Support Facilities (ICKDSF) GC35-0033 product used with IBM direct access storage device (DASD) subsystems. ICKDSF is a program that you can use to perform functions that are needed for the installation, the use, and the maintenance of IBM DASD. You can also use it to perform service functions, error detection, and media maintenance. This handbook, from the IBM International Technical Support Organization, helps you understand what makes up enterprise storage management. The concepts include the key technologies that you must know and the IBM subsystems, software, and solutions that are available today. It also provides guidelines for implementing various enterprise storage administration tasks so that you can establish your own enterprise storage management environment. SG24-5250
IBM TotalStorage Solutions Handbook
Ordering IBM publications

You can order copies of IBM publications using the IBM publications center.
xvii
IBM publications center

The publications center is a worldwide central repository for IBM product publications and marketing material. The IBM publications center offers customized search functions to help you find the publications that you need. Some publications are available for you to view or download free of charge. You can also order publications. The publications center displays prices in your local currency. You can access the IBM publications center through the following Web site: http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/ pbi.cgi Note: Open the Web site in a new browser window by right clicking on the link and selecting Open in New Window.
Web sites
The following Web sites provide information about the IBM System Storage DS6000 series and other IBM storage products.
Type of Storage Information Concurrent Copy for S/390 and zSeries host systems Copy Services command-line interface (CLI) DS6000 Information Center DS6000 series publications Web Site http://www.storage.ibm.com/software/sms/sdm/ http://www-1.ibm.com/servers/storage/support/software/cscli/ http://publib.boulder.ibm.com/infocenter/ds6000ic/index.jsp http://www-1.ibm.com/servers/storage/support/disk Click Documentation. FlashCopy for S/390 and zSeries host systems Host system models, operating systems, and adapters that the storage unit supports IBM Disk Storage Feature Activation (DSFA) IBM storage products IBM System Storage DS6000 series IBM version of the Java (JRE) that is often required for IBM products Multiple Device Manager (MDM) http://www.storage.ibm.com/software/sms/sdm/ http://www.ibm.com/servers/storage/disk/ds6000/ Click Interoperability matrix. http://www.ibm.com/storage/dsfa http://www.storage.ibm.com/ http://www-1.ibm.com/servers/storage/disk/ds6000 http://www-106.ibm.com/developerworks/java/jdk/ http://www.ibm.com/servers/storage/support/ Click Storage Virtualization. Remote Mirror and Copy (formerly PPRC) for S/390 and zSeries host systems SAN fibre channel switches Storage Area Network Gateway and Router Subsystem Device Driver (SDD) Technical notes and product tips http://www.storage.ibm.com/software/sms/sdm/ http://www.ibm.com/storage/fcswitch/ http://www-1.ibm.com/servers/storage/support/san/ http://www-03.ibm.com/servers/storage/support/software/sdd http://www.ibm.com/servers/storage/support/disk/ds6800/ Click Technical notes on the Troubleshooting tab. z/OS Global Mirror (formerly XRC) for S/390 and zSeries host systems http://www.storage.ibm.com/software/sms/sdm/
xviii
How to send your comments

Your feedback is important to help us provide the highest quality information. If you have any comments about this information or any other DS6000 series documentation, you can submit them in the following ways: v e-mail Submit your comments electronically to the following e-mail address: starpubs@us.ibm.com Be sure to include the name and order number of the book and, if applicable, the specific location of the text you are commenting on, such as a page number or table number. v Mail Fill out the Readers Comments form (RCF) at the back of this book. Return it by mail or give it to an IBM representative. If the RCF has been removed, you can address your comments to: International Business Machines Corporation RCF Processing Department Department 61C 9032 South Rita Road TUCSON AZ 85775-4401
xix
xx
Summary of changes for GC26-7922-00 IBM System Storage DS6000 Command-Line Interface Users Guide
This document contains terminology, maintenance, and editorial changes. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change.
New Information
The following commands and topics were added or enhanced in this release: v The Activating your machine and feature licenses using the DS CLI in Chapter 3 was upgraded for the use of some additional activation codes. v The Creating a default configuration setup with a profile file in Chapter 3 was upgraded to include a typical edit process for your profile configuration file. v Using forced failover and failback during an unplanned Metro/Global Mirror outage was added to Chapter 7. v Using forced failover and failback during a planned Metro/Global Mirror outage was added to Chapter 7. v lskey command - Enhanced for the addition of some new activation codes. v failoverpprc command - Enhanced with the addition of the -force parameter. v failbackpprc command - Enhanced with the addition of the -force parameter. v showsu command - Enhanced the reports. v showsi command - Enhanced the reports. v chsu command - Removed all unsupported functions. v chsi command - Removed all unsupported functions. v setrmpw command - New command used when DS8000 uses the IBM TotalStorage Productivity Center Replication Manager function. v lspprc command - This command was updated to include descriptions for the reason codes that might be reported.
xxi
xxii
Chapter 1. Introduction to the IBM System Storage DS6000 series

The IBM System Storage DS6000 series is a member of the family of DS products and is built upon 2 Gbps fibre-channel technology that provides RAID-protected storage with advanced function, scalability, and increased addressing capabilities. The DS6000 series is an enterprise-class storage solution that offers high reliability and performance in a modular midrange package. The DS6000 series provides storage sharing and consolidation for a wide variety of operating systems and mixed server environments. The DS6000 series offers high scalability and excellent performance. With the DS6800 (Models 1750-511 and 1750-522), you can install up to 16 disk drive modules (DDMs). The minimum storage capability with 4 DDMs is 292 GB. The DS6000 series also offers 500 GB, 7 200 rpm Fibre-channel ATA (FATA) disk drives, so the maximum storage capability with 16 DDMs for the DS6800 model is 8 TB. FATA drives combine a fibre-channel interface with an ATA drive, which provides additional capacity to address specific application and business requirements. You can add FATA disk drives to the DS6000 series to satisfy the needs of various fixed-content, data-archival, reference data, and near-line applications that require large amounts of storage capacity at a lower cost. If you want to connect more than 16 disks, you can use the optional DS6000 expansion enclosures (Models 1750-EX1 and 1750-EX2). A storage system supports up to 128 disk drives for a total of up to 64 TB of storage. The DS6800 measures 5.25-in. high and is available in a 19-in. rack mountable package with an optional modular expansion enclosure of the same size to add capacity to help meet your growing business needs. The DS6000 series addresses business efficiency needs through its heterogeneous connectivity, high performance, and manageability functions, thereby helping to reduce total cost of ownership. The DS6000 series offers the following major features: v PowerPC 750GX processors v Dual active controllers that provide continuous operations through the use of two processors that form a pair that back up each other v A selection of 2 GB fibre-channel (FC) disk drives, including 73 GB, 146 GB, and 300 GB sizes with speeds of 10 000 or 15 000 revolutions per minute (rpm) v 500 GB, 7 200 rpm FATA disk drives v 2 GB fibre-channel and FICON host attachments of up to 8 ports, which can be configured with an intermix of Fibre-channel Protocol (FCP) and FICON v Fibre-channel Arbitrated Loop (FC-AL) switched device attachment of up to 2 dual loops v Storage virtualization v Battery backed mirrored cache v Fully redundant power and cooling system v Disaster recovery and Copy Services features
You can also view the DS6000 e-learning overview from the DS6000 Storage Manager Welcome page at http://www-1.ibm.com/support/docview.wss?rs=1112 &uid=ssg1S7001165. The e-learning overview provides an animated presentation about installation and configuration, service and support, and management tasks. Note: Some DS6000 series features and functions might not be available or be supported in all environments. You can find current information on supported environments, prerequisites, and minimum operating systems levels at the following Web site: http://www.ibm.com/servers/storage/ disk/ds6000/
Overview of the DS6000 series models

The DS6000 series offers a base enclosure model with storage and optional expansion enclosures.
DS6800 (Models 1750-511 and 1750-522)

The DS6000 offers the following features: v Two fibre channel processor cards v PowerPC 750GX 1 GHz processor v 4 GB of cache v Two battery backup units (one per each processor card) v Two ac/dc power supplies with imbedded enclosure cooling units v Eight 2 Gb/sec device ports v Connectivity with the availability of two to eight fibre-channel/FICON host ports. The host ports autonegotiate to either 2 Gbps or 1 Gbps link speeds. v Attachment to 7 DS6000 expansion enclosures.
f2d00067
The DS6800 is a self-contained 3U enclosure that can be mounted in a standard 19-inch rack. The DS6800 comes with authorization for up to 16 internal fibre-channel DDMs or FATA drives, offering up to 8 TB of storage capability. The DS6800 allows up to 7 DS6000 expansion enclosures to be attached. A storage system supports up to 128 disk drives for a total of up to 64 TB of storage. Note: The intermix of drive types is not allowed within an enclosure. The DS6800 system offers connectivity with the availability of two to eight fibre-channel/FICON host ports. The 2 GB fibre-channel/FICON host ports, which are offered in longwave and shortwave, autonegotiate to either 2 Gbps or 1 Gbps link speeds. This flexibility supports the ability to exploit the potential benefits offered by higher performance, 2 Gbps SAN-based solutions, while also maintaining compatibility with existing 1 Gbps infrastructures. In addition, with the maximum of eight host ports enabled, the DS6800 system can be configured with an intermix of Fibre Channel Protocol (FCP) and FICON. This can help protect your investment in fibre-channel adapters and increase your ability to migrate to new servers. The DS6800 system offers connectivity support across a broad range of server environments, including IBM eServer, zSeries, iSeries, and pSeries servers as well as servers from Sun Microsystems, Hewlett-Packard, and other Intel-based providers. The ability to easily partition the capacity of the DS6800 system storage among the attached environments supports storage consolidation requirements in dynamic and changing environments.
DS6000 expansion enclosure (Models 1750-EX1 and 1750-EX2)

The DS6000 series expansion enclosure contains the following features: v Two expansion processor cards. Each processor card provides the following: 2 inbound ports (2 Gb/sec.) 2 outbound ports (2 Gb/sec.) 1 fibre-channel switch per processor card v Expansion disk enclosure that holds up to 16 fibre-channel DDMs v Two ac/dc power supplies with imbedded enclosure cooling units v Supports attachment to DS6800
f2d00068
The 3U DS6000 expansion enclosure can be mounted in a standard 19-inch rack. The front of the enclosure contains the docking sites where you can install up to 16 DDMs. The DDMs are installed in a horizontal position with a locking handle. The rear of the enclosure provides the docking sites for the power supplies and the processor cards. You can attach the DS6800 and expansion enclosure by using the processor card interfaces at the rear of the enclosure. A system display panel is also located at the rear of the enclosure.
Management console requirements

The DS6000 Storage Manager requires that the system that is used as the management console be continuously available for customer operation, configuration, and problem management. It is best to load the DS6000 Storage Manager on a dedicated system. If you must install the DS6000 Storage Manager on a nondedicated system, contact your account sales representative to contract locally delivered services to install and set up the DS6000 Storage Manager. Do not use a laptop for the management console, because communication with the DS6000 is lost if the laptop is shut down or moved.
f2d00069
f2d00067
Before you can install the DS Storage Manager software on the computer that you will use to manage your storage system, you must ensure that your computer meets a minimum set of hardware and operating system compatibility requirements: v IBM Personal Computer compatible with the following components: 1.4 GHz Pentium 4 processor 256 KB cache 1 GB memory 1 GB disk space for the DS Storage Manager software 1 GB work space per managed server enclosure Ethernet IP connectivity to each processor card Ethernet IP connectivity to external network (for call home and remote support) USB port or serial port for modem connection CD connectivity If you want to order a management console, consider the IBM 8143 ThinkCentre M51 Model 34U (8143-34U) Desktop system with a 3.2 GHz/800 MHz Intel Pentium 4 Processor. If a monitor also is required, IBM suggests the IBM 6737 ThinkVision C170 (6737-P6N) 17-inch full flat shadow mask CRT color monitor with a flat screen (16-inch viewable-image). Ensure that your Windows PC is using one of the supported operating systems that are listed in Table 1. Note: The DS Storage Manager is not supported on any Windows 64-bit operating system.
Table 1. Supported operating systems Full management console install X X X (English only) See Note. X (English only) See Note. X (English only) See Note.
Operating System Windows Server 2003 Enterprise Edition Windows Server 2003 Standard Edition Windows 2000 Advanced Server SP4 Windows 2000 Server SP4 Windows 2000 Professional SP4 Windows XP Professional SP1 Windows XP Professional SP1a Windows XP Professional SP2
Note: Windows 2000 Advanced Server SP4, Windows 2000 Server SP4, and Windows 2000 Professional SP4, require update 818043.
Ensure that your Windows PC has the regional settings option that is specified to your language and country or region.
Ensure that animation is turned on in your browser if you want to observe the installation progress bars that are associated with the DS Storage Manager installation. Use the following instructions for your specific browser: v Internet Explorer 1. From the Tools menu, select Internet Options. 2. Select the Advanced tab and scroll down to the Multimedia section. 3. Check Play animations in web pages. v Netscape 1. From the Edit menu, select Preferences. 2. Double-click on Privacy and Security. 3. Select Images and select as many times as the image specifies in the Animated image should loop section. To allow your browser to display the DS Storage Manager and the Information Center in separate windows, ensure that the Internet options are not set to reuse windows for launching shortcuts. 1. Select Start, Settings, Control panel, then Internet Options. 2. On the Advanced tab, ensure the Reuse windows for launching shortcuts checkbox is not selected. 3. Click Apply.
Performance features
The DS6000 series is built upon 2 Gbps fibre-channel technology that can help bring high availability RAID-protected storage with scalable capacity, increased addressing capabilities, and connectivity to a wide range of storage area network (SAN) applications. The DS6000 series provides the following technology and hardware to meet todays on demand business environments: Integrated RAID controller technology The DS6000 series features IBMs 32-bit PowerPC microprocessor, a fourth generation processing technology. High availability The DS6000 series is designed with component redundancy to eliminate single points of hardware failure, and no single point of repair other than the enclosure. Industry standard fibre-channel disk drives The DS6000 series offers a selection of 2 GB fibre-channel disk drives, including 300 GB drives, and 500 GB, 7200 rpm fibre-channel ATA (FATA) disk drives, which allow the DS6000 series to scale up to a capacity of 64 TB. Parallel Access Volumes Parallel Access Volumes (PAV) can provide significant performance enhancements in zSeries environments by enabling simultaneous processing for multiple I/O operations to the same logical volume, which can help to significantly reduce device queue delays. This is achieved by defining multiple addresses per volume. With Dynamic PAV, the assignment of addresses to volumes can be automatically managed to help the workload meet its performance objectives and reduce overall queuing.
PAV is an optional feature for the DS6000 series and also requires the purchase of the FICON Attachment feature. LUN and volume management LUN and volume creation and deletion is nondisruptive. When you delete a LUN or volume, the capacity can immediately be reused. You can configure LUN and volumes to span arrays, which allows larger LUNs and volumes. Addressing capabilities The DS6000 series allows the following: v Up to 32 logical subsystems v Up to 8192 logical volumes v Up to 1040 volume groups Simplified storage management for zSeries with z/OS The DS6000 series supports a new 65 520 cylinder 3390 volume. This volume option has a capacity of approximately 55.7 GB. It helps relieve addressing constraints, improve disk resource use, and improve storage administrator productivity by providing the ability to consolidate multiple disk volumes into a single address. System management The DS6000 series provides online and offline configuration capability features and a graphical user interface (GUI) that is designed to offer increased ease of use. A single command line interface (CLI) supports both logical configuration and copy services. Online Information Center The online Information Center is an information database that provides the opportunity to quickly familiarize yourself with the major aspects of the DS6000 series and to easily recognize the topics for which you might require more information. It provides information regarding user assistance for tasks, concepts, reference, user scenarios, tutorials, and other types of user information. Because the information is all in one place rather than across multiple publications, you can access the information that you need more efficiently and effectively.
RAID implementation
RAID implementation improves data storage reliability and performance. Redundant array of independent disks (RAID) is a method of configuring multiple disk drives in a storage subsystem for high availability and high performance. The collection of two or more disk drives presents the image of a single disk drive to the system. In the event of a single device failure, data can be read or regenerated from the other disk drives in the array. With RAID implementation, the DS6000 series offers fault-tolerant data storage by storing the data in different places on multiple disk drive modules (DDMs). By placing data on multiple disks, input/output operations can overlap in a balanced way to improve the basic reliability and performance of the attached storage devices. Physical capacity for the DS6000 series can be configured as RAID 5, RAID 10, or a combination of both. RAID 5 can offer excellent performance for most applications,
while RAID 10 can offer better performance for selected applications, in particular, high random write content applications in the open systems environment. You can reconfigure RAID 5 disk groups as RAID 10 disk groups or vice versa.
RAID 5 overview
RAID 5 is a method of spreading volume data across multiple disk drives. The DS6000 series supports RAID 5 arrays. RAID 5 increases performance by supporting concurrent accesses to the multiple DDMs within each logical volume. Data protection is provided by parity, which is stored throughout the drives in the array. If a drive fails, the data on that drive can be restored using all the other drives in the array along with the parity bits that were created when the data was stored.
RAID 10 overview
RAID 10 provides high availability by combining features of RAID 0 and RAID 1. The DS6000 series supports RAID 10 arrays. RAID 0 increases performance by striping volume data across multiple disk drives. RAID 1 provides disk mirroring which duplicates data between two disk drives. By combining the features of RAID 0 and RAID 1, RAID 10 provides a second optimization for fault tolerance. RAID 10 implementation provides data mirroring from one DDM to another DDM. RAID 10 stripes data across half of the disk drives in the RAID 10 configuration. The other half of the array mirrors the first set of disk drives. Access to data is preserved if one disk in each mirrored pair remains available. In some cases, RAID 10 offers faster data reads and writes than RAID 5 because it does not need to manage parity. However, with half of the DDMs in the group used for data and the other half used to mirror that data, RAID 10 disk groups have less capacity than RAID 5 disk groups.
Licensed functions
Activate licensed features before you configure your DS6000 series. Before you can configure your DS6000 series, you must activate your licensed features to enable the functions purchased on your machine. The DS6000 series is licensed at the following levels: v Machine licensing uses licensed machine code to activate base functions on your machine. When you receive a DS6800 and/or DS6000 expansion enclosure, you receive an licensed machine code agreement. The use of the machine constitutes acceptance of the license terms outlined in the licensed machine code agreement. The DS6800 system requires licensed machine code level 5.0.0, or later. Some DS6000 series features and functions may not be available or supported in all environments. Current information on supported environments, prerequisites, and minimum operating systems levels is available at: http://www.ibm.com/ servers/storage/disk/ds6000/ v Operating environment licensing manages the machine operating environment and is required on every DS6800 system. The extent of IBM authorization
acquired through the DS6800 feature numbers (50xx) must cover the physical capacity of the DS6800 system, where system is defined as the base enclosure and all attached expansion enclosures. If the operating environment license has not been acquired and activated on the machine, disk drives installed within the DS6800 system cannot be logically configured for use. Upon activation, disk drives can be logically configured up to the extent of authorization. As additional disk drives are installed, the extent of IBM authorization must be increased by acquiring additional DS6800 feature numbers (5xxx). Otherwise, the additional disk drives cannot be logically configured for use. v Feature licensing controls the licenses of features of each DS6800. Each DS6800 licensed function feature number enables the use of, and establishes the extent of, IBM authorization for licensed functions that are acquired for a DS6800 system. Each licensed function feature number is applicable only for the specific DS6800 (by serial number) for which it was acquired and is not transferable to another serial numbered DS6800. To activate the feature licenses for your DS6000 series, you must access the Disk Storage Feature Activation (DSFA) application from the IBM Web site.
DS6000 Interfaces
This section describes the following interfaces: v IBM System Storage DS Storage Manager v IBM System Storage DS Command-Line Interface v IBM System Storage DS Open Application Programming Interface v IBM TotalStorage Productivity Center for Disk v IBM TotalStorage Productivity Center for Replication
IBM System Storage DS Storage Manager

The IBM System Storage DS Storage Manager is an interface that is used to perform logical configurations, firmware upgrades, and Copy Services management functions. The DS Storage Manager software must be installed on a computer (management console) that you provide. You can install the DS Storage Manager as a GUI (graphical mode) or as an unattended (silent) mode installation for the supported operating systems. The unattended (silent) mode installation option allows you to run the installation program unattended. Use this method of installation to customize a response file and issue a command from a command prompt window. The response file is a template on the IBM System Storage Storage Manager CD. The DS Storage Manager can be accessed from any location that has network access using a Web browser. It offers you the following choices: Simulated configuration This component provides the ability to create or modify logical configurations when your storage unit is disconnected from the network. After creating the configuration, you can save it and then apply it to a network attached storage unit at a later time.
This simulated configuration tool is installed on your server and can be used for the configuration of a DS6000 series at initial installation. Real-time configuration This component provides you with real-time (online) configuration support, including the ability to create logical configurations and use Copy Services features when your storage unit is attached to the network. Express configuration This component provides the simplest and fastest configuration method. Copy services This component allows you to process copy services functions.
The DS command-line interface

The IBM System Storage DS command-line interface (CLI) enables open systems hosts to invoke and manage FlashCopy and Metro and Global Mirror functions through batch processes and scripts. The DS CLI provides a full-function set of commands that allows you to check your storage unit configuration and to perform specific application functions, when necessary. Many of the values that are used or reported with the DS CLI commands are hexadecimal. Note: Before you can use the DS CLI commands, ensure that the following conditions are met: v Your management console must be equipped with the DS Storage Manager graphical user interface (GUI). v The GUI must have been installed as a full management console installation management type. v Your storage unit must be configured (part of DS Storage Manager postinstallation instructions). v You must activate your licensed functions (part of DS Storage Manager postinstallation instructions) before you can use the CLI commands that are associated with Copy Services functions. v You must not start more than 100 DS CLI sessions simultaneously. Starting more than 100 DS CLI sessions simultaneously can result in connection problems. v You cannot install the DS CLI on a Windows 64-bit operating system. The following list highlights a few of the specific types of functions that you can perform with the DS command-line interface: v Check and verify your storage unit configuration v Check the current Copy Services configuration that is used by the storage unit v Create new logical storage and Copy Services configuration settings v Modify or delete logical storage and Copy Services configuration settings
DS open application programming interface

The IBM System Storage DS Open Application Programming Interface (API) is a nonproprietary storage management client application that supports routine LUN management activities, such as LUN creation, mapping and masking, and the creation or deletion of RAID 5 and RAID 10 volume spaces. The DS Open API
10
supports these activities through the use of the Storage Management Initiative Specification (SMI-S), as defined by the Storage Networking Industry Association (SNIA). The DS Open API helps integrate configuration management support into storage resource management (SRM) applications, which allow customers to benefit from existing SRM applications and infrastructures. The DS Open API also enables the automation of configuration management through customer-written applications. Either way, the DS Open API presents another option for managing storage units by complementing the use of the IBM System Storage DS Storage Manager web-based interface and the DS command-line interface. You must implement the DS Open API through the IBM System Storage Common Information Model (CIM) agent, a middleware application that provides a CIM-compliant interface. The DS Open API uses the CIM technology to manage proprietary devices as open system devices through storage management applications. The DS Open API allows these storage management applications to communicate with a storage unit. The DS Open API supports the IBM System Storage DS8000 and the IBM System Storage DS6000, and the IBM TotalStorage Enterprise Storage Server. It is available for the AIX, Linux, and Windows operating system environments and must be used on storage units that have fibre-channel ports.
Host systems attachment overview

The DS6000 storage unit provides a variety of host attachments so that you can consolidate storage capacity and workloads for open-systems hosts, S/390 hosts, and eServer zSeries hosts. You can configure the storage unit for fibre-channel adapters, for support of Fibre Channel Protocol (FCP) and fibre connection (FICON) protocol . For fibre-channel attachments, you can establish zones. The zones must contain a single port that is attached to a system adapter with the desired number of ports that are attached to the storage unit. By establishing zones, you reduce the possibility of interactions between system adapters in switched configurations. You can establish the zones by using either of two zoning methods: v Port number v Worldwide port name You can configure switch ports that are attached to the storage unit in more than one zone. This enables multiple host system adapters to share access to the storage unit fibre-channel ports. Shared access to a storage unit fibre-channel port might come from host platforms that support a combination of bus adapter types and the operating systems.
IBM System Storage Resiliency Family

IBM System Storage Resiliency Family is a set of products and features that can help you implement storage solutions to keep your business running 24 hours a day, 7 days a week. This set of products provide disaster recovery, data migration, and data duplication functions.
11
As a part of the IBM System Storage Resiliency family, the DS6000 supports Copy Service functions that contribute to the protection of your data. These functions are also supported on the IBM TotalStorage Enterprise Storage Server. The following IBM System Storage Resiliency family functions are available as optional features: v Point-in-time copy, which includes IBM System Storage FlashCopy The FlashCopy function enables you to make point-in-time, full volume copies of data, so that the copies are immediately available for read or write access. For zSeries environments, you can also use FlashCopy function to perform data set level copies of your data. v Remote mirror and copy, which includes the following functions: IBM System Storage Metro Mirror (previously known as Synchronous PPRC) Metro Mirror provides real-time mirroring of logical volumes between two DS6000 storage units that can be located up to 300 km from each other. It is a synchronous copy solution where write operations are completed on both copies (local and remote site) before they are considered to be done. IBM System Storage Global Copy (previously known as PPRC Extended Distance) Global Copy is a nonsynchronous long-distance copy function where incremental updates are sent from the local to the remote site on a periodic basis. IBM System Storage Global Mirror (previously known as Asynchronous PPRC) Global Mirror is a long-distance remote copy function across two sites using asynchronous technology. Global Mirror processing is designed to provide support for virtually unlimited distance between the local and remote sites, with the distance typically limited only by the capabilities of the network and the channel extension technology. The point-in-time and remote mirror and copy features are supported across various server environments such as zSeries, pSeries, iSeries and servers from Sun and Hewlett-Packard. You can manage these functions through a command-line interface called the DS CLI and a Web-based interface called the DS Storage Manager. The DS Storage Manager allows you to set up and manage the following types of data-copy functions from any point where network access is available:
Point-in-time copy (FlashCopy)

The FlashCopy function enables you to make point-in-time, full volume copies of data, with the copies immediately available for read or write access. For zSeries environments, you can also use the FlashCopy function to perform data set level copies of your data. You can use the copy with standard backup tools that are available in your environment to create backup copies on tape. FlashCopy is an optional function. To use it, you must purchase the point-in-time feature code 52xx (which can include codes 5200, 5201, 5202, 5203, or 5204). The FlashCopy function creates a copy of a source volume on the target volume. This copy is called a point-in-time copy. When you initiate a FlashCopy operation, a FlashCopy relationship is created between a source volume and target volume. A FlashCopy relationship is a mapping of the FlashCopy source volume and a
12
FlashCopy target volume. This mapping allows a point-in-time copy of that source volume to be copied to the associated target volume. The FlashCopy relationship exists between this volume pair from the time that you initiate a FlashCopy operation until the storage unit copies all data from the source volume to the target volume or you delete the FlashCopy relationship, if it is a persistent FlashCopy. One of the main benefits of the FlashCopy function is that the point-in-time copy is immediately available for creating a backup of production data. The target volume is available for read and write processing so it can be used for testing or backup purposes. Data is physically copied from the source volume to the target volume using a background process. (A FlashCopy operation without a background copy is also possible, which allows only data that is modified on the source to be copied to the target volume.) The amount of time that it takes to complete the background copy depends on the following criteria: v The amount of data being copied v The number of background copy processes that are occurring v The other activities that are occurring on the storage units The FlashCopy function supports the following copy options: Consistency groups Creates a consistent point-in-time copy of multiple volumes, with negligible host impact. You can enable FlashCopy consistency groups from the DS CLI. Change recording Activates the change recording function on the volume pair that is participating in a FlashCopy relationship. This enables a subsequent refresh to the target volume. Establish FlashCopy on existing Metro Mirror source Allows you to establish a FlashCopy relationship where the target volume is also the source of an existing remote mirror and copy source volume. This enables you to create full or incremental point-in-time copies at a local site and then use remote mirroring commands to copy the data to the remote site. Fast reverse Reverses the FlashCopy relationship without waiting for the finish of the background copy of the previous FlashCopy. This option applies to the Global Mirror mode. Inhibit writes to target Ensures that write operations are inhibited on the target volume until a refresh FlashCopy operation is complete. Multiple Relationship FlashCopy Allows a source volume to have multiple (up to 12) target volumes at the same time. Persistent FlashCopy Allows the FlashCopy relationship to remain even after the FlashCopy operation completes. You must explicitly delete the relationship. Refresh target volume Provides the ability to refresh a FlashCopy relationship, without recopying all tracks from the source volume to the target volume.
13
Resynchronizing FlashCopy volume pairs Provides the ability to update an initial point-in-time copy of a source volume without having to recopy your entire volume. Reverse restore Reverses the FlashCopy relationship and copies data from the target volume to the source volume.
Remote mirror and copy

The remote mirror and copy feature is a flexible data mirroring technology that allows replication between a source volume and a target volume on one or two disk storage units. You can also issue remote mirror and copy operations to a group of source volumes on one logical subsystem (LSS) and a group of target volumes on another LSS. (An LSS is a logical grouping of up to 256 logical volumes for which the volumes must have the same disk format, either count key data or fixed block.) Remote mirror and copy is an optional feature that allows for data backup and disaster recovery. To use it, you must purchase the remote mirror and copy code 53xx (which can include codes 5300, 5301, 5302, 5303, or 5304). DS6000 storage units can participate in remote mirror and copy solutions with the DS8000 series, ESS Model 750, and ESS Model 800. The remote mirror and copy feature provides synchronous (Metro Mirror) and asynchronous (Global Copy) data mirroring. The main difference is that the Global Copy feature can operate at very long distances, even continental distances, with minimal impact on applications. Distance is limited only by the network and channel extenders technology capabilities. The maximum supported distance for Metro Mirror is 300 km. With Metro Mirror, application write performance is dependent on the available bandwidth. Global Copy allows you to better use your available bandwidth capacity, therefore allowing you to include more of your data to be protected. The enhancement to Global Copy is Global Mirror, which uses Global Copy and the benefits of FlashCopy to form consistency groups. (A consistency group is a set of volumes that contain consistent and current data to provide a true data backup at a remote site.) Global Mirror uses a master storage unit (along with optional subordinate storage units) to internally, without external automation software, manage data consistency across volumes using consistency groups. Consistency groups can also be created using the freeze and run functions of Metro Mirror. The freeze and run functions, when used with external automation software, provide data consistency for multiple Metro Mirror volume pairs. The following sections describe the remote mirror and copy functions. Synchronous mirroring (Metro Mirror) Provides real-time mirroring of logical volumes (a source and a target) between two storage units that can be located up to 300 km from each other. With Metro Mirror copying, the source and target volumes can be on the same storage unit or on separate storage units. You can locate the storage unit at another site, some distance away. Metro Mirror is a synchronous copy feature where write operations are completed on both copies (local and remote site) before they are considered
14
to be complete. Synchronous mirroring means that a storage server constantly updates a secondary copy of a volume to match changes made to a source volume. The advantage of synchronous mirroring is that there is minimal host impact for performing the copy. The disadvantage is that since the copy operation is synchronous, there can be an impact to application performance because the application I/O operation is not acknowledged as complete until the write to the target volume is also complete. The longer the distance between primary and secondary storage units, the greater this impact to application I/O, and therefore, application performance. Asynchronous mirroring (Global Copy) Copies data nonsynchronously and over longer distances than is possible with the Metro Mirror feature. When operating in Global Copy mode, the source volume sends a periodic, incremental copy of updated tracks to the target volume instead of a constant stream of updates. This causes less impact to application writes for source volumes and less demand for bandwidth resources, while allowing a more flexible use of the available bandwidth. The updates are tracked and periodically copied to the target volumes. As a consequence, there is no guarantee that data is transferred in the same sequence that was applied to the source volume. To get a consistent copy of your data at your remote site, you must periodically switch from Global Copy to Metro Mirror mode, then either stop the application I/O or freeze data to the source volumes using a manual process with freeze and run commands. The freeze and run functions can be used with external automation software such as Geographically Dispersed Parallel Sysplex (GDPS), which is available for z/Series environments, to ensure data consistency to multiple Metro Mirror volume pairs in a specified logical subsystem. Common options for Metro Mirror and Global Copy include the following modes: Suspend and resume If you schedule a planned outage to perform maintenance at your remote site, you can suspend Metro Mirror or Global Copy processing on specific volume pairs during the duration of the outage. During this time, data is no longer copied to the target volumes. Because the primary storage unit keeps track of all changed data on the source volume, you can resume operations at a later time to synchronize the data between the volumes. Copy out-of-synchronous data You can specify that only data that was updated on the source volume while the volume pair was suspended be copied to its associated target volume. Copy an entire volume or not copy the volume You can copy an entire source volume to its associated target volume to guarantee that the source and target volume contain the same data. When you establish volume pairs and elect not to copy a volume, a relationship is established between the volumes but no data is sent from the source volume to the target volume. In this case, it is assumed that the volumes contain exactly the same data
15
and are consistent, so copying the entire volume is not necessary or required. Only new updates are copied from the source to target volumes. Global Mirror Provides a long-distance remote copy across two sites using asynchronous technology. Global Mirror processing is most often associated with disaster recovery or disaster recovery testing. However, it can also be used for everyday processing and data migration. The Global Mirror function mirrors data between volume pairs of two storage units over greater distances without affecting overall performance. It also provides application-consistent data at a recovery (or remote) site in case of a disaster at the local site. By creating a set of remote volumes every few seconds, the data at the remote site is maintained to be a point-in-time consistent copy of the data at the local site. Global Mirror operations periodically invoke point-in-time FlashCopy operations at the recovery site, at regular intervals, without disrupting the I/O to the source volume, thus giving a continuous, near up-to-date data backup. By grouping many volumes into a session, which is managed by the master storage unit, you can copy multiple volumes to the recovery site simultaneously while maintaining point-in-time consistency across those volumes. (A session contains a group of source volumes that are mirrored asynchronously to provide a consistent copy of data at the remote site. Sessions are associated with Global Mirror relationships and are defined with an identifier [session ID] that is unique across the enterprise. The ID identifies the group of volumes in a session that are related and that can participate in the Global Mirror consistency group.)
Disaster recovery using Copy Services

One of the main reasons for using Copy Services functions is to prepare for a possible disaster by backing up, copying, and mirroring your data both at the local (production) and remote sites. Having a disaster recovery plan can ensure that critical data is recoverable at the time of a disaster. Because most disasters are unplanned, your disaster recovery plan must provide a way that allows you to recover your applications quickly, and more importantly, to access your data. Consistent data to the same point-in-time across all storage units is vital before you can recover your data at a backup (normally your remote) site. Most users use a combination of remote mirror and copy and point-in-time copy (FlashCopy) features to form a comprehensive enterprise solution for disaster recovery. In an event of a planned event or unplanned disaster, you can use failover and failback modes as part of your recovery solution. Failover and failback modes help to reduce the time that is required to synchronize remote mirror and copy volumes after you switch between the local (or production) and the remote sites during planned and unplanned outages. Although failover transmits no data, it changes the status of a device, and the status of the secondary volume changes to a suspended primary volume. The Failback command transmits data and can go in either direction depending on which device the Failback command is issued to. Recovery procedures that include failover and failback modes use remote mirror and copy functions, such as Metro Mirror, Global Copy, Global Mirror, Metro/Global Mirror, and FlashCopy.
16
Note: See the IBM System Storage DS6000 Command-Line Interface Users Guide for specific disaster recovery tasks. Data consistency can be achieved using the following methods: Manually using external software (without Global Mirror) If you use Metro Mirror, Global Copy, and FlashCopy functions to create a consistent and restartable copy at your recovery site, you must do a manual and periodic suspend operation at your local site. This means using freeze and run commands together with external automated software and then using the FlashCopy function to make a consistent copy of your target volume for backup or recovery purposes. (Automation software is not provided with the storage unit; it must be supplied by the user.) Note: Freezing of the data is done at the same point-in-time across all links and all storage units. Automatically (with Global Mirror and FlashCopy) If you use a two-site Global Mirror configuration, the process to create a consistent and restartable copy at your remote site is done using an automated process, with minimal or no interruption to your applications. Global Mirror operations automate the process of continually forming consistency groups. It combines Global Copy and FlashCopy operations to provide consistent data at the remote site. A master storage unit (along with subordinate storage units) internally manages data consistency using consistency groups within a Global Mirror configuration. Consistency groups can be created many times per hour to increase the currency of data that is captured in the consistency groups at the remote site. Note: A consistency group is a collection of volumes (grouped in a session) across multiple storage units that are managed together in a session during the creation of consistent copies of data. The formation of these consistency groups is coordinated by the master storage unit, which sends commands over remote mirror and copy links to its subordinate storage units. In a two-site Global Mirror configuration, if you have a disaster at your local site and have to start production at your remote site, you can use the consistent point-in-time data from the consistency group at your remote site to recover when the local site is operational.
Comparison of licensed functions

A key decision that you must make in planning for a disaster is deciding which licensed functions to use to best suit your environment. Table 2 provides a brief summary of the characteristics of the Copy Services features that are available for the storage unit.
Table 2. Comparison of licensed functions Licensed function Metro/Global Mirror Description Three-site, long distance disaster recovery replication Advantages A backup site is maintained regardless of which one of the sites is lost. Considerations Recovery point objective (RPO) might grow if bandwidth capability is exceeded.
17
Table 2. Comparison of licensed functions (continued) Licensed function Metro Mirror Description Synchronous data copy at a distance Advantages No data loss, rapid recovery time for distances up to 300 km. Nearly unlimited distance, suitable for data migration, only limited by network and channel extenders capabilities. Nearly unlimited distance, scalable, and low RPO. The RPO is the time needed to recover from a disaster; that is, the total system downtime. Considerations Slight performance impact.
Global Copy
Continuous copy without data consistency
Copy is normally fuzzy but can be made consistent through synchronization.
Global Mirror
Asynchronous copy
RPO might grow when link bandwidth capability is exceeded.
Logical configuration overview

It is important to understand IBM terminology for storage concepts and the storage hierarchy. In the storage hierarchy, you begin with a disk. Logical groupings of four disks form an array site. Logical groupings of one or two array sites form an array. When you define your array storage type as CKD or fixed block, you create a rank. A rank is divided into a number of fixed-size extents. If you work with an open-systems host, an extent is 1 GB. If you work with IBM eServer zSeries or S/390 systems, an extent is the size of an IBM 3390 Mod 1 disk drive. After you create ranks, your physical storage can be considered virtualized. Virtualization dissociates your physical storage configuration from your logical configuration, so that volume sizes are no longer constrained by the physical size of your arrays. The available space on each rank is divided into extents. The extents are the building blocks of the logical volumes. An extent is striped across all disks of an array. Extents of the same storage type are grouped together to form an extent pool. Multiple extent pools can create storage classes that provide greater flexibility in storage allocation through a combination of RAID types, DDM size, DDM speed, and DDM technology. This allows a differentiation of logical volumes by assigning them to the appropriate extent pool for the desired characteristics. Different extent sizes for the same device type (for example, count-key-data or fixed block) can be supported on the same storage unit, but these different extent types must be in different extent pools. A logical volume is composed of one or more extents. A volume group specifies a set of logical volumes. By identifying different volume groups for different uses (for example, SCSI target, FICON control unit, Remote Mirror and Copy
18
secondaries, FlashCopy targets, and Copy Services), access to the set of logical volumes that are identified by the volume group can be controlled. Volume groups map hosts to volumes.
Disk
Array Site
Array
Rank = CKD Mod 1 Extent with IBM zSeries or S/390 systems = FB 1GB in an Open systems Host Extents Virtualization
Extent Pool
Ex
Volume Groups Map Hosts to Volumes

f2d00137
Logical Volume
Figure 1. Logical configuration sequence
te
nt
Volume Group
The storage management software can be used in Real-time or Simulated modes. When you are connected to storage devices over your network, you can use the Real-time Manager to manage your hardware or configure your storage. When you want to work offline, you can use the Simulated Manager to create or import a configuration. This lets you export a configuration that you have already created to a system when it reaches your site.
19
The custom configuration option is ideal if you want to customize your configuration. The Express Configuration option shortens and simplifies the configuration process, but only allows you to create one host. This is ideal if you want only one host and you want to quickly and easily set up and configure your storage because most storage-appropriation decisions have already been made.
20
Chapter 2. Upgrading your system to use DS CLI

You can upgrade your system to use DS CLI by following the remove and install procedures put in place for DS CLI. However, there are some things that you must consider before you make this upgrade. It is recommended that you upgrade the level of code and then the DS Storage Manager before upgrading your system to use DS CLI. The DS CLI is designed to support the following features that exist on the IBM TotalStorage Enterprise Storage Server (ESS) Models 750 and 800: v A Copy Services domain, configured as part of the IBM TotalStorage Enterprise Storage Server (ESS) Models 750 and 800. v FlashCopy Version 2 and PPRC Version 2 licenses that are available on the ESS. However, the DS CLI is not designed to support the CLI scripts that you have written for these features without modification. As part of your upgrade preparation, consider the following tips and questions: v An upgrade requires that you uninstall the DS CLI and that you reinstall the upgraded DS CLI. This is the most certain way to ensure that you receive a clean installation. However, this uninstall and reinstall process can be a concern where you have customized the system profile file. A reinstallation will most likely overwrite your current system profile file. If you want to keep your current system profile file, do the following actions: Make a copy of your current system profile file and save it in a convenient place. Copy the saved system profile file into the DS CLI installation directory after the installation has completed. This allows you to overwrite the system profile file that was installed with the upgraded DS CLI. v Do you plan to add the DS6000 to your network? If you do, you must install the DS CLI application. This application is used for the configuration, performance, and Copy Services functions. Also, only the DS CLI can be used to perform Copy Services functions between the ESS and the DS models. v Do you plan to keep the DS6000 separate from your network? If you do, you cannot communicate with the ESSs in your network, even for Copy Services functions. You can install the DS CLI on your server and it supports the DS6000, but new scripts must be written that support the ESSs.
21
22
Chapter 3. Installing and removing the CLI

On most systems you can install and remove the DS command-line interface (CLI) using silent mode, console mode, or by using a GUI application.
Supported operating systems for the DS command-line interface

The DS command-line interface (CLI) can be installed on these operating systems. v AIX 5.1, 5.2, 5.3 v HP-UX 11.0, 11i, v1, v2 v HP Tru64 version 5.1, 5.1A v Linux (RedHat 3.0 Advanced Server (AS) and Enterprise Server (ES) v SUSE Linux SLES 8, SLES 9, SUSE 8, SUSE 9 v Novell Netware 6.5 v System i system i5/OS 5.3 v OpenVMS 7.3-1 (or newer) v Sun Solaris 7, 8, 9 v Windows 2000, Windows Datacenter, Windows 2003, and Windows XP Note: The DS CLI cannot be installed on a Windows 64-bit operating system.
DS CLI operational limitations

There are operational limitations associated with the use of the DS CLI. These limitations are described as follows: v Volumes in the same volume space, logical subsystem (LSS), logical control unit (LCU), or address group cannot be of mixed type. They are either fixed block or count key data (CKD). Note: The volume space is called an extent pool. An extent pool contains one or more ranks of a common storage type (fixed block or CKD). v Logical subsystems cannot be created using the DS CLI. A fixed block LSS is automatically created when your first fixed block volume is assigned to the LSS address space. A fixed block LSS is automatically deleted when the last fixed block volume is removed from an LSS address space. Note: You can use DS CLI commands to create, modify, and delete logical control units (LCUs), which are the CKD volume equivalent of a fixed block LSS. v If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must not enable its write acceleration feature. The Remote Mirror and Copy commands might fail if the write acceleration feature is enabled. v A maximum of 256 volumes for each logical subsystem can be defined. v You must not start more than 100 DS CLI sessions simultaneously. Starting more than 100 DS CLI sessions simultaneously can result in connection problems.
23
Preparing for the DS CLI installation

The IBM System Storage DS CLI program enables open systems hosts to invoke and manage FlashCopy and Metro and Global Mirror functions through batch processes and scripts. You can choose to install the DS CLI interface using the unattended (silent) mode, console mode, or graphic mode. The mode of installation that you choose is often dependent on the configuration of your system. Before you use the DS CLI commands, be aware of the following requirements: v Your management console must be equipped with the DS Storage Manager graphical user interface (GUI). v The GUI must have been installed as a Full Management Console installation. v Your storage unit must be configured. The DS Storage Manager is used for this initial configuration. The configuration process includes the following tasks: Selecting your storage complex Assigning your storage unit to the storage complex Designating network information for the storage unit v Before you can use the CLI commands that are associated with Copy Services functions, you must activate your license activation codes (part of DS Storage Manager postinstallation instructions). The DS CLI can be installed on only one of the following supported operating systems:
Supported Host Systems IBM AIX (5.1, 5.2, 5.3) Hewlett-Packard-UX (11.0, 11i, v1, v2) Linux (Red Hat 3.0 Advanced Server [AS] and Enterprise Server [ES]) Installation File Name setupaix.bin setuphp1020.bin or setuphp11x.bin setuplinux.bin for xSeries setupgenericunix.sh for pSeries
SUSE Linux SLES 8, SLES 9, SUSE 8, SUSE 9 setuplinux.bin for xSeries setupgenericunix.sh for pSeries Sun Solaris (7, 8, 9) HP Tru64 (5.1, 5.1A) Novell Netware 6.5 System i system i5/OS 5.3 setupsolarisSparc.bin setupgenericunix.sh setupwin32.exe Add -os400 at a command line after the name of the installation file. For example, setupaix.bin -os400 setupwin32.exe setupos.bin -console
Windows 2000, Windows Datacenter, Windows 2003, and Windows XP UNIX users that do not have an X display
Note: Use the same installation file name for Where os represents the name of your your host operating system as shown in the operating system as shown in the previous previous rows, but add the -console rows. parameter after the installation file name. For example: setupaix.bin -console setuplinux.bin -console
24
v The DS CLI cannot be installed on a Windows 64-bit system. v You must have Java 1.4.1 or later installed on your machine. The installation program checks for this requirement during installation and does not install the DS CLI if you do not have Java 1.4.1 or later. Note: The DS CLI installation CD-ROM contains Java 1.4.2, which you can install if your system is not equipped with this version of Java. v You must use the ksh (Korn shell) or bash (Bourne again shell) shell if you are installing on a HP Tru64. Installshield does not support the sh shell. You must perform all HP Tru64 installations using the setupgenericunix.sh file that is located on the installation compact disc. v AIX installation: The LIBPATH environment variable can interfere with the installation of the DS CLI and can result in the display of the JVM-not-found error. To avoid this interference, disable the LIBPATH environment variable before you install the DS CLI. After the installation of the DS CLI, enable the LIBPATH environment variable so that it can be used with other applications. Run the following commands to sequentially disable the LIBPATH environment variable, install the DS CLI, and restore the LIBPATH environment variable:
export LIBSAVE=$LIBPATH unset LIBPATH setupaix.bin -is:javahome /opt/ibm-Java-whatever/java/bin export LIBPATH=$LIBSAVE unset LIBSAVE
v System i system installation: Note: The installation of DS CLI on a System i system is done remotely from a Windows, AIX or some other system platform. You cannot install the DS CLI directly on a System i system. The System i system and i5/OS must meet the following requirements before the DS CLI can be installed: Prerequisites - The latest Java group program temporary fixes (PTF) - i5/OS 5722-SS1 option 34 - Digital certificate manager - Licensed product 5722-AC3 option *base - Crypto Access Provider 128 bit - Licensed product 5722-DG1option *base - IBM HTTP Server for iSeries - Licensed product 5722-JV1 options 6 - Java Developer Kit 1.4 - The latest cumulative PTF package that is installed on the i5/OS If you are installing onto a System i system, ensure that the machine that you are installing from is network-attached to the iSeries machine. During the installation of the DS CLI application onto a System i system, you must provide the following information: - The name of the iSeries machine to which you are installing the DS CLI application. - The user name and password that is used to access the designated iSeries machine. The installation process installs the DS CLI in the following default directory: AIX /opt/ibm/dscli
HPUX /opt/ibm/dscli
Chapter 3. Installing and removing the command-line interface (CLI)
25
Linux /opt/ibm/dscli Sun Solaris /opt/ibm/dscli Windows C:\Program Files\IBM\dscli HP Tru64 /opt/ibm/dscli iSeries /ibm/dscli Novell Netware SYS:\dscli Perform the following steps in preparation for the DS CLI installation: 1. Log on to your host system as a root user or administrator. 2. Insert the DS CLI product CD into the CD drive. If a window opens for the CD drive, close the window. 3. Mount the CD drive using the mount command according to your system. You can mount your CD drive using the following examples: AIX Create a directory for the CD-ROM by issuing the following command:
mkdir /cdrom -p
Create a file system for the CD-ROM by issuing the following command:
crfs -v cdrfs -p ro -d cd0 -m /cdrom
where cd0 represents the CD-ROM drive. Mount the CD-ROM file system by issuing the following command:
mount /cdrom
HPUX Mount the CD-ROM file system using the path name for your environment by issuing the following commands:
ioscan -funC disk | more mount /dev/dsk/c?t?d? /<cdrom>
Linux Issue the following command on Red Hat systems:

mount /dev/cdrom
Sun Solaris Issue the following command:

mkdir /mnt mount -F hsfs -r /dev/dsk/c0t6d0s2 /mnt
Note: The device name /dev/dsk/c0t6d0s2 is the default name for Sun Solaris. The device name might be different on your system depending on your hardware configuration. Windows You are not required to mount the CD if you are using this operating system. HP Tru64 Issue the following command:
mount -t cdfs -o noversion /dev/rznn /mnt
26
where nn represents the number of CD-ROM drives. Novell Netware You are not required to mount the CD if you are using this operating system. 4. Navigate to your CD drive and proceed with either the unattended (silent), console, or graphic installation.
Installing the DS CLI using the graphical mode

Complete this task to install the DS CLI application on your system using the graphical installation mode. Users of Windows, Novell, UNIX, and System i systems can install the DS CLI using the graphical mode. Consider the following before you perform the installation of the DS CLI application: v You cannot install the DS CLI on a computer that contains the ESS CLI. v You cannot install the DS CLI on a Windows 64-bit operating system. v You must have a version of Java 1.4.1 or higher that is installed on your system in a standard directory. The DS CLI installer checks the standard directories to determine if a version of Java 1.4.1 or higher exists on your system. If this version is not found in the standard directories, the installation fails. The DS CLI installation CD contains the Java 1.4.2 version. You can install this version from the CD and continue with the installation of the DS CLI application. v If the DS CLI application was installed on your client or host machine in the past, ensure that you end any active sessions of the DS CLI before you run the DS CLI installation CD. v If you are installing onto a Novell system, you are directed to provide the following information: The directory where your Windows drive is mapped The JAVA HOME directory where the version of Java that you want to use is located. v System i and i5/OS installation considerations: The latest Java group PTF i5/OS 5722-SS1 option 34 - Digital certificate manager Licensed product 5722-AC3 option *base - Crypto Access Provider 128 bit Licensed product 5722-DG1option *base - IBM HTTP Server for iSeries Licensed product 5722-JV1 options 6 - Java Developer Kit 1.4 The latest cumulative tape (CUM) package that is installed on the i5/OS The machine that you are installing from must be connected to the i5/OS through an IP connection. You can install the DS CLI application using the graphical mode with the help of an installation wizard. Before you can use the DS CLI, some operating systems require that you restart your system after the installation is complete. Or, you might be required to open a new command prompt window to start a DS CLI session. Note: After you install the new version of DS CLI, your old DS CLI sessions might be unusable.
27
Perform the following steps to install the DS CLI application using the graphical mode: 1. Start the setup file that is appropriate for your operating system. If you are ultimately installing the DS CLI onto a System i system, add -os400 to your command that includes the setup file. For example, setupwin32.exe -os400 Initially the DS CLI installer checks your standard directories for the correct version of Java. If the correct version of Java is not found, you receive the following message:
A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>
If you receive this message, see Correcting the JVM-not-found error on page 42. Go to Step 2 if you are installing for a System i system. Go to Step 3 for all installations other than System i. 2. The installation wizard displays a sign-on panel that directs you to provide the name of the System i machine to which you are installing the DS CLI application. You must provide the IP address or the DNS name of the i5/OS server. In addition, you must also supply the user name and password that is used to access the designated System i machine. Click OK. 3. The Welcome window opens. Click Next to continue or Cancel to exit the installation.
4. The License Agreement window opens. Select I accept the terms of this license agreement to continue. Click I do not accept the terms of this license agreement or Cancel to exit the installation.
28
1xxb6z
5. The Target System window opens. Select the appropriate target system where you want the DS CLI installed, and then click Next to continue or Cancel to exit the installation.
6. The Installation Location window (Windows has been selected as your operating system) opens. If you selected Novell, go to Step 7 on page 30. If you are installing on a Linux system, go to Step 9 on page 31. If you are satisfied with the Windows default directory, click Next. If not, type the directory path where you want to install the DS CLI and click Next. Do not use blank spaces in the installation path. Click Cancel if you want to exit the installation.
1xxb9o
29
Note: If you are installing onto a System i system, a window that asks for the directory where Java is installed on the i5/OS is displayed when you click Next. Go to Step 8. 7. The Novell Location window opens. Complete the information for where the Windows drive is installed and where the JAVA HOME directory that contains the version of Java you want to use is located. Click Cancel if you want to exit the installation.
8. The Java directory window for the System i system opens. Insert the directory information. Click Next to continue or Cancel to exit the installation.
30
9. The Installation Preview window opens. This window provides the location where the command-line interface will be installed and specifies how much space it will occupy on your drive. Click Next to continue or Cancel to exit the installation. You can change the installation directory by clicking Back.
10. The Installation Progress window opens. This window provides the progress of the command-line interface installation. Click Next to continue or Cancel to exit the installation.
1xxbet
31
f2c00405
11. The Installation Summary window opens. This window provides the installation summary information. Click Next to continue or Cancel to exit the installation.
12. The Installation Complete window opens. A reminder is provided in text to read the Readme file. Click Finish to complete the installation.
32
1xxbkb
1xxbge
Notes: 1. You can verify that the command-line interface has installed correctly by reviewing the CLI.CFG file in the lib/ directory. 2. The DS CLI application is installed in the following two places in i5/OS: v IFS directory IBM/DS_CLI. This directory contains the profiles, exe files, java jars, readme files, and so forth. v The QDSCLI library. This library contains executable code. 3. Before you can invoke the DS CLI application from the i5/OS, you must add the QDSCLI library to the i5/OS library list.
Installing the DS CLI using the console mode

Complete this task to install the DS CLI application on your system using the console mode. The console mode is primarily used for installations on a Linux operating system or on a UNIX operating system without an X display. Users can run the installer from a command prompt on a Windows operating system. Consider the following before you perform the installation of the DS CLI application: v You cannot install the DS CLI on a computer that contains the ESS CLI. v You cannot install the DS CLI on a Windows 64-bit operating system. v You must have a version of Java 1.4.1 or higher that is installed on your system in a standard directory. The DS CLI installer checks the standard directories to determine if a version of Java 1.4.1 or higher exists on your system. If this version is not found in the standard directories, the installation fails. If the installation fails because the correct version of Java is not found, see Correcting the JVM-not-found error on page 42. The DS CLI installation CD contains the Java 1.4.2 version. You can install this version from the CD and continue with the installation of the DS CLI application. v If the DS CLI application was installed on your client or host machine in the past, ensure that you end any active sessions of the DS CLI before you run the DS CLI installation CD.
1xxb1h
33
v If you are installing onto a Novell system, you are directed to provide the following information: The directory where your Windows drive is mapped The directory where the JAVA HOME is located v If you are installing the DS CLI onto an OS/400 system, ensure that the machine that you are installing from is network-attached to the OS/400 machine. v During the installation of the DS CLI application onto an OS/400 system, you must provide the following information: The name of the OS/400 machine to which you are installing the DS CLI application. The user name and password that is used to access the designated OS/400 machine. The console mode is primarily used for installations on a Linux operating system or on a UNIX operating system that does not have an X display. Users can run the installer from a command prompt on a Windows operating system. The console mode installer displays its various screens as text. Before you can use the DS CLI, some operating systems require that you restart your system after the installation is complete. Or, you might be required to open a new command prompt window to start a DS CLI session. Perform the following steps to install the DS CLI using the console mode: 1. Insert the DS CLI installation CD into the CD drive. If the Installshield starts, click the Exit selection to exit. 2. Open a command prompt and locate the setupwin32console.exe or the setuplinux.bin file on the DS CLI CD. 3. Type the following command on the command line (unless you are installing onto an OS/400 system): setup platform<.exe | .bin | .sh> -console. The Welcome screen is displayed. For example, for Windows, type: setupwin32console.exe or, for Linux, type: setuplinux.bin -console For an installation onto an OS/400 system from a Windows operating system, type: setupwin32console.exe -os400 Notes: a. When you issue the setupwin32console.exe command on a Windows operating system, you do not need to include the -console parameter as part of your command. b. Initially the DS CLI installer checks your standard directories for the correct version of Java. If the correct version of Java is not found, you receive the following message:
If you receive this message, see Correcting the JVM-not-found error on page 42.
34
Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... . Searching for Java 1.4.1 by IBM Corporation Verifying Java 1.4.1 by IBM Corporation ....... ------------------------------------------------------------------------------Welcome to the InstallShield Wizard for IBM System Storage DS Command-Line Interface (CLI) The InstallShield Wizard installs IBM System Storage DS Command-Line Interface on your computer. To continue, choose Next. DS Command-Line Interface IBM Corporation Users are encouraged to read the Users Guide PDF and the README file before installing. Both files are located in the cliReadmes/ directory of this CD-ROM. Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]
4. Press 1 for Next. The License agreement screen is displayed. You can also press 3 to Cancel, or 4 to Redisplay.
Please read the following license agreement carefully. Use of the IBM System Storage DS Command-Line Interface (CLI) is governed by the IBM Agreement for Licensed Internal Code, a copy of which has been provided with your DS Machine. (C) Copyright 2004, 2005 International Business Machines Corporation All rights reserved. Please choose from the following options: [ ] 1 - I accept the terms of the license agreement. [ ] 2 - I do not accept the terms of the license agreement. To select an item enter its number, or 0 when you are finished: [0] 1 [X] 1 - I accept the terms of the license agreement. [ ] 2 - I do not accept the terms of the license agreement. To select an item enter its number, or 0 when you are finished: [0] 1 Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
5.
Press 1 to accept the terms of the license agreement. A confirmation prompt is returned with an X next to the acceptance line and a 0 in the finished line. a. Press Enter to notify the installer that you are finished with this section. The next action line of instructions is displayed. b. Press 1 for Next. One of the following results occurs depending on the system that you are using to install the DS CLI: v The Windows Users screen is displayed if you are installing on a Windows operating system or are pointing to a Novell system. Continue with the next step.
35
v The Install Location screen is displayed if you are installing on a Linux operating system. Continue with Step 10 on page 37. You can also press 3 to Cancel, or 4 to Redisplay.
Please select the appropriate target system: [X] 1 - Windows [ ] 2 - Novell Netware To select an item enter its number, or 0 when you are finished: [0] Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
If you want the Windows operating system, press 1. If you want the Novell operating system, press 2. If you choose 1 or 2, a confirmation prompt is returned with an X next to the system that you choose and with a 0 in the finished line. a. Press Enter to notify the installer that you are finished with this section. b. Press 1 to continue. The Install Location screen is displayed. This screen can be different depending whether you choose Windows, Novell, or are installing for an OS/400. v Continue to Step 7 if you choose Windows. v Continue to Step 8 if you choose Novell. v Continue to Step 9 on page 37 if you are installing for an OS/400. You can also press 2 to go to the previous screen, 3 to Cancel, or 4 to Redisplay. 7. (Windows and Linux only) Observe the default directory path that is displayed in the Install Location screen and take the following action (example: the Install Location screen at the end of this step): a. Press 1 to continue if you are satisfied with the default directory. b. Change the directory path where you want to install the CLI (do not use blank spaces in the path) if you are not satisfied, and press 1 to continue. 6. c. Go to Step 10 on page 37 after pressing 1. The Install Location screen is displayed after pressing 1. You can also press 2 to go to the previous screen, 3 to Cancel, or 4 to Redisplay.
IBM System Storage DS Command-Line Interface Install Location Please specify a directory or press Enter to accept the default directory. Directory Name: [C:\Program Files\ibm\dscli]or [opt/ibm/dscli] Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
8. (Novell only) Observe the default directory paths that are displayed in the Installation Location screen for Novell and perform the following action (example: the Install Location screen at the end of this step): Notes:
36
a. SYS represents where the Windows drive is mapped in a Novell system. However, this could also be SYS:\DS\CLI or a volume other than SYS: b. J: (could be any drive letter) a. Press 1 to continue if you are satisfied with the default values. b. Enter the applicable value if you are not satisfied with the default, and press 1 to continue. c. Go to Step 10 after you press 1. The Install Location screen is displayed after you press 1. You can also press 2 to go to the previous screen, 3 to Cancel, or 4 to Redisplay.
IBM System Storage DS Command-Line Interface Install Location Please indicate the Novell location (volume:\directory) where this window J: drive is mapped: Enter a value: [SYS:] Please indicate the JAVA HOME location on Novell: (JVM 1.4.1 or above is required) Enter a value: [SYS:\JAVA] Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
9. (Windows and OS/400 only) Record the default directory path that is displayed in the Install Location screen for OS/400 and perform the following action (example: the Install Location screen shown at the end of this step): a. Press 1 to continue if you are satisfied with the default value. b. Enter the applicable value if you are not satisfied with the default, and press 1 to continue. c. Go to Step 10 after you press 1. The Install Location screen is displayed after you press 1. You can also press 2 to go to the previous screen, 3 to Cancel, or 4 to Redisplay.
Please indicate the directory where Java is installed on the OS/400 Enter a value: [/QOpenSys] Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
10. Verify that the installation directory shown on the Install Location screen is the one you want the DS CLI application installed in. Press 1 to continue. The Installation Progress screen is displayed. Note: Depending on the current configuration of your system, the total size of the installation can vary. You can also press 2 to go to the previous screen, 3 to Cancel, or 4 to Redisplay.
37
IBM System Storage DS Command-Line Interface will be installed in the following location: C:\Program Files\ibm\dscli
for a total size: 16.6 MB Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
11. Observe the installation progress and wait until the DS CLI installation is completed before pressing 1. Press 1 after the installation completes (there is no reminder to press 1 when the installation is completed). The Install Completed screen is displayed after you press 1.
Installing command-line Interface. Please wait... Installing IBM System Storage DS Command-Line Interface. Please wait...
|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||| |-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% ||||||||||||||||||||||||||||||||||||||||||||||||||
Creating uninstaller...
12. Press 1 to continue if you are satisfied with the installation. The Readme screen is displayed (not shown). You can also press 3 to Cancel, or 4 to Redisplay.
The InstallShield Wizard has successfully installed IBM System Storage DS Command-Line Interface. Choose Next to continue the wizard. Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]
13.
Press Enter to read the readme information or press 3 to finish the installation process. If you press Enter, you must press q to quit the readme file and then press 3 to finish the installation process. The Readme screen contains specific information about the DS CLI for your operating system. Note: If you are installing on a Windows operating system, you might have to restart your system. If this is the case, the following screen is displayed and you must complete the next step.
38
To complete the installation you must restart your computer. [X] 1 - Yes, restart my computer. [ ] 2 - No, I will restart my computer at a later time. To select an item enter its number, or 0 when you are finished:
14. Select the restart computer item that you want and press 3 to finish the installation process. Use of the DS CLI application becomes effective with a reboot of your system. You can verify that the command-line interface has installed correctly by reviewing the CLI.CFG file in the lib subdirectory of the install directory that you defined in Step 6.
Installing the DS CLI using the unattended (silent) mode

Complete this task to install the DS CLI application using the unattended (silent) mode. Consider the following before you perform the installation of the DS CLI application: v You cannot install the DS CLI on a computer that contains the ESS CLI. v You cannot install the DS CLI on a Windows 64-bit operating system. v You must have installed a version of Java 1.4.1 or higher on your system in a standard directory. The DS CLI installer checks the standard directories to determine if a version of Java 1.4.1 or higher exists on your system. If this version is not found in the standard directories, the installation fails. If the installation fails because the correct version of Java is not found, see Correcting the JVM-not-found error on page 42. The DS CLI installation CD-ROM contains the Java 1.4.2 version. You can install this version from the CD and continue with the installation of the DS CLI application. v If the DS CLI application was installed on your client/host machine in the past, ensure that you end any active sessions of the DS CLI before you run the DS CLI installation CD. v If you are installing onto a Novell system, you are directed to provide the following information: The directory where your Windows drive is mapped. The directory where the JAVA HOME is located. v If you are installing onto a System i system, ensure that the machine that you are installing from is network-attached to the iSeries machine. v During the installation of the DS CLI application onto an System i system, you must provide the following information: The name of the iSeries machine to which you are installing the DS CLI application. The user name and password that is used to access the designated iSeries machine.
39
The unattended (silent) mode of installation allows you to perform the installation from the command line without prompts or feedback. You can create an options/response file and use a text editor to change the default selections to a selection of your choosing. Before you can use the DS CLI, some operating systems require that you restart your system after the installation is complete. Or, you might be required to open a new command prompt window to start a DS CLI session. Note: After you install the new version of DS CLI, your old DS CLI sessions might be unusable. Perform the following steps to install the DS CLI application using the unattended (silent) mode: 1. Log on to your system as an administrator. 2. Insert the DS CLI installation CD into the CD drive. If the InstallShield starts, click the Exit selection to exit. 3. Type the following command for all systems except the System i system at the command prompt setup<platform>.<exe|bin|sh> -silent. Press the Enter key on your keyboard to start the installation process in unattended (silent) mode. The silent installation process applies all the default options to your installation. If you want to modify the default options, go to the next step. Note: Initially the DS CLI installer checks your standard directories for the correct version of Java. If the correct version of Java is not found, you receive the following message:
If you receive this message, see Correcting the JVM-not-found error on page 42. 4. Generate the template response file if you must modify the defaults. Two example response files are provided in the cliReadmes directory of the CD: one for Windows, Novell, and iSeries installations, and one for all UNIX and Linux installations. You can copy the applicable response file to a directory of your choice. The following output is an example of the Windows, Novell, or iSeries response or options file.
40
InstallShield Options File Template # # Wizard name: Install # Wizard source: setup.jar # Created on: Mon May 09 16:35:04 MST 2005 # Created by: InstallShield Options File Generator # # This file can be used to create an options file (i.e., response file) for the # wizard "Install". Options files are used with "-options" on the command-line # to modify wizard settings. # # The settings that can be specified for the wizard are listed below. To use # this template, follow these steps: # # 1. Enable a setting below by removing leading ### characters from the # line (search for ### to find settings you can change). # # 2. Specify a value for a setting by replacing the characters <value>. # Read each settings documentation for information on how to specify its # value. # # 3. Save the changes to the file. # # 4. To use the options file with the wizard, specify -options <file name> # as a command-line argument to the wizard, where <file name> is the name # of this options file. # ######################################################################## ######################################################################## # # License Agreement State # # The initial state of the License Agreement panel. Legal values are: # # 0 - Nothing will be selected # 1 - "I accept the terms of the license agreement." will be selected # 2 - "I do not accept the terms of the license agreement." will be # selected # # For example, to configure the panel to initially display "I accept the # terms of the license agreement.", use # # -W license.selection=2 -W license.selection=1 ######################################################################## # # User Input Field - Win_Novell_select # # This field only has meaning if you are running the installer on Windows. # You must choose whether it should install the Windows CLI or the Novell # CLI. # # If you choose Novell, then make sure that the installLocation (see below) # is on a Novell drive. # # 1 - Novell Netware # 2 - Windows # -W win_user_input.Win_Novell_select="2" ########################################################################
41
IBM System Storage DS command-line Interface Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # ### -P installLocation="C:\Program Files\My Product" # -P installLocation="C:\Program Files\IBM\dscli" ################################################################################ # # User Input Field - os400_java_location # # # This is only used on i5/OS iSeries system installations. # # ### -W os400_java_location_panel.os400_java_location="<value>" # ################################################################################# # # User Input Field - novell_location_mapped # # This is only used on Novell installations. # ### -W novell_user_input.novell_location_mapped="<value>" # ################################################################################# # # User Input Field - novel_java_location # # This is only used on Novell installations. # ### -W novell_user_input.novel_java_location="<value>" # #################################################################################
5. Save the modifications to the response file. 6. Type the following command for all systems (including UNIX and Linux) except the i5/OS iSeries system at the command prompt setup<platform>. <exe|bin|sh> -silent -options options.txt and press the Enter key on your keyboard to start the installation process in unattended (silent) mode. 7. Type the following command if you are installing the DS CLI onto an i5/OS iSeries system setup<platform>. <exe|bin|sh> -os400 -silent -options options.txt and press the Enter key on your keyboard to start the installation process in unattended (silent) mode. You can verify that the command-line interface has installed correctly by reviewing the CLI.CFG file in the lib/ subdirectory of the installation directory.
Correcting the JVM-not-found error

Complete this task to correct the JVM-not-found error. The JVM-not-found error occurs if the DS CLI installer cannot find the correct version of Java in the standard directories of your system. You must have Java 1.4.1 or higher on your system for the DS CLI application to work. Notes: 1. This error might also occur if you are installing the DS CLI on an AIX system. The LIBPATH environment variable can interfere with the
42
installation of the DS CLI and results in the display of the JVM-not-found error. It is recommended that you disable the LIBPATH environment variable before you install the DS CLI. After the installation of the DS CLI, enable the LIBPATH environment variable so that it can be used with other applications. 2. If you have already installed the DS StorageManager, you have installed Java 1.4.2 on your system. Because it was not installed in one of your standard directories, the DS CLI installer did not find it during its initial check. If Java 1.4.1 is not found during the initial check, the following message is displayed:
Perform either step 1 or step 2 of the following steps to correct the JVM not found error (see Step 4 for AIX): 1. (Optional) Run the installer again, and provide the path to the JVM. The following examples represent directories where you can find the correct version of Java: For a Windows system, specify the following:
setupwin32 -is:javahome C:\Program Files\IBM\dsniserver\java\jre
For a Linux system, specify the following:

setuplinux.bin -is:javahome /opt/ibm-Java-whatever/java/bin
Note: If you use this argument, the installer attempts to use whatever JVM that you specify, even if it is an unsupported version. Go directly to step 4 after this step completes. 2. (Optional) Open the DS CLI installation CD and install the Java 1.4.2 version into one of your standard directories. 3. Continue with the installation of the DS CLI application. 4. (AIX) Run the following commands to sequentially disable the LIBPATH environment variable, install the DS CLI, and restore the LIBPATH environment variable:
export LIBSAVE=$LIBPATH unset LIBPATH setupaix.bin -is:javahome /opt/ibm-Java-whatever/java/bin export LIBPATH=$LIBSAVE unset LIBSAVE
Proceed to the next step after you disable the LIBPATH environment variable.
Installing DS CLI on an OpenVMS system

The DS Command-Line Interface (CLI) provides a full function command set that allows you to check your storage unit configuration and perform specific application functions when necessary. It also enables open systems hosts to invoke and manage FlashCopy, Metro and Global Mirror functions through batch processes and scripts.
43
This topic describes how to install the DS CLI on an OpenVMS system. Additionally, it provides hints for integrating the DS CLI into the operating system environment.
Preparing to install the DS CLI on an OpenVMS System

The IBM System Storage DS CLI program enables open systems hosts to invoke and manage FlashCopy and Metro and Global Mirror functions through batch processes and scripts. The DS CLI is installed on an OpenVMS sytem by using the Polycenter Software Installation utility. Be aware of the following requirements before you begin the installation of the DS CLI: v The installation process places all command-line interface files in the [IBMDSCLI...] directory tree as a subdirectory of the Polycenter destination directory. You can specify this directory by using the PRODUCT INSTALL command with the /DESTINATION=devicename:[directoryname] qualifier. If you omit the device name, the Polycenter installation utility uses your current default device. If you omit the directory name, the Polycenter Software Installation utility uses the [VMS$COMMON] directory as the default destination directory. If you do not use the /DESTINATION qualifier at all, the utility installs the software in the location that is defined by logical name PCSI$DESTINATION. If this logical name is not defined, the utility installs the software in SYS$SYSDEVICE:[VMS$COMMON]. v Extract and check the Release Notes file from the DS CLI installation package in the root directory of the installation CD. v Ensure that you have at least 140000 blocks (approximately 70 MB) of free space on the installation disk. v Install the required prerequisite patches operating system patches (ECOs) on your OpenVMS host system. The command-line interface installation process automatically installs Java Runtime Environment (JRE) 1.4.2-4 on your host system. The JRE requires several ECOs. For detailed patch information, see the Java SDK v1.4.2 patch installation page at: http://h18012.www1.hp.com/java/download/ovms/1.4.2/sdk1.4.2_patches.html To download these ECOs, use the HP IT Resource Center (ITRC) database to perform a search for the patches from which you can select. These download steps are described at the Java SDK v1.4.2 patch installation page.
Installing the DS CLI on your OpenVMS system

Use the following steps to install the DS CLI application in your OpenVMS environment. Before you install the DS CLI application, verify that the prerequisite software and hardware are installed on your system. The installation program checks for prerequisites and stops if any prerequisites are missing. 1. Log on to your host system as a user with SYSLCK, SYSNAM, SYSPRV, (or a system UIC), TMPMBX, and CMKRNL privileges. 2. Insert the DS CLI product CD-ROM into the CD drive.
44
3. Mount the CD drive. For example, for an IDE CD device DQA0, type the following command: MOUNT /NOASSIST /OVERRIDE=IDENTIFICATION /MEDIA_FORMAT=CDROM DQA0: A message similar to the following is displayed.
%MOUNT-I-WRITELOCK,volume is write locked %MOUNT-I-CDROM_ISO, : (1 of 1) , mounted on VMS1$DQA0:
For a SCSI CD device DKA nnn, type the following command: MOUNT /NOASSIST /OVERRIDE=IDENTIFICATION /MEDIA_FORMAT=CDROM DKAnnn: where nnn represents the number that is assigned by the OpenVMS system to your CD device. 4. Type the following command: DIRECTORY/FULL DQA0:[000000]IBM-AXPVMSDSCLI-*.PCSI and press Enter to access the command-line interface installation package in the root directory of the CD. Output similar to the following is displayed.
Directory DQA0:[000000] IBM-AXPVMS-DSCLI-V0500-01F96-1.PCSI;1 File ID: (4,7,0) Size: 55.79MB/55.80MB Owner: [0,0] Created: 9-MAR-2005 04:07:22.25 Revised: 9-MAR-2005 04:09:43.98 (1) Expires: None specified Backup: No Backup record Effective: None specified Recording: None specified Accessed: None specified Attributes: None specified Modified: None specified Linkcount: 1 File organization: Sequential Shelved state: Online Caching attribute: Writethrough File attributes: Allocation: 114282, Extend: 0, Global buffer count: 0 Version limit: 0, Backups disabled Record format: Undefined, maximum 0 bytes, longest 0 bytes Record attributes: None RMS attributes: None Journaling enabled: None File protection: System:RWED, Owner:RWED, Group:RWED, World:RWED Access Cntrl List: None Client attributes: None Total of 1 file, 55.79MB/55.80MB
5. Type the following command and press Enter to extract the command-line interface for OpenVMS release notes: PRODUCT EXTRACT RELEASE_NOTES DSCLI /SOURCE=DQA:[000000] /FILE=filespec Note: If you do not use the /FILE qualifier, the release notes are written to the DEFAULT.PCSI$RELEASE_NOTES file in your current default directory. Read the release notes before continuing to ensure that you are equipped with the information that you need to complete your installation successfully. 6. Type the following command and press Enter to invoke the command-line interface installation process: PRODUCT INSTALL DSCLI /SOURCE=DQA0:[000000] /DESTINATION=devicename:[directoryname] /RECOVERY_MODE. A message similar to the following is displayed.
45
The following product has been selected: IBM AXPVMS DSCLI V5.0-1F96 Layered Product Do you want to continue? [YES]
The /DESTINATION qualifier can be omitted from the command. However, IBM recommends that you use the optional /RECOVERY_MODE qualifier. For a detailed description of all PRODUCT INSTALL command qualifiers and parameters, see the HP OpenVMS System Management Utilities Reference Manual or the OpenVMS online help. 7. Press Enter to continue the installation process. The following message is displayed.
Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. IBM AXPVMS DSCLI V5.0-1F96: IBM DS Command Line Interface (DS CLI) (C) Copyright IBM Corp. 1999, 2005. All Rights Reserved. International Business Machines Corporation (IBM) No PAK Do you want the defaults for all options? []
8. Type No and press Enter to review the installation options. Note: You can type Yes if you have decided to install with the default options. The following CLI license message is displayed after typing Yes or No.
License Agreement IBM System Storage DS Command-line Interface Copyright 2005 International Business Machines Corporation All rights reserved. Use of the IBM System Storage DS Command-line Interface (DS CLI) is governed by the IBM Agreement for Licensed Internal Code, a copy of which has been provided with your DS Machine. Answer "Yes" to install the DS CLI code. By installing this code, you are certifying that you have read and accept the IBM DS CLI License agreement. Answer "No" to terminate and exit the IBM DS CLI installation. Do you want to continue? [YES]
9. Press Enter to accept the DS CLI license agreement. The following Java license message is displayed.
46
License Agreement HP Java Run-Time Environment for OpenVMS The IBM DS CLI requires the Java 1.4.2 Java Runtime Environment (JRE). Installing the DS CLI program automatically installs the required JRE. The installed JRE is the intellectual property of and licensed by Hewlett-Packard Company. You can view the license agreement on the World Wide Web at: http://h18012.www1.hp.com/java/download/ovms/1.4.2/ rte1.4.2_license.html Answer "Yes" to install the Java code. By installing this code, you are certifying that you have read and accepted the HP Java License agreement. Answer "No" to terminate and exit the IBM DS CLI installation. Do you want to continue? [YES]
10. Press Enter to accept the Java license agreement. The command-line interface requires Java 1.4.2 on an OpenVMS Alpha host system. If you answer No, the installation process automatically ends and exits. The following library update warning message is displayed.
WARNING: By default the system Help and Message libraries will be updated. The IBM DS CLI program provides local Help and Help Message library files. By default, the CLI instalation integrates these local libraries into the OpenVMS system Help and Help Message libraries. To prevent the system libraries from being modified chose to review the installation options and answer "No" when prompted to update the libraries. Do you want to continue? [YES]
11. Press Enter to continue the installation process. The following configuration question is displayed.
Would you like the local IBM DS CLI Help and Help Message libraries to be integrated into the OpenVMS system libraries? If you answer "Yes", the following OpenVMS libraries will be updated: SYS$COMMON:[SYSHLP]HELPLIB.HLB SYS$COMMON:[SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA If you answer "No", OpenVMS system libraries will not be modified. In every case, local libraries are available under: IBMDSCLI$HELP:IBMDSCLI_OVR.HLB IBMDSCLI$HELP:IBMDSCLI_MESSAGES.MSGHLP$DATA Modify the system Help and Help Message libraries? [YES]
12. Press Enter to confirm the library update option (or type No and press Enter to deny the library update option). The following confirmation message is displayed:
47
Do you want to review the options? [NO]
13. Press Enter to confirm and accept all selections. The following installation message with completion status is displayed.
Execution phase starting ... The following product will be installed to destination: IBM AXPVMS DSCLI V5.0-1F96 DISK$V732_ALPHA:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...60%...70%...80%...90%...100% The following product has been installed: IBM AXPVMS DSCLI V5.0-1F96 Layered Product
14. Review the Installation Verification Procedure (IVP) report, which is similar to the following output, and check for possible errors.
%PCSI-I-IVPEXECUTE, executing test procedure for IBM AXPVMS DSCLI V5.0-1F96 ... dscli ver IBM DSCLI Version: 5.0.1.96 %PCSI-I-IVPSUCCESS, test procedure completed successfully
15. Ensure that the installation completes. When the Polycenter Software Installation utility finishes the command-line interface installation process, a message similar to the following is displayed.
IBM AXPVMS DSCLI V5.0-1F96: IBM DS Command Line Interface (DS CLI) Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @PCSI$DESTINATION:[IBMDSCLI.MGR]IBMDSCLI$STARTUP.COM Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @IBMDSCLI$MANAGER:IBMDSCLI$SHUTDOWN.COM Users of this product require the following lines in their login command procedure: @IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM Release notes for IBM DS CLI available in IBMDSCLI$HELP
16. Unmount the CD drive and remove the CD-ROM. The command-line interface provides program startup, login, and shutdown procedures in the [destinationdir.IBMDSCLI.MGR] directory. The installation process runs the startup and login procedures immediately before invoking the IVP procedure. But for persistent setup, you must integrate the startup, login, and shutdown procedures.
48
Using the DS CLI on an OpenVMS system

To use the DS CLI on an OpenVMS system, you must integrate the required IBMDSCLI$STARTUP.COM and IBMDSCLI$LOGIN.COM procedures.You can also integrate the optional IBMDSCLI$SHUTDOWN.COM procedure. This integration is accomplished when you use the OpenVMS persistent setup procedure. You must add the required IBMDSCLI$STARTUP.COM procedure to your system startup processes. The IBMDSCLI$STARTUP.COM procedure defines the logical names that are required for the command-line interface in your system logical name table and installs some images with enhanced privileges. This procedure is intended to be invoked during the system startup. You also must add the required IBMDSCLI$LOGIN.COM procedure to your system login processes. The IBMDSCLI$LOGIN.COM procedure sets up the JRE that is required by the command-line interface and defines the DSCLI command as a foreign DCL command symbol. It is intended to be invoked during the system-wide SYS$MANAGER:SYLOGIN.COM or user-specific SYS$LOGIN:LOGIN.COM procedure. In order to use the DS CLI interface from start to finish in your OpenVMS system, you can add the optional IBMDSCLI$SHUTDOWN.COM procedure to your system shutdown processes. The IBMDSCLI$SHUTDOWN.COM procedure performs the removal operations for privileged images and undefines system-wide logical names that are associated with the DS CLI. It is intended to be invoked during the system shutdown process. 1. Integrate the IBMDSCLI$STARTUP.COM procedure into your system startup by adding the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM script: $ @destinationdev:[destinationdir.IBMDSCLI.MGR]IBMDSCLI$STARTUP destinationdev Specifies the name of the device that contains the command-line interface installation directory destinationdir Specifies the name of the directory where you just installed the command-line interface. Note: You can alternatively add the IBMDSCLI$STARTUP.COM procedure to the SYSMAN startup database. 2. Integrate the IBMDSCLI$LOGIN.COM procedure into the system-wide or user-specific login by adding the following line: $@IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM Note: Run the IBMDSCLI$LOGIN.COM procedure only after you have successfully run the IBMDSCLI$STARTUP.COM procedure. 3. Integrate the IBMDSCLI$SHUTDOWN.COM procedure by adding the following line to the SYS$MANAGER:SYSHUTDOWN.COM script: $@IBMDSCLI$MANAGER:IBMDSCLI$SHUTDOWN Note: This step is optional. However, processing this step allows your system to make the full use of the DS CLI application.
49
Removing the DS CLI from an OpenVMS system

The removal of the DS CLI application from an OpenVMS system requires not only a removal from your main system but also a removal from your startup, login, and shutdown processes. Perform the following steps to remove the CLI from your OpenVMS system: 1. Log on to your host system as a user with SYSLCK, SYSNAM, SYSPRV (or a system group UIC), TMPMBX, and CMKRNL privileges. 2. Type the following command at the command prompt to start the uninstallation process: PRODUCT REMOVE IBMDSCLI. A message similar to the following is displayed.
The following product has been selected: IBM AXPVMS DSCLI V5.0-1F96 Do you want to continue? [YES]
Layered Product
3. Press Enter to confirm the uninstallation. The following uninstallation confirmation message with completion status is displayed.
The following product will be removed from destination: IBM AXPVMS DSCLI V5.0-1F96 DISK$V732_ALPHA:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
When the uninstallation process ends, a message similar to the following is displayed.
The following product has been removed: IBM AXPVMS DSCLI V5.0-1F96
Layered Product
4. Remove the command-line interface startup, login, and shutdown functions from your system startup, login, and shutdown processes.
Completing DS CLI postinstallation

Complete these tasks to set up the DS CLI application so that you can use the DS CLI to configure your DS6000. You must install the DS CLI before you complete these postinstallation tasks. After you install the DS CLI application, how do you log into the application? After the initial login, what are some of the first tasks that you must accomplish before you can get the full benefit of the DS CLI application? The instructions in this section answer these questions, as well as, describe how to configure your volumes and how to manage potential problems. Before you can use the DS CLI application with the i5/OS (particularly if you are using external load source), you must set up the initial configuration of your DS6000 models. After the initial configuration, you can do a D-mode IPL and begin using the DS CLI application directly from the i5/OS. In the meantime, you can follow the list below as a guide for your initial configuration.
50
1. Initiate the DS CLI to begin using it in either single-shot, script, or interactive command mode. 2. Set up your required user accounts and passwords. 3. Set your DS CLI default configuration settings. 4. Activate your licensed functions. This includes obtaining your feature activation codes and applying the feature activation codes to your storage unit. 5. Enable the remote support and call home functions. You must provide customer contact and network information to enable these functions. 6. Register for the My Support service. 7. Configure new fixed block storage. Use the DS CLI to create and modify fixed block extent pools, arrays, ranks, volumes, and volume groups. You can also configure host ports and connections.
Using the DS CLI application

You must ensure that you have installed the DS Storage Manager using the full-management console installation and that you have configured your domain. Without this domain configuration (which is a one-time process), you cannot use the DS CLI. After you install the DS CLI, three command modes are available to you. You must log into DS CLI to use the command modes. There are three command modes for the DS CLI: v Single-shot v Interactive v Script Note: You must not start more than 100 DS CLI sessions simultaneously. Starting more than 100 DS CLI sessions simultaneously can result in connection problems.
Logging into the DS CLI application

You must log into the DS CLI application to use any of the command modes. You must ensure that you are in the directory where you installed the DS CLI application. The following list provides a reminder of the supported operating systems default directories where the DS CLI is installed if the directory designation is not changed: AIX /opt/ibm/dscli
HPUX /opt/ibm/dscli Linux /opt/ibm/dscli Sun Solaris /opt/ibm/dscli Windows C:\Program Files\IBM\dscli HP Tru64 /opt/ibm/dscli iSeries /ibm/dscli
51
Novell Netware SYS:\dscli When you log into the DS CLI application (type dscli at the command prompt), you must provide the following information: HMC1 Specify the primary management console. User Name Specify the name of the user account. The default account for the first login is admin. Password Specify the user password. The default password for the admin account is admin. However, this password is only good for your first login. Note: Because the password for the admin account expires after you log in for the first time, you must change the password before you can perform any other DS CLI command function. Use the chuser command to change your password. The first time that you log in to the DS CLI, you can specify this information using either of the following two methods: v Ensure you are in the directory where you installed the DS CLI application and type the dscli command at the command prompt. Supply all the log in information with the command. For example: dscli -hmc1 mtc032h.storage.tucson.ibm.com -user admin -passwd topn0t. Use this command when you use the single-shot mode for the first time and when the DS CLI application is not active on your system. In addition, when you use the single-shot mode, you must include the command that you want to process. For example, if you want to process the lssi command, if you have not activated the DS CLI application, and if you are using the single-shot mode, type: dscli -hmc1 mtc032h.storage.tucson.ibm.com -user admin -passwd topn0t lssi. v When you log into the DS CLI application (from the directory where you installed the DS CLI application) by typing dscli, you are prompted to supply the information for HMC1, user name, and password. Notes: 1. Entering a DS CLI command at the dscli command prompt requires that you continue entering all the parameters and values until the command is complete. This can result in an automatic line wrap if your command has many parameters and values. 2. You cannot force a line break or wrap by hitting the Enter key and then entering the rest of the command on a second line. The DS CLI application interprets the use of the Enter key as an end to the function and begins to process whatever is contained on the line, ignoring the second line. 3. The DS CLI command examples that are provided in this guide are often shown with line wraps that would not occur during your input. These examples are displayed for clarity and other formatting considerations.
52
Using the DS CLI single-shot command mode

Use the DS CLI single-shot command mode if you want to issue an occasional command but do not want to keep a history of the commands that you have issued. You must supply the login information and issue the command that you want to process at the same time. Perform the following steps to use the single-shot mode: 1. Use the following command format to enter a DS CLI session (Windows operating system):
dscli -hmc1 mtc032h.storage.tucson.ibm.com -user admin -passwd topn0t lssi -s -fullid -hdr off
Here is an example of this same command in i5/OS without the report delimiters:
DSCLI SCRIPT(*NONE) HMC1(9.5.17.156) USER(admin) PASSWORD(itso4all) DSCL(lssi)
This command demonstrates the use of the lssi command with the -s parameter. Use this command to view the storage image IDs for your storage complex. The storage image ID consists of the manufacture name (IBM), the machine type (1750), and the serial number. Notes: a. The command example uses the -fullid DS CLI command flag. The -fullid command flag generates fully qualified IDs, which include the storage image ID, for every ID that is displayed in the command output. b. The command example also uses the -hdr off command flag which turns off the header that is generally associated with the report that is generated from the lssi command. c. Almost every DS CLI command requires the use of the storage image ID. If you add your target storage ID into your profile file under the -devid designation, you are not required to provide the storage image ID when you issue a command. However, if you do provide the -dev (storage_image_ID) parameter, the value that you type takes priority over the value contained in your profile file. 2. Wait for the command to process. The following type of report is generated that lists the storage image IDs that are associated with the storage complex.
IBM.1750-68FA111 IBM.1750-68FA111 IBM.1750-68FA120
Using the DS CLI script command mode

Use the DS CLI script command mode if you want to issue a sequence of DS CLI commands. Administrators can use this mode to create automated processes; for example, establishing remote mirror and copy relationships for volume pairs. Consider the following when using the DS CLI script command mode: v The DS CLI script can contain only DS CLI commands. Use of shell commands results in a process failure. v You can add comments to the scripts. Comments must be prefixed by the number sign (#); for example, # This script contains PPRC Path establish procedures.
53
Note: It is not the intent of this instruction to tell you how to write a script. An example script is displayed for your use as a guide. You can issue the DS CLI script from the command prompt at the same time that you provide your login information. 1. Enter the script name at the command prompt using the following format:
dscli> -hmc1 mtc032h.storage.tucson.ibm.com -user admin -passwd password -script ~/bin/mkpprcpairs
Note: If you are using i5/OS and have already logged on to the DS CLI application, you invoke the script mode using the following format:
DSCLI SCRIPT(/myscript) USER(admin) OUTPUT(/outfile)
2. Wait for the script to process and provide a report regarding the success or failure of the process. The following is an example of a script that could be used to establish remote mirror and copy relationships for volume pairs.
mkpprc mkpprc mkpprc mkpprc mkpprc mkpprc mkpprc -dev -dev -dev -dev -dev -dev -dev IBM.1750-1303561 IBM.1750-1303561 IBM.1750-1303561 IBM.1750-1303561 IBM.1750-1303561 IBM.1750-1303561 IBM.1750-1303561 -remotedev -remotedev -remotedev -remotedev -remotedev -remotedev -remotedev IBM.1750-7504491 IBM.1750-7504491 IBM.1750-7504491 IBM.1750-7504491 IBM.1750-7504491 IBM.1750-7504491 IBM.1750-7504491 -type -type -type -type -type -type -type mmir 1000-103F:2300-233F gcp 1100-113F:2340-237F mmir 1800-187F:2800-287F gcp 1200-127F:2500-257F mmir 1040-1054:2700-2714 gcp 1055-107F:2400-242A mmir 1140-117F:2600-263F
Using the DS CLI interactive command mode

Use the DS CLI interactive command mode when you have multiple transactions to process that cannot be incorporated into a script. The interactive command mode provides a history function that makes repeating or checking prior command usage easy to do. In addition to being able to enter DS CLI commands at the DS CLI command prompt, a history function provides a view of the last DS CLI commands that you have used. It also allows you to repeat any of the last commands more quickly than having to type out the entire command. The example at the end of this process shows how the history function works. Perform the following steps to use the DS CLI in the interactive command mode: 1. Log on to the DS CLI application at the directory where it is installed. Note: If you make a mistake and type the wrong user name or password, do not try to correct the error within the current session. Exit the DS CLI session that you are in and log in to a new DS CLI session. 2. Provide the information that is requested by the information prompts. The information prompts might not appear if you have provided this information in your profile file. The command prompt switches to a dscli command prompt. 3. Begin using the DS CLI commands and parameters. You are not required to begin each command with dscli because this prefix is provided by the dscli command prompt. Note: Issue the setoutput command if you know that you will be using interactive mode for a lengthy period of time. The setoutput command allows you to set or display command output format options. You
54
control how the reports that are generated by the list and the show commands are displayed on your computer. For example, you can specify that the reports be displayed in one of the following formats: v delim = displays output in a table format and sets the column delimiter to a single character v xml = displays output in XML format v stanza = displays output in stanza (horizontal table) format See the setoutput command for more details. To use the DS CLI history function that is associated with the interactive command mode, perform the following steps: 1. Issue an exclamation mark (!) to display CLI commands that you have used in the current session. For example: dscli>! results in a list of commands such as the following:
[4] [3] [2] [1] lsarraysite -dev IBM.1750-1300771 lsarray -dev IBM.1750-1300771 lsextpool -dev IBM.1750-1300771 lsextpool -dev IBM.1750-1300771
2. Issue dscli>!1 to retry the last command. Or, issue dscli>!3 to retry command [3].
Obtaining the serial (storage image ID) number using the DS CLI
Almost every DS CLI command requires the use of the storage image ID. If you add your target storage image ID into your profile file under the -devid designation, you are not required to provide the storage image ID when you issue each command. Use the lssi or lssu DS CLI commands to list the storage image IDs that are associated with your storage complex. It is recommended that you record the target storage image ID in your profile file. This can save you input time when you have to process many transactions that cannot be part of a script. To obtain a list of the storage image ID numbers, perform the following steps. The storage image ID consists of the manufacture name (IBM), the machine type (1750), and the serial number. 1. Log into the DS CLI application in interactive command mode (if you are not already logged in). 2. Type the following command format at the dscli command prompt to obtain the storage image IDs. Substitute lssi or lssu for the command name variable in the example.
dscli>commandname -s -fullid -hdr off
Note: The result of using the parameters and command flags as shown in the example is the same for either command. However, each command can produce different information when you use their associated parameters. See the lssi or lssu commands for more details. 3. Wait for the command to process. The following type of report is generated, which lists the storage image IDs that are associated with the storage complex.
IBM.1750-75FA111 IBM.1750-75FA111 IBM.1750-75FA120
55
DS CLI command help

You can obtain online help for each CLI command. To obtain the help, type the word help and the command name at the dscli command prompt. There are additional parameters that you can use with the help command that designate the type of help information that you can receive. The help command contains the following parameters that influence the type of help information that you can receive:
Command help help -s help -l command_name -h command_name -help command_name -? help command_name help -s command_name help -l command_name Description Displays a list of all the DS CLI commands that are available for use. Displays a list of commands with brief descriptions. Displays a list of commands with their associated syntax. Displays the reference page (man page) for the command name.
Displays the brief description for the command name. Displays the usage statement for the command name.
Note: You cannot use the -s and -l parameters with the following help command flags: -h, -help, and -?.
Examples
The following examples represent the type of information that is displayed when you use various parameters with the help command. Each of these examples start at the dscli command prompt. Note: Much of the information that is associated with the help command is displayed in list format. You can include the page (-p on) and row (-r number) controls; for example, dscli>help -p on -r20. This command pauses your page listing after 20 entries and prompts you to press any key to continue. Example 1
dscli>help
This line of input provides the entire list of DS CLI commands. Only the command names are displayed. No other details are provided. Example 2
dscli>help -s
This line of input provides the entire list of DS CLI commands and a short description for each command. The short description explains what each command accomplishes.
56
Example 3
dscli>help -l
This line of input provides the entire list of DS CLI commands and the syntax for each command. In addition, you see all the help syntax and formatting parameters, which can make your reading of the help difficult. For example, you can see something similar to the following for each command:
lsextpool [ { -help|-h|-? } ] [ { -l (long)|-s (short) } ] [-fmt default|xml|delim|stanza] [-p on|off] [-delim char] [-hdr on|off] [-bnr on|off ] [-r #] [-v on|off] [-fullid] [-hmc1 SMC1] [-hmc2 SMC2] [-user username] [-passwd password] -dev storage_image_ID [-stgtype fb|ckd] [-rankgrp 0|1] [Extent_Pool_ID ... | -]
The following line is the actual syntax for the lsextpool command: -dev storage_image_ID [-stgtype fb|ckd] [-rankgrp 0|1] [Extent_Pool_ID ... | -] Example 4
dscli>lssi dscli>lssi dscli>lssi dscli>help -h -help -? lssi
Any of the previous lines of input generates the entire help page that is associated with the lssi command. This is the same information that is found in the IBM System Storage DS6000 Command-Line Interface Users Guide or in the Information Center for the lssi command. Example 5
dscli>help -s lssi
This line of input provides the short description that is associated with the designated command. For instance, you might see the following:
lssi The lssi command displays a list of storage images in a storage complex. You can use this command to look at the status of each storage image in the list. The storage image worldwide node name (WWNN) is displayed when this command is used. You must use the storage image WWNN when using the lsavailpprcport and mkpprcpath commands.
Example 6
dscli>help -l lssi
This line of input displays the entire reference page found in both the IBM System Storage DS6000 Command-Line Interface Users Guide and in the Information Center for the lssi command.
Obtaining and interpreting DS CLI exit codes

Complete this task to obtain and interpret DS CLI exit codes. Whenever you complete a transaction using the DS CLI single-shot mode or the script mode, an exit code is generated. However, no exit codes are generated when you use the DS CLI interactive mode, because you never leave the DS CLI session.
57
When you use the single-shot mode, an exit code is generated after each DS CLI command is fully processed. When you use the script mode, exit codes are only generated when the script exits the session. In script mode, you must interpret output for the status. DS CLI exit codes provide more general reasons (than the error messages provide) why a CLI command transaction has failed. The following table lists the exit codes and their meanings. Note: Only the code number is displayed when you are using the single-shot or script mode not the code description.
Code 0 2 Category Success Syntax Error Description Specifies that the command is successfully processed Specifies that there is an error in the way that the command is presented (misaligned or wrong parameters) for processing Specifies that there is a connectivity or protocol error Specifies that an error occurs during a function call to the application server Specifies that an error occurs during the authentication process Specifies that an error occurs due to a MetaProvider client application specific process
3 4
Connection Error Server Error
Authentication Error
Application Error
Perform the following steps to obtain, interpret and use the DS CLI exit codes. 1. (Script mode) Retrieve the most recent exit code. For a Windows operating system, use %ERRORLEVEL% to retrieve the most recent exit code. For a UNIX or Linux operating system, use $? to retrieve the most recent exit code. The following examples demonstrate the retrieval commands. The first part of the example shows the command that failed and the second part of the example shows the code to obtain the DS CLI exit code. Windows operating system
C:\Program Files\ess\cli>dscli test CMMCI9013E Command: test was not found. Tip: Enter help for a list of available commands. C:\Program Files\ess\cli>echo %ERRORLEVEL% 2
UNIX or Linux operating system

aix23 ->dscli test CMMCI9013E Command: test was not found. Tip: Enter help for a list of available commands. echo $? 2
2. Use the previous table to interpret the value that is associated with the code and correct the command according to the exit code description.
58
Processing that determines your next course of action Based on the interpretation of the exit code value and the following processing description that is associated with a failed DS CLI transaction, you can determine your next course of action. Single-shot mode The following processing is associated with a single-shot mode transaction: v All operations of the DS CLI transaction that can be processed are processed even though an error has occurred with one or more of the processed parameters that are associated with the transaction. v A report on all successful completions is generated. v A report on all failures is generated. Script mode The following processing is associated with a script mode transaction: 1. A DS CLI failure exit code is issued. 2. The script mode is automatically exited with no additional processing.
Activating your machine and feature licenses using the DS CLI

Use the steps described in this task to activate your license activation codes. These codes must be activated before any configuration can be applied to your DS6000 network. The following licenses can be activated depending on your purchase: v Operating environment license for each storage unit that you own. (This license must be activated.) v Copy Services, which can consist of the following features: FlashCopy Remote mirror and copy There are multiple codes that are associated with these features. To obtain the information that you need to activate these licenses and features in your storage unit, go to the IBM Disk Storage Feature Activation (DSFA) Web site at: http://www.ibm.com/storage/dsfa/ Download your codes onto a diskette in XML format. You can then import the codes from the XML file when you process the DS CLI applykey command. Note: In most situations, the DSFA application can locate your order confirmation code (OCC) when you enter the DS6000 (1750) serial number and signature. However, if the OCC is not attached to the 1750 record, you must assign it to the 1750 record in the DSFA application. In this situation, you must have the OCC (which you can find on the License Function Authorization document). The applykey DS CLI command activates the licenses for your storage unit. The lskey DS CLI command verifies which type of licensed features are activated for your storage unit. Perform the following steps to activate your license activation codes.
59
1. Log into the DS CLI application in interactive command mode (if you are not already logged in). 2. Issue the DS CLI applykey command at the dscli command prompt as follows (this example presumes that your XML file is named keys and it resides on a diskette in your A: drive): dscli> applykey -file a:\keys.xml IBM.1750-68FA120 3. Press Enter. When the process has completed, the following message is displayed:
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 Licensed Machine Code key xxxx, key xxxx successfully applied.
4. Verify that the keys have been activated for your storage unit by issuing the DS CLI lskey command as follows: lskey IBM.1750-68FA120 5. Press Enter and the following type of report is displayed:
Sun Apr 09 02:23:49 PST 2006 IBM DS CLI Activation Key Operating Environment (OEL) Remote mirror and copy (RMC) Remote mirror for z/OS (RMZ) Point in time copy (PTC) Parallel access volumes (PAV) Authorization Level (TB) 45 25.1 25.1 On On Scope All All CKD All CKD
Setting up user accounts using the DS CLI

This scenario describes how to set up a user account. You must have administrator authority to enable this function. The admin account is set up automatically at the time of installation. It is accessed using the user name admin and the default password admin. This password is temporary and expires after its initial use. You must change the password before you can use any of the other functions. There are 7 groups the administrator can assign to a user. A user can be assigned to more than one user group. The groups and the associated functions allowed by the assignment are as follows: admin All users that you assign to the administrator user group allows access to all storage management console server service methods and all storage image resources. op_volume The volume operator user group allows access to service methods and resources that relate to logical volumes, hosts, host ports, logical subsystems, logical volumes, and volume groups, excluding security methods. In addition, this user group inherits all authority of the monitor user group. op_storage The storage operator user group allows access to physical configuration service methods and resources, including storage complex, storage image, array, rank, and extent pool objects. This user group inherits all the authority of the op_copy_services and monitor user groups, excluding security methods.
60
op_copy_services The copy services operator user group allows access to all Copy Services service methods and resources, excluding security methods. In addition, this user group inherits all authority of the monitor user group. service The service user group includes monitor authority, plus access to all management console server service methods and resources, such as performing code loads and retrieving problem logs. monitor The monitor user group allows access to list and show commands. It provides access to all read-only, nonsecurity management console server service methods and resources. no access The no access user group does not allow access to any service methods or storage image resources. By default, this user group is assigned to any user account in the security repository that is not associated with any other user group. In addition to assigning users to one or more user groups, you also must assign a default password to each user. When you notify users of their group assignment and default password, indicate that the default password is only good for the initial log on. Users must change the password at the time of their initial log on. Also, remind all users to record their password in a safe place, because there is no way that the administrator or the application can retrieve a password. Note: You must change the default password for an account, including the admin account, to be able to use any CLI command other than the one to change the password. See the chuser command for more information. Use the mkuser DS CLI command to create new user accounts with specific roles (user group or groups) and an initial password. If you assign multiple roles to an account, ensure that you separate the different roles by using a comma for example, op_volume, op_storage. See the mkuser command description for more details. 1. Log into the DS CLI application in interactive command mode. 2. Issue the following command from the dscli command prompt to assign a user to an account with a default password: dscli>mkuser -pw AB9cdefg -group service,op_copy_services testuser 3. Press Enter and observe the processing result. A successful process returns the following display:
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 User Name testuser successfully created.
Creating a default configuration setup with a profile file

You can create default settings for the command-line interface by defining one or more profiles on the system. For example, you can specify the storage management console (SMC) for the session, the output format for list commands, the number of rows per page in the command-line output, and the banner that is included with the command-line output. If a user enters a value with a command that is different from a value in the profile, the command overrides the profile.
61
You have several options for using profile files: v You can modify the default profile. The default profile, dscli.profile, is installed in the profile directory with the software. For example, c:\Program Files\IBM\DSCLI\profile\dscli.profile is the directory path for the Windows platform and /opt/ibm/dscli/profile/dscli.profile is the directory path for UNIX and Linux platforms. v You can create a personal default profile by making a copy of the system default profile as <user_home>/dscli/profile/dscli.profile. v You can create a profile for the storage unit operations. Save the profile in the user profile directory. For example: <user_home>\dscl\profile\operation_name1 <user_home>\dscl\profile\operation_name2 These profile files can be specified using the DS CLI command parameter -cfg <profile_name>. If the -cfg profile file is not specified, the users default profile file is used. If a users profile file does not exist, the system default profile file is used. The home directory <user_home> is defined by the Java system property named user.home The location of your password file is determined by your operating system. The following examples are home directories in different operating systems: Windows operating system For a Windows operating system, the property value defaults to the environment variable %USERPROFILE%. As a result, your personal profile is C:\Documents and Settings\username\dscli\profiles\dscli.profile. UNIX or Linux operating system For an UNIX or Linux operating system, the property value defaults to the environment variable $HOME. As a result, your personal profile is ~/dscli/profile/dscli.profile. OpenVMS system For an OpenVMS operating system, the property value defaults to the logical name SYS$LOGIN. As a result, your personal profile is [.dscli.profile]dscli.profile. Note: The values of the Java system properties can be redefined by JRE options. If you are having problems, check to see if you have an environment setting like the following on your local system:
_JAVA_OPTIONS=-Duser.home=...
When you install the command-line interface software, the default profile is installed in the profile directory with the software. The file name is dscli.profile. For example. c:\Program Files\IBM\DSCLI\profile\dscli.profile. | | | | | | | | | Example profile file modification: The following steps represent a typical modification process for some of the key items. Making these changes before you begin using DS CLI commands could save you time. 1. Click the DSCLI icon on your desktop (a DOS window opens) 2. Enter edit dscli.profile at the command prompt. The profile configuration file is displayed. 3. Scroll down to the # sign in front of HMC1: and remove the # sign. 4. Enter the correct IP address of your management console. 5. Scroll down to the # sign in front of DEVID and remove the # sign.
62
| | | | | | |
6. Enter the serial number of your machine type (include the values for manufacture, machine type, and serial number). 7. Save the file. 8. Enter cd.. at your command prompt. 9. Enter DSCLI at your command prompt and the DS CLI applications starts. You are asked to provide only your user ID and password and not the address of your management consoles. Table 3 provides the list of profile variables that you can use to create the profile.
Table 3. Profile variables Variable banner: on|off Description Enables or disables the banner that appears before the command output. This variable is equivalent to the command option -bnr. The command option -bnr overrides this default value. Specifies a delimiter character for the format: delim variable. The default character is a comma. This variable is equivalent to the command option -delim. The command option -delim overrides this default value. Specifies the storage image ID that is the target for the command. This value is equivalent to the command option -dev. The command option -dev overrides this default value. Specifies the output format for list commands. Specify one of the following formats: v default: Specifies default output. v xml: Specifies XML format. v delim: Specifies columnar format. Columns are delimited with the character that you must specify with the delim variable. v stanza: Specifies a horizontal table. This variable is equivalent to command option -fmt. The command option -fmt overrides this default value. fullid header: on|off Specifies that IDs display in fully qualified format, which includes the storage image ID. Enables or disables the headers that display with the columns of data in the list commands. This variable is equivalent to the command option -hdr. The command option -hdr overrides this default value. Specifies the primary Storage Manager IP address. This variable is equivalent to the command option -hmc1. The command option -hmc1 overrides this default value. Specifies the secondary Storage Manager IP address. This variable is equivalent to the command option -hmc2. The command option -hmc2 overrides this default value.
delim
devid
format
hmc1
hmc2
63
Table 3. Profile variables (continued) Variable locale Description Specifies the language for the output on the local computer. v ar: Arabic v be: Byelorussian v bg: Bulgarian v ca: Catalan v cs: Czech v da: Danish v de: German v el: Greek v en: English v es: Spanish v et: Estonian v fi: Finnish v fr: French v gu: Gujarati v hi: Hindi v hr: Croatian v hu: Hungarian v in: Indonesian v is: Icelandic v it: Italian v iw: Hebrew v ja: Japanese v kk: Kazakh v kn: Kannada v ko: Korean v lt: Lithuanian v lv: Latvian (Lettish) v mk: Macedonian v mr: Marathi v ms: Malay
64
Table 3. Profile variables (continued) Variable locale, continued Description v nl: Dutch v no: Norwegian v pa: Punjabi v pl: Polish v pt: Portuguese v ro: Romanian v ru: Russian v sa: Sanskrit v sh: Serbo-Croatian v sk: Slovak v sl: Slovenian v sq: Albanian v sr: Serbian v sv: Swedish v ta: Tamil v te: Telugu v th: Thai v tr: Turkish v uk: Ukrainian v vi: Vietnamese v zh: Chinese paging: on|off Controls the display of output. If paging is enabled, a limited number of lines of output displays when a command is issued. The lines do not scroll. You must set the number of lines per page with the rows variable. This variable is equivalent to command option -p. The command option -p overrides this default value. Set timeout value of client/server synchronous communication. The unit of the value is second. The default value is 420 seconds. You can set this timeout if the processing of a command ends by timeout due to network or client/server performance issue. Note: The command timeout value can be longer than this value because one command can consist of multiple client/server requests. Set timeout value to establish client or server connection. The unit of this value is seconds. The timeout value must be greater than zero. System default socket timeout value is used if the value is set to zero. The default value is 20 seconds. Notes: 1. If the DS CLI returns a connection error, check for the following conditions: v Is there a secure physical connection between the client and server? v Is the default timeout value too short to establish a connection? 2. Setting a connection timeout value too short can cause unexpected connection problems.
timeout
timeout.connection
65
Table 3. Profile variables (continued) Variable remotedevid Description Specifies the remote storage image ID. This variable is equivalent to the command option -remotedev. The command option -remotedev overrides this default value. Specifies the number of rows per page of output if the paging variable is enabled. This variable is equivalent to command option -r. The command option -r overrides this default value. Enables or disables verbose output. This variable is equivalent to the command option -v. The command option -v overrides this default value.
rows
verbose: on|off
Example
# # DS CLI Profile # # # Management Console/Node IP Address(es) # hmc1 and hmc2 are equivalent to -hmc1 and -hmc2 command options. #hmc1: 127.0.0.1 #hmc2: 127.0.0.1 # # Default target Storage Image ID # "devid" and "remotedevid" are equivalent to # "-dev storage_image_ID" and "-remotedev storeage_image_ID" command options, # respectively. #devid: IBM.1750-AZ12341 #remotedevid: IBM.1750-AZ12341 # # locale # Default locale is based on user environment. #locale: en # Timeout value of client/server synchronous communication in second. # DSCLI command timeout value may be longer than client/server communication # timeout value since multiple requests may be made by one DSCLI command # The number of the requests made to server depends on DSCLI commands. # The default timeout value is 420 seconds. #timeout: 900 # Socket connection timeout value in seconds. # The timeout value must be greater than zero. # System default socket timeout value is used if timeout value is set to zero. # The default connection timeout value is 20 seconds. #timeout.connection: 20 # Output settings # # ID format of objects: # on: fully qualified format # off: short format fullid: off # # # # # # Paging and Rows per page. paging enables/disables paging the output per line numbers specified by "rows". "paging" is equivalent to "-p on|off" option. on : Stop scrolling per output lines defined by "rows". off : No paging. (default) "rows" is equivalent to "-r #" option.
66
paging: off #rows: 24 # Output format type for ls commands, which can take one of the following values: # default: Default output # xml : XML format # delim : delimit columns using a character specified by "delim" # stanza : Horizontal table format # "format" is equivalent to option "-fmt default|xml|delim|stanza". #format: default # delimitter character for ls commands. #delim: | # Display banner message. "banner" is equivalent to option "-bnr on|off". # on : Banner messages are displayed. (default) # off : No Banner messages are displayed. banner: on # # Display table header for ls commands. "header" is equivalent # to option "-hdr on|off". # on : Table headers are displayed. (default) # off : No table headers are displayed. header: on # # Display verbose information. "verbose" is equivalent to option "-v on|off". # on : Display verbose information. # off : No verbose information. verbose: off # End of Profile
Configure support options using the DS CLI

This scenario provides a high-level description of the tasks that you must perform to configure support options using the command-line interface. Support options (for example, e-mail alerts and alert traps that are sent by an SNMP agent) enable IBM support personnel to quickly assist you with problem determination and, with your consent, remotely perform certain maintenance procedures. Note: The Call Home function also has a modem call home feature. The DS CLI cannot be used to configure this feature. You must use the DS Storage Manager to configure the modem call home feature. Before you begin, you must have the command-line interface prompt, and you must be connected to a storage unit that is used for open systems host system storage. This scenario first creates the contact information and then establishes the SMTP port and IP address where a message is sent in the event of a problem. After these two tasks are completed, you can activate the Call Home function and verify that the Call Home function works according to your specifications. You can also set up your storage unit to receive alert traps. 1. Set up the contact information. The contact information that you supply is sent to IBM so that an IBM service representative can contact you. The type of information that you must supply consists of the following but is not limited to this list: v Company name v Company address
67
Country State or province Primary contact phone number Primary e-mail address (required if you are using the Call Home e-mail notification feature). See Setting up contact information using the DS CLI for details. 2. Set up the e-mail notification process. Using e-mail, the Call Home function can notify IBM when a problem occurs on your storage unit. You must specify the SMTP port and IP address where the message is sent in the event of a problem. See Setting up Call Home (SMTP) notifications using the DS CLI on page 69 for details. 3. Activate and verify the Call Home function. v v v v After you provide your contact information and specify the SMTP port and IP address where the message is sent in the event of a problem, you can activate and test Call Home. See Activating the Call Home function using the DS CLI on page 72 for details. 4. Set up the SNMP alert notifications process. One of the support options you can configure for your storage unit involves the notification of Simple Network Management Protocol (SNMP) alert traps. SNMP notifications are alerts and notifications of thresholds that have been exceeded and exception events that have occurred. See Setting up SNMP notifications using the DS CLI on page 73 for details. 5. Set up the Service information messages (SIM) notification process. SIMs are generated by a storage unit for S/390 and zSeries hosts. You can designate the level of erro you want to be notified about and how often you want to be notified. See Setting up SIM notifications using the DS CLI on page 73 for details.
Setting up contact information using the DS CLI

Complete this task to establish your contact information in your system. When you use any of the remote support features, the contact information you supply is sent to IBM so that an IBM service representative can contact you. You must supply the following information when you are setting up for remote support: v Company name v Ship state or province v Ship location v Ship country v Contact primary phone number v Machine identification (consists of the manufacture, machine type, and serial number) v Primary e-mail address (required if you are using the Call Home e-mail notification feature). It is also recommended that you supply the following additional types of information when setting up for remote support: v Company address
68
v Machine location (the physical location of the machine) v Machine address (where the machine is physically located) v Ship phone (the telephone number of the person to contact when parts are being shipped) v Ship to city v Ship postal code v Contact name (the name of the system administrator who can be contacted by IBM service personnel) v Contact alternate phone number Use the setcontactinfo command to provide the contact information that is needed for the remote support function. Perform the following steps to establish your contact information in the system. The example commands that are displayed in this task are shown in two formats. The first format provides the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the setcontactinfo command to supply the contact information. Enter the setcontactinfo command at the dscli command prompt with the following parameters and variables:
dscli>setcontactinfo companyname company_name -shipstate [state, province] -shiploc building_location -shipcountry country contactpriphone primary_phone_number -contactemail primary_email_address storage_image_ID
Example
dscli>setcontactinfo companyname Examples -shipstate AZ -shiploc bld1300 -shipcountry US contactpriphone 520-799-8001 -contactemail example@example.com IBM.1750-68FA120
Notes: a. The phone number is displayed with hyphens that separate the various parts. b. If you decide to use the company address, ensure that you use double quotation marks around your input. For example: -companyaddr 9210 S. High Rd Tucson Az 85744 2. Press Enter. The following message is displayed if the process is successful:
Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The contact information settings were successfully modified
3. Issue the showcontactinfo command to verify that the contact information is active in your system. Enter the showcontactinfo command at the dscli prompt with the following parameter:
dscli>showcontactinfo storage_image_ID
Example
dscli>showcontactinfo IBM.1750-68FA120
A report is displayed showing the contact information that is established and recognized by your system.
Setting up Call Home (SMTP) notifications using the DS CLI

Complete this task to set up the Call Home function to contact IBM support using e-mail when a problem occurs on your storage unit. The setsmtp command is used to set up the e-mail feature of the Call Home function.
69
Note: The Call Home function also has a modem call home feature. The DS CLI cannot be used to configure this feature. You must use the DS Storage Manager to configure the modem call home feature. Consider the following requirements before you use the setsmtp command to set up e-mail notifications: v You must know your SMTP port and IP address, because these are required to activate the e-mail notifications. This information specifies where a message is sent in the event of a problem. v Your system must recognize all the required contact information before you can issue the setsmtp command. This includes the following information: Company name Ship state Ship location Ship country Primary contact phone number Primary e-mail address (required if you are using the call home e-mail notification feature). Perform the following steps to activate the e-mail notification support option feature. The example commands that are displayed in this task are shown in two formats. The first format provides the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the showplex command to obtain a report that provides your SMTP port and IP address. Enter the showplex command at the dscli command prompt with the following parameter:
dscli>showplex storage_image_ID
Example
dscli>showplex IBM.1750-68FA120
2. View the report and make a copy of it. The important thing is that you have a record of the SMTP and SNMP IP addresses and port numbers that are used in setting up the Call Home function. 3. Issue the showcontactinfo command. This command displays a report that allows you to ensure that the required contact information, including the primary e-mal address, has been set in the system. Enter the showcontactinfo command at the dscli command prompt with the following parameter:
dscli>showcontactinfo storage_image_ID
Example
4. Review the report and ensure that all the required contact information has been set in the system, including the primary e-mail address. If any of the required information is missing, issue the setcontactinfo command before you proceed with this task. 5. Issue the setsmtp command to specify where a message is sent in the event of a problem. Enter the setsmtp command at the dscli command prompt with the following parameters and variables:
dscli>setsmtp -server smtp_server_IP:port_number -emailnotify [on, off] storage_image_ID
Example
70
dscli>setsmtp server 9.11.242.12:25 -emailnotify on IBM.1750-68FA120
6. Press Enter. The following message is displayed if the process is successful:

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SMTP settings were successfully modified
Setting up your account information using the DS CLI

Complete this task to set up your account information which is needed when using the Call Home function. You must use the setplex command to associate a unique name with the 1750, which in turn allows you to open a secure shell connection to a storage unit for remote support. Before you can activate and test the Call Home function, ensure that the following tasks have been completed: v You have supplied the following required contact information using the setcontactinfo command: Company name Ship state Ship location Ship country Primary contact phone number Primary e-mail address (required if you are using the call home e-mail notification feature). v You have supplied the location where e-mail notifications are sent by specifying the SMTP port and IP address through the setsmtp command. To set up your account information, provide the following information: v Account number v The secure shell connection enabled v Storage image ID (manufacture, machine type, and serial number) unless you have stored this information in your profile file Note: The example in the following steps presumes that the storage image ID information has not been stored in the profile file. Perform the following steps to set up your account information. The example commands that are displayed in this task are shown in two formats. The first format provides the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the setplex command to establish your account information in the system. Enter the setplex command at the dscli command prompt with the following parameters and variables:
dscli>setplex -acct account -allowrssh enable storage_image_ID
Example
dscli>setplex -acct 101010 -allowrssh enable IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Storage Plex successfully modified
71
3. Issue the showplex command to verify that your system recognizes the account information. Enter the showplex command at the dscli command prompt with the following parameter:
dscli>showplex storage_image_ID
Example
A report is displayed that details the properties of your 1750 storage complex. Detailed properties include names, descriptions, and notification settings for the storage complex.
Activating the Call Home function using the DS CLI

Complete this task to activate the Call Home function using the DS CLI. The Call Home function allows the transmission of operational and error-related data to IBM. It is the capability that allows the storage unit to alert IBM support of machine conditions. Note: The Call Home function also has a modem call home feature. The DS CLI cannot be used to configure this feature. You must use the DS Storage Manager to configure the modem call home feature. Before you can activate and test the Call Home function, ensure that the following tasks have been completed: v You have supplied your required contact information using the setcontactinfo command. This consists of the following information: Company name Ship state Ship location Ship country Primary contact phone number Primary e-mail address (required if you are using the call home e-mail notification feature). v You have supplied the location where e-mail notifications are sent by specifying the SMTP port and IP address through the setsmtp command. v You have set up your account information using the setplex command. Use the setdialhome command to enable the Call Home function. You can designate the machine and enable the function on the machine with this command. Use the testcallhome command to verify that the Call Home function is active. Perform the following steps to activate and test the Call Home function for your storage unit. The example commands that are displayed in this task are shown in two formats. The first format provides the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the setdialhome command to activate the Call Home function. Enter the setdialhome command at the dscli command prompt with the following parameters and variables:
dscli>setdialhome -action enabled storage_image_ID
Example
dscli>setdialhome -action enabled IBM.1750-68FA120
72
Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The dial home settings were successfully modified
3. Issue the testcallhome command to verify that the Call Home function is active. Enter the testcallhome command at the dscli command prompt with the following parameter:
dscli>testcallhome storage_image_ID
Example
dscli>testcallhome IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 A test problem record was successfully created.
Setting up SNMP notifications using the DS CLI

One of the support options you can configure for your storage unit involves the notification of Simple Network Management Protocol (SNMP) alert traps. SNMP notifications are alerts and notifications of thresholds that have been exceeded and exception events that have occurred. This task shows you how to set up your storage unit to receive these notifications as they occur. You need to know your SNMP port and IP address as these are required when activating the notifications feature. This information specifies where a message is sent in the event of a problem. To use the setsnmp command to activate the SNMP alert notification support option feature, perform the following steps: 1. Log in to the DS CLI application in interactive command mode, if you are not already logged in. 2. Specify where a message is sent in the event of a problem by issuing the setsnmp command at the dscli command prompt as follows:
dscli>setsnmp server 9.11.242.12:161 IBM.1750-68FA120
3. Press Enter and a successful process displays the following message:

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SNMP settings were successfully modified
Setting up SIM notifications using the DS CLI

Service information messages (SIMs) are generated by a storage unit for S/390 and zSeries hosts. You can designate the level of error you want to be notified about and how often you want to be notified. It is recommended that you determine your levels of notification before using the setsim command. You need to decide what type of message should generate a message. You have the following choices including a level of severity, severity designations are the same for each type of message. You can also designate how often you want to be notified. SIM message types consist of the following: v DASD service information messages v Media service information messages v Storage unit messages
73
SIM severity designations consist of the following choices: v acute - An irrecoverable error with possible loss of data. v moderate - A system path is not operational and performance might be degraded. v serious - An irrecoverable error or a data check with loss of access to data. v service - A recoverable error, equipment checks, or data checks. You can defer repair. v none SIM notifications for each message type can be in the range of 0-5 time. To set up your SIM notification choices using the setsim command, perform the following steps: 1. Log in to the DS CLI application in interactive command mode, if you are not already logged in. 2. Specify your notification choices using the following example format for the setsim command. At the dscli command prompt type the following:
dscli>setsim -dasdlevel serious -dasdnotify 3 -medialevel moderate -medianotify 2 -sulevel service -sunotify 1 IBM.1750-68FA120
3. Press Enter and a successful process displays the following message:

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SIM settings were successfully modified
Registering for the My Support function

Complete this task to register for the My Support function. The My Support function provides proactive notification of code updates though an e-mail address that you specify. My Support automatically notifies you of the latest code updates and how to obtain them. It is highly recommended that you register for My Support. To access online technical support, go to the following Web site: http://www-1.ibm.com/servers/storage/support/disk/ds6800/ My Support registration provides e-mail notification when new firmware levels have been updated and are available for download and installation. To register for My Support, perform the following steps: 1. Go to the following Web site: http://www.ibm.com/support/mySupport and click register now. 2. On the My IBM registration Step 1 of 2 page, fill in the required information. Items with an asterisk (*) are required fields. Click Continue. 3. On the My IBM registration Step 2 of 2 page, fill in the required information. Items with an asterisk (*) are required fields. Click Submit. Click Continue. 4. On the Sign in page, enter your IBM ID and password and click Submit. 5. On the My support page, click Edit profile. Select the information that is required for your profile in the Products section. a. From the Products list, select Storage. b. From the second list, select Computer Storage. c. From the third list, select Disk Storage Systems.
74
d. From the fourth list, select System Storage DS6000 series. e. Select the System Storage DS6800 check box. f. Click Add products. g. Review your profile for accuracy. 6. Click Subscribe to email. In the Documents list, select Storage. Then select the Please send these documents by weekly email check box, select the Downloads and drivers check box, and select the Flashes check box. Click Update. 7. In the Welcome area, click Sign out to end your session.
Removing the DS Command Line Interface

You can remove the DS CLI using the same modes that are allowed by the operating systems during the installation process. For example, you can use the graphical mode, unattended (silent) mode, or console mode to install this interface. Conversely, you can remove this interface using the graphical mode, unattended (silent) mode, or console mode. The following topics describe the steps required to successfully remove this interface.
Removing the DS CLI from your system using graphical mode

Use the graphical mode to remove the DS CLI from your system when the DS CLI is installed on a Windows, Novell, or UNIX system. Notes: 1. The following procedure applies to the removal of only the DS CLI application. This procedure cannot be used to remove other versions of the CLI. 2. If you do not want to create a new profile when you reinstall the CLI, select to not delete the DS CLI profile as you complete this task. You use the Add/Remove Programs facility of the Windows operating system to remove the DS CLI from your system. When you have processed the uninstall steps, restart your system to complete the uninstall. Perform the following steps to remove the DS CLI using the graphical mode. 1. Navigate to the Windows Control Panel and open the Add/Remove program facility. 2. Scroll the list of currently installed programs and click the listing for IBM System Storage DS Command-Line Interface. 3. Click the Change/Remove button and the Welcome window for the Uninstaller is displayed.
75
4. Click Next to continue or click Cancel to exit the removal process. When you click Next, the Confirmation window is displayed that shows the directory from which the DS CLI program is removed.
5. Click Remove to continue or Cancel to stop the removal and exit the uninstall process. Click Back to return to the previous window. When you click Remove, the Uninstallation Progress window is displayed. When the uninstall process is finished, the Finish window is displayed, which contains a statement about the success or failure of the uninstall process. Click Finish to close.
76
1xxbr5
1xxbos
If the uninstall program does not remove some information from your system, the Restart window is displayed. You must restart so that previously locked files are released and automatically deleted. 6. Close the Add/Remove Programs window. 7. Restart your system, if required (now or later), to complete the removal process.
Removing the DS CLI using unattended (silent) mode

Use the unattended (silent) mode to remove the DS CLI through the command line if the DS CLI is installed on a UNIX system or a variant of UNIX (for example, HPUX, Sun, or AIX). Perform the following steps to successfully uninstall the DS CLI. Notes: 1. If you are using Windows or Novell, you will use the Add/Remove Programs feature to uninstall the DS CLI. 2. This uninstall process only works with DS CLI. No other versions of CLI can be removed with this process. 1. Locate the uninstaller file in the /_uninst folder. If you selected the default directory, you can find the _uninst folder using the /opt/ibm/dscli path. The uninstaller file name is uninstaller.xxx, where xxx depends on the operating system. If you have a Hewlett Packard, Sun, or AIX system, then the file name is uninstaller.bin. For all other operating systems the file name is uninstaller.sh. 2. Type the following command at the command prompt: <install directory>/_uninst/uninstaller.<exe|sh|bin> -silent 3. Press the Enter key. All the associated CLI files are uninstalled.
Removing the DS CLI using the console mode

Use the console mode to remove the DS CLI when the DS CLI is installed on a UNIX system that does not the have use of an X display. Perform the following steps to remove the DS CLI using the console mode:
1xxbt1
77
Note: Do not use the console method to uninstall DS CLI on a Windows system. Instead, follow the steps in this guide for removing the DS CLI using graphical mode. 1. Type the following command at a command prompt: <install directory>/_uninst/uninstaller.<sh | bin> -console 2. The Welcome screen displays. Press 1 and Enter to continue, or 3 to Cancel the removal process.
Welcome to the InstallShield Wizard for IBM System Storage DS Command-Line Interface (CLI) The InstallShield Wizard uninstalls IBM System Storage DS Command-Line Interface on your computer. To continue, choose Next. DS Command-Line Interface IBM Corporation Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]
3. The Uninstallation Location screen is displayed. Press 1 and Enter to continue, or 3 and Cancel to exit the removal process.
IBM System Storage DS Command-Line Interface will be uninstalled from the following location: C:\Program Files\ibm\dscli Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
4. The Uninstallation progress screen is displayed while the command-line interface is being removed.
Uninstalling IBM System Storage DS Command-Line Interface...
5. The Uninstallation Finish screen is displayed. Press 3 to finish the removal.

The InstallShield Wizard has successfully uninstalled IBM System Storage DS Command-Line Interface. Choose Finish to exit the wizard. Press 3 to Finish or 4 to Redisplay [3]
Removing the DS CLI from a System i system

This section contains information to help you uninstall the DS CLI from a System i system. Because the DS CLI is installed on a System i system from a remote system, it is not possible to use the conventional DS CLI removal methods that you use with other systems. When the DS CLI was installed onto your System i system, you used a remote system to perform the installation (for example, Windows, UNIX or AIX). Part of the installation process is the creation of an uninstaller. However, because you were using another system to do your installation, the uninstaller that was created was for the system that you installed from and not for the System i system. This uninstaller cannot be used to uninstall the DS CLI. When you want to uninstall the DS CLI, you can use one of the following two methods:
78
v Uninstall directly from your i5/OS iSeries system. You might use this method if you are not planning to upgrade the DS CLI and you want to totally remove the DS CLI from your System i system. v Uninstall using a remote system. You might use this method when you are upgrading the DS CLI, because after the removal, you can use this remote system to install the upgraded DS CLI.
Removing the DS CLI using your System i system directly

Complete this task to remove the DS CLI through the direct use of your System i system. You cannot use the conventional DS CLI removal methods that are used on other systems because the installation of the DS CLI on your System i system was done from a remote system. The remote installation does not allow the creation of an uninstaller that can be used directly by your System i system for the removal process. However, it is possible to use your System i system directly (bypassing the uninstaller) to remove the DS CLI application. You cannot use the uninstaller that was created for the DS CLI when you originally installed the DS CLI because it was created for the remote system that you used for the installation and not for the System i system. You can perform this procedure at any time. However, it is common to perform this procedure when you want to remove the DS CLI from your system, but you do not intend to perform an associated upgrade of the DS CLI application. Note: The i5/OS direct removal method requires that you use the i5/OS console mode and that you issue an i5/OS command. The following steps presume that you are logged in to the i5/OS and have the authority to issue a removal command. Perform the following steps to remove the DS CLI through the direct use of your System i system: 1. Issue the following command from your i5/OS application:
RUNJVA CLASS(run) PARM(-console) CLASSPATH(/QIBM/ProdData/Java400/jt400ntv.jar:/yourdir/_uninst /uninstall.jar)
Substitute your uninstall directory for yourdir. 2. Wait until the uninstall process is complete before you continue with your next process.
Removing the DS CLI from your System i system using the remote method
Complete this task to remove the DS CLI from your System i system using the remote method. You cannot use the conventional DS CLI removal methods that are used on other systems because the installation of the DS CLI on your System i system has been done from a remote system. The remote installation does not allow the creation of an uninstaller that can be used directly by your System i system for the removal process. However, it is possible to use the remote removal method on your System i system to remove the DS CLI application. Ensure that the remote system that you use to uninstall the DS CLI is network-attached to the System i system and is a supported platform for DS CLI.
79
You can use the following remote method to remove the DS CLI from a System i system. You can perform this procedure at any time. However, it is common to perform this procedure when you want to upgrade the DS CLI application, because the remote system that you are using to remove the DS CLI is typically the same system that you use for the upgrade. To remove the DS CLI from your System i system using the remote method, perform the following steps: 1. Use FTP to copy the uninstall.dat and uninstall.jar files from the uninstall directory on your System i system into a common directory on the machine that you are using to do the uninstall. 2. Invoke the uninstall process from the common directory (or point to it using the classpath [-cp] option) by issuing the following command: java -cp uninstall.jar run -os400 <system> <userid> <password> 3. Wait until the uninstall process is completed before you continue to your next process.
OpenVMS system integration

You can adjust your OpenVMS system to obtain greater benefits from the use of the DS CLI application. The hints and tips that are provided in this section show how to obtain these benefits through the optimal integration of the DS CLI into your OpenVMS system. The following list provides the areas that you might consider for optimizing the use of the DS CLI in your OpenVMS system: v Command Console LUN (CCL) v OpenVMS system messages v Message help v Java Run Time Environment (JRE) v Quota recommendations
Enhancing the command console LUN for DS CLI use

The OpenVMS operating system considers a fibre-channel device with LUN ID 0 as Command Console LUN (CCL). These devices do not normally display when you issue the DS CLI lshostvol command. However, with adjustments, these devices can be displayed when you issue the lshostvol command. The following description provides the information that you need to make this enhancement work on your OpenVMS system. Fibre-channel CCL devices have the OpenVMS device type GG, which result in OpenVMS device names in the form $1$GGAn. In contrast, fibre-channel disk devices have the OpenVMS device type DG, which result in device names in the form $1$DGAn. Therefore, LUN 0 devices on OpenVMS are a special device type, different from disk devices. The DS CLI lshostvol command displays the mapping of host device names or volume names to machine type 2105, 2107, and 1750 volume IDs. That implies that all host devices belonging to 2105/2107/1750 volumes are displayed. Therefore, CCL devices $1$GGAn are included in the lshostvol output for multiplatform consistency and to match the output of other DS CLI commands.
80
However, the inclusion of CCL devices can be confusing for users who expect that the lshostvol command displays only the disk devices. You can use the OpenVMS logical name IBMDSCLI$SHOW_GG_DEVICES to modify the DS CLI behavior: If this logical name translates to an expression which evaluates as True in OpenVMS conventions (1, Y, YES, T, or TRUE), then the $1$GGAn CCL devices are shown in the command output. Otherwise, the $1$GGAn CCL devices are not shown. The startup procedure IBMDSCLI$STARTUP.COM defines the logical name IBMDSCLI$SHOW_GG_DEVICES as Y. If you want to suppress $1$GGAn CCL devices in the lshostvol command output, you can redefine the logical name after the startup procedure has been processed.
Enhancing the OpenVMS system messages

When you use the DS CLI, the application provides messages regarding the application processes, status, and errors. You also receive the OpenVMS system messages but they are displayed in a different format. You can make this situation less confusing by making the following adjustments. The DS CLI messages are presented in an operating-system independent format. In contrast, native OpenVMS programs provide messages using the system message facility as displayed in the following format: %facility-level-identification, text. To ensure that the OpenVMS command SET MESSAGE and customer-written tools that scan for such messages work correctly, the DS CLI provides each message using OpenVMS system services in addition to the operating system independent output. After displaying the OpenVMS message, the normal DS CLI message is provided unchanged. This ensures that the DS CLI messages are identical across platforms and that you can work with the DS CLI documentation. However, these redundant messages can be confusing for users who are not familiar with OpenVMS. You can use the OpenVMS logical name IBMDSCLI$OPENVMS_MESSAGES to modify the DS CLI behavior: If this logical name translates to an expression which evaluates as True in OpenVMS conventions (1, Y, YES, T, or TRUE), then the additional OpenVMS-formatted messages are presented. Otherwise, only the operating system independent DS CLI messages are shown. The startup procedure IBMDSCLI$STARTUP.COM defines the logical name IBMDSCLI$OPENVMS_MESSAGES as Y. If you want to suppress the OpenVMS-formatted messages, you can redefine the logical name after the startup procedure has been processed.
Enabling OpenVMS to use the DS CLI help

The DS CLI installation process offers the option to add modules to the system help library. If you enable OpenVMS with this option, you can use the DS CLI help. The DS CLI installation process offers the option to add modules to the system help library SYS$COMMON:[SYSHLP]HELPLIB.HLB and the system messages database SYS$COMMON:[SYSHLP]MSGHLP$LIBRARY.MSGHLP$DATA. If you choose this option, the module IBMDSCLI is added as the top-level key to the help library, and the DS CLI status messages can be accessed using the HELP/MESSAGE/FACILITY=IBMDSCLI command. Additionally, the login
81
procedure IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM activates the message section file IBMDSCLI$SYSTEM:IBMDSCLI_Messages_Shr.exe for the current process. In every case, the installation process provides the following files in the directory which is referred by the logical name IBMDSCLI$HELP: IBMDSCLI_Ovr.hlp A help library containing one module with the top-level key IBMDSCLI. You can add this library to the search list for help libraries in your OpenVMS system by defining appropriate logical names HLP$LIBRARY, HLP$LIBRARY_1, HLP$LIBRARY_2, and so forth. IBMDSCLI_Messages.msghlp$data A message help data file with messages for facility IBMDSCLI. You can add this data file to the searchlist for message help files in your OpenVMS system by defining the logical name MSGHLP$LIBRARY accordingly. If you do not want the installation process to modify the OpenVMS system libraries, you can use these OpenVMS default logical names to integrate the DS CLI help information manually.
Java Runtime Environment considerations for DS CLI

The DS CLI login procedure IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM defines JAVA$CLASSPATH in the OpenVMS process logical name table and it overrides any existing Java classpath definition. If you want to use other Java-based software in the same process, you must redefine JAVA$CLASSPATH so that it provides the classpath as a JAVA command parameter. The following information provides an overview of how the installation of the DS CLI affects the Java environment of your OpenVMS system. Because the DS CLI relies on Java Run Time Environment (JRE) V1.4.2, mandatory JRE files are installed in the directory tree that is referenced by the logical name IBMDSCLI$JRE. This setup is according to HP guidelines. The login procedure IBMDSCLI$MANAGER:IBMDSCLI$LOGIN.COM calls the JRE setup procedure which defines several logical names and DCL symbols for usage by the Fast Virtual Machine. If your OpenVMS host system uses other software that requires JRE but cannot run with the same JRE version as the DS CLI, users of that software can switch between different Java versions. To use different JRE versions, you must run a command procedure to set up the Java environment definitions for the version that you want to use in the given process (see the OpenVMS Java documentation at: http://h18012.www1.hp.com/java/documentation /1.4.2/ovms/docs/user_guide.html The DS CLI application-specific Java classes are bundled in Java Archive (.JAR) files in the directory referenced by logical name IBMDSCLI$LIBRARY. These files must be included in the Java classpath. On OpenVMS, two logical names define the classpath: CLASSPATH For UNIX-style names. You can use a string inside single quotation marks that consists of colon-separated path names.
82
JAVA$CLASSPATH For OpenVMS specification syntax. You can specify multiple paths with a comma-separated expression (not enclosed in single quotation marks) as OpenVMS logical name search list. JAVA$CLASSPATH overrides CLASSPATH, if JAVA$CLASSPATH is defined. Because of this override process, you might have to redefine the JAVA$CLASSPATH to provide the class path as a JAVA command parameter. However, this JAVA command parameter is only required if you want to use other Java-based software in the same process.
Quota considerations for DS CLI

The JRE was designed to perform optimally on UNIX systems, where each process is given large quotas by default. On OpenVMS, the default behavior gives each process lower quotas so that many processes can co-exist on a system. To get the best Java performance on OpenVMS, HP recommends that you set process quotas to match a typical UNIX system. HP also recommends these as minimum quota settings (except where noted). See these recommendations at: http://h18012.www1.hp.com/java/documentation/1.4.2/ovms/ docs/user_guide.html To check if your current process quotas fulfill the recommendations, you can run the following process: IBMDSCLI$JRE:[LIB]Java$Check_Environment.com.
83
84
Chapter 4. Providing PE package and state save information

This section contains information to help you use the DS CLI commands to provide your PE package and state save information to IBM. This information allows IBM to analyze your problem and to assist you directly with maintaining your DS6000 in an optimal state. Note: The commands you issue for providing PE package and state save information can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. When you are directed by IBM Support personnel, you can use the DS CLI mkpe, offloadss, sendpe, and sendss commands to collect and to pass detailed information to IBM. You can use the following modes to provide this information to IBM: v FTP v An e-mail with the PE package, statesave file, or both, included as attachments v CD sent by postal mail v A manual method that does not use FTP, e-mail, or a CD sent by postal mail Perform the following steps to send your pe package and statesave files to IBM support personnel: 1. Use the DS CLI mkpe and offloadss commands to initially collect and send pe package and state save information to IBM support personnel. See Providing problem determination information using FTP for additional information. 2. Use the DS CLI sendpe command to send the PE package to IBM Support after the initial FTP transfer failed. See Sending the PE package after the FTP transfer has failed on page 89 for additional information. 3. Use the DS CLI sendss command to send the state save information to IBM Support after the initial FTP transfer has failed. See Sending the statesave file after the FTP transfer has failed on page 91 for additional information. 4. Use the DS CLI mkpe command to collect and send an SMC only PE package to IBM support personnel. See Providing a management console only PE package on page 88 5. Use the alternative methods (e-mail or CD) to send PE package and state save information to IBM support personnel when there is no way you can use FTP. See Providing problem determination information when FTP is not available on page 92 for additional information.
Providing problem determination information using FTP

The problem determination information that you collect when you process the mkpe and offloadss commands is forwarded automatically using FTP to IBM support personnel. Because FTP is not a 100% reliable transport protocol, files that are sent by FTP are also saved on the storage management console. These saved files are automatically managed so that they do not accumulate and take up too much disk space on the storage management console. To use the FTP feature of the mkpe and offloadss commands, ensure that you meet the following requirements:
85
v The mkpe and offloadss commands can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. v The server enclosures must be powered on and functioning. v There must be an active IP connection between your storage management console and both processor cards. v Adequate disk space must exist on your storage management console. v The storage management console must be connected to the Internet, and its firewall must allow FTP to the IBM support Web address. v You must have administrator authority to initiate and follow through with this process. Note: The mkpe and offloadss commands only work when the DS CLI is installed on the storage management console PC. This is because the programs that gather and send the problem determination information to IBM, only exist on the storage management console PC. The mkpe command collects the PE package data and presents the information in a summary format. The offloadss command collects the statesave data, which contains additional detailed information. Generally, when IBM support personnel request the PE package, they also request that you provide the statesave information. There are occasions, however, when only the PE package is needed for analysis. Notes: 1. On a typical installation, MR1750_SM_HOME is set to C:\Program Files\IBM\DS6000StorageManager\SM. 2. Statesave files and PE packages are copied to the management console in subdirectory %MR1750_SM_HOME%\send2IBM before they are sent to IBM. 3. Statesave files and PE package files that have been sent by FTP to IBM can be found in the management console subdirectory, %MR1750_SM_HOME%\send2IBM\sent\. 4. The examples provided in this task are based on a Windows environment. Perform the following steps to create PE package and statesave files and to automatically provide the requested information to IBM support personnel through the FTP process. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the mkpe command to create the PE package file. Enter the mkpe command from the dscli prompt with the following parameters and variables: dscli>mkpe -retry count storage_image_ID Example
dscli>mkpe -retry 3 IBM.1750-75FA120
Note: Use the -retry parameter when you want the FTP process to attempt to send the files more than once. You can specify a value of 0 - 3, with 0 being the default value. A successful process of this example command displays the following message:
The following PE package successfully generated and copied from 1750-68FA120: c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A.
86
IBM.0.NOPMH.20050328223544.cl0.pe.zip c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A. IBM.0.NOPMH.20050328223807.cl1.pe.zip PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223807.cl1.pe.zip mkpe successfully completed.
Notes: a. The PE package information is collected on the management console subdirectory %MR1750_SM_HOME%\send2IBM and using FTP, is automatically sent to the IBM support Web address. b. Files that are sent by FTP are automatically moved to the management console subdirectory, %MR1750_SM_HOME%\ send2IBM\sent\. 2. Issue the offloadss command to create the statesave file. Enter the offloadss command at the dscli command prompt with the following parameters and variables: dscli>offloadss -retry count storage_image_ID Example
dscli>offloadss -retry 3 IBM.1750-68FA120
Note: Use the -retry parameter when you want the FTP process to attempt sending the files more than once. You can specify a value of 0 - 9, with 0 being the default value. A successful process of this example command displays the following message:
offloadss: The following files offloaded from 1750-68FA120: /Program Files/IBM/DS6000StorageManager/SM/send2IBM/ 175051113AB15A.IBM.0.NOPMH.20050327243603.cl0.dumptrace.tgz offloadss: statesave FTPed to IBM: 175051113AB15A.IBM.0.NOPMH.20050327243603.cl0.dumptrace.tgz offloadss: successfully completed.
Notes: a. The statesave information is collected on the management console subdirectory %MR1750_SM_HOME%\send2IBM and automatically sent to the IBM support Web address. b. The files that are sent by FTP are automatically moved to the management console subdirectory %MR1750_SM_HOME%\ send2IBM\sent\. If the automatic process that sends files by FTP is not available, you can use the sendpe or sendss commands at a later time. Or, contact IBM support personnel. You might be asked to use the following process: 1. Open a DOS window on the management console and change directories (cd) to the location of the files to be sent to IBM. For example, c:\program files\IBM\DS6000\SM\send2IBM
87
2. Type ftp testcase.software.ibm.com at the command prompt and press Enter. A prompt for user is displayed. 3. Type ftp at the user prompt and press Enter. The password prompt is displayed. 4. Type your e-mail address at the password prompt and press Enter. The command prompt is displayed. 5. Type bin and press Enter. It is important that you type bin to avoid the corruption of files. 6. Type cd /ssd/toibm/sharkdumps at the command prompt and press Enter. The command prompt at the ssd/toibm/sharkdumps directory is displayed. 7. Type mput *.* at the command prompt and press Enter. The file names that can be sent to IBM are displayed one at a time. 8. Answer y (yes) or n (no) to each file name that is presented to denote whether you want to transfer the file. Notes: 1. You are not able to do a dir or ls command to validate that the file have been transferred. 2. You are not able to transfer the same file twice. If a situation arises where this needed, rename the file and then transfer it. Provide an e-mail to IBM support explaining this circumstance.
Providing a management console only PE package

Complete this task to create and send a management console (MC) only PE package to IBM support personnel. An MC only PE package contains the log files and configuration files that are associated only with the management console. It does not contain any files that are associated with the DS6000 nodes. You must use the DS CLI mkpe command to collect and create the MC only PE package. To use this command and to use the automatic FTP feature to transfer the information to IBM support personnel, you must ensure that you meet the following requirements: v The mkpe command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. v The server enclosures must be turned on and functioning. v There must be an active IP connection between your storage management console and both processor cards. v Adequate disk space must exist on your storage management console. v The storage management console must be connected to the Internet, and its firewall must allow FTP transfer to the IBM support Web address. v You must have administrator authority to use the mkpe command. Perform the following steps to create and send an MC only PE package file to IBM support personnel using the DS CLI mkpe command. The example commands that are displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Call IBM support personnel and determine that a problem exists that affects only the management console. After you determine that you must send an MC only PE package to IBM, ensure that you also agree on a name to attach to the report before you hang up.
88
Note: The name is critical in identifying the PE package because there is no other way to determine which management console is being referenced by the PE package. If you do not have a name, you can assign one at the time that you initiate the command. Then, you must call the IBM support personnel and inform them of the name that you have attached to the report before you can send it to them. 2. Issue the mkpe command to collect and create the MC only PE package. Enter the mkpe command at the dscli command prompt with the following parameters and variables: dscli>mkpe -smconly -customer customer_name -retry count storage_image_ID Example
dscli>mkpe -smconly -customer mine4results -retry 3 IBM.1750-75FA120
The output from this command example produces the following file name:
1750511SMC0000.mine4results.000.NOPMH.20051028223544. cl0.SMCLog.zip
This file name is copied to the management console in subdirectory %MR1750_SM_HOME%\send2IBM. The FTP feature of this command automatically initiates and sends the MC only PE package to IBM support personnel. Based on the request that you made in the command (-retry 3), the FTP continues to initiate the transfer up to 3 times if it was not successful on the initial attempt. When the FTP transfer is successful, the following two results occur: v You receive a confirmation message that the transfer was successful like the following:
PE package successfully sent to IBM: 1750511SMC0000.mine4results. 000.NOPMH.20051028223544.cl0.SMCLog.zip
v The MC only PE package file is moved into the management console subdirectory, %MR1750_SM_HOME%\send2IBM\sent\. Note: If the FTP transfer was not successful, you can wait until later and attempt to resend the file using the sendpe command.
Sending the PE package after the FTP transfer has failed

Complete this task to send PE package files to IBM support personnel after the initial FTP transfer failed when you used the DS CLI mkpe command. You must use the DS CLI sendpe command to send a PE package to IBM support personnel after the initial FTP transfer has failed when you used the DS CLI mkpe command. To use the sendpe command and to use the automatic FTP feature to transfer the information to IBM support personnel, you must ensure that you meet the following requirements: v The sendpe command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. v The server enclosures must be turned on and functioning. v There must be an active IP connection between your storage management console and both processor cards. v Adequate disk space must exist on your storage management console. v The management console must be connected to the Internet, and its firewall must allow FTP transfer to the IBM support Web address. v You must have administrator authority to use the sendpe command.
89
It is possible that when you initially created the PE package file and tried to send it using FTP that there was a problem with the connection. Or, it might be a case that your management console is located in a network that does not have direct access to the Internet or to IBM support personnel. In any case, the time period for using the automatic feature of FTP that is associated with the DS CLI mkpe command has expired. However, you must still send the PE package to IBM support personnel. This can be done using the DS CLI sendpe command. Perform the following steps to send a PE package file to IBM support personnel after the time period has expired for using the DS CLI mkpe command. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspe command to locate the PE package files that are ready to be sent to IBM support personnel. Enter the lspe command at the dscli prompt with the following parameters and variables: dscli>lspe -l -state ready Example
dscl>lspe -l -state ready
Notes: a. ready is the actual value that you must state in the command. b. Your search criteria is narrowed by using the -state ready parameter. Only the files that are in a ready state can be sent to IBM support personnel. c. Use the -l parameter to provide PE package file details such as, file name, state (status), creation date, and size. d. These files reside in the management console subdirectory %MR1750_SM_HOME%\send2IBM until they are sent to IBM support personnel. 2. Issue the sendpe command when you have determined which PE package file that you must send to the IBM support personnel. Enter the sendpe command at the dscli command prompt with the following parameters and variables: dscli>sendpe -retry count pepackage_name Example
dscli>sendpe -retry 3 175051113AB15A.IBM.0.NOPMH.20050328223544. cl0.pe.zip
Notes: a. Use the -retry count parameter to specify the number of times that you want the command to try to initiate the FTP transfer process. You can specify a value of 0 - 9 attempts. b. If there is an FTP transfer problem that does not allow an FTP transfer, you can do one of the following: v Wait until a later time, use the sendpe command, and once again attempt to send the PE package. v Use an e-mail or copy the PE package file onto a CD and mail it to an address that is provided by IBM support personnel. When the FTP transfer is successful, the following two results occur: v You receive a confirmation message that the transfer was successful:
90
PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223544. cl0.pe.zip
v The PE package file is moved into the management console subdirectory, %MR1750_SM_HOME%\send2IBM\sent\.
Sending the statesave file after the FTP transfer has failed
Complete this task to send statesave files to IBM support personnel after the initial FTP transfer has failed when you used the DS CLI offloadss command. You must use the DS CLI sendss command to send a statesave file to IBM support personnel after the initial FTP transfer has failed when you used the DS CLI offloadss command. To use the sendss command and to use the automatic FTP feature to transfer the information to IBM support personnel, you must ensure that you meet the following requirements: v The sendss command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. v The server enclosures must be turned on and functioning. v There must be an active IP connection between your storage management console and both processor cards. v Adequate disk space must exist on your storage management console. v The management console must be connected to the Internet, and its firewall must allow FTP transfer to the IBM support Web address. v You must have administrator authority to use the sendss command. It is possible that when you initially created the statesave file and tried to send it using FTP that there was a problem with the connection. Or, it might be a case that your management console is located in a network that does not have direct access to the Internet or to IBM support personnel. In any case, the time period for using the automatic feature of FTP that is associated with the DS CLI offloadss command has expired. However, you must still send the pe package to IBM support personnel. This can be done using the DS CLI sendss command. Perform the following steps to send a statesave file to IBM support personnel after the time period has expired for using the DS CLI offloadss command. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lsss command to locate the statesave files that are ready to be sent to IBM support personnel. Enter the lsss command at the dscli prompt with the following parameters and variables: dscli>lsss -l -state ready Example
dscl>lsss -l -state ready
Notes: a. ready is the actual value you must state in the command. b. Narrow your search criteria by using the -state ready parameter. These are the only files that can be sent to IBM support personnel.
91
c. Use the -l parameter to provide the statesave file details such as, file name, state (status), creation date, and size. d. These files reside in the management console subdirectory %MR1750_SM_HOME%\send2IBM until they are sent to IBM support personnel. 2. Issue the sendss command when you have determined which PE package file that you must send to the IBM support personnel. Enter the sendss command at the dscli command prompt with the following parameters and variables: dscli>sendss -retry count statesave_filename Example
dscli>sendss -retry 3 175051113AB15A.IBM.0.NOPMH.050318180713.cl0.dumptrace.tgz
Notes: a. Use the -retry count parameter to specify the number of times that you want the command to try to initiate the FTP transfer process. You can specify a value of 0 - 9 attempts. b. If there is an FTP transfer problem that does not allow an FTP transfer, you can do one of the following: v Wait until a later time, and then try again to send the statesave package with the sendss command. v Use an e-mail or copy the statesave file onto a CD and mail it to an address that is provided by IBM support personnel. When the FTP transfer is successful, the following two results occur: v You receive a confirmation message that the transfer was successful:
sends: Statesave sent to IBM: 175051113AB15A.IBM.0.NOPMH.050318180713.cl0.dumptrace.tgz sendss: successfully completed.
v The statesave file is moved into the management console subdirectory, %MR1750_SM_HOME%\send2IBM\sent\.
Providing problem determination information when FTP is not available

Complete this task to provide problem determination information to IBM if FTP is not available. There might be times when you must provide problem determination information to IBM support personnel but your FTP connection is not available. You can still make use of the mkpe and offloadss commands to collect the information, but you must include the -noftp parameter. You can send the collected information to IBM support using e-mail or sending a CD that contains the information. You must ensure that you are logged into the DS CLI application in interactive mode. The mkpe command collects the PE package data and presents the information in a summary format. The offloadss command collects the statesave data, which contains additional detailed information. Generally, when IBM support personnel request the PE package, they also request that you provide the statesave information, as well. There are occasions however, when only the PE package is needed for analysis. Perform the following steps to provide the requested information to IBM support:
92
Note: Obtain the address information from IBM Support where you can send your e-mail or CD. 1. Issue the mkpe command from the dscli prompt as follows: dscli>mkpe -noftp IBM.1750-75FA120. The PE package information is collected on the management console subdirectory %MR1750_SM_HOME%\send2IBM. 2. Create and send an e-mail with your attached PE package file, to the address IBM Support has directed that your file be sent. Or, send your CD by mail to the address that IBM Support has given you. Note: The size of the attachment might exceed the limits that you have set for your e-mail attachments. It is suggested that the e-mail attachments be put into individual e-mails to preclude exceeding your limits. If there is still a problem, you might consider copying the files onto a CD and then mailing the CD to the address that IBM Support has given you. 3. Issue the offloadss command from the dscli prompt as follows: dscli>offloadss -noftp IBM.1750-75FA120. The statesave files are collected on the management console subdirectory %MR1750_SM_HOME%\send2IBM. 4. Create and send an e-mail with your attached statesave file to the address that IBM Support has directed that your file be sent. Or, send your CD by mail to the address that IBM Support has given you. 5. Wait for confirmation from IBM Support that they have received your e-mail and copy your statesave files and PE package files to a backup directory. Note: When your problem has been resolved, you can delete the backup copy of your files. 6. Delete the PE package files from your backup directory. 7. Delete the statesave files from your backup directory.
93
94
Chapter 5. Configuring and managing logical storage

This section provides the information that you need to configure and maintain your logical storage whether it consists of fixed block volumes or count-key-data volumes. You must complete a logical configuration for each storage unit. For example, each storage unit must be assigned a worldwide node name (WWNN). You must also configure the arrays, ranks, logical subsystems or logical control units, and extent pools from which your logical volumes are created. After your initial configuration, you might make adjustments in your configuration and in time you might delete your configuration and create a new one. The processes that are listed in this section are designed to help you complete these tasks using the DS CLI commands.
Configuring new fixed block storage using the DS CLI

This section describes how you can configure new fixed block storage within a storage unit by using the command-line interface. Before you begin, you must be logged into the DS CLI application in interactive command mode. You must also be connected to a storage unit that is used for open systems host system storage. The creation of the fixed block storage configuration is described first. The configuration of the storage unit SCSI host ports to enable access to fixed block storage is described second. You can run these two basic steps in the reverse order, but it is better to create storage configurations first, thereby creating the media to back up configuration data that is not related to the storage configuration. Configuring new fixed block storage involves the following processes: v Creating fixed block extent pools v Creating arrays v Creating and associating ranks with extent pools v Creating fixed block volumes v Creating fixed block volume groups v Configuring fibre-channel I/O ports v Creating SCSI host port connections Note: All the examples provided in the described tasks are based on the premise of using the interactive mode of DS CLI. If you were processing many transactions, you would likely use the script mode to process your transactions.
Creating extent pools for fixed block volumes using the DS CLI
Complete this task to create fixed block volume extent pools. This is the first step in configuring new fixed block storage. You can use the DS CLI commands to create extent pools for fixed block volumes.
95
Creating the extent pools before the arrays and ranks saves a processing step. When you create the new ranks, you can assign them to existing extent pools. Otherwise, you must modify each rank object to complete the extent pool ID assignment after the extent pools have been defined. Each extent pool is defined with the rank group of 0 or 1 and a storage type of fb. You must define one extent pool for each rank group and storage type combination. This means that you must make a minimum of two extent pools for a storage unit that contains fixed block storage: one fixed block extent pool per rank group. Extent pools that are defined for rank group 0 or 1 are assigned an even- or odd-numbered extent pool ID, respectively. Even-numbered extent pools are managed by storage server ID 0. Odd-numbered extent pools are managed by storage server ID 1. Each rank is assigned to one extent pool; therefore, storage server workload is affected by the rank assignments to even- and odd-numbered extent pool IDs. It is better to evenly distribute rank and extent pool allocations in order to keep the storage server workloads balanced. You can create more than the minimum number of extent pools. For example, you can define unique extent pools for each RAID type (5 or 10) that is configured in a storage image. Or, you can define and name extent pools according to the host system attachments that access the volumes that are created from extent pool extents. You can have the same number of extent pools as ranks. i5/OS considerations i5/OS supports only specific volume sizes and these might not be an exact number of extents. i5/OS volumes are defined in decimal gigabytes (10^9 bytes). You can use the following table when you are creating the logical volumes for use with i5/OS. You will notice that in almost every case, the i5/OS device size does not match a whole number of extents, so some space can be wasted for you specific configuration.
i5/OS Device size (decimal gigabytes) 8.5 17.5 35.1 70.5 141.1 282.2 Unusable space (binary gigabytes) 0.00 0.66 0.25 0.28 0.56 0.13
Protected Model Type xxxx-A01 xxxx-A02 xxxx-A05 xxxx-A04 xxxx-A06 xxxx-A07
Unprotected Model Type xxxx-A81 xxxx-A82 xxxx-A85 xxxx-A84 xxxx-A86 xxxx-A87
Number of LBAs 16 777 216 34 275 328 68 681 728 137 822 208 275 644 416 551 288 832
Extents 8 17 33 66 132 263
Usable space% 100.00 96.14 99.24 99.57 99.57 99.95
Note: Only Ax2, Ax4 and Ax5 models are supported as external LSU LUNs. Use the lsextpool and mkextpool commands to create the fixed block extent pools. You must be logged into the DS CLI application and connected to the storage unit that will be used for open systems host system storage.
96
Perform the following steps to create the fixed block extent pools. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables 1. Issue the mkextpool command to create the fixed block extent pool for rank group 0. Enter the mkextpool command at the dscli command prompt with the following parameters and variables:
dscli>mkextpool -dev storage_image_ID -rankgroup [0 | 1] -stgtype fb extent_pool_name
Example
dscli>mkextpool -dev IBM.1750-68FA120 -rankgrp 0 -stgtype fb P0
where P0 represents the extent pool name that you assign. This name can be 16 double-byte characters. 2. Press Enter. A successful process displays the following message:
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Extent pool P0 successfully created.
Note: The unique name that you assigned to the extent pool does not display in the process message. However, when you issue the lsextpool command, the extent pool name is displayed. 3. Repeat Step 1 for each extent pool that you want to create. Try to evenly distribute rank and extent pool allocations in order to keep the storage server workloads balanced. 4. Verify the extent pool assignments by issuing the lsextpool command when you are done creating the extent pools. Use the -l parameter to display a full report for the extent pools that are assigned to the storage unit. Enter the lsextpool command at the dscli command prompt with the following parameters and variables:
dscli>lsextpool -dev storage_image_ID -l
Example
dscli>lsextpool dev IBM.1750-68FA120 -l
Creating arrays for fixed block volumes using the DS CLI

Complete this task to create arrays using the DS CLI commands. The machine type 1750 contains at least one storage enclosure, with a minimum of four DDMs. The DDMs of a storage enclosure are partitioned into array sites. A machine type 1750 array site consists of four DDMs in one storage enclosure of a storage enclosure pair, with two-to-eight (four DDM) array sites per storage enclosure pair. All storage enclosure pairs must have identical capacity, rpm, and interface characteristics, and an interface to a common DA pair. The creation of arrays is based on the array sites that are associated with the storage unit. Use the lsarraysite and mkarray commands to create the arrays. You want to make an array from 1 or 2 array sites. An array inherits the characteristics of its parent array sites and is given a RAID type attribute (5 or 10). A 1750 array object of RAID type 5 or 10 is made from one or two (4 DDMs) array sites. The status of the array is unassigned until the array is assigned to a rank.
97
Perform the following steps to create an array from unassigned array sites: 1. Issue the lsarraysite command to view a list of array site IDs for all installed array sites. Review those arrays that are designated with the state of unassigned. Enter the lsarraysite command at the dscli command prompt with the following parameters and variables:
dscli>lsarraysite -dev storage_image_ID -state unassigned
Note: If this is your first time creating fixed block volumes, all the arrays are displayed with a state of unassigned. 2. Press Enter. A report of unassigned array sites is displayed. Use the list to identify unassigned array site capacity, rpm, and device adapter (DA) pair attributes. Record the RAID type for each array site. 3. Issue the mkarray command to create an array from either one or two array sites with the status unassigned. Enter the mkarray command at the dscli command prompt with the following parameters and variables:
dscli>mkarray -dev storage_image_ID -raidtype [5 | 10] -arsite array_site
Consider the following when you create the arrays: v Specify one or two array sites with identical capacity, rpm, interface, and DA pair attributes. v The new array inherits the capacity, rpm, interface, and DA pair characteristics of its parent array sites. v The state of the array remains unassigned until it is assigned to a rank. 4. Repeat Step 3 until all unassigned array sites have been assigned to an array. 5. Verify that the array-to-array site assignment is recognized and complete by issuing either the lsarray or lsarraysite command with the -l parameter.
Creating a rank using the DS CLI

Complete this task to create a rank using the DS CLI commands. A rank is a logically contiguous storage space that is made up of one array. You can assign a rank to every unassigned array. A rank inherits the characteristics, including the RAID type, of its parent array and is given a storage type attribute of either FB (fixed block) or CKD (count key data). The rank configuration state is unassigned until it is assigned to an extent pool. An unassigned rank is not associated with either rank group 0 or 1. Any unassigned rank can be assigned to an extent pool that is associated with either rank group 0 or 1. Note: You can assign a rank to an unassigned array and also assign the rank to an extent pool at the same time if you have already created the extent pools and the arrays. Creating extent pools first saves a step in the configuration. Use the lsarray, mkrank, and lsrank commands to assign a rank to each unassigned array. You must be logged into the DS CLI application and connected to the storage unit that will be used for open systems host system storage. To create ranks, perform the following steps: 1. Ensure you have a list of the unassigned arrays for which ranks must be assigned. Issue the lsarray command to obtain this list if you do not already have it. Enter the lsarray command at the dscli command prompt with the following parameters and variables:
dscli>lsarray -dev IBM.1750-68FA120 -state unassigned
98
2. Issue the mkrank command to assign a rank to rank group 0 or 1 according to the rank group number of the assigned extent pool ID. Enter the mkrank command at the dscli command prompt with the following parameters and variables:
mkrank -dev IBM.1750-68FA120 -array A44 -stgtype fb -extpool P1
Notes: a. You can specify either the -wait or the -extpool parameter when you use the mkrank command. Either of these parameters allows you to be notified if the rank configuration has failed for any reason. b. If you use the -wait parameter, you cannot issue other commands until the entire transaction has processed. 3. Press Enter to display a report of rank assignments for your entire storage unit. Because the process of creating the rank involves formatting drives, it could take some time before the process finishes. If you want to check on the process, you can issue the lsrank command from a different DS CLI session. A successful process displays the following type of message:
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Device: IBM.1750-68FA120 Rank IBM.1750-68FA120/R44 successfully created.
4. Repeat Step 2 until all unassigned arrays are assigned a rank and an extent pool. 5. Issue the lsrank command to verify that ranks and extent pools have been assigned. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
dscli>lsrank -dev IBM.1750-68FA120 -l
6. Press Enter to display a report of the rank assignments for your entire storage unit.
Creating fixed block volumes using the DS CLI

Complete this task to create fixed block volumes. You must have completed the following tasks before you can create your fixed block volumes: v Created your extent pools. v Created your arrays. v Created and assigned your ranks. Perform the following steps to create fixed block volumes: 1. View your list of fixed block extent pool IDs and determine which extent pool IDs that you want to use as the source for the fixed block logical volumes. You obtained this list when you first created your extent pools. If this list is not available, issue the lsextpool command to obtain the list of extent pool IDs. Enter the lsextpool command at the dscli command prompt with the following parameters and variables:
dscli>lsextpool -dev IBM.1750-13AAD7A -stgtype fb -l
Extent pool attributes determine the size and quantity of volumes that can be created. The extent pool ID (even/odd) indicates the storage server (0|1), which dictates that the LSS ID component of the volume ID must be an even or an odd number.
99
2. Issue the lsaddressgrp command to find unassigned and available address groups. Enter the lsaddressgrp command at the dscli command prompt with the following parameters and variables: dscli> lsaddressgrp -dev IBM.1750-68FA120 -l An address group refers to a group of LSSs. Up to 16 LSSs can be grouped into one address group. All LSSs in an address group must be of the same format (CKD or fixed block). Note: If this is your first time creating fixed block volumes, all the address groups are displayed with a state of unassigned. 3. Analyze the address group list to determine which LSSs can be used to make fixed block volumes. Consider the following conditions when doing your analysis: v If the address group list is empty, then all address groups are available to be defined (0 - 3). v If an undefined address group is used to create new fixed block volumes, select the lowest numbered address group. v If you are adding new fixed block volumes to an existing fixed block address group, use the lslss command to identify LSSs that are already defined in the target address group. 4. Issue the mkfbvol command to create fixed block volumes for the specified LSS. Enter the mkfbvol command at the dscli command prompt with the following parameters and variables:
dscli>mkfbvol -dev IBM.1750-68FA120 -extpool P1 -name finance#d -cap 8.6 0100-010f
Consider the following conditions with regard to the command example in this step: v All volumes will have the same type and capacity attributes. v The -extpool parameter identifies a fixed block extent pool containing available data extents. v The -name parameter allows you to assign an easy-to-use label or nickname to the volume. The volume name parameter can include a wild card (#d or #h) that inserts a decimal or hexadecimal volume ID value into the volume name. Note: The decimal designation does not apply to the volume ID number or the number of volumes that were created by the command. It only applies to the unique name that you have assigned. Also, when you process this command, the volume name that you have assigned does not appear in the confirmation message. To view the volume name that you have assigned, issue the lsfbvol or showfbvol command. v The -cap (capacity) parameter is 8.6 GB. The default is binary GB where 1 GB = 1 073 741 824 (2^30 bytes) v The example provides a range of numbers (0100 - 010F) for the number of volumes to be created. Because volumes are created using the hexadecimal numbering system, the range in the example creates 16 volumes. The actual number of volumes that can be created is 255 per LSS based on the following criteria: The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF).
100
DS6000 has a 16 384 volume address space that is partitioned into 64 logical subsystem (LSS) units, where each LSS contains 256 logical volume numbers. The 64 LSS units are assigned to one of 4 address groups, where each address group contains 16 LSSs, or 4096 volume addresses. All of the LSSs in one address group must be of the same type (CKD or fixed block). 5. Repeat step 4 for all of the required logical volumes for each LSS. 6. Issue the lsfbvol command to display a report you can use to confirm the status of your fixed block volumes. Enter the lsfbvol command at the dscli command prompt with the following parameters and variables:
dscli>lsfbvol -dev IBM.1750-68FA120 -l -volgrp V2,V20
Note: It is possible that the report will display that there was a configuration error that is associated with one or more of your mkfbvol transactions.
Creating LUN volumes for System i systems

Complete this task to create fixed block LUN volumes for System i systems. You must have completed the following tasks before you can create your fixed block LUN volumes: v Created your extent pools v Created your arrays v Created and assigned your ranks When you begin your initial configuration, the LSSs and address groups do not exist. The LSSs are created when the first volume of the LSSs is defined during the processing of the mkfbvol command; likewise, the address group gets defined when the first LSS is defined. When you create volumes, you must designate the logical subsystem (LSS) that a particular volume belongs to. After you assign a volume ID, use the first two digits to designate the LSS. For example, if you specify a volume ID of 1900, the volume then belongs to LSS 19. Consider the following specifications before you create your fixed block LUN volumes: v Volumes that belong to an even numbered rank group (cluster) must be in an even numbered LSS; volumes that belong to an odd numbered rank group (cluster) must be in an odd numbered LSS. The cluster that a volume belongs to is determined by specifying the extent pool that the volume is assigned to. v LSS number 1F is reserved for internal use and must not be used as a volume ID. v You must define each volume as protected or unprotected. This is simply a notification to i5/OS; it does not mean that the volume is protected or unprotected. In reality, all LUNs are protected, either by RAID5 or RAID10. Defining a volume as unprotected means that it is available for i5/OS to mirror that volume to another internal or external volume of equal capacity. Unless you intend to use i5/OS (host based) mirroring, define your logical volumes as protected. Under some circumstances, you might want to mirror the i5/OS internal Load Source Unit (LSU) to a LUN in the DS6000. In this case, define only one LUN volume as unprotected; otherwise, i5/OS attempts to mirror all unprotected volumes. v In general, it is best to use one LSS for volumes from one rank.
101
Perform the following steps to create fixed block LUN volumes: 1. View your list of fixed block extent pool IDs and determine which extent pool IDs that you want to use as the source for the fixed block logical volumes. You obtained this list when you first created your extent pools. If this list is not available, issue the lsextpool command to obtain the list of extent pool IDs. Enter the lsextpool command at the dscli command prompt with the following parameters and variables:
dscli>lsextpool -dev IBM.1750-13AAD7A -stgtype fb -l
Extent pool attributes determine the size and quantity of volumes that can be created. The extent pool ID (even | odd) indicates the storage server (0 | 1), which dictates that the LSS ID component of the volume ID must be an even or an odd number. 2. Issue the mkfbvol command to create fixed block LUN volumes for the specified LSS. Enter the mkfbvol command at the dscli command prompt with the following parameters and variables:
dscli>mkfbvol -dev IBM.1750-13AAD7A -extpool p0 -os400 A05 -name i5_unprot_#h 1001-1002
Consider the following conditions with regard to the command example in this step: v The -extpool parameter identifies a fixed block extent pool containing available data extents. v The -os400 parameter allows you to designate the size and protection of a LUN volume by specifying the volume model. The example shows LUN volumes of protected model type A05 with a size of 35.1 decimal gigabytes. v The -name parameter allows you to assign an easy-to-use label or nickname to the volume. The volume name parameter can include a wildcard (#d or #h) that inserts a decimal or hexadecimal volume ID value into the volume name. Note: The hexadecimal designation does not apply to the volume ID number or the number of volumes that were created by the command. It only applies to the unique name that you have assigned. Also, when you process this command, the volume name that you have assigned does not appear in the confirmation message. To view the volume name that you have assigned, issue the lsfbvol or showfbvol command. v The example provides a range of numbers (0101 - 0102) for the number of volumes to be created. The actual number of volumes that can be created is 255 per LSS based on the following criteria: The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF). You can define up to 31 LSSs in a storage unit. Even numbered LSSs have an association with storage unit server 0. Odd numbered LSSs have an association with storage unit server 1. LSS number 1F is reserved. 3. Repeat step 2 for all of the required logical volumes for each LSS. 4. Issue the lsfbvol command to display a report you can use to confirm the status of your LUN volumes. Enter the lsfbvol command at the dscli command prompt with the following parameters and variables:
dscli>lsfbvol -dev IBM.1750-13AAD7A -l
102
Correcting a fixed block configuration error

Complete this task to correct a fixed block volume configuration error. There might be occasions when you are using the mkfbvol command to create fixed block volumes, but the transaction fails. You might not be aware of the failure until you run the lsfbvol or the showfbvol command to check the status of the volumes that you have created. The lsfbvol or the showfbvol commands display reports that includes a configstate category. The configuration state category reports on the current state of the rank. One of the configuration state codes is configuration error. A status of configuration error specifies that the configuration process did not complete successfully. This state reflects an internal error condition and is not an indication that there was a user input error. You might want to gather additional information about what caused the error, which can help you determine how to correct it. Generally, to correct this error state, you must delete the designated volume configuration and submit a new transaction request. Perform the following steps to obtain additional information about the configuration error and to correct this error condition. 1. Add the -v (verbose) command flag to your mkfbvol command, and reissue the command for the transactions that show the configuration error designation. Note: You can also turn on the verbose mode in your profile file, and reissue the command. If you designate the verbose mode, the display of extra output includes the error code that is generated when the create rank transaction fails. 2. Issue the rmfbvol command to delete the designated volume configurations if you do not want to obtain additional information about what caused the configuration error. Note: In the majority of instances, this is the only method for correcting a configuration error.
Creating fixed block volume groups using the DS CLI

Complete this task to create fixed block volume groups. A volume group identifies the set of fixed block logical volumes that are accessible by one or more SCSI host system ports. SCSI host system access is constrained to the identified access mode. Only those SCSI host ports that are registered to a volume group ID are allowed to access the set of logical volumes that is contained by the volume group. Logical volumes can be assigned to a volume group when the volume group is created, or the logical volumes can be added (or removed) at a later time. The volume group type determines the maximum number of volumes that can be assigned to a volume group, either a maximum of 256 volumes or a maximum of 64 000 volumes. The volume group type must be selected according to the addressing capability of the SCSI host system that will use the volume group.
103
Perform the following steps to create and view fixed block volume groups: 1. Issue the mkvolgrp command to create a fixed block volume group. Enter the mkvolgrp command at the dscli command prompt with the following parameters and variables: Note: Repeat this step for each volume group that you want to create.
dscli>mkvolgrp -dev IBM.1750-68FA120 -hosttype pSeries -volume 0001-0010,0120 my_nickname
Notes: a. You can use the -hosttype parameter with the mkvolgrp command. This parameter is an easier way of specifying the type of volume group. If you do not use the -hosttype parameter, it is assumed that the volume group type is scsimask. b. You cannot use the -type parameter and the -hosttype parameter together. c. If your volume group is not scsimask type and you do not want to use the -hosttype parameter, use the -type parameter. scsimask as the default value of the -type parameter; you can also specify scsimap256 or os400mask as your volume group type. Because you need to know the criteria that is associated with these volume group types, see the mkvolgrp command for more information. d. Volume IDs must meet the following criteria: v ID ranges must be separated by a comma (displayed as 0001-0010,0120 in the example). v For scsimap256, the array or ranges cannot exceed 256 volume ID entries. Otherwise, up to 64 384 entries are allowed. v Use the -type 0s400mask parameter if the volume group is limited to fixed block volume OS400-protected or OS400-unprotected types. Otherwise, the volume group is limited to the fixed block volume type 1750. v The volume group name (my_nickname in the example command) must be unique within the scope of the specified storage unit. 2. Issue the lsvolgrp command to create a list of assigned volume group IDs. Enter the lsvolgrp command at the dscli command prompt with the following parameters and variables:
dscli>lsvolgrp -dev IBM.1750-68FA120 -l
Notes: a. The lsvolgrp command with the -l parameter displays a report with the following 3 values: v Name (the unique name that you assigned to the volume group) v Volume group ID v Type (the configured volume group type) b. You can narrow the scope of the report by requesting a specific type of volume. See the lsvolgrp command for information about the -type parameter.
Creating a volume group for System i systems

Complete this task to create volume groups for System i systems so that volumes can be assigned to the i5 fibre-channel adapters.
104
Use the mkvolgrp command to create a volume group that contains the volumes to be assigned to an i5 fibre-channel adapter. The following considerations determine how you will create your volume groups: v If you are using a multipath connection, a volume group is assigned to two or more i5 fibre-channel adapters. Each fibre-channel adapter provides one path to volumes in the volume group. v If you are using an external load source, you create a volume group that contains one volume. After a partition is initially loaded from the external load source, you can add more volumes to this volume group so that the i5/OS recognizes them and can use them. v If you do not use an external load source, you create a volume group that contains all the volumes that are assigned to an i5 fibre-channel adapter. You cannot specify more than 32 LUN volumes for each attachment to an i5 fibre-channel adapter. When you create a volume group for i5/OS, you should specify the -hosttype iSeries parameter as part of the mkvolgrp command. The -hosttype iSeries parameter saves some processing time because this parameter automatically supplies information that would have to be specified separately.For example, the i5/OS uses a logical blocksize of 520, and volumes that are created for i5/OS use a blocksize of 520 bytes. By specifying the -hosttype iSeries parameter,also you denote that the logical size of the blocks in the volumes is 520 bytes. Perform the following steps to create and view volume groups for System i systems: 1. Issue the mkvolgrp command to create a volume group. Enter the mkvolgrp command at the dscli command prompt with the following parameters and variables: Note: Repeat this step for each volume group that you want to create. The following two examples provide the commands that you can use to create volume groups depending on whether you use the external load source. The first example creates a volume group that contains one unprotected volume if you do use an external load source. (If you are using an external load source, you can initially only have one volume in the volume group.) The second example creates a volume group that contains all volumes if you do not use an external load source. Example 1 (using an external load source)
dscli>mkvolgrp -dev IBM.1750-13ABVDA -hosttype iSeries -volume 1000 blue Date/Time: July 5, 2005 11:57:50 PM GMT+01:00 IBM DSCLI Version: 5.0.4.32 DS: IBM.1750-13ABVDA CMUC00030I mkvolgrp: Volume group V14 successfully created.
Example 2 (not using an external load source)

dscli>mkvolgrp -dev IBM.1750-13ABVDA -hosttype iSeries -volume 1000-1002 blue Date/Time: July 5, 2005 11:57:50 PM GMT+01:00 IBM DSCLI Version: 5.0.4.32 DS: IBM.1750-13ABVDA CMUC00030I mkvolgrp: Volume group V14 successfully created.
Notes: a. The confirmation message for the end process shows that the created volume group is automatically assigned an ID that is different from the name of the volume group that you specify in the command. You will see the name that you assigned associated with
105
the volume group when you use the lsvolgrp and showvolgrp commands. However, if you want to work specifically with the volume group, you must reference the volume group ID. b. This volume group is also referred to as SCSI520-MASK. When an error message is displayed for the OS400 MASK, SCSI520-MASK is referenced instead. c. If you do not use an external load source, it is a good practice to create a volume group that contains all the volumes that will be assigned to the i5 fibre-channel adapter. d. System i only supports 32 device addresses per volume group. 2. Issue the lsvolgrp command to create a list of assigned volume group IDs. Enter the lsvolgrp command at the dscli command prompt with the following parameters and variables:
dscli>lsvolgrp -dev IBM.1750-13ABVDA -l
Notes: a. The lsvolgrp command with the -l parameter displays a report with the following three values: v Name (the unique name that you assigned to the volume group) v Volume group ID (the identification number of the volume group) v Type (the configured volume group type) b. You can narrow the scope of the report by requesting a specific type of volume. See the lsvolgrp command for information about the -type parameter. 3. Verify your host type information by issuing the lshosttype command using the following command format at the dscli command prompt:
dscli>lshosttype -type os400mask
This command displays a report like the following:

Name iSeries Profile IBM iSeries - os400 AddrDiscovery reportlun LBS 520
Note: You can obtain the same results if you use the -type os400all parameter.
Configuring fibre-channel I/O ports using the DS CLI

Complete this task to configure fibre-channel I/O ports using the DS command-line interface. Before you begin, you must have the command-line interface prompt, and you must be connected to a storage unit that will be used for open systems host system storage. In this process, you must designate the topology for the I/O port. The following three topology settings are available: fibre channel arbitrated loop (coded as fc-al in the setioport command) Enables the SCSI ULP with a FC-AL topology. The FC-AL topology does not support PPRC path I/O operations. SCSI-FCP (coded as scsi-fcp in the setioport command) Enables the SCSI ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are enabled for this setting.
106
Note: Designate this topology for System i systems using i5/OS level V5R3M5 and above. ficon (coded as ficon in the setioport command) Enables the FICON ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are not supported for FICON ULP. The storage unit supports the fibre-channel host adapter (HA) card type. For machine type 1750, one or two HA cards are installed in each of the two CEC assemblies. Use the lsioport and setioport commands to configure fibre-channel I/O ports. Each fibre-channel HA card contains four I/O ports. The storage image microcode automatically creates one I/O port to represent each HA card I/O port. The default fibre-channel I/O port settings enable SCSI-FCP identified access to fixed block volumes. You might have to modify the I/O port settings to enable SCSI FC-AL access to fixed block volumes. To configure the fibre-channel ports, perform the following steps: 1. View a list of fibre-channel port IDs by typing the following command format at the dscli command prompt:
dscli>lsioport -dev IBM.175075FA120 -l -type fc
A detailed report is displayed that lists the fibre-channel I/O ports. 2. Analyze the report and determine which I/O port IDs that you want to access the fixed block volumes. Configure a minimum of four I/O ports for SCSI host I/O operations. Select ports with physical locations on different host bus adapter (HA) cards. If possible, locate the HA cards in different I/O enclosures. 3. Set the I/O ports that you have identified to enable the FC-AL (fibre-channel arbitrated loop), SCSI-FCP, or FICON topology. The following example shows how to enable the FC-AL topology by typing the following command format at the dscli command prompt: Note: I/O ports are automatically set to the offline state and returned to the online state after configuration changes are applied.
dscli>setioport -dev IBM.175075FA120 -topology fc-al 0012 0013 0112 0113
4. Press Enter. A successful process returns a confirmation message indicating that the port IDs have been successfully configured.
Creating SCSI host port connections using DS CLI

Complete this task to create SCSI host port connections using the DS command-line interface. Before you begin, you must have the command-line interface prompt, and you must be connected to a storage unit that can be used for open systems host system storage. The 1750 machine type supports the identified access mode for SCSI host attachments, which requires that all SCSI host ports be identified to a storage unit. One SCSI host port connection must be created for each SCSI host port that accesses storage unit fixed block volumes. Use the lshosttype, mkhostconnect, and lshostconnect commands to create the SCSI host port connections.
107
A SCSI host port contains attributes that identify the following information: v SCSI host system type v Port profile v Port WWPN v Volume group ID that the port accesses v An array of storage unit I/O port IDs that the host port logs into for volume access v An attribute to indicate that all I/O ports can be used for volume access v Host port description v Port nickname There are two ways that you can approach this task: v Use the -hosttype parameter with the mkhostconnect command. Using the -hosttype parameter is the best solution for most users. v Use the mkhostconnect command with the -lbs, -addrdiscovery, and -profile parameters. Notes: 1. Specifying the -hosttype parameter automatically sets the -lbs, -addrdiscovery, and -profile values. 2. If you do not use the -hosttype parameter, you must issue the lsportprof command to ensure that you obtain the correct values to use with the -lbs, -addrdiscovery, and -profile parameters. 3. You cannot use the -hosttype parameter with these other parameters. The following task is described from the assumption that you have used the -hosttype parameter. To configure the SCSI host ports, perform the following steps: 1. Obtain your host type information by issuing the lshosttype command. Enter the lshosttype command at the dscli command prompt with the following parameters and variables:
dscli>lshosttype l -type volumeGroup_type
This command displays a report like the following:

Name pSeries Profile IBM pSeries AIX AddrDiscovery reportlun LBS 512 Description IBM pSeries, RS/6000 and RS/6000 SP Servers (AIX) IBM zSeries Servers (Linux) IBM iSeries Servers (System i)
zLinux iSeries (if os400all was specified)
IBM zSeries zLinux IBM iSeries os400
lunpolling reportlun
512 520
Note: Volume group type is one of the following designations (use a separate command for each choice): v ficonall v scsiall
108
v v v v
scsimask scsimap256 os400all os400mask
The same results are displayed when you specify os400all or os400mask or when you specify scsiall and scsimask or scsimap256. 2. Create SCSI host ports by issuing the mkhostconnect command. Enter the mkhostconnect command at the dscli command prompt with the following parameters and variables:
dscli>mkhostconnect -dev storage_image_ID -wwname wwpn -hosttype host_type -volgrp volume_group_ID -ioport port_ID host_name
Notes: a. The -wwname parameter specifies the 16-character worldwide name that is assigned to the host system fibre-channel adapter port. This WWPN value is validated each time that the host system port logs into an I/O port. b. The -hosttype parameter specifies fibre-channel communications layer characteristics that might be unique according to the host system manufacturer, operating system, or version of the system. Typical specifications are iSeries, pSeries, an so on. c. The -volgrp parameter specifies the volume group ID that this host port can access. Host port objects might be created prior to creating volume groups, in which case you must use the chhostconnect command to add volume group ID assignments at a later time. d. The -ioport all specifies SCSI host port (WWPN) access into all IO ports that are configured for the FC-AL or SCSI-FCP topology. e. host_name specifies the SCSI host system nickname that you have assigned. 3. Repeat Step 2 for each SCSI host system port that will access LUN volumes. 4. Verify that all SCSI host ports have been configured and that they are recognized by the storage unit according to your specifications by issuing the lshostconnect command with the -l parameter.
Configuring new count key data storage using DS CLI

This section describes how to configure new count key data (CKD) storage within your storage unit for a zSeries host system. Before you begin, you must be logged into the DS CLI application in interactive command mode. You must also be connected to a storage unit that is used for zSeries systems host storage. Configuring CKD storage involves two basic processes: the creation of the CKD storage configuration and the configuration of the storage unit I/O ports for zSeries host system attachment. These two basic processes can be performed in the reverse order, but it is better to create storage configurations first. Creating the storage configuration first creates the media to back up configuration data that is not related specifically to the storage configuration. Configuring new CKD storage involves the following processes:
109
Creating CKD extent pools Creating arrays Creating and associating ranks with extent pools Creating logical control units Creating CKD volumes Creating CKD volume groups (system generated). The internal microcode automatically creates the CKD FICON All volume group ID (V10) and automatically assigns all CKD base and alias volumes to this volume group. This volume group ID (V10) is automatically assigned to storage unit I/O fibre channel ports that are configured for FICON I/O operations. v Configuring fibre-channel I/O ports v v v v v v
Creating count key data extent pools using the DS CLI

Complete this task to create CKD volume extent pools. This is the first step in configuring new count key data storage. You can use the DS CLI commands to create extent pools for CKD volumes. Creating the extent pools before the arrays and ranks saves a processing step. When you create the new ranks, you can assign them to existing extent pools. Otherwise, you must modify each rank object to complete the extent pool ID assignment after the extent pools have been defined. Each extent pool is defined with the rank group of 0 or 1 and a storage type of ckd. At a minimum, you must define one extent pool for each rank group and storage type combination. This means that you must make a minimum of two extent pools for a storage unit that contains CKD storage: one CKD extent pool per rank group. Extent pools that are defined for rank group 0 or 1 are assigned an even- or odd-numbered extent pool ID, respectively. Even-numbered extent pools are managed by storage server ID 0. Odd-numbered extent pools are managed by storage server ID 1. Each rank group is assigned to one extent pool; therefore, storage server workload is affected by the rank assignments to even- and odd-numbered extent pool IDs. It is better to evenly distribute rank and extent pool allocations in order to keep the storage server workloads balanced. Notes: 1. You can create more than the minimum number of extent pools. For example, you can define unique extent pools for each RAID type (5 or 10) that is configured in a storage image. Or, you can define and name extent pools according to the host system attachments that access the volumes that are created from extent pool extents. 2. You can have the same number of extent pools as ranks. Use the lsextpool and mkextpool commands to create the CKD extent pools. You must be logged into the DS CLI application and connected to the storage unit that will be used for your zSeries host system. To make your extent pools, perform the following steps: 1. Find defined CKD extent pools by issuing the lsextpool command to display a list of the existing CKD extent pools. Type the following command at the dscli command prompt: dscli> lsextpool -dev IBM.1750-75FA120 -stgtype ckd
110
2. Analyze the extent pool listing for the following information. v Does the minimum set of extent pools exist? There must be one extent pool for rank group 0 and one extent pool for rank group 1. Note: If this is the first time that the extent pools are created, the minimum number of extent pools does not already exist. v Does each extent pool have a rank group that is assigned to it and are they balanced? If this is the first time, there will be no rank assignments. v Are additional extent pools needed? 3. Make your extent pools by issuing the mkextpool command. (A minimum of two extent pools must be created. One for rank group 0 and one for rank group 1.) Type the following command at the dscli command prompt:
dscli>mkextpool -dev IBM.1750-68FA120 rankgrp 0 -stgtype ckd extent_pool_name dscli>mkextpool -dev IBM.1750-68FA120 rankgrp 1 -stgtype ckd extent_pool_name
The extent_pool_name parameter is required with the mkextpool command. The extent pool name is a unique name that you assign to each extent pool and it cannot be longer than 16 characters. Make additional extent pools for each of the following conditions: v Each RAID type (5 or 10) v Each disk drive module (DDM) size v Each CKD volume type (3380, 3390) v Each logical control unit (LCU) address group 4. Press Enter. A successful process displays the following message: Note: The unique name that you assigned to the extent pool does not display in the process message. However, when you issue the lsextpool command, the extent pool name is displayed.
5. Repeat Step 2 for each extent pool that you want to create. Try to evenly distribute rank and extent pool allocations in order to keep the storage server workloads balanced. 6. Verify the extent pool assignments by issuing the lsextpool command when you are done making the extent pools. Use the -l parameter to display a full report for the extent pools that are assigned to the storage unit. Type the following command at the dscli command prompt: dscli> lsextpool dev IBM.1750-75FA120 -l You might want to print this report because this list is used later during the process of creating CKD volumes.
Creating arrays for CKD volumes using the DS CLI

Complete this task to create arrays for CKD volumes using the DS CLI commands. The machine type 1750 must contain at least one storage enclosure, with a minimum of four DDMs. The DDMs of a storage enclosure are partitioned into array sites. A machine type 1750 array site consists of four DDMs in one storage enclosure of a storage
111
enclosure pair, with two to eight (four DDM) array sites per storage enclosure pair. All array sites of a storage enclosure pair have identical capacity, rpm, and interface characteristics, and an interface to a common DA pair. The creation of arrays is based on the array sites that are associated with the storage unit. You must make an array from 1 or 2 array sites. An array inherits the characteristics of its parent array sites, and is given a RAID type attribute (5 or 10). A 1750 Array object of RAID type 5 or 10 is made from one or two (4 DDMs) array sites. Note: The array status is unassigned until the array is assigned to a rank. Use the lsarraysite and mkarray commands to create the arrays. You must be logged into the DS CLI application and connected to the storage unit that will be used for open systems host system storage. Perform the following steps to create arrays for a CKD volume configuration: 1. Issue the lsarraysite command to find the unassigned array sites. Enter the lsarraysite command at the dscli command prompt with the following parameters and variables:
dscli>lsarraysite -dev storage_image_ID -state unassigned
Note: If this is your first time creating volumes, you will see all the arrays with a state of unassigned. 2. Press Enter. A report of unassigned array sites is displayed. Use the list to identify unassigned array site capacity, rpm, and device adapter (DA) pair attributes. Record the RAID type for each array site. 3. Issue the mkarray command to create an array from each site with the status unassigned. Enter the mkarray command at the dscli command prompt with the following parameters and variables:
dscli>mkarray -dev storage_image_ID -raidtype [5 | 10] -arsite array_site
Repeat this command until all unassigned array sites have been assigned to an array. Notes: a. You can specify one or two array sites for RAID types 5 and 10. If there are two array sites, both sites must be associated with a common DA pair ID. Two array sites must be separated by commas with no blank space in between. Example: S10,S11. b. The new array site inherits the capacity, rpm, interface, and DA pair characteristics of its parent array sites. The state of the array is unassigned until it is assigned to a rank.
Creating a rank for CKD volumes using the DS CLI

Complete this task to create a rank for a CKD volume. A rank is a logically contiguous storage space that is made up of one or more arrays. You want to assign a rank to every unassigned array. A rank inherits the characteristics, including RAID type, of its parent array and is given a storage type attribute FB (fixed block) or CKD (count key data). The rank configuration state is unassigned until it is assigned to an extent pool. An unassigned rank is not associated with either rank group 0 or 1. Any unassigned rank can be assigned to an extent pool that is associated with either rank group 0 or 1.
112
Note: You can assign a rank to an unassigned array and also assign the rank to an extent pool at the same time if you have already created the extent pools and the arrays. Creating extent pools first saves a step in the configuration. Use the lsarray, mkrank, and lsrank commands to assign a rank to each unassigned array. You must be logged into the DS CLI application and be connected to the storage unit that will be used for open systems host system storage. To make ranks, perform the following steps: 1. Issue the lsarray command to ensure you have a list of the unassigned arrays for which ranks must be assigned. Enter the lsarray command at the dscli command prompt with the following parameters and variables:
2. Issue the mkrank command to assign a rank to rank group 0 or 1 according to the rank group number of the assigned extent pool ID. Enter the mkrank command at the dscli command prompt with the following parameters and variables:
dscli>mkrank -dev IBM.1750-68FA120 -array A44 -stgtype ckd -extpool P1
Notes: a. You can specify either the -wait or the -extpool parameter when you use the mkrank command. Either of these parameters allows you to be notified if the rank configuration has failed for any reason. b. Be aware that when you use the -wait parameter, you cannot issue any other commands until the entire transaction has processed. 3. Press Enter to create the ranks. The process of making the rank involves formatting drives. It can take a little time before the process finishes. To check on the process, issue the lsrank command from a different DS CLI session. A successful process generates the following type of message:
4. Repeat Step 2 and step 3 until all unassigned arrays are assigned a rank and an extent pool. 5. Issue the lsrank command to verify that ranks and extent pools have been assigned. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
6. Press Enter. A report of the rank assignments for your entire storage unit is displayed.
Creating logical control units for CKD volumes using DS CLI

The logical control unit (LCU) is the S/390 and zSeries host equivalent of the logical subsystem (LSS) for open systems hosts. The LCU must be defined (created) before CKD logical volumes can be created. The DS6000 has a 16 384 volume address space that is partitioned into 64 logical subsystem (LSS) units, where each LSS contains 256 logical volume numbers. The 64 LSS units are assigned to one of 4 address groups, where each address group
113
contains 16 LSSs, or 4096 volume addresses. All of the LSSs in one address group must be of the same type (CKD or fixed block). Typically, LCUs are created in groups of 16, beginning at LSS address Xx0. Use the lsaddressgrp, mklcu, and lslcu commands to create the LCU type logical subsystems. You must be logged into the DS CLI application and connected to the storage unit that will be used for open systems host system storage. To create LCUs, perform the following steps: 1. Find unassigned and available address groups by issuing the lsaddressgrp command. To use the lsaddressgrp command, type the following at the dscli command prompt:
dscli>lsaddressgrp -dev IBM.1750-75FA120
This command displays a report on the status of the address groups within your storage unit. 2. Analyze the report to identify all of the address groups that are available to be defined. Use the following criteria: v If the list is empty, all of the address groups are available to be defined. v A defined address group with the storage type fb (fixed block) is not available to be defined. v A defined address group with the storage type ckd and with fewer than 16 LSSs is available for LCU definition. v If you are using an undefined address group to make new LCUs, select the lowest numbered address group that is not defined. v If you are defining a new LCU in an existing CKD address group, use the lslcu command to identify LCUs that are already defined in the target address group. 3. Make the LCU logical subsystem objects by issuing the mklcu command. Type the command using the following format at the dscli command prompt:
dscli>mklcu dev IBM.1750-75FA120 -qty 16 -id 00 -ss 0010 -lcutype 3390-3
In this example, the values specify the following: qty Specifies the number of LCU IDs to be created. id Specifies the LCU ID to be created, or the first LCU ID in a sequence of LCU IDs to be created. ss Specifies the subsystem ID that you have assigned. If multiple LCU IDs are being created, then the SSID value increments for each additional LCU ID that is created. If 16 LCUs are created, starting with SSID 0x10, then the SSID values are 0x0010 0x001F. lcutype Specifies the type of LCU to be created. You can specify the following types: v 3390-3 v 3990-tp v 3990-6 v bs2000
114
4. Press Enter. A successful process displays a confirmation message listing each LCU ID number that has been successfully created. 5. Verify that the LCUs are recognized in the storage unit by issuing the lslcu command at the dscli command prompt as follows:
dscli>lslcu -dev IBM.1750-75FA120 -l
Using the -l parameter displays a more detailed report for each LCU that is associated with your storage unit.
Creating count key data volumes using the DS CLI

Complete this task to create count key data (CKD) volumes. A logical volume consists of one or more data extents that are allocated from a single extent pool. The volume data type is inherited from the extent pool extent storage type (fixed block or CKD) characteristic. When a CKD volume is created, volume attributes are further defined by a base or alias volume type, 3390 or 3380 volume cylinder type, and volume capacity in cylinders. These volume attributes characterize the volume to the host system that will eventually access the volume. Each volume is assigned a volume ID, which is the volume address within the 64 KB address space. Host access to a volume is enabled when the volume ID is assigned to a volume group; however, CKD volumes are automatically assigned to the volume group CKD FICON/ESCON All (ID V10). Perform the following steps to create your CKD volumes: 1. View your list of CKD extent pool IDs and determine which extent pool IDs that you want to use as the source for the CKD volumes to be created. You obtained this list when you first created your extent pools. If this list is not available, you can issue the lsextpool command to obtain the list of extent pool IDs. Extent pool attributes determine the size and quantity of volumes that can be created. The extent pool ID (even/odd) indicates the storage server (0|1), which dictates that the logical control unit (LCU) ID component of the volume ID must be an even or an odd number. 2. Issue the mkckdvol command to make 128 base volumes for each LCU. Enter the mkckdvol command at the dscli command prompt with the following parameters and variables:
dscli>mkckdvol dev IBM.1750-68FA120 -extpool p1 cap 3339 name finance#d 0000-007F
The following considerations affect the command example in this step: v The -extpool parameter identifies a CKD extent pool that contains available data extents. The -cap parameter specifies the quantity of CKD cylinders that are allocated to this volume. v The -name parameter allows you to assign an easy-to-use label or nickname to the volume. The volume name parameter can include a wild card (#d or #h) that inserts a decimal or hexadecimal volume ID value into the volume name. v Note: The decimal designation does not apply to the volume ID number or the number of volumes that were created by the command. It only applies to the unique name that you have assigned to the volume. When you process the mkckdvol command, the volume name that
115
you have assigned does not appear in the confirmation message. To view the volume name that you have assigned, issue the lsckdvol or showckdvol command. v Volume ID 0000 - 007F specifies 128 volumes, starting at CKD address group (0), LCU ID (00), and volume number (00). You must specify volume IDs that have not been previously defined as CKD or fixed block volumes. 3. Press Enter to create the volumes. A confirmation message is displayed that lists the successful creation of each volume. 4. Repeat Steps 2 and 3 until all required logical volumes for all LCUs have been created. 5. Issue the mkaliasvol command to make 128 alias volumes for each LCU. Enter the mkaliasvol command at the dscli command prompt with the following parameters and variables:
dscli>mkaliasvol dev IBM.1750-68FA120 base 0000-004F -order decrement -qty 2 00FF
Consider the following conditions with regard to the command example in this step: v The -base 0000 - 004F parameter specifies that alias volumes are assigned to existing base volume IDs 0000 - 004F. Base and alias volumes must be associated with a common LCU ID. v The -order parameter specifies the order in which alias volume IDs are assigned. v The -qty parameter specifies the number of alias volumes that are assigned to each base volume. v The volume ID (00FF) parameter specifies that the alias volumes are assigned, starting at a CKD address group (0), LCU ID (00) and volume number (FF). You are responsible for specifying the volume ID values that have not been previously defined as CKD or fixed block volume types. As a result, alias volumes 00FF and 00FE are created for base volume 0000, 00FD and 00FC for 0001, and so on. 6. Repeat Step 5 until you have defined all required logical volumes for all the LCUs. 7. Press Enter to create the alias volumes. A confirmation message is displayed that lists the successful creation of each volume. 8. Issue the lsckdvol command to display a report that you can use to confirm the status of your CKD volumes. Enter the lsckdvol command at the dscli command prompt with the following parameters and variables:
dscli>lsckdvol -dev IBM.1750-6800861 -l 1410
Note: It is possible that the report will display that there was a configuration error that is associated with one or more of your mkckdvol transactions. In the majority of instances, the only way to correct this error is to issue the rmckdvol command.
Correcting a CKD volume configuration error

Complete this task to correct a count key data (CKD) volume configuration error. There might be occasions when you are using the mkckdvol command to create CKD volumes, but the transaction fails. You might not be aware of the failure until you run the lsckdvol or the showckdvol command to check the status of the volumes that you have created.
116
The lsckdvol or the showckdvol commands display reports that includes a configstate category. The configuration state category reports on the current state of the rank. One of the configuration state codes is configuration error. A status of configuration error specifies that the configuration process did not complete successfully. This state reflects an internal error condition and is not an indication that there was a user input error. You might want to gather additional information about what caused the error, which can help you determine how to correct it. Generally, to correct this error state, you must delete the designated volume configuration and submit a new transaction request. Perform the following steps to obtain additional information about the configuration error and to correct this error condition. 1. Add the -v (verbose) command flag to your mkckdvol command and reissue the mkckdvol command for the transactions that show there is a configuration error. Note: You can also turn on the verbose mode in your profile file and reissue the command. If you designate the verbose mode, the display of extra output includes the error code that is generated when the create CKD volume transaction fails. 2. Issue the rmckdvol command to delete the designated volume configurations if you do not want to obtain additional information about what caused the configuration error. Note: In the majority of instances, this is the only method for correcting a configuration error.
Configuring fibre-channel I/O ports using the DS CLI

Complete this task to configure fibre-channel I/O ports using the DS command-line interface. Before you begin, you must have the command-line interface prompt, and you must be connected to a storage unit that will be used for open systems host system storage. In this process, you must designate the topology for the I/O port. The following three topology settings are available: fibre channel arbitrated loop (coded as fc-al in the setioport command) Enables the SCSI ULP with a FC-AL topology. The FC-AL topology does not support PPRC path I/O operations. SCSI-FCP (coded as scsi-fcp in the setioport command) Enables the SCSI ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are enabled for this setting. Note: Designate this topology for System i systems using i5/OS level V5R3M5 and above. ficon (coded as ficon in the setioport command) Enables the FICON ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are not supported for FICON ULP.
117
The storage unit supports the fibre-channel host adapter (HA) card type. For machine type 1750, one or two HA cards are installed in each of the two CEC assemblies. Use the lsioport and setioport commands to configure fibre-channel I/O ports. Each fibre-channel HA card contains four I/O ports. The storage image microcode automatically creates one I/O port to represent each HA card I/O port. The default fibre-channel I/O port settings enable SCSI-FCP identified access to fixed block volumes. You might have to modify the I/O port settings to enable SCSI FC-AL access to fixed block volumes. To configure the fibre-channel ports, perform the following steps: 1. View a list of fibre-channel port IDs by typing the following command format at the dscli command prompt:
dscli>lsioport -dev IBM.175075FA120 -l -type fc
A detailed report is displayed that lists the fibre-channel I/O ports. 2. Analyze the report and determine which I/O port IDs that you want to access the fixed block volumes. Configure a minimum of four I/O ports for SCSI host I/O operations. Select ports with physical locations on different host bus adapter (HA) cards. If possible, locate the HA cards in different I/O enclosures. 3. Set the I/O ports that you have identified to enable the FC-AL (fibre-channel arbitrated loop), SCSI-FCP, or FICON topology. The following example shows how to enable the FC-AL topology by typing the following command format at the dscli command prompt: Note: I/O ports are automatically set to the offline state and returned to the online state after configuration changes are applied.
dscli>setioport -dev IBM.175075FA120 -topology fc-al 0012 0013 0112 0113
4. Press Enter. A successful process returns a confirmation message indicating that the port IDs have been successfully configured.
Managing your logical storage configuration

The topics in this section provide task information that are related to working with configuration files after the initial creation of the configuration. This information is for working with the commands associated with the DS CLI application.
Using DS CLI commands on i5/OS

Complete this task to use DS CLI commands from the green screen interface on i5/OS. Before you can use the DS CLI on i5/OS, ensure that the following conditions have been met: v You have installed the DS CLI code on i5/OS. The DS CLI is installed on the i5/OS integrated file system (IFS) in the following two places: IFS directory IBM/DSCLI, which contains the profiles, executable files, and readme files. The library QDSCLI, which contains executable code.
118
v You have added library QDSCLI to the i5/OS library list by performing the following process: 1. Enter WRKSYSVAL QUSRLIBL at the i5/OS command line. 2. Press Enter and select option number 2. 3. Add the QDSCLI library into the lib list. v You have completed the initial configuration from the server from which you did your installation. For example, you have activated your licenses, created your arrays, ranks, extent pools, host attachments, and logical volumes on the DS6000. v You have configured the DS CLI profile as appropriate. To edit the profile file, perform the following: 1. Enter EDTF /ibm/dscli/profile/dscli.profile at the i5/OS command line. 2. Update the following two lines when the profile file displays: HMC IP address field and remove the comment from this command line Dev ID field and remove the comment from this command line v You have performed an IPL to System i. Assuming that you have met the previous conditions, perform the following steps using DS CLI on i5/OS to process storage configuration and Copy Services functions on the DS6000: 1. From the i5/OS main menu, enter DSCLI at the prompt to start DS CLI on i5/OS and press Enter.
MAIN OS/400 Main Menu System: IBMSYSTEM Select one of the following: 1. User tasks 2. Office tasks 3. General system tasks 4. Files, libraries, and folders 5. Programming 6. Communications 7. Define or change the system 8. Problem handling 9. Display a menu 10. Information Assistant options 11. iSeries Access tasks 90. Sign off Selection or command ===> dscli F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant F23=Set initial menu
2. The DSCLI displays the following screen where you can specify a DS CLI script for DS CLI commands and a DS CLI profile. In this example, a default profile is specified. The profile is not configured so the value of *DEFAULT is used. If you are not using a script, specify *None and press Enter. After you press Enter, more fields appear in the screen as shown in step 3 on page 120.
119
Run DSCLI Functions (DSCLI) Type choices, press Enter. Script: *NONE or name . . . . . Profile . . . . . . . . . . . . F3=Exit F4=Prompt F24=More keys F5=Refresh *NONE___ *DEFAULT F12=Cancel F13=How to use this display
3. Specify the values, as appropriate and press Enter.

Run DSCLI Functions (DSCLI) Type choices, press Enter. Script: *NONE or name . . . . . > *NONE Profile . . . . . . . . . . . . HMC1 . . . . HMC2 . . . . User . . . . Password . . Install Path DSCLI CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *DEFAULT *PROFILE *PROFILE admin /ibm/dscli *int Bottom F3=Exit F4=Prompt F24=More keys F5=Refresh F12=Cancel F13=How to use this display
Consider the following fields and values: v If you are using a DS CLI script for DS CLI commands, enter the name in the Script field. Otherwise, specify *None. v If you use default profile, leave the value *DEFAULT in the field Profile. If you use another file as a profile, specify the name and path of this file in the field Profile. v Enter the hardware management console (also known as the management console) user in the User field. Typically, it is Admin. v Enter the password of the user (typically the administrators password). v Enter *INT (for interactive session) in the DSCLI CMD field. The screen shown in step 4 displays. 4. Specify the DS CLI commands to invoke storage configuration or Copy Services functions.
Date/Time: July 8, 2005 2:55:20 PM MST IBM DSCLI Version: 5.0.4.32 DS: IBM.1750-13ABVDA
dscli> ===> F3=Exit F6=Print F21=CL command entry
F9=Retrieve
F12=Exit F13=Clear F17=Top F18=Bottom
120
Modifying an extent pool

Complete this task to modify the properties of an extent pool using the DS CLI application. Use the chextpool command to modify the properties of an extent pool. You can modify the following extent pool properties: v name of the extent pool v extent limit on or off indicator v extent limit percentage v extent threshold percentage Perform the following steps to modify the extent pool properties. 1. Issue the lsextpool command to generate a report that identifies the status of your extent pools by storage type (fixed block or count key data). Enter the lsextpool command at the dscli command prompt with the following parameters and variables:
dscli>lsextpool -dev storage_image_ID -l -stgtype (fb | ckd)
Note: The -stgtype parameter must be designated as either fb (fixed block) or ckd (count key data). The storage type allows you to limit the list of extent pools for issues such as which ones to rename or to change the limit or threshold percentages. 2. Issue the chextpool command to change the name that is assigned to the extent pool or to change the percentages that are allocated for extent and threshold limits. Enter the chextpool command at the dscli command prompt with the following parameters and variables:
dscli>chextpool -dev storage_image_ID -name new_extent_pool_name -extentlimit [on | off] -limit extent_limit_percentage -threshold extent_threshold_percentage -extentpool_ID
Notes: a. The new extent pool name can include up to sixteen characters. b. The -extentpool_ID parameter is required but does not need to be specified as a separate entry. You can add it to the storage_image_ID parameter. For example: IBM.1750-68FA120/P21, with P21 being the extent pool ID. Extent pool IDs are specified as 4-digit values with no leading zeros, and they are preceded by the letter P. c. The unique name that you assigned to the extent pool does not display in the output message of the chextpool command. However, when you issue the lsextpool command, the extent pool name is displayed. 3. Issue the lsextpool command to verify that your changes have been processed.
Viewing extent pool status

Complete this task to display a list of extent pools in a storage unit and status information on each extent pool in the list. Issue the lsextpool command if you want to view the unique names that you have assigned to your extent pools or if you want to view general status information about the extent pools in your storage unit. If you want to view the details or properties that are associated with your extent pools or if you want to view the performance metrics, issue the showextpool command.
121
Perform the following step to display a list of extent pools and their status in a storage unit. Issue the lsextpool command to display the extent pool list and status information. Enter the lsextpool command at the dscli command line prompt with the following parameters and variables:
dscli>lsextpool -dev storage_image_ID -l
Notes: 1. Use the -l parameter if you want to see the list and status for all the extent pools (fixed block and CKD) in your storage unit. A full report is displayed. 2. Use the -s parameter if you just want to see only a list of the extent pools in your storage unit. No additional information is provided.
Viewing extent pool properties and performance metrics

Complete this task to display the detailed properties for the list of extent pools in a storage unit and to view the performance metrics status information on each extent pool in the list. You must know and use an extent pool ID that resides in your storage unit. You can obtain these IDs by issuing the lsextpool command. Issue the showextpool command when you want to view the details of the properties that are associated with an extent pool or when you want to view the performance metrics for an extent pool in your storage unit. Perform the following steps to display the detailed properties of an extent pool or to display the performance metrics of an extent pool. 1. (For detailed properties information) Issue the showextpool command. Enter the showextpool command at the dscli command-line prompt with the following parameters and variables:
dscli>showextpool -dev storage_image_ID extentpool_ID
2. (For performance metrics information) Issue the showextpool command. Enter the showextpool at the dscli command-line prompt with the following parameters and variables:
dscli>showextpool -dev storage_image_ID -metrics extentpool_ID
Notes: a. All performance metrics are an accumulation since the most recent counter wrap or counter reset. b. The extent pool performance counters are reset on the following occurrences: v When the storage unit is turned on. v When a server has failed, and the failover and failback sequence is performed.
Deleting extent pools from a storage configuration

Complete this task to remove one or more extent pools from a storage configuration.
122
When you are using the DS CLI to delete extent pools as part of a storage configuration deletion, the following sequential deletions must have already occurred: v The volumes associated with the extent pool must be removed. v (CKD volume configuration only) The logical control units (LCUs) that are associated with the extent pool must be removed. v The ranks that are assigned to the extent pool must be unassigned or removed. v The arrays that are assigned to the extent pool must be removed. To delete an extent pool or a number of extent pools, you must first generate a list of extent pool IDs by storage type (fixed block or CKD) by issuing the lsextpool command. After you determine which extent pools can be deleted, you can issue the rmextpool command that designates the extent pools that you want to delete. Perform the following steps to delete one or more extent pools from a fixed block volume configuration. 1. Issue the lsextpool command to display a list of extent pools. Ensure that you designate the storage type within your command parameters. Enter the lsextpool command at the dscli command prompt with the following parameters and variables:
dscli>lsextpool -dev storage_image_ID -l -stgtype [fb | ckd]
2. Analyze the list and determine which extent pools can be deleted. 3. Issue the rmextpool command to delete the designated extent pools. Enter the rmextpool command at the dscli command prompt with the following parameters and variables:
dscli>rmextpool -dev storage_image_ID extentpool_ID
Note: If you are deleting several extent pools, you can add the -quiet parameter to your command. This parameter turns off the confirmation message that is generated for each deletion transaction. 4. Issue the lsextpool command after the deletion processing has completed to verify that the extent pools have been deleted.
Viewing the array disk drive module status

Complete this task to view the status of an array disk drive module (DDM) using DS CLI commands. The machine type 1750 contains at least one storage enclosure, with a minimum of four DDMs. The DDMs of a storage enclosure are partitioned into array sites. A machine type 1750 array site consists of four DDMs in one storage enclosure of a storage enclosure pair, with two-to-eight (four DDM) array sites per storage enclosure pair. All array sites of a storage enclosure pair have identical capacity, rpm, and interface characteristics, and an interface to a common DA pair. The DDMs of a storage enclosure are partitioned into array sites. The creation of arrays is based on the array sites that are associated with the storage unit. Before and after creating an array you might want to check on the status of the DDMs. Perform the following steps to view the DDM status:
123
1. Issue the lsddm command to obtain a list and status of the DDMs currently associated with the storage unit. Enter the lsddm command at the dscli command prompt with the following parameters and variables:
dscli>lsddm -l storage_image_ID
2. Issue the showarraysite command after you have created an array using the DDMs. Enter the showarraysite command at the dscli command prompt with the following parameters and variables:
dscli>showarraysite storage_image_ID -fullid site_ID
Notes: a. The storage image ID is optional. You do not have to specify it but, if you choose not to use it, you need to provide a fully qualified site_ID which includes the manufacture, model type, and serial number information. b. The site-ID parameter is a four-digit number preceded by the letter S with no leading zeros. c. The -showarraysite command provides the following DDM information that is associated with the DDM after the array has been created: v DDM serial number v Spares - Identifies, if any, the number of spare DDMs that are allocated from the array site. v Data DDM - Specifies the number of data DDMs. This value is based on the number of DDMs minus the number of spares.
Viewing array status

Complete this task to view the status of all arrays that are associated with a storage unit using DS CLI commands. The steps in this task presume that you have already created your arrays from the array sites. The creation of arrays is based on the array sites that are associated with the storage unit. After you have created your arrays, there might be times when you want to view the status of the array sites and the associated arrays. Perform the following steps to view the status of all the array sites and arrays that are associated with the storage unit. 1. Issue the lsarraysite command to generate a list of all the array sites and their status. Enter the lsarraysite command at the dscli command prompt with the following parameters and variables:
dscli>lsarraysite -dev storage_image_ID -l
The state column of the report might be of interest as it specifies the following state of the array site and conditions that require attention: v Assigned - The array site has been defined as an array. v Unassigned - The array site is available to be defined as an array. v Unavailable - Specifies that the designated array site is unassigned and at least one disk is not in the normal state. Also, the array site is not in the initializing state. v Initializing - Specifies that the array site is unassigned and all disks are either in the normal or initializing state. Also, at least one disk is in the initializing state.
124
2. Issue the lsarray command to generate a list of all the arrays and their status. Enter the lsarray command at the dscli command prompt with the following parameters and variables:
dscli>lsarray -dev storage_image_ID -l
Note: You might want to analyze the state and data column information for the arrays. Some of the reported conditions require further action. See the lsarray command for additional information.
Viewing properties for one array

Complete this task to view the detailed properties of one array and the array site that is associated with a storage unit using DS CLI commands. The steps in this task presume that you have created your arrays. The creation of arrays is based on the array sites that are associated with the storage unit. After you have created your arrays, there might be times when you want to view the status of an array site and the associated array. Note: For your 1750 machine type, you might have created your array from one or two array sites. An array inherits the characteristics of its parent array sites and is given a RAID type attribute (5 or 10). Perform the following steps to view the status of the array site or sites and the array that is associated with the storage unit. 1. Issue the showarraysite command to generate a report that displays the array site or sites and their status. Enter the showarraysite command at the dscli command prompt with the following parameters and variables:
dscli>showarraysite -dev storage_image_ID site_ID
Notes: a. The site ID is a four-digit number that is preceded by the letter S with no leading zeros. b. The site ID does not specify a physical location. It is, however, an identifier for the array site ID. c. The array site state shows a value of assigned if you have created the array. 2. Issue the showarray command to generate the properties report for the specified array. Enter the showarray command at the dscli command prompt with the following parameters and variables:
dscli>showarray -dev storage_image_ID array_ID
Removing arrays from a storage configuration or a rank assignment

Complete this task to remove an array or a range of arrays from a storage configuration using the DS CLI. When the array or arrays are deleted as part of deleting a storage configuration and you are using DS CLI to delete the configuration, the following sequential deletions must have already occurred: v Host access to the volumes of the configuration must have been removed. (Does not apply to a CKD configuration.)
125
v The associated volume groups must have been removed. (Does not apply to a CKD configuration.) v The fixed block or CKD volumes that are part of the configuration must have been removed. v The LCUs (if you are removing a CKD configuration) must have been removed. v The ranks must have been removed. There might be times when you want to remove arrays from a storage configuration or from a rank assignment. You can avoid errors when you use the DS CLI by ensuring that the arrays are ready for removal. The arrays must have a status of unassigned before they can be removed or be reassigned to another rank. When you remove a rank using the DS CLI, there is an extended period of processing because the array is unassigned from the rank and the drives are formatted. During this processing, the array is still shown with a status of assigned, even though you have received a confirmation message that the rank has been removed. The status for the array does not change to unassigned until after the array has been formatted. Perform the following steps to remove arrays from a storage configuration or a rank: 1. Issue the lsarray command to obtain a list of array IDs to be removed. Enter the lsarray command at the dscli command prompt with the following parameters and variables:
dscli>lsarray -dev storage_image_ID -state unassigned
Notes: a. You might have to issue the lsarray command several times before you observe that the arrays are in a state that allows them to be removed or reassigned. b. Specify the -state unassigned parameter to narrow your list to just the array IDs that are not assigned to a rank ID. c. If you issue the lsarray command without using the -state unassigned parameter, you might see a list of arrays that have a state of unavailable. This is generally a good indication that the ranks have not been removed and that the arrays are still formatting. You must wait until the ranks have been removed and the arrays have been formatted before you can proceed. d. Proceed to the next step (remove arrays) only after all the arrays that you want to remove or reassign are displayed with a state of unassigned. 2. Issue the rmarray command to delete the unassigned arrays so that the array sites can be redefined as new arrays. Enter the rmarray command at the dscli command prompt with the following parameters and variables:
dscli>rmarray -dev storage_image_ID array_ID
Notes: a. You can remove one or many arrays as long as you designate the range of arrays using a hyphen and separate each range of arrays or a single array with a space before the next array designation. For example, A44-A48 A51 designates a range of arrays and a single array.
126
b. If you are removing several arrays, you might want to designate the -quiet parameter in your command. This parameter turns off the deletion confirmation message that is generated after each array is deleted.
Adding a rank to an extent pool

Complete this task to add an unassigned rank to an extent pool using the DS CLI. To add a rank to an extent pool, the rank must have a data state designation of normal and a configuration state designation of unassigned. A rank is a logically contiguous storage space made up of one or more arrays. An unassigned rank is not associated with either rank group 0 or 1. Any unassigned rank can be assigned to an extent pool that is associated with either rank group 0 or 1. Over time, you might remove a rank from an array and extent pool without deleting the rank. When a rank is removed and not deleted, it retains its storage type designation of fixed block or CKD. This designation cannot be changed. Perform the following steps to add a rank to an extent pool: 1. Issue the lsrank command to generate a report that lists the status of the ranks that are associated with the storage unit. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
dscli>lsrank -dev storage_unit_ID -l -state unassigned
Notes: a. The report that is generated by this example provides a list of all unassigned ranks; however, the storage type is mixed between fixed block and CKD. b. You can narrow your report information to a specific storage type by adding the -stgtype [fb | ckd] parameter to your command. 2. Issue the chrank command to add (reassign) a rank or ranks to an extent pool. Enter the chrank command at the dscli command prompt with the following parameters and variables:
dscli>chrank -dev storage_image_ID -extpool extentpool_ID rank_ID
Notes: a. The rank ID is a 4-digit number with the prefix R and with no leading zeros. You can specify a range of rank IDs by using a hyphen between the beginning and ending values of the range. For example: R102-R105 b. You can specify multiple rank IDs or rank ID ranges, but you must leave a space between each designation. For example: R102 R105 R107-R109
Modifying a rank
Complete this task to modify a rank using the DS CLI You can perform the following modifications to a rank using the DS CLI commands: v Designate that the rank be given a reserved status. v Release a rank from a reserved status.
127
v Designate that the rank be removed (but not deleted) from its current extent pool and array assignment and be designated as unassigned. v Designate that the rank be assigned to an extent pool. Perform the following steps to modify a rank using DS CLI commands: 1. Issue the lsrank command to generate a report that lists the status of the ranks that are associated with the storage unit. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
dscli>lsrank -dev storage_unit_ID -l
Notes: a. The report that is generated by this example provides a list of all ranks; however, the storage type is mixed between fixed block and CKD. b. You can narrow your report information to a specific storage type by adding the -stgtype [fb | ckd] parameter to your command. 2. Use the report to determine the rank or ranks you want to modify. The report contains details about the ranks that you must use to issue the chrank command for modifications. 3. Issue the chrank command to implement one of the following types of modifications: a. To designate a rank as reserved, enter the chrank command at the dscli command prompt with the following parameters and variables:
dscli>chrank -dev storage_image_ID -reserve rank_ID
Changing the rank configuration state to reserved designates that the extents that are associated with the rank are not eligible for allocation to a logical volume. However, the existing allocations remain in effect until the configuration state is changed to normal. In other words, the characteristics that the rank inherited from its parent array when it was originally assigned remain intact. Notes: 1) You can specify a range of rank IDs or multiple rank IDs as long as you match the command usage criteria. 2) You cannot change the configuration state of a reserved rank to unassigned without first releasing it. b. To release a rank from its reserved configuration state, enter the chrank command at the dscli command prompt with the following parameters and variables:
dscli>chrank -dev storage_image_ID -release rank_ID
When a rank is released from the configuration state of reserved, it is designated with a configuration state of normal. c. To remove a rank from its current extent pool and array assignment but not delete it, enter the chrank command at the dscli command prompt with the following parameters and variables:
dscli>chrank -dev storage_image_ID -unassign rank_ID
Notes: 1) A rank must have a configuration state of normal before it can be changed to a configuration state of unassigned.
128
2) A rank that is unassigned can be assigned to an array and extent pool of another storage configuration as long as the storage type is compatible: all fixed block or all CKD.
Viewing rank status

Complete this task to view the status of all the ranks that are associated with a storage unit using DS CLI commands. After you have created your ranks, there might be times when you want to view the status of all the ranks that are associated with your storage unit. Using the parameters that are associated with the lsrank command, you can refine your search to specific rank criteria such as: v Storage type (fixed block or CKD) v Data state v Configuration state v RAID type Perform the following step to view the status of all the ranks that are associated with the storage unit. Issue the lsrank command to generate a list of all the ranks and their status. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
dscli>lsrank -dev storage_image_ID -l
The state and datastate column information for the ranks contains reported conditions that can require further action. See the lsrank command for an explanation of the action designations.
Viewing properties for one rank

Complete this task to view the detailed properties of one rank that is associated with a storage unit using DS CLI commands. A rank is a logically contiguous storage space that is made up of one array. After you have created your ranks, there might be times when you want to view the status of an individual rank. Perform the following steps to view the status of a rank that is associated with the storage unit. Issue the showrank command to generate the properties report for the specified rank. Enter the showrank command at the dscli command prompt with the following parameters and variables:
dscli>showrank -dev storage_image_ID rank_ID
Notes: 1. Because the showrank command requires the use of a specific rank ID, you can issue the lsrank command first to obtain the specific rank IDs. 2. The state and datastate column information for the ranks contains reported conditions that can require further action. See the showrank command for an explanation of the action designations.
129
Correcting a rank-related configuration error

Complete this task to correct a rank-related configuration error. There might be occasions when you are using the mkrank command to create ranks, but the transaction fails. You might not be aware of the failure until you run the lsrank or showrank command to check the status of the ranks that you have created. The lsrank or the showrank commands display reports that includes a state category. The state category reports on the current state of the rank. One of the state codes is configuration error. A state of configuration error specifies that a rank configuration process has not completed successfully. This state reflects an internal error condition and is not an indication that there was a user input error. You might want to gather additional information about what caused the error, which can help you determine how to correct it. Generally, to correct this error state, you must delete the designated rank configuration and submit a new transaction request. Perform the following steps to obtain additional information about the configuration error and to correct this error condition. 1. Obtain additional information about the transaction by implementing one of the following methods: v Add the -v (verbose) command flag to your mkrank command and reissue the command for the transactions that show the configuration error designation. Note: You can also turn on the verbose mode in your profile file and reissue the command. Designating the verbose mode allows the display of extra output that includes the error code that is generated when the create rank transaction fails. v Add the -extpool parameter to your mkrank command and reissue the command for the transactions that show the configuration error. You might consider using this parameter if you have not yet assigned your ranks to the extent pools. If the transaction fails, a message states the reason for a failure. 2. Issue the rmrank command to delete the designated rank configurations if you do not want to obtain additional information about what caused the configuration error. Note: In the majority of instances, this is the only method for correcting a configuration error.
Removing ranks from a storage configuration

Complete this task to remove ranks from a storage configuration using the DS CLI. When you are using the DS CLI to delete ranks as part of a storage configuration deletion, the following sequential deletions must have already occurred: v Host access to the volumes of the configuration must have been removed. (Does not apply to a CKD configuration.)
130
v The associated volume groups must have been removed. (Does not apply to a CKD configuration.) v The fixed block or CKD volumes that are part of the configuration must have been removed. v The LCUs (if you are removing a CKD configuration) must have been removed. When you remove ranks using the DS CLI, there is an extended period of processing because the arrays and extent pools are unassigned from the ranks and the drives are formatted. During this processing, the arrays and extent pools are still shown with a status of assigned, even though you receive a confirmation message each time a rank has been deleted. The status for the arrays and extent pools do not change to unassigned until after the drives have been formatted. Perform the following steps to remove ranks from a storage configuration: 1. Issue the lsrank command to obtain a list of the ranks that are associated with the storage configuration that is being deleted. Enter the lsrank command at the dscli command prompt with the following parameters and variables:
dscli>lsrank -dev storage_image_ID -l -stgtype [fb | ckd]
2. Look at the list and ensure that the ranks are in a state that allows them to be deleted. All the ranks need to have a data and configuration state of normal. 3. Issue the rmrank command to delete the ranks from the storage configuration. Enter the rmrank command at the dscli command prompt with the following parameters and variables:
dscli>rmrank -dev storage_image_ID rank_ID
Notes: a. If you have multiple ranks that are being deleted, you might want to include the -quiet parameter in your command. This parameter suppresses the confirmation message that is issued for each rank that is deleted. b. Deleting a rank or many ranks is a lengthy process because the array and extent pool assignments are unassigned and the disk drives are formatted. When a rank is unassigned from the array and extent pool, a confirmation messages is issued that indicates that the rank has been deleted. However, because of the formatting, the process is not complete. You cannot initiate any action on the arrays or extent pools until the formatting is completed.
Modifying a logical control unit

Complete this task to modify a logical control unit (LCU) using the DS CLI. You can perform the following modifications to an LCU using the DS CLI commands: v Change the subsystem ID to ensure it retains its unique identity v Change the system behavior so that it emulates an LCU type that allows your system to process DS CLI transactions v Change the behavior of consistency group creation v Change the system behavior for processing concurrent copy transactions Perform the following steps to modify an LCU using DS CLI commands:
131
1. Issue the lslcu command to generate a report that lists the status of the LCUs that are associated with the storage unit. Enter the lslcu command at the dscli command prompt with the following parameters and variables:
dscli>lslcu -dev storage_unit_ID -l
2. Use the report to determine the LCU or LCUs that you want to modify. The report contains details about the LCUs that you must use to issue the chlcu command for modifications. 3. Issue the chlcu command to implement one of the following types of modifications: a. To maintain the unique identity that is associated with your logical subsystem within your Copy Services domain, you can change your subsystem ID (SSID). Enter the chlcu command at the dscli command prompt with the following parameters and variables:
dscli>chlcu -dev storage_image_ID -ss new_ss_ID lcu_ID
Note: The new SSID that you specify replaces the existing SSID value in the initial target LCU ID. b. To provide your system a format that allows you to process DS CLI transactions. Enter the chlcu command at the dscli command prompt with the following parameters and variables:
dscli>chlsu -dev storage_image_ID -lcutype [3990-3 | 3990-tpf | 3990-6 | bs2000] lcu_ID
Notes: 1) The target LCUs are changed to the LCU type that you designate 2) When you designate multiple LCUs, separate multiple IDs and multiple ID ranges with a space. Separate your LCU range with a dash (-) between the first and last number of the range. c. To modify the concurrent copy timeout value using the chlcu command, see Modifying the concurrent copy timeout value on page 158. d. To modify the consistency group timeout value, see Modifying the consistency group timeout value on page 158. e. To modify the critical mode (Administrator authority only), see Modifying the critical mode setting on page 159.
Viewing logical control unit status

Complete this task to view the status of all the logical control units (LCUs) that are associated with a storage unit using DS CLI commands. After you have created your LCUs, there might be times when you want to view the status of all the LCUs that are associated with your storage unit. Using the parameters that are associated with the lslcu command, you can refine your search to the following specific LCU criteria: v Address group v Specific LCUs or multiple LCUs Perform the following step to view the status of all the LCUs that are associated with the storage unit. Issue the lslcu command to generate a list of all the LCUs and their status. Enter the lslcu command at the dscli command prompt with the following parameters and variables:
132
dscli>lslcu -dev storage_image_ID -l
Notes: 1. Issue the lsaddressgrp command first if you decide to refine your search to include just the LCUs that are associated with a specific address group. The lsaddressgrp command provides a list of address groups that you can then use with the -addrgrp parameter of the lslcu command. 2. To specify a range of LCU IDs, separate the LCU IDs with a dash (-). You must separate multiple LCU IDs or ranges of LCU IDs with a blank space between each ID or range of IDs.
Viewing properties for one logical control unit

Complete this task to view the detailed properties of one logical control unit (LCU) that is associated with a storage unit using DS CLI commands. An LCU represents a logical subsystem for zSeries hosts. The DS6000 has a 16 384 volume address space that is partitioned into 64 logical subsystem (LSS) units, where each LSS contains 256 logical volume numbers. The 64 LSS units are assigned to one of 4 address groups, where each address group contains 16 LSSs, or 4096 volume addresses. All of the LSSs in one address group must be of the same type (CKD or fixed block). Because you can modify some of the properties of an LCU, there might times when you want to examine the associated properties. The showlcu command allows you to view the properties of a single LCU. Perform the following step to view the properties of a single LCU: Issue the showlcu command to view a report that displays the properties of a single LCU. Enter the showlcu command at the dscli command prompt with the following parameters and variables:
dscli>showlcu -dev storage_image_ID LCU_ID
Note: The LCU ID is a 2-digit hexadecimal number in the range of 00 - 1F.
Removing logical control units from a CKD storage configuration

Complete this task to remove all logical control units (LCUs) from a CKD storage configuration using the DS CLI. When you are using the DS CLI to delete LCUs as part of a storage configuration deletion, the following sequential deletions must have occurred: v The alias CKD volumes that are part of the configuration must have been removed v The CKD volumes that are part of the configuration must have been removed Perform the following steps to remove LCUs from a CKD storage configuration: 1. Issue the lslcu command to obtain a list of the LCUs that are associated with the storage configuration that is being deleted. Enter the lslcu command at the dscli command prompt with the following parameters and variables:
dscli>lslcu -dev storage_image_ID -l
133
2. Look at the list to ensure that the LCUs are in a state to be removed. They are ready if there are no volumes that are assigned to the LCU (zeros are displayed for each LCU in the Confgvols column of the list). 3. Issue the rmlcu command to delete the LCUs from the storage configuration. Enter the rmlcu command at the dscli command prompt with the following parameters and variables:
dscli>rmlcu -dev storage_image_ID lcu_ID
Notes: a. If you have multiple LCUs that are being deleted, you can include the -quiet parameter in your command. This parameter suppresses the confirmation message that is issued for each LCU that is deleted. b. You must separate multiple LCU IDs or ranges of LCU IDs with a blank space between each ID or range of IDs. Each range of LCU IDs must be separated by a dash (-) between the first ID and the last ID of the range.
134

This topic provides information about how to use DS CLI commands to perform the Copy Services tasks associated with FlashCopy, Metro Mirror, Path establishment, and Global Mirror transactions.
FlashCopy functions
This topic provides a list of tasks that help you create, monitor, and manage your FlashCopy operations using DS CLI commands.
Creating a FlashCopy relationship

Complete this task to create a FlashCopy relationship between a source and target volume that enables a point-in-time copy of a source volume onto a target volume. You can create a FlashCopy relationship between a source and a target volume that enables a point-in-time copy of a source volume onto a target volume. FlashCopy functions run on the DS6000 storage units and are supported on many operating systems. For example, if you set up and configure your DS6000 to use i5/OS, you can create copies of System i disk pools within a single DS6000 using FlashCopy. After the FlashCopy function completes, you can immediately access the target point-in-time copies by associating another System i or logical partition. When you issue a FlashCopy command with the background copy option, the FlashCopy relationship is established but it is put in a queue for background copying. The time difference between the submission and actual start time of the task depends on the number of FlashCopy relationships that are currently copying in the background or waiting in the queue. When the copy processing starts, the status displays as background copy running for that FlashCopy volume pair. How long actual physical copy processing takes can depend on the amount of data being copied and other activities that are occurring on the storage unit. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following steps to create FlashCopy relationships using the DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format is an example command with declared values for the variables. 1. Issue the mkflash command to create FlashCopy relationships. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 0001:0004
Notes: a. Specify the storage unit for the -dev storage_image_ID parameter. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. If the management console
135
has an IP connection to the specified storage unit, the command works. If the IP connection is not established, you can use the mkremoteflash command if there is a PPRC Path established between the storage unit from which you issue the command and the (remote) storage unit where the FlashCopy volumes are located. b. For further information, including optional parameters, see the mkflash and mkremoteflash commands. A confirmation message is issued for each successful FlashCopy pair that is created. 2. Issue the lsflash command to check the status information for each FlashCopy relationship. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l SourceVolumeID:TargetVolumeID.
dscli>lsflash -dev IBM.1750-68FA150 -l 0100:0100
Use the -l parameter to provide a more detailed report about the FlashCopy relationships. Note: If you used the mkremoteflash command, you must enter the lsremoteflash command to perform a status check.
Creating a persistent FlashCopy relationship

Complete this task to create a persistent FlashCopy relationship that remains even after the FlashCopy operation completes. Creating a persistent FlashCopy relationship prevents another FlashCopy task from writing to your target volume before you have deleted the FlashCopy relationship. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to create a persistent FlashCopy relationship. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format is an example command with declared values for the variables. Issue the mkflash on page 426 command with the persist parameter to create a persistent FlashCopy relationship. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID -persist sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-1337370 -persist 0000:1300
The resulting output

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-1337370 FlashCopy pair 0000:1300 successfully created.
Viewing information about FlashCopy relationships

Complete this task to view status information about each existing FlashCopy relationship.
136
You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to view status information about existing FlashCopy relationships using DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. Issue the lsflash command to provide a report that lists the FlashCopy relationships and status information for each FlashCopy relationship in the list. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l source_volume_ID:target_volume_ID Example
dscli>lsflash -dev IBM.1750-68FA150 -l 0100:0200 0101:0201 0102:0202 0103:0203
The resulting output Note: The following tables display the output that is associated with the lsflash command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750.
Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Sequence SrcLSS Num 01 01 01 01 10 10 11 11 Timeout (secs) 120 120 120 120
ID 0100:0200 0101:0201 0102:0202 0103:0203
Active Copy Disabled Disabled Disabled Disabled
Record ing Disabled Disabled Disabled Disabled
Persist ent Disabled Disabled Disabled Disabled
Rever tible Disabled Disabled Disabled Disabled
SourceWriteEnabled Enabled
TargetWriteEnabled Disabled
BackgroundCopy Disabled
CopyIndicator Yes
OutOfSyncTracks 0
DateCreated 12/01 /2003 02:20 :00 12/01 /2003 02:20:00 12/01 /2003 02:20 :00 12/01 /2003 02:20 :00
DateSynced 12/01 /2003 02:23 :47 12/01 /2003 02:23:47 12/01 /2003 02:23 :47 12/01 /2003 02:23 :47
Enabled
Disabled
Disabled
Yes
Enabled
Disabled
Disabled
Yes
Enabled
Disabled
Disabled
Yes
137
Deleting FlashCopy relationships

Complete this task to delete FlashCopy relationships. Deleting FlashCopy relationships between volume pairs ends a FlashCopy operation. You can delete a FlashCopy relationship at any time. If you delete a FlashCopy relationship with the background copy option and the background copy operation is still in progress, the target volume is not a complete point-in-time copy of the source volume. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following steps to remove FlashCopy relationships using DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format is an example command with values declared for the variables. 1. Issue the lsflash command to check the status information for each FlashCopy relationship. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l SourceVolumeID:TargetVolumeID.
Use the -l parameter to provide a more detailed report about the FlashCopy relationships. Note: If you have originally used the mkremoteflash command to create your FlashCopy relationships, you must enter the lsremoteflash command to perform a status check. 2. Analyze the list of volumes and ensure that these are the volumes from which the FlashCopy relationship must be removed. 3. Issue the rmflash command to remove the FlashCopy volume relationships. Enter the rmflash command at the dscli command prompt with the following parameters and variables: dscli>rmflash -dev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>rmflash -dev IBM.1750-68FA120 0001:0004 0003:00FF 0008:000C
Notes: a. The example shows the use of multiple FlashCopy pair IDs. Ensure that you separate multiple FlashCopy pair IDs with spaces. b. If you used the mkremoteflash command to create your FlashCopy relationships, you must enter the rmremoteflash command to remove the FlashCopy relationships. 4. A confirmation message is displayed for each FlashCopy relationship that you want to remove. Enter Y in response to each message that requests that you confirm that you want to remove the specified FlashCopy pair. A message similar to the following appears for each FlashCopy pair being removed when you process the rmflash command.
Are you sure you want to remove the FlashCopy pair 0001:0004? [y/n]: Y FlashCopy pair 0001:0004 successfully removed.
138
Creating remote FlashCopy transactions

Complete this task to create a remote FlashCopy (inband FlashCopy on the ESS 2105) at a target (remote) site using remote FlashCopy commands. Remote FlashCopy operations can only be processed using the DS CLI and not the DS Storage Manager. (Part of the Remote FlashCopy operation requires that you create paths and volume pairs first. You can issue those requests using either the DS Storage Manager or the DS CLI.) To establish a FlashCopy relationship at the target site, remote FlashCopy commands are issued to a source volume of a remote mirror and copy volume pair on a source (local) storage unit and sent across paths (acting as a conduit) to a target storage unit. This eliminates the need for a network connection to the target site solely for the management of FlashCopy relationships. Limitation: Remote FlashCopy commands establish a FlashCopy relationship at the target (remote) site when a network connection to the target site is lost. The Remote FlashCopy operation is not supported through the DS Storage Manager, because network connections to both the source and target sites are required. If the network connection to the target site is lost, the DS Storage Manager cannot connect to the target site. Whether you use the DS Storage Manager or DS CLI for Steps 1 and 2, you must perform Step 3 from the DS CLI. Note: You can perform all steps from the DS CLI. The details are described in Processing Remote FlashCopy (inband) transactions. The following example illustrates the required steps for creating a remote FlashCopy operation. 1. Create paths between the source LSS and the target LSS. For example, IBM.1750-1300861 and IBM.1750-1300871 You need to know which volumes are available for use before you can issue the request to establish the path. 2. Create Metro Mirror volume pairs from the source LSS to the target LSS. For example, volume 2200 (IBM.2107-1300861/2200) from LSS22 and volume 2A00 (IBM.2107-1300871/2A00) from LSS22. 3. Enable a Remote FlashCopy operation at the target site using volume B as the source volume and volume C as the target volume. Assume that the target site network connection is lost. You can create the FlashCopy relationship from volume B to volume C (both volumes at the target site). However, you cannot use the DS Storage Manager for this step because connections to the target site are lost. Assume that you performed Step 1 and Step 2 from the DS Storage Manager (connections to both storage units at the source and target sites were available at that time) and the Metro Mirror relationship between the volume pair still exists. To create the Remote FlashCopy operation, you must perform Step 3 from the DS CLI using the following command as an example. (You must be logged into the DS CLI in interactive command mode.) Note: Use LSS 22 on the local site as a conduit LSS for the new remote Flash Copy relationship on the remote storage unit that will use volume 2A00 as the source. The target can be any other volume on the remote storage unit (in this example 2A01) dscli>mkremoteflash -dev IBM.2107-1300871 -conduit IBM.2107-1300861/22 2A00:2A01
139
where: -dev Specifies the storage unit ID, which includes manufacturer, machine type, and serial number.
-conduit LSS_ID (Required) Identifies the source LSS of an existing remote mirror and copy relationship that is used as a conduit for communicating with the target storage unit. The source volume IDs that are specified in source_volume_ID:target_volume_ID must be the target volumes in a remote mirror and copy relationship in which one of the conduit LSS volumes acts as a source volume. You can specify a fully qualified LSS ID, which includes the storage unit ID. source_volume_ID:target_volume_ID (Required) Establishes a remote FlashCopy relationship for the source and target volume pairs with the specified IDs. You can specify fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage unit IDs if the -dev parameter is specified. Separate the IDs of the FlashCopy relationships with spaces. This report is displayed if your command input is correct. Date/Time: February 7, 2005 4:29:42 PM IST IBM DSCLI Version: 5.0.0.0 DS: IBM.2107-1300871 FlashCopy Pair ID 2A00:2A01 successfully initiated. Use the lsremoteflash command to determine copy completion. Verify that the transaction has processed successfully by issuing the following command: dscli>lsremoteflash -dev IBM.2107-1300871 -conduit IBM.2107-1300861/22 2A00:2A01
Resynchronizing FlashCopy relationships

Complete this task to resynchronize (apply incremental changes on the source volume to) a FlashCopy target volume. After the initial FlashCopy operation, only data that has changed on the source volume since the last resynchronization operation was performed is copied to the target volume. The change recording option and the persistent option must have been enabled on the FlashCopy volume pair. When a pair is established with the -record and -persist parameters, the pair initially synchronizes and then a record of all host write operations to the source is maintained in the source volumes. You can resynchronize a FlashCopy target volume to create a new point-in-time copy of your data without waiting to copy an entire volume for each point-in-time copy. Instead, only tracks that have changed on the source volume since the last resynchronization operation was performed are copied to the target volume. The specified parameters in this command replace the parameters in the existing relationship. In order to keep the initial -record and -persist parameters, specify the -record and -persist parameters with the resyncflash command. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to resynchronize FlashCopy relationships with DS CLI commands. The example commands in this task are shown in two formats. The
140
first format shows the type of information the command requires. The second format is an example command with declared values for the variables. Issue the resyncflash command to resynchronize FlashCopy relationships. Enter the resyncflash command at the dscli command prompt with the following parameters and variables: dscli>resyncflash -dev storage_image_ID sourcevolumeID:targetvolumeID Example
dscli>resyncflash IBM.1750-68FA120/0100:IBM.1750-68FA120/0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully incremented.
Reversing a FlashCopy relationship

Complete this task to reverse the direction of a FlashCopy volume pair. When the direction of a FlashCopy relationship is reversed, the volume that was previously defined as the target becomes the source for the volume that was previously defined as the source. The data that has changed is copied to the volume that was previously defined as the source. For example, suppose you create a FlashCopy relationship between source volume A and target volume B. Data loss occurs on source volume A. To keep applications running, you can reverse the FlashCopy relationship so that data on volume B is copied to volume A. The background copy process must complete before you can reverse the direction of the FlashCopy relationship. Exception: You cannot reverse the direction of the FlashCopy relationship during recovery from the failure of FlashCopy consistency group formation in a Global Mirror configuration due to a failure at the Global Mirror primary site. In this case, after you ensure the consistency of the FlashCopy consistency group target volumes, you can use the fast option of the reverseflash command before the background copy process completes to reverse the direction of the FlashCopy volume pair. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to reverse the direction of FlashCopy relationships with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format is an example command with declared values for the variables. Issue the reverseflash command to reverse the direction of FlashCopy relationships. Enter the reverseflash command at the dscli command prompt with the following parameters and variables: dscli>reverseflash -dev storage_image_ID sourcevolumeID:targetvolumeID Example
141
dscli>reverseflash IBM.1750-68FA120/0100:IBM.1750-68FA120/0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully reverse restored.
Applying the FlashCopy revertible option to existing FlashCopy relationships

Complete this task to prepare for disaster recovery of a FlashCopy consistency group in a Global Mirror configuration. Issue the setflashrevertible command to a FlashCopy relationship with the persistent, change recording, target write inhibit, and no copy options enabled, and the revertible option disabled. It is not valid to issue the setflashrevertible command to a FlashCopy relationship that is already revertible. The setflashrevertible command modifies a FlashCopy volume pair that is part of a Global Mirror relationship to revertible. If a failure occurs on the primary site during a Global Mirror create FlashCopy consistency group process and if that failure results in an inconsistency of the FlashCopy consistency group target volumes, you might be able to correct the inconsistency either by discarding changes or committing changes to the target volumes. The revertible option allows data to be committed to the target to form a new consistency group or to be reverted back to the last consistency group. The setflashrevertible command must be run before the FlashCopy pair can be committed or reverted. You must have previously created a FlashCopy relationship with the persistent, change recording, target write inhibit, and no copy options enabled. The FlashCopy Revertible option must be disabled prior to performing this task. It is not valid to perform the FlashCopy Revertible task on a FlashCopy relationship that is already revertible. The FlashCopy Revertible task restarts an existing FlashCopy volume pair with the revertible option enabled for disaster recovery. The FlashCopy Revertible option remains in effect until the commit changes or discard changes task is performed. Both the commit changes and discard changes tasks disable the FlashCopy revertible option. You can perform the FlashCopy Revertible task using either the DS CLI or the DS Storage Manager. Perform the following steps to apply the revertible option to existing FlashCopy relationships with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. Note: The -nocp, -record, -persist, and -tgtinhibit (target inhibit) parameters are included automatically when this command processes. Issue the setflashrevertible command to apply the revertible option to existing FlashCopy relationships. Enter the setflashrevertible command at the dscli command prompt with the following parameters and variables: dscli>setflashrevertible -dev storage_image_ID sourcevolumeID:targetvolumeID
142
Note: Specify the storage unit for the -dev storage_image_ID parameter. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. Example
dscli>setflashrevertible IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 The resulting output Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy volume pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully made revertible.
Starting a background copy of a FlashCopy relationship

Complete this task to create a FlashCopy volume pair that allows data to be copied from the source volume to the target volume. When you issue a FlashCopy command without using the nocp parameter, the FlashCopy relationship is established but it is put in a queue for background copying. The exact time that the background copying starts for the specific relationship depends on the number of FlashCopy relationships that have already begun, or are waiting to begin, background copying. When the background copy starts, the state of that FlashCopy volume pair is displayed as background copy running. A background copy causes all data on the source volume to be physically copied to the target volume. After a FlashCopy pair is established, an automatic withdrawal of the FlashCopy relationship occurs when all source tracks have been physically copied to the target volume (unless the FlashCopy relationship was designated as persistent by using the persist parameter when it was established). Note: The amount of time that the actual physical copy can take depends on the amount of data that is copied and other activities that are occurring on the storage unit. You can monitor when the copy completes by issuing the lsflash command to check the status information for each FlashCopy relationship. Perform the following steps to create FlashCopy relationships with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. 1. Issue the mkflash command without the nocp parameter to create FlashCopy relationships that allow data to be copied from the source volume to the target volume. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 0001:0004
Note: Specify the storage unit for the -dev storage_image_ID parameter. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devidvariable in your profile file.
143
A confirmation message is issued for each successful FlashCopy pair that is created. 2. Issue the lsflash command to check the status information for each FlashCopy relationship. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l SourceVolumeID:TargetVolumeID. Example
Use the -l parameter to provide a more detailed report about the FlashCopy relationships.
Preventing write operations on FlashCopy target volumes

Complete this task to prevent (inhibit) host write operations on FlashCopy target volumes. By inhibiting writes on the target volume, you ensure that the target is an uncorrupted incremental backup. Use the mkflash command with the tgtinhibit parameter to prevent host write operations on the target volume. When you use the tgtinhibit parameter, the change recording feature is not active on the target volume. Write operations are not allowed on the target volume; therefore, the change recording bitmap for the target volume is not modified. Note: By default, when you issue a mkflash command with the record and persist parameters, the FlashCopy relationship is established to act as an incremental FlashCopy. In addition, by default, when you issue the setflashrevertible command to a FlashCopy volume pair, the source volume of the volume pair is write inhibited. This allows the FlashCopy relationship to revert (change back) to a previous consistent state, if needed. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following steps to prevent (inhibit) host write operations on FlashCopy target volumes with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format is an example command with declared values for the variables. Issue the mkflash command with the tgtinhibit parameter to prevent host write operations on the target volume of the FlashCopy relationships that you create. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID -tgtinhibit sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 -tgtinhibit 0001:0004
A confirmation message is issued for each successful FlashCopy pair that is created.
144
Creating a FlashCopy target volume on an existing Metro Mirror source volume

Complete this task to create a FlashCopy target volume on an existing Metro Mirror source volume. Use the mkflash command with the tgtpprc parameter to create a FlashCopy target volume on an existing Metro Mirror source volume. The FlashCopy takes a point-in-time copy of a source volume, and then Metro Mirror makes a copy of the FlashCopy target volume at a remote site. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following steps to create a FlashCopy target volume on an existing Metro Mirror source volume with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. v Issue the mkflash command with the tgtpprc parameter to create a FlashCopy target volume on an existing Metro Mirror source volume. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID -tgtpprc sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 -tgtpprc 0001:0004
A confirmation message is issued for each successful FlashCopy pair that is created. Note: The tgtpprc parameter can also be used with the resyncflash command. When you issue a resyncflash command to a FlashCopy relationship, only the new write operations to the source since the last resynchronization are copied to the target. This minimizes the data that is copied to the remote site when you also use the tgtpprc parameter. The specified parameters in the resyncflash command replace the parameters in the existing relationship. In order to keep the initial record, persist, and tgtpprc parameters, the record, persist, and tgtpprc parameters must be specified in the resyncflash command. v Issue the resyncflash command with the tgtpprc parameter to resynchronize FlashCopy relationships and create a FlashCopy target volume on an existing Metro Mirror source volume. Enter the resyncflash command at the dscli command prompt with the following parameters and variables: dscli>resyncflash -dev storage_image_ID -record -persist -tgtpprc sourcevolumeID:targetvolumeID Example
dscli>resyncflash dev IBM.1750-68FA120 -record -persist -tgtpprc 0100:0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair 0100:0200 successfully incremented.
145
Discarding changes to FlashCopy target volumes

Complete this task to discard changes to FlashCopy target volumes to form a consistency group on the target volumes as part of a disaster recovery process. You cannot discard changes to FlashCopy target volumes unless you have modified the FlashCopy relationship using the setflashrevertible command, which changes the Revertible value to Enabled. You can use the revertflash command only when your analysis of the FlashCopy relationships reveals one of the following conditions: v The FlashCopy relationships are revertible and all the sequence numbers are equal. v There is a group of FlashCopy pairs that are all revertible and another group of FlashCopy pairs that are all nonrevertible. In addition, all the FlashCopy sequence numbers are not equal. However, the following conditions exist: The FlashCopy sequence number for all revertible pairs is equal. The FlashCopy sequence number for all nonrevertible pairs is equal. If a FlashCopy consistency group formation operation does not complete, you must determine whether to discard changes (revert to a previous consistent state) or commit the operation to the current state. As part of a disaster recovery process, determine the state of the consistency groups in the affected sessions. The Discard Changes task specifies that the previous consistency group that was created by the Global Mirror session becomes the current state, and the Commit Changes task is no longer possible. The Discard Changes task removes the FlashCopy relationship changes and resets them to the last consistency group state. The revertible state is set to No. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to correct the applicable FlashCopy relationships with DS CLI commands. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. Issue the revertflash command to correct the FlashCopy relationships and reset them to the last consistency group state. Enter the revertflash command at the dscli command prompt with the following parameters and variables: dscli>revertflash -dev storage_image_ID SourceVolumeID Example
dscli>revertflash -dev IBM.1750-68FA150 0100
Notes: 1. Remember that storage_image_ID is the value for the remote server that has been designated the primary server until the original primary server is again available for use. 2. Global Mirror operations have performed the establish FlashCopy revertible processing but might have failed to form a consistency group before the disaster occurred. If your analysis, through use of the lsflash command, has determined that a revertflash command is needed, there is no need to issue a new mkflash command.
146
A confirmation message like the following one is generated for each FlashCopy relationship that has been successfully reset.
FlashCopy pair 0100:0200 successfully reverted to the previous consistency.
Committing data to FlashCopy target volumes

Complete this task to commit data to FlashCopy target volumes to form a consistency group on the target volumes as part of a disaster recovery process. You can commit changes to FlashCopy target volumes only if you have modified the FlashCopy relationship using the setflashrevertible command, which changes the Revertible value to Enabled. You can use the commitflash command to commit data only when your analysis of the FlashCopy relationships reveals one of the following conditions: v All the FlashCopy sequence numbers are equal and at least one of the FlashCopy relationships is nonrevertible. v The FlashCopy relationships appear as follows: Some of the FlashCopy relationships completed processing so that a consistent group was created. These FlashCopy relationships are no longer revertible. Some of the FlashCopy relationships have not completed creating a new consistency group. These FlashCopy relationships are still in a revertible state. All the FlashCopy relationships have the same FlashCopy sequence number. This indicates that all the FlashCopy relationships are involved in the same consistency group. If a FlashCopy consistency group formation operation does not complete, you must verify the consistency group at the remote site and determine whether the changes need to be rolled forward (committed) or rolled backward (discarded). The commit task specifies that the last consistency group that has been created by the Global Mirror session is committed to the current state, and reverting to the previous consistency group state is no longer possible. You can perform this task using either the DS CLI or the DS Storage Manager. Perform the following step to correct the applicable FlashCopy relationships with DS CLI commands. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format is an example command with declared values for the variables. Issue the commitflash command to correct the FlashCopy relationships and commit them to the consistency group that was being formed before the disaster occurred. Enter the commitflash command at the dscli command prompt with the following parameters and variables: dscli>commitflash -dev storage_image_ID SourceVolumeID Example
dscli>commitflash -dev IBM.1750-68FA150 0100
Note: v Remember that storage_image_ID is the value for the remote server that has been designated the primary server until the original primary server is again available for use.
147
v Global Mirror operations have performed the establish FlashCopy revertible processing and might have failed to form a consistency group before the disaster occurred. If your analysis, through use of the lsflash command, has determined that a commitflash command is needed, there is no need to issue a new mkflash command. A confirmation message like the following one is generated for each FlashCopy relationship that has been successfully reset.
FlashCopy pair 0100:0200 successfully committed.
Metro Mirror functions

This topic provides information to help you use Metro Mirror functions using the DS CLI commands. Metro Mirror is a function for application data recovery, but also for failover to remote sites for disaster recovery, remote migration of data, and off-site backups. Note: If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must not enable its write acceleration feature. The Remote Mirror and Copy commands might fail if the write acceleration feature is enabled.
Displaying the status of established paths

Complete this task to display a list of established remote mirror and copy paths that are established between LSSs. Before you begin with this task, ensure that the following guidelines are met: v Fibre-channel I/O ports are configured. v Fibre-channel paths have been established between source and target LSSs. Use this task after you have issued the mkpprcpath command to determine the status of the paths that have been established between the specified source and target LSSs. Perform the following step to display the status of established remote mirror and copy paths with DS CLI commands: Issue the lspprcpath command to display the list of established paths. Enter the lspprcpath command at the dscli command prompt with the following parameters and variables: dscli>lspprcpath -dev storage_image_ID Source_LSS_ID. Example
dscli>lspprcpath -dev IBM.1750-68FA120 10
Note: You can specify multiple LSS IDs, but they must be separated with spaces.
Displaying the WWNN of a storage unit

Complete this task to display a list of worldwide node names (WWNNs) of the storage unit in a storage complex. Before you begin, ensure that you have met the following conditions: v The remote mirror and copy license key is installed and enabled to allow operations to be performed.
148
v The fibre-channel I/O ports are configured. To participate in a fibre channel environment, each storage unit is assigned a unique 16-hexadecimal ID called a WWNN that identifies the storage unit. You must use the WWNN of the storage unit as part of the lsavailpprcport and mkpprcpath commands. Perform the following steps to display the WWNN of the storage unit in a storage complex. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lssi command to display the list of WWNNs. Enter the lssi command at the dscli command prompt as follows:
dscli>lssi -l
2. Review the output that displays the WWNN of the storage unit. This information is required when you establish a path.
Creating remote mirror and copy paths

Complete this task when you create paths because they are required when creating source and target remote mirror and copy volume pair relationships. Before you begin, ensure that you have met the following conditions: v The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have the PPRC Version 2 license enabled. v The I/O ports are configured for paths between source and target LSSs. v The I/O ports that will be used for paths are available and identified. v The worldwide node name (WWNN) of the storage unit is identified because it is a required parameter for this task. Create paths so that the logical subsystems (LSSs) are associated with each other. These are the paths through which data will be transferred so it essential that bandwidth for these operations be sufficient. In addition, you want to ensure that the ports used for remote mirror and copy operations are not the same ones that will be used for host I/O activity. Perform the following steps to create remote mirror and copy paths. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the mkpprcpath command to create the fibre-channel paths for the remote mirror and copy source and target volume pairs. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit.
149
b. The -remotewwnn parameter must specify the WWNN of the secondary storage unit. If you specify the WWNN of the primary storage unit, the command fails. c. You can specify the -dev and -remotedev parameters or specify fully-qualified srclss and tgtlss parameters, but not both. d. The shortened version of the -srclss and -tgtlss parameters are shown (value = 00) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter was not used, you must specify the fully qualified -srclss source_LSS_ID and the -tgtlss target_LSS_ID values. For example: -srclss IBM.1750-75FA120/00 -tgtlss IBM.1750-75FA120/01 e. The shortened version of the source_port_ID:target_port_ID parameter is shown (value = I1A10:I2A20), because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_immage_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified source_port_ID:target_port_ID value. For example: IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20. The fully qualified source_port_ID:target_port_ID parameter is positional on your command line. It must be placed after the -tgtlss parameter. For example:
dscli>mkpprcpath -srclss 00 -tgtlss 00 IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20
Example
dscli>mkpprcpath -dev IBM.1750-75FA120 -remotedev IBM.1750-68FA150 -srclss 00 -tgtlss 00 -remotewwnn 12341234000A000F I1A10:I2A20
2. Issue the lspprcpath command to review the list of established remote mirror and copy paths,
Correcting a path-related configuration error

Complete this task to correct a path-related configuration error with DS CLI commands. There might be occasions when you are using the mkpprcpath command to establish a path between the specified source and target LSSs and the transaction fails. You might not be aware of the failure until you run the lspprcpath command to check the status of the paths that have been established between the specified source and target LSSs. The lspprcpath command displays a report that includes a state category. The state category reports on the current remote mirror and copy path state. One of the state codes is configuration error. A state code of configuration error is an indication that you have specified an incorrect value for the remote WWNN or the target lss ID. Perform the following steps to correct the configuration error with DS CLI commands. 1. Check the original input values you provided for the -remotewwnn and -tgtlss parameters. The following criteria applies to these parameters:
150
-remotewwnn You must use the worldwide node name that is associated with the secondary storage unit. If you use the WWNN (worldwide node name) that is associated with the primary storage unit, the mkpprcpath command fails. Issue the lssi or showsi command to obtain the remote WWNN number of the secondary storage unit. You must use the logical subsystem ID that is associated with the secondary storage unit as the target. You can verify that you have used the correct value by looking at the report that is generated by the lspprcpath command. 2. Obtain the correct values for the remote WWNN or target LSS ID and reissue the mkpprcpath command followed by issuing the lspprcpath command to verify that your transaction has processed correctly. tgtlss
Removing paths
Complete this task to remove paths between the LSSs on the source storage unit and the target LSSs on the target storage units. Before you delete paths, review the paths that are currently established. If you delete all paths, you lose the communication between your remote mirror and copy volume pairs. All paths between the source LSS and target LSS are removed. Perform the following steps to remove the paths between the source and target LSSs with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspprcpath command to display a list of existing remote mirror and copy path definitions. Enter the lspprcpath command at the dscli command prompt with the following parameters and variables: dscli>lspprcpath -dev storage_image_ID source_LSS_ID Example
dscli>lspprcpath dev IBM.1750-68FA120 01
The report that displays from this command provides the worldwide node name (WWNN) that is used with the rmpprcpath command. 2. Issue the rmpprcpath command to remove the paths between all source and target pairs. Enter the rmpprcpath command at the dscli command prompt with the following parameters and variables: dscli>rmpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn source_LSS_ID:target_LSS_ID Example
dscli>rmpprcpath -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -remotewwnn 12341234000A000F 01:01
Note: v The -remotedev parameter specifies the ID of the secondary storage unit. v The -remotewwnn parameter must specify the WWNN of the secondary storage unit. If you specify the WWNN of the primary storage unit, the command fails.
151
v If you do not specify the fully qualified -dev and -remotedev parameters, you must use the fully qualified source_LSS_ID:target_LSS_ID value. For example: IBM.1750-68FA120/01:IBM.1750-68FA150/01 The fully qualified source_LSS_ID:target_LSS_ID value must be the last parameter in your command. A confirmation message is displayed for each path that is being removed. 3. Enter Y to confirm that you want to remove the specified remote mirror and copy path. A message similar to the following appears for each remote mirror and copy path that is being removed when you process the rmpprcpath command.
Are you sure you want to delete PPRC path (whatever was designated)? [y/n]: Y PPRC path (designated in the command) successfully deleted.
4. Repeat Step 2 for all the remote mirror and copy paths that you want removed from the same source LSS to a different target LSS.
Creating a Metro Mirror relationship

Complete this task to create a Metro Mirror relationship between a source volume and target volume. Before you begin, ensure that you have met the following conditions: v The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have enabled PPRC Version 2 license. v The I/O ports are configured for paths between source and target LSSs. v The fibre-channel paths are created between all Metro Mirror source and target LSSs. The paths are required for communication between the volume pairs and to copy data from the source volumes to the target volumes. Otherwise, this task fails. Metro Mirror is a function of a storage server that constantly updates a target copy of a volume to match changes made to a source volume. The source and target volumes can be on the same storage unit or on separate storage units. Metro Mirror creates the remote mirror and copy relationship in a synchronous manner. Metro Mirror functions run on the DS6000 storage unit and are supported on many operating systems. For example, if you set up and configure your DS6000 to use i5/OS, you can use Metro Mirror to create a copy of a System i disk pool on a separate DS6000, typically in a remote location. Perform the following steps to create Metro Mirror relationships between the source volumes and target volumes. 1. Issue the lsfbvol command (for fixed blocked (FB) volumes) or the lsckdvol command (for count key data (CKD) volumes) to display which volumes are available for Metro Mirror relationships on the source and target LSSs. A report is displayed that shows the availability of the volumes. 2. Issue the mkpprc command to create a Metro Mirror relationship between a source volume and a target volume. The mkpprc command must contain the following parameters and variables: dscli>mkpprc -dev storage_imag_ID -remotedev storage_image_ID -type mmir SourceVolumeID:TargetVolumeID.
152
Note: v The -remotedev parameter specifies the ID of the secondary storage unit. v The -type mmir parameter specifies that you want to establish one or more Metro Mirror volume relationships. Metro Mirror creates the remote mirror and copy relationship in a synchronous manner. v The shortened version of the SourceVolumeID:TargetVolumeID parameter is shown (value = 0100:0100) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 . Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-75FA150 -type mmir 0100:0100
A confirmation message is issued for each successful Metro Mirror volume association that is created. 3. Issue the lspprc command to view the status information of each Metro Mirror relationship in the list. Enter the lspprc command at the dscli command prompt with parameters and variables as follows: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -s SourceVolumeID:TargetVolumeID.
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -s 0100:0100 0101:0101
Creating a Metro Mirror consistency group

Complete this task to create a Metro Mirror consistency group. Ensure that the Remote Mirror and Copy license key is installed and enabled to allow the operations to be performed. In order to restart applications at a remote site successfully, data at the remote site must be consistent. The Metro Mirror consistency group function keeps data consistency at the remote site using consistency groups. A consistency group is a group of volumes that provides the ability to temporarily queue (at the hosts level) subsequent write operations to all consistency group volumes on a single LSS pairing when an error occurs to one of the volumes in the group (source or target), or when a total link failure is detected between the source and target LSS volume pair. The consistency group function of Metro Mirror consists of two parts. One is the consistency group option and the other is the freeze and unfreeze operation. The freeze operation causes the storage unit to hold off I/O activity through the freezepprc command. The unfreeze operation allows I/O activities to resume when you issue the unfreezepprc command. You can specify the consistency group option when you are defining Metro Mirror paths between pairs of LSSs or when you change the default consistency group setting on each LSS (the consistency group option is disabled by default) with the chlss command. A group of volumes in a consistency group can consist of a combination of count-key-data volumes and fixed block volumes. In addition, the group of
153
volumes in a consistency group can also consist of source volumes that are associated with a Model 1750 storage unit and target volumes that are associated with an ESS 2105 Model 800 or 750. Perform the following step to define a path that has enabled the consistency group option for the volume pairs that are associated with the LSS volume pair. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with values declared for the variables. 1. Issue the mkpprcpath command to create a consistency group for the remote mirror and copy volume pairs. Enter the mkpprcpath command with the -consistgrp parameter at the dscli command prompt with the following parameters and variables: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -srclss source_LSS_ID -tgtlss target_LSS_ID remotewwnn wwnn -consistgrp source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -srclss 01 -tgtlss 01 remotewwnn 12341234000A000F -consistgrp I0100:I0100
2. View the current consistency group state setting status of the consistency group by issuing the showlss command. You can also use the chlss command to change the default consistency group timeout value. dscli>showlss -dev storage_image_ID LSS_ID Example
dscli>showlss IBM.1750-68FA120/10
Resuming a Metro Mirror relationship

Complete this task to resume a Metro Mirror volume pair that has been suspended (paused). Before you begin, ensure that you have met the following conditions: v The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have enabled the PPRC Version 2 license. v The fibre-channel paths are created between all Metro Mirror source and target LSSs. . When you suspend (pause) volume pairs, Metro Mirror processing stops transferring data to the target volumes. Any I/O operations to the source volume are tracked during this time. Use this task to resume a suspended (paused) Metro Mirror volume on the specified LSSs. When I/O is resumed, data is sent across to the target volumes. Perform the following steps to resume Metro Mirror processing with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the resumepprc command to continue Metro Mirror processing after it has been suspended (paused). Enter the resumepprc command at the dscli command prompt with the following parameters and variables:
154
dscli>resumepprc -dev storage_image_ID -remotedev storage_image_ID -type [mmir, gcp] SourceVolumeID:TargetVolumeID Notes: 1. The -remotedev parameter specifies the ID of the secondary storage unit. 2. Specify the -type parameter when you use the resumepprc command. Otherwise, the command fails. 3. If you do not specify the fully qualified -dev and -remotedev parameters, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-68FA120/01:IBM.1750-68FA150/01 Example
dscli> resumempprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -type mmir 0100:0100
Pausing a Metro Mirror relationship

Complete this task to pause (suspend) a Metro Mirror relationship. If you need to access target volumes or perform maintenance on a remote storage unit, you can pause (or suspend) Metro Mirror volume pairs. This task pauses a Metro Mirror volume pair that you specify, and data is not copied to the target volume. The source storage unit keeps track of all changed data on the source volume, and after you resume the connection, only changes to the source volume are copied to the target volume. Perform the following steps to pause Metro Mirror processing with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the pausepprc command to pause Metro Mirror processing. Enter the pausepprc command at the dscli command prompt using the following parameters and variables: dscli> pausepprc -dev storage_image_ID_-remotedev storage_image_ID SourceVolumeID:TargetVolumeID Note: v The -remotedev parameter specifies the ID of the secondary storage unit. v If you do not specify the fully qualified -dev and -remotedev parameters, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-75FA120/01:IBM.1750-68FA150/01. Example:
dscli> pausepprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100
A confirmation message is displayed that indicates that processing for the specified volume pair has been paused. After making your changes, you can resume processing by issuing the resumepprc command.
155
Creating a Global Copy relationship

Complete this task to create a Global Copy relationship between a source volume and target volume. Before you begin, ensure that you have met the following conditions: v The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have PPRC Version 2 license enabled. v The I/O ports are configured for paths between source and target LSSs. v The fibre-channel paths are created between all Metro Mirror source and target LSSs. The paths are needed for communication between the volume pairs and to copy data from the source volumes to the target volumes. Otherwise, this task fails. You can create a Global Copy relationship between a source and target volume. Global Copy functions run on the DS6000 storage units and are supported on many operating systems. For example, if you set up and configure your DS6000 to use i5/OS, you can use Global Copy to create a copy of a System i disk pool on a separate DS6000, typically in a remote location. Perform the following steps to create Global Copy relationships between the source volumes and target volumes. 1. Issue the lsfbvol command (for fixed blocked (FB) volumes) or the lsckdvol command (for count key data (CKD) volumes) to display which volumes are available for Global Copy relationships on the source and target LSSs. A report is displayed that shows the availability of the volumes. 2. Issue the mkpprc command to create a Global Copy relationship between a source volume and a target volume. Enter the mkpprc command at the dscli command prompt with the following parameters and variables: dscli>mkpprc -dev storage_image_ID -remotedev storage_image_ID -type gcp -mode full SourceVolumeID:TargetVolumeID Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit. b. The -type gcp parameter specifies that one or more Metro Mirror volume relationships be established. Global Copy creates the remote mirror and copy relationship in an asynchronous manner. c. The shortened version of the SourceVolumeID:TargetVolumeID parameter is shown (value = 0100:0100) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 . This value must be placed at the end of your command line. Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -type gcp -mode full 0100:0100
A confirmation message is issued for each successful Global Copy volume association that is created.
156
3. Issue the lspprc command to view the status information of each Metro Mirror relationship in the list. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -s SourceVolumeID:TargetVolumeID.
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -s 0100:0100 0101:0101
Deleting a Metro Mirror relationship

Complete this task to delete the Metro Mirror relationship between a source and target volume. You can use this task to delete the relationship between a Metro Mirror volume pair. The source and target volumes are removed from the configuration when this process runs. The rmpprc command removes a remote mirror and copy (formerly PPRC) volume pair relationship. Perform the following steps to delete the Metro Mirror relationship with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspprc command to generate a report of Metro Mirror relationships. This can help you determine which Metro Mirror relationship that you want to delete. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -state -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750-68FA120 -l -remotedev IBM.1750-68FA150 0100:0100 0101:0101
2. Issue the rmpprc command to delete the Metro Mirror relationship between the source and target volume. Enter the rmpprc command at the dscli command prompt with the following parameters and variables: dscli>rmpprc -dev storage_image_ID -remotedev SourceVolumeID:TargetVolumeID Example
dscli>rmpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100
Notes: a. If you delete a Metro Mirror volume pair with the source LSS and the process runs successfully, the source and the target volume go into the simplex state. b. If you delete a Metro Mirror volume pair with the target LSS and the process runs successfully, the source volume is in the suspended state, and the target volume is in the simplex state. This option is useful in a disaster situation when the source (local) site has failed.
Modifying logical subsystem timeout values

This section describes the list of logical subsystem (LSS) timeout values that you can modify using DS CLI commands.
157
The following lists contains the LSS timeout values that you can modify using the mkpprcpath command: v Concurrent copy timeout (zSeries only) v Consistency group timeout v Critical mode enable (zSeries only)
Modifying the concurrent copy timeout value

Complete this task to modify a concurrent copy timeout value, which determines how long a volume in a concurrent copy session stays long busy (unavailable) before suspending the session. This topic applies to zSeries only. Use the chlcu command to modify the Concurrent Timeout value of the logical control unit. The Concurrent timeout value determines how long a logical volume in a concurrent copy session in a specified LSS remains in a long-busy condition before the session is suspended. Perform the following step to modify a concurrent copy timeout value (the DS CLI command refers to this as -ccsess timeout or concurrent copy session timeout). The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the chlcu command to modify a concurrent copy timeout value. Enter the chlcu command at the dscli command prompt with the following parameters and variables: dscli>chlcu -dev storage_image_ID -ccsess timeout LCU_ID Example
dscli>chlcu -dev IBM.1750-68FA120 -ccsess 190 00-0F
A confirmation message is displayed for each LCU that has been modified.
Modifying the consistency group timeout value

Complete this task to modify the consistency group timeout value, which determines the amount of time that I/O is withheld from updating a source volume of a consistency group after an error occurs. The consistency group timeout value (the -extlongbusy timeout parameter) is the time in seconds that a volume in a Metro Mirror consistency group stays unavailable after an error causes the suspension of a consistency group operation if a consistency group is not received before the timeout value. The consistency group timeout value enables automation software to detect that an error has occurred and to issue a command to freeze all other volumes of the consistency group. When an error is detected, a long-busy condition occurs. Perform the following step to modify the consistency group timeout value. The example command in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the chlcu command to modify the consistency group timeout value. Enter the chlcu command at the dscli command prompt with the following parameters and variables:
158
dscli>chlcu -dev storage_image_ID -extlongbusy timeout LCU_ID Example

dscli>chlcu -dev IBM.1750-68FA120 -extlongbusy 3 00-0F
Modifying the z/OS Global Mirror timeout value

Complete this task to modify the time that a volume in an z/OS Global Mirror session remains in a long-busy condition (the volume is not available) before the session is suspended. This task can be done in the DS8000 only. You can modify the z/OS Global Mirror timeout value, which determines how long any volume in the selected LSS in a z/OS Global Mirror session remains long busy before the session is suspended. The default value is 300 seconds. (The z/OS Global Mirror timeout value is also known as the Extended Remote Copy (XRC) timeout value that is supported on the ESS.) The long-busy condition occurs because the system data mover cannot copy data when the volume (or z/OS Global Mirror session) is not able to accept additional data. The value of this timeout is associated with a z/OS Global Mirror session when the session is created. Perform the following step to modify the z/OS Global Mirror timeout value. The example command in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with values declared for the variables. Issue the chlcu command to modify the z/OS Global Mirror timeout value. Enter the chlcu command at the dscli command prompt with the following parameters and variables: dscli>chlcu -dev storage_image_ID -xrcsess timeout LCU_ID Example
dscli>chlcu -dev IBM.1750-68FA120 -xrcsess 175 00-0F
Modifying the critical mode setting

Complete this task to enable the critical mode setting to prevent write operations to source volumes if data cannot be copied to the target volume of the volume pair because of a permanent error. You must have Administrator authority to perform this task. The critical mode setting is used to determine the behavior of remote mirror and copy (PPRC) pairs or consistency groups after the source and target storage units can no longer communicate or when paths between a volume pair in the specified LSS are lost. This setting is associated with the volume pairs in the LSSs that you selected. This option is available for z/OS environments only. When you enable the critical mode setting, the volume pair is suspended and further write operations to the source volume are not accepted if data cannot be sent to the target volume. The volume pair remains in a suspended state until you correct the problem and either issue a request to resynchronize the volume pair or delete it. If you do not enable this setting and an error occurs to the target volume, the remote mirror and copy feature suspends the copy pair, which allows the subsequent write operations to be copied to the source volume of that volume pair.
159
The storage unit records all tracks that have changed. When the problem is resolved, you can resynchronize the volume pair. Perform the following step to modify the critical mode setting. The example command in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the chlcu command to modify the critical mode setting. Enter the chlcu command at the dscli command prompt with the following parameters and variables: dscli>chlcu -dev storage_image_ID -critmode enable LCU_ID Example
dscli>chlcu -dev IBM.1750-68FA120 -critmode enable 00-0F
Note: Use the -critmode parameter only for log devices, not for devices that the system requires. In extreme cases, the host system might have to be IPLed in order to recover a device that is write inhibited. Whenever possible, use the freezepprc command as an alternative to using the -critmode parameter. This parameter cannot be used with Global Copy or remote copy and mirror cascading volumes. This parameter only applies to S/390 or zSeries volumes. The following table presents an overview of how the critical volume mode works.
Critical Mode Normal LCU, Critical Heavy Disabled or Enabled mkpprc critmode Disabled Description v Suspends the primary volume. v Allows write operations to the primary volume. Critical Volume Disabled Enabled v Suspends primary volume when the last path to the secondary volume has failed. v Inhibits write operations to the primary volume. Critical Heavy Enabled Enabled v Suspends the primary volume when the secondary volume cannot be updated for any reason. v Inhibits write operations to the primary volume.
160
Defining a path that has the consistency option enabled

Complete this task to define a path that has enabled the consistency group option for the volume pairs that are associated with the LSS volume pair. Ensure that the Remote Mirror and Copy license key is installed and enabled to allow the operations to be performed. The mkpprcpath command establishes or replaces a remote mirror and copy (formerly PPRC) path between source and target logical subsystems (LSSs) over a fibre-channel connection. This is the only supported connectivity for machine types 2107 and 1750. Paths can be established between the following machine types: 2105:2105, 2107:2107, 2107:1750, 2107:2105, 1750:1750, 1750:2105. A consistency group is a group of volumes that provides the ability to temporarily queue (at the hosts level) subsequent write operations to all consistency group volumes on a single LSS pairing when an error occurs to one of the volumes in the group (source or target), or when a total link failure is detected between the source and target LSS volume pair. This process describes how to define paths that have enabled the consistency group option . This means that when an error occurs on any volume pairs or on the links that are associated with these LSS pairs, an alert is issued and I/O to all duplex remote mirror and copy volumes on LSS pairs will be queued either until a consistency group creation operation is run or the consistency group timeout time expires. This allows external automation to use the consistency group created operation to create a dependent write consistent set of target volumes over any number of LSS and disk storage units. Perform the following step to define a path that has enabled the consistency group option for the volume pairs that are associated with the LSS volume pair. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with values declared for the variables. Issue the mkpprcpath command to create a consistency group for the remote mirror and copy volume pairs. Enter the mkpprcpath command with the -consistgrp parameter at the dscli command prompt with the following parameters and variables: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -srclss source_LSS_ID -tgtlss target_LSS_ID remotewwnn wwnn -consistgrp source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -srclss 01 -tgtlss 01 remotewwnn 12341234000A000F -consistgrp I0100:I0100
Monitoring Remote Mirror and Copy paths

Complete this task to display a list of existing remote mirror and copy path definitions using the DS CLI. Perform the following step to display a list of existing remote mirror and copy path definitions. The example command in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables.
161
Issue the lspprcpath command to generate a report of existing remote mirror and copy path definitions. Enter the lspprcpath command at the dscli command prompt with the following parameters and variables: dscli>lspprcpath -dev storage_image_ID -fullid Source_LSS_ID Example
dscli>lspprcpath -dev IBM.1750-68FA120 -fullid 10
Performing a failback recovery operation

Complete this task to perform Global Copy failback processing for the A volumes. This process resynchronizes the volumes at Site A with volumes at Site B and restarts mirroring from site A (local site) to site B (remote site). You must first create a remote mirror and copy volume pair. Before you run the failback operation, the volumes must be full duplex. The failbackpprc command copies the required data from the source volume to the target volume in order to resume mirroring. The failover process converted the full-duplex target volumes at site A to suspended source volumes. The volumes at site A started the change recording process while in failover mode. The failback processing that is described in this task can be issued against any remote mirror and copy volume that is in a primary suspended state. The failback processing copies the required data from the source volume to the target volume in order to resume mirroring. Perform the following step to perform a failback recovery operation. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the failbackpprc command to perform a failback recovery operation. Enter the failbackpprc command at the dscli command prompt with the following parameters and variables: dscli>failbackpprc -dev storage_image_ID -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>failbackpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100-0103:0100-0103
2. Issue the lspprc command to check the status information of each Metro Mirror relationship in the list. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -s SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -s 0100:0100 0200:0200 0300:0300
Performing a failover recovery operation

Complete this task to perform a failover recovery operation using DS CLI Metro Mirror. In a disaster recovery process, the failover procedure must be followed by a failback procedure after a path from the target site to the source site is created.
162
You must have created a remote mirror and copy volume pair. Volume sizes for operations that use failover and failback operations must be the same; otherwise, the failback operation fails. A failover to the Global Copy secondary volume turns the secondary volumes into primary volumes and suspends these volumes immediately. When you run a Global Copy failover, the B volumes are the primary volumes and the A volumes are the secondary volumes. This action just changes the Global Copy state of the secondary volumes from Target Copy Pending to Suspended. The failoverpprc command changes a secondary device into a primary suspended device while leaving the primary device in its current state. This command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent. Perform the following step to perform a failover recovery operation. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the failoverpprc command to perform a failover recovery operation. Enter the failoverpprc command at the dscli command prompt with the following parameters and variables: dscli>failoverpprc -dev storage_image_ID -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>failoverpprc -dev IBM.1750-68FA150 -remotedev IBM.1750-68FA120 0100-0103:0100-0103
Viewing information about Metro Mirror relationships

Complete this task to view information about Metro Mirror relationships using the DS CLI. The lspprc command displays a list of remote mirror and copy (formerly PPRC) volume relationships for a storage unit, and status information for each remote mirror and copy volume relationship in the list. Perform the following step to view information about Metro Mirror relationships. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the lspprc command to generate a report of Metro Mirror relationships. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -state -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750-68FA120 -l -remotedev IBM.1750-68FA150 0100:0100 0101:0101
163
Converting Global Copy volume pairs to synchronous

Complete this task to convert Global Copy volume pairs to synchronous (Metro Mirror volume pairs). Before you begin, ensure that the license for the remote mirror and copy feature is activated. Paths are required between the source and the target LSS storage units for the volume pairs. There are two common situations where you would convert a Global Copy volume pair to a Metro Mirror volume pair: v You have used the Global Copy function to complete the bulk transfer of data in the creation of many copy pairs, and you now want to convert some or all of those pairs to Metro Mirror mode. v You have Global Copy pairs for which you want to make FlashCopy backups on the remote site. You convert the pairs temporarily to synchronous mode to obtain a point-in-time consistent copy. If you created a Global Copy volume pair where the source volume was associated with a Model 1750 storage unit and the target volume was associated with an ESS 2105 Model 800 or 750, you can convert that volume pair to synchronous. Perform the following step to convert Global Copy volume pairs to synchronous (Metro Mirror volume pairs). The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the mkpprc command to convert Global Copy volume pairs to synchronous (Metro Mirror volume pairs). Enter the mkpprc command with the -type mmir parameter at the dscli command prompt with the following parameters and variables: dscli>mkpprc -dev storage_image_ID -remotedev storage_image_ID -type mmir SourceVolumeID:TargetVolumeID Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100 -type mmir 0101:0101 0102:0102 0103:0103
Determining which I/O ports are available for paths

Complete this task to determine which I/O ports are available for paths between the source and target LSSs. Before you begin with this task, ensure that the following guidelines are met: v The remote mirror and copy license key is installed and enabled to allow operations to be performed. v The fibre-channel I/O ports are configured. . v The I/O ports that will be used for paths are available and identified. . v The WWNN of the storage unit is identified because it is a required parameter for this task. Before you create paths, use this task to determine which ports are available for remote mirror and copy (formerly PPRC) I/O operations. These are the ports
164
through which data will be transferred so it essential that bandwidth for these operations be sufficient. In addition, you want to ensure that the ports used for remote mirror and copy operations are not the same ones that will be used for host I/O activity. You need to determine which source and target I/O ports are available for paths on the local and remote storage units. The output that is generated from this task displays fibre channel protocol (FCP) I/O ports that are available to be used as remote mirror and copy paths. Note: When you establish FCP paths, the LSSs on the source and target storage units can be connected either through a point-to-point connection (no switch) or through a switched fabric. For fibre-channel attachments, you can establish zones to help reduce the possibility of interactions between system adapters in switched configurations. For information, see the fibre channel switches publication that is available for your environment. Perform the following steps to determine the available I/O ports with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with values declared for the variables. 1. Issue the lsavailpprcport command to display a list of available I/O ports that are available for paths. Enter the lsavailpprcport command at the dscli command prompt with the parameters and variables shown as follows: dscli>lsavailpprcport -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn source_LSS_ID:target_LSS_ID Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit. b. The -remotewwnn parameter must specify the worldwide node name of the secondary storage unit. If you make a mistake and specify the worldwide node name of the primary storage unit, the command fails. c. The shortened version of the source_LSS_ID:target_LSS_ID parameter is shown (value = 01:01) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_immage_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified source_LSS_ID:target_LSS_ID value. For example: IBM.1750-68FA120/01:IBM.1750-68FA150/01 The fully qualified source_LSS_ID:target_LSS_ID value must be placed after the -remotewwnn value in your command line. For example, your command line would look like the following:
dscli>lsavailpprcport l remotewwnn 12341234000A000F IBM.1750-68FA120/01:IBM.1750-68FA150/01
Example
dscli>lsavailpprcport l dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 remotewwnn 12341234000A000F 01:01
2. Analyze the output that is generated and select from the available I/O ports to create the path. The information that is displayed shows available I/O ports combinations between the source LSSs and the target LSSs and the output depends on the current selection of adapters.
165
Deleting a single volume Metro Mirror relationship

Complete this task to delete the single volume Metro Mirror relationship whether it exists on the source or the target volume. There might be times when a communication problem occurs between your primary server and your secondary server or visa versa. If this happens during the processing of a rmpprc command, only part of the removal transaction is completed. The removal takes place even though the error message might indicate that the entire process has failed. | | | | | | | | | | | To correct this situation and to remove the other part of the pair relationship, you must reissue the rmpprc command for each volume that was not removed using the following parameters: v The -at src parameter, if the pair relationship has not been removed from the source volumes. v The -at tgt parameter, if the pair relationship has not been removed from the target volumes. v The -unconditional parameter with the -at src or -at tgt parameter; otherwise, the transaction fails. When the transaction completes, the affected volume is returned to a simplex state and becomes available for use in another pair relationship. Perform the following steps to delete the Metro Mirror relationship with DS CLI commands. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspprc command to generate a report about Metro Mirror relationships. This can help you determine which Metro Mirror relationships must be deleted. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -l 0100:0100 0101:0101
2. Issue the rmpprc command to delete the pair relationship that the volume still maintains. Enter the rmpprc command at the dscli command prompt with the following parameters and variables: | | | | | | | | | | Source volume
dscli>rmpprc -dev storage_image_ID -at src -unconditional SourceVolumeID
Example
dscli>rmpprc -dev IBM.1750-68FA120 -at src -unconditional 0100
Target volume
dscli>rmpprc -dev storage_image_ID -at tgt -unconditional TargetVolumeID
Example
dscli>rmpprc -dev IBM.1750-68FA150 -at tgt -unconditional 0100
Notes:
166
| | | | | |
a. The -dev parameter must contain the value of the secondary server when you are removing the pair relationship from a target volume. b. The management console must be able to communicate with the secondary server for this command to succeed.
Copy Services functions across a 2105 and 1750

Copy Services functions that are performed using either the DS Storage Manager or DS CLI interact with both the DS8000 (Machine type 2107) DS6000 (Machine type 1750) and the IBM System Storage 2105 Enterprise Storage Servers (ESS) Models 800 and ESS 750. Most Copy Services functions that are available on the ESS 2105 are also available on the 2107 and 1750 and in open systems and zSeries environments. Before you begin, consider the following guidelines: v To perform Copy Services functions between machine types 2105, 1750 and 2107, you must configure a Copy Services domain on the DS Storage Manager or DS CLI. v To connect to the 2105 Copy Services domain on the ESS, all interfaces that you use require an authenticated login procedure to access Copy Services functions across the storage complex. The authentication is performed by using a user name and password that was created with the ESS Specialist. Therefore, the existing user name and password that was created with the ESS Specialist for the 2105 Copy Services domain for which you will be working must match the user name and password on the management console that is connected to the 2107or 1750. Otherwise, you must add them using either the DS Storage Manager or DS CLI as part of the procedure for adding a 2105 Copy Services domain to the storage complex. v To manage Copy Services across the 2105 and 1750, you must install licensed internal code version 2.4.2 or later on the 2105. v The 2105 nor the 1750 supports remote mirror and copy (formerly PPRC) operations with an ESCON link. However, if you want to configure a remote mirror and copy relationship between the 1750 and 2105, you must use a FCP link.
Creating a Metro Mirror volume pair between a 1750 and a 2105

Complete this task to create a Metro Mirror volume pair using volumes from a 1750 and a 2105. Before you begin, ensure that you meet the following requirements: v The license for the remote mirror and copy feature must be activated. v To create a Metro Mirror volume pair between Model types 1750 and a 2105, you must have added the 2105 Copy Services domain to your storage complex environment. v Ensure that paths are set up between the source and the target LSSs for the Metro Mirror volume pairs. The paths between the 2105 and the 1750 must be configured using Fibre Channel Protocol (FCP) ports. v The storage type of the source and target volumes on the 1750 and 2105 domain must have the same type. That is, if the source volumes are fixed block volumes, the target volumes must also be fixed block volumes.
167
v The size of the volumes in the source LSS must be less than or equal to those of the target LSS. v Gather the following preliminary information: Open the ESS Specialist on the ESS 800 to determine the its WWNN. The WWNN is listed in 20 point font on the opening page. The format is 5005076300C08641. Determine the number of available volumes on the ESS 800 with the ESS 800 GUI. Document the LSS and volume mappings. Ensure that the volume sizes are matched and are -type ESS on the DS6000. You can create Metro Mirror relationships using source and target volumes from the following machine types: v A 2107 and a 2107 v A 1750 and a 1750 v A 2107 and a 1750 v A 2105 and a 1750 v A 2105 and a 2107 v A 2105 and a 2105 Note: If the source is a Copy Services 2105 domain, the Metro Mirror task is performed on the source domain. However, if you perform a Suspend at target action, the suspension occurs at the target domain. Perform the following steps to create a Metro Mirror pair between a 1750 and a 2105. For this task, the source domain is a 2105 Model 800 or 750 and the target is a 1750. You can use this task if the target domain is a 2105 Model 800 or 750 and the source is a 1750 by switching the device IDs in the volume pairs. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lsavailpprcport command to list all of the available ports to the remote system to create a connection. It is recommended that you use ports that are not mapped to hosts for PPRC for increased performance, but sharing host ports with PPRC ports is supported. Specify the remote WWPN and device ID for the target cluster. Enter the lsavailpprcport command at the dscli command prompt with the following parameters and variables: dscli>lsavailpprcport -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn Source_LSS_ID:Target_LSS_ID Example
dscli>lsavailpprcport -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602 -remotewwnn 5005076300C08642 10:10
2. Issue the mkpprcpath command to create a path between LSSs on the DS6000 to the ESS 800. You associate an LSS on the DS6000 to the ESS 800 and specify specific ports. You can list multiple ports. You should create redundant port paths from both controllers of the DS6000 to both clusters of the ESS 800. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables:
168
dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -srclss source_LSS_ID -tgtlss target_LSS_ID remotewwnn wwnn -consistgrp source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA120 -remotedev IBM.2105-18602 -srclss 01 -tgtlss 01 remotewwnn 12341234000A000F -consistgrp I0100:I0100
3. Issue the lspprcpath command to display the created paths and their status. Success indicates that the path is valid, failure indicates that the path did not create correctly, or that the relationship has become separated. Enter the lspprcpath command at the dscli command prompt with the following parameters and variables: dscli> lspprcpath -dev IBM.1750-13AB7DA 10 Example
dscli>lspprcpath -dev storage_image_ID Source_LSS_ID
4. Issue the rmpprcpath command to remove a path. You must specify both the source and target device IDs and the source and destination LSS. Enter the rmpprcpath command at the dscli command prompt with the following parameters and variables: dscli>rmpprcpath -dev storage_image_ID -remotedev storage_image_ID source_LSS_ID:target_LSS_ID Example
dscli>rmpprcpath -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602 10:10
5. Issue the mkpprc command to create a relationship between a source and target volume. The volumes must be type ESS and be exactly the same size or the attempt to create the volume pair will fail. Enter the mkpprc command at the dscli command prompt with the following parameters and variables: dscli>mkpprc -dev storage_image_ID -remotedev storage_image_ID -type mmir SourceVolumeID:TargetVolumeID Example
dscli>mkpprc -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602 -type mmir 1001:1001
6. Issue the lspprc command to list the pairs that are in existence. Upon creation, the volumes will be in the copy pending state. When the initial copy is complete, the volumes will show as full duplex on the primary and target full duplex on the secondary. If something interrupts the connection, the primary volumes indicate suspended, but the target volumes still show full duplex. You can specify a range of volumes to list multiple pairs 1001 - 10ff. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750.13AB7DA 1001-10ff
Global Mirror functions

This topic provides information to help you use Global Mirror functions using the DS CLI commands. Global Mirror asynchronously copies data from a host to a remote site, and maintains a consistent copy of the data on a storage unit at the remote site.
169
Note: If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must not enable its write acceleration feature. The Global Mirror commands might fail if the write acceleration feature is enabled.
Adding volumes to a session (Global Mirror)

Complete this task to add volumes to a Global Mirror session. Remote flash copy pairs must be mapped to the target storage unit to create a valid global mirror. You can add Global Copy primary volumes to a Global Mirror session at any time after the Global Mirror session has started without stopping the session. If you attempt to add a Metro Mirror volume or volume which, for example, is converted from Global Copy to Metro Mirror, the formation of a Consistency Group fails. Volumes can be added to a Global Mirror session but do not become active in the session until the Global Copy pair has completed its first pass and a consistent copy of the data has been formed at the remote site. If you have many volumes that you want to add to a Global Mirror session, you might consider adding them to the session in stages. This lessens the impact on your processing. Perform the following steps to add volumes to a Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspprc command to obtain a list of the Global Copy volumes that you can add to the Global Mirror session. A detailed report is displayed (if you use the -l parameter) that allows you to see the available volumes. Enter the lspprc command at the dscli command prompt with the parameters and variables shown as follows: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID. Example
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -l 0100:0100
2. Issue the chsession command to add the available volumes to a Global Mirror session. Enter the chsession command at the dscli command prompt with the parameters and variables shown as follows: dscli>chsession -dev storage_image_ID -lss LSS_ID -action add -volume volume_ID session_ID Example
dscli>chsession -dev IBM.1750-75FA120 -lss 10 -action add -volume 0100-010F 01
A confirmation message is displayed that indicates the session has been modified successfully. 3. Issue the lssession command to query the status of all volumes being processed including the volumes you added to the session. Enter the lssession command at the dscli command prompt with the parameters and variables shown as follows: dscli>lssession dev storage_image_ID -l LSS_ID
dscli>lssession dev IBM.1750-68FA120 -l 01
170
When you use the -l parameter, a detailed report displays a list of Global Mirror sessions for the specified logical subsystem (LSS) and information regarding the volumes of each session in the list.
Modifying the tuning parameters of a Global Mirror session

Complete this task to modify the tuning parameters of a Global Mirror session. A global mirror session consists of tuning parameters and topology, both of which can be modified. However, they cannot be modified using the same method. The modification of the tuning parameters requires that the Global Mirror session be paused and the parameters changed. Then you resume the session with the new tuning parameter values. The modification of the Global Mirror topology requires that you stop the Global Mirror session. Change the topology. Then start Global Mirror processing. The tuning parameters of a Global Mirror session consist of the following: v Consistency Group interval time v Maximum Coordination interval time v Maximum Consistency drain time There are two specific occasions when you might want to modify the tuning parameters: v After the initial setup of your session and your observance of Global Mirror processing indicates that these parameters should be adjusted. v After you have stopped Global Mirror processing as opposed to pausing Global Mirror processing. When you restart Global Mirror processing, the values for the tuning parameters revert to their DS CLI default values. Perform the following steps to modify the tuning parameters of a Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the pausegmir command to pause Global Mirror processing on the specified logical subsystem and the specified session within the logical subsystem. Enter the pausegmir command at the dscli command prompt using the following parameters and variables: dscli>pausegmir -dev storage_image_ID -lss LSS_ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID
dscli>pausegmir -dev IBM.1750-68FA120 -lss 10 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
A confirmation message indicates that the session has been paused after all buffered writes to the target have been processed. 2. Issue the showgmir command to determine what the current properties or performance metrics report for a Global Mirror logical subsystem ID. Enter the showgmir command at the dscli command prompt with the following parameters and variables: For a detailed properties report, use: dscli>showgmir -dev storage_image_ID -fullid LSS_ID For a performance metrics report, use: dscli>showgmir -dev storage_image_ID -metrics LSS_ID These commands are entered as follows when you add values:
dscli>showgmir -dev IBM.1750-68FA120 -fullid 10
171
dscli>showgmir -dev IBM.1750-68FA120 -metrics 10
3. Analyze the report and determine which if any of the Global Mirror tuning parameters must be changed. 4. Issue the resumegmir command with the values for all 3 tuning parameters. Enter the resumegmir command at the dscli command prompt with the following parameters and variables: Note: The example command shows all 3 tuning parameters with new values. You must specify a value for all 3 tuning parameters even if only one value changed. The values for the two unchanged tuning parameters would be the DS CLI default values. dscli>resumegmir -dev storage_image_ID -lss ID -cginterval seconds -coordinate milliseconds -drain seconds -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID
dscli>resumegmir -dev IBM.1750-68FA120 -lss 10 -cginterval 10 -coordinate 60 -drain 35 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
Notes: a. The -cginterval parameter specifies the consistency group interval time, in seconds. The value specifies how long to wait between the formation of consistency groups. If this value is set to zero, consistency groups are formed continuously. The DS CLI default value is 0. b. The -coordinate parameter specifies the maximum coordination interval, in milliseconds. This value indicates the maximum time that Global Mirror processing queues Primary/Host/IO to start forming a consistency group. The DS CLI default value is 50 milliseconds. c. The -drain parameter specifies the maximum time writes are inhibited to the remote site, in seconds. The value indicates the maximum amount of time that writes are inhibited to the remote site before stopping the current consistency group. The DS CLI default value is 30 seconds.
Modifying the topology of a Global Mirror session

Complete this task to modify the topology of a Global Mirror session which is not part of a script. A global mirror session consists of tuning parameters and topology, both of which can be modified. However, they cannot be modified using the same method. The modification of the Global Mirror topology requires that you stop the Global Mirror session, change the topology, and then restart Global Mirror processing. The modification of the tuning parameters is handled differently. Topology in this process refers to the list of storage servers which are subordinates. You establish remote mirror and copy paths between the Master and Subordinate LSSs. Just one LSS per subordinate is sufficient. When you define the remote mirror and copy path you identify the primary LSS on the Master server. The secondary LSS in the remote mirror and copy path establishes command points to a corresponding subordinate server. These LSSs go into the topology specification which defines the communication paths between Master and subordinate storage servers. To change these values you must stop the Global Mirror process.
172
Note: When you restart Global Mirror processing, the tuning parameters revert to their DS CLI default values. Perform the following steps to modify the topology of a Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the showgmir command to display a detailed properties or performance metrics report for a Global Mirror logical subsystem ID. Enter the showgmir command at the dscli command prompt with the following parameters and variables: For a detailed properties report: dscli>showgmir -dev storage_image_ID -fullid LSS_ID For a performance metrics report: dscli>showgmir -dev storage_image_ID -metrics LSS_ID These commands are entered as follows when you add values:
dscli>showgmir -dev IBM.1750-68FA120 -fullid 10 dscli>showgmir -dev IBM.1750-68FA120 -metrics 10
2. Use the report as a guide to see what is currently being processed and to determine what topology values you want to change. 3. Issue the rmgmir command to stop Global Mirror processing. Enter the rmgmir command at the dscli command prompt with the following parameters and variables: dscli>rmgmir -dev storage_image_ID -lss ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
dscli>rmgmir -dev IBM.1750-68FA120 -lss 10 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
Notes: a. This command might interrupt the formation of a consistency group. If, due to failures, this command cannot complete an error code is issued. If this occurs, examine the error code and follow your local procedures for problem determination. In most cases, correcting the error and reissuing the rmgmir command is successful. However, if reissuing the rmgmir command fails and Global Mirror absolutely must be ended, the rmgmir command can be reissued with the -force parameter. b. You cannot use the rmgmir command to stop a script that involves Global Mirror processing. The only way to stop a script is to press the Ctrl C keys on your keyboard. The use of Ctrl C stops the DS CLI session. It does not stop the microcode processing Global Mirror transactions. To stop the microcode processing, you must log back into the DS CLI session and issue the rmgmir command. 4. Enter Y to confirm that you want to stop Global Mirror processing for the specified session. The message is displayed as follows:
Are you sure you want to stop Session ID (xx)? [y/n]: Y Global Mirror for Session ID 01 successfully stopped.
5. Issue the mkgmir command with your changes to the topology values to start Global Mirror processing. Enter the mkgmir command at the dscli command prompt with the following parameters and variables:
173
dscli>mkgmir -dev storage_image_ID -lss ID -session session_ID -cginterval seconds -coordinate milliseconds -drain seconds Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
dscli>mkgmir -dev IBM.1750-68FA120 -lss 10 -session 01 -cginterval 0 -coordinate 40 -drain 35 IBM.1750-68FA120/00:IBM.1750-68FA150/00
Notes: a. You can change your mind and decide not to change any of the topology values. However, you still need to issue the mkgmir command to resume Global Mirror processing when you have stopped the processing. You cannot issue the resumegmir command to start the processing. The resumegmir command is used in conjunction only with the pausegmir command. b. You must enter values for the tuning parameters (-cginterval, -coordinate, -drain) when you restart or start Global Mirror processing.
Viewing a Global Mirror session

Complete this task to view the associated properties of the Global Mirror session or information about the volumes in each session. The lssession command is used to display Global Mirror session information regarding the volumes in each session. Perform the following step to view the associated properties of the Global Mirror session or information about Global Mirror session failures. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. Issue the lssession command to display Global Mirror session information regarding the volumes in each session. Enter the lssession command at the dscli command prompt with the following parameters and variables: dscli>lssession dev storage_image_ID -l LSS_ID Example
Note: v Use the -l parameter if you want to see a detailed report. The report provides you with information like the following: State of the session status. For example, the consistency group of the session is in progress or the increment process is in progress. The status of each volume in the session. Whether the first cycle of the volume in the global mirror relationship has ended. This value is displayed as true or false. v Use the -s parameter if you only want to see the volumes (with no details) associated with each session within the LSS.
174
Querying Global Mirror processing

Complete this task to display detailed properties and performance metrics for a Global Mirror session. The showgmir command to display a detailed report about the current Global Mirror operations and you can also request that the report include the detailed performance metrics. Perform the following step to view the detailed properties and performance metrics for a Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. Issue the showgmir command to display a detailed report about the current Global Mirror operations. Or, you can request a report that displays the performance metrics associated with the current Global Mirror operations. Enter the showgmir command at the dscli command prompt with the parameters and variables shown as follows: For transaction details, enter: dscli>showgmir -dev storage_image_ID LSS_ID For performance metrics, enter: dscli>showgmir storage_image_ID -metrics LSS_ID Examples
dscli>showgmir -dev IBM.1750-68FA120 10 dscli>showgmir -dev IBM.1750-68FA120 -metrics 10
Pausing Global Mirror processing

Complete this task to pause Global Mirror processing. Use the pausegmir command to pause Global Mirror processing. This action allows you to temporarily suspend Global Mirror processing attempts to form consistency groups. There are 2 primary reasons to pause Global Mirror processing: v You must repair a part of the Global Mirror infrastructure, such as: Global Copy volume pairs FlashCopy pairs Storage control unit values v You must make modifications to the Global Mirror tuning parameters Perform the following steps to pause Global Mirror processing. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the pausegmir command to pause Global Mirror processing. Enter the pausegmir command at the dscli command prompt using the following parameters and variables: dscli>pausegmir -dev storage_image_ID -lss LSS_ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
175
2. Use the showgmir command to verify that your changes are correct. When you are ready to resume Global Mirror processing, issue the resumegmir command to continue with the Global Mirror processing. Do not issue the start (mkgmir) command to start Global Mirror processing.
Resuming Global Mirror processing

Complete this task to resume Global Mirror processing after you have paused Global Mirror processing. Note: If you have issued a pausegmir command to pause Global Mirror processing, you should issue the resumegmir command to continue Global Mirror processing. Use the resumegmir command to change your Global Mirror tuning parameters and continue Global Mirror processing. When you change the Global Mirror tuning parameters you must include values for all three parameters (consistency group interval time, coordination interval time, and drain time). You cannot submit a value for just one parameter, even if the two other parameters do not need to be changed. Perform the following steps to resume Global Mirror processing. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. Issue the resumegmir command to continue Global Mirror processing after you have paused Global Mirror processing. Enter the resumegmir command at the dscli command prompt using the following parameters and variables: dscli>resumgmir -dev storage_image_ID -lss LSS_ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
dscli>resumegmir -dev IBM.1750-68FA120 -lss 10 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
Note: If you are making changes to your tuning parameters, your command would look like the following:
In this example the -cginterval parameter was changed while the -coordinate and -drain parameters maintained their DS CLI default values. However, because the -cginterval parameter was changed, all the parameters and their corresponding values must be listed in your command. Otherwise the command fails.
Starting Global Mirror processing

Complete this task to start Global Mirror processing. The volume relationships (paths, pairs, and FlashCopy) plus the creation of a Global Mirror session must be complete before Global Mirror processing can start.
176
Use the mkgmir command to start Global Mirror processing. Perform the following step to start Global Mirror processing. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. Issue the mkgmir command to start Global Mirror processing. Enter the mkgmir command at the dscli command prompt using the following parameters and variables: dscli>mkgmir -dev storage_image_ID -lss LSS_ID -cginterval seconds -coordinate milliseconds -drain seconds -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
dscli>mkgmir -dev IBM.1750-68FA120 -lss 10 -cginterval 0 -coordinate 50 -drain 30 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
Note: Issuing the mkgmir command requires that you specify the tuning parameters. The values for the tuning parameters are not retained when you end Global Mirror processing. So, in the case where you need to change the Global Mirror topology parameters, you need to resubmit the tuning parameters when you restart Global Mirror processing.
Ending Global Mirror processing (script mode)

Complete this task to end Global Mirror processing that is being controlled through a script. The steps in this task should only be taken if there is no alternative. For example a disaster has occurred and you need to immediately stop all processing. There is no way to pause a script. The only way to stop a script is to press the Ctrl C keys. Of course this stops your DS CLI session. It is likely that this action might cause some transactions to remain partly completed and others completely undone. Pressing Ctrl C does not stop Global Mirror processing which is controlled through the microcode. To stop the microcode processing of Global Mirror operations you must log back into a DS CLI session and issue the rmgmir command. This task does not provide the detailed instructions for recovery as these are related to the failover and failback tasks described in the Recovering when a disaster strikes scenario. Perform the following step when you need to end Global Mirror processing that is using a script. 1. Press the Ctrl C keys to immediately end The DS CLI session. 2. Log back into a DS CLI session and enter the rmgmir command to stop the microcode processing of the Global Mirror operations. 3. Proceed with the steps described in the Recovering when a disaster strikes scenario.
Ending Global Mirror processing (no script)

Complete this task to end Global Mirror processing that is not being controlled through a script.
177
To use this task your Global Mirror processing cannot be controlled through a script. You can use this task when you must end Global Mirror processing to change the topology of a Global Mirror session or when you have time (because of a rolling disaster) to end processing even though a disaster has occurred. The rmgmir command is used to end Global Mirror processing. Note: This command might interrupt the formation of a consistency group. If, due to failures, this command cannot complete an error code is issued. If this occurs, examine the error code and follow your local procedures for problem determination. In most cases, correcting the error and reissuing the rmgmir command is successful. However, if reissuing the rmgmir command fails and Global Mirror absolutely must be ended, the rmgmir command can be reissued with the -force parameter. Perform the following steps to end Global Mirror processing. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the rmgmir command to end Global Mirror processing. Enter the rmgmir command at the dscli command prompt using the following parameters and variables: dscli>rmgmir -dev storage_image_ID -lss LSS_ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
2. Enter Y in response to each message that requests that you confirm that you want the specified session stopped. A message similar to the following appears when you process the rmgmir command.
Are you sure you want to stop Session ID 01? [y/n]: Y Global Mirror for Session ID 01 successfully stopped.
Setting up the Global Mirror Environment

This task lists the high-level steps that you must complete in order to set up the Global Mirror environment to allow Global Mirror processing. Each of these steps must be completed in the order in which they are shown before you can move onto the next step. 1. Create fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. See Creating fibre-channel paths (Global Mirror setup) on page 179 for additional steps. 2. Create Global Copy pairs from the local storage units to the remote storage units. See Creating Global Copy pairs (Global Mirror setup) on page 181 for additional information. 3. Create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. See Creating FlashCopy relationships (Global Mirror setup) on page 182 for additional information. 4. Create the Global Mirror session. See Creating the Global Mirror session on page 183 for additional information.
178
Creating fibre-channel paths (Global Mirror setup)

Complete this task to create fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. This is the first step in setting up your Global Mirror environment. Create paths so that the logical subsystems (LSSs) are associated with each other. These are the ports that the copy services I/O pass through. It is preferred that they are not the same ports that are used for host I/O. This ensures that there is enough capacity for the data transfer. Perform the following steps to create fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Obtain the worldwide node name of the secondary storage unit. This information is needed when you do the next step. Enter the lssi or showsi at the dscli command prompt as follows:
dscli>lssi -l
This is the entire command. there are no additional variables needed. The showsi command does contain a variable and a command flag: dscli>showsi storage_image_id -fullid Example
dscli>showsi -fullid IBM.1750685FA120
Notes: a. Use the lssi command if you want to display a list of all the storage image instances for a storage-complex and status information for each storage image in the list. b. Use the showsi command if you want to display the detailed properties of a specific storage unit. c. Use the -fullid DS CLI command flag with the showsi command to display fully qualified IDs, which include the storage image ID, for every ID that is displayed in the command output. d. Record the worldwide node name for the secondary (target) storage unit so that it can be used when you issue the mkpprcpath command. 2. Issue the lsavailpprcport command to display a list of fibre-channel I/O ports that can be defined as remote mirror and copy paths. Enter the lsavailpprcport command at the dscli command prompt with the parameters and variables shown as follows: dscli>lsavailpprcport -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn source_LSS_ID:target_LSS_ID Example
dscli>lsavailpprcport l dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 remotewwnn 12341234000A000F 01:01
Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit.
179
b. The -remotewwnn parameter must specify the worldwide node name of the secondary storage unit. If you make a mistake and specify the worldwide node name of the primary storage unit, the command fails. c. The shortened version of the source_LSS_ID:target_LSS_ID parameter is shown (value = 01:01) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_immage_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified source_LSS_ID:target_LSS_ID value. For example: IBM.1750-68FA120/01:IBM.1750-68FA150/01 The fully qualified source_LSS_ID:target_LSS_ID value must be placed after the -remotewwnn value in your command line. For example, your command line would look like the following:
3. Issue the mkpprcpath command to create the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables as follows: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -remotewwnn 12341234000A000F -srclss 00 -tgtlss 01 I1A10:I2A20
Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit. b. The -remotewwnn parameter must specify the worldwide node name of the secondary storage unit. If you make a mistake and specify the worldwide node name of the primary storage unit, the command fails. c. The shortened version of the -srclss parameter is shown (value = 00) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter was not used, you must use the fully qualified -srclss source_LSS_ID value. For example: -srclss IBM.1750-68FA120/00. d. The shortened version of the -tgtlss parameter is shown (value = 01) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter was not used, you must use the fully qualified -tgtlss target_LSS_ID value. For example: -tgtlss IBM.1750-68FA120/01. e. The shortened version of the source_port_ID:target_port_ID parameter is shown (value = I1A10:I2A20) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_immage_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified source_port_ID:target_port_ID value. For example: IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20.
180
The fully qualified source_port_ID:target_port_ID parameter is positional on your command line. It must be placed after the -tgtlss parameter and value. For example:
Creating Global Copy pairs (Global Mirror setup)

Complete this task to create Global Copy pairs from the local storage units to the remote storage units. This is the second step in setting up your Global Mirror environment. Ensure that the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units have been created. The purpose of this step is to create a relationship between a source volume and a target volume. Perform the following steps to create Global Copy pairs from the local storage units to the remote storage units. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the mkpprc command to create a Global Copy pairs from the local storage unit to the remote storage unit and to create a relationship between the associated source volume and target volume. Enter the mkpprc command at the dscli command prompt with the parameters and variables shown as follows: : dscli>mkpprc -dev storage_imag_ID -remotedev storage_image_ID -type gcp SourceVolumeID:TargetVolumeID. Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -type gcp 0100:0100
Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit. b. The -type gcp parameter specifies that one or more remote mirror and copy Global Copy volume relationships be established. Global Copy maintains the remote mirror and copy relationship in a nonsynchronous manner. I/O write completion status is returned to the application when the updates are committed to the source. c. The shortened version of the SourceVolumeID:TargetVolumeID parameter is shown (value = 0100:0100) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 . The use of this parameter is positional. It must be placed after the -type parameter. For example:
dscli>mkpprc -type gcp IBM.1750-68FA120/0100:IBM.1750-68FA150/0100
A confirmation message is issued for each successful Global Copy volume association that is created.
181
2. Issue the lspprc command to check the status information for each remote mirror and copy volume relationship in the list. A report is displayed and you should see that each Global Copy relationship you have created has a status of copy pending. Enter the lspprc command at the dscli command prompt with the parameters and variables shown as follows: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID. Example
Use the -l parameter to provide a more detailed report about the Global Copy volume relationships. It is recommended that wait until the Global Copy pair process has completed its first pass before you begin creating the FlashCopy relationships. Note: Global Copy source volumes are not in the active Global Mirror session until the volumes have been added to the session and the session started. So you need to add the volumes to the session, establish the pairs, let the first pass complete, establish the FlashCopy relationships (BACKGROUND NOCOPY, change recording, inhibit target write), and then start the session.
Creating FlashCopy relationships (Global Mirror setup)

Complete this task to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. This is the third step in setting up your Global Mirror environment. v Ensure that the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units have been created. v Ensure that the Global Copy pairs have been created between the local storage units and the remote storage units. The purpose of this step is to create a FlashCopy target for the Global Mirror pairs. Perform the following steps to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the mkflash command to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. Enter the mkflash command at the dscli command prompt as follows: The mkflash command must contain the following parameters and variables as follows: dscli>mkflash -dev storage_image_ID -tgtinhibit -persist -record -nocp sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 -tgtinhibit -record -persist -nocp 0001:0004
Notes: a. Specify the secondary storage unit MTS for the -dev storage_image_ID parameter. If the management console has an IP connection to the specified remote async site the command works. If the IP connection is not established you must use the mkremoteflash command with all the same parameters as displayed in the example.
182
b. Use the -tgtinhibit parameter to inhibit writes on the target volume. c. Use the -record parameter to activate change recording on the volume pair. d. Use the -persist parameter to retain the FlashCopy relationship after the background copy completes. e. Use the -nocp parameter to inhibit the background copy. A confirmation message is issued for each successful FlashCopy pair that is created. 2. Issue the lsflash command to check the status information for each FlashCopy relationship at the remote site. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l SourceVolumeID:TargetVolumeID.
Use the -l parameter to provide a more detailed report about the FlashCopy relationships. Note: If you used the mkremoteflash command, you must enter the lsremoteflash command to perform a status check.
Creating the Global Mirror session

Complete this task to create a Global Mirror session. This is the fourth step in setting up your Global Mirror environment. After you complete this step you are ready to start Global Mirror processing. v Ensure that the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units have been created. v Ensure that the Global Copy pairs have been created between the local storage units and the remote storage units. v Ensure that the FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes have been created. The purpose of this step is to create a container to associate volumes to a Global Mirror session. Perform the following steps to create the Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the mksession command to create the Global Mirror session. Enter the mksession command at the dscli command prompt using the parameters and variables shown as follows: dscli>mksession -dev storage_image_ID -lss LSS_ID -volume volume_ID Session_ID Example
dscli>mksession -dev IBM.1750-68FA120 -lss 10 -volume 0800-0810 01
2. Repeat Step 1 for each LSS. You must make a session for each LSS. However, you can associate each LSS to the same session. For example: You have LSS 08 and it contains volumes 0800-0810. You create a session and assign it to session 08. You also have LSS 09 and it contains volumes 0900-0910. You create a session and assign it to session
183
08. When you start Global Mirror processing the volumes for LSS 8 and LSS 9 are processed in the same session (session 08).
Removing a Global Mirror environment

This task lists the high-level steps that you must complete in order to remove the Global Mirror environment from your system. The removal of a Global Mirror environment is prompted by circumstances similar to the following: v You decide that you want to run with a totally different configuration. v You were running a test and the volumes you were using you never want to use for an asynchronous pair again. Each of the following steps must be completed in sequence before you can move on to the next step. 1. Remove all Global Copy primary volumes from the Global Mirror sessions. See Removing volumes from a session (Global Mirror) for additional information. 2. End the Global Mirror sessions. See Ending a Global Mirror session on page 185 for additional information. 3. Withdraw all FlashCopy relationships between the B and C volumes. See Removing FlashCopy relationships on page 186 for additional information. 4. Remove the Global Copy pair relationships. See Removing the Global Copy pair relationship on page 187 for additional information. 5. Remove the remote mirror and copy paths between the local site and the remote site. Removing the fibre-channel paths on page 188 for additional information.
Removing volumes from a session (Global Mirror)

Complete this task to remove volumes from a Global Mirror session. This task is also the first step in removing the Global Mirror environment from your system. Ensure that you have closed the Global Mirror sessions associated with the Global Mirror environment if you are processing this task as part of removing the Global Mirror environment from your system. This task covers two circumstances v removing volumes from a session without removing the session from Global Mirror processing v removing all volumes from each session as part of the steps for removing the Global Mirror environment from your system. You can remove Global Copy primary volumes from a Global Mirror session at any time after the Global Mirror session has started without stopping the session. If you have many volumes that you want to remove from a Global Mirror session, you might consider removing them from the session in stages. This lessens the impact on your processing. If you intend to use the volumes in a different configuration, you must remove the pair and path associations. Removing a volume from a Global Mirror session does not remove the pair and path associations. Perform the following steps to remove volumes from a Global Mirror session. The example commands in this task are shown in two formats. The first format shows
184
the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the lssession command to query the status of all volumes that are associated with the sessions of a specified logical subsystem. Enter the lssession command at the dscli command prompt with the following parameters and variables: dscli>lssession dev storage_image_ID -l LSS_ID
When you use the -l parameter, a detailed report displays a list of Global Mirror sessions for the specified logical subsystem (LSS) and information regarding the volumes of each session in the list. 2. Analyze the report and determine which volumes you want to remove. 3. Issue the chsession command to remove the specified volumes from the specified Global Mirror session. Enter the chsession command at the dscli command prompt with the parameters and variables shown as follows: dscli>chsession -dev storage_image_ID -lss LSS_ID -action remove -volume volume_ID session_ID Example
dscli>chsession -dev IBM.1750-68FA120 -lss 10 -action remove -volume 0100-010F,0180-018F,0120 01
A confirmation message indicates that the session has been modified successfully. Note: A volume ID range is defined by two volume IDs that are separated by a hyphen. Multiple volume IDs or volume ID ranges must be separated by a comma. After the volumes have been removed from the Global Mirror session, you must end the volume associations for the removed volumes (FlashCopy, Global Copy pair, and remote mirror and copy path) if you plan to use the volumes in a different configuration.
Ending a Global Mirror session

Complete this task to end a Global Mirror session. In addition to ending a single session, this task is also the second step that you use when you remove the Global Mirror environment from your system. Each session that you have created for Global Mirror processing must be ended individually. You cannot designate that a range of sessions be closed. Ending a session does not remove the volume or path associations. Each of these must be removed in their own way. Perform the following steps to close a Global Mirror session. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the lssession command to obtain a list of all sessions associated with the specified logical subsystem. Enter the lssession command at the dscli command prompt with the parameters and variables shown as follows: dscli>lssession -dev storage_image_ID -s LSS_ID Example
dscli>lssession dev IBM.1750-68FA120 -s 01
185
Note: For the circumstance described in this task, it is better to issue the -s parameter. The -s parameter causes a report with the following 3 pieces of information to display: v LSSID v Session number v Volume numbers 2. Print the report or record the session numbers that need to be closed. 3. Issue the rmsession command to close the specified session. Enter the rmsession command at the dscli command prompt with the parameters and variables shown as follows: dscli>rmsession -dev storage_image_ID -lss ID session_ID Example
dscli>rmsession -dev IBM.1750-68FA120 -lss 10 01
4. Enter Y to respond to the message that requests that you confirm you want the specified session stopped. A message similar to the following appears when you process the rmsession command.
Are you sure you want to stop Global Mirror Session ID 01? y/n Y Global Mirror Session ID 01 successfully stopped
5. Repeat Step 3 for each session that needs to be closed.
Removing FlashCopy relationships

Complete this task to remove FlashCopy relationships that exist with the volumes that are part of your Global Mirror environment. In addition, this task is the third step in removing the Global Mirror environment from your system. Ensure that the following tasks have been completed before invoking this step when you are removing your Global Mirror environment: v Remove the volumes that are associated with each Global Mirror session you have closed. v End the Global Mirror sessions that are part of your Global Mirror environment. If you attempt to remove the FlashCopy relationships (as part of removing the Global Mirror environment) before doing the first two tasks, this task fails. This task step only applies as part of the removal of your Global Mirror environment. Note: Make certain that you no longer need your consistent set of data before you withdraw your relationships. If you still need your consistent data perform a backup data before proceeding with this task. Perform the following steps to remove FlashCopy relationships that existed with the volumes that were part of your Global Mirror environment. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. 1. Issue the lsflash command to check the status information for each FlashCopy relationship at the remote site. A detailed report (when you use the -l parameter) is displayed for each FlashCopy relationship. Enter the lsflash command at the dscli command prompt with the parameters and variables shown as follows: dscli>lsflash -dev storage_imag_ID -l SourceVolumeID:TargetVolumeID.
186
Use the -l parameter to provide a more detailed report about the FlashCopy relationships. Note: If you originally used the mkremoteflash command to create your FlashCopy relationships, you must enter the lsremoteflash command to perform a status check. 2. Analyze the list of volumes that have been part of your Global Mirror environment and ensure that these are the volumes from which the FlashCopy relationship must be removed. 3. Issue the rmflash command to remove the FlashCopy volume relationships. Enter the rmflash command at the dscli command prompt with the parameters and variables shown as follows: dscli>rmflash -dev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>rmflash -dev IBM.1750-68FA120 0001:0004 0003:00FF 0008:000C
Note: v The example shows the use of multiple FlashCopy pair IDs. Ensure that you separate multiple FlashCopy pair IDs with spaces. v If you used the mkremoteflash command to create your FlashCopy relationships, you must enter the rmremoteflash command to remove the FlashCopy relationships. 4. Enter Y in response to each message that requests that you confirm that you want the specified FlashCopy pair removed. A message similar to the following appears for each FlashCopy pair being removed when you process the rmflash command.
Are you sure you want to remove the FlashCopy pair 0001:0004? [y/n]: Y FlashCopy pair 0001:0004 successfully removed.
Removing the Global Copy pair relationship

Complete this task to remove Global Copy relationships that existed with the volumes that were part of your Global Mirror environment. This task is the fourth step in removing the Global Mirror environment from your system. Ensure that you have completed the following tasks before initiating this task otherwise this task fails: v Remove the volumes that are associated with each Global Mirror session you have closed. v End the Global Mirror sessions that are part of your Global Mirror environment. v Remove FlashCopy relationships that existed with the volumes that were part of your Global Mirror environment. The purpose of this task is to remove the Global Copy relationships for each pair of source volumes on your primary site and the target volumes on your secondary site. There might be several LSSs involved and the Global Copy relationships must be removed within each LSS. This requires that you repeat the remove command for each LSS until all relationships are removed. Perform the following steps to remove Global Copy pair relationships that existed with the volumes that were part of your Global Mirror environment. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables.
187
1. Issue the lspprc command to check the status information for each Global Copy volume relationship in the list. Enter the lspprc command at the dscli command prompt with the parameters and variables shown as follows: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID. Example
Use the -l parameter to provide a more detailed report about the Global Copy volume relationships. 2. Analyze the list of volumes that have been part of your Global Mirror environment and ensure that these are the volumes from which the Global Copy relationships must be removed. 3. Issue the rmpprc command to remove the Global Copy volume relationships. Enter the rmpprc command at the dscli command prompt with the parameters and variables shown as follows: dscli>rmpprc -dev storage_image_ID -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
4. Enter Y in response to each message that requests that you confirm that you want the specified Global Copy pair removed. A message similar to the following appears for each Global Copy pair being removed when you process the rmflash command.
Are you sure you want to remove PPRC pair 0100:0100? [y/n]: Y Remote Mirror and Copy pair IBM.1750-68FA120/0100:0100 successfully removed.
5.
Repeat Step 3 for all the volumes that have Global Copy relationships in the LSSs that were part of your Global Mirror environment.
Removing the fibre-channel paths

Complete this task to remove the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. This is the fifth and final step you use when you remove the Global Mirror environment from your system. Ensure that the following tasks have been completed before you initiate this task, otherwise this task fails: v Remove the volumes that are associated with each Global Mirror session you have closed. v Close the Global Mirror sessions that are part of your Global Mirror environment. v Remove FlashCopy relationships that existed with the volumes that were part of your Global Mirror environment. v Remove the Global Copy relationships that existed with the volumes that were part of your Global Mirror environment. You need to repeat the process described for issuing the remove command (rmpprcpath) for each data path (between LSSs on the source Storage Images on the primary site and the target LSSs on the target Storage Images on secondary site) and for each control path (between the Master Storage Image LSS and the Subordinate Storage Image LSSs).
188
Perform the following steps to remove the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. The example commands in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with values declared for the variables. 1. Issue the lspprcpath command to display a list of existing remote mirror and copy path definitions. Enter the lspprcpath command at the dscli command prompt with the parameters and variables shown as follows: dscli>lspprcpath -dev storage_image_ID source_LSS_ID Example
dscli>lspprcpath l dev IBM.1750-68FA120 01
Note: The report displayed from this command provides the worldwide node name (WWNN) that is used with the rmpprcpath command. 2. Record the path information for use when issuing the rmpprcpath command. 3. Issue the rmpprcpath command to remove the fibre-channel paths between all Global Mirror source and target pairs and between the Master and subordinate storage units. Do this for each path that must be removed. Enter the rmpprcpath command at the dscli command prompt with the parameters and variables shown as follows: dscli>rmpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn source_LSS_ID:target_LSS_ID Example
4. Enter Y in response to each message that requests that you confirm that you want the specified remote mirror and copy path removed. A message similar to the following appears for each remote mirror and copy path being removed when you process the rmpprcpath command.
Are you sure you want to delete PPRC path (whatever was designated)? [y/n]: Y PPRC path (designated in the command) successfully deleted.
5.
Repeat Step 3 for all the remote mirror and copy paths per LSS that were part of your Global Mirror environment.
After this task is complete, you can create your new Global Mirror environment and configuration.
189
190
Chapter 7. Recovering from a disaster using Global Mirror

This task lists the high-level steps that you must complete in order to recover from a disaster using Global Mirror processing. A failure at the local or primary site stops all I/O to and from the local storage server. The local server cannot communicate with the remote sites. This might impact the formation of consistency groups, because the entire process is managed and controlled by the master storage server, which is the primary storage server. Your initial goal is to swap operations between the local and remote sites and then restart the applications. This requires that you make available a set of consistent volumes at the remote site, before the application can restart at the remote site. When the local site is operational again, you want to return processing to the local site. Before you can return processing to the local site, you must apply changes from the remote site to the local site. These changes are the transactions that occurred after you started failover processing to the remote site. The following considerations can help you determine where transactions are being processed: v The local site contains A volumes (the source volume), which are copied to the recovery site using Global Copy v The recovery (or remote) site contains B volumes (the target volume and FlashCopy source volume) and C volumes (the FlashCopy target volume) v A storage unit at the local site is designated as the Global Mirror master and all other local (or production) storage units are designated as subordinate storage units. The master storage unit sends commands to its subordinate storage units. These subordinates work together to create a consistency group and to communicate the FlashCopy commands to the recovery (or remote) site. All status is relayed back to the Global Mirror master. To recover from a disaster, you must perform the following high-level tasks using the Global Mirror function and the DS CLI commands: 1. End Global Mirror processing when a disaster occurs. See Ending Global Mirror processing when a disaster occurs on page 192 for additional substeps. 2. Check the status of the current processing for Global Mirror transactions. See Checking Global Mirror transaction status in a disaster situation on page 193 for additional substeps. 3. Initiate the failover process of A volumes to B volumes. See Initiating failover processing for B volumes to A volumes on page 194 for additional substeps. 4. Analyze the consistency group status. See Analyzing and validating the consistency group state on page 195 for additional substeps. 5. Use the revertflash command to correct FlashCopy relationships. See Using the revertflash command to correct FlashCopy relationships on page 197 for additional substeps. 6. Use the commitflash command to correct FlashCopy relationships. See Using the commitflash command to correct FlashCopy relationships on page 198for additional substeps.
191
7. Initiate the fast reverse restore process. See Using fast reverse restore processing to create consistency on page 199 for additional substeps. 8. Wait for the background copy to complete. See Waiting for the background copy to complete on page 200 for additional substeps. 9. Reestablish the FlashCopy relationships, B volumes to C volumes. See Reestablishing the FlashCopy relationships between B volumes and C volumes on page 201 for additional substeps. 10. Prepare to reinstate production at the local site. See Preparing to reinstate production at the local site on page 202 for additional substeps. 11. Resynchronize the volumes. See Resynchronizing the volumes on page 203 for additional substeps. 12. Query for first pass and drain time out-of-synch zero value and quiesce your system. See Querying, quiescing, and querying on page 204 for additional substeps. 13. Reestablish the remote mirror and copy paths, A site to B site. See Reestablishing remote mirror and copy paths (site A to site B) on page 205 for additional substeps. 14. Perform Global Copy failover processing to the A volumes. See Performing Global Copy failover processing to the A volumes on page 207 for additional substeps. 15. Perform Global Copy failback processing for the A volumes. See Performing Global Copy failback processing for the A volumes on page 207 for additional substeps. 16. Resume Global Mirror processing at site A. See Resuming Global Mirror processing at site A on page 208 for additional substeps.
Ending Global Mirror processing when a disaster occurs

Complete this task to end Global Mirror processing when a disaster occurs. This is the first step in the Global Mirror disaster recovery process, when possible. Depending on the state of the local Global Mirror storage server, you might have an opportunity to end Global Mirror processing before initiating the rest of the recovery steps. Generally a disaster affects your local server and your choices for ending Global Mirror processing in one of the following ways: v You experience a rolling disaster and your Global Mirror processing is not being done through a DS CLI script. This circumstance allows you time to initiate some planning by issuing a pause command, followed by a query command, and then issuing the end Global Mirror processing command. Note: If the query displays a status of Fatal or a null (-) you must analyze and correct your consistency groups during the recovery process. If the query displays a status of Paused your consistency groups are formed before you end Global Mirror. v You experience a rolling disaster and your Global Mirror processing is being done through a DS CLI script. You can take a chance that you have enough time to allow the script to process to the end. However, it is likely that you will have to end Global Mirror processing by pressing the CTRL C buttons on your keyboard because there is no pause feature when running a script. Because this is a rolling disaster you might have time to log back into your DS CLI session on the local server and query the status of the Global Mirror processing before it was ended.
192
v Your local server is affected immediately and you have no time to end Global Mirror processing or issue a status query. When possible, you want to end Global Mirror processing. Perform the following step to end Global Mirror processing. Issue the rmgmir command to end Global Mirror processing or press the CTRL C buttons when you are using a DS CLI script and then issue the rmgmir command. After Global Mirror processing has been ended, you are ready for the next step in the Global Mirror failover recovery process.
Checking Global Mirror transaction status in a disaster situation

Complete this task to check the status of your Global Mirror transactions before processing was ended as a result of the disaster. This is the second step in the Global Mirror failover recovery process when you have time because of dealing with a rolling disaster and your primary server is still operational. This might be the first step if your primary server is not operational. You must end Global Mirror processing before you initiate this task. You must determine where Global Mirror processing was before processing was ended. Some transactions might be half completed while others were not yet started. Querying the status of your transactions provides a basis for planning what must be done next. The situation you face is similar to the following: v The formation of a consistency group was in progress and the FlashCopy state between the B volumes and the C volumes in the remote storage server are not the same at the for all relationships when Global Mirror processing was ended. v Some FlashCopy pairs might have completed the FlashCopy phase of Global Mirror processing to form a new consistency group and already committed the changes. v Some FlashCopy pairs might not have completed yet and are in the middle of processing to form their consistent copy and remain in a revertible state. v There is no master server that controls and coordinates what might still go on for a brief period at the remote site. Perform the following steps to obtain an initial idea of the status of your transactions. 1. Issue the lssession and lspprc commands to obtain reports that allow you to determine the status of your Global Mirror transactions, if your primary server is still operational. If your primary server is not available, go to the next step. 2. Gain access to your remote server and navigate to the directory where you installed the DS CLI application. 3. Log in to a DS CLI session. 4. Issue the lspprc command to provide a report that allows you to determine the status of your Global Mirror transactions. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -l 0100-0103:0100-0103 0200:0200 0300-0303:0300-0303
193
Note: The report displays your Global Copy pairs with a suspended state. After you have your reports, you are ready for the next step in the Global Mirror disaster recovery process which is to issue the failover command.
Initiating failover processing for B volumes to A volumes

Complete this task to initiate failover processing for B volumes to A volumes so that the B volumes become the primary volumes and A volumes become the secondary volumes. The effect is that the Global Copy state of the B volumes changes from secondary to primary and suspended. This is the next step after obtaining a status of your Global Mirror transactions in the Global Mirror failover recovery process. The failover task cannot be done unless you have completed the following: v Ended Global Mirror processing. v Obtained the report or reports that help you determine the status of your Global Mirror transactions before the disaster occurred. You must issue a recovery failover request on the Global Copy volumes pair to force a stop of the A Volume to B Volume extended distance relationship and create a B Volume to A Volume Global Copy relationship. A failover to the Global Copy secondary volume turns the secondary volumes into primary volumes and suspends these volumes immediately. When you run a Global Copy Failover, the B volumes are the primary volumes and the A volumes are the secondary volumes. This action just changes the Global Copy state of the secondary volumes from Target Copy Pending to Suspended. Perform the following step to fail over the B volumes to A volumes. The example commands that are displayed in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the failoverpprc command to change the Global Copy state on the B volumes from secondary, target pending to primary, suspended. Enter the failoverpprc command at the dscli command prompt with the following parameters and variables: dscli>failoverpprc -dev storage_image_ID -remotedev storage_image_ID SourceVolumeID:TargetVolumeID Example
dscli>failoverpprc -dev IBM.1750-68FA150 -remotedev IBM.1750-68FA120 0100:0100 0101:0101 0102:0102 0103:0103
Note: Unlike most other commands, the values for the storage_image_ID and SourceVolumeID:TargetVolumeID are reversed in the failoverpprc command. That is, the command is issued directly to the remote server. So, the values for the remote server are first and the values for the original primary server are second. A role reversal is affected so that the remote becomes the primary server. This results in the following: v The source volumes show as suspended host. v The target volumes show as suspended target and they are accessible for mounting.
194
A confirmation message like the following is generated for each Global Copy pair that has been changed and moved to a state of suspended.
PPRC pair IBM.1750-68FA150/0100:IBM.1750-68FA120/0100 successfully suspended.
Note: All B volumes must successfully process the failoverpprc command before you can move on to the next step. After all the B volumes have been processed, you are ready for the next step which involves analyzing the FlashCopy relationships and initiating the appropriate commands.
Analyzing and validating the consistency group state

Complete this task to analyze and validate the consistency group state. This is the fourth step in the Global Mirror failover recovery process. Before you can initiate this task, you must ensure that the following tasks have been completed: v Global Mirror processing has been ended at the primary server site. v The status of Global Mirror transaction processing before the disaster caused the process to end has been obtained. v Failover processing from B volumes to A volumes has completed with the B volumes state being changed from a secondary, target pending state to a primary, suspended state. The consistency group state must be validated. This means that you must investigate whether all FlashCopy relationships are in a consistent state. Query the FlashCopy relationships that exist between B volumes and C volumes to determine the state of the FlashCopy relationship at the time that the primary server experienced a failure. Global Mirror might have been in the middle of forming a consistency group and FlashCopy might not have completed so as to create a complete set of consistent C volumes. When you query a FlashCopy pair, there are two key pieces of information, that determine whether the C volume set is consistent or needs intervention to correct some states. Revertible status The revertible status is indicated as Enable or Disable and shows whether the FlashCopy is revertible or nonrevertible. A nonrevertible state means that a FlashCopy process has completed successfully and all changes are committed. Sequence number The sequence number indicates the number of the actual or last FlashCopy process (if the FlashCopy process is finished). There are some combinations of revertible states and FlashCopy sequence numbers that require different corrective actions; this is, what you are looking for when you do your analysis. Perform the following steps to analyze and validate the consistency group state. The example command displayed in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables.
195
1. Issue the lsflash command to provide a report that lists the FlashCopy relationships and status information for each FlashCopy relationship in the list. Enter the lsflash command at the dscli command prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -l source_volume_ID:target_volume_ID Example
Remember that at this point your remote server has become your primary server. 2. Analyze your report to determine the state of the consistency group between the B volume and C volume. You are looking primarily at the FlashCopy relationships and your analysis determines your next step in the recovery process. The following provides the types of FlashCopy relationships that might exist and a reference to the action that must be taken: v The FlashCopy relationships are nonrevertible and all the sequence numbers are equal. Action: No further action is necessary and the set of C volumes is consistent and a complete copy. v The FlashCopy relationships are revertible and all the sequence numbers are equal. Action: Issue the revertflash command to revert the FlashCopy pairs to the last consistency group. v All the FlashCopy sequence numbers are equal and at least one of the FlashCopy relationships is nonrevertible. Action: Issue the commitflash command to commit the data to a target volume to form a consistency group between the source and target. v The FlashCopy relationships appear as follows: a. Some of the FlashCopy relationships completed processing so that a consistent group was created. These FlashCopy relationships are no longer revertible. b. Some of the FlashCopy relationships have not completed creating a new consistency group formation. They are still in a revertible state. c. All the FlashCopy relationships have the same FlashCopy sequence number. This indicates that all the FlashCopy relationships were involved in the very same consistency group. Action: Issue the commitflash command to commit the data of the FlashCopy relationships that have not completed creating a new consistency group so that a consistency group is formed. v There is a group of FlashCopy pairs that are all revertible and another group of FlashCopy pairs that are all nonrevertible. In addition, all the FlashCopy sequence numbers are not equal. However, the following conditions exists: a. The FlashCopy sequence number for all revertible pairs is equal. b. The FlashCopy sequence number for all nonrevertible pairs is equal. Action: Issue the revertflash command to revert the FlashCopy pairs to the last consistency group. v The FlashCopy sequence numbers are not equal for all FlashCopy relationships in the concerned consistency group and either a or b in the previous bullet was not true. This indicates that the consistency group is corrupted. Action: Contact your IBM service representative. Note: When you know the state of all the FlashCopy relationships, you might want to initiate a tape backup of the C volume.
196
After determining the state of the FlashCopy relationships, issue the revertflash or commitflash commands, as appropriate.
Using the revertflash command to correct FlashCopy relationships

Complete this task to correct the revertible states and FlashCopy sequence numbers that require the use of the DS CLI revertflash command. This is the fifth step in the Global Mirror failover recovery process unless your corrections require the use of the commitflash DS CLI command. In this case, the use of the commitflash command becomes your fifth step. You can use the revertflash command only when your analysis of the FlashCopy relationships reveals one of the following conditions: v The FlashCopy relationships are revertible and all the sequence numbers are equal. v There is a group of FlashCopy pairs that are all revertible and another group of FlashCopy pairs that are all nonrevertible. In addition, all the FlashCopy sequence numbers are not equal. However, the following conditions exist: The FlashCopy sequence number for all revertible pairs is equal. The FlashCopy sequence number for all nonrevertible pairs is equal. The revert action removes the FlashCopy relationship changes and resets them to the last consistency group state. The revertible state is set to No. Perform the following step to correct the applicable FlashCopy relationships. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the revertflash command to correct the FlashCopy relationships and reset them to the last consistency group state. Enter the revertflash command at the dscli command prompt with the following parameters and variables: dscli>revertflash -dev storage_image_ID SourceVolumeID Example
Notes: 1. Remember that the storage_image_ID is the value for the remote server that has been designated the primary server until the original primary server is available for use. 2. Global Mirror operations have performed the establish FlashCopy revertible processing as it was trying to form a consistency group before the disaster occurred. If your analysis, through use of the lsflash command, has determined that a revertflash command is needed, then there is no need to issue a new mkflash command. A confirmation message like the following one is generated for each FlashCopy relationship that has been successfully reset.
FlashCopy pair 0100:0200 successfully reverted to the previous consistency.
197
After all the FlashCopy relationships have been corrected, you are ready to use the fast reverse restore process, which is the next step in the Global Mirror disaster recovery process.
Using the commitflash command to correct FlashCopy relationships

Complete this task to correct the revertible states and FlashCopy sequence numbers that require the use of the DS CLI commitflash command. This is the fifth step in the Global Mirror failover recovery process unless your corrections require the use of the revertflash DS CLI command. In this case, the use of the revertflash command becomes your fifth step. You can use the commitflash command only when your analysis of the FlashCopy relationships reveals one of the following conditions: v All the FlashCopy sequence numbers are equal and at least one of the FlashCopy relationships is nonrevertible. v The FlashCopy relationships appear as follows: Some of the FlashCopy relationships completed processing so that a consistent group was created. These FlashCopy relationships are no longer revertible. Some of the FlashCopy relationships have not completed creating a new consistency group formation. These FlashCopy relationships are still in a revertible state. All the FlashCopy relationships have the same FlashCopy sequence number. This indicates that all the FlashCopy relationships were involved in the very same consistency group. The commit action keeps a FlashCopy relationship in its current state and resets the revertible state to No. When the commitflash command is processed, the data in these relationships is committed to the consistency group to which it would have become a part of before the disaster occurred. Perform the following step to correct the applicable FlashCopy relationships. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the commitflash command to correct the FlashCopy relationships and commit them the consistency group that was being formed before the disaster occurred. Enter the commitflash command at the dscli command prompt with the following parameters and variables: dscli>commitflash -dev storage_image_ID SourceVolumeID Example
dscli>commitflash -dev IBM.1750-68FA150 0100
Notes: 1. Remember that the storage_image_ID is the value for the remote server that has been designated the primary server until the original primary server is available for use. 2. Global Mirror operations have performed the establish FlashCopy revertible processing as it was trying to form a consistency group before the disaster occurred. If your analysis, through use of the lsflash
198
command, has determined that a commitflash command is needed, then there is no need to issue a new mkflash command. A confirmation message like the following one is generated for each FlashCopy relationship that has been successfully reset.
FlashCopy pair 0100:0200 successfully committed.
After all the FlashCopy relationships have been corrected, you are ready to use the fast reverse restore process, which is the next step in the Global Mirror disaster recovery process.
Using fast reverse restore processing to create consistency

Complete this task to create the same consistent data on the B volumes that you have on the C volumes. The fast reverse restore option allows you to reverse a FlashCopy relationship without waiting for the background copy of a previous FlashCopy operation to finish. This is the sixth step in the Global Mirror disaster recovery process. The fast reverse restore option reverses a FlashCopy target volume and allows consistent data to be copied back to its associated source volume, without having to wait for the background copy from the original source to the original target to complete. You can then vary the volumes online and start your applications. Fast reverse restore processing creates a background copy of all tracks that changed on the B volume since the last consistency group formation. This results in the B volume becoming the same as the image that was present on the C volume. However, this process ends the FlashCopy relationship, so that the C volume is no longer usable. Use the DS CLI reverseflash command with the -fast parameter to accomplish this task. This command results the following conditions: v Start background copy from the C volumes to the B volumes. v No change recording. v There must be no I/O allowed to the B or C volumes during the fast reverse restore process. Perform the following step to create the same consistent data on the B volumes that you have on the C volumes. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. Issue the reverseflash command to create the same consistency on the B volumes that you have on the C volumes. Enter the reverseflash command at the dscli command prompt with the following parameters and variables: dscli>reverseflash -dev storage_image_ID -fast -tgtpprc source_volume_ID:target_volume_ID Example
dscli>reverseflash -dev IBM.1750-68FA150 -fast -tgtpprc 0200:0100
Notes:
199
1. The -fast parameter determines that the reverseflash command is processed before the background copy completes. 2. The source volume ID is the value that is specified for the C volume. The data from this volume is copied to the target volume ID, which is the B volume. 3. The -tgtpprc parameter allows the FlashCopy target volume (B volume) to be a Remote Mirror and Copy source volume. 4. The storage_image_ID parameter is the value that is assigned to the remote storage unit, which has become the primary storage unit as a result of the failover action. 5. You must wait for the background copy to complete before you can go on to the next process.
Waiting for the background copy to complete

Complete this task to determine when all fast reverse restore operations are complete and when no more FlashCopy relationships exist between the B volumes and the C volumes. This is the seventh step in the Global Mirror disaster recovery process. The fast reverse restore operations complete the data transfer from the C volumes to the B volumes. However, before you can proceed with any additional steps, the back ground copy must complete. When the background copy is completed, FlashCopy relationships no longer exist between the B volumes and C volumes. Also, the C volume is no longer usable. Both of these operations must complete before you can move on in the disaster recovery process. The best way to determine if these operations are complete is to periodically issue the lsflash command against the B volumes to query the existence of FlashCopy relationships. Perform the following steps to determine that no FlashCopy relationships exist between the B volumes and the C volumes. The example command in this task is shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lsflash command to check the existence of FlashCopy relationships between the B volume and the C volume. Enter the lsflash command at the dscli command line prompt with the following parameters and variables: dscli>lsflash -dev storage_image_ID -s target_volume_ID Example
dscli>lsflash -dev IBM.1750-68FA150 -s 0200
Notes: a. The storage_image_ID is the manufacture, storage unit type, and serial number value of the remote storage unit that has become the primary unit because of the disaster. b. The -s parameter limits the report information that is returned only to the FlashCopy pair relationships that still exist. c. By designating only the target volume ID, you are further limiting the report to display just the target side of the FlashCopy pair relationship. When the report returns a blank screen, it indicates that
200
background copy has completed and that no FlashCopy relationships exist between the B volume and the C volume. 2. Repeat Step one periodically until no FlashCopy relationships exist between the B volume and the C volume. After the fast reverse restore and the background copy operations have completed, you can proceed to the next task which is reestablishing the FlashCopy relationship between the B volume and the C volume.
Reestablishing the FlashCopy relationships between B volumes and C volumes

Complete this task to reestablish the FlashCopy relationships between your B volumes and C volumes. This is the eighth step in using the Global Mirror disaster recovery process. In this task, you are reestablishing the FlashCopy relationships between the B volumes and C volumes that were established for Global Mirror operations before the disaster occurred. The task is not much different than the one that you used to establish FlashCopy relationships during the set up of your Global Mirror environment. Perform the following steps to create FlashCopy relationships between the B volumes and the C volumes. The example command in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the mkflash command to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. Enter the mkflash command at the dscli command prompt with the following parameters and variables: dscli>mkflash -dev storage_image_ID -tgtinhibit -persist -record -nocp sourcevolumeID:targetvolumeID Example
dscli>mkflash -dev IBM.1750-68FA150 -tgtinhibit -record -persist -nocp 0001:0004
Notes: a. Specify the secondary storage unit MTS (which has become the primary storage unit because of the disaster) for the -dev storage_image_ID parameter. b. Use the -tgtinhibit parameter to inhibit writes on the target volume. c. Use the -record parameter to activate change recording on the volume pair. d. Use the -persist parameter to retain the FlashCopy relationship after the background copy completes. e. Use the -nocp parameter to inhibit the background copy. f. The source_volume_ID is the value associated with the B volumes and the target_volume_ID is the value associated with the C volumes. 2. Use the lsflash command to check the status of the FlashCopy relationships after you have processed the mkflash command.
201
After you have reestablished the FlashCopy relationships, you can start host I/O processing at the remote site on the B volumes. The production operation on the remote site, in this configuration, remains until you are ready to return production to the local site.
Preparing to reinstate production at the local site

Complete this task to begin the process of returning production to your local site. Just as there was a series of steps in the failover recovery process to your remote site, there are a series of steps that you must take to return production to your local site. Returning production to its original implementation is called a failback recovery. After restoring operations at Site A, you can schedule a failback operation to synchronize data and to enable production to resume at your original site, Site A. This task is initiated when your local site has been repaired and is operational. The first step in returning production to site A is to create fibre-channel paths between Site B to Site A and between the specific LSSs. Perform the following steps to create fibre-channel paths from Site B to Site A and between the specific LSSs. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with values declared for the variables. Note: Before you can establish the paths, you must obtain the worldwide node name that is associated with the remote storage unit. In this task your remote storage unit is your local storage unit (Site A). 1. Issue the lssi command against the Site A storage unit to obtain its worldwide node name. A report is displayed that provides the specific information about the Site A storage unit. Enter the lssi command at the dscli command prompt with the following parameters and variables: dscli>lssi -l storage_image_ID Example
dscli>lssi -l IBM.1750-68FA120
Record the worldwide node name because it is used in the next step. 2. Issue the mkpprcpath command to create the fibre-channel paths from Site B to Site A and between the specific LSSs. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA150 -remotedev IBM.1750-68FA120 -remotewwnn 12341234000A000A -srclss 00 -tgtlss 01 I1A20:I2A10
Notes: a. The -dev parameter specifies the ID of your source storage unit. At this point in time, your source is the Site B storage unit.
202
b. The -remotedev parameter specifies the ID of the secondary storage unit. At this point in time, the remote storage unit is your Site A storage unit. c. The -remotewwnn parameter must specify the worldwide node name of the secondary storage unit (Site A at this point in time). If you specify the worldwide node name of the primary storage unit (Site B), the command fails. d. The -srclss parameter refers to Site B storage unit as the source. e. The -tgtlss parameter specifies the Site A storage unit as the target. f. The source_port_ID:target_port_ID value has the Site B port ID as the source and the Site A port ID as the target. After you have established the paths, you are ready to move on to the second step on the failback recovery process which involves issuing the failbackpprc command from the B volume to the A volume.
Resynchronizing the volumes

Complete this task to resynchronize the volumes, B volumes to A volumes. This is the second step in the failback recovery process that allows production to be returned to your A site. Before you can do this task, you must ensure that you have created paths from Site B to Site A between the specific LSSs. This task requires the use of the failbackpprc command. Processing this command resynchronizes the volumes in the following manner depending on the volume state: v If a volume at Site A is in simplex state, all of the data for that volume is sent from Site B to Site A. v If a volume at Site A is in full-duplex or suspended state and without changed tracks, only the modified data on the volume at Site B is sent to the volume at Site A. v If a volume at Site A is in a suspended state but has tracks that have been modified, the volume at Site B will discover which tracks were modified at any site and send both the tracks that were changed on Site A and the tracks that were marked at Site B from Site A to Site B. Perform the following step to resynchronize your volumes. The example commands displayed in this task are shown in two formats. The first format shows the type of information the command requires. The second format provides the command with declared values for the variables. Note: This task does not affect normal operations. All your operations remain at the remote site (Site B). This task is just part of the preparation you need to make to transfer operations back to Site A after it has been repaired. Issue the failbackpprc command to resynchronize your volumes. Enter the failbackpprc command at the dscli command prompt with the following parameters and variables: dscli>failbackpprc -dev storage_image_ID -remotedev storage_image_ID -type gcp source_volume_ID:target_volume_ID
203
Example
dscli>failbackpprc -dev IBM.175068FA150 -remotedev IBM.175068FA120 -type gcp 1000:1000
Notes: 1. The -dev parameter specifies the ID of your source storage unit. At this point in time, your source is the Site B storage unit. 2. The -remotedev parameter specifies the ID of the target storage unit. At this point in time, the remote storage unit is your Site A storage unit. 3. The source_volume_ID:target_volume_ID value has the Site B volume ID as the source and the Site A volume ID as the target. After submitting this command for processing, you must track the progress of the transaction until it completes its first pass. So, querying for first pass completion is the next step in the failback recovery process.
Querying, quiescing, and querying

Complete this task series to query for the first pass of the out-of-sync bitmap completion, to quiesce your system, and to complete the query process to ensure that the out-of-sync tracks equal 0. This series of tasks is the third step in the failback recovery process that allows production to be returned to your A site. To perform this series of tasks, you must ensure that you have resynchronized the volumes, B volumes to A volumes. This series of tasks requires the use of the lspprc command and that you quiesce your system. Perform the following steps to complete the third step of the failback recovery process. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables. 1. Issue the lspprc command periodically to identify when the first pass of the out-of-sync (OOS) bitmap completes. Depending on the number of transactions that you have, some period of time elapses. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.175068FA150 -remotedev IBM.175068FA120 1000:1000
Notes: a. The -dev parameter specifies the ID of your source storage unit. At this point, your source is the Site B storage unit. b. The -remotedev parameter specifies the ID of the target storage unit. At this point, the remote storage unit is your Site A storage unit. c. The source_volume_ID:target_volume_ID value has the Site B volume ID as the source and the Site A volume ID as the target. 2. Quiesce your I/O and unmount your file systems at the B site to preserve the integrity of your file system.
204
Note: Unmounting your file systems flushes the host cache and ensures that you actually copy valid data sets. 3. Reissue the lspprc on page 474 command periodically to identify when the remaining bits completely drain from the B site. This is indicated when the out-of-sync (OOS) tracks equal zero. Depending on the number of transactions that you have, some period of time elapses. Enter the lspprc command at the dscli command prompt with the following parameters and variables: dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l SourceVolumeID:TargetVolumeID Example
dscli>lspprc -dev IBM.175075FA150 -remotedev IBM.175075FA120 1000:1000
After this task is completed, you are ready to establish the remote mirror and copy paths from Site A to Site B.
Reestablishing remote mirror and copy paths (site A to site B)

Complete this task to reestablish the remote mirror and copy paths between site A and site B in preparation for the transfer of operations from the B site to the A site. This is the fourth step in the failback disaster recovery process. Each of the prior tasks must be competed in sequence in order for this task to succeed. This task is similar to when you initially created your remote mirror and copy paths as part of setting up your Global Mirror environment, before the disaster occurred. Create paths so that the logical subsystems (LSSs) are associated with each other. These are the ports that the copy services I/O pass through. It is preferred that they are not the same ports that are used for host I/O. This ensures that there is enough capacity for the data transfer. Perform the following steps to create remote mirror and copy paths between all Global Mirror source and target pairs and between the master and subordinate storage units. The example commands in this task are shown in two formats. The first format shows the type of information that is required by the command. The second format provides the command with declared values for the variables. 1. Obtain the worldwide node name of the secondary storage unit. This information is needed when you do the next step. Enter the lssi or showsi at the dscli command prompt as follows:
dscli>lssi -l
This is the entire command. No additional variables are needed. The showsi command does contain a variable and a command flag: dscli>showsi storage_image_id -fullid Example
dscli>showsi -fullid IBM.175068FA120
Notes: a. Use the lssi command if you want to display a list of all the storage image instances for a storage complex and the status information for each storage image in the list.
205
b. Use the showsi command if you want to display the detailed properties of a specific storage unit. c. Use the -fullid DS CLI command flag with the showsi command to display fully qualified IDs, which include the storage image ID, for every ID that is displayed in the command output. d. Record the worldwide node name for the secondary (target) site B storage unit so that you can use it when you issue the mkpprcpath command. 2. Issue the mkpprcpath command to create the remote mirror and copy paths between all Global Mirror source and target pairs and between the master and subordinate storage units. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables as follows: dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID Example
dscli>mkpprcpath -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -remotewwnn 12341234000A000F -srclss 00 -tgtlss 01 I1A10:I2A20
Notes: a. The -remotedev parameter specifies the ID of the secondary storage unit. b. The -remotewwnn parameter must specify the worldwide node name of the secondary storage unit. If you make a mistake and specify the worldwide node name of the primary storage unit, the command fails. c. The shortened version of the -srclss parameter is shown (value = 00) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter is not used, you must use the fully qualified -srclss source_LSS_ID value. For example: -srclss IBM.1750-68FA120/00. d. The shortened version of the -tgtlss parameter is shown (value = 01) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter is not used, you must use the fully qualified -tgtlss target_LSS_ID value. For example: -tgtlss IBM.1750-68FA120/01. e. The shortened version of the source_port_ID:target_port_ID parameter is shown (value = I1A10:I2A20) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters are not used, you must use the fully qualified source_port_ID:target_port_ID value. For example: IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20. The fully qualified source_port_ID:target_port_ID parameter is positional on your command line. It must be placed after the -tgtlss parameter and value. For example:
206
Performing Global Copy failover processing to the A volumes

Complete this task to perform failover processing from A volumes to B volumes so that the A volumes become the primary volumes and B volumes become the secondary volumes. This is the fifth step in the failback recovery process. The resynchronization of the A volumes and B volumes must be completed (no out-of-sync tracks) before you can proceed with this task. You must issue this restore failover request on the Global Copy volumes pair to reestablish the extended distance relationship and create the A Volume to B Volume Global Copy relationship. Perform the following step to complete failover processing from the A volumes to the B volumes. The example commands in this task are shown in two formats. The first format shows the type of information that is required by the command. The second format provides the command with declared values for the variables. Issue the failoverpprc command to reestablish the extended distance relationship and create the A Volume to B Volume Global Copy relationship. Enter the failoverpprc command at the dscli command prompt with the following parameters and variables: dscli>failoverpprc -dev storage_image_ID -remotedev storage_image_ID -type gcpSourceVolumeID:TargetVolumeID Example
dscli>failoverpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -type gcp 0100:0100 0101:0101 0102:0102 0103:0103
Note: The SourceVolume_ID is the A volume and the TargetVolume_ID is the B volume. A confirmation message like the following is generated for each Global Copy pair that has been changed and moved to a state of suspended.
PPRC pair IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 successfully suspended.
Note: All A volumes must successfully process the failoverpprc command before you can move on to the next step.
Performing Global Copy failback processing for the A volumes

Complete this task to perform Global Copy failback processing for the A volumes. This process resynchronizes the volumes at Site A with volumes at Site B and restarts mirroring from site A (local site) to site B (remote site). This is the sixth step in the failback recovery process. The failover processing that is described in the fifth step of the failback recovery process must have completed. The failover process converted the full-duplex target volumes at site A to suspended source volumes. The volumes at site A started the change recording process while in failover mode.
207
The failback processing that is described in this task can be issued against any remote mirror and copy volume that is in a primary suspended state. The failback processing copies the required data from the source volume to the target volume in order to resume mirroring. Perform the following step to complete failback processing for the A volumes. The example commands in this task are shown in two formats. The first format shows the type of information that is required by the command. The second format provides the command with declared values for the variables. Issue the failbackpprc command to resynchronize your volumes. Enter the failbackpprc command at the dscli command prompt with the following parameters and variables: dscli>failbackpprc -dev storage_image_ID -remotedev storage_image_ID -type gcp SourceVolume_ID:TargetVolume_ID Example
dscli>failbackpprc -dev IBM.175068FA120 -remotedev IBM.175068FA150 -type gcp 1000:1000
Notes: 1. The -dev parameter specifies the ID of your source storage unit. Your source is the Site A storage unit. 2. The -remotedev parameter specifies the ID of the target storage unit. The remote storage unit is your Site B storage unit. 3. The SourceVolume_ID:TargetVolume_ID value has the Site A volume ID as the source and the Site B volume ID as the target.
Resuming Global Mirror processing at site A

Complete this task to start or resume Global Mirror processing at the A site. This is the final step in the failback recovery process. Site A has been repaired and connectivity reestablished with your remote site. You have followed all the prior steps in sequence and are ready to start up I/O processing from your local site. Perform the following steps to start or resume Global Mirror processing. The example commands in this task are shown in two formats. The first format shows the type of information that is required by the command. The second format provides the command with declared values for the variables. 1. Issue the mkgmir command to start Global Mirror processing. Enter the mkgmir command at the dscli command prompt using the following parameters and variables:
mkgmir -dev storage_image_ID -lss LSS_ID -cginterval seconds -coordinate milliseconds -drain seconds -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID
Example
dscli>mkgmir -dev IBM.2107-75FA120 -lss 10 -cginterval 0 -coordinate 50 -drain 30 -session 01 IBM.2107-75FA120/00:IBM.2107-75FA150/00
Note: Issuing the mkgmir command requires that you specify the tuning parameters. The values for the tuning parameters are not retained when you end Global Mirror processing. So, in the case where you need to
208
change the Global Mirror topology parameters, you need to resubmit the tuning parameters when you restart Global Mirror processing. 2. Issue the resumegmir command to continue Global Mirror processing after you have paused Global Mirror processing. Enter the resumegmir command at the dscli command prompt using the following parameters and variables: dscli>resumegmir -dev storage_image_ID -lss LSS_ID -session session_ID Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID Example
Note: You might want to change or maintain the values that you had on your B site for the tuning parameters. You must restate these values before you process the resumegmir command. You cannot state a value for just one of the tuning parameters. You must restate all of the values (-cginterval, -coordinate, and -drain). The following example shows how to enter the resumegmir command to provide these values:
209
210
Chapter 8. CLI commands

This section describes the command-line interface (CLI) commands that you can use to perform configuration and storage management tasks.
About CLI commands

This is a description of the components and structure of a command-line interface command. A command-line interface command consists of the following types of components, arranged in the following order: 1. The command name. 2. The command flags and flag parameters. 3. One or more command parameters, each followed by any sub parameters it might require. The command name specifies the task that the command-line interface is to perform. For example, lsarraysite tells the command-line interface to list array sites, and mklcu tells the command-line interface to create a logical control unit. Flags modify the command. They provide additional information that directs the command-line interface to perform the command task in a specific way. For example, the -v flag tells the command-line interface to display the command results in verbose mode. Some flags may be used with every command-line interface command. Others are specific to a command and are invalid when used with other commands. Flags are preceded by a hyphen (-), and may be followed immediately by a space and a flag parameter. Flag parameters provide information that is required to implement the command modification that is specified by a flag. For example, the -user flag requires a user_name parameter, and the -passwd flag requires a password parameter. Flag parameters are variables. This means that their value changes to meet your needs. Every user will have a different user name and password. Not all flags require parameters. In this case, the flag itself provides all the information that is necessary. Some flag parameters are optional and might allow the use of multiple values. These values must be separated with a comma and no white space between the values. If you do not provide a parameter, then a default value is assumed. For example, you can specify -v on, or -v off to turn verbose mode on or off; but if you specify -v only, then the flag parameter is assumed to be on. The command parameter provides basic information that is necessary to perform the command task. When a command parameter is required, it is always the last component of the command; and it is not preceded by a flag. Some commands permit multiple command parameters with each parameter separated by a white space and not a comma (unlike flag parameters that allow multiple values). Some commands, like lsuser, do not require a command parameter, because a default value of all is always assumed. For some commands, like lsarraysite, the command parameter is optional. If no value is provided, then a default value of all is assumed. If a value is provided, then the command-line interface lists information only about the array site or sites provided in the command parameter string.
211
In the following example, lsrank is the command name. -dev and -l are command parameters. IBM.210775FA120 is the sub parameter for the -dev parameter, and R1, R2, and R3 are a list of command parameters. dscli>lsrank -dev IBM.2107-75FA120 -l R1 R2 R3
Understanding the syntax diagrams

A syntax diagram uses symbols to represent the elements of a command and to specify the rules for using these elements.
Syntax diagrams
Main path line
Begins on the left with double arrowheads (>>) and ends on the right with two arrowheads facing each other (><). If a diagram is longer than one line, each line to be continued ends with a single arrowhead (>) and the next line begins with a single arrowhead. Read the diagrams from left-to-right, top-to-bottom, following the main path line. Keyword
dscli
Represents the name of a command, flag, parameter, or argument. A keyword is not in italics. Spell a keyword exactly as it is shown in the syntax diagram. Required keywords
mkuser -pw password -group group_name [ . . . ] User Name -
Indicate the parameters or arguments you must specify for the command. Required keywords appear on the main path line. Mutually exclusive required keywords are stacked vertically. Optional keywords
-h
-help
-?
Indicate the parameters or arguments you can choose to specify for the command. Optional keywords appear below the main path line. Mutually exclusive optional keywords are stacked vertically. Variable
variable
Represents the value you need to supply for a parameter or argument, such as a file name, user name, or password. Variables are in italics.
212
Special characters
- (minus) or / (slash) sign Flags are prefixed with a - (minus) sign. Flags define the action of a command or modify the operation of a command. You can use multiple flags, followed by parameters, when you issue a command. [ ] square brackets Optional values are enclosed in square brackets. { } braces Required or expected values are enclosed in braces. | vertical bar A vertical bar indicates that you have a choice between two or more options or arguments. For example, [ a | b ] indicates that you can choose a, b, or nothing. Similarly, { a | b } indicates that you must choose either a or b. ... ellipsis An ellipsis signifies the values that can be repeated on the command line or multiple values or arguments. dash A dash indicates that, as an alternative to entering the parameter, a value or values are supplied from stdin. stdin varies depending on your settings and is available when you are using single-shot or script mode. This option is not available when using interactive mode.
List of commands
This is a complete list of the command-line interface commands, alphabetized by command name.
Command applykey Type application key and version Description The applykey command applies the licensed machine code (LMC) activation keys for a storage server. You can enter the LMC keys manually, or you can import the keys from an XML file. The file that contains the LMC keys must be downloaded from an IBM Web site. The chckdvol command changes the name of a count key data (CKD) base volume. The chextpool command modifies an extent pool. The chfbvol command changes the name or data type of a fixed block volume. The chhostconnect command modifies a SCSI host port configuration. The chlcu command modifies a logical control unit.
chckdvol
storage configuration
chextpool chfbvol
storage configuration storage configuration
chhostconnect
I/O port and host connect configuration storage configuration
chlcu
Chapter 8. Command-line interface commands
213
Command chlss chpass
Type storage configuration user account and security
Description The chlss command modifies a logical subsystem. The chpass command changes the password expiration time and the number of login attempts for a storage complex. The chrank command assigns an unassigned rank to an extent pool, or removes an assigned rank from a extent pool. This command can also be used to change an assigned rank to an unassigned rank. The chsession command allows you to modify a Global Mirror session. The chsi command modifies a storage image. You can use it to set characteristics such as online or offline state, name, and description. The chsu command modifies a storage unit. The chuser command is used to modify and lock or unlock a DS CLI or a DS Storage Manager user account. A CLI user with administrative authority uses this command to update a user account password, modify user group authority, or to lock or unlock a user account. Users that do not have administrator authority, use this command to change an expired password and create a password that is not known to the administrator who created their account. The chvolgrp command modifies a volume group name and volume members. The clearvol command clears Copy Services relationships for a base logical volume. The closeproblem command modifies the status of a problem in the problem log file to closed. The commitflash command is used as part of the recovery from a disaster scenario to complete a partially formed Global Mirror consistency group.
chrank
chsession
Copy Services
chsi
storage image configuration
chsu chuser
storage unit configuration user account and security
chvolgrp
clearvol
closeproblem
DS6000 close problem
commitflash
Copy Services
214
Command commitremoteflash
Type Copy Services
Description The commitremoteflash command sends data to a target volume to form a consistency between the remote source and target FlashCopy pair. The diagsi command is an administrative command that is provided to a DS6000 (1750) user who has administrator or service authority. This command is used to enable a warm start. The dscli command starts DS CLI. Use this command to run DS CLI commands in the interactive, single-shot, or script mode. The failbackpprc command copies the required data from the source volume to the target volume in order to resume mirroring. This command is used in the disaster recovery processes that are associated with sites using Metro Mirror, Global Mirror, or Metro/Global Mirror processing. The failoverpprc command is used only with disaster recovery processing. This command is used in the disaster recovery processes associated with sites using Metro Mirror, Global Mirror, or Metro/Global Mirror processing. The failoverpprc command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent. The freezepprc command creates a new remote mirror and copy consistency group. It places the source logical subsystem (LSS) in the long busy state so that no I/Os can be directed to it. It also removes remote mirror and copy paths between the source LSS and target LSS and sets the queue full condition for the primary volume. This causes the host to queue writes to the primary volume until the queue full condition is reset. During the queue full condition, the primary volume reports long busy status.
diagsi
dscli
framework
failbackpprc
Copy Services
failoverpprc
Copy Services
freezepprc
Copy Services
215
Command lsaddressgrp
Type storage configuration
Description The lsaddressgrp command displays a list of address groups for a storage image and the status information for each address group in the list. The lsarray command displays a list of arrays in a storage image and status information for each array in the list. The lsarraysite command displays a list of array sites and status information for each array site in the list. The lsavailpprcport command displays a list of ESCON or fibre-channel I/O ports that can be defined as remote mirror and copy (formerly PPRC) paths. The DS6000 supports only fibre-channel ports. The Enterprise Storage Server (2105 machine type) supports ESCON ports. The lsckdvol command displays a list of count key data (CKD) base and alias volumes in a storage image and status information for each volume in the list. The lsddm command displays a list of disk drive modules (DDMs) and status information for each DDM in the list. The lsextpool command displays a list of extent pools in a storage unit and status information on each extent pool in the list. The lsfbvol command displays a list of fixed block volumes in a storage image and status information for each volume in the list. The lsflash command displays a list of FlashCopy relationships and status information for each FlashCopy relationship in the list.
lsarray
lsarraysite
lsavailpprcport
Copy Services
lsckdvol
lsddm
physical resource information
lsextpool
lsfbvol
lsflash
Copy Services
216
Command lshostconnect
Type I/O port and host connect configuration
Description The lshostconnect command displays a list of host connections for a storage image and the status information for each host connection in the list. You can also use this command to obtain a list of worldwide port numbers (WWPNs) from a system-detected-unknown host port. You can use these WWPNs to create a new host connection using the mkhostconnect command. The lshosttype command displays a list of known hosts, their associated port profiles, address discovery, and logical block size values. Use this command to get the available host types for the mkhostconnect command. The lshostvol command displays the mapping of host device names or volume names to machine type 2105, 2107, and 1750 volume IDs. (This command is not supported on the i5/OS.) The lsioport command displays a list of I/O ports on a specified storage image and optionally provides performance metrics for each I/O port that is listed. The lskey command displays the type of licensed machine code (LMC) activation keys that are installed and available for use by the storage unit. The lslcu command displays a list of logical control units (LCUs) for a storage image and status information for each logical control unit in the list. The lslss command displays a list of logical subsystems (LSSs) for a storage image and status information for each logical subsystem in the list. The lspe command is used by a DS6000 user to find previously created PE package files that are ready to send to IBM. These files were created with the mkpe command and must be sent to IBM because there was an error during the original FTP of the PE package file.
lshosttype
I/O port and host connect configuration
lshostvol
lsioport
lskey
application key and version
lslcu
lslss
lspe
DS6000 PE Package
217
Command lsportprof
Type I/O port and host connect configuration
Description The lsportprof command displays a list of port profiles that are supported on a storage unit and their recommended address discovery and logical block size values. The lspprc command displays a list of remote mirror and copy (formerly PPRC) volume relationships for a storage image, and status information for each remote mirror and copy volume relationship in the list. The lspprcpath command displays a list of existing Remote Mirror and Copy (formerly PPRC) path definitions. The lsproblem command lists problem logs. This command is exclusive to the DS6000. The lsrank command displays a list of defined ranks in a storage image and status information for each rank. The lsremoteflash command displays a list of FlashCopy relationships and status information for each FlashCopy relationship in the list. The lsserver command displays all servers in a storage complex or a list of specified servers and it also displays the status information for each server in the list. The lssession command displays a list of Global Mirror sessions for a logical subsystem (LSS) and information regarding the volumes of each session in the list. The lssi command displays a list of storage images in a storage complex. You can use this command to look at the status of each storage image in the list. The storage image worldwide node name (WWNN) is displayed when this command is used. You must use the storage image WWNN with the lsavailpprcport and mkpprcpath commands.
lspprc
Copy Services
lspprcpath
Copy Services
lsproblem
DS6000 problem log
lsrank
lsremoteflash
Copy Services
lsserver
lssession
Copy Services
lssi
218
Command lsss
Type DS6000 PE Package
Description The lsss command is used by a DS6000 user to find previously created offloaded statesave files that are ready to send to IBM. These files were created with the offloadss command and must be sent to IBM because there was an error during the original FTP transfer of the statesave file. The lsstgencl command displays a list of storage enclosures and status information for each enclosure in the list. The lssu command displays a list of storage units in a storage complex. You can use this command to look at the status and other properties of each storage unit in the list. The lsuser command returns a list of storage image user account names and access authority levels. The lsvolgrp command displays a list of volume groups in a storage image and status information for each volume group in the list. The managehostconnect command modifies the volume group assignment for a SCSI host port. The managepwfile command creates a password file for an existing ESS or DS user account. This command processes the password requirements for 2105, 2107, and 1750 systems. The mkaliasvol command creates zSeries CKD alias volumes (generally referred to as parallel access volumes or PAVs) in a storage image. The mkarray command creates one array per command. The mkckdvol command creates zSeries count key data (CKD) base or CKD alias volumes in a storage image.
lsstgencl
physical enclosure information
lssu
storage unit configuration
lsuser
user account and security storage configuration
lsvolgrp
managehostconnect
I/O port and host connect configuration user account and security
managepwfile
mkaliasvol
mkarray mkckdvol
219
Command mkesconpprcpath
Type Copy Services
Description The mkesconpprcpath command creates a remote mirror and copy (formerly PPRC) path between source and target logical subsystems over an ESCON connection. The command allows you to specify ESCON direct and ESCON switch connections. Use this command only with IBM System Storage Enterprise Storage Servers (2105, Model 800 and Model 750). The mkextpool command creates a fixed block or count key data (CKD) storage type extent pool. The mkfbvol command creates open systems fixed block (FB) volumes in a storage image. The mkflash command initiates a point-in-time copy from source volumes to target volumes. The mkgmir command starts Global Mirror for a specified session. The mkhostconnect command configures open systems hosts port attachments to fibre-channel ports that are configured for FC-AL or SCSI-FCP topology. Open systems hosts port attachments to fibre-channel ports are configured for identified access mode and SCSI protocol. The mklcu command creates a logical control unit (LCU) in a storage image. The mkpe command creates and copies PE packages from DS6000 nodes to the destination directory on a management node. The mkpe command is also used to create a PE package from the log and configuration files contained on the storage management console, and the package does not contain any files that are copied from the DS6000 nodes. The mkpprc command establishes a remote mirror and copy (formerly PPRC) relationship for a volume pair.
mkextpool
mkfbvol
mkflash
Copy Services
mkgmir
Copy Services
mkhostconnect
mklcu
mkpe
DS6000 PE package
mkpprc
Copy Services
220
Command mkpprcpath
Type Copy Services
Description The mkpprcpath command establishes or replaces a remote mirror and copy (formerly PPRC) path between source and target logical subsystems (LSSs) over a fibre-channel connection. This is the only supported connectivity for machine types 2107 and 1750. Paths can be established between the following machine types: 2105:2105, 2107:2107, 2107:1750, 2107:2105, 1750:1750, 1750:2105. The mkrank command creates one fixed block or count key data (CKD) rank from one array. The mkremoteflash command initiates a remote point-in-time copy from source volumes to target volumes through a Remote Mirror and Copy relationship. The mksession command opens a Global Mirror session. The mkuser command creates a DS CLI or a DS Storage Manager user account. A CLI user with administrative authority uses this command to create a user account with a password and user group authority. The mkvolgrp command creates a volume group in a storage image. The offloadauditlog command provides an activity report for a console (identified as smc1 or smc2). The report includes basic information, such as, a list of who logged in, when they logged in, and what they did during their session. The offloadss DS6000 command copies state information from nodes to the destination directory on a management node. The pausegmir command pauses Global Mirror for the specified session.
mkrank
mkremoteflash
Copy Services
mksession mkuser
Copy Services user account and security
mkvolgrp offloadauditlog
storage configuration audit commands
offloadss
DS6000 PE package
pausegmir
Copy Services
221
Command pausepprc
Type Copy Services
Description The pausepprc command pauses an existing remote mirror and copy volume pair relationship. Or, this command can be used to pause a single volume ID. To use with a single volume you must specify either the -at src parameter option or the -at tgt parameter option. If neither of these options are specified in the command, single volumes are not valid. The resumegmir command resumes Global Mirror processing for a specified session. The resumepprc command resumes a remote mirror and copy (formerly PPRC) relationship for a volume pair. The resyncflash command is a point in time copy of an existing FlashCopy pair established with the -record and -persist parameters. The resyncflash command only copies the parts of the volume that have changed since the last point in time copy. When a pair is established with the -record and -persist parameters, the pair initially synchronizes and then a record of all host write operations to the source is maintained in the source volumes. When the resyncflash command is issued on the pair, the new data that is written to the source is copied to the target. The parameters specified in this command replace the parameters in the existing relationship. In order to keep the initial -record and -persist parameters, the -record and -persist parameters must be specified in the resyncflash command. The resyncremoteflash command (formerly called the incremoteflash command and associated with the incremental FlashCopy process) increments an existing remote FlashCopy pair that has been established with the -record and -persist parameters. The reverseflash command reverses the FlashCopy relationship.
resumegmir
Copy Services
resumepprc
Copy Services
resyncflash
Copy Services
resyncremoteflash
Copy Services
reverseflash
Copy Services
222
Command revertflash
Type Copy Services
Description The revertflash command is used as part of the recovery from a disaster scenario to rollback a Global Mirror consistency group that is in the process of forming. The former Global Mirror consistency group is restored. The revertremoteflash command is used to restore data on the source volume to its most recent consistency formation. All new write operations to the source since the most recent consistency formation are overwritten with the previous consistency. The rmarray command deletes arrays. The rmckdvol command deletes count key data (CKD) base or alias volumes from a storage image. The rmextpool command deletes extent pools from a storage image. The rmfbvol command deletes fixed block volumes from a storage image. The rmflash command removes a relationship between FlashCopy volume pairs. The rmgmir command ends Global Mirror processing for the specified session. The rmhostconnect command removes a SCSI host port connection from a storage image. The rmlcu command deletes existing logical control units.
revertremoteflash
Copy Services
rmarray rmckdvol
rmextpool rmfbvol
rmflash
Copy Services
rmgmir
Copy Services
rmhostconnect
I/O port and host connect configuration storage configuration
rmlcu
223
Command rmpprc
Type Copy Services
Description The rmpprc command removes a Remote Mirror and Copy volume pair relationship. Or, this command can be used to remove a single volume ID (which might be useful when a disaster occurs and you want to specify only the available volume and not both the primary and secondary). To use with a single volume, you must specify either the -at src parameter option or the -at tgt parameter option. If neither of these options are specified in the command, single volumes are not valid. The -unconditional parameter must be specified when you designate a single volume; otherwise an error occurs and the command process fails. The rmpprcpath deletes a Remote Mirror and Copy path. The rmrank command deletes ranks from a storage image. The rmremoteflash command removes a relationship between remote FlashCopy volume pairs. The rmsession command closes an existing Global Mirror session. The rmuser command removes a storage image user account. CLI users with administrative authority use this command to delete a user account file. Administrators use their passwords in the required field. The rmvolgrp command deletes existing volume groups from a storage image. The sendpe command is used by a DS6000 user with administrator authority to send a previously created PE package to IBM. This might be necessary because there was an error during the original FTP transfer of the package. The sendss command is used by a DS6000 user with administrator authority to send previously created offloaded statesave files to IBM. This might be necessary if there was an error during the original FTP of the statesave file.
rmpprcpath rmrank rmremoteflash
Copy Services storage configuration Copy Services
rmsession rmuser
Copy Services user account and security
rmvolgrp
sendpe
DS6000 PE Package
sendss
DS6000 PE Package
224
Command setcontactinfo
Type DS6000 remote support and notification
Description The setcontactinfo DS6000 command provides contact information for your storage system administrator. When you use any of the remote support features, this information is sent to IBM so that an IBM service representative can contact you. The setdialhome command activates the Call Home feature. The setflashrevertible command modifies a FlashCopy volume pair that is part of a Global Mirror relationship to revertible. The revertible feature allows data to be committed to the target to form a new consistency, or reverted back to the last consistency. This command must be run before the FlashCopy pair can be committed or reverted. The setioport command configures one or more I/O ports for open systems or zSeries host system connections. This command cannot be used for ESCON ports. The setplex command allows you to modify the 1750 storage complex settings. You can associate a unique name with the 1750 which allows you to open a secure shell connection to a storage unit for remote support. The setremoteflashrevertible command modifies a remote FlashCopy volume pair that is part of a Global Mirror relationship to revertible. This command must be run before the FlashCopy pair can be committed or reverted. Once a pair is revertible, the data can be committed to the target to form a new consistency, or reverted back to the last consistency. The setrmpw command changes the IBM TotalStorage Productivity Center Replication Manager password. Only a person that has administrator authority can invoke this command.
setdialhome setflashrevertible
DS6000 remote support and notification Copy Services
setioport
setplex
DS6000 remote support and notification
setremoteflashrevertible
Copy Services
| | | | | |
setrmpw
User accounts and security
225
Command setsim
Type DS6000 remote support and notification
Description On zSeries hosts, data storage and data retrieval errors are recorded and can be offloaded. A service information message (SIM) provides the error information. The setsim command activates the SIM notification feature. The setsmtp DS6000 command modifies the storage image Simple Mail Transport Protocol (SMTP) and activates the e-mail notification settings. The setsnmp command activates the Simple Network Management Protocol (SNMP) trap notification feature, which sends notifications using SNMP when a problem occurs on a storage unit. Use the command to set the SNMP addresses for the notifications. The showarray command displays detailed properties of a specific array. The showarraysite command displays detailed properties of a specific storage image array site. The showckdvol command displays detailed properties of an individual count key data volume. This command can also be used to display the performance metrics for an individual volume ID. The showcontactinfo command displays customer contact information for the storage image. The showextpool command displays detailed properties or performance metrics of an extent pool. The showfbvol command displays detailed properties for an individual volume. This command can also be used to display the performance metrics of a fixed block volume. The showgmir command displays detailed properties and performance metrics for a Global Mirror logical subsystem ID. The showgmircg command displays consistency group status for the specified Global Mirror session.
setsmtp
setsnmp
showarray
showarraysite
showckdvol
showcontactinfo
DS6000 remote support and notification storage configuration
showextpool
showfbvol
showgmir
Copy Services
showgmircg
Copy Services
226
Command showgmiroos
Type Copy Services
Description The showgmiroos command displays the number of unsynchronized (out of sync) tracks for the specified Global Mirror session. The showhostconnect command displays detailed properties of a storage image host connection. The showioport command displays properties of an I/O port. It optionally displays the performance metrics for a specific I/O port. The showlcu command displays the detailed properties of an individual logical control unit (LCU). The showlss command displays detailed properties of a logical subsystem (LSS). The showpass command lists the properties of passwords. The showplex DS6000 command displays detailed properties of a 1750 storage complex. Detailed properties include your names, descriptions, and notification settings for the storage complex. The showrank command displays detailed properties or performance metrics of a rank. The showsi command displays detailed properties of a storage image. The storage image worldwide node name (WWNN) is displayed when this command is used. You must use the storage image WWNN with the lsavailpprcport and mkpprcpath commands. The showsu command displays detailed properties of an individual storage unit. The showuser command displays storage image user account details. A CLI user with administrative authority uses this command to display the properties (group assignment, user account status and number of failed log ins) that is associated with a current user account name.
showhostconnect
I/O port and host connect configuration I/O port and host connect configuration
showioport
showlcu
showlss
showpass showplex
user account and security DS6000 remote support and notification
showrank
showsi
showsu
storage unit configuration user account and security
showuser
227
Command showvolgrp
Type storage configuration
Description The showvolgrp command displays detailed properties of a volume group. The testcallhome DS6000 command initiates a call home test by creating a test problem record. The unfreezeflash command resets a FlashCopy consistency group that was previously established with the -freeze parameter when the mkflash or resyncflash commands were issued. The unfreezepprc command resumes I/O activity on a storage unit where the freezepprc command has been issued. The unfreezepprc command resets the queue full condition for the primary volume. All queued writes to the source volume are written. The ver command displays the versions of the command-line interface, Storage Manager, and licensed machine code.
testcallhome
DS6000 remote support and notification Copy Services
unfreezeflash
unfreezepprc
Copy Services
ver
application key and version
Command flags
You can use these flags with any command-line interface command.
Flag -p Parameters on | off Description Turns paging on or off. Displays 24 rows at a time unless used with the -r flag. The default is off in single-shot mode and on in interactive mode. You can page by pressing any key. Note: This flag can be used only with the ls type (for example, lsuser, lskey, lsserver) commands and the help (setoutput) command. Specifies the number of rows (1 100) per page. This flag is valid only when the -p flag is set to on. The default value is 24 rows. Note: This flag can be used only with the ls type (for example, lsuser, lskey, lsserver) commands and the help (setoutput) command.
-r
number
228
Flag -fmt
Parameters xml
Description Sets the output format to XML. Note: This option can be used only with list (for example, lsuser, lskey, lsserver) commands Sets the output format to stanza. Note: This option can be used only with list (for example, lsuser, lskey, lsserver) commands Sets the output format to a table. You must set the column delimiter to a single character with the -delim flag. Note: This option can be used only with list (for example, lsuser, lskey, lsserver) commands Sets the output to a space-separated plain text table. Note: This option can be used only with list (for example, lsuser, lskey, lsserver) commands Sets the output to delimited output and the delimiter to the single character char. You must enclose char in single or double quotation marks if the character is a shell metacharacter (such as * or \t). If char is not specified, the CLI program returns a syntax error. A blank space, even when it is enclosed within quotation marks, is not a valid character as a delimiter. Note: This option can be used only with list (for example, lsuser, lskey, lsserver) commands Turns the header on or off. The default is on. Turns the banner on or off. The default is on. Turns verbose mode on or off. The default is off. If you specify the -v flag and do not specify on or off, then verbose mode defaults to on. Provides fully qualified IDs, which include the storage image ID, for every ID that is displayed in the command output. The default value is off. Note: This command flag can only be used with list (for example, lsioport, lskey) and show (for example, showsu, showlss) commands.
stanza
delim
default
-delim
char
-hdr -bnr -v
on | off on | off [ on | off ]
-fullid
[ on | off ]
229
Using hexadecimal values

Use this conversion table to determine the hexadecimal value for a field or DS CLI command parameter that requires a hexadecimal value, or to determine the decimal value for a field or DS CLI command parameter that displays a hexadecimal value, such as the LSS and LUN fields or values.
Purpose
Table 4 provides a list of common decimal to hexadecimal conversion values. For values not listed in the table, you can use the Windows calculator to convert values. From the Windows calculator, click View, then Scientific. If you are converting from decimal to hexadecimal, ensure that DEC is selected in the row of radio buttons, enter a decimal number, and then select HEX. If you are converting from hexadecimal to decimal, ensure that HEX is selected in the row of radio buttons, enter a hexadecimal number, and then select DEC.
Table 4. Decimal to hexadecimal conversion Decimal 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 Hexadecimal 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B
230
Table 4. Decimal to hexadecimal conversion (continued) Decimal 28 29 30 31 32 64 100 128 200 256 500 1000 8192 10000 64384 65280 Hexadecimal 1C 1D 1E 1F 20 40 64 80 C8 100 1F4 3E8 2000 2710 FB80 FF00
Command equivalents
Use this list to correlate commands that are supported on the Enterprise Storage Server machine type 2105 to equivalent commands on the DS6000 machine type 1750.
Enterprise Storage Server machine type 2105 command list server DS6000 machine type 1750 command lsserver Description
Like the 2105, a 2107 storage image contains one pair of servers. A 2107 storage image can contain two storage images. See Note 1.
list volumespace
lsextpool, showextpool, lsrank, showrank, lsarray, showarray, showarraysite mkextpool, mkarray, mkrank rmrank, rmarray, rmextpool lsarraysite, showarraysite
create volumespace delete volumespace list diskgroup
Like the 2105 disk group, a 2107 array site consists of eight storage devices that are made into a RAID array. A 1750 array site consists of eight storage devices that are made into a RAID array. The 2107 does not support the JBOD array configuration.
231
Enterprise Storage Server machine type 2105 command list port
DS6000 machine type 1750 command lsioport, showioport
Description
Like 2105, the 2107 supports fibre-channel and ESCON ports. The 2107 does not support parallel SCSI ports. The 1750 does not support ESCON ports. The maximum quantity of host device adapter cards and I/O ports is dependent on 2107 model number and on the quantity of installed I/O enclosure features. The 2107 CLI lsioport and showioport commands include the -metrics parameter that returns the performance counter values for the respective I/O port IDs. The -metrics parameter provides the means to monitor I/O port performance statistics. For 2107, a I/O adapter card is assigned to a storage image. For 1750, the I/O adapter is integrated with the RAID controller.
set port list volume create volume set volume list pav create pav delete pav list volumeaccess create volumeaccess delete volumeaccess list hostconnection create hostconnection delete hostconnection set hostconnection list log list featurecode
setioport lsfbvol, lsckdvol mkfbvol, mkckdvol chfbvol, chckdvol lsckdvol, showckdvol mkckdvol rmckdvol lsvolgrp, showvolgrp mkvolgrp, chvolgrp rmvolgrp lshostconnect, showhostconnect mkhostconnect rmhostconnect chhostconnect, managehostconnect Not applicable. lsuser, mkuser, rmuser, chuser, lsstgencl
See Note 2. See Note 3.
See Note 4.
The 2105 and 2107 CLI commands are essentially the same, except that the 2107 commands include the volume group ID parameter. For 2107, the hostconnect commands concern SCSI-FCP host port connections to ESS I/O ports that are configured for SCSI-FCP and identified access mode. -The 2107 CLI commands can display feature codes when the appropriate parameters are used with the commands.
232
Enterprise Storage Server machine type 2105 command list webuseraccount create webuseraccount set webuseraccount delete webuseraccount list perfstats
DS6000 machine type 1750 command Not applicable. Not applicable. Not applicable. Not applicable. --
Description
lsioport, showioport, The 2105 CLI list perfstats commands showrank, showextpool, concern the Specialist facility that showfbvol, showckdvol streams performance counter device adapter to the ESS Expert at predefined intervals. This facility does not exist for 2107. Use the 2107 CLI commands with the -metrics parameter to obtain current performance counter values. Not applicable. Not applicable. showplex setsmtp, setcontactinfo showcontactinfo setsmtp, setcontactinfo setsmtp, setcontactinfo setsmtp, setcontactinfo Not applicable. Not applicable. Not applicable. Not applicable. showplex setsnmp setsnmp setsnmp lsproblem lsproblem closeproblem Not applicable. Not applicable. lsflash, lsremoteflash, lspprcpath, lspprc, lsavailpprcport, showgmir -----Unlike the 2105, the 2107 CLI Copy Services functions are not task-oriented. The 2107 CLI provides a complete set of FlashCopy and remote mirror and copy (formerly PPRC) make, change, remove, list, and show commands. The 2107 CLI provides a complete set of FlashCopy, remote mirror and copy (formerly PPRC) commands that can be used in the coding of scripts that emulate 2105 Copy Services tasks. --The 2105 Specialist remote communication functions are implemented in the 1750 as attributes of the storage complex object. The following 1750 commands provide methods to view, set, and modify the remote communication attributes: setplex, showplex, setsmtp, setsnmp, setsim, setcontactinfo, and showcontactinfo. The setsmtp command activates the e-mail notification feature, which sends notifications using e-mail when a problem occurs. Use the showplex command to see the smtp setting.
create perfstats delete perfstats show remotesupport set remotesupport show email create email delete email set email show pager create pager delete pager set pager show snmp create snmp set snmp delete snmp list problem show problem delete problem list task show task list pprcpaths
rsExecuteTask
Copy Services commands
233
Enterprise Storage Server machine type 2105 command rsList2105s
DS6000 machine type 1750 command lshostvol
Description
The lshostvol command displays the mapping of host device or volume names to 2107, 2105, and 1750 and volume IDs. -These 2107 Copy Services CLI commands are equivalent to the respective 2105 CLI commands. The 2107 mkflash and mkpprc commands provide a -wait flag that delays command response until copy complete status is achieved.
rsPrimeServer rsQuery, rsQueryComplete, rsFlashCopyQuery
Not applicable. lsflash, lspprc
rsTestConnection Note 1
ver
--
Volume space configuration is a primary difference between 2105 and 2107. For 2105, one command configures an array site into a RAID array and rank. For 2107, one command configures an array site into an array, and a second command configures an array into a rank. For 2105, a rank is configured as fixed block or CKD, and a CKD rank can contain interleave CKD volumes. For 2107, a rank is assigned to a user-defined extent pool object, which the user defines as either the fixed block or CKD storage type. The interleave volume construct does not exist for 2107. For 2105, a volume is configured from a specific rank, and cannot span rank boundaries. For 2107, a volume is configured from an extent pool. An extent pool can contain multiple ranks. A 2107 volume consists of one or more extents that can be allocated from one or more ranks. A fixed block extent is 1 GB (128 logical blocks). Each block contains 512 bytes of usable data space. A CKD extent is 0.94 GB or 1113 CKD cylinders. For 2105, a rank is either assigned to server 0 or server 1, dependent on array site location. A 2105 rank is assigned to one of four possible LSS IDs, dependent on device adapter pair location and storage type configuration. For 2107, an extent pool is assigned to server 0 or server 1. A rank that is configured from any array site can be assigned to a server 0 or 1 extent pool. Array site position and device adapter pairs are not factors for the rank-to-extent-pool assignment. A volume that is created from a server 0 extent pool is assigned to an even-numbered LSS ID. A volume created from a server 1 extent pool is assigned to odd-numbered LSS ID. A user must define at least two extent pools (0 and 1) but can define as many extent pools as there are ranks. For 2105, a user can delete a rank but cannot delete a volume. For 2107, a user can delete a single volume, rank, or extent pool. The 2107 CLI showrank and showextpool commands include a -metrics parameter that returns the performance counter values for a specified rank or extent pool ID. The -metrics parameter provides the means to monitor rank and extent pool performance statistics.
234
Enterprise Storage Server machine type 2105 command Note 2
DS6000 machine type 1750 command
Description
A 2107 ESCON I/O port is used for zSeries host attachment but cannot be configured as a remote mirror and copy path. Each ESCON I/O port must be assigned to only one address group. An address group is a set of 16 LSS IDs that are configured as CKD LCUs; for example, 0x00 to 0x0F. ESCON I/O port access to 2107 CKD volumes is constrained to the address group LCU volumes, up to 4096 volumes. A 2107 fibre-channel port is configured for either SCSI-FCP or FICON protocol. Like 2105, a FICON port is restricted to the point-to-point/switched fabric topology setting. A FICON I/O port is used for zSeries host attachment, but cannot be configured as a remote mirror and copy path. A FICON port must be configured for anonymous access mode, meaning that any zSeries host system port (WWNN or WWPN) has unrestricted access to all CKD volumes, up to 64 KB volumes. Like 2105, a 2107 fibre-channel SCSI-FCP I/O port can be configured for either the point-to-point/switched fabric or FC-AL connection topologies. A port that uses the point-to-point/switched fabric topology can be simultaneously used for OS host system I/O and for remote mirror and copy path configurations. Like 2105, a 2107 fibre-channel SCSI-FCP I/O port allows only identified host system ports to access volumes. A host system port WWPN must be identified (registered) to each I/O port through which volume access is intended. For 2107, this configuration constraint is defined as I/O port identified access mode. Host system port WWPN identification is accomplished by the CLI mkhostconnect command. Note 3 A 2107 storage image can contain up to 32 000 volumes, whereas a 2105 unit can contain up to 8 000 volumes. Otherwise, the 2105 and 2107 volume definitions and characteristics are essentially identical. For 2107 CKD PAV volumes, the CLI list and show commands identify both the original base and current base volume assignments. The original and current base concept exists for 2105, but specific relationships are not identified in the output. The 2107 CLI provides a specific set of volume commands for each storage type (fixed block or CKD) as a means to clarify input parameter and output device adapter definitions. The 2107 CLI showfbvol and showckdvol commands include a -metrics parameter that returns the performance counter values for a specified volume ID. The -metrics parameter provides the means to monitor volume performance statistics.
235
Enterprise Storage Server machine type 2105 command Note 4
DS6000 machine type 1750 command
Description
The 2105 volume access commands concern volume ID assignment to a SCSI-FCP host port initiator or WWPN. For 2107, volume IDs are assigned to a user-defined volume group ID (mkvolgrp and chvolgrp). A volume group ID is then assigned to one or more host system ports (mkhostconnect and chhostconnect) as a means to complete the volume access configuration. The volume group construct also exists in the 2105 internal code, but the construct is not externalized by the 2105 Specialist or CLI commands. For 2107, a user must create a FICON/ESCON-all type volume group. This volume group ID is assigned to each ESCON I/O port and to each FICON I/O port. The volume group ID enables FICON access all storage image CKD volumes, up to 64 KB volumes. The volume group ID enables an ESCON I/O port to access to the storage image CKD Address Group volumes, up to 4 KB volumes. For 2107 fixed block volumes, a volume group must be configured as either SCSI-mask or SCSI-map-256, depending whether the volume group is accessed by a SCSI-FCP host port that uses the report LUNs or poll LUNs access method protocol.
Output field descriptions

This list describes the output field names, abbreviations, and field descriptions.
Output field name Access Abbreviation access Description Access state. The term access is used throughout the CLI in different contexts. Access state Account Active copy Addr group accstate acct actcpy addrgrp The accessibility state of an object, online or offline. Customer account name for a storage complex. The FlashCopy background copy process is active. A set of 16 contiguous logical subsystems (LSSs) or logical control units (LCUs), starting at ID X0. Address group identifier that is assigned to this ESCON I/O port. A set of 16 contiguous logical subsystems (LSSs) or logical control units (LCUs), starting at ID X0. Address group identifier that is assigned to this ESCON I/O port. An array of device drive modules (DDMs). Array identifier that is assigned to a rank.
Address group
addrgrp
Array Array ID
array arrayID
236
Output field name Array site arsite
Abbreviation
Description Storage unit identifier followed by an array site identifier. Array site ID does not indicate physical location. Ports to which the host can attach. Storage that is available for a segment pool, in GB. FlashCopy process that copies data from a source volume to a target volume. Lowest number of logical volumes in the address group. Count of bypass cache I/O requests. Count of bytes that are transferred by SCSI read I/O operations, in 128 KB. Count of bytes that are transferred by SCSI write I/O operations, in 128 KB. Count of cache fast-write write I/O operations where data did not move to or from a storage device. Count of cache fast-write read I/O operations where data was not moved to or from a storage device. Count of cache fast-write read I/O operations issued by a host to a volume. Count of cache fast-write write I/O operations issued by a host to a volume. Count of delayed I/O operations from a host to a volume because of insufficient cache space. Quantity of volume logical blocks or cylinders that are available for access by a host system. Number of attempts to form a consistency group. The maximum time that writes are inhibited to the remote site before stopping the current consistency group. The interval time between attempts to form a consistency group. The percentage of successful attempts to form consistency groups. The time when the last successful consistency group was formed.
Attaching topology Available storage Background copy
atchtopo availstor bkgrndcopy
Base Vol # Bypass cache Bytes read
basevolnum bypasscach byteread
Bytes written
bytewrit
Cache fast-write hits
cachfwhits
Cache fast-write read hits
cachfwrhits
Cache fast-write read requests Cache fast-write requests
cachfwrreqs
cachfwreqs
Cache space delay
cachspdelay
Capacity
cap
CG attempts CG drain
CGattem CGdrain
CG interval CG success
CGinterval CGsuccess
CG time
CGtime
237
Output field name CKD irregular track accesses
Abbreviation CKDirtrkac
Description Count of I/O operations from a host to a CKD volume that has accessed at least one logical track not described by a regular track format descriptor. Count of irregular track I/O operations where data did not move to or from a storage device. Count of write I/O operations to a volume, where track format descriptor data in cache has promoted at least one track to cache with requiring access to a storage device. Number of logical volumes configured on an address group. Storage unit internal I/O interface configuration: model and feature code dependent. Number of configured volumes. Count of side file additions to a volume from an update to a concurrent copy protected track or an update to an XRC monitored track. Count of remote mirror and copy SCSI control I/O operations that are received from a SCSI source. Count of remote mirror and copy SCSI control I/O operations that are sent to a SCSI target. Default or user-assigned logical control unit type. Global Mirror copy state. Indicates Yes if the CopyIndicator is set for this FlashCopy relationship. Date of creation. Status of critical heavy mode, either enabled or disabled. Status of critical heavy mode for remote mirror and copy (formerly PPRC) copy operations, either enabled or disabled. Base and alias volume number. Current number of FICON N-port worldwide node name (WWNN) identifiers that are logged in to this I/O port. Current number of N-ports that are logged in to this I/O port.
CKD irregular track hits
CKDirtrkhits
CKD write promote hits
CKDwrtprohits
Config Vols Configuration
confgvol config
Configured volumes Contaminating writes
confgvols contamwrts
Control ops received
conopsrcd
Control ops sent
conopssent
Control unit base type Copy state CopyIndicator Created Crit mode Critical heavy mode
conbasetype cpystate CopyIndicator created critmode crithvmode
Current base vol Current FICON logins
curbasevol curflogs
Current SCSI logins
currentlogs
238
Output field name Current time DA pair
Abbreviation currtime DA pair
Description Current date, time, local time zone, and Daylight Savings Time. Identifier of the device adapter pair that the DDM is associated with. The DA pair indicates I/O enclosure location. Count of logical tracks for a volume that were promoted to cache in full or partial track mode (excluding sequential pre-state). Status of the array data access: normal, degraded, read only, failed, repairing, or inaccessible. Status of data access: normal, degraded, read only, failed, repairing, or inaccessible. Date and time, including time zones and Daylight Savings Time. Current clock setting of date. Minimum disk capacity of DDMs, in GBs. Minimum rate of disk revolutions per minute of the DDMs in an array. User-defined description. Capacity of the DDM, in GBs. Interface type of DDM. Interface rate of DDM, in GBs per second. DDM revolutions per minute. DDM usage in an array site. Counting number of extents that were source of a dynamic relocation. Counting number of extents that were target of a dynamic relocation. Engineering change level of the listed enclosure. One or more e-mail addresses that receive service notification. Identifier for an I/O enclosure within a storage unit frame. Ending track address or number. The set of Enterprise Storage Server I/O ports to which a SCSI host port can log in. Status of storage complex ESSNet user interface, either enabled or disabled.
DASD cache transfers
DASDtrans
Data
data
Data state
datastate
Date Date (85) DDM capacity (GB) DDM RPM (revolutions per minute) Description Disk capacity (GB) Disk interface Disk rate (Gb/Sec) Disk RPM Disk usage
date date DDMcap DDMRPM
desc dkcap dkinf dkrate diskrpm dkuse
Dynamic relocation source dyrelocsource
Dynamic relocation target EC level E-mail addresses Enclosure # Ending track ESS IO ports
dyreloctarget EClvl emailaddr enclnum endtrk ESSIOport
ESSNet
ESSnet
239
Output field name Extended long busy active
Abbreviation xtndlbzactive
Description Default or user-assigned extended long busy setting, enabled or disabled. Default or user-assigned extended long busy timeout value. Maximum number of possible extents. LSS persistent cache extent number. Extent pool. Identifier for the extent pool of the assigned rank. Name of the extent pool of the assigned rank. Number of logical tracks in an extent. Extent allocation threshold setting that triggers notification. Number of extents in the rank. Number of extents used by this volume ID. Current speed of a fan. Reason code for a fatal error. Identifier code that is used to order the PC enclosure. FICON I/O operations that are enabled for this port. FICON status, enabled or disabled. Identifier for the firmware level that is installed in the hardware management console (HMC) enclosure. Identifier of storage unit frame that contains this I/O enclosure. Frame identifier format is six hexadecimal characters. Identifier of storage unit frame that contains this I/O enclosure. Frame identifier format is six hexadecimal characters. Frame number of a listed enclosure. -SCSI host identifier for an Open Systems host that is associated with this host port. Storage image ID in the following format: manufacturer.type.serial number.
Extended long busy timeout (secs) Extent limit Extent number Extent pool Extent pool ID Extent pool name Extent size Extent threshold Extents Extents used Fan speed Fatal reason Feature code FICON FICON enabled Firmware level
xtndlbztimout extlim extentnum extpool extpoolID extpoolnam extsize extthresh exts extused fanspeed fatalrsn FC FICON fenabled firmwarelevel
Frame
frame
Frame ID
frameID
Frame # Group Host ID
frm# group hostID
ID
ID
240
Output field name ImACopy Inhibit cache loading Interface address
Abbreviation imacpy inhcachload interadd
Description Indicates Yes if the ImAcopyBit is set for this FlashCopy relationship. Count of inhibit cache loading I/O requests. FlashCopy arbitrated-loop base address of the storage image enclosure. Identifies four interface IDs that are associated with I/O ports on the HBA. Minimum disk interface rate of the disk in an array, in GBs per second. Host attachment interface type (FC-AL, SCSI-FCP, or FICON). Identifier of three interface ports for the HMC enclosure consisting of four hexadecimal characters. Location of enclosure. Location format is Utttt.mmm.ppsssss. Logical block (512 bytes or 520 bytes). Logical block size. Identifier of logical volumes. Maximum number of N-ports that can log in to this I/O port. Number of logical subsystems in an address group. Quantity of LUNs that are accessible by this host attachment (256 LUNs or 64K LUNs). Quantity of LUNs that are accessible by this host attachment (256 LUNs or 64K LUNs). User-defined name. Count of I/O operations that cause nonvolatile storage (NVS) space allocation. Count of I/O operations from a host to a volume. Quantity of master LSS IDs on this storage image ID. Master storage image ID. Global Mirror session ID. LSS subsystem identifier. Amount of processor memory in this PC enclosure, in MB. Migration disk serial number.
Interface IDs
interfID
Interface rate Interface type Interfaces
interrate interface type interfs
Location Logical block Logical block size Logical vols Login limit LSSs LUN access
loc logblk logblksz logvols loglim LSSs LUNacc
LUN capacity
LUNcap
Name NVS space allocations
name NVSspallo
NVS space delay Master count Master ID Master session ID Master SSID Memory Migration disk SN
NVSspadel mastcount mastID mastsessID mastSSID mem migradiskSN
241
Output field name MRPD interval
Abbreviation MRPDintvl
Description Number of days between dial home to report machine-reported product data (MRPD). This interval can be 0. Manufacturer, machine type, and sequence number. Number of narrow arrays in a rank. Number of normal read operations where data did not move to or from a storage device. Number of normal read operations issued by a host to a volume. Number of normal write operations where data did not move to or from a storage device. Number of command sequences with at least one write command. Number of normal write operations issued by a host to a volume. Amount of nonvolatile storage (NVS) memory that is assigned to this server, in MB. Current number of valid N-ports that are logged in to this I/O port. Number of logical volumes configured from an extent pool. Number of extents. Number of ranks configured in an extent pool. Original base volume CKD volume identifier. Amount of operating system memory that is assigned to the server, in MB. The number of tracks that are not synchronized for this FlashCopy relationship. Status of persistent FlashCopy, either enabled or disabled. Amount of persistent cache memory that is assigned to a server, in MB. Number of physical bytes read. Number of physical bytes written. Number of physical storage read operations. Number of physical storage write operations. I/O port. Group identifier for host port.
MTS Narrow arrays Normal read hits
MTS nararrays normrdhits
Normal read requests Normal write hits
normrdrqts normwritehits
Normal write operations Normal write requests NVS memory
normwriteops normwritereq NVSmem
Number of logins Number of logical vols Number of extents Number of ranks Original base vol OS memory
numlogins numlvols numexts numranks orgbvols OSmem
Out-of-sync tracks
outsynctrks
Persistent Persistent cache (MB) Physical bytes read Physical bytes written Physical read Physical write Port Port group
persistent pcache phbyteread phbytewrit phread phwrite port portgrp
242
Output field name Port profile Position Power mode Power state PPRC control operations received PPRC control operations sent PPRC source
Abbreviation portpro pos pw mode pw state PPRCcntrloprec PPRCcntrlopsent PPRCsce
Description Port behavior identification for this SCSI host ID. Position of DDM in an array configuration of DDMs. Current storage unit power control mode. Current storage unit power status. Remote mirror and copy (formerly PPRC) I/O control operations. Remote mirror and copy (formerly PPRC) I/O control operations. Remote mirror and copy (formerly PPRC) source I/O operations that are enabled for this port. Remote mirror and copy (formerly PPRC) target I/O operations that are enabled for this port. Count of logical tracks for a remote mirror and copy (formerly PPRC) primary volume that were transferred to a remote mirror and copy secondary volume. Identifier of processor complex with which the central electronic complex enclosure is associated. Number of processors in the PC enclosure. Number of processors that are assigned to the server. Host port profile. Count of logical tracks for a volume that have been destaged from cache to storage devices. Type and configuration of RAID array. Identifier that the array is assigned to. Rank number consists of storage unit ID and a rank number. Identifier of rank group where segment pool is configured. Array position within the assigned rank. Count of I/O command sequences in one read or search command (but no write commands). Count of read I/O operations. Count of real allocated extents. Count of real extent conversion.
PPRC target
PPRCtgt
PPRC tracks
PPRCtrks
Processor complex
procplex
Processor qty Processors assigned Profile Quick write promotes
procqty procassd profile qwriteprots
RAID type Rank
RAIDtype rank
Rank group Rank position Read operations
rnkgrp rankpos readops
Reads Real allocated extents Real extent conversion
reads realallocext realextconv
243
Output field name Real extent pool capacity Real extents Reason Record cache misses
Abbreviation relextcap realext reason reccachemis
Description Number of gigabytes of real extent pool capacity. Count of real extents. The reason a condition exists. Number of normal record mode read operations where data moved to or from a storage device. Number of normal record mode read operations issued by a host to a volume. FlashCopy - record changed tracks. Number of volume cylinders that are available for host system access. Desired state of storage unit: online or offline. Extents that are reserved in an extent pool. Reserved storage in an extent pool, in GB. Revertible to previous Global Mirror state. SCSI host port users of this volume group. SCSI target I/O operations that are enabled for this port. User-defined time that the storage unit powers on. User-defined time that the storage unit powers off. Count of logical tracks for a volume that were promoted to cache because data was moved by sequential pre-stage and required movement from a storage device. Number of sequential read operations where data did not move to or from a storage device. Number of sequential read operations issued by a host to a volume. Number of sequential write operations that did not require movement of data to or from a storage device before the completion of the operation. Number of command sequences that contain at least one sequential write command.
Record mode reads
recmoreads
Recording Requested capacity Requested state Reserved extents Reserved storage (GB) Revertible SCSI host port users SCSI TGT Scheduled on Scheduled off Sequential DASD cache transfers
rec reqcap reqstate resvdexts resvdstor revertible SCSIhostportusr SCSItgt schl-on schl-off seqDASDtrans
Sequential read hits
seqreadhits
Sequential read requests
seqreadreqs
Sequential write hits
seqwritehits
Sequential write operations
seqwriteops
244
Output field name Sequential write requests
Abbreviation seqwritereq
Description Number of sequential write operations issued by a host to a volume. Internal identifier for the data space of an array. Server or DA group to which the DA is assigned. Unique serial number. One or two IP addresses where the storage complex sends SNMP error messages. Host writes to the source volume are allowed. The current speed of this fan tray. Source volume is enabled to be in a cascading remote mirror and copy (formerly PPRC) relationship. Source volume LSS. Subsystem. The starting track address for the volume pinned data. Storage unit functional status: online, offline, resuming, quiescing, quiesce exception, forced quiescing, or fenced. Current state of the disk drive module. Number of storage devices in an enclosure. Number of slots for storage devices in an enclosure. Extent pool type of the assigned rank. One storage device. Number of logical tracks in a strip. Number of logical tracks in a stripe. Count of subordinate associations. Subordinate storage unit ID. Subordinate subsystem identifier. User-assigned or default subsystem identifier. The relationship is suspended. Date the FlashCopy was synchronized. Host write I/O operations to a target volume are allowed.
Serial number Server SN SNMP addresses
SN server SN SNMPaddr
Source write enabled Speed SRC cascade
sourcewrite speed SRCcascade
SRC vol LSS SS Starting track State
SRCvolLSS SS starttrk state
State (FRU) Storage devices Storage slots Storage type Storage unit Strip size Stripe size Subordinate count Subordinate ID Subordinate SSID Subsystem Suspended Synced Target write enabled
statefru stordev storslot stortype su strpsize strpesize subcount subID subSSID subsys suspended synced tgtwrite
245
Output field name Tgt cascade
Abbreviation tgtcascade
Description Target volume is enabled to be configured in a cascading remote mirror and copy relationship. Host read I/O operations to a target volume are allowed. Current clock setting of time. Accumulated time of lower interface I/O activity for the volume. Amount of I/O port time for SCSI I/O operations, in seconds. Accumulated time for physical storage read operations. Accumulated time for physical storage write operations. Accumulated time for all read operations. Accumulated time for all write operations. Current clock settings of time zone and Daylight Savings Time. -Amount of storage in an extent pool, in GB. Port topology. Size of the track if the volume is CKD or fixed block. Type of storage unit enclosure. List of unknown SCSI N-port WWPN identifiers that attempted login into this I/O port. Number of extents that are allocated to volumes in a rank. Count of virtual extent conversion. Number of gigabytes of virtual extent pool capacity. Count of virtual extents. Volume group ID. The unique identifier that is assigned to this volume. Volume group. Number of logical volumes in an address group. Volume type. Number of wide arrays in a rank. Count of write I/O operations.
Tgt read enabled Time Time lower interface activity Time on-channel
tgtread time timelowifact
timeonchan
Time physical storage read timephread Time physical storage write Time read Time write Time zone Timout active copy recording Total storage (GB) Topology Track size Type Unknown SCSI IDs timephwrite timeread timewrite timez timoutactcpyrec totlstor topo trksize type unkSCSIlog
Used extents Virtual extent conversion Virtual extent pool capacity Virtual extents Vol group
usedexts virextconv virextcap virext vol
Volume group Vols Volume type Wide arrays Writes
volgrp vols voltype widearrays writes
246
Output field name WWNN WWPN XDC interval
Abbreviation WWNN WWPN XDCintvl
Description Worldwide node name. Worldwide port name. Global Mirror copy interval.
Framework command
This section contains the user interface framework commands for the DS command-line interface. The framework commands consist of the following commands: v dscli v exit v help v quit v setoutput The dscli command starts the DS command-line interface (CLI). Use this command to perform storage management tasks from the command-line. The setoutput command generates the format of the reports for the list and show commands during an interactive command session.
dscli
The dscli command starts DS CLI. Use this command to run DS CLI commands in the interactive, single-shot, or script mode.
dscli -h -help -? -ver -overview -script file_name command -cfg profile -hmc1 HMC1 -hmc2 HMC2
-user
user_name
-passwd
password
-pwfile
passwordfile
Parameters
Note: You must not start more than 100 DS CLI sessions simultaneously. Starting more than 100 DS CLI sessions simultaneously can result in connection problems. -help | -h | -? (Optional) Displays a help screen about how to use the DS CLI program. -ver (Optional) Displays the DS CLI version. -overview (Optional) Provides overview information about the DS CLI.
247
-script file_name (Optional) Initiates the script mode so that multiple dscli program commands can be issued consecutively using a saved file. file_name Specifies the file with the stored program commands to be executed. Format options that are specified using the framework setoutput command apply to all commands in the file. Output from successful commands routes to stdout, and output from failed commands routes to stderr. If an error occurs during the processing of one of the commands in the file, the script exits at the point of failure and returns to the system prompt. command Specifies the single command that you want to run. -cfg profile Specifies a profile file. This parameter is not required if you are using default profiles. The default profile file name is dscli.profile, and it is provided as part of the DS CLI package under the profile directory. -hmc1 HMC1 (Optional) Specifies the primary management console IP address or the host name. HMC1 The IP address for the primary management console. This parameter is not required if you have established this information as a profile variable. -hmc2 HMC2 (Optional) Specifies the secondary management console IP address or the host name. HMC2 The IP address for the secondary management console. This parameter is not required if you have established this information as a profile variable. Note: The HMC1 and HMC2 values must apply to two different management consoles. -user user_name (Optional) Specifies your user name for issuing DS CLI commands on the command-line. user_name Your user name. This parameter is not required if you have established this information as a profile variable. -passwd password (Optional and not recommended) Specifies the password that you use for issuing DS CLI commands on the command line. password Your password.
248
This parameter is not required or recommended. If you use this method to designate your password, the password is displayed on the screen. Another option is to specify a password file (see the next parameter) that is used when you start the DS CLI application. Also, if you specify this parameter and do not specify the -user parameter, nothing happens. In other words, you are still prompted for a user ID and password before you can log in to the DS CLI application. -pwfile passwordfile Specifies the password file that contains your password. passwordfile Specifies a password file as an alternative to the passwd parameter.
Example
This command invokes the CLI in interactive mode:
>dscli

dscli>
exit
Ends an interactive command-line interface session.
exit -? -h -help
Parameters
-? | -h | -help Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored.
Example
Exit interactive mode
dscli>exit
Out of interactive mode

#
help
Displays a list of commands available in a command-line interface and optionally displays the syntax or brief description of each command. If you specify this command with no parameters, this command displays only a list of available commands.
249
help -? -h -help -l -s -p off on -r number command_name
Parameters
-? | -h | -help Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored. -l Displays a list of available commands with the syntax diagrams for each. If you specify a command name with this parameter, this command displays the syntax for only the specified command. Displays a list of available commands with a brief description of each. If you specify a command name with this parameter, this command displays a brief description for only the specified command.
-s
-p off | on Specifies whether to display one page of text at a time or all text at once. off Displays all text at one time. This is the default value. on Displays one page of text at a time. Pressing any key displays the next page. -r number Specifies the number of rows per page to display when the -p parameter is on. The default is 24 rows. You can specify a value from 1 to 100. command_name Displays help information for the specified command, including the syntax diagram, parameter descriptions, return codes and errors, descriptions, examples, and miscellaneous remarks.
Example
Invoke help
#dscli>help -s exit

Ends a command-line interface session.
quit
Ends an interactive command-line interface session.
quit -? -h -help
250
Parameters
-? | -h | -help Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored.
Example
Quit interactive mode
dscli>quit
Out of interactive mode

#
setoutput
The setoutput command sets or displays command output format options. You can use this command to set either default or user-defined output formats. The output format set by this command remains in effect for the duration of the interactive command session unless reset either with a command option or the re-issuance of the setoutput command. Running this command with no parameters displays the current output settings in the default output format.
setoutput -? -h -help -fmt default delim xml stanza -p off on -hdr on off
-delim
char
-r
number -v
off on
-bnr
off on
Parameters
-? | -h | -help Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored. -fmt default | delim | xml | stanza Specifies the format of the output. You can specify one of the following values: default Specifies that the output be displayed in a tabular format using spaces as the delimiter between the columns. This is the default value. delim Specifies that the output format be set to a table and sets the column delimiter to a single character specified by the -delim char option. xml Specifies that the output be displayed in XML format. stanza Specifies that the output be displayed in stanza (horizontal table) format.
251
-p off | on Specifies whether to display one page of text at a time or all text at once. off Displays all text at one time. This is the default value. on Displays one page of text at a time. Pressing any key displays the next page. -hdr on | off Specifies whether to display the table header. on Displays the table header. This is the default value. off Does not display the table header. -delim char Specifies the delimiter character (such as a comma) used in the report. -r number Specifies the number of rows per page to display when the -p parameter is on. The default is 24 rows. You can specify a value from 1 to 100. -v off | on Specifies whether to enable verbose mode. off Disables verbose mode. This is the default value. on Enables verbose mode. -bnr off | on Specifies whether the banner (command header) message be enabled. off Turns the header mode off so that the command header does not display. on Turns the header mode on so that the command header is displayed.
Format Examples
Invoke the setoutput command with no options When you specify the setoutput command with no options, the DS CLI always displays the current output settings in the default format (space-separated plain text table), regardless of the values of the output settings. Issue the setoutput command as follows:
dscli>setoutput

Paging Rows Format Header Verbose =================================== Off Default On Off On Banner
Invoke the setoutput command using the -delim parameter The following is an example of the commands that you would issue to get (long) output in comma-separated format for an unassigned rank only. Issue the setoutput command to specify the report format and then issue the lsrank command to designate the rank being queried.
252
dscli> setoutput -fmt delim delim , dscli> lsrank dev IBM.1750-75FA120 -state unassigned
The resulting output Note: While this example shows the header turned on, you can choose to turn the header off, in which case you issue the command and include the -hdr off parameter.
ID,Group,State,datastate,Array,RAIDtype,extpoolID,stgtype ========================================================== R0,-,Unassigned,Normal,A0,5,-,fb
Invoke the setoutput command using the -fmt xml parameter The following is an example of the commands that you would issue to get (long) output in XML format for an unassigned rank only. Issue the setoutput command to specify the report format and then issue the lsrank command to designate the unassigned rank being queried.
dscli> setoutput -fmt xml dscli> lsrank dev IBM.1750-68FA120 state unassigned

<IRETURNVALUE> <INSTANCE CLASSNAME="CliRankHandler"><PROPERTY NAME="rank_id"> <DISPLAY TYPE="string">R0</DISPLAY><VALUE TYPE="string">R0</VALUE> </PROPERTY><PROPERTY NAME="grp"><DISPLAY TYPE="unit8">-</DISPLAY> <VALUE TYPE="unit16">-</VALUE></PROPERTY><PROPERTY NAME="state"> <DISPLAY TYPE="string">Unassigned</DISPLAY><VALUE TYPE="string"> unassigned</VALUE></PROPERTY><PROPERTY NAME="data"> <DISPLAY TYPE="string">Normal</DISPLAY><VALUE TYPE="string"> Normal</VALUE></PROPERTY><PROPERTY NAME="array_id> <DISPLAY TYPE=string">A0</DISPLAY><VALUE TYPE="string">A0 </VALUE></PROPERTY><PROPERTY NAME="raidtype"><DISPLAY TYPE="unit8">5</DISPLAY> <VALUE TYPE="string">5</VALUE><PROPERTY><PROPERTY NAME="extpool_id"> <DISPLAY TYPE="string">-</DISPLAY><VALUE TYPE=string">-<VALUE> <PROPERTY><PROPERTY NAME="stgtype"><DISPLAY TYPE="string">fb</DISPLAY> <VALUE TYPE="string">fb</VALUE><PROPERTY> <INSTANCE><IRETURNVALUE>
Invoke the setoutput command using the -fmt stanza parameter When columns are horizontally long, output can be difficult to visually align. Using the stanza format option eliminates this problem. The following is an example of the commands that you would issue to get (long) output in stanza format for an unassigned rank only. Issue the setoutput command to specify the report format and then issue the lsrank command to designate the unassigned rank being queried.
dscli> setoutput -fmt stanza dscli> lsrank dev IBM.1750-68FA120 state unassigned

ID R0 Group State unassigned datastate normal Array A0 RAIDtype 5 extpoolID stgtype fb
253
User account and security commands

This section contains commands that are used to maintain command-line interface (CLI) user accounts and security. The following commands are used to add, modify, delete, and show CLI user accounts and security information: v chpass v chuser v lsuser v managepwfile v mkuser v rmuser v showpass v showuser The chpass command changes the password expiration time and the number of login attempts for a storage complex. The chuser command modifies and locks or unlocks a DS CLI or a DS Storage Manager user account. Users that do not have administrator authority, use this command to change an expired password and create a password that is not known to the administrator who created their account. The lsuser command generates a report that lists the storage image user account names and access authority levels. The managepwfile command creates a password file for an existing ESS or DS user account. This command processes the password requirements for 2105, 2107, and 1750 systems. The mkuser command creates a DS CLI or a DS Storage Manager user account. The rmuser command removes a storage image user account. CLI users with administrative authority use this command to delete a user account file. The showpass command generates a report that lists the number of days until the password expires and the number of failed logins that are associated with the password. The showuser command generates a report that displays the details for an individual storage image user account.
chpass
The chpass command changes the password expiration time and the number of login attempts for a storage complex.
chpass -expire number -fail number
254
Parameters
-expire number (Optional) Specifies the number of days a Storage Manager user account password is valid before it expires. The default number of days is 365. If you do not want the password to expire, enter a value of zero. After the password expires, the user is not allowed to log in unless the password is changed. | | | | | | -fail number (Optional) Specifies the number of login attempts allowed on any given Storage Manager user account. The number of login attempts can be zero to twenty-five. The default number of login attempts is 15. If you do not want a limit on the number of login attempts, enter zero . After the number of login attempts is exceeded, the user account is locked.
Example
Invoking the chpass command
dscli>chpass -expire 20 -fail 0

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS:IBM 175068FA120 Password parameters successfully changed.
chuser
The chuser command is used to modify and lock or unlock a DS CLI or a DS Storage Manager user account. A CLI user with administrative authority uses this command to update a user account password, modify user group authority, or to lock or unlock a user account. Users that do not have administrator authority, use this command to change an expired password and create a password that is not known to the administrator who created their account.
chuser -pw new_password User Name - -lock -unlock -group group_name [ . . . ]
Parameters
Note: When a person with administrator authority designates the password, the password is set as expired upon its initial use. The user of the password is required to establish a new password using the chuser command before access to the rest of the DS CLI application is granted. -pw new_password (Optional) Specifies that a new password be assigned to the user. Notes: 1. When a person with administrator authority is using this parameter in association with the -unlock parameter, the new password is temporary and expires upon the initial use. 2. When a person without administrator authority uses this parameter, the new password becomes their valid password and replaces their prior password.
255
new_password The new password. The new password and its usage must meet the following criteria: v Be six to 16 characters long. v Must contain five or more letters, and it must begin and end with a letter. v Must contain one or more numbers. v Cannot contain the users user ID. v Is case-sensitive. -lock (Optional) Locks a user account. Persons with administrator authority can use this parameter to lock a user account. The affect of this locking action is not enacted until the user authenticates their account. In other words, if a user is already active (authenticated) and using the DS CLI application, the lock does not take place until they log out of the application. -unlock (Optional) Unlocks a user account. A person with administrator authority can use this parameter to unlock a user account when the user can no longer log into the DS CLI application. The reasons a user might not be able to log into the DS CLI application can include: v The user forgot their password and in an attempt to log in they went beyond the set number of allowable attempts. Going beyond the set limit locks the user account. Note: When unlocking a user account for this scenario, the administrator must also assign a new password to the user using the -pw parameter. The new password is temporary and immediately expires after its initial use. The administrator must notify the user of this new password. v Someone with administrator authority has locked the user account. -group group_name [...] (Optional) The users access authority group. group_name [...] The following list provides the list choices that can be assigned to a user. Multiple names must be separated by commas. For example, op_copy_services,service. admin The administrator user group has access to all management console server service methods and all storage image resources. op_storage The storage operator user group has access to physical configuration service methods and resources, including storage complex, storage image, array, rank, and extent pool objects. This user group inherits all the authority of the op_copy_services and monitor user groups, excluding security methods. op_volume The volume operator user group has access to service methods and
256
resources that relate to logical volumes, hosts, host ports, logical subsystems, logical volumes, and volume groups, excluding security methods. In addition, this user group inherits all authority of the monitor user group. op_copy_services The copy services operator user group has access to all Copy Services service methods and resources, excluding security methods. In addition, this user group inherits all authority of the monitor user group. service The service user group includes monitor authority, plus access to all management console server service methods and resources, such as performing code loads and retrieving problem logs. monitor The monitor user group has access to list and show commands. It provides access to all read-only, nonsecurity management console server service methods and resources. no access The no access user group does not have access to any service methods or storage image resources. By default, this user group is assigned to any user account in the security repository that is not associated with any other user group. User Name | (Required) The user account name. Notes: 1. The administrator inserts the name of the user account that is affected by the changes (group name, lock, or unlocking). 2. Users who are changing their passwords insert their user account name. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chuser command
dscli>chuser -pw xy0abcde testuser

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 User Name testuser successfully modified.
lsuser
The lsuser command returns a list of storage image user account names and access authority levels.
lsuser
257
Parameters
There are no parameters for this command.
Example
Note: For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. Invoking the lsuser command
dscli>lsuser

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Name Testuser Biguser Smalluser Group services,op_copy_services admin op_storage State active active locked
Report field definitions

Name Specifies the user name that is assigned to the user account. Group Specifies the access authority group of the user. One or more of the following group designations is displayed: v admin v op_storage v op_volume v op_copy_services v service v monitor v no access State Specifies the status of the user account for the designated user group, either active or locked.
managepwfile
The managepwfile command creates a password file for an existing ESS or DS user account. This command processes the password requirements for 2105, 2107, and 1750 systems.
managepwfile -action add remove change -pw -name username
-pwfile
file_name
-mc1
HMC1
-mc2
HMC2
password
258
Parameters
-action (Required) Specifies that a process that is designated by the subparameter be enacted on the password file. add Specifies that the password file be created by adding the first line of the file, which contains the primary HMC designation and the HMC user name. Specifies that the password file be removed for the designated user. change Specifies that the password file be changed for the designated user. -pwfile file_name (Optional) Specifies the name that you want to use for the password file. You can specify the password file as an absolute path or a relative path. The relative path is obtained from the current working directory. file_name The user-specified ESS or DS password file name. -mc1 (Optional) Specifies the DNS name or the IP address. Note: You can use the default value that is specified for HMC1 in your profile file, or you can use the value that is specified for the current CLI session connection. HMC1 Designates the primary HMC or 2105 DNS name or IP address. This information along with the -name parameter is used as a key in the password file. -mc2 (Optional) Specifies the DNS name or the IP address of the secondary HMC. Note: You can use the default value that is specified for HMC2 in your profile file, or you can use the value that is specified for the current CLI session connection. HMC2 Designates the secondary HMC or 2105 DNS name or IP address. -name (Optional) Specifies the name that you use to access the DS CLI application. username Designates the user-specified SMC or 2105 user name. This information along with the mc1 parameter information is used as a key in the password file. -pw password (Required) Specifies a user-assigned password. password Specifies the password that enables user name access to this ESS or DS CLI client installation. The password is case-sensitive. Notes:
remove
259
1. A password file is created with a users default protection mask. The user needs to update the protection mask to allow access only to the owner of the file. Also, you must write down the directory name where the password file is contained in case you need to use it later. 2. The password file has a default value of <user_home>/dscli/security.dat. The home directory <user_home> is defined by the Java system property named user.home The location of your password file is determined by your operating system. The following examples are home directories in different operating systems: Windows operating system For a Windows operating system, the property value defaults to the environment variable %USERPROFILE%. As a result, your personal profile is C:\Documents and Settings\<username>\dscli\ security.dat . UNIX or Linux operating system For an UNIX or Linux operating system, the property value defaults to the environment variable $HOME. As a result, your personal profile is ~/dscli/security.dat. i5/OS For the i5/OS, your personal profile is /home/<username>/dscli/ security.dat. OpenVMS system For an OpenVMS operating system, the property value defaults to the logical name SYS$LOGIN. As a result, your personal profile is [.dscli.profile]security.dat Note: The values of the Java system properties can be redefined by JRE options. If you are having problems, check to see if you have an environment setting like the following on your local system:
_JAVA_OPTIONS=-Duser.home=...
Example (1750)
Invoking the managepwfile command
dscli>managepwfile -action add -mc1 myess.ibm.com -name testuser pw AB9cdefg

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 Record myess.ibm.com/testuser successfully added to password file c:\Documents and Settings\testuser\dscli\security.dat
mkuser
The mkuser command creates a DS CLI or a DS Storage Manager user account. A CLI user with administrative authority uses this command to create a user account with a password and user group authority.
mkuser -pw password -group group_name [ . . . ] User Name -
260
Parameters
pw password (Required) Specifies the password that is assigned to the user that allows them to access the use of the DS CLI command line function. This password is temporary and set to expire after the initial use. The user must assign themselves a new password using the chuser command before they can us any other commands in the DS CLI application. password The password assigned by the administrator to user. The password and its usage must meet the following criteria: v Be six to 16 characters long. v Must contain five or more letters, and it must begin and end with a letter. v Must contain one or more numbers. v Cannot contain the users user ID. v Is case-sensitive. -group group_name [...] (Required) The users access authority group. group_name [...] The following list provides the list choices that can be assigned to a user. Multiple names must be separated by commas. For example, op_copy_services,service. admin The administrator user group has access to all management console server service methods and all storage image resources. op_storage The storage operator user group has access to physical configuration service methods and resources, including storage complex, storage image, array, rank, and extent pool objects. This user group inherits all the authority of the op_copy_services and monitor user groups, excluding security methods. op_volume The volume operator user group has access to service methods and resources that relate to logical volumes, hosts, host ports, logical subsystems, logical volumes, and volume groups, excluding security methods. In addition, this user group inherits all authority of the monitor user group. op_copy_services The copy services operator user group has access to all Copy Services service methods and resources, excluding security methods. In addition, this user group inherits all authority of the monitor user group. service The service user group includes monitor authority, plus access to all management console server service methods and resources, such as performing code loads and retrieving problem logs. monitor The monitor user group has access to list and show commands. It
261
provides access to all read-only, nonsecurity management console server service methods and resources. no access The no access user group does not have access to any service methods or storage image resources. By default, this user group is assigned to any user account in the security repository that is not associated with any other user group. User Name | (Required) The current user account user name. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkuser command
dscli>mkuser -pw AB9cdefg -group service,op_copy_services testuser

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 User Name testuser successfully created.
rmuser
The rmuser command removes a storage image user account. CLI users with administrative authority use this command to delete a user account file. Administrators use their passwords in the required field.
rmuser -quiet User Name -
Parameters
-quiet (Optional) Turns off the confirmation prompt. User Name | (Required) The current user account user name. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmuser command
dscli>rmuser testuser

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete User Name testuser? y/n Y User Name testuser successfully deleted.
262
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
setrmpw
setrmpw
The setrmpw command changes the IBM TotalStorage Productivity Center Replication Manager password. Only a person that has administrator authority can invoke this command.
-dev storage_image_ID -server 0 | 1 | both -rmpw RM_password
Parameters
-dev storage_image_ID (Required) Specifies the storage image ID, which consists of the values for manufacturer, machine type, and serial number. -server 0 | 1 | both (Optional) Specifies the server where the password is changed. The default is both. -rmpw RM_password (Required) Specifies the new Replication Manager password. The password must meet the following criteria: v The password must contain a minimum of 5 alphabetic characters and 1 numeric character. v The password must begin and end with an alphabetic character. v The alphabetic characters must be entered in uppercase and the pass word is case sensitive. v The password cannot contain the user name of the account that it is for.
Example
Note: If you do not specify the -rmpw parameter on your command line, you are asked twice to supply the Replication Manager password after you have entered the setrmpw command. Invoking the setrmpw command
dscli>setrmpw -dev IBM.2107-75ALA2P -server 0 -rmpw CLI1TIME

Sun OCT 8 02:23:49 PST 2006 IBM DS CLI Version 5.0.0.0 DS:IBM RM password was successfully updated.
showpass
The showpass command lists the properties of passwords.
showpass
Parameters
There are no parameters for this command.
263
Example (1750)
Invoking the showpass command
dscli>showpass

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version 5.0.0.0 DS: IBM.1750-68FA120 Password Expiration (days) 33 days Failed Logins Allowed 5
showuser
The showuser command displays storage image user account details. A CLI user with administrative authority uses this command to display the properties (group assignment, user account status and number of failed log ins) that is associated with a current user account name.
showuser User_Name -
Parameters
User_Name | (Required) Specifies the user account name. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output reports that are associated with the showuser command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. . Invoking the showuser command
dscli>showuser testuser

Column Header Name Group Description Name of the user that you have queried. The users access authority group. One or more of the following group designations is displayed: v admin v op_storage v op_volume v op_copy_services v service v monitor v no_access
264
Column Header State FailedLogins
Description The status of the user account for the specified user group, either active or locked. Count of login failures since last successful login for this user. This number resets to 0 with each successful login.
Application key and version commands

This section contains commands that are used to maintain application keys and to view the current CLI version. Use the following commands to add and list application keys and to show the current command-line interface version: v applykey v lskey v ver The applykey command activates the licenses for your storage unit. The lskey command generates a report that displays the type of licensed machine code activation keys that are installed and are available for use by the specified storage unit. The ver command displays the versions of the command-line interface, Storage Manager, or licensed machine code either individually or collectively depending on how you enter the command.
applykey
The applykey command applies the licensed machine code (LMC) activation keys for a storage server. You can enter the LMC keys manually, or you can import the keys from an XML file. The file that contains the LMC keys must be downloaded from an IBM Web site.
applykey -key key [...] -file file_name storage_image_ID -
Parameters
-key key [...] (Optional) Specifies the LMC key. To specify multiple keys, enter a comma between each key. Do not include a blank space between each key. This parameter is required if the -file parameter is not specified. -file file_name (Optional) Specifies the file name of the LMC activation key file. This parameter is required if the -key parameter is not specified. storage_image_ID | (Required) Specifies the storage image ID where the LMC activation key file will be imported. The ID includes manufacturer, type, and serial number.
265
If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the applykey command
dscli>applykey -file keys.xml IBM.1750-68FA120
lskey
The lskey command displays the type of licensed machine code (LMC) activation keys that are installed and available for use by the storage unit.
lskey storage_image_ID
Parameters
storage_image_ID | (Required) Specifies the storage image ID for which to view a list of activated features. The ID includes manufacturer, type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lskey command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. The only difference is the value input for the storage_image_ID parameter. Invoking the lskey command
dscli>lskey IBM.2107-75FA120

Sun Apr 09 02:23:49 PST 2004 IBM DS CLI Activation Key Operating Environment (OEL) Remote mirror and copy (RMC) Remote mirror for z/OS (RMZ) Point in time copy (PTC) Parallel access volumes (PAV) Authorization Level (TB) 45 25 25.1 On On Scope All All CKD All CKD
266

Activation key Specifies the type of LMC activation key that is activated for the storage image. One of the following values is displayed: v v v v v Operating Environment Point-in-time copy Remote Mirror and Copy Parallel access volumes Remote Mirror for z/OS
Authorization Level (TB) Specifies the capacity of the specified license feature. The quantity is displayed in terabytes (TB). One of the following values is displayed: v Value in terrabytes v On if the license is for the maximum capacity or Off if the license is for zero capacity Scope Specifies the storage type for the designated license: fixed block (FB), count key data (CKD), or All. Parallel access volumes and Remote Mirror for z/OS display only the values CKD or All.
ver
The ver command displays the versions of the command-line interface, Storage Manager, and licensed machine code.
ver -s -l -cli -stgmgr -lmc
Parameters
-s -l (Optional) The -s parameter displays the version of the command line interface program. You cannot use the -s and -l parameters together. (Optional) The -l parameter displays the versions of the command line interface, Storage Manager, and licensed machine code. You cannot use the -l and -s parameters together. (Optional) Displays the version of the command line interface program. Version numbers are in the format version.release.modification.fixlevel. -stgmgr (Optional) Displays the version of the Storage Manager. -lmc (Optional) Displays the version of the licensed machine code.
-cli
Example
Invoking the ver command
dscli>ver l
267
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS Storage Manager 5.0.1.0 LMC 5.0.1.0
Physical enclosure information commands

This section contains commands that are used to view information about the physical enclosures in your storage complex. Use the following commands to view information about the physical enclosures in your storage complex: v lsstgencl The lsstgencl command generates a report that displays a list of the storage enclosures and status information for each enclosure in the list.
lsstgencl
The lsstgencl command displays a list of storage enclosures and status information for each enclosure in the list.
lsstgencl -s -l -state normal not normal storage_image_ID - . . .
Parameters
-s -l (Optional) Displays the storage enclosure ID. You cannot use the -l and the -s parameters together. (Optional) Displays default output, plus the storage enclosure feature code and engineering change level. You cannot use the -l and the -s parameters together.
-state normal|not normal (Optional) Displays all the storage enclosures that are associated with the specified storage unit that contain a condition of normal or a condition that falls under the category of not normal. storage_image_ID . . . | (Required) Displays storage enclosure information for the specified storage image IDs. A storage image ID consists of manufacturer, machine type, and serial number. You must separate multiple IDs with a space between each ID. Note: You cannot specify an ID range. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsstgencl command using the -l parameter. There are some differences in the returned values for a 2107 versus a 1750.
268
Invoking the lsstgencl command

dscli>lsstgencl -l IBM.1750-68FA120

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 ID IBM.1750EX1.68FA120 /S00 Frame - (null) Enclnum S01 Loc U1750. 511.685FA120 FC - (Not applicable) Interfaces 0080, 0081, 0180, 0181 (Not interface values. See the field definitions) 0082, 0083, 0182, 0183 (Not interface values. See the field definitions)
IBM.1750EX1.68FA120 /S01
- (null)
S02
U1750. 511.685FA120
- (Not applicable)
Interadd 0x0 0x1
Storslot 16 16
Stordev 16 16
Cap 145 145
RPM 10000 10000
State normal normal

ID Specifies the enclosure ID and enclosure number. Note: This is the only information that is displayed if you use the -s parameter. None of the other values are displayed. Frame Specifies null (-) for the 1750. Enclnum (1750) Identifies a storage enclosure within a storage unit frame. The values displayed for the enclosure are S00 - S03 or S10 - S13. These values are interpreted as follows: v Enclosures S0x are located on DA pair interface 0. v Enclosures S1x are located on DA pair interface 1. Notes: 1. y represents the position of the storage enclosure. For example, the distance from the server enclosure. (0 first, 1 second, 2 third, 3 fourth) 2. The server enclosure contains a storage enclosure element that resides on FC-AL Loop 0, and that is what is returned with the command output. Loc Specifies the storage enclosure location by identifying the storage unit frame that contains the storage enclosure. The location format is Utttt.mmm.ppsssss. Specifies the feature code that was used to order this storage enclosure.
FC
269
Interfaces Specifies a list of four interface identifiers, one for each DA I/O port. A DA interface ID consists of four hexadecimal characters with the following format: t00 eeeee aaaa pppp b, (value is separated for readability), where v t = port type (0 = I/O port, DA ports are always I/O ports) v 00 = reserved v eeeee = enclosure number v aaaa = adapter number v pppp = port number v b = indicates that the value is a binary string The values for DS6000 represent the following: Notes: 1. For dual loop 0 enclosures, the DA I/O port values are displayed as 0080, 0081, 0180, 0181. 2. For dual loop 1 enclosures the DA I/O port values are displayed as 0082, 0083, 0182, 0183. Interadd Specifies the FC-AL interface base address assigned to this storage enclosure for DDM access. Storslot Specifies the number of slots for storage devices in this storage enclosure. Stordev Specifies the number of storage devices that are installed in this storage enclosure. Cap Specifies the capacity of DDMs in the storage enclosure. Note: This field can contain multiple capacity values separated by a comma when the DDMs with different capacity are installed in the storage enclosure. RPM Specifies the rpm of the DDMs in the storage enclosure. Note: This field can contain multiple RPM values separated by a comma when the DDMs with different capacity are installed in the storage enclosure. State Specifies the condition of the storage enclosure. The condition of the enclosure is either normal or one of the conditions that falls under the category not normal. The following values can be displayed: normal Indicates that the storage enclosure is not in any failure or transient condition. failed Indicates that the storage enclosure is broken and ready to be removed without impacting the system. This condition changes to inter failed if the storage enclosure is found to be in good condition again. new This condition only displays when a storage enclosure is first discovered.
270
removed Indicates that the storage enclosure was removed from the system. inappropriate Indicates that the hardware resource cannot be integrated in the system. inter failed Indicates that the hardware resource is faulty but still working. PFSed (Prepared for Service) Indicates that the storage enclosure is ready to be removed without impacting the system. attention Indicates that there is a problem with the storage enclosure; however, it is not known whether it is faulty or not. This condition reverts to normal if the problem is closed.
Physical resource information commands

This section contains commands that are used to view information about the physical resources in your storage complex. Use the following commands to view information about the physical resources in your storage complex: v lsddm The lsddm command displays a report that lists the disk drive modules and status information for each disk drive module in the list.
lsddm
The lsddm command displays a list of disk drive modules (DDMs) and status information for each DDM in the list.
lsddm -s -l -enclosure enclosure_ID -dapair dapair_ID
-arsite
arraysite_ID
-usage
unassigned unconfigured spare not_spare array_member
-state
normal not_normal
storage_image_ID -dualloop 1 2 . . . -
Parameters
-s -l (Optional) Displays the DDM IDs. You cannot use the -s and -l parameters together. (Optional) Displays the default output. You cannot use the -s and -l parameters together.
271
-enclosure enclosure_ID (Optional) Displays DDMs that are associated with a common storage enclosure ID. This parameter accepts a fully qualified enclosure ID, which includes either the storage image ID or a shortened version without the storage image ID. The shortened version is a hexadecimal number within the range (00 - 3F). -dapair dapair_ID (Optional) Displays DDMs that are associated with a common device adapter (DA) pair ID. This parameter accepts a fully qualified DA pair ID, which includes either the storage image ID or a shortened version without the storage image ID. The shortened version is a two-digit decimal number with no leading zeros. -arsite arraysite_ID (Optional) Displays DDMs that are associated with a common array site ID. This parameter accepts a fully qualified array site ID, which includes either the storage image ID or a shortened version without the storage image ID. The shortened version is a four-digit decimal number with no leading zeros, prefixed with the letter S. -usage unassigned | unconfigured | spare | not_spare | array_member (Optional) Displays DDMs that are associated with a specified usage. -state normal | not_normal (Optional) Displays DDMs that are associated with a specified state. -dualloop 1 | 2 (Optional) Specifies that DDMs that are associated with a specified dual loop be displayed. storage_image_ID . . . | (Required) Displays DDM information for the specified storage image IDs. A storage image ID includes manufacturer, type, and serial number. You can specify multiple IDs and they must be separated with a space between each ID. Note: You cannot specify ID ranges. If you use the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsddm command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Also, the table shows only the first 2 DDMs associated with the specified storage unit. Invoking the lsddm command
dscli>lsddm -l IBM.2107-75FA120

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120
272
ID IBM.2107D2175FA120 /R1-S11P1-D1 IBM.2107D2175FA120 /R1-S11P1-D2
Model S0BE146
loc U2107.921. 75FA120
Firmware level 3603
DA pair 11
Dualloop 1
dkcap (10^9B) 145
S0BE146
U2107.921. 75FA120
3603
11
145
Diskrpm 1000 1000
Dkinf FCAL FCAL
Dkrate 2 2
Dkuse array member array member
Arsite S123 S123
Position 1 2
State normal normal
Diskclass ENT ENT

ID Specifies the system-assigned unique identifier for the DDM. Model Specifies the DDM model. The model name is a string of the form VRFCGGG, where VRFC is the type of disk family and GGG is the disk capacity in GB. loc Specifies the storage enclosure and the DDM location. The DDM location format is Pn-Dn, where Pn is the Planer number (1), and Dn is the DDM number (1 - 16).
Firmwarelevel Specifies the level of firmware that is installed on the specified DDM. DA pair Specifies the device adapter pair ID. DA pairs are located in I/O enclosure pairs. Note: An even-numbered DA pair ID indicates the first DA pair in an I/O enclosure pair. An odd-numbered DA pair ID indicates the second DA pair in an I/O enclosure pair. Dualloop Specifies the dual loop that the specified DDM resides on. The value is either 1 or 2. dkcap (10^9B) Specifies the DDM raw capacity in gigabytes. diskrpm Specifies the DDM rpm. One of the following values is displayed: v 10000 v 15000 dkinf Specifies the DDM interface type. One of the following values are displayed: v FC-AL
273
v FC-NL dkrate Specifies the DDM interface rate. dkuse Specifies the DDM usage in an array site. One of the following values are displayed: v unassigned v unconfigured v spare required v spare not required v array member arsite Specifies the array site ID.
Position Specifies the DDM position in an array site configuration of DDMs. State Specifies the current DDM state. One of the following values are displayed: Normal The storage device is operational and functional in its current disk usage. New Indicates the initial state when a DDM is inserted or first discovered. Installing A new storage device has been identified. Verifying The storage device is made accessible to the device adapter, its characteristics are determined, cabling is checked, and diagnostics are run. Formatting A verified storage device requires low-level formatting and the formatting operation is in progress. Initializing The storage device is being initialized with all zero sectors. Certifying The storage device is read-accessed to determine that all sectors can be read. Rebuilding The storage device is being rebuilt with data from the array that it is associated with. Migration Target DDM migration is migrating another array member storage device to this spare storage device. Migration Source DDM migration is migrating this array member storage device to another spare storage device. Failed The storage device has failed and an immediate repair action is required.
274
Failed - Deferred Service The storage device has failed and a repair action is not immediately required. Removed The storage device is removed from the system and removal has been processed by the system. Inappropriate The storage device is incompatible with the system; for example, a storage device that has the wrong capacity or rpm. The DDM is not failed, because it can be valid for other systems and locations. Inter failed Indicates that the DDM is faulty but still working. PFSed Indicates that the DDM is prepared for service, and ready to be removed without impacting the system. Diskclass Specifies the disk class as either high speed fibre channel disk drives or near-line disk drives. The value displayed is one of the following: v ENT = Specifies enterprise and represents high speed fibre channel disk drives v NL = Specifies near-line and represents ATA (FATA) disk drives
Storage unit configuration commands

This section contains commands that are used to configure a storage unit. Use the following commands to configure a storage unit and show storage unit information: v chsu v lssu v showsu The chsu command changes the description and name you have associated with a specified storage unit. The lssu and showsu commands generate reports that allow you to view details about your storage units.
chsu
The chsu command modifies a storage unit.
chsu -desc new_su_description -name new_su_name storage_unit_ID -
Parameters
-desc new_su_description (Optional) Allows you to specify a description for the storage unit. The description is limited to 256 byte or 128 double-byte characters.
275
-name new_su_name (Optional) Allows you to specify a user-defined name for the storage unit. This name is limited to 32 bytes or 16 double-byte characters. storage_unit_ID | (Required) Accepts the fully qualified storage unit ID. The storage unit ID consists of manufacturer, machine type, and serial number. For example, IBM.1750-68FA120. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chsu command
dscli>chsu -name mystgunit IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Storage unit IBM.1750-68FA120 successfully modified.
lssu
The lssu command displays a list of storage units in a storage complex. You can use this command to look at the status and other properties of each storage unit in the list.
lssu -s -l -power on off storage_unit_ID . . . -
Parameters
-s -l (Optional) Displays storage unit IDs. You cannot use the -l and the -s parameters together. (Optional) Displays default output and remote mode with scheduled power-on and power-off times, and the storage unit description. You cannot use the -l and the -s parameters together.
-power on | off (Optional) Displays only the storage units in the specified power state. storage_unit_ID . . . | (Optional) Displays storage units with the specified storage unit IDs. A storage unit ID includes manufacturer, type, and serial number. You must separate multiple IDs with a space between each ID. Note: You cannot specify ID ranges. If you specify the dash (-), this parameter information is automatically supplied.
276
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lssu command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for the 2107 and 1750. The only difference is the value input for the storage_unit_ID parameter. Invoking the lssu command
dscli>lssu -l

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-75FA120 Pw State On Pw Mode Local
Name SU 1
ID IBM.210775FA110 IBM.210775FA120 IBM.210775FA130
Model 921
WWNN 3007ACF 3012399 E0 3007ACF 3045699 E0 3007ACF 3078999 E0
Desc Test
SU 2
921
On
Local
Production Backup
SU 3
921
On
Local

Name Specifies the user-defined name for each storage unit found within the storage complex. This value is null (-) if you have not assigned a name to a storage unit. ID Specifies the storage unit ID which consists of the manufacture name, machine type, and serial number. When the -s parameter is used, this is the only information that is displayed for the lssu command. Identifies the model number of the storage unit. WWNN Specifies the World Wide Node Name for the listed storage unit. This value is null (-) if the WWNN is not known Pw State Indicates the power status of the listed storage unit. One of the following values is displayed: On Indicates the storage unit power is on. Off Indicates the storage unit power is off. Turning On Indicates the storage unit power is in the process of turning on.
Model
277
Turning Off Indicates the storage unit power is in the process of turning off. Power Exception Indicates that storage unit power is on, but online operation is not possible due to a power fault in one of the storage unit frames. Pw Mode Indicates the power control mode in effect for the listed storage unit. One of the following values is displayed: Local Indicates that the SMC local/remote switch is set to the local power control mode. Remote SMC Manual Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to manual power control. Remote SMC Scheduled Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to scheduled power control. Remote SMC Auto Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to auto-power control. Remote SMC Scheduled/Auto Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to auto/scheduled power control. Remote zSeries Power Control Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to zSeries remote power control. Desc Specifies the description that you assigned the storage unit. This value is displayed as a null (-) if no description has been assigned.
showsu
The showsu command displays detailed properties of an individual storage unit.
showsu storage_unit_ID -
Parameters
storage_unit_ID (Required) Specifies the storage unit ID. A storage unit ID consists of manufacturer, machine type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables.
278
The following table represents the headers that are displayed on the output report that is associated with the showsu command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showsu command
dscli>showsu DS: IBM.210775FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Name My Storage Unit Desc This is my DS Storage Unit ID IBM.210775FA120 Model 921 WWNN 3007ACF 3012399 E0 Config One I/O interface
Pw State On
Pw Mode Local
Reqpm Remote SMC manual
Processor Memory 1 GB

Name Specifies the name that you assigned for the designated storage unit. This value is null (-) if you have not assigned a name to a storage unit. Desc ID Specifies the description that you assigned for the designated storage unit. This value is displayed as a null (-) if no description has been assigned. Specifies the storage unit ID which consists of the manufacture name, machine type, and serial number.
Model Identifies the model number of the designated storage unit. WWNN Specifies the World Wide Node Name for the listed storage unit. This value is null (-) if the WWNN is not known. Config Specifies the internal I/O interface configuration for the storage unit. One of the following values is displayed: Undefined Indicates that a configuration upgrade is in progress that causes the configuration option to change. One I/O interface Indicates that there is one dedicated I/O interface between the I/O enclosure pairs and storage enclosures. Two I/O interfaces Indicates that there are two dedicated I/O interfaces between the I/O enclosure pairs and storage enclosures. Four I/O interfaces Indicates that there are four dedicated I/O interfaces between the I/O enclosure pairs and storage enclosures.
279
Six I/O interfaces Indicates that there are six dedicated I/O interfaces between the I/O enclosure pairs and storage enclosures. Pw State Indicates the power status of the listed storage unit. One of the following values is displayed: On Indicates the storage unit power is on. Off Indicates the storage unit power is off. Turning On Indicates the storage unit power is in the process of turning on. Turning Off Indicates the storage unit power is in the process of turning off. Power Exception Indicates that storage unit power is on, but online operation is not possible due to a power fault in one of the storage unit frames. Pw Mode Indicates the power control mode in effect for the listed storage unit. One of the following values is displayed: Local Indicates that the SMC local/remote switch is set to the local power control mode. Remote SMC Manual Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to manual power control. Remote SMC Auto Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to auto-power control. Remote zSeries Power Control Indicates that the SMC local/remote switch is set to remote and that the power control mode is set to zSeries remote power control. Reqpm Indicates the power control mode to apply when the local/remote switch is set to remote power control mode. One of the following values is displayed: v Remote SMC Manual v Remote SMC Scheduled v Remote SMC Auto v Remote SMC Scheduled/Auto v Remote zSeries Power Control Note: The default value is remote SMC Manual mode. Processor Memory Specifies the amount in gigabytes of processor memory configured on the storage unit.
280
Storage image configuration commands

This section contains commands that are used to configure a storage image. Use the following commands to configure a storage image and show storage image information: v chsi v diagsi v lsserver v lssi v showsi The chsi command primarily enables or disables the ESSNet user interface that invokes Copy Services operations for the storage image, changes the description and name that you have assigned to the storage image, or changes an iSystem serial number. The diagsi command initiates a warm start on a DS6000 system. The lsserver command displays all the servers in a storage complex or a list of specified servers. The displayed list also provides the status information for each server including the LIC version number, operating system version number, and bundle version. The lssi command with the lsavailpprcport and the mkpprcpath commands displays a list of storage images in a storage complex. These commands requires that you use the storage image WWNN, which is displayed for each storage image when you use the lssi command. The showsi command displays the detailed properties of a storage image. In addition, the storage image WWNN is displayed for the specified storage image. The storage image WWNN is needed when you use the lsavailpprcport and mkpprcpath commands.
chsi
The chsi command modifies a storage image. You can use it to set characteristics such as online or offline state, name, and description.
chsi -essnetcs y n -volgrp volume_group_ID -desc new_si_description
-name
new_si_name
-os400sn
iSeries_Serial_Number
storage_image_ID -
Parameters
-essnetcs y | n (Optional) Enables or disables the storage complex ESSNet user interface to invoke Copy Services operations for the storage image. y (yes) is the default. -volgrp volume_group_ID (Optional)
281
When the -essnetcs y parameter is used, the -volgrp parameter specifies the ESSNet Copy Services type volume group that contains the logical volumes that are eligible for controll by Copy Services operations. If the -essnetcs y parameter and the volume group ID are not specified, then all logical volumes are eligible for controll by Copy Services operations. The -volgrp parameter accepts a fully qualified volume group ID including the storage image ID or a shortened version. The shortened version is a four-digit decimal number with no leading zeros, prefixed with the letter V. -desc new_si_description (Optional) Specifies the description that you assign to the storage image. The description is limited to 256 byte or 128 double-byte characters. -name new_si_name (Optional) Specifies the name that you assign to the storage image. The storage image name is limited to 32 byte or 16 double-byte characters. -os400sn iSeries_Serial_Number (Optional) Specifies the new iSeries serial number. The serial number consists of 3 hexadecimal characters. It uniquely identifies LUNs within a customer storage complex. It is appended to the unit serial number that is returned by a SCSI inquiry command that is directed to each LUN. Notes: 1. You must restart your computer after you process this DS CLI command to assign a new serial number. 2. The iSeries serial number is only required when you have multiple DS**** machines with the last 3-digits of the machine serial number that overlap. storage_image_ID | (Required) Specifies the storage image ID, which consists of the values for manufacturer, machine type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chsi command
dscli>chsi -essnetcs n IBM.175068FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.175068FA120 Storage image IBM.175068FA120 successfully modified.
diagsi
The diagsi command is an administrative command that is provided to a DS6000 (1750) user who has administrator or service authority. This command is used to enable a warm start.
diagsi -action warmstart storage_image_ID -
282
Parameters
Notes: 1. You must be in interactive mode to process this command. This command cannot be initiated while in single shot mode or from a script. 2. Only users with administrator or service authority are authorized to use this command. 3. The -action warmstart parameter allows you to collect microcode data when you have a problem with your DS6000 storage unit. -action warmstart (Required) Specifies the administrative action to be performed. warmstart The -action warmstart parameter is restricted to the following usage rules: v Five minutes must pass before you can reissue the -action warmstart parameter. v You cannot issue the -action warmstart parameter more than 10 times during a 24 hour period. storage_image_ID | (Required) Accepts a fully qualified storage image ID. The storage image ID consists of manufacturer, machine type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example
Invoking the diagsi command
dscli>diagsi -action warmstart IBM.175068FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.175068FA120 Warmstart on Storage Unit IBM.1750-68FA120 successfully completed
lsserver
The lsserver command displays all servers in a storage complex or a list of specified servers and it also displays the status information for each server in the list.
lsserver -s -l Server_ID . . . -
Parameters
-s -l (Optional) Displays the server ID. You cannot use the -l and the -s parameters together. (Optional) Displays the default output and the state mode of the servers. You cannot use the -l and the -s parameters together.
283
Server_ID . . . | (Optional) Displays the server information for the specified server IDs. This parameter accepts a fully qualified server ID, which includes the storage image ID or a shortened version without the storage image ID. The shortened version is a two-digit decimal number with no leading zeros. Example: IBM.1750-13AAV3A/0 Example: IBM.1750-13AAV3A/1 Note: If you choose to use this parameter with a fully qualified storage image ID, ensure that you properly specify the server ID with the /x or /xx server designation. A properly coded lsserver command that designates the server ID looks like the following:
dscli>lsserver -l IBM.1750-68FA120/0
To specify a range of server IDs, separate the server IDs with a hyphen. You must separate multiple server IDs or ranges of server IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables The following table represents the headers that are displayed on the output report that is associated with the lsserver command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. The only difference is the value you input when you use the Server_ID parameter. Invoking the lsserver command
dscli>lsserver -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Power Control SFI 0
ID IBM.2107 75FA120 /00
Image Image ID Name 1 SF75ALK C0ESS01
State Online
LIC Version 5.0.7.155
OS Version 2005.9. 1.163506
Bundle Version 6.0.500.8

ID Specifies the unique identifier of the server. This value includes the storage image ID and the server ID.
Image ID Specifies the image ID for the designated storage server. Image Name Specifies the image name for the designated storage server.
284
Power Control SFI Specifies the storage server power control SFI. LIC Version Specifies the LIC version for the designated storage server. State Specifies the current state of the designated server.
OS Version Specifies the operating system version for the designated server. Bundle Version Specifies the bundle version for the designated storage server.
lssi
The lssi command displays a list of storage images in a storage complex. You can use this command to look at the status of each storage image in the list. The storage image worldwide node name (WWNN) is displayed when this command is used. You must use the storage image WWNN with the lsavailpprcport and mkpprcpath commands.
lssi -s -l -state online offline fenced -su_id storage_unit_ID
storage_image_ID . . . -
Parameters
-s -l (Optional) Displays storage image IDs. You cannot use the -l and the -s parameters together. (Optional) Displays the default output, ESSNet, volume group, and storage image description. You cannot use the -l and the -s parameters together.
-state online | offline | fenced (Optional) Displays only the storage images in the specified state. -su_id storage_unit_ID . . . (Optional) Displays the storage images that are associated with the specified storage unit. A storage unit ID consists of manufacturer, machine type, and serial number. storage_image_ID . . . | (Optional) Accepts fully qualified storage image IDs. A storage image ID consists of manufacturer, machine type, and serial number. You must separate multiple IDs with a space between each ID. Note: You cannot specify ID ranges. If you specify the dash (-), this parameter information is automatically supplied.
285
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represents the headers that are displayed on the output report that is associated with the lssi command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for the 2107 and 1750. There is a difference in the input values when you use the su_ID and storage_image_ID parameters. Invoking the lssi command
dscli>lssi -l

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Name DS 1 ID IBM.210775FA120 Storage Unit IBM.210775FA120 Model 921 WWNN 3007ACF30 12399E0
State Online
ESSNet Enabled
Volume Group -
Desc This is my DS storage Image

Name Specifies the name that you assigned to the storage unit. ID Specifies the storage image ID that consists of the manufacture, machine type, and serial number.
Storage Unit Specifies the storage unit ID that consists of the manufacture, machine type, and serial number. Model Specifies the model number that is associated with the storage unit. WWNN Specifies the worldwide node name that is assigned to the storage unit. State Specifies the status of the storage unit. One of the following values are displayed: Online Indicates that the storage unit is capable of processing all functions. Offline Indicates that the storage unit is offline and not capable of processing any functions. Resuming Indicates that the storage unit is in the process of coming online. Quiescing Indicates that the storage unit is in the process of going offline.
286
Quiesce Exception Indicates that the storage unit is in the quiesce exception state. Forced Quiescing Indicates that the storage unit is in the process of performing a force offline operation. Fenced Indicates that the storage unit has failed and is offline. Discovery Indicates that the storage unit is determining which physical configurations are available and updates itself when it discovers new hardware. (1750 only) ESSNet Specifies that the storage-complex ESSNet user interface can invoke Copy Services operations to this storage image. Enabled or Disabled are the values that are displayed in this field. Volume Group Specifies the ESSNet Copy Services Volume Group ID or displays a null (-) in this field. If ESSNet Copy Services operations are enabled, the value that is displayed in this field specifies the ESSNet Copy Services type volume group. This volume group contains the logical volumes that can be controlled by Copy Services operations that are initiated through the ESSNet. If ESSNet Copy Services operations are enabled and the ESSNet Copy Services Volume Group ID is not specified (represented by the null (-) value in this field), all logical volumes are eligible to be controlled by Copy Services operations that are initiated through the ESSNet. Desc Specifies the value that you have assigned as a description for the storage unit.
showsi
The showsi command displays detailed properties of a storage image. The storage image worldwide node name (WWNN) is displayed when this command is used. You must use the storage image WWNN with the lsavailpprcport and mkpprcpath commands.
showsi storage_image_ID -
Parameters
storage_image_ID | (Required) Specifies the storage image ID. A storage image ID consists of a manufacturer, machine type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables.
287
The following tables represents the headers that are displayed on the output report that is associated with the showsi command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. The report displays the iSeries serial number for a 1750 machine type. Invoking the showsi command
dscli>showsi IBM.210775FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Storage Unit IBM. 210775FA120
Name
Desc
ID IBM. 210775FA120
Model 921
WWNN
Signature
My Storage This is my Image DS storage Image
3007ACF30 0123-4500 12399E0 -0000
State Online
ESSNet Enabled
Volume Group -
Os400 Serial -
NVS Memory 8 GB
Cache Memory 128 GB
Processor Memory 1 GB

Name Specifies the name that you assigned to the storage unit. Desc ID Specifies the value that you have assigned as a description for the storage unit. Specifies the storage image ID that consists of the manufacture, machine type, and serial number.
Storage Unit Specifies the storage unit ID that consists of the manufacture, machine type, and serial number. Model Specifies the model number that is associated with the storage unit. WWNN Specifies the worldwide node name that is assigned to the storage unit. Signature Specifies the machine signature that is represented by 12 hexadecimal digits in the format xxxx-xxxx-xxxx. State Specifies the status of the storage unit. One of the following values are displayed: Online Indicates that the storage unit is capable of processing all functions. Offline Indicates that the storage unit is not capable of processing any functions. Resuming Indicates that the storage unit is in the process of coming online.
288
Quiescing Indicates that the storage unit is in the process of going offline. Quiesce Exception Indicates that the storage unit is in the quiesce exception state. Forced Quiescing Indicates that the storage unit is in the process of performing a force offline operation. Fenced Indicates that the storage unit has failed and is offline. Discovery Indicates that the storage unit is determining which physical configurations are available and updates itself when it discovers new hardware. (1750 only) ESSNet Specifies that the storage-complex ESSNet user interface can invoke Copy Services operations to this storage image. Enabled or Disabled are the values that are displayed in this field. Volume Group Specifies the ESSNet Copy Services Volume Group ID or displays a null (-) in this field. If ESSNet Copy Services operations are enabled, the value that is displayed in this field specifies the ESSNet Copy Services type volume group. This volume group contains the logical volumes that can be controlled by Copy Services operations that are initiated through the ESSNet. If ESSNet Copy Services operations are enabled and the ESSNet Copy Services Volume Group ID is not specified (represented by the null (-) value in this field), all logical volumes are eligible to be controlled by Copy Services operations that are initiated through the ESSNet. OS400Serial (1750 only) Specifies null (-) for a 2107 model type and the iSeries serial number for a 1750 model type. The serial number consists of 3 hexadecimal characters. It is used to uniquely identify LUNs within a customers storage complex. It is appended to the unitSerialNumber that is returned by a SCSI inquiry command directed to each LUN. NVS Memory Specifies the amount in gigabytes of nonvolatile storage (NVS) memory configured on the storage unit. Cache Memory Specifies the amount in gigabytes of cache memory configured on the storage unit. Processor Memory Specifies the amount in gigabytes of processor memory configured on the storage unit.
I/O port and host connection configuration commands

This section contains storage image I/O port and host connection configuration commands.
289
Use the following commands to configure your storage image I/O ports and host connections and to display connection information.
Storage image I/O port commands

This section contains commands that are used to configure storage image I/O port information and to display storage image I/O port information. Use the following commands to configure storage image I/O ports and to display storage image I/O port information: v lsioport v setioport v showioport The lsioport command displays a list of I/O ports on a specified storage image and optionally provides performance metrics for each I/O port that is listed. The setioport command configures one or more I/O ports for open systems or zSeries host system connections. The showioport command displays the properties of a specified I/O port. It optionally displays the performance metrics for the I/O port.
lsioport
The lsioport command displays a list of I/O ports on a specified storage image and optionally provides performance metrics for each I/O port that is listed.
lsioport -dev storage_image_ID -s -l -type fc
-topology
fc-al scsi-fcp ficon
-state
online offline fenced deconfigured
-metrics
port_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. Note: This parameter is required if you do not specify a fully qualified port ID and you do not specify a value for the devid variable in your profile file. -s -l (Optional) Displays fully qualified port IDs. You cannot use the -l and -s parameters together. (Optional) Displays default output plus the maximum login limit and the number of current logins. You cannot use the -l and -s parameters together.
290
-type fc (Optional) Displays I/O ports of the specified port type. -topology fc-al | scsi-fcp | ficon (Optional) Displays fibre-channel I/O ports with the specified topology. -state online | offline | fenced | deconfigured (Optional) Displays I/O ports of the specified state. -metrics (Optional) Displays port ID and performance metrics for each port that is specified. Note: All performance counts are an accumulation since the most recent counter wrap or counter reset operation. I/O port performance counters are reset with a storage unit power-on sequence. port_ID . . . | (Optional) Displays I/O ports that match the specified IDs. This parameter accepts a fully qualified port ID, which includes the storage image ID, or a shortened version without the storage image ID when the -dev parameter is specified. A port ID is prefixed with the letter I and consists of four hexadecimal characters in the format EEAP, where: v EE is an I/O port enclosure number in the range of 00 - 01 (1750 machine types). v A is the adapter number and is specified as 0, 1, 2, or 3 (1750 machine types). v P is the port number (0 - 3). To specify a range of port IDs, separate the port IDs with a hyphen. You must separate multiple port IDs or ranges of port IDs by a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the lsioport command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsioport command
dscli>lsioport dev IBM.2107-75FA120 -l

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120
291
ID IBM.2107 -75FA120 /I0111
WWPN 307BCF30 A3299E0
State Online
Type Fibre Channel-LW
Topo SCSI-FCP
Portgrp 0
Report field definitions (without the -metrics parameter)

ID WWPN Specifies the fibre channel worldwide port number. If the port type is not fibre channel, the value displayed is null (-). State Specifies the current I/O port status. One of the following values can be displayed: Online Indicates that the storage unit is capable of processing all functions (default). Offline Indicates that the storage unit is not capable of processing any functions. Resuming Indicates that the storage unit is in the process of coming online. Quiescing Indicates that the storage unit is in the process of going offline. Fenced Indicates that the storage unit has failed and is offline. Deconfigured Indicates that the I/O port is in the process of being deleted. Type Specifies the port type. The following values can be displayed: v Fibre Channel-SW - (SW stands for short wave) v Fibre Channel-LW - (LW stands for long wave) Specifies the I/O port topology. The following values can be displayed: v FC-AL v SCSI-FCP v FICON v Null (-) This value is displayed when the port type is not fibre channel. Specifies the identifier that associates a subset of the I/O ports that are operating in anonymous access mode. Default value is 0 when these subsets are not specified. Specifies the fully qualified port ID, which includes the storage image ID.
Topo
Portgrp
Report field definitions (with -metrics parameter)

When you use the -metrics parameter and do not specify a port type, two reports are displayed. One report is for the FICON I/O port type and the other report is for the SCSI-FCP I/O port type. A banner is displayed (for example: ===FICON-Enabled I/O Ports===) before each report. A report is not displayed for a port type that has no ports that are enabled.
292
FICON ports: Each of the following headers and value types are displayed: ID Date Specifies the fully qualified port ID. Specifies the current time stamp for the I/O port performance counters. For example, 08/11/05 02:23:49 is the format that is used to report this value.
byteread Specifies the number of bytes that are read in 128 KB increments. bytewrit Specifies the number of bytes that are written in 128 KB increments. Reads Specifies a value that is based on extended count-key-data (ECKD) data received operations. Writes Specifies a value that is based on ECKD data transferred operations. Timeread Specifies a value that is based on the ECKD data that is received (read-accumulated time) on a channel. The displayed value is based on increments of 16 milliseconds. Timewrite Specifies a value that is based on the ECKD data that is transferred (write-accumulated time) on a channel. The displayed value is based on increments of 16 milliseconds. SCSI-FCP ports: Each of the following headers and value types are displayed: ID Date Specifies the fully qualified port ID. Specifies the current time stamp for the I/O port performance counters. For example, 08/11/05 02:23:49 is the format used to report this value.
Bytewrit Specifies a value for the remote mirror and copy data transferred operations in increments of 128 KB. Byteread Specifies a value for the remote mirror and copy data received operations in increments of 128 KB. Writes Specifies a value for the remote mirror and copy data transferred operations. Reads Specifies a value for the remote mirror and copy data received operations. Timewrite Specifies a value that is based on the remote mirror and copy data transferred (write-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Timeread Specifies a value for the remote mirror and copy data received (read-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Byteread Specifies a value that is based on the SCSI data received operations. The displayed value is based on increments of 128 KB.
293
Reads Specifies a value that is based on the SCSI data transferred operations. Writes Specifies a value that is based on the SCSI data transferred operations. Timeread Specifies a value that is based on the SCSI data received (read-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Timewrite Specifies a value that is based on the SCSI data transferred (write-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds.
setioport
The setioport command configures one or more I/O ports for open systems or zSeries host system connections. This command cannot be used for ESCON ports.
setioport -dev storage_image_ID port_ID . . . - -topology fc-al scsi-fcp ficon
Parameters
-dev storage_image_ID | (Optional) Accepts a fully qualified storage image ID. The storage image ID consists of manufacturer, machine type, and serial number. Note: This parameter is required if you do not specify a fully qualified port ID and you do not specify a value for the devid variable in your profile file. -topology fc-al | scsi-fcp | ficon (Optional) Sets the topology for an I/O port, either Fibre Channel Arbitrated Loop, SCSI-FCP, or FICON. fibre channel arbitrated loop (code fc-al) The fc-al topology setting enables the SCSI ULP with a FC-AL topology. The FC-AL topology does not support PPRC path I/O operations. SCSI-FCP The SCSI-FCP topology setting enables the SCSI ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are enabled for this setting. ficon The ficon topology setting enables the FICON ULP with a point-to-point or switched fabric topology. PPRC path I/O operations are not supported for FICON ULP. port_ID . . . | (Required) Displays I/O ports matching the specified IDs. Accepts a fully qualified port ID, which includes the storage image ID, or a shortened version without the storage image ID when the -dev parameter is specified.
294
A port ID is prefixed with letter I and consists of four hexadecimal characters in the format EEAP, where: v EE is an I/O port enclosure number in the range of 00 - 01 (1750 machine types). v A is the adapter number and is specified as 0, 1, 2, or 3 (1750 machine types). v P is the port number (0 - 3). To specify a range of port IDs, separate the port IDs with a hyphen. You must separate multiple port IDs or ranges of port IDs by a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the setioport command This example configures four I/O ports for FICON topology.
dscli>setioport -dev IBM.175068FA120 -topology ficon I0011 I0021 I0111 I0121

Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.175068FA120 I/O I/O I/O I/O Port Port Port Port I0011 I0021 I0111 I0121 successfully successfully successfully successfully configured. configured. configured. configured.
showioport
The showioport command displays properties of an I/O port. It optionally displays the performance metrics for a specific I/O port.
showioport -dev storage_image_ID -metrics port_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the port. -metrics (Optional) Specifies that the port ID and the performance metrics for the specified I/O port be displayed. Note: All performance counts are an accumulation since the most recent counter wrap or counter reset operation. I/O port performance counters are reset with a storage unit power-on sequence. port_ID | (Required) Displays the property level details for the specified port IDs. This
295
parameter accepts a fully qualified unique port ID, that is represented in the following format: manufacturer.machine type-serial number/portID. For example, IBM.175068FA120/I0023 A port ID is prefixed with the letter I and consists of four hexadecimal characters in the format EEAP, where: v EE is an I/O port enclosure number in the range of 00 - 01 (1750 machine types). v A is the adapter number and is specified as 0, 1, 2, or 3 (1750 machine types). v P is the port number (0 - 3). If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showioport command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showioport command to show port information
dscli>showioport -dev IBM.210775FA120 I0112

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS:IBM.2107-75FA120 ID IBM.2107 -75FA120/ IO112 WWPN 307ACF30 A2399E0 State Online Loc U2107 75FA123I1-P1-C2-T1 Type Fibre channel-LW
Topo SCSI-FCP
Portgrp 0
unkSCSIlog -
Report field definitions (without the -metrics parameter)

ID WWPN Specifies the fibre channel I/O port worldwide port number (WWPN). If the port type is not fibre channel, this value is specified as a null (-). State Specifies the current state of the I/O port. One of the following values is displayed: Online Indicates that the storage unit is capable of processing all functions (default). Specifies the fully qualified unique port ID.
296
Offline Indicates that the storage unit is not capable of processing any functions. Resuming Indicates that the storage unit is in the process of coming online. Quiescing Indicates that the storage unit is in the process of going offline. Fenced Indicates that the storage unit has failed and is offline. Deconfigured Indicates that the I/O port is in the process of being deleted. Loc Specifies the storage enclosure location by identifying the storage unit frame that contains the storage enclosure. The location format is Utttt.mmm.ppsssss. Specifies the port type. The following values can be displayed: v Fibre Channel-SW - (SW stands for short wave) v Fibre Channel-LW - (LW stands for long wave) Specifies the port topology. If the port type is not fibre channel, then the displayed value is null (-). One of the following values is displayed: v FC-AL v SCSI-FCP v FICON v - (null if not fibre channel) Specifies an identifier that associates a subset of the I/O port objects that are operating in anonymous access mode. unkSCSIlog Specifies a list of unknown SCSI N-port WWPN identifiers that have attempted to login into this I/O port.
Type
Topo
Portgrp
Report field definitions (with the -metrics parameter)

ID Date Specifies the fully qualified port ID. Specifies the current time stamp for the I/O port performance counters. For example, 08/11/05 02:23:49 is the way that this value is reported.
byteread Specifies the number of bytes that are read in increments of 128 KB. bytewrit Specifies the number of bytes that are written in increments of 128 KB. Reads Specifies a value that is based on the extended count-key-data (ECKD) architecture data received operations. Writes Specifies a value that is based on the ECKD architecture data transferred operations.
297
Timeread Specifies a value that is based on the ECKD data received (read-accumulated time) on a channel. The displayed value is based on increments of 16 milliseconds. Timewrite Specifies a value that is based on the ECKD data transferred (write-accumulated time) on a channel. The displayed value is based on increments of 16 milliseconds. Bytewrit Specifies a value for the remote mirror and copy data transferred operation in increments of 128 KB. Byteread Specifies a value for the remote mirror and copy data received operations in increments of 128 KB. Writes Specifies a value for the remote mirror and copy data transferred operations. Reads Specifies a value for the remote mirror and copy data received operations. Timewrite Specifies a value based on the remote mirror and copy data transferred (write-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Timeread Specifies a value for the remote mirror and copy data received (read-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Byteread Specifies a value that is based on the SCSI data received operations. The displayed value is based on increments of 128 KB. Reads Specifies a value that is based on the SCSI data received operations. Writes Specifies a value that is based on the SCSI data transferred operations. Timeread Specifies a value that is based on the SCSI data received (read-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds. Timewrite Specifies a value that is based on the SCSI data transferred (write-accumulated) time on a channel. The displayed value is based on increments of 16 milliseconds.
Host connection commands

This section contains commands that are used to configure host connections and to display host connection information. Use the following commands to configure host connections and to display host connection information: v chhostconnect v lshostconnect v lshostvol
298
v v v v v v
lsportprof managehostconnect mkhostconnect rmhostconnect showhostconnect lshosttype
The chhostconnect command modifies a SCSI host port configuration. You must ensure that the host port is offline to the host system before you process the chhostconnect command. The lshostconnect command displays a list of host connections for a storage image and the status information for each host connection in the list. The lshostvol command displays the mapping of host device names or volume names to machine type 2105, 2107, and 1750 volume IDs. The lsportprof command displays a list of port profiles that are supported on a storage unit and their recommended address discovery and logical block size values. This command is particularly helpful to obtain the recommended values for the mkhostconnect command. The managehostconnect command modifies the volume group assignment for a SCSI host port. Ensure that the host port is offline to the host system before you process the managehostconnect command. The mkhostconnect command configures the open systems hosts port attachments to fibre-channel ports that are configured for FC-AL or SCSI-FCP topology. The rmhostconnect command removes a SCSI host port connection from a storage image. The showhostconnect command displays the detailed properties of a specified storage image host connection. The lshosttype command displays a list of known hosts, their associated port profiles, address discovery, and logical block size values.
chhostconnect
The chhostconnect command modifies a SCSI host port configuration.
chhostconnect -dev storage_image_ID -lbs 512 520
-addrdiscovery
reportlun lunpolling
-profile
port_profile_name
-hosttype
host_type
-portgrp
port_grp_number
-volgrp
volume_group_ID none
299
-ioport
port_ID all none . . .
-desc
description
-name
new_host_name
host_connection_ID -
Parameters
Notes: 1. The chhostconnect command can be disruptive to host system I/O operations if the affected host port is logged into the target storage unit. You must ensure that the host port is offline to the host system before you process the chhostconnect command. 2. Using the -hosttype parameter when you issue this command allows you to save input and processing time. The -hosttype parameter supplies the same information as if you had used the following three parameters: v -profile v -addrdiscovery v -lbs 3. If you are using the HP-UX operating system, see the volume restriction that is described under the -addrdiscovey parameter. -dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified host connection ID. Example of a fully qualified storage image ID: IBM.1750-68FA120 -lbs 512 | 520 (Optional) Specifies the logical block size that is used by the host system. The block size must be compatible with the volume group type and the volume type configurations that apply to the host port connection. The 520 logical block size is typically used by the IBM iSeries systems (OS/400). Notes: 1. You cannot use the -lbs parameter and -hosttype parameter together, but you can use each one separately. 2. If you do not use the -hosttype parameter, use the lsportprof command to determine the block size that you need to specify for the -lbs parameter. -addrdiscovery reportlun | lunpolling (Optional) Specifies the method for identifying logical unit number (LUN) addresses. v The reportlun method specifies that the host system can access up to 64 000 LUNs. v The lunpolling method specifies that the host system can access up to 256 LUNs. Notes:
300
1. You cannot use the -addrdiscovery parameter and -hosttype parameter together, but you can use one separately. 2. For HP-UX operating systems, the number of volumes in the volume group must not exceed seven volumes. This restriction only applies when the -addrdiscovery parameter is set to reportlun and the associated volume group is of type scsimap256. -profile port_profile_name (Optional) Specifies the name of the host connection behavior profile. If the name includes a blank space, enclose the name with double quotation marks. For example, -profile IBM pSeries Sun. Notes: 1. You cannot use the -profile parameter and the -hosttype parameter together, but you can use one separately. 2. If you do not use the -hosttype parameter, use the lsportprof command to obtain a list of available profiles. -hosttype host_type (Optional) Specifies information about the following three parameters: v -profile v -addrdiscovery v -lbs Notes: 1. You cannot use the -hosttype parameter with the -profile, addrdiscovery, or -lbs parameters. 2. Use the lshosttype command to obtain a list of known host types. -portgrp port_grp_number (Optional) Specifies a user-assigned number that associates two or more host ports with access to a common volume group. Port group zero is reserved for ports that have not been associated with a port group. -volgrp volume_group_ID | none (Optional) Specifies an available volume group or no volume group if the none subparameter is used. This command accepts a fully qualified volume group ID including the storage image ID or a shortened version if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeros, prefixed with the letter V. Examples of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the -volgrp parameter as follows:
dscli>chhostconnect -dev IBM.1750-68FA120 V11 1
where 1 represents the required parameter, host_connection_ID. If you do not specify the -dev parameter and you specify the -volgrp parameter, you must use the fully qualified version of the volume group ID with the -volgrp parameter specified as follows:
dscli>chhostconnect -volgrp IBM.1750-68FA120/V11 IBM.1750-68FA120/1
where IBM.1750-68FA120/1 or IBM.2107-75FA120/1 represents the required parameter, host_connection_ID

301
A host connection can use only one volume group per storage image. In other words, a single WWPN can access only one volume group per storage image. Host operations cannot be initiated until a volume group ID is assigned. If none is specified, the volume group ID assignment is removed from a SCSI host port object. -ioport port_ID all|none| . . . (Optional) Specifies all, none, one, or more I/O port IDs that allow host connection access to volumes. This command accepts a fully qualified port ID including the storage image ID or a shortened version if the -dev parameter is specified. all Specifies that you want to add all I/O port IDs. This allows the specified host connection access to the designated volume group through all the associated I/O port IDs. Specifies that you do not want to add any I/O ports. If you do not specify I/O ports, the storage unit is configured to allow host connection access to the specified volume group using any I/O port that is configured for FC-AL or SCSI-FCP topology.
none
... (ellipsis) Specifies that you can designate up to 128 ports for an open systems host attachment assignment. If you enter a list of I/O port IDs, access from the specified host connection to the specified volume group is allowed using only the designated list of port IDs. Examples of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the -ioport parameter as follows:
dscli>chhostconnect -dev IBM.1750-68FA120 -ioport I0102 1
where 1 represents the required parameter, host_connection_ID. If you do not specify the -dev parameter and you specify the -ioport parameter, you must use the fully qualified version of the port ID with the -ioport parameter specified as follows:
dscli>chhostconnect -ioport IBM.1750-68FA120/I0102 IBM.1750-68FA120/1
where IBM.1750-68FA120/1 or IBM.2107-75FA120/1 represents the required parameter, host_connection_ID A port ID is prefixed with the letter I and consists of four hexadecimal characters in the format EEAP, where: v EE is an I/O port enclosure number in the range of 00 - 01 (1750 machine types). v A is the adapter number and is specified as 0, 1, 2, or 3 (1750 machine types). v P is the port number (0 - 3). To specify a range of port IDs, separate the port IDs with a hyphen. Separate multiple port IDs or ranges of port IDs with a comma between each ID or range of IDs.
302
Note: Changing the I/O port values can result in a disruption of current logins by the host systems. -desc description (Optional) Specifies the description that you defined for the SCSI host port. The description is limited to 256-byte or 128 double-byte characters. -name new_host_name (Optional) Specifies the user-assigned host system or port name. The name is limited to 32-byte or 16 double-byte characters. host_connection_ID | (Required) Specifies the host connection ID, which is a unique identifier that uses any number from 0 - FFFE within the scope of a storage image. This parameter accepts a fully qualified ID or a shortened version if the -dev parameter is specified. Examples of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the host_connection_ID parameter as follows:
dscli>chhostconnect -dev IBM.1750-68FA120 -desc newdescription 1
where 1 represents the value for the host_connection_ID. If you do not specify the -dev parameter and you specify the host_connection_ID parameter, you must use the fully qualified version of the host connection ID as follows:
dscli>chhostconnect -desc newdescription IBM.1750-68FA120/1
If you specify the dash (-), this parameter information is automatically supplied. Attention: Use caution when you work with connection IDs to ensure that you have specified the correct connection that you want to change. For example, if you intend to make a change to connection ID 0005 and type 000, the system makes the change to connection ID 0. Or, if you want to make a change to connection ID 0020 and type 002, the system makes the change to connection ID 2. The system does not recognize the leading zeros, and 000 is interpreted as connection ID 0 and 002 is interpreted as connection ID 2.
Example (1750)
Invoking the chhostconnect command
dscli>chhostconnect -dev IBM.175068FA120 -name host_1_port_2 1

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.175068FA120 Host connection 1 successfully modified.
lshostconnect
The lshostconnect command displays a list of host connections for a storage image and the status information for each host connection in the list. You can also use this command to obtain a list of worldwide port numbers (WWPNs) from a system-detected-unknown host port. You can use these WWPNs to create a new host connection using the mkhostconnect command.
303
lshostconnect -dev storage_image_ID -s -l -portgrp port_grp_number
-volgrp
volume_group_ID
-unknown
-login
host_connection_ID . . . -
Parameters
-dev storage_image_ID (Optional) Displays the host connections for the specified storage image. A storage image ID consists of manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified host connection ID and you do not specify a value for the devid variable in your profile file. Example of a fully qualified storage image ID: IBM.1750-68FA120 -s -l (Optional) Specifies the host connection IDs. You cannot use the -l and -s parameters together. (Optional) Specifies the default output and your description for each host connection in the list. You cannot use the -l and -s parameters together.
-portgrp port_grp_number (Optional) Specifies the host connections that have an associated group number. | | Note: You cannot use the -portgrp parameter with the -unknown or -login parameters. -volgrp volume_group_ID (Optional) Specifies that only the host connections with the specified volume group ID be displayed. The volume group ID is a four-digit decimal number with no leading zeros, prefixed with the letter V. | | Note: You cannot use the -volgrp parameter with the -unknown or -login parameters. -unknown (Optional) Specifies that a list of logged in host ports (WWPNs), that are not recognized as being associated with the designated storage unit, be displayed. This parameter generates a list report that contains the following three information fields: v WWNN v WWPN v ESSIOport | | | | | | | Note: You cannot use the -unknown parameter with the -portgrp, -volgrp, -login or host_connection_ID parameters. -login (Optional) Specifies that a list be displayed of host port (WWPNs) that are logged in and sorted by the ESS I/O port IDs for known connections. The report displays one line of information per connection. However, no information is displayed for a FICON connection.
304
| | | | | | |
Notes: 1. Known logins are those that you have created a host connection for, as well as Remote Mirror and Copy paths and anonymous connections. 2. You cannot use the -login parameter with the -unknown, -portgrp, -volgrp, or host_connection_ID parameters. host_connection_ID . . . | (Optional) Specifies that host connection information for the specified host connection IDs be displayed. This parameter accepts a fully qualified ID (includes manufacture. machine type, serial number/hostconnectID) or a shortened version if the -dev parameter is specified. Note: You cannot use the host_connection_ID parameter with the -login or -unknown parameters. If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified host connection ID: IBM.1750-68FA120/2 Example of a shortened version host connection ID: 0002
| |
Example
| | | Note: You can receive different reports when you use the lshostconnect command, one for the -unknown parameter, one for the -login parameter, one for the -l parameter, and one for the -s parameter. The reports that are associated with the -unknown, -login, and -l parameters are provided in this description. For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the lshostconnect command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lshostconnect command without the -unknown parameter
dscli>lshostconnect -dev IBM.210775FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Addrdis covery reportLUN reportLUN
Name My host port 1 My host port 2
ID IBM.210775FA120/1 IBM.210775FA120/2
WWPN 3007ACF3 0A2399E0 3007ACF3 0A2399E1
HostType Unknown Unknown
LBS 512 512
305
Profile IBM pSeries - AIX IBM pSeries - AIX
portgrp 0
volgrpID V100
achtopo SCSI -FCP SCSI -FCP
ESSIOport I0111,I0121 I0211,I0221 All
Desc SCSI1
V100
SCSI2
Example of lshostconnect using the -unknown parameter

Invoking the lshostconnect command with the -unknown parameter
dscli>lshostconnect -dev IBM.210775FA120 -unknown

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 WWNN 3007ACF30A239900 3007ACF30A239900 3007ACF30A239900 3007ACF30A239900 WWPN 3007ACF30A2399E0 3007ACF30A2399E1 3007ACF30A2399E2 3007ACF30A2399E3 ESSIOport I0111, I0121, I0211, I0221 I0121 I0111, I0121, I0211, I0221 I0111
| | | | | | | | | | | | | | | |
Example of lshostconnect using the -login parameter

Invoking the lshostconnect command with the -login parameter
dscli>lshostconnect -dev IBM.210775FA120 -login

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 WWNN 3007ACF3 0A239900 3007ACF3 0A239900 3007ACF3 0A239900 WWPN 3007ACF3 0A2399E0 3007ACF3 0A2399E1 3007ACF3 0A2399E2 ESSIOport I0111 I0111 I0221 LoginType SCSI SCSI SCSI Name MyHostA MyHostB ID 1 1 -
Report field definitions when the -unknown or -login parameter is not used
Name Host connection/SCSI port nickname. The name is limited to 32-byte or 16 double-byte characters. ID A fully qualified host connection ID: manufacturer.type-serial number/hostconnectID The host connection ID component is a unique identifier (0 - FFFE) within the scope of a storage unit.
306
WWPN Specifies the worldwide port name (WWPN) for this host system port. HostType Specifies the name of the host type. Unknown is displayed when the information is not available and indicates that the host type was not specified when the host connection was created or modified. LBS Specifies the logical block size that is used by the designated host system and host system port. The logical block setting must be compatible with the volume group type that is configured for volume access. The 520 block size is typically used for IBM iSeries host system attachments. Addrdiscovery Specifies the LUN address discovery method used by the designated host system and host system port. The LUN Discovery method must be compatible with the volume group type that is configured for volume access. The Poll LUNs method enables access to a maximum of 256 LUNs. The Report LUNs method enables access to a maximum of 64 000 LUNs. Profile Specifies the name of the host connection behavior profile. Portgrp Specifies the host port group ID. This ID ties together a group of SCSI host port objects that are accessing a common volume group. If the port group value is set to zero, the host port is not associated with any port group. VolgrpID Specifies the volume group ID. This ID is a unique identifier within the DS6000 for the SCSI volume group that the specified SCSI host port is assigned to. Achtopo Specifies the topology of the attached unit. This value is used to select which storage facility I/O ports are compatible with the attachment to the specified storage unit. One of the following values is displayed: v Unknown v SCSI-FCP v FC-AL ESSIOport Specifies the array of port IDs that the designated host port is logged into. The port ID component is four hexadecimal characters in the format EEAP, where EE is a port enclosure number 00 - 01 for 1750, A is the adapter number 0 - 3 for 1750, and P is the port number (0 - 3). The number is prefixed with the letter I. Desc Specifies the description that you defined for the SCSI host port. The description is limited to 256 byte or 128 double-byte characters.
307
Report field definitions when the -unknown parameter is used

WWNN Specifies the worldwide node name for the designated host system. WWPN Specifies the worldwide port name for the designated host system port. ESSIOport Specifies the array of port IDs that the designated host port is logged into. The port ID component is four hexadecimal characters in the format EEAP, where EE is a port enclosure number 00 - 01 for 1750, A is the adapter number 0 - 3 for 1750, and P is the port number (0 - 3). The number is prefixed with the letter I. | | | | | | | | | | | | | | | | | | | | |
Report field definitions when the -login parameter is used

WWNN Specifies the worldwide node name (WWNN) for this host system. WWPN Specifies the worldwide port name (WWPN) for this host system port. ESSIOport Specifies the port ID that the designated host port is logged into. The port ID component is four hexadecimal characters in the format EEAP, where EE is a port enclosure number 00 - 01 for 1750, A is the adapter number 0 - 3 for 1750, and P is the port number (0 - 3). The number is prefixed with the letter I. LoginType Specifies the type of login such as SCSI. Name Specifies the name that you assigned to the host. If a name is not assigned, a null (-) value is displayed. ID A fully qualified host connection ID: manufacturer, machine type, serial number/hostconnectID The host connection ID component is a unique identifier (0 - FFFE) within the scope of a storage unit.
lshostvol
The lshostvol command displays the mapping of host device names or volume names to machine type 2105, 2107, and 1750 volume IDs. (This command is not supported on the i5/OS.)
lshostvol
Parameters
There are no parameters for this command. Notes: 1. The lshostvol command displays only volumes that are accessed using a direct fibre channel path when you use the command on an
308
OpenVMS host system that is a member of an OpenVMS cluster. The command output does not display information about the following OpenVMS cluster devices: v Volumes to which the host system only has MSCP paths. v Volumes to which the host system uses only MSCP paths at this time even though it has both MSCP and direct paths. 2. If you do not have installed the IBM Multipath Subsystem Device Driver (SDD), the virtual path (vPath) name is not displayed. 3. On a Red Hat Enterprise Linux system, attached devices might be detected by the HBA driver, but they are not registered with the operating system. Normally, the operating system is set up to automatically detect all LUNS. However, if this does not occur automatically, you must issue the following for every volume (LUN):
echo scsi add-single-device host# channel# lun# >/proc/scsi/scsi
If SDD is installed on your system, you can run the scsiscan script to detect all the LUNs.
Example
The information that is displayed on the report that is generated from the lshostvol command is different depending on whether you have SDD installed. The following example tables indicate the differences. For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the lshostvol command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lshostvol command
dscli>lshostvol
The resulting output with SDD installed

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.175075FA120 Device/Volume Name my_vol_01,my_vol_04 my_vol_02,my_vol_05 my_vol_03,my_vol_06 my_vol_07,my_vol_09 my_vol_08,my_vol_10 Volume ID IBM.1750-75DA110/175D IBM.1750-75EA120/175E IBM.1750-75FA130/175F IBM.2105-29239/119E IBM.2105-29239/119F Vpath Name vpath01 vpath02 vpath03 Vpath04 Vpath05
The resulting output without SDD installed

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.175075FA120 Device/Volume Name Hdisk01 Volume ID IBM.1750-75DA110/175D Vpath Name -
309
Device/Volume Name Hdisk02 Hdisk03 Hdisk07 Hdisk08
Volume ID IBM.1750-75EA120/175E IBM.1750-75FA130/175F IBM.2105-29239/119E IBM.2105-29239/119F
Vpath Name -
Report column definitions

Device/Volume name Specifies the nickname you assigned to the device or volume. When SDD is installed, this column reports the volume name instead of the device name. Volume ID Specifies the ID of the storage unit. Vpath name Specifies the virtual path name. When SDD is not installed, this value is reported as null (-).
lsportprof
The lsportprof command displays a list of port profiles that are supported on a storage unit and their recommended address discovery and logical block size values. You can use this command to view known values for the block size (lbs) and address discovery (addrdiscovery) parameters in the mkhostconnect command. Note: Use this command to get the recommended values for the mkhostconnect command.
lsportprof storage_image_ID -
Parameters
storage_image_ID | (Required) Displays a list of port profiles for the specified storage image IDs. A storage image ID consists of manufacturer, type, and serial number. If you specify the dash (-), this parameter information is automatically supplied. Example: IBM.1750-68FA120
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lsportprof command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsportprof command
dscli>lsportprof IBM.2107-75FA120
310

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Name IBM pSeries AIX IBM pSeries pLinux AddrDiscovery ReportLUN LUNPolling LBS 512 512

Name Specifies the name of the host connection behavior profile. The port profile specifies a given host or operating system type. AddrDiscovery Specifies the address discovery method. One of the following values is displayed: LUN Polling Specifies that host system LUN access is limited to a maximum of 256 LUNs. Report LUN Specifies that host system LUN access is limited to a maximum of 64000 LUNs LBS Specifies the logical block size. One of the following values is displayed: v 512 - This value is displayed for all hosts except OS400. v 520 - This value is displayed for an OS400 host.
managehostconnect
The managehostconnect command modifies the volume group assignment for a SCSI host port.
managehostconnect -dev port_grp_number - storage_image_ID -volgrp volume_group_ID none
Parameters
Notes: 1. The managehostconnect command can be disruptive to host system I/O operations if the affected host port is logged onto the target storage unit. Ensure that the host port is offline to the host system before you process the managehostconnect command. 2. This command is used more effectively after you have issued the lshostconnect or showhostconnect commands and have analyzed the reports that are generated by these commands. The information that is reported by these commands can help you ensure that you specify the correct port group number when you issue the managehostconnect command. -dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number.
311
-volgrp volume_group_ID | none (Required) Specifies that the SCSI host port connections that are associated with the specified port group number will be modified to access this volume group ID. A volume group ID is a four-digit decimal number with no leading zeroes, prefixed with the letter V. If none is specified, the volume group ID assignment is removed from all SCSI host port objects that are associated with a common port group number. Example: -volgrp none port_grp_number | (Required) Specifies the SCSI host port group number that associates two or more host ports as having access to a common volume group. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the managehostconnect command
dscli>managehostconnect -dev IBM.1750-68FA120 -volgrp 11 1

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Port group number 1 successfully modified.
mkhostconnect
The mkhostconnect command configures open systems hosts port attachments to fibre-channel ports that are configured for FC-AL or SCSI-FCP topology. Open systems hosts port attachments to fibre-channel ports are configured for identified access mode and SCSI protocol.
mkhostconnect -dev storage_image_ID -wwname wwpn -lbs 512 520
-addrdiscovery
reportlun lunpolling
-profile
port_profile_name
-hosttype
host_type
-portgrp
port_grp_number
-volgrp
volume_group_ID
-ioport
port_ID . . .
-desc
description
host_name -
Parameters
Notes: 1. It is recommended that you use the -hosttype parameter when you issue this command, because doing so saves input and processing time. The -hosttype parameter supplies the same information as if you had used the following three parameters: v -profile
312
v -addrdiscovery v -lbs 2. If you are using the HP-UX operating system, see the volume restriction that is described under the -addrdiscovey parameter. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes the manufacturer, type, and serial number. -wwname wwpn (Required) Specifies the worldwide port name (WWPN). The WWPN is a 16-character hexadecimal ID. The names are host attachment specific; for example, 12341234000A000F. -lbs 512 | 520 (Optional) Specifies the logical block size that is used by the specified host system, in bytes. The block size must be compatible with the volume group type and the volume type configurations that apply to the specified host port connection. The 520-byte size is typically used by IBM iSeries systems (OS/400). Notes: 1. Do not use the -lbs parameter if you specify the -hosttype parameter. 2. If you do not use the -hosttype parameter, use the lsportprof command to determine the block size that you need to specify. -addrdiscovery reportlun | lunpolling (Optional) Specifies the method for discovering logical unit number (LUN) addresses. v The reportlun method specifies that the host system can access up to 64 000 LUNs. Note: Use the reportlun method only with volume groups that are designated as mask type. (This designation is assigned when you use the mkvolgrp command to create the volume group.) However, you can use the reportlun method for a map type, but there are additional considerations if you are using an HP-UX operating system. For HP-UX operating systems, the number of volumes in the volume group must not exceed seven volumes. This restriction only applies when the -addrdiscovery parameter is set to reportlun and the associated volume group is of type scsimap256. v The lunpolling method specifies that the host system can access up to 256 LUNs. For Sun, Linux, and Windows operating systems, the lunpolling method is typically selected. Notes: 1. Use the lunpolling method only with volume groups that are designated as map type. (This designation is assigned when you use the mkvolgrp command to create the volume group.) 2. Do not use the -addrdiscovery parameter if you specify the -hosttype parameter. -profile port_profile_name (Optional. If you specify the -hosttype parameter, this parameter is not used.)
313
Specifies the name of the host connection behavior profile. If the name includes a blank space, enclose the name with double quotation marks. For example, -profile IBM pSeries AIX. Notes: 1. Do not use the -profile parameter if you specify the -hosttype parameter. 2. If you do not use the -hosttype parameter, use the lsportprof command to obtain a list of available profiles. -hosttype host_type (Optional) Specifies information about the following three parameters: v -profile v -addrdiscovery v -lbs Notes: 1. When the -hosttype parameter is specified, do not use the -profile, addrdiscovery, or -lbs parameters. 2. Use the lshosttype command to obtain a list of known host types. -portgrp port_grp_number (Optional) Specifies the identifier that associates two or more host ports with access to a common volume group. Port group zero is reserved for ports that have not been associated with a port group. -volgrp volume_group_ID (Optional) Specifies an available volume group. This parameter accepts a fully qualified volume group ID including the storage image ID or a shortened version. The shortened version is a four-digit decimal number with no leading zeroes, prefixed with the letter V. A host connection uses only one volume group per storage image; that is, a single WWPN can access only one volume group per storage image. Note: If you do not specify a volume group when a host connection is created, the value for volume group is displayed as a null (-) when you issue a lshostconnect or showhostconnect command. -ioport port_ID . . . (Optional) Specifies all, none, one, or more I/O port IDs that allow host connection access to volumes. Enter all to specify that you want all I/O ports added. Enter none to specify that you do not want to add I/O ports. If you do not specify I/O ports, the image is configured to allow host connection access to the specified volume group using any I/O port that is configured for FC-AL or SCSI-FCP topology. I/O ports cannot share the same WWPN. Ensure that there are no conflicts with the I/O ports of existing SCSI host connections. You can select up to 128 ports for an open systems host attachment assignment. If you enter a list of I/O port IDs, access from this host connection to the specified volume group is allowed using only the specified list. A port ID is four hexadecimal characters in the format EEAP, where:
314
v EE is an I/O port enclosure number in the range of 00 - 01 (1750 machine types). v A is the adapter number and is specified as 0, 1, 2, or 3 (1750 machine types). v P is the port number (0 - 3). This number is prefixed with the letter I. To specify a range of port IDs, separate the port IDs with a hyphen. You must separate multiple port IDs or ranges of port IDs with a comma between each ID or range of IDs. -desc description (Optional) Specifies the description that you defined for the SCSI host port. The description is limited to 256 byte or 128 double-byte characters. host_name | (Required) Specifies your host system or port name, limited to 16 characters. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkhostconnect command
dscli>mkhostconnect -dev IBM.1750-68FA120 wwname 12341234000A000F profile IBM pSeries AIX host_1_port_1

Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Host connection 0 successfully created.
rmhostconnect
The rmhostconnect command removes a SCSI host port connection from a storage image.
rmhostconnect -dev storage_image_ID -quiet host_connection_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all host connections. -quiet (Optional) Turns off the confirmation prompt. host_connection_ID | (Required) Specifies the host connect ID, which is a unique identifier that uses any number from 0 - FFFE within the scope of a storage image. This parameter accepts a fully qualified ID (includes manufacture.type-serial number/hostconnectID) or a shortened version if the -dev parameter is specified. Example of a fully qualified host connection ID: IBM.1750-68FA120/2
315
If you specify the dash (-), this parameter information is automatically supplied. Attention: Use caution when you work with connection IDs to ensure that you have specified the connection that you want to delete. For instance, if you intend to delete connection ID 0005 and type 000, the system deletes connection ID 0. Or, if you want to delete connection ID 0020 and type 002, the system deletes connection ID 2. The system does not consider the leading zeros, and 000 is interpreted as connection ID 0 and 002 is interpreted as connection ID 2.
Example (1750)
Invoking the rmhostconnect command
dscli>rmhostconnect -dev IBM.1750-68FA120 1

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete Host Connection IBM.1750-68FA120/1? y/n Y Host Connection IBM.1750-68FA120/1 successfully deleted.
showhostconnect
The showhostconnect command displays detailed properties of a storage image host connection.
showhostconnect -dev storage_image_ID host_connection_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the host connection. host_connection_ID | (Required) Specifies a fully qualified host connection ID, which includes the manufacturer, type, and sequence number if the -dev parameter is not used. The host connection ID is a unique identifier (0 - FFFE) within the scope of a storage image. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showhostconnect command. A separate example is not shown for the 1750 because the information is the same for both the 1750 and 2107. Invoking the showhostconnect command
dscli>showhostconnect -dev IBM.210775FA120
316

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 Addrdis covery reportLUN
Name My host port 1
ID IBM.210775FA120/1
WWPN 3007ACF3 0A2399E0
HostType Unknown
LBS 512
Profile IBM pSeries - AIX
Portgrp 0
VolgrpID 100
Achtopo SCSI -FCP
ESSIOport I0111,I0121 I0211,I0221
Desc SCSI1

Name Specifies the host connection SCSI port nickname. The name is limited to 32 byte or 16 double-byte characters. ID Specifies a fully qualified host connection ID. The value that is represented by the host_connection_ID parameter is a unique identifier (0 - FFFE) within the scope of a storage unit. WWPN Specifies the worldwide port name (WWPN) for the designated host system port. HostType Specifies the name of the host type. Unknown is displayed when the information is not available. This indicates that the host type was not specified when the host connection was created or modified. LBS Specifies the logical block size that is used by this host system and the host system port. The logical block setting must be compatible with the volume group type that is configured for volume access. The 520 block size is typically used for IBM iSeries host system attachments. Addrdiscovery Specifies the LUN address discovery method that is used by this host system and the host system port. The LUN Discovery method must be compatible with the volume group type that is configured for volume access. The Poll LUNs method enables access to a maximum of 256 LUNs. The Report LUNs method enables access to a maximum of 64 000 LUNs. Profile Specifies the name of the host connection behavior profile. Portgrp Specifies the host port group ID. The ID ties together a group of SCSI host port objects that are accessing a common volume group. If the port group value is set to zero, the host port is not associated with any port group.
317
VolgrpID Specifies the volume group ID. This ID is a unique identifier within the DS6000 for the SCSI volume group that the specified SCSI host port is assigned to. Achtopo Specifies the topology of the attached unit. This value is used to select which storage facility I/O ports are compatible with the attachment to the specified storage unit. One of the following values is displayed: v Unknown v SCSI-FCP v FC-AL ESSIOport Specifies the array of port IDs that the designated host port is logged into. The port ID component is four hexadecimal characters in the format EEAP, where EE is a port enclosure number 00 - 01 for the 1750, A is the adapter number 0 - 3 for the 1750, and P is the port number (0 - 3). The number is prefixed with the letter I. Desc Specifies the description you defined for the SCSI host port. The description is limited to 256 byte or 128 double-byte characters.
lshosttype
The lshosttype command displays a list of known hosts, their associated port profiles, address discovery, and logical block size values. Use this command to get the available host types for the mkhostconnect command.
lshosttype -s -l -type volumeGroup_type
Parameters
-s -l (Optional) Displays the host types only. You cannot use the -l and -s parameters together. (Optional) Displays the default output for the specified host type. You cannot use the -l and -s parameters together.
-type volumeGroup_type (Required) Displays only those host types that are associated with the specified volume group type. volumeGroup_type Only one type can be queried at a time. The following list provides the choices that can be specified. v ficonall v scsiall v scsimask v scsimap256 v os400all v os400mask
318
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lshosttype command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lshosttype command
dscli>lshosttype -l -type scsiall

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 Host Type pSeries Profile IBM pSeries AIX AddrDiscovery reportlun LBS 512 Description IBM pSeries, RS/6000 and RS/6000 SP Servers (AIX)

Host Type Specifies the name of the specific host type. Profile Specifies the name of the host connection behavior profile. The port profile specifies a given host or operating system type. AddrDiscovery Specifies the address discovery method. One of the following values is displayed: LUN Polling Specifies that host system LUN access is limited to a maximum of 256 LUNs. Report LUN Specifies that host system LUN access is limited to a maximum of 64K LUNs LBS Specifies the logical block size. One of the following values is displayed: v 512 - This value is displayed for all hosts except OS400. v 520 - This value is displayed for an OS400 host.
Description Specifies additional host type details.
Storage configuration commands

This section contains storage configuration commands. The following commands allow you to configure storage for zSeries and open system hosts.
319
Array site specific commands

This section contains commands that are used to display array site information. Use the following commands to display array site image information: v lsarraysite v showarraysite The lsarraysite command generates a report that lists the array sites and status information for each array site in the list. The showarraysite command generates a report that displays the detailed properties of a specific storage image array site.
lsarraysite
The lsarraysite command displays a list of array sites and status information for each array site in the list.
lsarraysite -dev storage_image_ID -s -l -dapair dapair_ID
-cap
capacity
-array
array_ID
-state
assigned unassigned abnormal initializing
site_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if the qualified site ID is not specified. -s -l (Optional) Displays the array ID. You cannot use the -l and the -s parameters together. (Optional) Displays the default output and the disk drive module rpm (revolutions per minute). You cannot use the -l and the -s parameters together.
-dapair dapair_ID (Optional) Displays array sites that are associated with a common device adapter pair ID. A device adapter pair ID is a two-digit decimal number with no leading zeros. -cap capacity (Optional) Displays in gigabytes (GB) the array sites that have the specified capacity of the disk drive module. -array array_ID (Optional) Displays the array site that is associated with the specified array ID. An array ID is a four-digit decimal number with no leading zeros, prefixed with the letter A.
320
-state assigned | unassigned | unavailable | initializing (Optional) Displays array sites that are in the specified state. One of the following values is displayed: assigned Specifies that the designated array site is defined as an array. unassigned Specifies that the array site is available to be defined as an array. unavailable Specifies that the designated array site is unassigned and at least one disk is not in the normal state. Also, the array site is not in the initializing state. initializing Specifies that the array site is unassigned and all disks are either in the normal or initializing state. Also, at least one disk is in the initializing state. site_ID . . . | (Optional) Displays array sites that have the specified IDs. An array site identifier is a four-digit decimal number with no leading zeros, prefixed with the letter S. To specify a range of array site IDs, separate the array site IDs with a hyphen. You must separate multiple array site IDs or ranges of array site IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsarraysite command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsarraysite command
dscli>lsarraysite -dev IBM.2107-75FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Dkcap (10^9B) 300
Arsite IBM.210775FA120/ S10 IBM.210775FA120/ S11
DA pair IBM.210775FA120 /11 IBM.210775FA120 /11
Diskrpm 1500
State Assigned
Array IBM.210775FA120 /A100 IBM.210775FA120 /A101
Diskclass ENT
300
1500
Assigned
ENT
321
Arsite IBM.210775FA120/ S12 IBM.210775FA120/ S13
DA pair IBM.210775FA120 /12 IBM.210775FA120 /12
Dkcap (10^9B) 300
Diskrpm 1500
State Assigned
Array IBM.210775FA120 /A102 IBM.210775FA120 /A103
Diskclass NL
300
1500
Assigned
NL

Arsite Specifies the array site ID. The array site ID is a four-digit decimal number, with no leading zeros, prefixed with the letter S. Note: The array site ID does not point to a physical location. DA pair Identifies the DA pair ID. DA pairs are located in I/O enclosure pairs. The DA pair ID indicates the I/O enclosure location. Note: An even-numbered DA pair ID indicates the first DA pair in an I/O enclosure pair. An odd-numbered DA pair ID indicates the second DA pair in an I/O enclosure pair. Dkcap (10^9 Byte) Specifies the minimum disk capacity of the disks in the designated array site in gigabytes. Diskrpm Specifies the minimum disk rpm of the disks in the designated array site. State Specifies the array site state. One of the following values can be displayed in this field: Assigned Specifies that the designated array site is defined as an array. Unassigned Specifies that the array site is available to be defined as an array. Unavailable Specifies that the designated array site is unassigned and at least one disk is not in the normal state. Also, the array site is not in the initializing state. Initializing Specifies that the array site is unassigned and all disks are either in the normal or initializing state. Also, at least one disk is in the initializing state. Array Specifies the array ID that this assigned array site is assigned to. The ID is prefixed by the letter A. Disk class Specifies the disk class as either high speed fibre-channel disk drives or near-line disk drives. The displayed value is one of the following: ENT NL Specifies enterprise and represents high speed fibre channel disk drives. Specifies near-line and represents ATA (FATA) disk drives
322
showarraysite
The showarraysite command displays detailed properties of a specific storage image array site.
showarraysite -dev storage_image_ID site_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the site ID. site_ID | (Required) Specifies that information be displayed for the designated array site ID. This parameter also accepts a fully qualified site ID, which consists of the storage image ID or a shortened version without the storage image ID, if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeros, prefixed by the letter S. The array site ID does not imply a physical location. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showarraysite command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showarraysite command
dscli>showarraysite -dev IBM.210775FA120 S11

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120 dkcap (10^9B) 146
arsite IBM.210775FA120/ S11
DA pair IBM.210775FA120 /0
Diskrpm 15000
State Assigned
Array IBM.210775FA120 /A44
Dkrate (GB/sec) 2
DDMSN 0123456789 ABCDEF
Spares 0
dataDDM 8
Diskclass NL
323

Arsite Specifies the array site ID. The array site ID is a four-digit decimal number, no leading zeros, prefixed by the letter S. Notes: 1. IBM 1750 array sites consist of four DDMs. 2. The array site ID does not imply a physical location. DA pair Specifies the DA pair ID. DA pairs are located in I/O enclosure pairs. DA pair ID implies the I/O enclosure location. Dkcap (10^9B) Specifies the minimum disk capacity of the disks in the designated array site. Diskrpm Specifies the minimum disk rpm of the disks in the designated array site. State Specifies the array site state. The values that can be displayed in this field are as follows: assigned Specifies that the designated array site is defined as an array. unassigned Specifies that the array site is available to be defined as an array. unavailable Specifies that the designated array site is unassigned and at least one disk is not in the normal state. Also, the array site is not in the initializing state. initializing Specifies that the array site is unassigned and all disks are either in the normal or initializing state. Also, at least one disk is in the initializing state. Array Specifies the array ID that the designated array site is assigned to. The ID is prefixed by the letter A. Dkrate Specifies the minimum disk interface rate of the disks in the designated array site. DDMSN Specifies the list of DDM serial numbers (SN) that are associated with the designated array site. Each DDM SN is a 16-character string. Each serial number is separated by a comma. Spares Specifies the number of spare DDMs that are allocated from the array site. DataDDM Specifies the number of data DDMs. This value is based on the number of DDMs minus the number of spares. Disk Class Specifies the disk class as either high speed fibre channel disk drives or near-line disk drives. The displayed value is one of the following:
324
ENT NL
Specifies enterprise and designates a high-speed fibre channel disk drive. Specifies near-line and represents ATA (FATA) disk drives.
Array specific commands

This section contains commands that are used to create and delete arrays and to display array information. Use the following commands to create and delete arrays and to display array information: v lsarray v mkarray v rmarray v showarray The lsarray command generates a report that displays a list of arrays in a storage image and the status information for each array in the list. The mkarray command creates one array per command. The rmarray command removes the specified array or arrays from the storage unit. The showarray command generates a report that displays the detailed properties of a specific array.
lsarray
The lsarray command displays a list of arrays in a storage image and status information for each array in the list.
lsarray -dev storage_image_ID -s -l -state assigned unassigned unavailable
-data
normal degraded readonly failed repairing inaccessible
-raidtype
5 10
-dapair
dapair_ID
-cap
capacity
-rank
rank_ID
array_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes the manufacturer, type, and serial number. This parameter is required if the fully qualified array ID is not specified. -s (Optional) Displays the array ID. You cannot use the -l and the -s parameters together.
325
-l
(Optional) Displays the default output data. You cannot use the -l and the -s parameters together.
-state assigned | unassigned | unavailable (Optional) Displays only those arrays that are in the specified state. -data normal | degraded | readonly | failed | repairing | inaccessible (Optional) Displays only those arrays that are in the specified data state. -raidtype 5 | 10 (Optional) Displays only those arrays with the specified RAID type, 5 or 10. -dapair dapair_ID (Optional) Displays only the array that is specified by the device adapter pair ID. A device adapter pair ID is a two-digit decimal number with no leading zeros. -cap capacity (Optional) Displays in gigabytes (GB) only the array with the specified DDM capacity. You can specify up to three digits after the decimal point, for example -cap 144.7. -rank rank_ID (Optional) Displays only the array that is assigned to the specified rank ID. A rank ID is a four-digit decimal number with no leading zeros, prefixed with the letter R. array_ID . . . | (Optional) Displays array information for the specified arrays. An array ID is a four-digit decimal number with no leading zeros, prefixed with the letter A. To specify a range of array IDs, separate the array IDs with a hyphen. For example: A10-A12 (equates to A10 A11 A12) You must separate multiple array IDs or ranges of array IDs with a blank space between each ID or range of IDs. For example: A11 A12 A14-A16. Your command in this case could look like:
dscli>lsarray IBM.175068FA120 -l A11 A12 A14-A16
If you specify the dash (-), this parameter information is automatically supplied..
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsarray command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsarray command
dscli>lsarray -dev IBM.210775FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120
326
Array A10 A11 A12 A13
State Assigned Assigned Assigned Unassigned
Data Normal Normal Normal Normal
RaidType 5(6+p) 5(7+p) 5(6+p) 5(7+p)
Arsite S20 S21 S30 S31
Rank R11 R12 R13 -
DA Pair 10 11 20 21
DDMcap (10^9B) 145 145 300 300
Diskclass ENT ENT NL NL
Report field descriptions

Array Specifies the array number. The array number starts with the prefix A, followed by a four-digit decimal number with no leading zeros (for example, A44). State Specifies the relationship between the array and a rank. One of the following values is displayed: Assigned The array is assigned to a rank. Unassigned The array is not assigned to a rank and all of the storage devices that are indicated by the disk serial numbers attribute are in the normal state. Unavailable The array is not assigned to a rank and one or more of the disk drive modules (DDMs) that are indicated by the disk serial numbers attribute are not in the normal state. Data This value reflects the current data status. One of the following values is displayed: Normal The array is in the Normal data state if none of the other data states applies. This status applies if the array is unassigned. Degraded The array is in the Degraded data state if both of the following conditions exist: v The Read-only, Failed, Repairing, or Inaccessible data states do not apply. v One or more redundancy groups are rebuilding (that is, there is a DDM with a rebuilding state in the array). Read Only The array is in the Read-only data state if all of the following conditions exist: v The Failed, Repairing, and Inaccessible data states do not apply. v One or more DDMs have failed.
327
v There are insufficient spares to support all rebuild operations. v Continued write operation without redundancy could result in data loss. Failed The array is in the Failed data state if all of the following conditions exist: v The Repairing and Inaccessible data states do not apply. v Two or more DDMs in the array have failed. v There are insufficient DDMs left in the array to rebuild the data that was lost on the failing storage devices. Repairing The array is in the Repairing data state if all of the following conditions exist: v v v v The The The The Inaccessible data status does not apply. array has previously entered the failed state. repair array function has been accepted. repair array function has not completed.
Inaccessible The array is in the Inaccessible data state if the storage unit cannot access a set of storage devices that are sufficient to access all the data on the array. RaidType Indicates the type of RAID array (5 or 10) and the array configuration (for example, 6+P). arsite Rank Indicates the array sites that are associated with the array. Specifies the rank the array is assigned to. The value is displayed as a combination of a Storage Image ID and a rank number. The rank number is the prefix R, followed by a four-digit decimal number, with no leading zeros (for example, R26).
DA pair Identifies the DA pair ID. DA pairs are located in I/O enclosure pairs. DA pair ID indicates the I/O enclosure location. Note: An even-numbered DA pair ID indicates the first DA pair in an I/O enclosure pair. An odd-numbered DA pair ID indicates the second DA pair in an I/O enclosure pair. DDMcap (10^9 Byte) Indicates the minimum disk capacity (10^9 Byte) of the storage devices (DDMs) in the specified array. Disk class Specifies the disk class as either high speed fibre-channel disk drives or near-line disk drives. The displayed value is one of the following: ENT NL Specifies enterprise and represents high speed fibre-channel disk drives Specifies near-line and represents ATA (FATA) disk drives
328
mkarray
The mkarray command creates one array per command.
mkarray -dev storage_image_ID -raidtype 5 10 -arsite array_site . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified array site. -raidtype 5 | 10 (Required) Specifies a RAID type for the array. -arsite array_site | . . . (Required: 1750 explanation) Specify one or two array sites for IBM 1750 RAID types 5 and 10. If there are two array sites, both must be associated with a common DA pair ID. An array site number is a four-digit decimal number with no leading zeroes, prefixed with the letter S. Separate the two arraysites by commas with no blank space in between. Example: S10,S11.
Example (1750)
Invoking the mkarray command
dscli>mkarray -dev IBM.175068FA120 -raidtype 10 -arsite S10,S11

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.175068FA120 Array A10 successfully created.
rmarray
The rmarray command deletes arrays.
rmarray -dev storage_image_ID -quiet - array_ID . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all array IDs. -quiet (Optional) Turns off the confirmation prompt for this command. array_ID . . . | (Required) Specifies the array IDs that are to be deleted. Accepts a fully qualified array ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four digit decimal number with no leading zeros, prefixed by the letter A.
329
To specify a range of array IDs, separate the array IDs with a hyphen. You must separate multiple array IDs or ranges of array IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmarray command
dscli>rmarray -dev IBM.175075FA120 A44

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.175075FA120 Are you sure you want to delete array IBM.175075FA120/A44? [y/n]: Y Array Storage Image ID/A44 successfully deleted.
showarray
The showarray command displays detailed properties of a specific array.
showarray -dev storage_image_ID array_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the array. array_ID | (Required) Specifies the array ID that you want to view. This parameter accepts a fully qualified array ID, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeros, prefixed by the letter A. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showarray command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showarray command
dscli>showarray -dev IBM.210775FA120 A44

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.210775FA120
330
Array
SN
State Assigned
Datastate Normal
RaidType 5 (6+P)
Arsite S21
IBM.2107AZ123AQ 75FA120/A44
Rank 2107-75FA 123/R26
DA Pair 2107-75FA 123/11
DDMcap (10^9B) 145
DDMRPM 15000
Interface Type FCAL
Interrate (GB/secs) 2
Diskclass ENT

Array Specifies the array ID number. The array ID number starts with the prefix A, followed by a four-digit decimal number with, no leading zeros (for example, A44). SN State Specifies the unique internal identifier for the data space of the designated array (for example, AZ123AQ). Specifies the array state. One of the following values is displayed: Assigned The array is assigned to a rank. Unassigned The array is not assigned to a rank and all of the storage devices that are indicated by the disk serial numbers attribute are in the normal state. Unavailable The array is not assigned to a rank and one or more of the disk drive modules (DDMs) that are indicated by the disk serial numbers attribute are not in the normal state. Datastate Specifies the current data state. One of the following values is displayed: Normal The array is in the Normal data state if none of the other data states applies. This status applies if the array is unassigned. Degraded The array is in the Degraded data state if both of the following conditions exist: v The Read-only, Failed, Repairing, or Inaccessible data states do not apply. v One or more redundancy groups are rebuilding (that is, there is a DDM with a rebuilding state in the array). Read Only The array is in the Read-only data state if all of the following conditions exist: v The Failed, Repairing, and Inaccessible data states do not apply. v One or more DDMs have failed. v There are insufficient spares to support all rebuild operations. v Continued write operation without redundancy could result in data loss.
331
Failed The array is in the Failed data state if all of the following conditions exist: v The Repairing and Inaccessible data states do not apply. v Two or more DDMs in the array have failed. v There are insufficient DDMs left in the array to rebuild the data that was lost on the failing storage devices. Repairing The array is in the Repairing data state if all of the following conditions exist: v The Inaccessible data state does not apply. v The array has previously entered the failed state. v The repair array function has been accepted. v The repair array function has not completed. Inaccessible The array is in the Inaccessible data state if the storage unit cannot access a set of storage devices that are sufficient to access all the data on the array. RaidType Specifies the type of RAID array (5 or 10) and the array configuration (for example, 6+P). Arsite Specifies the array sites that are associated with the array. Rank Specifies the rank that the array is assigned to. The value is displayed as a combination of a storage image ID and a rank number. The rank number is the prefix R, followed by a four-digit decimal number, with no leading zeros (for example, R26). Note: If the array is unassigned, the field is null () DA pair Specifies the DA pair ID. DA pairs are located in I/O enclosure pairs. The DA pair ID indicates the location of the I/O enclosure. Note: DA adapters are installed in slot 3 an enclosure and slot 6 in the peer enclosure. The DA pair ID identifies the enclosure that contains the DA adapter in slot 3. For example, a DA adapter is installed in slot of 3 of enclosure 2. Its peer is installed in slot 6 of enclosure 3. In this case, the DA Pair ID is 2. DDMcap (10^9B) Specifies the minimum disk capacity (10^9B) of the storage devices (DDMs) in the designated array. DDMRPM Specifies the minimum disk rpm of the DDMs in the designated array. Interface Type Specifies the disk interface type of the DDMs in the designated array Interrate Specifies the minimum disk interface rate of the disks in the designated array.
332
Disk class Specifies the disk class as either high speed fibre-channel disk drives or near-line disk drives. The displayed value is one of the following: ENT NL Specifies enterprise and represents high speed fibre-channel disk drives Specifies near-line and represents ATA (FATA) disk drives
Rank specific commands

This section contains commands that are used to create, modify, and delete ranks and to display rank information. Use the following commands to create, modify, and delete ranks and to display rank information: v chrank v lsrank v mkrank v rmrank v showrank The chrank command assigns an unassigned rank to an extent pool or removes an assigned rank from a extent pool. This command can also be used to change an assigned rank to an unassigned rank. The lsrank command generates a report that displays a list of defined ranks in a storage unit and the status information for each rank in the list. The mkrank command creates one fixed block or count key data (CKD) rank from one array. The rmrank command deletes the specified ranks from a storage unit. The showrank command generates two types of reports. One report displays the detailed properties of a specified rank. The other report displays the performance metrics of a specified rank.
chrank
The chrank command assigns an unassigned rank to an extent pool, or removes an assigned rank from a extent pool. This command can also be used to change an assigned rank to an unassigned rank.
chrank -dev storage_image_ID rank_ID -extpool extentpool_ID - . . . -reserve -release -unassign
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all ranks; otherwise, it is optional.
333
Example: IBM.1750-68FA120 -reserve (Optional) Specifies that the rank configuration state be set to Reserved. -release (Optional) Specifies that the rank configuration state be set to Normal. -unassign (Optional) Specifies that the rank configuration state be set to Unassigned. -extpool extentpool_ID (Optional) Assigns the rank to an extent pool. Accepts either a fully qualified extent pool ID including storage image ID or a shortened version if the -dev parameter is used. The shortened version is a four-digit decimal number with no leading zeroes, prefixed with the letter P. rank_ID . . . | (Required) Specifies one or more ranks to be modified. Accepts either a fully qualified rank ID, or a rank number if the -dev parameter is used. A rank number is a four-digit decimal number with no leading zeroes, prefixed by the letter R. To specify a range of rank IDs, separate the rank IDs with a hyphen. You must separate multiple rank IDs or ranges of rank IDs with a blank space between each ID or range of IDs. Example: IBM.1750-68FA120/R2 If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chrank command
dscli>chrank -dev IBM.1750-68FA120 -extpool P101 R2

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Rank IBM.1750-68FA120/R2 successfully modified.
lsrank
The lsrank command displays a list of defined ranks in a storage image and status information for each rank.
lsrank -dev storage_image_ID -s -l -grp 0 1
334
-state
normal configuring unassigned reserved deconfiguring depopulating configerr deconfigerr
-data
normal degraded readonly failed repairing inaccessible
-type
5 10
-extpool
extentpool_ID
-stgtype
fb ckd
rank_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. Example: IBM.1750-68FA120 -s -l (Optional) Displays the rank ID. You cannot use the -l and the -s parameters together. (Optional) Displays the default output, extent pool name, number of extents, and extents that are used for each rank. You cannot use the -l and the -s parameters together.
-grp 0 | 1 (Optional) Displays only the ranks that belong to the specified rank group. A rank in the unassigned state is not associated with a rank group. -state normal | configuring | unassigned | reserved | deconfiguring | depopulating | configerr | deconfigerr (Optional) Displays only ranks in the specified state. -data normal | degraded | readonly | failed | repairing | inaccessible (Optional) Displays only ranks in the specified data state. -type 5 | 10 (Optional) Displays only ranks of the specified RAID type. -extpool extentpool_ID (Optional) Displays only ranks in the specified extent pool. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed with the letter P. -stgtype fb | ckd (Optional) Displays only ranks that are configured for the specified storage type. rank_ID . . . | (Optional) Displays rank information for specified rank IDs. An ID range is defined by two IDs that are separated by a hyphen. You must separate multiple rank IDs or ranges of rank IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
335
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsrank command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsrank command

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 ID IBM.210775FA120/R1 IBM.210775FA120/R2 IBM.210775FA120/R3 IBM.210775FA120/R4 Group 0 0 0 0 State Normal Normal Normal Normal Datastate Normal Normal Normal Normal Array A1 A2 A3 A4 RAIDtype 5 5 5 5
ExtentpoolID P1 P1 P1 P1
Extpoolnam host_1_volumes host_1_volumes host_1_volumes host_1_volumes
Stgtype fb fb fb fb
Exts 1,000 1,000 1,000 1,000
Usedexts 500 500 500 500

ID Specifies the unique identifier assigned to the rank. Group Specifies the rank group that the rank is assigned to. A value of 0, 1, or (null) is displayed. If a rank is unassigned the value displayed is - (null). State Specifies the current configuration state of this rank ID. One of the following values is displayed: Normal Specifies that rank is assigned to an extent pool ID and none of the other state conditions apply. Configuring Specifies that the rank is in the process of being initially configured. Unassigned Specifies that the rank is not assigned to a extent pool ID.
336
Reserved Specifies that the rank extents are not eligible for volume assignment. Deconfiguring Specifies that the rank is in the process of being deleted. Depopulating Specifies that the extents on a rank are not eligible for allocation and the existing allocations are to be moved to another rank in the extent pool using dynamic extent relocation. Configuration Error Specifies that a rank configuration process failed to complete successfully. This state reflects an internal error condition and not an error in the users request to create the rank. To correct this state, you must delete the designated rank configuration. Deconfiguration Error Specifies that a rank removal process has failed to complete successfully. This state reflects an internal error condition and not an error in the request to remove the rank. To correct this state, you must reissue the rmrank command for the designated rank configuration. Datastate Note: A rank is not considered for new extent allocations if it is not in the normal or degraded data state (even if the configuration state is normal). Datastate specifies the current state of the data extents contained by the designated rank ID. One of the following values is displayed: Normal A rank is in the normal data state when the configuration state is one of the following: unassigned, configuring, or configuration error. Degraded A rank is in the degraded data state if one or more arrays in the rank are in the degraded data state and none are in the read only, failed, repairing, or inaccessible data states. Read only A rank is in the read only data state if one or more arrays in the rank are in the read only data state and none are in the failed, repairing, or inaccessible data states. Failed The rank is in the failed data state if one or more arrays in the rank are in the failed data state. Repairing A rank is in the repairing data state if one or more arrays in the rank are in the repairing data state and none are in the failed data state. Inaccessible A rank is in the inaccessible data state if one or more arrays in the rank are in the inaccessible data state and none are in the failed or repairing data states.
337
Array Specifies the array ID that is assigned to the designated rank. RAIDtype Specifies the RAID type of the array associated with this rank. The value displayed is either 5 or 10. ExtentpoolID Specifies the extent pool to which the rank is assigned. Extpoolnam Specifies the name that is assigned to the extent pool to which the rank is assigned. Stgtype Specifies the storage type of the extent pool to which the rank is assigned. The value displayed is either fb (fixed block) or ckd (count key data) Exts Specifies the number of extents that are contained in the designated rank. The value displayed is a number in the range of 1 - 4000.
Usedexts Specifies the number of extents that are allocated to volumes from the designated rank. The value displayed is a number in the range of 1 - 4000.
mkrank
The mkrank command creates one fixed block or count key data (CKD) rank from one array.
mkrank -dev storage_image_ID -array array_ID -stgtype fb ckd
-wait
-extpool
extentpool_ID
Parameters
Note: It is recommended that you specify either the -wait or the -extpool parameter when using the mkrank command. Using either of these parameters allows you to be notified if the rank configuration has failed for any reason. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the extent pool and you do not specify a value for the devid variable in your profile file. -array array_ID (Required) Specifies the ID of the array from which the rank is to be created. An array ID is a four digit decimal number with no leading zeroes, prefixed with the letter A. -stgtype fb | ckd (Required) Specifies the type of extent for which the rank will be configured, either fixed block or count key data. -wait (Optional) Delays the command response until the rank configuration process completes.
338
-extpool extentpool_ID (Optional) Specifies the extent pool that contains the created rank extents. If an extent pool is specified, then the rank will be assigned to the extent pool. Otherwise, the rank state is unassigned. If specified, the extent pool must exist and must be compatible with the specified -stgtype parameter option. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed with the letter P. Note: You must use the chrank command if you choose to specify the extent pool ID at a later time.
Example (1750)
Invoking the mkrank command
dscli>mkrank -dev IBM.1750-68FA120 -array A44 -stgtype fb -wait

rmrank
The rmrank command deletes ranks from a storage image. This command is rejected if any volume extents in the rank are being used. In addition, this command formats the drives (DDMs). Until the formatting is done, the associated array cannot be removed.
rmrank -dev storage_image_ID -quiet - rank_ID . . .
Parameters
Note: The processing time that is associated with this command can be lengthy and might inhibit your use of the array on which this command is being processed. When the rmrank command is issued, the following processing occurs: v The rank is unassigned from the array. v The rank is removed. When this is successful a message is displayed. This piece of the process does not take long; however, the processing that is associated with this command is not complete even though you have received a message that the rank was removed. v The array is formatted. This processing can take some time. During this processing the array cannot be removed or assigned to another rank. Also, until this process is fully completed, the array is listed as assigned to the rank from which it is has been removed. v You can check the progress of the rmrank command by logging onto another session of DS CLI. Issue the lsarray command against the storage unit where the rank or ranks are being deleted. When you no longer see the array that is assigned to the rank from which you removed it, the remove rank process is complete.
339
The following list defines the parameters that are associated with the rmrank command: -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for all ranks; otherwise, it is optional. -quiet (Optional) Turns off the confirmation prompt for this command. rank_ID . . . | (Required) Specifies an array of one or more ranks to be deleted. This parameter accepts a fully qualified rank ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeroes, prefixed with the letter R. To specify a range of rank IDs, separate the rank IDs with a hyphen. You must separate multiple rank IDs or ranges of rank IDs with a space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmrank command
dscli>rmrank -dev IBM.1750-68FA120 R23

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete rank R23? [y/n]: Y Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Rank R23 successfully deleted.
showrank
The showrank command displays detailed properties or performance metrics of a rank.
showrank -dev storage_image_ID -metrics rank_ID
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the rank; otherwise, it is optional. -metrics (Optional) Displays the rank ID and performance statistics for the specified rank.
340
Note: All performance statistics are an accumulation since the most recent counter wrap or counter reset. Rank performance counters are reset on a power up sequence or by a server failover and failback sequence. rank_ID (Required) Specifies the properties for the specified rank. This parameter accepts a fully qualified rank ID, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeros, prefixed by the letter R.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showrank command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showrank command to show rank properties
dscli>showrank -dev IBM.2107-75FA120 R34

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-75FA120 ID 1750 -75FA120 /R34 SN A23567 Group 0 State Normal Datastate Normal Array IBM.1750 -75FA120 /A44 RAIDtype 10
ExtpoolID IBM.1750 -75FA120 /P48
Extpoolnam host_4 _extpool
Volumes IBM.1750 -75FA120 /R7
Stgtype FB
Exts 1,000
Usedexts 500
Widearrays 1
Nararrays 0
Trksize 128
Strpsize 4
Strpesize 4
Extsize 16,384
Report field definitions (-metrics parameter not specified)

ID SN Specifies the unique ID that is assigned by the system to the rank. The ID includes the storage image ID and the rank ID. Specifies the unique serial number that is assigned to the designated rank ID.
Group Specifies the rank group that the rank is assigned to. One of the following values are displayed: 0, 1, - (null). Note: Null (-) is displayed if the rank has not been assigned to an extent pool.
341
State
Specifies the configuration state that is associated with the rank at the time that the report is generated. The following values can be displayed for the rank: Normal Specifies that a rank is assigned to an extent pool ID and none of the other state conditions apply. Configuring Specifies that a rank is in the process of being initially configured. Generally this state indicates that the associated rank transaction has not completed. Unassigned Specifies that a rank is not assigned to an extent pool ID. Reserved Specifies that rank extents are not eligible for volume allocation. Deconfiguring Specifies that a rank is in the process of being deleted. Configuration Error Specifies that a rank configuration process did not complete successfully. This state indicates that there is an internal error condition and it is not an indication that there was a user input error. Deconfiguration Error Specifies that a rank removal process did not complete successfully. This state indicates that there is an internal error condition and it is not an indication that there was a user input error. This configuration state is corrected by reissuing the rmrank command.
Datastate Specifies the current state of the data extents that are contained by this rank ID. The following values can be displayed for the rank: Normal Specifies that none of the other data states apply. Degraded Specifies that one or more arrays in the rank are in the degraded state. Read Only Specifies that one or more arrays in the rank are in the Read Only state. Failed Specifies that one or more arrays in the rank are in the Failed state. Repairing Specifies that one or more arrays in the rank are in the Repairing state. Inaccessible Specifies that one or more arrays in the rank are in the Inaccessible state. Array Specifies the array ID that is assigned to the designated rank. RAIDtype Specifies the RAID type of the array that is associated with the designated rank.
342
ExtpoolID Specifies the extent pool to which the designated rank is assigned. Extpoolnam Specifies the extent pool to which the designated rank is assigned. Volumes Specifies the volume IDs that have an extent pool value that is allocated on the designated rank. Stgtype Specifies the storage type of the extent pool the designated rank is assigned to. Valid values are fixed block and count key data (CKD). Exts Specifies the number of extents that are contained in the designated rank. 1 - 4000 are valid values.
Usedexts Specifies the number of extents that are allocated to volumes from the designated rank. Widearrays Specifies the number of wide arrays that are contained by the designated rank. 0 or 1 are valid values. Nararrays Specifies the number of narrow arrays that are contained by the designated rank. Trksize Specifies the track size. Notes: 1. The track size is displayed as a 1 if it is associated with a CKD storage type. 2. The track size is displayed as 128 if it is associated with a fixed block storage type. Strpsize Specifies the number of logical tracks in a strip on the designated rank. Strpesize Specifies the number of logical tracks in a stripe on the designated rank. Extsize Specifies the number of logical tracks in a extent on the designated rank. Notes: 1. A CKD 1 GB extent contains 16 696 tracks. 2. A fixed block 1 GB extent contains 16 384 tracks. Performance request Invoking the showrank command to show performance metrics
dscli>showrank -dev IBM.2107-75FA120 - metrics R34

343
ID 1750 -75FA120 /R34
Date 10/11/04 02:23:47
Byteread 10000
Bytewrite 10000
Reads 10000
Writes 10000
Timeread 10000
Timewrite 10000
Report field definitions (with the -metrics parameter specified)

ID Date Specifies the unique ID that is assigned by the system to the rank. The ID includes the storage image ID and the rank ID. Specifies the time stamp for the rank performance counters.
Byteread Specifies the number of rank bytes that are read in 128 KB increments. Bytewrite Specifies the number of rank bytes that are written in 128 KB increments. Reads Specifies the rank read operations. Writes Specifies the rank write operations. Timeread Specifies the rank read response time in 16 millisecond increments. Timewrite Specifies the rank read response time in 16 millisecond increments.
Extent pool specific commands

This section contains commands that are used to create, modify, and delete extent pools and to display extent pool information. Use the following commands to create, modify, and delete extent pools and to display extent pool information: v chextpool v lsextpool v mkextpool v rmextpool v showextpool The chextpool command modifies an extent pool. The lsextpool command generates a report that displays a list of the extent pools in a storage unit and the status information on each extent pool in the list. The mkextpool command creates a fixed block or count key data (CKD) storage type extent pool. The rmextpool command deletes one or more specified extent pools from a storage unit.
344
The showextpool command generates two types of reports. One of the reports displays the detailed properties of a specified extent pool. The other report displays the performance metrics for the specified extent pool.
chextpool
The chextpool command modifies an extent pool.
chextpool -dev storage_image_ID -name new_extent_pool_name
-extentlimit
enabled disabled
-limit
extent_limit_percentage
-threshold
extent_threshold_percentage
extentpool_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the extent pool; otherwise, it is optional. -name new_extent_pool_name (Optional) Specifies a new name for the extent pool. Note: To change any other extent pool attributes, you must delete the extent pool and create a new one. -extentlimit enabled | disabled (Optional) Specifies that the extent limit function be enabled or disabled. -limit extent_limit_percentage (Optional) Specifies the maximum value of the percentage of allocated real extents that are allowed in this extent pool. -threshold extent_threshold_percentage (Optional) Specifies threshold as a percentage of the available real extents that is compared to the actual percentage of available real extents. extentpool_ID | (Required) Specifies the ID of the extent pool to be changed. Accepts either a fully qualified extent pool ID or a shortened version if the -dev parameter is used. The shortened version is a four-digit decimal number with no leading zeros, prefixed with the letter P. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chextpool command
dscli>chextpool -name host_4_extpool IBM.1750-68FA120/P21

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Extent Pool IBM.1750-68FA120/P21 successfully modified.
345
lsextpool
The lsextpool command displays a list of extent pools in a storage unit and status information on each extent pool in the list.
lsextpool -dev storage_image_ID -s -l -stgtype fb ckd -rankgrp 0 1
extentpool_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. -s -l (Optional) Displays extent pool IDs. You cannot use the -l and the -s parameters together. (Optional) Displays default output plus additional attributes that are identified as long output. You cannot use the -l and the -s parameters together.
-stgtype fb | ckd (Optional) Displays only extent pools with the specified storage type. -rankgrp 0 | 1 (Optional) Displays only extent pools in the specified rank group. extentpool_ID . . . | (Optional) Displays only the extent pools with the specified IDs. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed by the letter P. To specify a range of extent pool IDs, separate the extent pool IDs with a hyphen. You must separate multiple extent pool IDs or ranges of extent pool IDs with a space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsextpool command using the -l parameter. A separate example is not shown for the 1750 as the information is the same for both the 2107 and 1750. Invoking the lsextpool command
dscli>lsextpool -dev IBM.2107-75FA120 -l
346
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Availstor (2^30B) 1000
Name host_1 _extpool host_1 _extpool host_2 _extpool host_2 _extpool host_3 _extpool host_3 _extpool
ID IBM.210775FA120 /P21 IBM.210775FA120 /P22 IBM.210775FA120 /P23 IBM.210775FA120 /P24 IBM.210775FA120 /P25 IBM.210775FA120 /P26
Stgtype fb
Rankgrp 0
Status exceeded
fb
exceeded
1000
fb
exceeded
1000
fb
exceeded
1000
fb
exceeded
1000
fb
exceeded
1000
%allocated 10 10 10 10 10 10
Available 1000 1000 1000 1000 1000 1000
Reserved 100 100 100 100 100 100
Numvols 4 4 4 4 4 4
Numranks 4 4 4 4 4 4

Name Identifies the name you assigned to the extent pool. ID stgtype Identifies the storage type associated with the extent pool. One of the following is displayed: v fb v ckd rankgrp Specifies the rank group in which the designated extent pool is configured. Status Specifies the extent status. One of the following values is displayed: exceeded Specifies that the %Extents available is greater than the extent threshold Specifies the system assigned unique identifier for the extent pool object.
347
below Specifies that the %Extents Available is less than the extent threshold full Specifies that the %Extents Available is 0. availstor (2^30 Bytes) Specifies the available storage for the designated extent pool, in gigabytes (2 ^ 30 Bytes). %allocated Specifies the percentage of extents allocated. available Specifies the maximum number of extents available for allocation in the designated extent pool. reserved Specifies the extents reserved in the designated extent pool. numvols Identifies the number of logical volumes that have been configured from the designated extent pool. numranks Identifies the number of ranks that have been configured in the designated extent pool.
mkextpool
The mkextpool command creates a fixed block or count key data (CKD) storage type extent pool.
mkextpool -dev storage_image_ID -rankgrp 0 1 -stgtype fb ckd
-extentlimit
enabled disabled
-limit
extent_limit_percentage
extent_pool_name -threshold extent_threshold_percentage
Parameters
Notes: 1. An extent pool object is assigned to either rank group 0 or 1, which allows the extent pool to be managed by storage unit server 0 or 1 respectively. 2. Create extent pool objects before creating array and rank objects. 3. Create extent pools of a given type for both rank groups 0 and 1 so that volumes that are assigned to a volume group can be spread across both rank groups 0 and 1. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number.
348
-rankgrp 0 | 1 (Required) Assigns the extent pool to either rank group 0 or 1. Rank group 0 is managed by server 0, and rank group 1 is managed by server 1. Note: If an extent pool does not exist, you can issue the chrank command after an extent pool is created in order to assign the rank to the extent pool. In addition, you can create extent pools of a given type for both rank groups 0 and 1 so that volumes that are assigned to a volume group might be spread across both rank groups 0 and 1. -stgtype fb | ckd (Required) Specifies the volume storage type that is contained by this extent pool. -extentlimit enabled | disabled (Optional) Specifies that the extent limit function be enabled or disabled. Disabled is the default. -limit extent_limit_percentage (Optional) Specifies the maximum value of the percentage of allocated real extents that are allowed in this extent pool. This value defaults to 100 if not specified. -threshold extent_threshold_percentage (Optional) Specifies threshold as a percentage of the available real extents that is compared to the actual percentage of available real extents. extent_pool_name | (Required) Specifies your extent pool name, which is limited to 16 characters. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkextpool command
dscli>mkextpool -dev IBM.1750-68FA120 -rankgrp 0 -stgtype fb my_extpool

rmextpool
The rmextpool command deletes extent pools from a storage image.
rmextpool -dev storage_image_ID -quiet - extentpool_ID . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This flag is required if you do not specify a fully qualified ID for all extent pools; otherwise, it is optional. -quiet (Optional) Turns off the confirmation prompt for this command.
349
extentpool_ID . . . | (Required) Specifies the IDs of one or more extent pools to be deleted. A fully qualified extent pool ID is accepted, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-decimal digit number with no leading zeroes, prefixed with the letter P. Note: All rank assignments must be removed before extent pool can be deleted. To specify a range of extent pool IDs, separate the extent pool IDs with a hyphen. You must separate multiple extent pool IDs or ranges of extent pool IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmextpool command
dscli>rmextpool IBM.1750-685FA120/P101

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete extent pool IBM.1750-68FA120/P101? [y/n]: Y Extent pool IBM.1750-68FA120/P101 successfully deleted.
showextpool
The showextpool command displays detailed properties or performance metrics of an extent pool.
showextpool -dev storage_image_ID -metrics extentpool_ID -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the extent pool; otherwise, it is optional. -metrics (Optional) Displays the extent pool ID and performance metrics for the specified extent pool. Note: All performance metrics are an accumulation since the most recent counter wrap or counter reset. The extent pool performance counters are reset on the following occurrences: v The storage unit is powered-up. v A server has failed and the failover and failback sequence is performed. extentpool_ID | (Required) Specifies the extent pool to be displayed. Accepts a fully qualified
350
extent pool ID, which consists of the storage image ID, or an extent pool number without the storage image ID if the -dev parameter is specified. The extent pool number is a four-digit decimal number with no leading zeroes, prefixed with the letter P. Even numbered extent pools are associated with rank group 0. Odd numbered extent pools are associated with rank group 1. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showextpool command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showextpool command to show extent pool properties
dscli>showextpool -dev IBM.2107-75FA120 P101

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 totlstor (2^30B) 1000 availstor (2^30B) 800 resvdstor (2^30B) 0
Name host_4 _extpool
ID IBM.210775FA120 /P21
stgtype fb
rankgrp 1
num ranks 4
numvols 3
status exceeded
%allocated 20
%available 80
configured 1000
allowed 600
available 800
allocated 200
reserved 0
%limit 80
%threshold 70
Report field definitions Name Identifies the name you assigned to the extent pool. ID stgtype Identifies the storage type associated with the extent pool. One of the following is displayed: v fb v ckd totlstor (2^30 Bytes) Specifies the amount of storage associated with the extent pool, in gigabytes. availstor (2^30 Bytes) Specifies the available storage for the designated extent pool, in gigabytes.
Specifies the system assigned unique identifier for the extent pool object.
351
resvdstor (2^30 Bytes) Specifies the amount of reserved storage for the designated extent pool, in gigabytes. rankgrp Specifies the rank group in which the designated extent pool is configured. numranks Specifies the number of ranks configured in the designated extent pool. numvols Identifies the number of logical volumes that have been configured from the designated extent pool. status Specifies the extent status. One of the following values is displayed: exceeded Specifies that the %Extents available is greater than the extent threshold below Specifies that the %Extents Available is less than the extent threshold full Specifies that the %Extents Available is zero. %allocated Specifies the percentage of extents allocated. A value of 1 - 100 is displayed. %available Specifies the percentage of extents that are available. A value of 1 - 100 is displayed. configured Specifies the number of extents that are contained in the extent pool. allowed Specifies the number of extents that are below the applicable extent limit. available The number of extents of a given type that are available for allocation to a logical volume. allocated Specifies the number of extents of a given type in the extent pool that are allocated to logical volumes or auxiliary volumes. %limit Specifies the maximum percentage of allocated real extents that are allowed in this extent pool. %threshold Specifies threshold as a percentage of the real extents that are available compared with the actual percentage of real extents that are available. Performance request Invoking the showextpool command to show performance metrics
dscli>showextpool -metrics IBM.2107-75FA120/P101

352
ID IBM.210775FA120 /P101
Date 10/11/04 02:23:47
real extcap 10000
realext 10000
real allocext 10000
real extconv 10000
dyreloc source 10000
dyreloc target 10000
Report field definitions ID Date Specifies the system assigned unique identifier for the extent pool object. Identifies the current time stamp for the extent pool performance counters.
realextcap Specifies the real extent pool capacity in gigabytes. realext Specifies the number of real extents in the extent pool. realallocext Specifies the number of real allocated extents in the extent pool.. realextconv Specifies real extent conversions. dyrelocsource Specifies the number of extents that were sources of a dynamic extent relocation dyreloctarget Specifies the number of extents that were targets of a dynamic extent relocation
Address group specific commands

This section contains commands that are used to display address group information. Use the lsaddressgrp command to display address group information. The lsaddressgrp command generates a report that displays a list of address groups for a storage unit and the status information for each address group in the list.
lsaddressgrp
The lsaddressgrp command displays a list of address groups for a storage image and the status information for each address group in the list.
lsaddressgrp -dev storage_image_ID -s -l -stgtype fb ckd
353
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. Displays only the objects for the storage unit specified. Example: IBM.1750-68FA120 -s -l (Optional). Displays the address group IDs only. You cannot use the -l and the -s parameters together. (Optional). Displays the default output. You cannot use the -l and the -s parameters together.
-stgtype fb | ckd (Optional). Displays only the address groups that are associated with the specified storage type.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lsaddressgrp command using the -l parameter. A separate example is not shown for the 1750 as the information is the same for both the 2107 and 1750. Invoking the lsaddressgrp command
dscli>lsaddressgrp -dev IBM.2107-75FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 ID IBM.2107 -75FA120 /0 IBM.2107 -75FA120 /1 IBM.2107 -75FA120 /2 IBM.2107 -75FA120 /3 Stgtype fb Basevolnum 0000 Vols 4096 LSSs 16 Confgvols 164096
fb
0100
4096
16
164096
ckd
0200
4096
16
164096
ckd
0300
4096
16
164096

ID Stgtype Specifies the type of logical devices that are configured for the specified address group: fb - fixed block and ckd - count key data. Specifies the storage image address group unique identifier. The address number is a single hexadecimal character (0 - 9 or uppercase A - F).
354
Basevolnum Specifies the lowest logical volume number in the address group. Vols LSSs Specifies the number of logical volume numbers that are associated with the address group Specifies the number of logical subsystems (LSSs) that are configured on the address group.
Confgvols Specifies the number of logical volumes that are configured on the address group.
Logical control unit specific commands

This section contains commands that are used to create, modify, and delete logical control units for zSeries systems and to display logical control unit information. Use the following commands to create, modify, and delete logical control units and to display logical control unit information: v chlcu v lslcu v mklcu v rmlcu v showlcu The chlcu command modifies a logical control unit. The lslcu command generates a report that displays a list of logical control units for a storage unit and the status information for each logical control unit in the list. The mklcu command creates a logical control unit in a storage unit. A logical control unit is configured to represent a grouping of logical CKD volumes. The rmlcu command deletes one or more specified logical control units. The showlcu command generates a report that displays the detailed properties for the specified logical control unit.
chlcu
The chlcu command modifies a logical control unit.
chlcu -dev storage_image_ID -ss new_ss_ID -lcutype 3990-3 3990-tpf 3990-6 bs2000
-critmode
enable disable
-pprcconsistgrp
enable disable
-extlongbusy
timeout
LCU_ID -ccsess timeout - . . .
355
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. Example: IBM.1750-68FA120 -ss new_ss_ID (Optional). Specifies your new LCU subsystem ID value (valid range is hexadecimal 0x0001 - 0xFFFF). If this parameter is specified, multiple LCUs are not allowed. The new SSID that you specify replaces the existing SSID value in the initial target LCU ID. Example: F010 -lcutype 3990-3 | 3990-tpf | 3990-6 | bs2000 (Optional). Changes the target LCUs to the new LCU type: 3990-3 TYPE_3990_MODEL_3 3990-tpf TYPE_3990_MODEL_3_for_TPF 3990-6 TYPE_3990_MODEL_6 BS2000 TYPE_BS_2000 -critmode enable | disable (Optional). Specifies that the critical heavy mode setting in the target LCUs be enabled or disabled. Critical heavy mode controls the behavior of the remote mirror and copy (formerly PPRC) pairs that have a primary logical volume on this LCU and are in an LCU consistency group. See the mkpprc command for additional information. You must have administrator privileges to specify this option. -pprcconsistgrp enable | disable (Optional). Specifies that the remote mirror and copy consistency group state setting be enabled or disabled. Any volume that becomes suspended that is associated with the subsystem LSS passes into an extended Long Busy state unless a created consistency group has been received. Otherwise, the volume does not become long busy. -extlongbusy timeout (Optional). Specifies the time in seconds that an LCU consistency group volume stays long busy after reporting an error that causes a remote mirror and copy (formerly PPRC) suspension if a consistency group has not been created. -ccsess timeout (Optional). Specifies the concurrent copy session timeout in seconds setting. This value indicates how long (in seconds) any LCU volume in a concurrent copy session stays long busy before the concurrent copy session is suspended. Example: 500 LCU_ID . . . | (Required). Specifies one or more LCUs that are to be modified by this command. An LCU ID is two hexadecimal characters 00 - 1F. You must separate multiple IDs and multiple ID ranges with a space. Accepts a fully qualified LCU ID or a shortened version, if the -dev parameter is specified.
356
To specify a range of LCU IDs, separate the IDs with a hyphen (-). If you have specified a new subsystem ID value with the -ss parameter, only one LCU ID can be specified. If you specify the dash (-), this parameter information is automatically supplied. Example: 00-03 08
Example (1750)
Invoking the chlcu command
dscli>chlcu -dev IBM.1750-68FA120 -critmode enable 00-0F

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 LCU 00 successfully modified. LCU 01 successfully modified. ... LCU 0F successfully modified.
lslcu
The lslcu command displays a list of logical control units (LCUs) for a storage image and status information for each logical control unit in the list.
lslcu -dev storage_image_ID -s -l -addrgrp address_group
LCU_ID . . . -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. Displays only the objects for the storage unit that is specified. Example: IBM.1750-68FA120 -s -l (Optional). Use this parameter to display LCU IDs only. You cannot use the -l and the -s parameters together. (Optional). Use this parameter to display the default output. You cannot use the -l and the -s parameters together.
-addrgrp address_group (Optional). Specifies an address group. Only the LCUs that belong to the specified address group are displayed. An address group is a single character in the range of 0 - 9 or A - F. LCU_ID . . . | (Optional). Specifies the ID associated with an LCU. An LCU ID is two hexadecimal characters 00 - 1F (1750 only). To specify a range of LCU IDs, separate the LCU IDs with a hyphen (-).
357
You must separate multiple LCU IDs or ranges of LCU IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied. Example: 00-03 08
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lslcu command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lslcu command
dscli>lslcu -dev IBM.2107-75FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 conbasetype 3990-6
ID IBM.2107 -75FA120 /10 IBM.210775FA120 /11 IBM.210775FA120 /12 IBM.210775FA120 /13
Group 0
addrgrp 0
confgvols 256
subsys 8010
256
8011
3990-6
256
8012
3990-6
256
8013
3990-6

ID Specifies the LCU ID. This is a unique identifier that is assigned to this logical control unit object. The ID includes the Storage Image ID and the 2-digit LCU ID. Group Specifies the server that is managing the logical control unit group. The server is identified as either 0 or 1. Addrgrp Specifies the address group object of which the logical control unit is a member.
358
Confgvols Specifies the number of volumes, or logical devices assigned to the LCU ID. This number includes base CKD volumes and alias CKD volumes. Subsys Specifies the value you assigned, or the default SSID value. Conbasetype Specifies the LCU type. The allowable values include the following LCU types: v 3390-3 v 3390-tpf v 3390-6 (this is the default value if no value is assigned) v bs2000
mklcu
The mklcu command creates a logical control unit (LCU) in a storage image.
mklcu -dev storage_image_ID -qty quantity -id lcu_ID -ss ss_ID
-lcutype
3990-3 3990-tpf 3990-6 bs2000
-critmode
-pprcconsistgrp
-extlongbusy
timeout
-ccsess
timeout
Parameters
Notes: 1. A logical control unit is configured to represent a grouping of logical CKD volumes. 2. Multiple sequential LCU IDs can be created with a single request, but all logical control units must be of the same type and specify the same options. 3. (1750 only) The DS6000 has a 16 384 volume address space that is partitioned into 64 logical subsystem (LSS) units, where each LSS contains 256 logical volume numbers. (1750 only) The 64 LSS units are assigned to one of 4 address groups, where each address group contains 16 LSSs, or 4096 volume addresses. All of the LSSs in one address group must be of the same type (CKD or fixed block). 4. LCUs are typically created in groups of 16, beginning at LSS address Xx0. -dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. Example: IBM.1750-68FA120 -qty quantity (Required). Specifies the number of LCU IDs to be created. The valid range is 1 - (1750 only) 64.
359
This command is rejected if any of the LCU IDs which are based on the initial LCU ID and the quantity, are currently defined or are outside the range of supported LCU IDs. The valid LCU ID range is (1750 only) 00 - 1F. Example: 16 -id lcu_ID (Required). Specifies the LCU ID to be created, or the first LCU ID in a sequence of LCU IDs to be created. A LCU ID is two hexadecimal characters (1750 only) 00 - 1F. Example: 00 -ss ss_ID (Required). Specifies the subsystem ID that you have assigned. A subsystem ID is four hexadecimal characters 0x0001 - 0xFFFF. If multiple LCU IDs are being created, then the SSID value increments for each additional LCU ID that is created. If 16 LCUs are created, starting with SSID 0x10, then the SSID values are 0x0010 0x001F. Example: 0010 -lcutype 3990-3 | 3990-tpf | 3990-6 | bs2000 (Optional). Specifies that one of the following types of LCU be created: 3990-3 type 3990 model 3 3990-tp type 3990 model 3 for tpf 3990-6 type 3990 model 6 bs2000 type bs 2000 -critmode (Optional). Specifies that critical heavy mode be enabled. Critical Heavy mode controls the behavior of the remote copy and mirror pairs that have a primary logical volume on this LCU. The default value is disable. You must have administrator privileges to specify this option. See the mkpprc command for additional notes about the use of this parameter. -pprcconsistgrp (Optional). Specifies a remote mirror and copy consistency group state setting. Any volume that becomes suspended that is associated with the subsystem LSS passes into an extended Long Busy state unless the consistency group that was created previously has been received. Otherwise, the volume does not become long busy. -extlongbusy timeout (Optional). Specifies the time in seconds that an LCU consistency group volume stays long busy after reporting an error that causes a remote mirror and copy suspension if a consistency group has not been created. Default value is 120 seconds. -ccsess timeout (Optional). Specifies the concurrent copy cession timeout parameter as the time in seconds that any LCU volume in a concurrent copy session stays long busy before suspending a concurrent copy session. The valid timeout range is 1 - 9999 seconds. Default value is 300 seconds.
360
Example: 500
Example (1750)
Invoking the mklcu command
dscli>dscli>mklcu -dev IBM.1750-68FA120 -qty 16 -id 00 -ss FF00

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 LCU 00 successfully created. LCU 01 successfully created. ... LCU 0F successfully created.
rmlcu
The rmlcu command deletes existing logical control units.
rmlcu -dev storage_image_ID -quiet - LCU_ID . . .
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all logical control units. Example: IBM.1750-68FA120 -quiet (Optional). Turns off the confirmation prompt for this command. LCU_ID . . . | (Required). An array of one or more LCUs to be removed. This parameter accepts a fully qualified LCU ID or a shortened version, if the -dev parameter is specified. A LCU ID is two hexadecimal characters in the range 00 - 1F (1750 only). To specify a range of LCU IDs, separate the LCU IDs with a hyphen (-). You must separate multiple LCU IDs or ranges of LCU IDs with a blank space between each ID or range of IDs. Example: 00-03 08 If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmlcu command
dscli>rmlcu -dev IBM.1750-68FA120 00-0F

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete LCU 00 ? y/n Y LCU 00 successfully deleted.
361
Are LCU ... Are LCU
you sure you want to delete LCU 01 ? y/n Y 01 successfully deleted. you sure you want to delete LCU 0F ? y/n Y 0F successfully deleted.
showlcu
The showlcu command displays the detailed properties of an individual logical control unit (LCU).
showlcu -dev storage_image_ID LCU_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical control unit. Example: IBM.1750-68FA120 LCU_ID | (Required). Displays the properties for the specified logical control unit. The LCU ID is a 2-digit hexadecimal number in the range of (1750 only) 00 - 1F. Accepts a fully qualified LCU ID, which consists of the storage image ID or a shortened version without the storage image ID, if the -dev parameter is specified. If you specify the dash (-), this parameter information is automatically supplied. Example: IBM.1750-68FA120/10
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showlcu command. A separate example is not shown for the 1750. However, there is one difference between what is displayed on the output report for a 2107 versus a 1750. The 2107 displays a value for xrcsesstimout (XRC session timeout), which is not supported on the 1750. Invoking the showlcu command
dscli>showlcu -dev IBM.2107-75FA120 10

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Conbasetype 3990-6
ID IBM.210775FA120 /10
Group 0
Addrgrp 1
Confgvols 256
Subsys 0010
362
pprcconsistgrp Disabled
xtndlbztimeout (secs) 120
ccsesstimout (secs) 300
xrcsesstimout (secs) (1750 only) Not supported
crithvmode Disabled

ID Specifies the unique identifier that is assigned to this logical control unit object. It includes the storage image ID and the 2-digit LCU ID 1750 only (00 - 1F)
Group Specifies the server that manages the logical control unit group. The displayed values are 0 or 1. Addrgrp Specifies the address group object that the logical control unit is a member of. Confgvols Specifies the number of volumes or the logical devices that are assigned to this LCU ID. This number includes base count key data (ckd) volumes and alias ckd volumes. Subsys Specifies the subsystem ID that you assigned to this logical control unit. The range of values that you selected from is 0001 - FFFF. Conbasetype Specifies the LCU type that you designated for the logical control unit. If you did not designate a type, the default value of 3990-6 is assigned and displayed. Pprcconsistgrp Specifies the assigned PPRC consistency group state setting. If you do not designate enabled, the default value of disabled is assigned. Xtndlbztimout (secs) Specifies the assigned extended long busy timeout value. If you do not designate a value, the default value of 210 seconds is assigned and displayed. Ccsesstimout (secs) Specifies the assigned concurrent copy session timeout value. If you do not designate a value, the default value of 300 seconds is assigned and displayed. Crithvmode Specifies whether the critical heavy mode for Remote Mirror and Copy operations is in effect. If you do not designate a value, the default value of Disabled is assigned and displayed.
CKD logical volume specific commands

This section contains commands that are used to create, modify, and delete count key data (CKD) logical volumes for zSeries systems and to display logical volume information.
363
Use the following commands to create, modify, and delete count key data logical volumes and to display logical volume information: v chckdvol v lsckdvol v v v v mkaliasvol mkckdvol rmckdvol showckdvol
The chckdvol command modifies the nickname that you assigned to the count key data (CKD) base volume. The lsckdvol command generates a report that displays a list of count key data (CKD) base and alias volumes in a storage unit and the status information for each volume in the list. The mkaliasvol command creates zSeries CKD alias volumes (generally referred to as parallel access volumes or PAVs) in a storage unit. The mkckdvol command creates zSeries count key data (CKD) base CKD volumes in a storage image. The rmckdvol command deletes one or more specified count key data (CKD) base or alias volumes from a storage unit. The showckdvol command generates two reports. One report displays the detailed properties of a specified count key data volume. The other report displays the performance metrics for specified count key data volume.
chckdvol
The chckdvol command changes the name of a count key data (CKD) base volume.
chckdvol -dev storage_image_ID - -name new_volume_name volume_ID . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified volume_ID. -name new_volume_name (Required) User specified nickname for this CKD base volume. This nickname should not exceed 16 characters. It can contain one of the following wild cards: v (#d) - insert volume_ID (decimal format) v (#h) - insert volume_ID (hexadecimal format) volume_ID . . . | (Required) An array of one or more CKD base volume IDs or volume ID ranges to modify.
364
A volume ID range is defined by two volume IDs that are separated by a dash. Multiple volume IDs or volume ID ranges must be separated with a blank space between each ID. Example: 0100-010F 0180-018F 0120 The volume ID format is hexadecimal LLVV, where LL is a logical control unit number (1750 only) 00 - 1F, and VV is a volume number (00 - FF) that is contained by a logical subsystem object. You must fully qualify the volume ID with manufacturer, type, and serial number if you do not use the -dev parameter. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chckdvol command
dscli>chckdvol -dev IBM.1750-68FA120 -name my_volume_#d 0100

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 CKD volume 0100 successfully modified.
lsckdvol
The lsckdvol command displays a list of count key data (CKD) base and alias volumes in a storage image and status information for each volume in the list.
lsckdvol -dev storage_image_ID -s -l -datatype 3380 3390
-extpool
extentpool_ID
-access
online fenced
-data
normal not_normal
-config
normal not_normal
-lcu
lcu_ID
-voltype
base alias
volume_ID . . . -
Parameters
Note: For a storage unit that is heavily configured, it is recommended that you include the -lcu parameter as part of your command. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. -s (Optional) Displays volume IDs. You cannot use the -l and the -s parameters together.
365
-l
(Optional) Displays default output plus additional attributes that are identified as long output. You cannot use the -l and the -s parameters together.
-datatype 3380 | 3390 (Optional) Displays only volumes of the specified volume data type. -extpool extentpool_ ID (Optional) Display only volumes that are associated with the specified extent pool. -access online | fenced (Optional) Displays only volumes with the specified access state. -data normal | not_normal (Optional) Displays only volumes with the specified data state. -config normal | not_normal (Optional) Displays volumes with the specified configuration state. -lcu lcu_ID (Optional) Displays only volumes with IDs that contain the specified logical control unit ID. Each logical control unit can contain up to 256 volumes. A logical control unit ID is two hexadecimal characters 00 - 1F (for 1750). Note: If you are doing a query on a fully configured storage unit, it is recommended that you specify a specific LCU. If you do not specify a specific LCU, the entire storage unit is queried which results in a longer processing time. -voltype base | alias Specifies the type of CKD volumes you want displayed. volume_ID . . . | (Optional) Displays volumes with the specified IDs. A volume ID is four hexadecimal characters in the range 0000 - 1FFF (for 1750). To specify a range of volume IDs, separate the volume IDs with a dash (-). You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. Example: 0100-010F 0180-018F 0120 If you specify a dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsckdvol command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. The following example is based on the output results for a volume with 3340 cylinders. Invoking the lsckdvol
dscli>lsckdvol -dev IBM.2107-1300861 -l 1410
366

Date/Time: April 12, 2005 6:06:31 PM JST IBM DS CLI Version: 5.0.3.40 DS: IBM.2107-1300861 acc state Online data state Normal config state Normal device MTM 3390-9 data type 3390
Name My_ volume _1410
ID 1410
Volser A03976
voltype CKD base
orgbvols -
extentpool P2
sam standard
cap (cyl) 3340
cap (2^30B) 2.6
cap (10^9B) 2.8

Name Identifies the nickname that you assigned to the designated volume object. ID Identifies the unique identifier that is assigned to the designated volume object
Accstate (access state) One of the following designations can be displayed: Online Specifies that the logical volume is accessible to a host. Fenced Specifies that the logical volume is in the volume fenced state and is not accessible to the host. - (null) Specifies that the logical volume is designated as a CKD alias volume. Datastate One of the following designations can be displayed: Normal Specifies that none of the other data states apply. The access state is Online. Pinned Specifies that none of the other data states apply and the logical volume has one or more pinned non-retryable tracks. The access state is Online. Read only Specifies that the logical volume is read only because one or more extents on the logical volume are on a rank in the read only data state. The access state is Online. Inaccessible Specifies that one or more extents that are associated with the logical volume are on a rank that is in the inaccessible data state. The access state is fenced. Indeterminate data loss Specifies that the following data states do not apply and that one of the following conditions has occurred:
367
Data states that do not apply: v Rank failed v Rank repairing v Rank repaired v Global inaccessible v Global lost data Conditions - one of the following occurred: v Committed write data was lost before it was destaged and the track identifiers that are associated with the data are unknown. v Data was lost that indicated extents on the logical volume were active FlashCopy targets. The access state is fenced. Rank failed Specifies that one or more extents that are associated with the logical volume are on a rank that is in the failed data state. The access state is fenced. Rank repairing Specifies that one or more extents that are associated with the logical volume are on ranks that are in the repairing data state. The access state is fenced. Rank repaired Specifies that one or more extents that are associated with the logical volume are on ranks that were in the repairing state, but are not in the repairing state now. The access state is fenced. Global inaccessible Specifies that the global metadata that is associated with the logical volume configuration is inaccessible. Some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. Global lost Specifies that global metadata that is associated with the logical volume configuration has been lost. As a result, some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. NVS data inaccessible Specifies that active NVS data is inaccessible for one or more logical volumes of an LSS group. The logical volumes in the LSS group cannot be made accessible. The access state is fenced. - (null) Specifies that the logical volume is designated as a CKD alias. Configstate One of the following configuration states are displayed: Normal Indicates that there are no logical volume configuration operations in progress.
368
Configuring Indicates that the logical volume is in the process of being configured for the first time. Reconfiguring Indicates that the logical volume is in the process of allocating or deallocating extents due to a modification of the requested capacity attribute after initial creation. Migrating Indicates that the logical volume is in the process of performing dynamic volume relocation to a specified extent pool. Deconfiguring Indicates that the logical volume is in the process of being deleted. Configuration error Indicates that the initial configuration did not complete successfully. This state reflects an internal error condition and not an error in the request to create the volume. Corrective action: Use the rmfbvol command to delete each volume listed with the configuration state of configuration error. Reconfiguration error Indicates that the reconfiguration request did not complete successfully. Migration error Indicates that the dynamic volume relocation operation was ended during processing. Deconfiguration error Indicates that a request to delete a volume did not complete successfully. This state reflects an internal error condition and not an error in the request to remove the volume. To correct this state, you must reissue the rmfbvol command for the designated volume. deviceMTM One of the following is displayed: v 3380-2 v 3380-3 v 3390-3 v 3390-9 Volume MTM is determined by the CKD base volume data type and volume capacity (in cylinders). Volser Specifies the base CKD volume serial number written by the user at track address 0x0000, record 3. Datatype Identifies the volume data type setting. Voltype Specifies that the logical volume is one of the following: v CKD base v CKD alias Orgbvols (original base vol) One of the following will be specified:
369
v Identifies the original base CKD volume ID to which this CKD alias volume is assigned. v For a CKD Alias type volume, the base and alias volume IDs are of a common LCU ID. v - (null) is displayed for a CKD base volume type. Extpool Identifies the extent pool ID. Volume extents are allocated from this extent pool ID. SAM (Standard Allocation Method) Specifies the space efficient implementation. The current designation is Standard. Cap (cyl) Specifies the quantity of volume CKD cylinders that are available for host system access. Cap (230B) Specifies the size of volume that is available for host system access in 230B (binary GB) unit. Cap (109B) Specifies the size of volume that is available for host system access in 109B (decimal GB) unit.
mkckdvol
The mkckdvol command creates zSeries count key data (CKD) base or CKD alias volumes in a storage image.
mkckdvol -dev storage_image_ID -extpool extentpool_ID -base volume_ID -3380 -cap capacity -name volume_name -wait - . . . volume_ID
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. -extpool extentpool_ID (Optional) Creates the base or alias volumes from data extents that are contained in this extent pool. The extent pool storage type defines the volume storage type. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed with the letter P. Note: This parameter is not required and ignored if the -base parameter is specified. -base volume_ID (Optional) Specifies an existing base CKD volume ID. The volume ID format is four hexadecimal characters LLVV, where LL is a logical control unit number 00 - 1F (1750 only), and VV is a volume number (00 - FF).
370
Use the -base parameter to create one or more CKD alias volumes that are assigned to the specified base CKD volume ID. The LCU ID component for all volume IDs must be identical. Note: It is recommended that you use the -mkaliasvol command to create alias volumes. -3380 (Optional) Specifies the 3380 volume type setting. Otherwise, the 3390 volume type is created. The -3380 parameter is ignored when the -base parameter is specified. Note: You must ensure that the volume data type is compatible with the host systems that access this volume. -cap capacity (Optional) Specifies the quantity of CKD cylinders that are allocated to this volume. The -cap parameter is ignored when the -base parameter is specified. For a 3380 specification, the -cap parameter value is 2226 (1.59 GB) or 3339 (2.37 GB). For 3390 volumes (default type), the -cap parameter can be a value in the range of 1 to 65 520 (849KB to 55.68 GB). Note: This parameter is not required, and it is ignored if the -base parameter is specified. -name volume_name (Optional) Specifies your nickname for the CKD base volumes that are created by this command. Your volume name cannot exceed 16 characters. It can contain one of the following wild cards: v (#d) insert volume ID (decimal) v (#h) insert volume ID (hexadecimal) Note: The -name parameter is ignored when the -base parameter is specified. -wait (Optional) Specifies that the command response be delayed until the volume configuration processes complete. volume_ID . . . | (Required) Specifies an array of one or more CKD base or alias volume IDs or volume ID ranges to be created. The volume IDs must share a common logical control unit ID. Note: Volumes are automatically assigned to the FICON/ESCON ALL volume group ID 10. The volume ID format is hexadecimal LLVV where LL is a logical control unit number 00 - 1F (1750 only), and VV is a volume number (00 - FF). A volume ID range is defined by two volume IDs that are separated by a dash. You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. Note: Multiple volumes can be created with a single request, but all volumes must have the same capacity, extent pool, and data type.
371
Example: 0100-010F 0180-018F 0120 If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkckdvol command
dscli>mkckdvol -dev IBM.1750-68FA120 -extpool P1 -name my_volume_#d -cap 3339 0100 0101 0102 0103

Sun Aug 11 02:23:49 PST 2004 IBM DS IBM.1750-68FA120 CKD CKD CKD CKD volume volume volume volume 0100 0101 0102 0103 successfully successfully successfully successfully created. created. created. created.
rmckdvol
The rmckdvol command deletes count key data (CKD) base or alias volumes from a storage image.
rmckdvol -dev storage_image_ID -quiet - volume_ID . . .
Parameters
A specific use of this command is made when you are confronted with a volume or volumes that are in a configuration state of configuration error. To correct this configuration state, issue the rmckdvol command for each affected volume. You can specify a volume range according to the command specifications when it is appropriate. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all logical volumes. -quiet (Optional) Turns off the confirmation prompt for this command. volume_ID . . . | (Required) An array of one or more CKD base or CKD alias volume IDs or volume ID ranges to be removed. Accepts a fully qualified volume ID, which includes the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. The shortened volume ID format is hexadecimal LLVV where LL is a logical control unit (LCU) number 00 - 1F (1750 only), and VV is a volume number (00 - FF) that is contained by a logical control unit (logical subsystem). Note: A CKD base volume cannot be removed if an alias volume is associated with it. A volume ID range is defined by two volume IDs that are separated by a dash.
372
You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. (1750) Example: 0100-010F 0180-1FFF 0120 If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmckdvol command
dscli>rmckdvol -dev IBM.1750-68FA120 0000 0001

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to Volume 0000 successfully Are you sure you want to Volume 0001 successfully delete Volume 0000? y/n Y deleted. delete Volume 0001? y/n Y deleted.
mkaliasvol
The mkaliasvol command creates zSeries CKD alias volumes (generally referred to as parallel access volumes or PAVs) in a storage image.
mkaliasvol -dev storage_image_ID -base volume_ID (volume_ID_range) volume_ID -
-order increment |
decrement
-qty
quantity
-wait
Parameters
Note: Volumes are automatically assigned to the FICON/ESCON ALL volume group ID 10. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. -base volume_ID (volume_ID_range) (Required) Specifies an existing base CKD volume ID or a volume ID range. Note: You cannot use multiple volume IDs separated by commas and multiple ID ranges in combination. This combination is rejected. Use the -base parameter to create one or more CKD alias volumes that are assigned to the specified base CKD volume ID. The LCU ID component for all volume IDs must be identical. The alias volume IDs are assigned consecutively in the order specified by the -order parameter. The following examples show the processing affects of the -order parameter:
dscli>mkaliasvol -base 0000 -order increment -qty 2 0080 creates two alias volumes 0080 and 0081 for base volume 0000.
373
dscli>mkaliasvol -base 0000-003F -order increment -qty 2 0080 creates two alias volumes for each base volume as follows: 0080,0081 for base volume 0000 0082,0083 for base volume 0001 ... 00FE,00FF for base volume 003F
-order increment | decrement (Optional) Specifies the order in which alias volume IDs are assigned. For example:
dscli>mkaliasvol -base 0000-003F -order decrement -qty 2 00FF creates two alias volumes for each base volume as follows: 00FF,00FE for base volume 0000 00FD,00FC for base volume 0001 ... 0081,0080 for base volume 003F
Note: If the -order parameter is not specified the default value is decrement. -qty quantity (Optional) Specifies the number of alias volumes that will be assigned to each specified CKD base volume. -wait (Optional) Delays the command response until the volume configuration processes complete. volume_ID (Required) Identifies the starting alias volume ID in a sequence of volume IDs to be created The volume ID format is hexadecimal LLVV where LL is a logical control unit number 00 - 1F (1750 only), and VV is a volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkaliasvol command
dscli> mkaliasvol dev IBM.1750-68FA120 base 0100-010F -order decrement -qty 2 01FF

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 CKD Volume 01FF successfully created. CKD Volume 01FE successfully created. ... CKD Volume 01E1 successfully created. CKD Volume 01E0 successfully created.
showckdvol
The showckdvol command displays detailed properties of an individual count key data volume. This command can also be used to display the performance metrics for an individual volume ID.
showckdvol -dev storage_image_ID -rank -metrics
374
-volgrp
volume_group_ID
volume_ID -
Parameters
Note: All performance counts are an accumulation from the most recent counter wrap or counter reset. A reset of the volume performance counters occurs in association with the following events: v The storage unit is turned on. v There has been a server failure and the server failover or failback sequence has been initiated. -dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical volume. -rank (Optional) Specifies that a rank extents table be displayed. This table displays the set of ranks that the logical volume has extents configured on and the number of extents for that logical volume. Note: This parameter cannot be used with the -metrics or -volgrp parameters. -metrics (Optional) Displays the volume ID and performance metrics for the specified volume. Note: v All performance counts are an accumulation since the most recent counter wrap or counter reset. Volume performance counters are reset on a power-up sequence. Volume performance counters are reset by a server failover and failback sequence. v Do not use this parameter with the -rank or -volgrp parameters. -volgrp volume_group_ID (Required if you do not specify the volume_ID parameter.) Specifies that the CKD volumes that are associated with the designated volume group ID be displayed. There is only one volume group for CKD volumes and it contains all volumes. Notes: 1. The -volgrp parameter can only be used when you are doing a query for performance metrics. 2. Do not use the -volgrp parameter with the volume_ID parameter. 3. Do not use the -volgrp parameter with the -rank or -metrics parameters. volume_ID | (Required when you do not specify the -volgrp parameter.) Displays information for the specified volume. This parameter accepts a fully qualified volume ID, which consists of the storage_image_ID or a shortened version without the storage_image_ID, if you specify the -dev parameter. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF).
375
If you specify the dash (-), this parameter information is automatically supplied. Note: Do not use the volume_ID parameter with the -volgrp parameter.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showckdvol command using the -rank parameter. When the rank parameter is specified, a rank extents table is also displayed. It appears at the end of the regular report. A separate example is not shown for the 1750 because the information is the same for both machine types. The only difference is the machine type designations 2107 versus 1750. Invoking the showckdvol to show volume properties Note: The following example is based on the use of the showckdvol command for a 3390 volume with 3339 cylinders.
dscli>showckdvol -dev IBM.2107-1300861 -rank 1410

Date/Time: April 13, 2005 3:44:27 PM JST IBM DS CLI Version: 5.0.3.40 DS: IBM.2107-1300861 acc state Online data state Normal config state Normal device MTM 3390-3 data type 3390
Name My_ volume_ 1410
ID 1410
Volser A03967
voltype CKD Base
orgbvols
addrgrp 1
extpool P2
exts 3
cap (cyl) 3339
cap (2^30B) 2.6
cap (10^9B) 2.8
Ranks 3
Rank R0 R2
Extents 1 2
Report field definitions ( -metrics parameter not specified)

Name Specifies the nickname that you assigned for this volume object. ID Specifies the unique identifier that is assigned to this volume object. Accstate One of the following designations can be displayed:
376
Online Specifies that the logical volume is accessible to a host. Fenced Specifies that the logical volume is in the volume fenced state and is not accessible to the host. - (null) Specifies that the logical volume is designated as a CKD alias volume. Datastate One of the following designations can be displayed: Normal Specifies that none of the other data states apply. The access state is Online. Pinned Specifies that none of the other data states apply and the logical volume has one or more pinned non-retryable tracks. The access state is Online. Read only Specifies that the logical volume is read only because one or more extents on the logical volume are on a rank in the read only data state. The access state is Online. Inaccessible Specifies that one or more extents that are associated with the logical volume are on a rank that is in the inaccessible data state. The access state is fenced. Indeterminate data loss Specifies that the following data states do not apply and that one of the following conditions has occurred: Data states that do not apply: v Rank failed v Rank repairing v Rank repaired v Global inaccessible v Global lost data Conditions - one of the following occurred: v Committed write data was lost before it was destaged and the track identifiers that are associated with the data are unknown. v Data was lost that indicated extents on the logical volume were active FlashCopy targets. The access state is fenced. Rank failed Specifies that one or more extents that are associated with the logical volume are on a rank that is in the failed data state. The access state is Fenced. Rank repairing Specifies that one or more extents that are associated with the logical volume are on ranks that are in the repairing data state. The access state is fenced.
377
Rank repaired Specifies that one or more extents that are associated with the logical volume are on ranks that were in the repairing state, but are not in the repairing state now. The access state is Fenced. Global inaccessible Specifies that the global metadata that is associated with the logical volume configuration is inaccessible. Some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. Global lost data Specifies that global metadata that is associated with the logical volume configuration has been lost. As a result, some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. NVS data inaccessible Specifies that active NVS data is inaccessible for one or more logical volumes of an LSS group. The logical volumes in the LSS group cannot be made accessible. The access state is fenced. (null) Specifies that the logical volume is designated as a CKD alias. Configstate One of the following designations can be displayed: Normal Indicates that there are no logical volume configuration operations in progress. Configuring Indicates that the logical volume is in the process of being configured for the first time. Reconfiguring Indicates that the logical volume is in the process of allocating or deallocating extents due to a modification of the requested capacity attribute after initial creation. Migrating Indicates that the logical volume is in the process of performing dynamic volume relocation to a specified extent pool. Deconfiguring Indicates that the logical volume is in the process of being deleted. Configuration error Indicates that the initial configuration did not complete successfully. This state reflects an internal error condition and not an error in the request to create the volume. Corrective action: Use the rmfbvol command to delete each volume listed with the configuration state of configuration error. Reconfiguration error Indicates that the reconfiguration request did not complete successfully. Migration error Indicates that the dynamic volume relocation operation was ended during processing. Deconfiguration error Indicates that a request to delete a volume did not complete successfully.
378
This state reflects an internal error condition and not an error in the request to remove the volume. To correct this state, you must reissue the rmfbvol command for the designated volume. deviceMTM One of the following will be displayed: v 3380-2 v 3380-3 v 3390-3 v 3390-9 Volser Specifies the volume serial number. A volume serial number is six bytes of data, displayed as six characters. Datatype Specifies the volume data type setting (3380 or 3390). Voltype Specifies that the logical volume is one of the following: v CKD base v CKD alias Orgbvols(original base vol) One of the following will be specified: v Identifies the original base CKD volume ID to which this CKD alias volume is assigned. v For a CKD Alias type volume, the base and alias volume IDs share a common LCU ID. v - (null) is displayed for a CKD base volume type. Addrgrp Specifies the address group that contains this volume object. An address group ID is one hexadecimal character (0 - F). Extpool Specifies the extent pool ID. Exts Specifies the number of extents used by the designated volume ID. Cap (cyl) Specifies the quantity of volume cylinders that are available for host system access. Cap (2^30B) Specifies the size of volume that is available for host system access in (2^30B binary GB) units. Cap (10^9B) Specifies the size of volume that is available for host system access in (10^9B decimal GB) units. Ranks Specifies the number of ranks the volume resides on. Rank (Rank Extent table) Specifies the rank ID. Extents (Rank Extents table) Specifies the number of extents for the volume on the rank.
379
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showckdvol command using the -metrics parameter. Invoking the showckdvol to show performance metrics
dscli>showckdvol -metrics IBM.2107-75FA120/0101

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 norm write req 10000 norm write hits 10000 seq read reqs 10000 seq read hits 10000 seq write req 10000
ID
Date
norm rdrqts 10000
norm rdhits 10000
10/11 /04 IBM. 02:23:49 210775FA120 /0101
seqwrite- cachfwrhits reqs 10000 10000
cachfwrhits 10000
cachfwreqs 10000
cachfwhits 10000
inbcachload 10000
bypasscach 10000
seq DASD trans 10000
DASDtrans 10000
cachetrans 10000
NVSspadel 10000
norm write ops 10000
rec seqwrite- cache ops mis 10000 10000
qwriteprots 10000
CKDirtrkac 10000
CKD irtrk hits 10000
cachspdelay 10000
timelowifact 10000
phread 10000
phwrite 10000
phwrite 10000
phbyteread 10000
phbytewrit 10000
recmoreads 10000
sfile trk reads 10000
contamwrts 10000
PPRCtrks 10000
NVSspallo 10000
timephread 10000
timephwrite 10000
byteread 10000
bytewrit 10000
timeread 10000
timewrite 10000
Report field definitions ( -metrics parameter specified)

ID Specifies the unique identifier that is assigned to this volume object.
380
Date Specifies the current time stamp for the volume performance counters. normrdrqts Specifies the number of normal read operations issued by a host to a volume. normrdhits Specifies the number of normal read operations where data did not move to or from a storage device. normwritereq Specifies Write Normal I/O Requests normwritehits Specifies DASD Fast Write I/O Request Hits seqreadreqs Specifies Search/Read Sequential I/O Requests seqreadhits Specifies Search/Read Sequential I/O Request Hits seqwritereq Specifies Write Sequential I/O Requests seqwritehits Specifies DASD Fast Write Sequential I/O Request Hits cachfwrreqs Specifies Search/Read Cache Fast Write I/O Requests cachfwrhits Specifies Search/Read Cache Fast Write I/O Request Hits cachfwreqs Specifies Cache Fast Write I/O Requests cachfwhits Specifies Cache Fast Write I/O Requests Hits inbcachload Specifies Inhibit Cache Loading I/O Requests that operate with DASD bypasscach Specifies Bypass Cache I/O Requests seqDASDtrans Specifies Sequential DASD to Cache Transfer Operations DASDtrans Specifies DASD to Cache Transfer Operation Count cachetrans Specifies Cache to DASD Transfer Operation Count NVSspadel Specifies DASD Fast Write Operations Delayed Due to nonvolatile storage Space Constraints normwriteops Specifies Normal DASD Fast Write Write Operation Counts seqwriteops Specifies Sequential Access DASD Fast Write Write Operation Counts
381
reccachemis Specifies Number of record cache Read Misses qwriteprots Specifies Quick Write Promotes CKDirtrkac Specifies Irregular Track Accesses CKDirtrkhits Specifies Irregular Track Accesses Hits cachspdelay Specifies Operations Delayed Due To Cache Space Constraints timelowifact Specifies Milliseconds of lower interface I/O activity for the indicated device. phread Specifies Physical Storage Read Operations phwrite Specifies Physical Storage Write Operations phbyteread Specifies Physical Storage Bytes Read in 128 KB increments. phbytewrit Specifies Physical Storage Bytes Written in 128 KB increments. recmoreads Specifies Record Mode Read Operations sfiletrkreads Specifies the Number of tracks read from the Concurrent Copy or XRC Sidefile. contamwrts Specifies the Number of Contaminating writes for a Concurrent Copy or XRC volume PPRCtrks Specifies the Number of tracks or portion of tracks that were transferred to the secondary device of a PPRC pair. NVSspallo Specifies the NVS Space Allocations timephread Specifies the physical storage read response time in 16 ms increments. timephwrite Specifies the physical storage write response time in 16 ms increments. byteread Specifies the number of bytes read in 128 KB increments bytewrit Specifies the number of bytes written in 128 KB increments. timeread Specifies the accumulated response time for all read operations. timewrite Specifies the accumulated response time for all write operations.
382
Logical subsystem specific commands

This section contains commands that are used to modify logical subsystems for Open Systems and to display logical subsystem information. Use the following commands to modify logical subsystems and to display logical subsystem information: v chlss v lslss v showlss The chlss command modifies one or more logical subsystems. The lslss command generates a report that displays a list of logical subsystems (LSSs) for a storage unit and the status information for each logical subsystem in the list. The showlss command generates a report that displays the detailed properties of a specified LSS.
chlss
The chlss command modifies a logical subsystem.
chlss -dev storage_image_ID -pprcconsistgrp enable disable
LSS_ID -extlongbusy timeout - . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all logical subsystems (LSSs); otherwise, it is optional. -pprcconsistgrp enable | disable (Optional) Enables a volume that is associated with a logical subsystem to become suspended and enter an extended long busy state if it has not received a notification that a consistency group has been created. Otherwise, the volumes associated with the LSS do not go to a long-busy state. -extlongbusy timeout (Optional) Specifies the time in seconds that an LCU consistency group volume stays long busy after reporting an error that causes a remote mirror and copy suspension if a consistency group has not been created. LSS_ID . . . | (Required) Specifies one or more LSSs to be modified by this command. An LSS ID is two hexadecimal characters 00 - 1F (1750 only). To specify a range of LSS IDs, separate the IDs with a hyphen. You must separate multiple LSS IDs or ranges of LSS IDs with a blank space between each ID or range of IDs. If you specify a dash (-), this parameter information is automatically supplied.
383
Example: 00-03 08
Example (1750)
Invoking the chlss command
dscli>chlss -dev IBM.1750-68FA120 06 0F

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 LSS 06 successfully modified. LSS 0F successfully modified.
lslss
The lslss command displays a list of logical subsystems (LSSs) for a storage image and status information for each logical subsystem in the list.
lslss -dev storage_image_ID -s -l -addrgrp address_group
LSS_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. -s -l (Optional) Displays LSS IDs. You cannot use the -l and the -s parameters together. (Optional) Displays the default output. You cannot use the -l and the -s parameters together.
-addrgrp address_group (Optional) Displays only LSSs that belong to the specified address group. An address group is a single hexadecimal character (0 - F). LSS_ID . . . | (Optional) Specifies the logical subsystem IDs. An LSS ID is two hexadecimal characters 00 - 1F (1750 only). To specify a range of logical subsystem IDs, separate the logical subsystem IDs with a hyphen. You must separate multiple logical subsystem IDs or ranges of logical subsystem IDs with a blank space between each ID or range of IDs. Example: 00-03 08 If you specify a dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables.
384
The following table represents the headers that are displayed on the output report that is associated with the lslss command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both machine types. The only difference is the machine type designation, 2107 versus 1750. Invoking the lslss command
dscli>lslss -dev IBM.1750-75FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 ID IBM.210775FA120 /10 IBM.210775FA120 /11 IBM.210775FA120 /12 Group 0 Addrgrp 1 Stgtype fb Confgvols 256 Subsys FF10
fb
256
FF11
fb
256
FF12

ID Specifies the unique identifier that is assigned to this logical subsystem object. The identifier includes the storage image ID and a 2-digit hexadecimal number for the LSS ID. The LSS ID can be in the range of 00 1F (1750 only).
Group Specifies the server that is managing the logical subsystem group. The server is identified as either 0 or 1. Addrgrp Specifies the address group object of which the logical subsystem is a member. Stgtype Specifies the type of storage volumes that are contained by this logical subsystem. The displayed value is either fb (fixed block) or ckd (count key data). Confgvols Specifies the number of volumes currently assigned to this logical subsystem. Subsys Specifies the user assigned, or default SSID value.
showlss
The showlss command displays detailed properties of a logical subsystem (LSS).
showlss -dev storage_image_ID LSS_ID -
385
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical subsystem; otherwise, it is optional. LSS_ID | (Required) Displays the properties for the specified logical subsystem. This parameter accepts a fully qualified LSS ID, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is two hexadecimal digits in the range 00 1F (1750 only). The following is an example of a fully qualified LSS ID: IBM.2107-75FA120/10 The following is an example of a shortened version of the LSS ID when the dev parameter is specified:
dscli>showlss -dev IBM.2107-75FA120 10
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showlss command. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the showlss command to show default information
dscli>showlss IBM.2107-75FA120/10

DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Sun Aug 11 02:23:49 PST 2004 IBM ID IBM.210775FA120 /10 Group 0 Addrgrp 1 Stgtype fb Confgvols 256
Pprcconsistgrp Disabled
Xtndlbztimout (secs) 120
Subsys FF10

ID Specifies the unique identifier that is assigned to this logical subsystem. It includes the storage image ID and the 2 digit LSS ID 00 - 1F (1750 only).
Group Specifies the server that manages the logical subsystem. The displayed values are 0 or 1.
386
Addrgrp Specifies the address group object that the logical subsystem is a member of. Confgvols Specifies the number of volumes that are assigned to this logical subsystem. Stgtype Specifies the type of storage volumes contained by this logical subsystem. The value displayed is fb (fixed block) or ckd (count key data) Pprcconsistgrp Specifies the assigned PPRC consistency group state setting. If you do not designate enabled, the default value of disabled is assigned. Xtndlbztimout (secs) Specifies the assigned extended long busy timeout value. If you do not designate a value, the default value of 210 seconds is assigned and displayed. Subsys Specifies the user assigned, or default SSID value.
Fixed block logical volume specific commands

This section contains commands that are used to create, modify, and delete fixed block logical volumes for Open Systems and to display logical volume information. Use the following commands to create, modify, and delete fixed block logical volumes and to display logical volume information: v chfbvol v lsfbvol v mkfbvol v rmfbvol v showfbvol The chfbvol command modifies the name or data type of a fixed block volume. The lsfbvol command generates a report that displays a list of fixed block volumes in a storage unit and the status information for each volume in the list. The mkfbvol command creates open systems fixed block volumes in a storage unit. The rmfbvol command deletes one or more specified fixed block volumes from a storage unit. The showfbvol command generates two types of reports. The first report displays the detailed properties for a specified fixed block volume. The second report displays the performance metrics for a specified fixed block volume.
chfbvol
The chfbvol command changes the name or data type of a fixed block volume.
chfbvol -dev storage_image_ID -os400 protected unprotected
387
volume_ID -name new_volume_name - . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified volume ID. -os400 protected | unprotected (Optional) Specifies options for the OS 400 volume data types. If the current volume data type is os400-protected(FB 520P) or os400-unprotected(FB 520U) then this data type can be modified to either os400-unprotected(FB 520U) or os400-protected(FB520P) respectively. If the current volume data type is 512, then this setting cannot be modified. -name new_volume_name (Optional) Specifies your nickname for this volume. A nickname cannot exceed 16 characters. volume_ID . . . | (Required) Specifies one or more volume IDs to be modified. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). You must fully qualify the volume ID with manufacturer, type, and serial number if you do not use the -dev parameter. To specify a range of volume IDs, separate the volume IDs with a hyphen. You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. Example: 0100-010F 0180-018F 0120 If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the chfbvol command
dscli>chfbvol -dev IBM.1750-68FA120 -os400 protected 0100 0101

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FB volume 0100 successfully modified. FB volume 0101 successfully modified.
lsfbvol
The lsfbvol command displays a list of fixed block volumes in a storage image and status information for each volume in the list.
lsfbvol -dev storage_image_ID -s -l -datatype 512 520p 520u
388
-extpool
extentpool_ID
-access
online fenced
-data
normal not_normal
-config
normal not_normal
-lss
LSS_ID
-volgrp
volume_group_ID
volume_ID . . . -
Parameters
Note: For a storage unit that is heavily configured, it is recommended that you specify the -lss or the -volgrp parameter as part of your command. -dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, type, and serial number. -s -l (Optional) Displays the volume IDs. You cannot use the -l and the -s parameters together. (Optional) Displays default output plus additional attributes that are identified as long output. You cannot use the -l and the -s parameters together.
-datatype 512 | 520p | 520u (Optional) Displays volumes of the specified volume data type. Standard 2107/1750 volume (512), System i protected (520p), System i unprotected (520u). -extpool extentpool_ID (Optional) Displays volumes that are sourced from the specified extent pool. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed with the letter P. -access online | fenced (Optional) Displays volumes with the specified access state. -data normal | not_normal (Optional) Displays volumes with the specified data state. -config normal | not_normal (Optional) Displays volumes with the specified configuration. -lss LSS_ID (Optional) Displays volumes with IDs that contain the specified logical subsystem ID. Each logical subsystem can contain up to 256 volumes. A logical subsystem ID is two hexadecimal characters 00 - 1F (for 1750). -volgrp volume_group_ID (Optional) Displays volumes that are assigned to the specified volume group ID. A volume group ID is a four-digit decimal number, with no leading zeros, prefixed by the letter V. For example, V123. volume_ID . . . | (Optional) Displays volumes with the specified IDs. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ
389
where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF). To specify a range of volume IDs, separate the volume IDs with a hyphen. You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied. Example: 0100-010F 0180-018F 0120
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsfbvol command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both machine types. The only difference is the machine type designation, 2107 versus 1750. Note: Invoking the lsfbvol command
dscli>lsfbvol -dev IBM.2107-75FA120 -l -volgrp V2

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 config state Normal device MTM 2107-900 data type FB 512
Name My_ volume_ 0001 My_ volume_ 0002 My_ _volume 0003
ID 0100
accstate Online
datastate Normal
0102
Online
Normal
Normal
2107-A07
FB 520P
0103
Online
Normal
Normal
2107-900
FB 512
extpool P21 P31 P21
sam standard standard standard
captype DS iSeries ESS
cap (2^30B) 64.0 128.0 -
cap (10^9B) 68.7 35.0
cap (blocks) 134217728 268435456 68359424
Volgrp V2 V2 -

Name Identifies the nickname that you assigned for the specified volume object. ID Identifies the unique identifier that is assigned to this volume object.
390
Accstate One of the following access states are displayed: Online or Fenced. Online The logical volume is accessible to a host. Fenced The logical volume is in the volume fenced state and is not accessible to the host. Datastate One of the following data states are displayed: Normal Specifies that none of the other data states apply. The access state is Online. Read only Indicates that the logical volume is read only because one or more extents on the logical volume are on a rank in the read only data state. The access state is Online. Inaccessible Indicates that one or more extents that are associated with the logical volume are on a rank that is in the inaccessible data state. The access state is fenced. Indeterminate data loss Specifies that the following data states do not apply and that one of the following conditions has occurred: Data states that do not apply: v Rank failed v Rank repairing v Rank repaired v Global inaccessible v Global lost data Conditions - one of the following occurred: v Committed write data was lost before it was destaged and the track identifiers that are associated with the data are unknown. v Data has been lost that indicates that extents on the logical volume were active FlashCopy targets. The access state is fenced. Rank failed Indicates that one or more extents that are associated with the logical volume are on a rank that is in the Failed data state. The access state is Fenced. This data state transitions to the Rank repairing state if the rank transitions to the Rank repairing state through use of the repair array function. Rank Repairing Indicates that one or more extents that are associated with the logical volume are on ranks in the repairing data state. The access state is fenced. Rank Repaired Indicates that one or more extents that are associated with the logical
391
volume are on ranks that were in the repairing state, but are not in the repairing state now. The access state is fenced. Global inaccessible Specifies that the global metadata that is associated with the logical volume configuration is inaccessible. Some of the data associated with the logical volume might be inaccurate. The access state is fenced. Global lost data Specifies that global metadata that is associated with the logical volume configuration has been lost. As a result, some of the data associated with the logical volume might be inaccurate. The access state is fenced. NVS data inaccessible Specifies that active NVS data is inaccessible for one or more logical volumes of an LSS group. The logical volumes in the LSS group cannot be made accessible. The access state is fenced. Configstate One of the following configuration states are displayed: Normal Indicates that there are no logical volume configuration operations in progress. Configuring Indicates that the logical volume is in the process of being configured for the first time. Reconfiguring Indicates that the logical volume is in the process of allocating or deallocating extents due to a modification of the requested capacity attribute after initial creation. Migrating Indicates that the logical volume is in the process of performing dynamic volume relocation to a specified extent pool. Deconfiguring Indicates that the logical volume is in the process of being deleted. Configuration error Indicates that the initial configuration did not complete successfully. This state reflects an internal error condition and not an error in the request to create the volume. Corrective action: Use the rmfbvol command to delete each volume listed with the configuration state of configuration error. Reconfiguration error Indicates that the reconfiguration request did not complete successfully. Migration error Indicates that the dynamic volume relocation operation was ended during processing. Deconfiguration error Indicates that a request to delete a volume did not complete successfully. This state reflects an internal error condition and not an error in the request to remove the volume. To correct this state, you must reissue the rmfbvol command for the designated volume.
392
deviceMTM Indicates the volume device type and model. The volume MTM (machine type, model) is determined by the fixed block volume data type and the volume capacity (in GB). The machine type is either 2107 or 1750; however, the MTM can be any one of the following depending on your system: 2107-900 Indicates a standard 2107 volume. 1750-500 Indicates a standard 1750 volume. | | | | | | xxxx-A0x Indicates that the xxxx is a 2107 or 1750. The A0 indicates a System i protected volume (for example, 2107-A01 or 1750-A07). xxxx-A8x Indicates that the xxxx is 2107 or 1750. The A8 indicates a System i unprotected volume (for example, 2107-A81 or 1750-A87). Datatype Indicates the volume data type setting. One of the following binary (B) values will be displayed: v FB 512 v FB 520P v FB 520U Extpool Identifies the extent pool ID. Volume extents are allocated from this extent pool ID. SAM (Storage Allocation Method) Specifies the space efficient implementation. The current designation is Standard. Captype Indicates the capacity unit type that is used at volume creation. One of the following values is displayed: ESS The capacity unit is 109B. DS The capacity unit is 230B. DS/ESS The capacity unit is 230B or 109B. Blocks The capacity unit is 512B. iSeries The capacity unit was not specified at volume creation. This fixed block volume was created only for iSeries. Cap (2^30B) Specifies the size of the volume that is available for host system access in 2^30B (binary GB) units. Note: (null) is displayed if the capacity unit type of the volume is ESS (captype=ESS)
393
Cap (10^9B) Specifies the size of the volume that is available for host system access in 10^9B (decimal GB) units. Note: (null) is displayed if the capacity unit type of the volume is DS (captype=DS) Cap (blocks) Indicates the quantity of volume logical blocks that are available for host system access. Volgrp Specifies the volume groups (excluding default volume groups) that a volume belongs to. Multiple volume groups that are associated with the volume are separated by a comma. A null (-) is displayed if there are no volume groups that are associated with the volume.
mkfbvol
The mkfbvol command creates open systems fixed block (FB) volumes in a storage image.
mkfbvol -dev storage_image_ID -extpool extentpool_ID -os400 A01 A81 A02 A82 A04 A84 A05 A85 A06 A86 A07 A87
-type ess ds blocks
-cap
capacity
-name
volume_name
volume_ID -volgrp volume_group_ID -wait - . . .
Parameters
Notes: 1. You can create multiple volumes with one command; however, all volumes must have the same capacity, extent pool, and data type. 2. If host attachment volume groups have not yet been created, create temporary volume groups and assign new fixed block volumes to the temporary volume groups according to the volume type and capacity characteristics.
394
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. -extpool extentpool_ID (Required) Creates the base or alias volumes from data extents that are contained in this extent pool. The extent pool storage type defines the volume storage type. An extent pool ID is a four-digit decimal number with no leading zeroes, prefixed with the letter P. -os400 A01 | A81 | A02 | A82 | A04 | A84 | A05 | A85 | A06 | A86 | A07 | A87 (Optional) The OS 400 volume options. This parameter is required if capacity is not specified. The storage sizes and the data types for this volume: v v v v v v v v v v v A01 A81 A02 A82 A04 A84 A05 A85 A06 A86 A07 8.6 GB, protected 8.6 GB, unprotected 17.5 GB, protected 17.5 GB, unprotected 70.5 GB, protected 70.5 GB, unprotected 35.1 GB, protected 35.1 GB, unprotected 141.12 GB, protected 141.12 GB, unprotected 282.25 GB, protected
v A87 - 282.25 GB, unprotected GB is 10^9 Byte. Note: You must ensure that the volume data type is compatible with the host systems that can access this volume. -type ess | ds | blocks (Optional) Specifies the unit type of capacity that is specified by the -cap parameter. ess: Specifies that the unit is 10^9 Bytes. ds: Specifies that the unit is 2^30 Bytes. blocks: Specifies that the unit is 512 blocks. Notes: 1. If the -type parameter is not specified the lun is created as type ds. 2. The -type parameter is ignored when the -os400 parameter is specified. -cap capacity (Optional) Specifies the storage size that is allocated to this volume object. Note: This parameter is required if the -os400 parameter is not specified. If the -type parameter is omitted or the -type ds parameter is specified: v 1GB = 1,073,741,824 (2^30 Bytes)
395
v Supported storage sizes range from 1 to 2048. If the -type ess parameter is specified: v capacity = X.Y or X where X is whole gigabytes, with 1 GB=1,000,000,000 (10^9 Bytes). where Y represents a fraction of 1 GB. Y is limited to a single digit (0...9) to the right of the decimal. v Supported storage sizes range from 0.1 to 982.2 (0.1 increment). If the -type blocks parameter is specified, capacity is the number of 512 blocks. Supported storage sizes are from 1 to 4294967296 (4x2^30 Bytes). -name volume_name (Optional) Your nickname for this volume. The nickname can be 16 characters long, and it can contain one of the following wildcard characters: v (#d) decimal volume ID v (#h) hexadecimal volume ID -volgrp volume_group_ID (Optional) Specifies to which volume group the volumes are assigned. A volume group ID is a four-digit decimal number with no leading zeroes, prefixed with the letter V. -wait (Optional) Delays the command response until the volume configuration processes complete. Note: If you specify this parameter, you must wait until your original command processes completely before you can issue a new command. volume_ID . . . | (Required) An array of one or more fixed block volume IDs to be created. The volumes must share a common logical subsystem ID. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). To specify a range of volume IDs, separate the volume IDs with a dash. You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. Example: 0100-010F 0180-018F 0120 If you specify a dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkfbvol command
dscli>mkfbvol -dev IBM.1750-68FA120 -extpool P1 -name my_vol_#d -type ess -cap 8.6 0100 0101 0102 0103
396
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Device: IBM.1750-68FA120 FB FB FB FB volume volume volume volume 0100 0101 0102 0103 successfully successfully successfully successfully created. created. created. created.
rmfbvol
The rmfbvol command deletes fixed block volumes from a storage image.
rmfbvol -dev storage_image_ID -quiet -safe - volume_ID . . .
Parameters
Note: You can use this command when there are volumes that are in the configuration error state. To correct this configuration state, issue the rmfbvol command for each affected volume. You can specify a volume range according to the command specifications when it is appropriate. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified volume ID for all logical volumes and you do not specify a value for the devid variable in your profile file. -quiet (Optional) Turns off the confirmation prompt for this command. -safe (Optional) Specifies that the system perform a check to see if the specified volumes are assigned to any user-defined volume group. If any volumes are still assigned to a user-defined volume group, the rmfbvol command fails without deleting any volumes. When this occurs, messages are provided that list the volumes that are still assigned to a user-defined volume group. Note: If there is any reason that the system cannot perform the check, the rmfbvol command fails and no volumes are deleted. volume_ID . . . | (Required) Specifies an array of one or more fixed block volume IDs to be removed. This parameter also accepts a fully qualified volume ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. Example of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the Volume_ID parameter as follows:
dscli>rmfbvol -dev IBM.1750-13ABR4A 0005-00FF
If you do not specify the -dev parameter and you specify the volume_ID parameter, you must use the fully qualified version of the volume ID as follows:
dscli>rmfbvol IBM.1750-13ABR4A/0005-00FF
397
The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). To specify a range of volume IDs, separate the volume IDs with a hyphen. You must separate multiple volume IDs or ranges of volume IDs with a blank space between each ID or range of IDs. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmfbvol command
dscli>rmfbvol -dev IBM.1750-68FA120 0100 0101

Sun Aug 11 02:23:49 PST 2004 IBM DSCLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to Volume 0100 successfully Are you sure you want to Volume 0101 successfully delete 0100? y/n Y deleted. delete 0101? y/n Y deleted.
The following is an example of the output that results when you specify that you want a range of volume IDs to be removed. Invoking the rmfbvol command
dscli>rmfbvol -dev IBM.1750-13ABR4A 0005-00FF Date/Time: September 13, 2005 9:38:52 PM MST IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-13ABR4A CMUC00027W [y/n]:y CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I rmfbvol: Are you sure you want to delete FB volume 0005-00FF? rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB FB volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 001A 001B 001C 001D successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully successfully deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted. deleted.
398
CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I CMUC00028I
rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol: rmfbvol:
FB FB FB FB FB FB FB
volume volume volume volume volume volume volume
001E 001F 0020 0021 0022 0023 0024
successfully successfully successfully successfully successfully successfully successfully
deleted. deleted. deleted. deleted. deleted. deleted. deleted.
showfbvol
The showfbvol command displays detailed properties for an individual volume. This command can also be used to display the performance metrics of a fixed block volume.
showfbvol -dev storage_image_ID volume_ID - -rank -metrics
-volgrp
volume_group_ID
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of the manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical volume. -rank (Optional) Specifies that a rank extents table be displayed. This table displays the set of ranks that the logical volume has extents configured on and the number of extents for that logical volume. Note: This parameter cannot be used with the -metrics or -volgrp parameters. -metrics (Optional) Displays volume ID and performance metrics for the specified volume. Notes: 1. All performance counts are an accumulation since the most recent counter wrap or counter reset. Volume performance counters are reset on a power-up sequence. Volume performance counters are reset by a server failover and failback sequence. 2. Do not use this parameter with the -rank or -volgrp parameters. -volgrp volume_group_ID (Required if you do not specify the volume_ID parameter.) Specifies that the fixed block volumes that are associated with the designated volume group ID be displayed. Notes: 1. You can only use the -volgrp parameter when you are doing a query for performance metrics. 2. Do not use the -volgrp parameter with the volume_ID parameter. 3. Do not use the -volgrp parameter with the -rank or -metrics parameters. volume_ID | (Required if you do not specify the -volgrp parameter.) Displays information
399
for the specified volume. This parameter accepts a fully qualified volume ID, which consists of the storage_image_ID or a shortened version without the storage image ID, if you specify the -dev parameter. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Note: Do not use the volume_ID parameter with the -volgrp parameter.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showfbvol command using the -rank parameter. When the rank parameter is specified, a rank extents table is also displayed. It appears at the end of the regular report. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the showfbvol to show volume properties Note: The example output is based on using the showfbvol command for a 1.0 (Binary) GB volume.
dscli>showfbvol -dev IBM.2107-1300861 -rank 6000

Date/Time: April 13, 2005 2:38:14 PM JST IBM DS CLI Version: 5.0.3.40 DS: IBM.21071300861 acc state Online data state Normal config state Normal device MTM 2107-900 data type FB 512
Name My_ volume _6000
ID 6000
addrgrp 6
extpool P0
exts 1
captype DS
cap (2^30B) 1.0
cap (10^9B)
cap (blocks) 2097152
volgrp V2
ranks 3
Rank R0 R2
Extents 1 2
Report field definitions ( -metrics parameter not specified)

Name Specifies the nickname that you assigned for this volume object.
400
ID Specifies the unique identifier that is assigned to this volume object. Accstate One of the following access states are displayed: Online or Fenced. Online The logical volume is accessible to a host. Fenced The logical volume is in the volume fenced state and is not accessible to the host. Datastate One of the following data states are displayed: Normal None of the other data states apply. The access state is Online. Pinned Specifies that none of the other data states apply and the logical volume has one or more pinned non-retryable tracks. The access state is Online. Read only Indicates that the logical volume is read only because one or more extents on the logical volume are on a rank in the read only data state. The access state is Online. Inaccessible Indicates that one or more extents that are associated with the logical volume are on a rank that is in the inaccessible data state. The access state is fenced. Indeterminate data loss Specifies that the following data states do not apply and that one of the following conditions has occurred: Data states that do not apply: v Rank failed v Rank repairing v Rank repaired v Global inaccessible v Global lost data Conditions - one of the following occurred: v Committed write data was lost before it was destaged and the track identifiers that are associated with the data are unknown. v Data was lost that indicated extents on the logical volume were active FlashCopy targets. The access state is fenced. Rank failed Indicates that one or more extents that are associated with the logical volume are on a rank that is in the Failed data state. The access state is Fenced. This data state transitions to Rank repairing if the rank transitions to the Rank repairing state through use of the repair array function. Rank Repairing Indicates that one or more extents that are associated with the logical volume are on ranks in the repairing data state. The access state is fenced.
401
Rank Repaired Indicates that one or more extents that are associated with the logical volume are on ranks that were in the repairing state, but are not in the repairing state now. The access state is fenced. Global inaccessible Specifies that the global metadata that is associated with the logical volume configuration is inaccessible. Some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. Global lost Specifies that global metadata that is associated with the logical volume configuration has been lost. As a result, some of the data that is associated with the logical volume might be inaccurate. The access state is fenced. NVS data inaccessible Specifies that active NVS data is inaccessible for one or more logical volumes of an LSS group. The logical volumes in the LSS group cannot be made accessible. The access state is fenced. Configstate One of the following configuration states are displayed: Normal Indicates that there are no logical volume configuration operations in progress. Configuring Indicates that the logical volume is in the process of being configured for the first time. Reconfiguring Indicates that the logical volume is in the process of allocating or deallocating extents due to a modification of the requested capacity attribute after initial creation. Migrating Indicates that the logical volume is in the process of performing dynamic volume relocation to a specified extent pool. Deconfiguring Indicates that the logical volume is in the process of being deleted. Configuration error Indicates that the initial configuration did not complete successfully. This state reflects an internal error condition and not an error in the request to create the volume. Corrective action: Use the rmfbvol command to delete each volume listed with the configuration state of configuration error. Reconfiguration error Indicates that the reconfiguration request did not complete successfully. Migration error Indicates that the dynamic volume relocation operation was ended during processing. Deconfiguration error Indicates that a request to delete a volume did not complete successfully. This state reflects an internal error condition and not an error in the request to remove the volume. To correct this state, you must reissue the rmfbvol command for the designated volume.
402
deviceMTM Indicates the volume device type and the model. The volume MTM is determined by the fixed block volume data type and the volume capacity (in GB). The model is either 2107 or 1750 however, the MTM can be any one of the following depending on your system: 2107-900 This indicates a standard 2107 volume. 1750-500 This indicates a standard 1750 volume. | | | | | | xxxx-A0x The xxxx is 2107 or 1750; the A0 indicates an System i protected volume (for example, 2107-A01 or 1750-A07). xxxx-A8x The xxxx is 2107 or 1750; the A8 indicates an System i unprotected volume (for example, 2107-A81 or 1750-A87). Datatype Indicates the volume data type setting. One of the following values will be displayed: v FB 512 v FB 520P v FB 520U Addrgrp Specifies the address group that contains the designated volume object. An address group ID is one hexadecimal character ( 0 - F ). Extpool Specifies the extent pool ID. Volume extents are allocated from this extent pool ID. Exts Specifies the number of extents used by the designated volume ID. Captype Indicates capacity unit type used at volume creation. One of the following values is displayed: ESS The capacity unit is 10 ^ 9B. DS The capacity unit is 2 ^ 30B. DS/ESS The capacity unit is 2 ^ 30B or 10 ^ 9B. Blocks The capacity unit 512B. iSeries The capacity unit was not specified at volume creation. This fixed block volume was created for iSeries. Cap (2 ^ 30B) Specifies the size of volume that is available for host system access in 2 ^ 30B (binary GB) unit.
403
Note: (null) is displayed if the capacity unit type of the volume is ESS (captype=ESS) Cap (10 ^ 9B) Specifies the size of volume that is available for host system access in 10 ^ 9B (decimal GB) unit. Note: (null) is displayed if the capacity unit type of the volume is DS (captype=DS) Cap blocks Indicates the quantity of volume logical blocks that are available for host system access. Volgrp Specifies the volume groups (excluding default volume groups) that a volume belongs to. Multiple volume groups that are associated with the volume are separated by a comma. A null (-) is displayed if there are no volume groups that are associated with the volume. Ranks Specifies the number of ranks the volume resides on. Rank (Rank Extent table) Specifies the rank ID. Extents (Rank Extents table) Specifies the number of extents for the volume on the rank.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showfbvol command using the -metrics parameter. Invoking the showfbvol to show performance metrics
dscli>showfbvol -metrics IBM.2107-75FA120/0101

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 norm write req 10000 norm write hits 10000 seq read reqs 10000 seq read hits 10000 seq write req 10000
ID
Date
norm rdrqts 10000
norm rdhits 10000
10/11 /04 IBM. 02:23:49 210775FA120 /0101
404
seqwrite- cachfwrhits reqs 10000 10000
cachfwrhits 10000
cachfwreqs 10000
cachfwhits 10000
inbcachload 10000
bypasscach 10000
seq DASD trans 10000
DASDtrans 10000
cachetrans 10000
NVSspadel 10000
norm write ops 10000
rec seqwrite- cache ops mis 10000 10000
qwriteprots 10000
CKDirtrkac 10000
CKD irtrk hits 10000
cachspdelay 10000
timelowifact 10000
phread 10000
phwrite 10000
phwrite 10000
phbyteread 10000
phbytewrit 10000
recmoreads 10000
sfile trk reads 10000
contamwrts 10000
PPRCtrks 10000
NVSspallo 10000
timephread 10000
timephwrite 10000
byteread 10000
bytewrit 10000
timeread 10000
timewrite 10000
Report field definitions ( -metrics parameter specified)

ID Specifies the unique identifier that is assigned to this volume object. Date Specifies the current time stamp for the volume performance counters. normrdrqts Specifies Search/Read Normal I/O Requests. normrdhits Specifies Search/Read Normal I/O Requests instances. normwritereq Specifies Write Normal I/O Requests. normwritehits Specifies DASD Fast Write I/O Request instances. seqreadreqs Specifies Search/Read Sequential I/O Requests. seqreadhits Specifies Search/Read Sequential I/O Request instances. seqwritereq Specifies Write Sequential I/O Requests. seqwritehits Specifies DASD Fast Write Sequential I/O Request instances. cachfwrreqs Specifies Search/Read Cache Fast Write I/O Requests.
405
cachfwrhits Specifies Search/Read Cache Fast Write I/O Request instances. cachfwreqs Specifies Cache Fast Write I/O Requests. cachfwhits Specifies Cache Fast Write I/O Requests instances. inbcachload Specifies Inhibit Cache Loading I/O Requests that operate with DASD. bypasscach Specifies Bypass Cache I/O Requests. seqDASDtrans Specifies Sequential DASD to Cache Transfer Operations. DASDtrans Specifies DASD to Cache Transfer Operation Count. cachetrans Specifies Cache to DASD Transfer Operation Count. NVSspadel Specifies DASD Fast Write Operations Delayed Due to nonvolatile storage Space Constraints. normwriteops Specifies Normal DASD Fast Write Write Operation Counts. seqwriteops Specifies Sequential Access DASD Fast Write Write Operation Counts. reccachemis Specifies Number of record cache Read Misses. qwriteprots Specifies Quick Write Promotes. CKDirtrkac Specifies Irregular Track Accesses. CKDirtrkhits Specifies Irregular Track Accesses instances. cachspdelay Specifies Operations Delayed Due To Cache Space Constraints. timelowifact Specifies Milliseconds of lower interface I/O activity for the indicated device. phread Specifies Physical Storage Read Operations. phwrite Specifies Physical Storage Write Operations. phbyteread Specifies Physical Storage Bytes Read in 128 KB increments. phbytewrit Specifies Physical Storage Bytes Written in 128 KB increments. recmoreads Specifies Record Mode Read Operations.
406
sfiletrkreads Specifies the Number of tracks read from the Concurrent Copy or XRC Sidefile. contamwrts Specifies the Number of Contaminating writes for a Concurrent Copy or XRC volume. PPRCtrks Specifies the Number of tracks or portion of tracks that were transferred to the secondary device of a PPRC pair. NVSspallo Specifies the NVS Space Allocations. timephread Specifies the Physical Storage Read Response Time in 16 ms increments. timephwrite Specifies the Physical Storage Write Response Time in 16 ms increments. byteread Specifies the number of Bytes read in 128 KB increments. bytewrit Specifies the number of Bytes written in 128 KB increments. timeread Specifies the accumulated response time for all read operations. timewrite Specifies the accumulated response time for all write operations.
Volume group specific commands

This section contains commands that are used to create, modify, and delete volume groups and to display volume group information. Use the following commands to create, modify, and delete volume groups and to display volume group information: v chvolgrp v lsvolgrp v mkvolgrp v rmvolgrp v showvolgrp The chvolgrp command modifies a volume group name and volume members. The lsvolgrp command generates a report that displays a list of volume groups in a storage unit and the status information for each volume group in the list. The mkvolgrp command creates a volume group in a storage unit. The rmvolgrp command deletes the specified volume group or volume groups from a storage unit. The showvolgrp command generates a report that displays the detailed properties of a volume group.
407
chvolgrp
The chvolgrp command modifies a volume group name and volume members.
chvolgrp -dev storage_image_ID -name new_Volume_Group_name
-action
add remove replace
-volume
volume_ID
. . .
-lun
lun_ID
Volume_Group_ID -
Parameters
Note: If you are using an HP-UX operating systems, the number of volumes in the volume group must not exceed 7 volumes. This restriction only applies when the hostconnect attribute for the -addrdiscovery parameter is set to reportlun and the associated volume group is of type mapscsi256. -dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the volume group ID. Example: IBM.1750-68FA120 -name new_Volume_Group_name (Optional). Specifies a new name for the volume group. The name is limited to 16 characters. The name must be unique across volume groups that are contained by a storage unit. -action add | remove | replace (Optional, unless the -volume parameter is specified). Specify one of the following values with this parameter: add remove Specifies that the volumes be removed from the volume group. replace Specifies that the existing volumes be replaced by the specified volumes. Note: The chvolgrp command fails if you have specified the -volume parameter and not included the -action parameter. -volume volume_ID . . . (Optional unless you are specifying the -action or the -lun parameter, then the -volume parameter is required.) Specifies an array of one or more volume IDs or volume ID ranges to be included in the volume group when the -action parameter is specified. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). Specifies that the volumes be added to the volume group.
408
To specify a range of volume IDs, separate the volume IDs with a dash (-). You must separate multiple volume IDs or ranges of volume IDs with a comma between each ID or range of IDs. Notes: 1. For SCSI MAP 256, the array or ranges cannot exceed 256 volume ID entries. Otherwise, up to 64 384 entries are allowed. 2. The chvolgrp command fails if you specify the -volume parameter and do not specify the -action parameter. Example: 0100-010F,0180-018F,0120 -lun lun_ID (Optional - SCSI MAP 256 only). Specifies the LUN ID in hexadecimal value (00 - FF), which is mapped to the specified volume ID when the -action add or -action replace parameter is specified. If multiple volume IDs are specified by the -volume parameter, the LUN ID is consecutively assigned in incremental order. If the specified LUN ID is not valid, the command is rejected. Note: This parameter is only valid when the target volume group type is SCSI MAP 256. Otherwise, this command fails. If the -action add parameter is specified and the specified LUN ID is already mapped to the other volume in the specified volume group, the command fails. If the -action add parameter is specified without the -lun parameter, an unused LUN ID is assigned to the volume ID. In this case, the unused LUN ID is selected from a smaller number. The following example shows how this works:
A volume group of "SCSI Map 256" type has Volume 0000 and 0001. Their LUNs are the members of the following volume group: (showvolgrp displays the current mapping.) 0000 : 10 0001 : 11 Because the range of LUN IDs is 00-FF, the unused LUN IDs are 00,01,...,0F,12,13,...,FF. If you add volume 0002 and 0003 to this volume group without the -lun parameter, the mapping results in the following because 00 and 01 are "smaller" unused LUN IDs: 0002 : 00 0003 : 01 0000 : 10 0001 : 11
If the -action replace parameter is specified without specifying the -lun parameter, lun_ID=00 is assumed. Volume_Group_ID | (Required). Specifies the ID of the volume group being changed. The volume group ID is made up of the storage image ID followed by the volume group ID. This parameter also accepts a fully qualified volume group ID including the storage image ID or a shortened version. The shortened version is a four-digit decimal number with no leading zeroes, prefixed with the letter V. If you specify the dash (-), this parameter information is automatically supplied. Example: IBM.1750-68FA1243/V1231
409
Example (1750)
Invoking the chvolgrp command
dscli>chvolgrp -volume 0000-000F IBM.1750-68FA120/V2341

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Volume group V2341 successfully modified.
lsvolgrp
The lsvolgrp command displays a list of volume groups in a storage image and status information for each volume group in the list.
lsvolgrp -dev storage_image_ID -s -l -type scsimask scsimap256 os400mask
-volume
volume_ID
Volume_Group_ID . . . -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, machine type, and serial number. Displays only the objects for the storage unit that is specified. This parameter is required if you do not specify a fully qualified volume group ID and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -s -l (Optional). Displays volume group IDs only. You cannot use the -l and the -s parameters together. (Optional). Displays the default output plus users. You cannot use the -l and the -s parameters together.
-type | scsimask | scsimap256 | os400mask (Optional). Displays only volume groups that are configured as the specified volume group type. -volume volume_ID (Optional). Displays volume groups that contain the specified volume ID. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). Volume_Group_ID . . . | (Optional). Displays volume groups with the specified IDs. A volume group ID is a four-digit decimal number with no leading zeroes, prefixed with the letter V. This parameter accepts a fully qualified volume group ID or a shortened version, if the -dev parameter is specified.
410
To specify a range of volume group IDs, separate the volume group IDs with a hyphen. You must separate multiple volume group IDs or ranges of volume group IDs with a blank space between each ID or range of IDs. If you specify a dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following table represents the headers that are displayed on the output report that is associated with the lsvolgrp command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both the 2107 and 1750. Invoking the lsvolgrp command
dscli>lsvolgrp -dev IBM.2107-75FA120 -l

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Device: IBM.2107-75FA120 Name Host_xxx _volumes Host_yyy _volumes Host_zzz _volumes ID 1011 1111 1211 Type OS400 Mask OS400 Map 256 SCSI Mask

Name Specifies the name you assigned for this volume group ID. ID Specifies the storage unit ID followed by the volume group ID. The volume group identifier is a four-digit decimal number, with no leading zeros, prefixed by the letter V. Specifies the type of the volume group.
Type
mkvolgrp
The mkvolgrp command creates a volume group in a storage image.
mkvolgrp -dev storage_image_ID -hosttype host_type -type scsimask scsimap256 os400mask
-volume
volume_ID
. . .
-lun
lun_ID
Volume_Group_Name -
Parameters
Notes:
411
1. It is highly recommended that you use the -hosttype parameter when you issue this command. 2. When you create DS6000 volume groups for (RedHat) Linux using the mkvolgrp command, the -type parameter must be set to scsimap256. 3. When you create DS6000 volume groups for AIX5L, the -type parameter must be set to scsimap. If you are using an HP-UX operating system, the number of volumes in the volume group must not exceed 7 volumes. This restriction only applies when the hostconnect attribute for the -addrdiscovery parameter is set to reportlun and the associated volume group is of type scsimap256. -dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified volume group name. Example: IBM.1750-68FA120 -hosttype host_type (Optional) Use this parameter as an alternative method for specifying the type of Volume Group. Note: You cannot use this parameter with the -type parameter. -type | scsimask | scsimap256 | os400mask | (Optional). Specifies the type of the volume group. scsimask (default) Creates a SCSI mask volume group. This option is available if the host adapter supports four-byte LUN addresses. scsimap256 Creates a SCSI-MAP 256 volume group. os400mask Creates an OS400 mask volume group. The IBM iSeries host system typically uses fixed block volumes of 520-byte logical block size. This option is available only if the host adapter supports four-byte LUN addresses. Note: This volume group is also referred to as SCSI520-MASK. When an error message is displayed for the OS400 MASK, SCSI520-MASK is referenced instead. Note: You cannot use this parameter with the -type parameter. -volume volume_ID | . . . (Optional). Specifies the array of volume IDs to include in the volume group. For the -type scsimap256 parameter, the array cannot exceed 256 volume ID entries. Otherwise, up to 64 384 entries are allowed. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). To specify a range of volume IDs, separate the volume IDs with a dash (). You must separate multiple volume IDs or ranges of volume IDs with a comma between each ID or range of IDs.
412
Example: 0100-010F,0180-018F,0120 -lun lun_ID (Optional)Specifies the LUN ID in hexadecimal value (00 - FF) which is mapped to the specified volume ID for a SCSI-MAP256 type volume group. If multiple volume IDs are specified by the -volume parameter, LUN IDs are assigned consecutively in incremental order. Note: This parameter is only valid for a SCSI-MAP 256 type volume group. If this parameter is specified for any other type of volume group, the command fails. Volume_Group_Name | (Required). Specifies the volume group name, not to exceed 16 characters. Ensure that the name is unique within the scope of the storage image. Accepts a fully qualified volume group name or a shortened version, if the -dev parameter is specified. If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the mkvolgrp command
dscli>mkvolgrp -dev IBM.1750-68FA120 -volume 0000-000F host_xyz_volumes

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Volume group V0 successfully created.
rmvolgrp
The rmvolgrp command deletes existing volume groups from a storage image.
rmvolgrp -dev storage_image_ID -quiet - Volume_Group_ID . . .
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified volume group ID and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -quiet (Optional). Specifies that confirmation prompt for this command be turned off. Volume_Group_ID . . . | (Required). Specifies an array of one or more volume groups IDs to be deleted. All volume groups specified must belong to the same storage unit. This parameter also accepts a fully qualified volume group ID, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeroes, prefixed with the letter V.
413
To specify a range of volume group IDs, separate the volume group IDs with a dash (-). You must separate multiple volume group IDs or ranges of volume group IDs with a blank space between each ID or range of IDs. If you use the dash (-), this parameter information is automatically supplied. Example of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the Volume_Group_ID parameter as follows:
dscli>rmvolgrp -dev IBM.1750-68FA120 V11
If you do not specify the -dev parameter and you specify the Volume_Group_ID parameter, you must use the fully qualified version of the volume group ID as follows:
dscli>rmvolgrp IBM.1750-68FA120/V11
Example (1750)
Invoking the rmvolgrp command
dscli>rmvolgrp IBM.1750-68FA1243/V123

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete Volume Group IBM.1750-75FA1243/V123? y/n Y Volume group IBM.1750-75FA1243/V123 successfully deleted.
showvolgrp
The showvolgrp command displays detailed properties of a volume group.
showvolgrp -dev storage_image_ID -lunmap Volume_Group_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, machine type, and serial number. Note: This parameter is required if you do not specify a fully qualified volume group ID and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -lunmap (Optional). Specifies that a LUN mapping table be displayed that shows the volume ID and LUN ID relationship. This parameter is valid for all scsi and os400 type volume groups. Volume_Group_ID | (Required). Specifies that the properties be displayed for the specified volume group. This parameter accepts a fully qualified volume group ID, which consists of the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is a four-digit decimal number with no leading zeros, prefixed with the letter V.
414
Examples of -dev parameter use If you specify the -dev parameter, you can use the shortened version of the Volume_Group_ID parameter as follows:
dscli>showvolgrp -dev IBM.1750-68FA120 V11
where V11 represents value for the volume group ID. If you do not specify the -dev parameter, and you specify the Volume_Group_ID parameter, you must specify the fully qualified version of the Volume_Group_ID parameter as follows:
dscli>showvolgrp IBM.1750-68FA120/V11
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output reports that are associated with the showvolgrp command. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Note: The volume group type determines the format of the LUN ID that is reported. The following examples demonstrate these differences. Invoking the showvolgrp command where the volume group type is SCSI MAP 256
dscli>showvolgrp -lunmap IBM.2107-1300861/V2

Date/Time: May 17, 2006 8:33:58 AM GMT IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-1300861 Name My_host_ system_ volumes ID V2 Type SCSIMAP 256 Vols 1000 1002 1004 1006 1001 1003 1005 1007
============================LUN Mapping=========================== Vol 1000 1001 1002 1003 1004 1005 1006 LUN 00 01 02 03 04 05 06
415
Vol 1007
LUN 07
Invoking the showvolgrp command where the volume group type is SCSI Mask
dscli>showvolgrp -lunmap IBM.2107-1300861/V18

Date/Time: May 17, 2006 8:38:08 AM GMT IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-1300861 Name myVG1 ID V18 Type SCSIMask Vols 1000 1002 1004 1006 1001 1003 1005 1007
============================LUN Mapping=========================== Vol 1000 1001 1002 1003 1004 1005 1006 1007 LUN 40104000 40104001 40104002 40104003 40104004 40104005 40104006 40104007

Name Specifies the name that you assigned for the designated volume group ID. ID Type Specifies the volume group ID. The volume group identifier is a four-digit decimal number having no leading zeros, and prefixed by a V. Specifies the configured volume group type. Any one of the following volume group types can be queried: SCSI all | SCSI Mask | SCSI MAP 256 | os400 all | os400 Mask Note: os400 all and os400 Mask are sometimes referred to as SCSI520 all and SCSI520 Mask. Vols Identifies the complement of accessible volume numbers within the designated volume group.
Vol (part of LUN mapping table) Specifies the volume ID. LUNS (part of LUN mapping table) Specifies the LUN ID that is mapped to the designated volume ID. As noted in the examples, the LUN IDs can be different based on volume group type.
416
Advanced operation commands

This section contains commands that are used to further administer and tune storage. Use the following command to administer and tune storage: clearvol The clearvol command clears Copy Services relationships for a base logical volume.
clearvol
The clearvol command clears Copy Services relationships for a base logical volume.
clearvol -dev storage_image_ID -pprcsource -pprctarget -fcsource
-fctarget
Volume_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the volume ID. Example: IBM.1750-68FA120 -pprcsource (Optional). This parameter is used with a base logical volume. It removes any remote mirror and copy relationships on the logical volume where the specified logical volume operates as a remote mirror and copy source. -pprctarget (Optional). This parameter is used with a base logical volume. It removes any remote mirror and copy relationships on the logical volume where the specified logical volume operates as a remote mirror and copy target. -fcsource (Optional). This parameter is used with a base logical volume. It removes any FlashCopy relationships on the logical volume where the specified logical volume operates as a FlashCopy source. -fctarget (Optional). This parameter is used with a base logical volume. It removes any FlashCopy relationships on the logical volume where the specified logical volume operates as a FlashCopy target. Volume_ID | (Required). Specifies the volume ID where Copy Services relationships are to be cleared. This parameter accepts a fully qualified volume ID, which includes the storage image ID or a shortened version, if the -dev parameter is specified. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF).
417
If you specify the dash (-), this parameter information is automatically supplied. Example: IBM.1750-68FA120/0001
Example (1750)
Invoking the clearvol command
dscli>clearvol -dev IBM.1750-68FA120 0001

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Volume 0001 successfully cleared.
Copy Services commands

This section contains Copy Services commands. You can use the following Copy Services commands to manage Copy Services tasks.
FlashCopy commands
This section contains commands that are used to configure FlashCopy relationships and to display FlashCopy information. Use the following commands to configure FlashCopy relationships and to display FlashCopy information: v v v v v v v commitflash resyncflash lsflash mkflash reverseflash revertflash rmflash
v unfreezeflash v setflashrevert The commitflash command completes a partially formed Global Mirror consistency group. It is used as part of the recovery from a disaster. The resyncflash command creates a point-in-time copy of an existing FlashCopy pair that was established with the -record and -persist parameters. The resyncflash command only copies the parts of the volume that have changed since the last point in time copy. The lsflash command generates a report that displays a list of FlashCopy relationships and the status information for each FlashCopy relationship in the list. The mkflash command initiates a point-in-time copy from source volumes to target volumes. The reverseflash command reverses the FlashCopy relationship.
418
The revertflash command restores the former Global Mirror consistency group from one that is currently forming. It is used as part of the recovery from a disaster. The rmflash command removes a relationship between FlashCopy volume pairs. The unfreezeflash command resets a FlashCopy consistency group that was previously established with the -freeze parameter when the mkflash or resyncflash commands were issued. The setflashrevert command modifies a FlashCopy volume pair that is part of a Global Mirror relationship to revertible. The revertible feature allows data to be committed to the target to form a new consistency group, or restored back to the last consistency group.
commitflash
The commitflash command is used as part of the recovery from a disaster scenario to complete a partially formed Global Mirror consistency group.
commitflash -dev source_volume_ID . . . - storage_image_ID -seqnum flash_sequence_num
Parameters
| | | | | The following transactions must be completed before you can issue the commitflash command: 1. Issue the mkflash command with the -record and -persist parameters specified to establish the FlashCopy volume pair relationship. 2. Issue the setflashrevertible command on the FlashCopy volume pair. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for all the source volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -seqnum flash_sequence_number (Optional) When a FlashCopy sequence number is specified, the commit operation is performed only on those relationships that are associated with the specified number. This parameter is not supported for machine type 2105. Example: 0010 source_volume_ID . . . | (Required) Specifies the source volumes for which FlashCopy relationships are to be committed. The chosen FlashCopy pair is the one established or modified with the -record parameter. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage
419
image IDs if either the -dev parameter is specified or you specify a value for the devid variable in your profile file. You must separate multiple source volume IDs with spaces. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified volume ID: IBM.1750-68FA120/0001 Example of a shortened version: 0001 Example of multiple IDs: 0001 0003 0008
Example (1750)
Invoking the commitflash command
dscli>commitflash IBM.1750-68FA120/0100

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy volume pair IBM.1750-75FA120/0100:IBM.1750-68FA120/0200 successfully committed.
resyncflash
The resyncflash command is a point in time copy of an existing FlashCopy pair established with the -record and -persist parameters. The resyncflash command only copies the parts of the volume that have changed since the last point in time copy. When a pair is established with the -record and -persist parameters, the pair initially synchronizes and then a record of all host write operations to the source is maintained in the source volumes. When the resyncflash command is issued on the pair, the new data that is written to the source is copied to the target. The parameters specified in this command replace the parameters in the existing relationship. In order to keep the initial -record and -persist parameters, the -record and -persist parameters must be specified in the resyncflash command.
resyncflash -dev storage_image_ID -record -persist -freeze
-tgtpprc
-tgtoffline
-tgtinhibit
-seqnum
flash_sequence_num
source_volume_ID:target_volume_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes values for the manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file.
420
Example: IBM.1750-68FA120 -record (Optional) Records the changed tracks on both volumes within a FlashCopy pair. Use this parameter if you intend to use the resyncflash command again with this pair. The -persist parameter is automatically selected when the -record parameter is selected. Note: You cannot reissue the resyncflash command if you leave this parameter out of your command string. -persist (Optional) Retains the FlashCopy relationship after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until broken by a rmflash command. This parameter is automatically selected when the -record parameter is selected. Select this parameter along with the -record parameter if you are using this volume pair with the commands resyncflash, reverseflash, or setflashrevertible. Note: You cannot reissue the resyncflash command if you leave this parameter out of your command string. -freeze (Optional) Triggers the queue full condition for the source volume. All writes to the source volume are queued by the host and are written after the queue full condition is reset. During the queue full condition, the source volume reports long busy status. The queue full condition is reset by an extended long busy timeout. The timeout condition affects all FlashCopy source volumes that are contained within a respective logical subsystem and that are established or modified with the -freeze parameter. -tgtpprc (Optional) Allows the FlashCopy target volume to be a Remote Mirror and Copy source volume. -tgtoffline (Optional) Causes the mkflash command to be rejected if the target volume is online for host system access. This parameter only applies to CKD volumes. -tgtinhibit (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relationships that are established with the specified sequence number. This sequence number can be used as an identifier for a relationship or group of relationships. Only the relationships that are modified successfully by the resyncflash command get the specified sequence number, leaving the ones that failed with the previous one (if they were previously specified). This parameter is not supported for machine type 2105. Example: 0010 source_volume_ID:target_volume_ID . . . | (Required) Increments a FlashCopy relationship for the source and target volume pairs with the IDs specified. This parameter accepts fully qualified
421
volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified or you specify a value for the devid variable in your profile file. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-75FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the resyncflash command
dscli>resyncflash IBM.1750-68FA120/0100:IBM.1750-68FA120/0200
The resulting output | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote FlashCopy volume pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully resynchronized.
lsflash
The lsflash command displays a list of FlashCopy relationships and status information for each FlashCopy relationship in the list.
lsflash -dev storage_image_ID -s -l -activecp -record -persist
-revertible
-cp
-state
valid invalid validation-required volume-inaccessible tgt-failed not-valid source_volume_ID:target_volume_ID
-seqnum
flash_sequence_num -
. . .
422
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -s -l (Optional) Displays FlashCopy pair IDs. You cannot use the -l and the -s parameters together. (Optional) Displays the default output plus copy indicator, out of sync tracks, date created, and date synchronized. You cannot use the -l and the -s parameters together.
-activecp (Optional) Displays the FlashCopy relationships where their background copy process is active. Note: The background copy process might be inactive for a while before it starts. -record (Optional) Displays the FlashCopy relationships that were established with the -record parameter. -persist (Optional) Displays the FlashCopy relationships that were established with the -persist parameter. -revertible (Optional) Displays the FlashCopy relationships that were established with the -revertible parameter. -cp (Optional) Displays the FlashCopy relationships that were established with the -cp parameter. -state valid | invalid | validation-required | volume-inaccessible | tgt-failed | not-valid (Optional) Displays the FlashCopy relationships that are identified by the specific state. Note: When you specify not-valid, all FlashCopy relationships that do not meet the requirements the valid state are displayed. -seqnum flash_sequence_number (Optional) Displays the FlashCopy relationships that are associated with the specified sequence number. The default is 0000. This parameter is not supported for machine type 2105. source_volume_ID:target_volume_ID | source_volume_ID . . . | (Required) Displays the FlashCopy relationships for the source and target volume pairs with the specified IDs, or displays the FlashCopy relationships for a single volume ID if the source volume ID is specified. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified or you can specify a value for the devid variable in your profile file.
423
A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). You must separate multiple IDs with spaces. You can specify FlashCopy pair IDs and a range of FlashCopy pair IDs, or you can specify source volume IDs and a range of source volume IDs. You cannot specify a combination of FlashCopy pair IDs and source volumes IDs. If you specify the dash (-0), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsflash command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the lsflash command

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Sequence Num 10 10 11 11 TimeActive out (secs) Copy 120 120 120 120 Disabled Disabled Disabled Disabled Recording Disabled Disabled Disabled Disabled Persistent Disabled Disabled Disabled Disabled Revertible Disabled Disabled Disabled Disabled
ID 0100:0200 0101:0201 0102:0202 0103:0203
SrcLSS 01 01 01 01
CopyIndicator Yes
OutOfSyncTracks 0
DateCreated 12/01 /2003 02:20:00
DateSynced 12/01 /2003 02:23:47
State Valid
424
CopyIndicator Yes
OutOfSyncTracks 0
DateCreated 12/01 /2003 02:20:00 12/01 /2003 02:20:00 12/01 /2003 02:20:00
DateSynced 12/01 /2003 02:23:47 12/01 /2003 02:23:47 12/01 /2003 02:23:47
State Valid
Enabled
Disabled
Disabled
Yes
Valid
Enabled
Disabled
Disabled
Yes
Valid

ID Specifies the FlashCopy pair ID. This ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. Specifies the Consistency Group LSS ID that is associated with the source volume of this FlashCopy relationship. Sequence Num Specifies the sequence number that is associated with the FlashCopy relationship. Note: This item is not supported on the 2105. Timeout (secs) Specifies the consistency group Long Busy Timeout setting for the LSS ID that is associated with the source volume of this FlashCopy relationship. You can specify a value in the range of 1 - 600 000. The default value is 120 seconds. ActiveCopy Specifies (Enabled or Disabled) whether the background copy process is active for this FlashCopy relationship. Recording Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the record changes option. Persistent Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the persistent option. Revertible Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the revertible option. SourceWriteEnabled Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the allow source writes option. TargetWriteEnabled Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the allow target writes option.
SrcLSS
425
BackgroundCopy Specifies (Enabled or Disabled) whether this FlashCopy relationship was established with the run background copy option. CopyIndicator Specifies (Yes or No) whether the CopyIndicator is set for this FlashCopy relationship. OutOfSyncTracks Specifies the number of tracks that are not synchronized for this FlashCopy relationship. The maximum value that can be displayed is dependent on the source volume size. DateCreated Specifies the date and the time that the FlashCopy relationship was established. DateSynced Specifies the date and time this FlashCopy relationship was synchronized, or null (-) if the relationship is not synchronized. State Specifies the state of the FlashCopy relationships. One of the following values is displayed for each FlashCopy relationship: Note: When a query indicates any state other than valid, the only information that is displayed on the report is the FlashCopy pair ID and the state condition. The rest of the information columns are displayed with a null (-) value. Valid Indicates that the FlashCopy relationship is in a normal state, and that it has been queried successfully.
Validation Required Indicates that the FlashCopy relationship cannot be queried. Generally, the reason that the query is blocked is only temporary. If you issue a new query within several seconds, the problem no longer exists. Tgt Failed Indicates that the FlashCopy relationship is in an error state. The point-in-time copy is lost, and the FlashCopy relationship must be withdrawn. You must issue the rmflash command to remove the FlashCopy relationship. Volume Inaccessible Indicates that the volume cannot be accessed and that the query has failed. When this state is displayed, it generally means that the volume is in a fenced condition. Invalid Indicates that a general internal error occurred when the query was processed.
mkflash
The mkflash command initiates a point-in-time copy from source volumes to target volumes.
mkflash -dev storage_image_ID -tgtpprc -tgtoffline -tgtinhibit
426
-freeze
-record
-persist
-nocp
-wait
source_volume_ID:target_volume_ID -seqnum flash_sequence_num - . . .
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of a manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -tgtpprc (Optional) Allows the FlashCopy target volume to be a remote mirror and copy source volume. -tgtoffline (Optional) Causes the mkflash command to be rejected if the target volume is online for host system access. This parameter applies only to count key data volumes. -tgtinhibit (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists. -freeze (Optional) Triggers the queue full condition for the source volume. All writes to the source volume are queued by the host and are written after the queue full condition is reset. During the queue full condition, the source volume reports long busy status. The queue full condition is reset by an extended long busy timeout. The timeout condition affects all FlashCopy source volumes that are contained within a respective logical subsystem and that are established or modified with the -freeze parameter. Note: If you need to modify the extended long busy timeout setting, use the chlss and chlcu commands. -record (Optional) Records the changed tracks on both volumes within a FlashCopy pair. Select this parameter when you establish an initial FlashCopy volume pair that you intend to use with the resyncflash command. The -persist parameter is automatically selected when this parameter is selected. -persist (Optional) Retains the FlashCopy relationship after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until you issue a rmflash command. This parameter is automatically selected when the -record parameter is selected. Select this parameter along with the -record parameter if you will be using this volume pair with the resyncflash, reverseflash, or setflashrevertible commands.
427
-nocp (Optional) Inhibits background copy. Data is copied from the source volume to the target volume only if a track on the source volume is modified. The FlashCopy volume pair relationship remains indefinitely until it is broken by a rmflash command, or until all tracks on the source volume are modified. -wait (Optional) Delays the command response until the background copy process completes. You cannot use the -wait parameter with either the -persist or -nocp parameters. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relations that are established with the specified sequence number. This sequence number can be used as an identifier for a relation or group of relations. This parameter is not supported for machine type 2105. Example: 0010 source_volume_ID:target_volume_ID . . . | (Required) Establishes a FlashCopy relationship for the source and target volume pairs with the specified IDs. This command accepts fully qualified volume IDs, which consist of storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You can also specify a value for the devid variable in your profile file. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. Note: It is possible that during processing you will receive an error message indicating that relationships have been exceeded or that an initial volume format is in progress. This means that the FlashCopy relationship cannot be established because the maximum number of relationships have already been established. Or, the volume was recently created and is still being initialized to support FlashCopy. You can issue a mkflash command to establish the FlashCopy relationship after the initial volume format process is complete. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
428
Example (1750)
Invoking the mkflash command
dscli>mkflash IBM.1750-68FA120/0100:IBM.1750-75FA120/0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair IBM.1750-75FA120/0100:IBM.1750-75FA120/0200 successfully created.
reverseflash
The reverseflash command reverses the FlashCopy relationship.
reverseflash -dev storage_image_ID -record -persist -fast
-tgtpprc
-tgtoffline
-tgtinhibit
-seqnum
flash_sequence_num
Parameters
The direction of a FlashCopy relationship can be reversed, where the volume that was previously defined as the target becomes the source for the volume that was previously defined as the source (and is now the target). The data that has changed is copied to the volume that was previously defined as the source. For example, suppose you create a FlashCopy relationship between source volume A and target volume B. Data loss occurs on source volume A. To keep applications running, you can reverse the FlashCopy relationship so that volume B is copied to volume A. The source volume and the target volume that are specified by this command are the current source and target volumes that, as a result of this command process, become reversed. The specified target volume becomes the source and the specified source volume becomes the target. The target parameters specified by this command apply to the new target (the source volume that becomes the target volume when this command is processed). After the reversal takes place, ensure that you designate this new relationship when you issue any future commands. Failure to designate this reversed relationship could produce unexpected results. For example, you reverse the relationship of source volume 1600 and target volume 1800. Using the reverseflash command, your source volume becomes 1800 and your target volume become 1600. All queries and future processing on this relationship must show volume 1800 as your source and volume 1600 as your target. The following list defines the parameters that are associated with the reverseflash command: -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not
429
specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-75FA120 -record (Optional) Records the changed tracks on both volumes within a FlashCopy pair. Use this parameter when you establish an initial FlashCopy volume pair that you intend to use with the resyncflash command. The -persist parameter is automatically designated when the -record parameter is selected. -persist (Optional) Retains the FlashCopy relationship after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until it is broken by a rmflash command. This parameter is automatically designated when the -record parameter is specified. Select the -persist parameter along with the -record parameter if you are using this volume pair with the resyncflash, reverseflash, or setflashrevertible commands. -fast (Optional) Specify this parameter when the reverseflash command will be issued before the background copy completes. Note: To use the fast reverse function, the relationship must be set to Target write inhibit. The fast reverse processing function is intended for use as part of Global Mirror recovery process. At the end of this operation (processing the reverseflash command with the -fast parameter), the original FlashCopy target volume is unusable. Normally, after this command completes the background copy, the new FlashCopy target is used as FlashCopy source to restore the original FlashCopy target. -tgtpprc (Optional) Allows the FlashCopy target volume to be a Remote Mirror and Copy source volume. -tgtoffline (Optional) Causes the reverseflash command to be rejected if the target volume is online for host system access. This parameter only applies to CKD volumes. -tgtinhibit (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relations that are reversed with the specified sequence number. Only the relations that are successfully modified by the command receive the specified sequence number, leaving the ones that failed with the previous number (if previously specified). The sequence number is a four-digit hexadecimal number (0000 - FFFF). The default is 0000. Example: 0010 This parameter is not supported for machine type 2105. source_volume_ID:target_volume_ID . . . | (Required) Reverses a FlashCopy relationship for the source and target volume pairs with the specified IDs. This parameter accepts fully qualified volume IDs,
430
which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified or you specify a value for the devid variable in your profile file. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the reverseflash command
dscli>reverseflash IBM.1750-68FA120/0100:IBM.1750-68FA120/0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy volume pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully reversed.
revertflash
The revertflash command is used as part of the recovery from a disaster scenario to rollback a Global Mirror consistency group that is in the process of forming. The former Global Mirror consistency group is restored.
revertflash -dev SourceVolume_ID . . . - storage_image_ID -seqnum flash_sequence_num
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source volume and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-685FA120
431
-seqnum flash_sequence_num (Optional) Specifies the FlashCopy sequence number. When this number is specified, the revertflash operation is performed only on those relations associated with the specified number. This parameter is not supported for machine type 2105. Example: 0010 SourceVolumeID . . . | (Required) Specifies the source volume ID for which the FlashCopy relationship is to be reverted. The chosen FlashCopy pair is the one established or modified with the -record parameter. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified or you specify a value for the devid variable in your profile file. You must separate multiple source volume IDs with spaces. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified volume ID: IBM.1750-68FA120/0001 Example of a shortened version: 0001 Example of multiple IDs: 0001 0003 0008
Example (1750)
Invoking the revertflash command
| | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair 0100:0200 successfully reverted.
rmflash
The rmflash command removes a relationship between FlashCopy volume pairs.
rmflash -dev storage_image_ID -quiet -tgtonly -cp
-resettgtinhibit
-wait
-seqnum
flash_sequence_number
SourceVolumeID:TargetVolumeID . . . -
Parameters
Notes:
432
1. Invoking this command with the -cp parameter on a FlashCopy relationship that was previously marked with the -persist parameter will not remove the relationship. Instead, the source data is copied to the target. 2. Invoking this command with the -resettgtinhibit parameter does not withdraw the relationship, but resets the -tgtinhibit parameter if it was previously set. 3. All settings apply to all FlashCopy pairs specified. 4. Do not use the -wait parameter on persistent relations. 5. The-seqnum parameter is not supported for model 2105. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -quiet (Optional) Specifies that the confirmation prompt for this command be turned off. -tgtonly (Optional) Specifies the target volume of the FlashCopy pair to remove the relationship. In addition, the Copy Indicator for the target volume is reset. This parameter applies only to fixed block volumes. -cp (Optional) Specifies that the FlashCopy relationship be changed from No Copy to Copy and that the remaining source volume tracks be copied to the target volume. The relationship is removed when all the data is copied unless the relationship is persistent. When this parameter is specified, the copy takes place for all volume pairs where the source volume ID is identical to the source volume specified in the command. -resettgtinhibit (Optional) Specifies that the flag that does not allow host system write operations to the target ID while the FlashCopy relationship exists be reset, in case it was previously set. Note: Specifying this parameter in itself does not cause the FlashCopy relationship to be withdrawn. -wait (Optional) Specifies that the command response be delayed until the background copy process completes. Notes: Only pairs of source and target volume IDs are allowed when you use the -wait parameter. 2. The -cp parameter must be used with the -wait parameter. 3. Do not use the -wait parameter on relationships that are marked -persist, an error occurs when this is done. 1.
433
-seqnum flash_sequence_num (Optional) Specifies the FlashCopy sequence number. When this number is specified, the rmflash operation is performed only on those relationships associated with the specified number. Example: 0010 Note: This parameter is not supported for machine type 2105. SourceVolumeID:TargetVolumeID . . . | (Required) Specifies the source and target volume pairs for which the FlashCopy relationships are removed. This parameter accepts a fully qualified volume ID, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified or you specify a value for the devid variable in your profile file. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. When the -tgtonly parameter is specified, you must enter volume IDs. Volume pair IDs are not valid with the -tgtonly parameter. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the rmflash command
dscli>rmflash IBM.1750-68FA12/00100:1750-68FA12/0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to remove the FlashCopy pair IBM.1750-68FA120/0001:IBM.1750-68FA120/0002? [y/n]: Y FlashCopy pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully removed.
unfreezeflash
The unfreezeflash command resets a FlashCopy consistency group that was previously established with the -freeze parameter when the mkflash or resyncflash commands were issued.
434
unfreezeflash -dev storage_image_ID
source_LSS_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source LSS ID or you do not specify a value for the devid variable in your profile file. | | | | | | | | | | | | source_LSS_ID . . . | (Required) Specifies that the FlashCopy consistency group be reset for the designated source LSS IDs. The parameter also accepts fully qualified LSS IDs, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified or you specify a value for the devid variable in your profile file. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified LSS ID: IBM.1750-68FA120/00 Example of a shortened version: 00 Example of multiple IDs: 10 20 30
Example (1750)
Invoking the unfreezeflash command
dscli>unfreezeflash IBM.1750-68FA120/01

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy consistency group for logical subsystem IBM.1750-75FA120 01 successfully reset.
setflashrevertible
The setflashrevertible command modifies a FlashCopy volume pair that is part of a Global Mirror relationship to revertible. The revertible feature allows data to be committed to the target to form a new consistency, or reverted back to the last consistency. This command must be run before the FlashCopy pair can be committed or reverted.
setflashrevertible -dev storage_image_ID -tgtoffline
source_volume_ID:target_volume_ID -seqnum flash_sequence_num - . . .
435
Parameters
Note: The -nocp, -record, -persist, and -tgtinhibit (target inhibit) parameters are included automatically when this command processes. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source volume and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -tgtoffline (Optional) Causes an establish FlashCopy volume pair command to be rejected if the target volume is online for host system access. This parameter applies only to CKD volumes. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relationships that are changed with the specified sequence number. Only the relationships that are successfully modified by the command are assigned the specified sequence number, leaving the ones that fail with the previous number (if previously specified). This parameter is not supported for machine type 2105. Example: 0010 source_volume_ID:target_volume_ID . . . | (Required) Modifies FlashCopy relationships for the source and target volume pairs with the IDs specified. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified, or you can specify a value for the devid variable in your profile file. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the setflashrevertible command
dscli>setflashrevertible IBM.1750-68FA120/0100:IBM.1750-68FA120/0200
436

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy volume pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully made revertible.
Remote FlashCopy commands

This section contains commands that are used to configure Remote FlashCopy relationships and to display Remote FlashCopy information. Remote FlashCopy commands are used to process what was formerly known as inband FlashCopy transactions. These types of transactions cannot be handled through the GUI. Use the following commands to configure Remote FlashCopy relationships and to display Remote FlashCopy information. Also, see the Processing Remote FlashCopy (inband) transactions scenario for more details. v commitremoteflash v resyncremoteflash v lsremoteflash v mkremoteflash v revertremoteflash v rmremoteflash v setremoteflashrevertible The commitremoteflash command sends data to a target volume to form a consistency between the remote source and target FlashCopy pair. The resyncremoteflash command increments an existing remote FlashCopy pair that has been established with the -record and -persist parameters. The lsremoteflash command generates a report that displays a list of FlashCopy relationships and the status information for each FlashCopy relationship in the list. The mkremoteflash command initiates a remote point-in-time copy from source volumes to target volumes through a remote mirror and copy relationship. The revertremoteflash command restores data on the source volume to its most recent consistency formation. The rmremoteflash command removes a relationship between remote FlashCopy volume pairs. The setremoteflashrevertible command modifies the specified remote FlashCopy volume pair that is part of a Global Mirror relationship to a revertible state. This command must be run before the FlashCopy pair can be committed or reverted.
commitremoteflash
The commitremoteflash command sends data to a target volume to form a consistency between the remote source and target FlashCopy pair.
commitremoteflash -dev storage_image_ID -conduit LSS_ID
437
SourceVolumeID -seqnum flash_sequence_num -srcss SS_ID - . . .
Parameters
Notes: 1. Establish the pair by issuing either the mkflash or mkremoteflash command with the -record and -persist parameters. 2. Issue either the setflashrevertible or setremoteflashrevertible command against the pair. Only after you have taken these two steps can you issue the commitremoteflash command. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all the source volumes and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy relationship that is to be used as a means for communicating with the remote storage image. The source volume IDs that are specified in the SourceVolumeID parameter must serve as secondary volumes in a remote mirror and copy relationship in which one of the conduit LSS volumes serves as a primary volume. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). Example: IBM.1750-68FA120/00 -seqnum flash_sequence_number (Optional) Specifies that the commit operation is performed only on those source volumes that are associated with the specified sequence number. This parameter is not supported for machine type 2105. Example: 0010 -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. When this parameter is used, all source volumes must be within the same logical subsystem. This parameter is required only for IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: FF10 SourceVolumeID . . . | (Required) Commits remote FlashCopy relationships for the source volumes with the specified IDs. The chosen pair is the one with the enabled -record parameter. You must separate multiple source volume IDs with spaces.
438
This parameter accepts fully qualified volume IDs, which includes the storage image ID, or a shortened version without the storage image ID if either the -dev parameter is specified, or you can specify a value for the devid variable in your profile file. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified volume ID: IBM.1750-68FA120/0001 Example of a shortened version: 0001 Example of IDs: 0001 0003 0008
Example (1750)
Invoking the commitremoteflash command
dscli>commitremoteflash -conduit IBM.1750-68FA150/10 IBM.1750-68FA120/0100

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy pair IBM.1750-68FA120/0100:IBM.1750-68FA120/0200 successfully committed.
resyncremoteflash
The resyncremoteflash command (formerly called the incremoteflash command and associated with the incremental FlashCopy process) increments an existing remote FlashCopy pair that has been established with the -record and -persist parameters.
resyncremoteflash -dev storage_image_ID -conduit LSS_ID -record
-persist
-freeze
-tgtpprc
-tgtoffline
-tgtinhibit
-seqnum
flash_sequence_num
-srcss
SS_ID
Parameters
Note: When a pair is established with the -record and -persist parameters, the pair initially synchronizes and then a record of all data that is written from the host to the source is maintained in the source volumes. When the resyncremoteflash command is issued on the pair, the new data that is written to the source is copied to the target. The specified parameters in this command replace the parameters in the existing relationship. In order to
439
keep the initial -record and -persist parameter values, the -record and -persist parameters must be specified using the resyncremoteflash command. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy relationship that is to be used as a means for communicating with the remote storage image. The source volume IDs that are specified in the SourceVolumeID:TargetVolumeID parameter, must serve as secondary volumes in a Remote Mirror and Copy relationship in which one of the conduit LSS volumes serves as a primary volume. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). Example: IBM.1750-68FA120/00 -record (Optional) Specifies that the changed tracks on both volumes within a FlashCopy pair be recorded. Select this parameter if you intend to use the resyncremoteflash command again with this pair. The -persist parameter is automatically set in the code when the -record parameter is specified. -persist (Optional) Specifies that the FlashCopy relationship be retained after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until you issue a rmremoteflash command. This parameter is automatically set in the code when the -record parameter is specified. Specify this parameter along with the -record parameter if you intend to use this volume pair with the resyncremoteflash, reverseremoteflash, or setremoteflashrevertible commands. -freeze (Optional) Specifies the Freeze Consistency Group condition. This option causes the source volume to be busy (Queue Full status on Open Systems) to all host I/O operations until a FlashCopy Consistency Group Created command is received. All writes to the source volume are queued by the host and are written after the Consistency Group Created command is complete. During the busy condition, the source volume reports Queue Full for fixed block volumes and busy status for CKD volumes. The busy condition can also be reset by an extended long busy timeout (default 120 seconds). The timeout condition affects all FlashCopy source volumes that are contained within a respective logical subsystem and that are established or modified with the -freeze parameter. Note: This parameter is used in conjunction with other processing steps for purposes such as backups, testing, or recovery solutions. The use of this parameter ensures that volumes on the target LSSs are consistent with the source LSSs volumes.
440
-tgtpprc (Optional) Allows the FlashCopy target volume to be a remote mirror and copy source volume. -tgtoffline (Optional) Causes the resyncremoteflash command to be rejected if the target volume is online for host system access. Note: This parameter applies only to count key data volumes. -tgtinhibit (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relationships that are established with the specified sequence number. You can use this sequence number as an identifier for a relationship or group of relationships. Only the relationships that are modified successfully by the resyncremoteflash command are assigned the specified sequence number, leaving the ones that fail with the previous one (if they were previously specified). This parameter is not supported for machine type 2105. Example: 0010 -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The subsystem ID is a four-digit hexadecimal number in the range (0001 - FFFF). When this parameter is used, all source volumes must be designated within the same logical subsystem. This parameter is required for IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: FF10 | | | | | | | | | | | | | | | | | | | | SourceVolumeID:TargetVolumeID . . . | (Required) Specifies that a remote FlashCopy relationship for the source and target volume pairs be incremented with the designated IDs. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified, A FlashCopy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004
441
Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the resyncremoteflash command
dscli>resyncremoteflash -conduit IBM.1750-68FA150/10 IBM.1750-68FA120/0100:IBM.1750-68FA120/0200
| | | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote FlashCopy volume pair 0100:0200 successfully resynchronized. Use the lsremoteflash command to determine copy completion.
Note: This message is returned before the copy completes.
lsremoteflash
The lsremoteflash command displays a list of FlashCopy relationships and status information for each FlashCopy relationship in the list.
lsremoteflash -dev storage_image_ID -conduit LSS_ID -s -l -activecp
-record
-persist
-revertible
-cp
-state
valid invalid validation-required volume-inaccessible tgt-failed not-valid path-unavailable
-seqnum
flash_sequence_num
-srcss
SS_ID
Parameters
Note: All settings apply to all FlashCopy pairs that are specified. | | | | | -dev storage_image_ID (Optional) Specifies the storage image ID, which consists of manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes or you do not specify a value for the devid variable in your profile file. -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing Remote Mirror and Copy relationship that is used as a means for communicating with the remote storage image.
442
The source volume IDs that are specified in the SourceVolumeID:TargetVolumeID parameter must serve as secondary volumes in a Remote Mirror and Copy relationship in which one of the conduit LSS volumes serves as a primary volume. This parameter accepts a fully qualified LSS ID, which includes the storage image ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). -s -l (Optional) Specifies that FlashCopy pair IDs be displayed. You cannot use the -l and the -s parameters together. (Optional) Specifies that the default detailed output plus Out-of-Sync Tracks and Date Created information be displayed. You cannot use the -l and the -s parameters together.
-activecp (Optional) Specifies that FlashCopy relationships where their background copy process is active be displayed. -record (Optional) Specifies that the FlashCopy relationships that were established with the -record parameter be displayed. -persist (Optional) Specifies that the FlashCopy relationships that were established with the -persist parameter be displayed. -revertible (Optional) Specifies that the FlashCopy relationships that were established with the -revertible parameter be displayed. -cp (Optional) Specifies that the FlashCopy relationships that were established with the run background copy (-cp) parameter be displayed. -state valid | invalid | validation-required | volume-inaccessible | tgt-failed | not-valid | path-unavailable (Optional) Displays the FlashCopy relationships that are identified by the specific state. Note: When you specify not-valid, all FlashCopy relationships that do not meet the requirements of the valid state are displayed. -seqnum flash_sequence_number (Optional) Specifies that the FlashCopy relationships that are associated with the specified sequence number be displayed. This parameter is not supported for machine type 2105. -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The ID is in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. When you specify SS_IDs, the source volumes are restricted to one LSS. Example: FF10 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies that the FlashCopy relationships for the source and target volume pairs with the specified IDs be displayed.
443
This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. You must separate multiple IDs with spaces. You can specify FlashCopy pair IDs and a range of FlashCopy pair IDs, or you can specify volume IDs and a range of volume IDs. You cannot specify a combination of FlashCopy pair IDs and volumes IDs. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified volume ID pair: IBM.1750-75FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsremoteflash command using the -l parameter. A separate example is not shown for the 1750 as the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the lsremoteflash command
dscli>lsremoteflash -l -dev IBM.2107-75FA120 -conduit IBM.2107-75FA150/10 IBM.2107-75FA120/0100:IBM.2107-75FA120/0200

Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Sequence Num 10 Active Copy Disabled
ID 0100:0200
SrcLSS 01
Recording Disabled
Persistent Disabled
Revertible Disabled
CopyIndicator Yes
OutOfSyncTracks 0
DateCreated 12/01 /2003 02:20:00
DateSynced 12/01 /2003 02:23:47
State Valid
444

ID Specifies the FlashCopy pair ID. The FlashCopy pair ID consists of two volume IDs. One is designated as the source and the other is the target volume for a FlashCopy relationship. Specifies the logical subsystem ID. Sequence Num Specifies the sequence number that is associated with the FlashCopy relationship. ActiveCopy Specifies (enabled or disabled) whether the background copy is active on the specified FlashCopy pair. Recording Specifies (enabled or disabled) whether the designated FlashCopy pair is established with recording activated. Persistent Specifies (enabled or disabled) whether the designated FlashCopy pair is established with persistent activated. Revertible Specifies (enabled or disabled) whether the designated FlashCopy pair is established with the revertible option activated. SourceWriteEnabled Specifies (enabled or disabled) whether or not this FlashCopy relationship was established with the Allow Source Writes option. TargetWriteEnabled Specifies (enabled or disabled) whether this FlashCopy relationship was established with the Allow Target Writes option Background Copy Specifies (enabled or disabled) whether this FlashCopy relationship was established with the Run Background Copy option. OutofSync Tracks Specifies the number of tracks that are not synchronized for this FlashCopy relationship. DateCreated Specifies the date and the time that the FlashCopy relationship was established. DateSynced Specifies the date and the time that this FlashCopy relationship was synchronized, or null (-) if the relationship is not synchronized. State Specifies the state of the FlashCopy relationships. One of the following values is displayed for each FlashCopy relationship: Note: When a query indicates any state other than valid, the only information that is displayed on the report is the FlashCopy pair ID and the state condition. The rest of the information columns are displayed with a null (-) value. Valid Indicates that the FlashCopy relationship is in a normal state, and that it has been queried successfully.
SrcLSS
445
Validation Required Indicates that the FlashCopy relationship cannot be queried. Generally, the reason that the query is blocked is only temporary. If you issue a new query within several seconds, the problem no longer exists. Tgt Failed Indicates that the FlashCopy relationship is in an error state. The point-in-time copy is lost, and the FlashCopy relationship must be withdrawn. You must issue the rmflash command to remove the FlashCopy relationship. Volume Inaccessible Indicates that the volume cannot be accessed and that the query has failed. When this state is displayed, it generally means that the volume is in a fenced condition. Invalid Indicates that a general internal error has occurred when the query is processed. Path Unavailable The specified inband path does not exist. The user should verify that the Remote Mirror and Copy pair exists.
mkremoteflash
The mkremoteflash command initiates a remote point-in-time copy from source volumes to target volumes through a Remote Mirror and Copy relationship.
mkremoteflash -dev storage_image_ID -conduit LSS_ID -tgtpprc
-tgtoffline
-tgtinhibit
-freeze
-record
-persist
-nocp
-seqnum
flash_sequence_num
-srcss
SS_ID
Parameters
| | | | | -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes or you do not specify a value for the devid variable in your profile file. -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy relationship that is to be used as a conduit for communicating with the remote storage image. The source volume IDs that are specified in the SourceVolumeID:TargetVolumeID parameter, must serve as secondary volumes in a remote mirror and copy relationship in which one of the conduit LSS volumes serves as a primary volume.
446
The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). Example: IBM.1750-68FA120/00 -tgtpprc (Optional) Allows the FlashCopy target volume to be a remote mirror and copy source volume. -tgtoffline (Optional) Causes the mkremoteflash command to be rejected if the target volume is online for host system access. This parameter applies only to CKD volumes. -tgtinhibit (Optional) Prevents host system write operations to the target while the FlashCopy relationship exists. -freeze (Optional) Specifies the Freeze Consistency Group condition. The use of this parameter triggers the queue full condition for the source volume. All writes to the source volume are queued by the host and are written after the queue full condition is reset. During the queue full condition, the source volume reports long busy status. The queue full condition is reset by an extended long busy timeout. The timeout condition affects all FlashCopy source volumes that are contained within a respective logical subsystem and that are established or modified with the -freeze parameter. Note: This parameter is used in conjunction with other processing steps for purposes such as backups, testing, or recovery solutions. The use of this parameter ensures that volumes on the target LSSs are consistent with the source LSSs volumes. -record (Optional) Specifies that the changed tracks on both volumes within a FlashCopy pair be recorded. Select this parameter if you intend to use the resyncremoteflash command again with this pair. The -persist parameter is automatically selected when the -record parameter is specified. -persist (Optional) Specifies that you want to retain the FlashCopy relationship after the background copy completes. The FlashCopy relationship between the source and the target volumes remains indefinitely until you issue a rmremoteflash command. This parameter is automatically selected when the -record parameter is specified. Specify this parameter along with the -record parameter if you intend to use this volume pair with the resyncremoteflash, reverseremoteflash, or setremoteflashrevertible commands. -nocp (Optional) Inhibits background copy. Data will be copied from the source volume to the target volume only if a track on the source volume is modified. The FlashCopy volume pair relationship remains indefinitely until it is broken by a rmremoteflash command, or until all tracks on the source volume are modified. -seqnum flash_sequence_num (Optional) Associates the FlashCopy relationships that are established with the
447
specified sequence number. This sequence number can be used as an identifier for a relationship or group of relationships. Example: 0010 This parameter is not supported for machine type 2105. -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The ID is in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. When you specify SS_IDs, the source volumes are restricted to one LSS. Example: FF10 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies that a remote FlashCopy relationship for the source and target volume pairs be incremented with the designated IDs. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified, A FlashCopy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-68FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the mkremoteflash command
dscli>mkremoteflash -dev IBM.1750-68FA120 -conduit IBM.1750-68FA150/10 0100:0200

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 FlashCopy volume pair 0100:0200 successfully created. Use the lsremoteflash command to determine copy completion.
revertremoteflash
The revertremoteflash command is used to restore data on the source volume to its most recent consistency formation. All new write operations to the source since the most recent consistency formation are overwritten with the previous consistency.
448
revertremoteflash -dev storage_image_ID
-conduit
LSS_ID
SourceVolumeID -seqnum flash_sequence_num -srcss SS_ID - . . .
Parameters
You must take the following actions before you can use the revertremoteflash command: Notes: 1. Issue the mkflash or mkremoteflash command with the -persist and -record parameters to establish the FlashCopy pair. 2. Issue the setflashrevertible or setremoteflashrevertible command against the FlashCopy pair. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source volume or you do not specify a value for the devid variable in your profile file. -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy (formerly PPRC) relationship that is used as a means for communicating with the remote storage image. The source volume IDs that are specified in SourceVolumeID:TargetVolumeID must serve as secondary volumes in a remote mirror and copy relationship in which one of the conduit LSS volumes serves as a primary volume. This parameter accepts a fully qualified LSS ID, which includes the storage image ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range00 - 1F (1750 only). Example: IBM.2107-75FA120/00 Example: IBM.1750-68FA120/00 -seqnum flash_sequence_num (Optional) When a FlashCopy sequence number is specified, the revertremoteflash operation is performed only on those relationships that are associated with the specified number. Example: 0010 This parameter is not supported for machine type 2105. -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The ID is in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. 3. When you specify SS_IDs, the source volumes are restricted to one logical subsystem. Example: FF10 SourceVolumeID . . . | (Required) Specifies the remote FlashCopy relationship for the source volume
449
with the specified ID that is to be reverted. The chosen FlashCopy pair is the one that is established or modified with the -record parameter. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple source volume IDs with spaces. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a shortened version: 0001 Example of multiple IDs: 0001 0003 0008
Example (1750)
Invoking the revertremoteflash command
dscli>revertremoteflash -dev IBM.1750-68FA120 -conduit IBM.1750-68FA150/10 0100
| | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote FlashCopy volume pair 0100:0200 successfully reverted.
rmremoteflash
The rmremoteflash command removes a relationship between remote FlashCopy volume pairs.
rmremoteflash -dev storage_image_ID -conduit LSS_ID -quiet -tgtonly
-cp
-seqnum
flash_sequence_number
-srcss
SS_ID
Parameters
Notes: 1. Invoking this command and using the -cp parameter on a FlashCopy relationship that was previously marked with the -persist parameter does not remove the relationship. Instead, the source volume is copied to the target volume. 2. Invoking this command resets the -tgtinhibit parameter option if it was previously set. 3. All settings apply to all specified FlashCopy pairs. 4. The -seqnum parameter is not supported for model 2105.
450
5. When SS_IDs are specified, the source volumes are restricted to 1 LSS. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes or you do not specify a value for the devid variable in your profile file. -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy (formerly PPRC) relationship that is to be used as a means for communicating with the remote storage image. The source volume IDs that are specified in SourceVolumeID:TargetVolumeID must serve as secondary volumes in a remote mirror and copy relationship in which one of the conduit LSS volumes serves as a primary volume. This parameter allows the use of a fully qualified LSS ID, which includes the storage image ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). -quiet (Optional) Turns off the confirmation prompt for this command. -tgtonly (Optional) Specifies only the target volume of the remote FlashCopy pair that you want to remove. In addition, the Copy Indicator for the target volume is reset. Note: You can use this parameter only with fixed block volumes. -cp (Optional) Specifies that the FlashCopy relationship be changed from the No Copy to the Copy mode. Additionally the remaining source volume tracks are copied to the target volume. The relationship is removed when all the data is copied unless the relationship is persistent. When the -cp parameter is specified, the copy is processed for all volume pairs where the source volume ID is identical to the source volume that is specified in the command. -seqnum flash_sequence_num (Optional) When a FlashCopy sequence number is specified, the rmremoteflash operation is performed only on those relations that are associated with the specified number. Example: 0010 This parameter is not supported for machine type 2105. -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The ID is in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. 4. When you specify SS_IDs, the source volumes are restricted to one logical subsystem. Example: FF10 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies the remote FlashCopy relationships for the source and target volume pairs with the specified IDs that are to be removed.
451
This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple FlashCopy pair IDs with spaces. A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. When you use the -tgtonly parameter, enter volume IDs. Volume pair IDs cannot be used with the -tgtonly parameter. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-75FA120/ 0001:IBM.1750-68FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the rmremoteflash command
dscli>rmremoteflash -dev IBM.1750-68FA120 -conduit IBM.1750-68FA150/10 0100:0200
| | | | | | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to remove the FlashCopy pair 0100:0200? [y/n]: Y Removal of the remote FlashCopy volume pair 0100:0200 has been initiated successfully. Use the lsremoteflash command to determine when the relationship is deleted.
setremoteflashrevertible
The setremoteflashrevertible command modifies a remote FlashCopy volume pair that is part of a Global Mirror relationship to revertible. This command must be run before the FlashCopy pair can be committed or reverted. Once a pair is revertible, the data can be committed to the target to form a new consistency, or reverted back to the last consistency.
setremoteflashrevertible -dev storage_image_ID -conduit LSS_ID -tgtoffline
-seqnum
flash_sequence_num
-srcss
SS_ID
452
Parameters
Note: The -nocp, -record, -persist, and -tgtinhibit (target inhibit) parameters that were specified when the FlashCopy pair was made (mkremoteflash command) are included automatically when the setremoteflashrevertible command processes. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source volume or you do not specify a value for the devid variable in your profile file. -conduit LSS_ID (Required) Specifies the source logical subsystem (LSS) of an existing remote mirror and copy (formerly PPRC) relationship that is to be used as a passage for communicating with the remote storage image. The source volume IDs that are specified in SourceVolumeID:TargetVolumeID must serve as secondary volumes in a remote mirror and copy relationship in which one of the passage LSS volumes serves as a primary volume. Accepts a fully qualified LSS ID, which includes the storage image ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range 00 - 1F (1750 only). -tgtoffline (Optional) Causes an establish FlashCopy volume pair command to be rejected if the target volume ID is online for host system access. This parameter applies only to CKD volumes. -seqnum flash_sequence_num (Optional) Associates the remote FlashCopy relationships that are changed with the specified sequence number. Only the relationships that are successfully modified by the command get the specified sequence number, leaving the ones that failed with the previous number (if previously specified). Example: 0010 This parameter is not supported for machine type 2105. -srcss SS_ID (Optional) Specifies the subsystem ID of the source logical subsystem at the remote site. The ID is in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: FF10 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies that the remote FlashCopy relationships for the designated source and target volume pairs be modified. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple FlashCopy pair IDs with spaces.
453
A FlashCopy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a FlashCopy relationship. You must separate the two volume IDs of a FlashCopy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified FlashCopy pair ID: IBM.1750-75FA120/ 0001:IBM.1750-75FA120/0004 Example of a shortened version: 0001:0004 Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking the setremoteflashrevertible command
dscli>setremoteflashrevertible -dev IBM.1750-68FA120 0100:
| | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote FlashCopy pair 0100:0200 successfully made revertible.
Remote Mirror and Copy path commands

This section contains commands that create and delete Remote Mirror and Copy (formerly PPRC) paths and display Remote Mirror and Copy path information. Use the following commands to create and delete Remote Mirror and Copy paths and to display Remote Mirror and Copy path information: v lsavailpprcport v v v v lspprcpath mkesconpprcpath mkpprcpath rmpprcpath
The lsavailpprcport command generates a report that displays a list of ESCON or fibre-channel I/O ports that can be defined as Remote Mirror and Copy paths. The lspprcpath command generates a report that displays a list of existing Remote Mirror and Copy path definitions. The mkesconpprcpath command creates a Remote Mirror and Copy path between source and target logical subsystems over an ESCON connection. The mkpprcpath command establishes or replaces a Remote Mirror and Copy path between source and target logical subsystems (LSSs) over a fibre-channel connection.
454
The rmpprcpath command deletes one or more specified Remote Mirror and Copy paths.
lsavailpprcport
The lsavailpprcport command displays a list of ESCON or fibre-channel I/O ports that can be defined as remote mirror and copy (formerly PPRC) paths. The DS6000 supports only fibre-channel ports. The Enterprise Storage Server (2105 machine type) supports ESCON ports.
lsavailpprcport -dev storage_image_ID -remotewwnn wwnn -s -l
-remotedev
storage_image_ID
Source_LSS_ID:Target_LSS_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the source volume storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source logical subsystem. Example: IBM.1750-68FA120 -remotewwnn wwnn (Required). Specifies the worldwide node name (WWNN). The format is a 16-hexadecimal ID. Note: You want to use the WWNN that is associated with the remote storage image. Run the lssi or showsi command to obtain this number. If you use the WWNN that is associated with the primary storage unit, this command fails. WWNN example: 12341234000A000F -s -l (Optional). Displays the local port ID. You cannot use the -l and the -s parameters together. (Optional). Displays all fields. You cannot use the -l and the -s parameters together.
-remotedev storage_image_ID (Required or Optional). Specifies the remote storage unit that contains the I/O ports that are queried by the Source_LSS_ID:Target_LSS_ID parameter. The remotedev ID consists of the value for the manufacturer, machine type, and serial number. Required - This parameter is required when querying ESCON I/O ports unless a fully qualified target logical subsystem ID is specified. Optional - This parameter is optional if you are querying fibre channel I/O ports. Note: If specified the format of this entry might be checked for correctness even though the value is not used. Example: IBM.1750-68FA120
455
Source_LSS_ID:Target_LSS_ID | (Required). Queries I/O ports that are available for a remote mirror and copy path relationship for the source and target LSSs. This parameter accepts fully qualified LSS IDs, which includes the storage image ID or shortened version without the storage image ID, if the -dev parameter is specified. A remote mirror and copy path LSS pair ID consists of two LSS IDs, one designated as the source LSS and the other as the target LSS for a remote mirror and copy path relationship. The two LSS IDs must be separated with a colon and no spaces. The first LSS ID is the source LSS. The second LSS ID is the target LSS. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range 00 - 1F (1750 only). For example, IBM.1750-68FA120/01:IBM.1750-68FA150/01 If you do not use the -dev and -remotedev parameters, the fully qualified source_LSS_ID:target_LSS_ID value must be placed after the -remotewwnn value in your command line. For example, your command line would look like the following:
If you specify the dash (-), this parameter information is automatically supplied. Example pair: 00:00 Example of multiple pairs: 00:00 01:01 02:02
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lsavailpprcport command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the lsavailpprcport command
dscli>lsavailpprcport l dev IBM.2107-75FA120 remotewwnn 12341234000A000F 01:01
The resulting output ESCON port information displays for the 2105 machine type.
Local port I0100 I0150 I0200 I0250 Attached port I0200 I0620 N/A N/A Type FCP ESCON ESCON Switch ESCON Switch Switch ID N/A N/A IBM.111.2222. 75113AB IBM.111.2222. 75113AB Switch port N/A N/A I10 I20
456

Local port Specifies the fully qualified unique Port ID on the local storage unit. FCP and ESCON port IDs are displayed as follows: FCP port ID Four hexadecimal characters in the format 0xEEAP, where EE is a port enclosure number (00 - 3F), A is the adapter number (0 - F), and P is the port number (0 - F). The FCP port ID number is prefixed with the letter I. ESCON port ID Four hexadecimal characters in the format 0xEEAP, where EE is a port enclosure number (04 - 07), A is the adapter number (0 - 3), and P is the port number (0 - 1). The ESCON port ID number is prefixed with the letter I. Note: When you specify the -s parameter, the local port information is the only information displayed on the report. Attached port Specifies the fully qualified unique Port ID on the attached storage unit. FCP and ESCON port ID numbers are displayed in the format that is described for Local port. However, if there is an ESCON Switch value, the value displayed in this column is N/A (not applicable). Type Specifies the connection type. FCP is the only applicable value for a 2107 or 1750 machine type. For a 2105 machine type, you can have a value of ESCON or ESCON Switch.
Switch ID Specifies the Switch ID for ESCON Switch connections. Note: For FCP and direct ESCON, the displayed value in this field is N/A (not applicable). Switch port Specifies the Port ID on the Switch device that is connected to the attached ESS. The Switch port ID component is two hexadecimal characters in the format 0xPP, where PP is a port number (00 - ff). The number is prefixed with the letter I. Note: For FCP and direct ESCON, the value of this field is N/A (not applicable).
lspprcpath
The lspprcpath command displays a list of existing Remote Mirror and Copy (formerly PPRC) path definitions. |
lspprcpath -dev storage_image_ID -s -l Source_LSS_ID . . . -
| | | |
Parameters
-dev storage_image_ID (Optional) Specifies the storage image ID, which consists of values for the
457
| | | | | | | -s -l
manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source LSS ID. Example: IBM.1750-68FA120 (Optional) Displays the default output of the report but does not include the Failed Reason column. You cannot use the -l and the -s parameters together. (Optional) Displays the default output and the Failed Reason descriptions. You cannot use the -l and the -s parameters together.
Source_LSS_ID . . . | (Required) Specifies that the Remote Mirror and Copy paths that are defined for the specified source LSS IDs be displayed. This parameter accepts either a fully qualified LSS ID, including the storage image ID, or a shortened version if the -dev parameter is specified. The fully qualified LSS ID format is storage_image_id/xx, where xx is a logical subsystem (LSS) hexadecimal number 00 - 1F (for 1750). You must separate multiple LSS IDs with spaces. If you specify the dash (-), this parameter information is automatically supplied. Example: 00 Example of multiple source LSS IDs: 00 01 02
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. | | | | | | | The following tables represent the headers that are displayed on the output report when the -l parameter is used with the lspprcpath command. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the lspprcpath command
dscli>lspprcpath -dev IBM.2107-75FA120 -l 10

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Src IBM.2107 -75FA120 /10 IBM.2107 -75FA120 /10 IBM.2107 -75FA120 /10 IBM.2107 -75FA120 /10 Tgt IBM.2107 -75FA150 /10 IBM.2107 -75FA150 /11 IBM.2107 -75FA150 /12 IBM.2107 -75FA150 /13 State Failed SS 0010
Success
0011
Success
0012
Invalid
0013
458
| | | | | | | | | | | | | | | |
Port IBM.2107 -75FA120 /I0100 IBM.2107 -75FA120 /I0100 IBM.2107 -75FA120 /I0100 IBM.2107 -75FA120 /I0100
Attached Port IBM.2107 -75FA150 /I0100 IBM.2107 -75FA150 /I0100 IBM.2107 -75FA150 /I0100 IBM.2107 -75FA150 /I0100
Tgt WWNN 3007ACF 3012399E0 3007ACF3012399E0 3007ACF3012399E0 3007ACF3012399E0
Failed Reason Configur ation Error -

Src Tgt | | | | | | | | | | SS Port State Specifies the fully qualified logical subsystem ID. Specifies the fully qualified Remote Mirror and Copy ID for the path target LSS. Displays the current Remote Mirror and Copy path state. One of the following values can be displayed: Failed The transaction failed for one of the specified reasons. See the Failed Reason column for an explanation. Success The transaction was a success. When this is the State value, the Failed Reason code displays a null (-) value. Invalid The transaction was not valid. When this is the State value, the Failed Reason code displays a null (-). Specifies the subsystem identifier (SSID) of the target LSS. Specifies the fully qualified unique Port ID for the source storage unit. The port ID component is four hexadecimal characters in the format EEAP, where EE is a port enclosure number (00 - 3F), A is the adapter number (0 - F), and P is the port number (0 - F). The number is prefixed with the letter I. Attached Port Specifies the fully qualified unique Port ID for the attached secondary storage unit. The port ID component is four hexadecimal characters in the format 0xEEAP, where EE is a port enclosure number (00 - 3F), A is the adapter number (0 - F), and P is the port number (0 - F). The number is prefixed with the letter I. Tgt WWNN Specifies the worldwide node name of the remote storage image. | | | Failed Reason Displays the reason for a failed transaction. One of the following values can be displayed:
459
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Configuration error A path has failed. Delete the original entry and resubmit the mkpprcpath command. Down An FCP path has failed because of a communication or hardware failure. FCP source login exceeded The maximum number of log ins for each source FCP path has been exceeded. Retry exceeded The maximum number of times that the storage unit tried to reestablish FCP paths has been exceeded. FCP target login exceeded The maximum number of logins for each FCP path to the target LSS has been exceeded. The FCP target is unavailable. FCP target unavailable An FCP path to the target LSS is unavailable. None The path has no state.
Source no resources No resources are available at the source site for the logical paths to be established. Retry Specifies the number of attempts to reestablish path connection.
Target mismatch There is a target (remote) site system adapter ID mismatch. Target no resources Resources are not available at the target (remote) site to establish the logical paths. Target LSS mismatch The sequence number of the storage unit at the target site does not match the number of the target LSS. Reserved Not available for use at this time. Timeout A timeout has occurred. No reason is available. Unknown The state of the path is unknown. Path Degraded Due to High Failure Rate Indicates that a fibre channel path is established; however, because of the high failure rate, the path is degraded. Path Removed Due to High Failure Rate Indicates that the fibre channel path link has been removed because the path has experienced a high failure rate.
mkesconpprcpath
The mkesconpprcpath command creates a remote mirror and copy (formerly PPRC) path between source and target logical subsystems over an ESCON connection. The command allows you to specify ESCON direct and ESCON switch connections. Use this command only with IBM System Storage Enterprise Storage Servers (2105, Model 800 and Model 750).
460
mkesconpprcpath -dev storage_image_ID Source_LSS_ID -srcss ss_ID -remotedev storage_image_ID -tgtlss Target_LSS_ID
-srclss -remotewwnn WWNN
Source_Port_ID:Target_Port_ID -tgtss ss_ID -consistgrp -force - . . .
Parameters
Notes: 1. The mkesconpprcpath command is applicable only for the IBM System Storage Enterprise Storage Server (2105, Model 800 and Model 750). Models 2107 and 1750 support only fibre-channel connections. 2. When you specify a switch port ID as the target port, specify the outgoing port that is connected to the remote ESS and not to the incoming port that is connected to the local ESS. -dev storage_image_ID (Optional). Specifies the source storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not fully qualify the source LSS ID. Example: IBM.2105-75FA120 -remotedev storage_image_ID (Optional). Specifies the remote storage image ID, which consists of manufacturer, type, and serial number. This parameter is required if you do not fully qualify the target LSS ID. Example: IBM.2105-75FA150 -srclss Source_LSS_ID (Required). Specifies the source logical subsystem (LSS) ID. Accepts a fully qualified LSS ID, which includes the storage image ID or a shortened version without the storage image ID, if the -dev parameter is used. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range 00 - FE. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtlss Target_LSS_ID (Required). Specifies the target logical subsystem (LSS) ID. Accepts a fully qualified LSS ID, which includes the storage image ID, or a shortened version without the storage image ID, if the -remotedev parameter is used. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range 00 - FE. -remotewwnn WWNN (Optional). Specifies the worldwide node name. The format is a 16-hexadecimal ID.
461
Note: If you use this parameter, the format is checked even though there might be times that the value is not used. Example: 12341234000A000F -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -consistgrp (Optional). Creates a consistency group for the remote mirror and copy volume pairs that are associated with the PPRC paths that are established by this command. A remote mirror and copy consistency group is a set of remote mirror and copy volume pairs that have the same source and target LSS. Normally, when an error occurs in a member of a remote mirror and copy volume pair, the volume is put in a suspended state. However, if the volume is participating in a consistency group, it is placed in a long busy state. -force (Optional). Creates a new remote mirror and copy path even if the specified remote mirror and copy path already exists. Source_Port_ID:Target_Port_ID . . . | (Required). Establishes a remote mirror and copy path between the source and target ports for the specified source and target logical subsystems. The source port must be an ESCON I/O port that is configured for point-to-point or switch topology. The source port is enabled automatically for remote mirror and copy primary I/O operations. The target port must be a switch I/O port that is configured for point-to-point or switch topology. The target port is enabled automatically for remote mirror and copy primary I/O operations. Note: Do not specify a target port ID when you specify an ESCON direct connection. Instead, specify only the source port ID. This parameter accepts only nonfully qualified port IDs, which does not include the storage image ID. A remote mirror and copy path port pair ID consists of two port IDs. The first is designated as the source port and the second as the target port for the remote mirror and copy path. You must separate the two port IDs with a colon and no spaces. A direct ESCON I/O port ID is four hexadecimal characters in the format EEAP, where EE is a port enclosure number 00 - 3F, A is the adapter number 0 - F, and P is the port number 0 - F. This number is prefixed with the letter I. A switch ESCON I/O port ID is two hexadecimal characters in the range 00 - FF. This number is prefixed with the letter I. This parameter accepts up to eight remote mirror and copy path port pair IDs. You must separate multiple port pair IDs with spaces. If you specify the dash (-), this parameter information is automatically supplied. Example pair: I1A10:I20 Example of a source ESCON port and target switch port pair: I1A10:I20
462
Example of multiple pairs: I1A10:I20 I1A11:I21 I1A12 (the last object identifies an ESCON connection)
Example (2105 use only)

Invoking the mkesconpprcpath command
dscli>mkesconpprcpath -dev IBM.2105-75FA120 -remotedev IBM.2105-75FA150 -srclss 01 -tgtlss 01 I0100:I20 I0110:I21

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2105-75FA120 Remote Mirror and Copy path IBM.2105-75FA120/01:IBM.2105-75FA150/01 successfully created.
mkpprcpath
The mkpprcpath command establishes or replaces a remote mirror and copy (formerly PPRC) path between source and target logical subsystems (LSSs) over a fibre-channel connection. This is the only supported connectivity for machine types 2107 and 1750. Paths can be established between the following machine types: 2105:2105, 2107:2107, 2107:1750, 2107:2105, 1750:1750, 1750:2105.
mkpprcpath -dev -remotewwnn wwnn storage_image_ID -srclss source_LSS_ID -srcss SS_ID -remotedev storage_image_ID -tgtlss target_LSS_ID
source_port_ID:target_port_ID -tgtss SS_ID -consistgrp - . . .
Parameters
-dev storage_image_ID (Optional) Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source port ID. -remotedev storage_image_ID (Optional) Specifies the ID of the secondary storage image, which includes manufacturer, machine type, and serial number. If specified, the format of this entry might be checked for correctness although the value is not used Example: IBM.1750-68FA150 -remotewwnn wwnn (Required) Specifies the worldwide node name of the secondary storage image. The format is a 16-hexadecimal ID. Note: Ensure that you use the worldwide node name that is associated with the secondary storage unit. Run the lssi or showsi command to obtain this number. Example: 12341234000A000F -srclss source_LSS_ID (Required) Specifies the source logical subsystem ID. Use a fully qualified LSS
463
ID, which includes the storage image ID, or use a shortened version without the storage image ID, if the -dev parameter is used. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range (1750) 00 - 1F. Example of a shortened version: 00 -srcss SS_ID (Optional) Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM TotalStorage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtlss target_LSS_ID (Required) Specifies the logical subsystem ID associated with the secondary storage unit as the target. Use a fully qualified LSS ID, which includes the storage image ID. The fully qualified LSS ID format is storage_image_ID/XX, where XX is a hexadecimal number in the range (1750) 00 - 1F. Example of a shortened version: 01 -tgtss SS_ID (Optional) Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM TotalStorage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -consistgrp (Optional) Creates a consistency group for the remote mirror and copy volume pairs. A remote mirror and copy consistency group is a set of remote mirror and copy volume pairs that have the same source and target LSS. Normally, when an error occurs in a member of a remote mirror and copy volume pair, the storage unit places the volume in a suspended state. However, if the volume participates in a consistency group, it is placed in a long busy state. source_port_ID:target_port_ID . . . | (Required) Establishes a remote mirror and copy path between the source and target ports for the specified source and target logical subsystems. The source and target ports must be fibre-channel I/O ports that are configured for point-to-point or switched fabric topology. They are enabled automatically for remote mirror and copy secondary I/O operations. They are not enabled for FICON I/O operations. Use fully qualified port IDs, which includes the storage image ID, or use a shortened version without the storage image ID if the -dev parameter is specified. A remote mirror and copy path port pair ID consists of two port IDs. Designate the first as the source port and the second as the target port for the remote mirror and copy path. You must separate the two port IDs with a colon and no spaces. A port ID is four hexadecimal characters in the format EEAP, where EE is a port enclosure number (00 - 3F), A is the adapter number (0 - F), and P is the port number (0 - F). This number is prefixed with the letter I. This parameter accepts up to eight remote mirror and copy path port pair IDs. You must separate multiple port pair IDs with spaces.
464
If you specify a dash (-), this parameter information is automatically supplied. Example of the shortened version: I1A10:I2A20 Example of multiple pairs: I1A10:I2A20 I1A11:I2A21 I1A12:I2A22
Example (1750)
Invoking the mkpprcpath command
dscli>mkpprcpath -dev IBM.1750-68FA120 -srclss 01 -tgtlss 01 remotewwnn 12341234000A000F I0100:I0100

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror and Copy path 01:01 successfully established.
rmpprcpath
The rmpprcpath deletes a Remote Mirror and Copy path.
rmpprcpath -dev storage_image_ID -remotedev storage_image_ID
remoteWWNN WWNN
-type
fcp
-quiet
-force
source_LSS_ID:target_LSS_ID . . . -
Parameters
-dev storage_image_ID (Optional) Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source LSS ID or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional) Specifies the target storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified target LSS ID or if the -dev parameter is used. -remoteWWNN WWNN (Optional) Specifies the secondary worldwide node name. Note: The following considerations can help you decide whether to use this parameter: v If you do not specify this parameter, DS CLI processing requires a query for this information from the remote device. In some cases, due to the path-specific state, the query might fail to locate the remote WWNN. If the remote WWNN cannot be located, the rmpprcpath command fails. Process the lspprcpath command to obtain the remote WWNN information and then process the rmpprcpath command with the remote WWNN information included.
465
v Use the lspprcpath command to obtain the remote WWNN information. -type fcp (Optional) The type of the connection over which the path was created. fcp Fibre-channel protocol
-quiet (Optional) Turns off the confirmation prompt for this command. -force (Optional) Specifies that you want to remove Remote Mirror and Copy paths even if Remote Mirror and Copy volume pairs exist. Otherwise, specified paths that are associated with existing Remote Mirror and Copy volume pairs are not be removed. | | | | | | | | | | | | | | | | | source_LSS_ID:target_LSS_ID . . . | (Required) Specifies the Remote Mirror and Copy path relationships for the source and target LSSs that are to be removed. The LSS pair ID consists of two LSS IDs, one designated as the source LSS and the other as the target LSS for a Remote Mirror and Copy path relationship. The two LSS IDs must be separated with a colon and no spaces. The first LSS ID is the source LSS. The second LSS ID is the target LSS. This parameter accepts fully qualified LSS IDs, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range (1750) 00 - 1F. If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified pair: IBM.1750-68FA120/00:IBM.1750-68FA150/00 Example of a shortened version: 00:00 Example of multiple pairs: 00:00 01:01 02:02
Example (1750)
Invoking the rmpprcpath command
| | | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure want to remove the Remote Mirror and Copy path 01:01? [y/n]:Y Remote Mirror and Copy path 01:01 successfully removed.
Remote Mirror and Copy pair commands

This section contains commands that create, manage, and delete Remote Mirror and Copy (formerly PPRC) pairs and display Remote Mirror and Copy pair information. Use the following commands to create, manage, and delete Remote Mirror and Copy pairs and to display Remote Mirror and Copy pair information:
466
v v v v v v v
failbackpprc failoverpprc lspprc mkpprc freezepprc pausepprc resumepprc
v rmpprc v unfreezepprc The failbackpprc command copies the required data from the source volume to the target volume in order to resume mirroring. You can use this command after a failoverpprc command has been issued to restart mirroring from site A (local site) to site B (remote site). The failoverpprc command generates Global Mirror and Metro Mirror disaster recovery processes with the following results: v In a Global Mirror failover recovery process, the failoverpprc command initiates failover processing of B volumes to A volumes. v In a Global Mirror failback recovery process (production is returned to the local site), the failoverpprc command initiates failover processing from A volumes to B volumes. v In a Metro Mirror disaster recovery process, failover processing to the Global Copy secondary volume causes the secondary volumes to become primary volumes and immediately suspends these volumes. The failoverpprc command changes a secondary device into a primary suspended device while leaving the primary device in its current state. The lspprc command generates a report that displays a list of remote mirror and copy volume relationships for a storage image and the status information for each remote mirror and copy volume relationship in the list. The mkpprc command establishes a remote mirror and copy relationship for a volume pair. The freezepprc command creates a new remote mirror and copy consistency group. It places the source logical subsystem (LSS) in the long busy state so that no I/O can be directed to it. It also removes remote mirror and copy paths between the source LSS and target LSS and sets the queue-full condition for the primary volume. The pausepprc command pauses an existing remote mirror and copy volume pair relationship or pauses a single volume ID. The resumepprc command resumes a remote mirror and copy relationship for a volume pair. The rmpprc command removes one or more specified remote mirror and copy volume pair relationships, or it removes a single volume ID (which might be useful when a disaster occurs and you want to specify only the available volume and not both the primary and secondary volumes).
467
The unfreezepprc command resumes I/O activity on a storage unit where the freezepprc command has been issued. The unfreezepprc command resets the queue full condition for the primary volume.
failbackpprc
The failbackpprc command copies the required data from the source volume to the target volume in order to resume mirroring. This command is used in the disaster recovery processes that are associated with sites using Metro Mirror, Global Mirror, or Metro/Global Mirror processing.
failbackpprc -dev -type mmir gcp storage_image_ID -remotedev storage_image_ID
-srcss
ss_ID
-tgtss
ss_ID
-cascade
-suspend
SourceVolumeID:TargetVolumeID -tgtonline -resetreserve -tgtread - . . .
Parameters
Notes: 1. You can issue the failbackpprc command against any remote mirror and copy volume that is in a primary suspended state. The failback processing copies the required data from the source volume to the target volume in order to resume mirroring. 2. A metro mirror (synchronous) pair must be suspended before it can be reestablished as a Global Copy (extended distance) pair and vice versa. 3. When you specify subsystem IDs (SSIDs), the source and target volumes are restricted to 1 LSS for the source and 1 LSS for the target. -dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID, which includes the storage image ID, for the source volume IDs that are defined by the Source_Volume_ID:Target_Volume_ID parameter. Note: The use of the failbackpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original primary site which has been repaired and is ready to once again become your primary production site. For example: v Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103. v Original secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202, 0203. v The following failbackpprc command is correct: (1750) dscli>failbackpprc -dev IBM.1750-685FA120 -remotedev IBM.1750-68FA150 0100:0200 0101:0201 0102:0202 0103:0203 -remotedev storage_image_ID (Optional). Specifies the target storage image ID, which includes manufacturer,
468
type, and serial number. The -remotedev parameter identifies the remote storage unit that contains the target volume IDs that are defined by the SourceVolumeID:TargetVolumeID parameter. The -remotedev parameter is required if you do not specify a fully qualified target volume ID or if you use the -dev parameter. Note: The use of the failbackrpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original secondary site. For example: v Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103. v Original secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202, 0203. v The following failbackpprc command is correct: (1750) dscli>failbackpprc -dev IBM.1750-685FA120 -remotedev IBM.1750-68FA150 0100:0200 0101:0201 0102:0202 0103:0203 -type mmir | gcp (Required). Modify one or more existing remote mirror and copy volume relationships as either Metro Mirror (Synchronous) or Global Copy (Extended Distance) relationships. mmir Metro Mirror maintains the remote mirror and copy relationship in a consistent manner by returning the I/O write completion status to the application when the updates are committed to the target. This process becomes slower as the physical distance between source and target increases. Global Copy maintains the remote mirror and copy relationship in a nonsynchronous manner. I/O write completion status is returned to the application when the updates are committed to the source. Updates to the target volume are performed at a later time. The original order of updates is not strictly maintained.
gcp
-cascade (Optional) Specifies that the remote mirror and copy target volume can also be a remote mirror and copy source volume of a different remote mirror and copy volume relationship. -suspend (Optional) Specifies that the remote mirror and copy relationship be suspended when the task completes. Notes: 1. This parameter is not valid for a Global Copy (Extended Distance) remote mirror and copy volume relationship. 2. This parameter is not valid for a Metro Mirror (Synchronous) remote mirror and copy volume relationship that is established with the No Copy option activated. -tgtonline (Optional) Specifies that a remote mirror and copy volume relationship be established, including when the target volume is online to host systems. Note: This parameter applies only to S/390 or zSeries volumes. It does not apply to Open Systems volumes.
469
-resetreserve (Optional) Specifies that a remote mirror and copy relationship be established when the volume on the secondary logical subsystem is reserved by another host. If this parameter is not specified and the volume on the secondary logical subsystem is reserved, the command fails. Note: This parameter applies only to fixed block volumes. -tgtread (Optional) Specifies that host servers be allowed to read from the remote mirror and copy target volume. For a host server to read the volume, the remote mirror and copy pair must be in a full-duplex state. Note: This parameter applies only to Open System volumes. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Note: The source and target volumes are restricted to one LSS for the source and one LSS for the target when you specify ss_IDs. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Note: The source and target volumes are restricted to one LSS for the source and one LSS for the target when you specify ss_IDs. Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required). Specifies the remote mirror and copy volume pair IDs for the source and target volume pairs that are to undergo failback processing. The original values (before the disaster) return with the source volume IDs equal to the A volumes and the target volume IDs equal to the B volumes. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy volume pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF).
470
If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified pair: IBM.1750-68FA120/0100:IBM.1750-68FA150/ 0100 Example of multiple pairs: 0101:0101 0102:0102 0103:0103
Example (1750)
Invoking the failbackpprc command
dscli>failbackpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100 0101:0101 0102:0102 0103:0103

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror successfully Remote Mirror successfully Remote Mirror successfully Remote Mirror successfully and Copy pair failed back. and Copy pair failed back. and Copy pair failed back. and Copy pair failed back. IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 IBM.1750-68FA120/0101:IBM.1750-68FA150/0101 IBM.1750-68FA120/0102:IBM.1750-68FA150/0102 IBM.1750-68FA120/0103:IBM.1750-68FA150/0103
failoverpprc
The failoverpprc command is used only with disaster recovery processing. This command is used in the disaster recovery processes associated with sites using Metro Mirror, Global Mirror, or Metro/Global Mirror processing. The failoverpprc command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent.
failoverpprc -dev -type mmir gcp storage_image_ID -remotedev storage_image_ID
-tgtonline
-cascade
-srcss
ss_ID
-tgtss
ss_ID
Parameters
The failoverpprc command is used in the Global Mirror and Metro Mirror disaster recovery processes with the following results: v In a Global Mirror failover recovery process, the failoverpprc command initiates failover processing of B volumes to A volumes. This causes the B volumes to become the primary volumes and the A volumes to become the secondary volumes. The effect is that the Global Copy state of the B volumes changes from secondary to primary and suspended. v In a Global Mirror failback recovery process (production is returned to the local site), the failoverpprc command initiates failover processing from A volumes to B volumes. This causes the A volumes to become the primary volumes and the B volumes to become the secondary volumes.
471
v In a Metro Mirror disaster recovery process, failover processing to the Global Copy secondary volume causes the secondary volumes to become primary volumes and immediately suspends these volumes. When you run a Global Copy failover, the B volumes are the primary volumes and the A volumes are the secondary volumes. This action changes only the Global Copy state of the secondary volumes from Target Copy Pending to Suspended. The failoverpprc command changes a secondary device into a primary suspended device while leaving the primary device in its current state. This command succeeds even if the paths are down and the volume at the production site is unavailable or nonexistent. Note: When you specify the subsystem identifier (SSID), the source and target volumes are restricted to one LSS for the source and one LSS for the target. -dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID. Note: The use of the failoverpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original secondary site. For example: v Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103. v Orignial secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202, 0203. v The following failoverpprc command is correct: (1750) dscli>failoverpprc -dev IBM.1750-685FA150 -remotedev IBM.1750-68FA120 0200:0100 0201:0101 0202:0102 0203:0103 -remotedev storage_image_ID (Optional). Specifies the target storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified target volume ID or if you use the -dev parameter. Note: The use of the failoverpprc command requires that this parameter reflect a role reversal. The value for this parameter must be the original primary site. For example: v Original primary site (Site A) has a value of (1750) IBM.1750-68FA120 with volumes 0100, 0101, 0102, 0103. v Orignial secondary site (Site B) has a value of (1750) IBM.1750-68FA150 with volumes 0200, 0201, 0202,0203. v The following failoverpprc command is correct: (1750) dscli>failoverpprc -dev IBM.1750-685FA150 -remotedev IBM.1750-68FA120 0200:0100 0201:0101 0202:0102 -type mmir | gcp (Required). Modifies one or more existing remote mirror and copy volume relationships as either Metro Mirror or Global Copy relationships. mmir Metro Mirror maintains the remote mirror and copy relationship in a
472
consistent synchronous manner when the updates are committed to the target. This process becomes slower as the physical distance between source and target increases. gcp Global Copy maintains the remote mirror and copy relationship in a nonsynchronous manner when the updates are committed to the source. Updates to the target volume are performed at a later time. The original order of updates is not strictly maintained.
-tgtonline (Optional). Establishes a remote mirror and copy volume relationship, including when the target volume is online to host systems. This parameter applies to S/390 or zSeries volumes. It does not apply to Open Systems volumes. -cascade (Optional). Specifies that the PPRC target volume can also be a PPRC source volume of a different PPRC volume relationship. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies the remote mirror and copy volume pair IDs of the source and target volumes that must have their relationships changed so that the target volumes (B volumes) become the source volumes and the original source volumes (A volumes) become the target volumes. This results in the following conditions: v The source volumes (B volumes) show as a suspended host. v The target volumes (A volumes) show as a suspended target and they are accessible for mounting. This parameter also accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF).
473
If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified pair: IBM.1750-68FA150/0100:IBM.1750-68FA120/ 0100 Example of a shortened version: 0100:0100 Example of multiple pairs: 0101:0101 0102:0102 0103:0103
Example (1750)
Invoking the failoverpprc command
dscli>failoverpprc -dev IBM.1750-68FA150 -remotedev IBM.1750-68FA120 0200:0100 0201:0101 0202:0102
The resulting output A confirmation message is presented for each remote mirror and copy pair that is successfully suspended.
lspprc
The lspprc command displays a list of remote mirror and copy (formerly PPRC) volume relationships for a storage image, and status information for each remote mirror and copy volume relationship in the list.
lspprc -dev storage_image_ID -remotedev storage_image_ID
SourceVolumeID:TargetVolumeID -state copy-pending full-duplex suspended target-copy-pending target-full-duplex target-suspended not-remote-copy-pair invalid-state volume-inaccessible -s -l . . . -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which consists of manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified ID for the source and target volumes. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional most times, however required as noted). Specifies the target volume storage image ID, which consists of manufacturer, machine type, and serial number. Note: The -remotedev parameter is required when volume pairs are specified and the -dev parameter is specified as well. Example: IBM.1750-68FA150
474
-state copy-pending | full-duplex | suspended | target-copy-pending | target-full-duplex | target-suspended | not-remote-copy-pair | invalid-state | volume-inaccessible (Optional). Identifies the state of the remote mirror and copy relationship that you want to view. copy-pending Specifies that you want to view remote mirror and copy relationships that have copy processing that is pending. A Global Copy relationship is always copy-pending. full-duplex Specifies that you want to view remote mirror and copy relationships that are full duplex. suspended Specifies that you want to view remote mirror and copy relationships that are suspended. The Reason attribute might indicate why the relationship is suspended. target-copy-pending Specifies that you want to view remote mirror and copy relationships where the target volume has copy processing that is pending. In this state, the source volume is unknown or cannot be queried. target-full-duplex Specifies that you want to view remote mirror and copy relationships where the target volume is full duplex. In this state, the source volume is unknown or cannot be queried. target-suspended Specifies that you want to view remote mirror and copy relationships where the target volume is suspended. In this state, the source volume is unknown or cannot be queried. The Reason attribute might indicate why the relationship is suspended. not-remote-copy-pair Specifies that you want to view remote mirror and copy relationships that are not a remote copy pair. invalid-state Specifies that you want to view remote mirror and copy relationships that do not meet requirements for being valid. The report that is generated with this query only displays the source and target volume IDs of a remote mirror and copy volume relationship and the state designation of invalid-state. All the other information columns are displayed with a null (-) value. volume-inaccessible Specifies that you want to view remote mirror and copy relationships where the volume cannot be viewed, generally this means that the volume is fenced. The report that is generated with this query only displays the source and target volume IDs of a remote mirror and copy volume relationship and the state designation of volume-inaccessible. All the other information columns are displayed with a null (-) value. -s -l (Optional). Displays the remote mirror and copy volume pair IDs. You cannot use the -l and the -s parameters together. (Optional). Displays the default output and the target read enabled, source cascade, target cascade, and suspended attributes. You cannot use the -l and the -s parameters together.
475
SourceVolumeID:TargetVolumeID . . . | (Required) Displays the remote mirror and copy relationships for the source and target volume pairs with the specified IDs. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no spaces. The first volume ID is the source volume. The second volume ID is the target volume. You can enter remote mirror and copy pair IDs, a range of remote mirror and copy pair IDs, single volume IDs, or a range of volume IDs. You cannot enter a combination of remote mirror and copy pair IDs and volume IDs. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a shortened version: 0100:0100 Example of multiple IDs: 0100:0100 0200:0200 0300:0300 Note: A query of target volume IDs is directed to the storage image that is identified by the -dev parameter or embedded in the fully qualified single volume IDs.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lspprc command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the lspprc command
dscli>lspprc -dev IBM.2107-75FA120 -remotedev IBM.2107-75FA150 -l 0100:0100 0101:0101

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120
476
ID IBM.210775FA120 /0100: IBM.210775FA150 /0100 IBM.210775FA120 /0101: IBM.210775FA150 /0101
State FullDuplex
Reason -
Type Metro Mirror
Out Of Sync Tracks 0
Tgt Read Enabled
Src Cascade Disabled
FullDuplex
Metro Mirror
Enabled
Disabled
Tgt Cascade Enabled Enabled
Date Sus pended -
Source LSS 01 02
Timeout (secs) 120 120
Crit Mode Disabled Disabled
First Pass Status False False
GMIR CG Disabled Enabled
PPRC CG Enabled Disabled

ID State Specifies the source and target volume IDs of a remote mirror and copy volume relationship. Displays the current remote mirror and copy volume relationship state. One of the following values is displayed: Copy Pending Indicates that the relationship is copy pending. A Global Copy (Extended Distance) relationship is always copy pending. Full Duplex Indicates that the relationship is full duplex. Suspended Indicates that the relationship is suspended. The Reason attribute might indicate why the relationship is suspended. Target Copy Pending Indicates that the source volume is unknown or cannot be queried and the target state is copy pending. Target Full Duplex Indicates that the source volume is unknown or cannot be queried and the target state is full duplex. Target Suspended Indicates that the source volume is unknown or cannot be queried and the target state is suspended. Not Part of Remote Copy Pair Indicates that the relationship is not a remote copy pair.
477
Invalid State Indicates that the listed remote mirror and copy volume relationships do not meet the requirements for being valid. Note: The report that is generated with the invalid-state designation only displays the source and target volume IDs of a remote mirror and copy volume relationship and the state designation of invalid-state. All the other information columns are displayed with a null (-) value. Volume Inaccessible Indicates that the volume could not be queried. Generally, this indicates that the volume is fenced. Note: The report that is generated with the Volume Inaccessible designation only displays the source and target volume IDs of a remote mirror and copy volume relationship and the state designation of Volume Inaccessible. All the other information columns are displayed with a null (-) value. Reason Indicates why the Remote Mirror and Copy volume relationship is suspended. The following values can be displayed: Unknown Specifies that the volume is suspended but the reason for the suspension is not specifically defined within the system Not in PPRC Relationship Specifies that the designated volume is not part of a Remote Mirror and Copy pair. Host Source Specifies that the Remote Mirror and Copy processing on the volume was suspended by the primary host. The host command might have specified an immediate suspension or that the volume be suspended when it entered a full duplex state. Host Target Specifies that Remote Mirror and Copy processing was suspended on the secondary volume. Updates to primary volumes and out-of-sync tracks are still being processed. Update Target Specifies that Remote Mirror and Copy processing was suspended on a secondary volume by the primary control unit update secondary device status command. Internal Conditions Both Specifies that Remote Mirror and Copy processing was suspended on a volume by either the primary control unit or the secondary control unit because of internal conditions. Simplex Target Specifies that Remote Mirror and Copy processing was suspended on a volume when the secondary control unit sent a state change interrupt to the primary control unit indicating a transition to a simplex state. Internal Conditions Target Specifies that Remote Mirror and Copy processing was suspended
478
on a secondary volume when the primary control unit was notified that the secondary volume became suspended due to internal conditions. Power Specifies that Remote Mirror and Copy processing was suspended on a volume when the primary or secondary control unit was shut down or restarted. Notes: 1. The paths to the secondary controller might not be available if the power to the primary controller was shut down. If only the secondary control unit was shut down, it might be possible for the paths to be restored depending on the path status. Use the following process to determine whether your Remote Mirror and Copy processing can be restored on the affected volumes: a. Issue the lspprc command and use the generated report to determine the path status. b. Issue the mkpprc command if the paths are still in tact. This process resynchronizes the volume pairs. c. Continue with your processing. 2. If the above process cannot be performed, you must remove the pair relationships on the affected volumes and start your Remote Mirror and Copy processing from the beginning on the affected volumes. Freeze Specifies that Remote Mirror and Copy processing was suspended on a volume pair because the host issued a Freeze PPRC Group order. Volume Not Configured Specifies that Remote Mirror and Copy processing was suspended on a volume because the volume is not part of a copy pair relationship. Type Indicates that the remote copy and mirror volume relationship is a Metro Mirror (synchronous) relationship, a Global Copy (extended distance) relationship, or the relationship type is unknown.
Out Of Sync Tracks Indicates the number of tracks that are not synchronized for this FlashCopy relationship. The maximum value is dependent on the source volume size. Notes: 1. If you issue the lspprc command to view the out of sync value for a volume pair (for example, 0000:0001) on a 2105, there is no observable decrease in the value from when you issue the query to the end of the process. 2. If you issue the lspprc command to view the out of sync value for a single volume (for example, 0000) on a 2105, there is an observable decrease in the value but only at 10 second intervals. If you issue the lspprc command and reissue it again before the 10 seconds has expired, there is no observable change in the value.
479
3. If you issue the lspprc command to view the out of sync value for a volume pair or a single volume on a 1750, there is an observable decrease in the value but only at 10 second intervals. Tgt Read Indicates that Read IO operations to the target volume are allowed. Src Cascade Indicates that the source volume of this relationship is enabled to also be a target volume of a different relationship. Tgt Cascade Indicates that the target volume of this relationship is enabled so that it is also a source volume for a different relationship. Date Suspended Indicates the date when this relationship was last suspended. The value can be displayed as a null (-). SourceLSS Indicates the consistency group LSS ID that is associated with the source volume of this PPRC volume relationship. Timeout (secs) Indicates the consistency group Long Busy Timeout setting for the LSS ID that is associated with the source volume of this PPRC volume relationship. The timeout value is either the default value of 120 seconds, or a user-specified value of 1 to 600 000 seconds. Crit Mode Indicates whether the remote copy and mirror primary volume represents a critical volume. First Pass Status Indicates the first pass Global Copy state of the source volume. The data is valid only when you query the primary box and the queried pair is a Global Copy pair. GMIR CG Indicates if the remote mirror and copy consistency group is enabled, disabled or not available. Notes: 1. This value is displayed when you designate the use of the -l parameter and when the primary volume is being queried. 2. This value is not reported for model 2105. If a model 2105 is being queried, the value displayed for this field is N/A (not available). PPRC CG Indicates if the volume is in consistent asynchronous remote mirror and copy mode or is not available. The values that can be displayed are enabled, disabled, or not available. Notes: 1. This value is displayed when you designate the use of the -l parameter. 2. This value is not reported for model 2105. If a model 2105 is using being queried, the value displayed for this field is N/A (not available).
480
mkpprc
The mkpprc command establishes a remote mirror and copy (formerly PPRC) relationship for a volume pair.
mkpprc -dev storage_image_ID -remotedev storage_image_ID -type mmir gcp
-mode
full nocp
-cascade
-tgtonline
-tgtread
-critmode
-resetreserve
-wait
-srcss
ss_ID
-tgtss
ss_ID
Parameters
Notes: 1. When you specify subsystem IDs, the source and target volumes are restricted to one LSS for the source and one LSS for the target. 2. If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must not enable the write acceleration feature. The mkpprc command might fail if the write acceleration feature is enabled. -dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID. Example: IBM.1750-75FA120 -remotedev storage_image_ID (Optional). Specifies the target storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified target volume ID, or if the -dev parameter is selected. Example: IBM.1750-68FA120 -type mmir | gcp (Required). Establishes one or more remote mirror and copy volume relationships as either Metro Mirror (Synchronous) or Global Copy (Extended Distance) relationships. mmir Metro Mirror maintains the remote mirror and copy relationship in a consistent (synchronous) manner by returning I/O write completion status to the application when the updates are committed to the target. This process becomes slower as the physical distance between source and target increases. Global Copy maintains the remote mirror and copy relationship in a nonsynchronous manner. I/O write completion status is returned to the application when the updates are committed to the source. Updates to the target volume are performed at a later time. The original order of updates is not strictly maintained.
gcp
481
-mode full | nocp (Optional). Specifies the initial data copy mode for the remote mirror and copy volume relationships. full nocp Full mode copies the entire source volume to the target volume. This is the default when you do not specify no copy. No Copy mode does not copy data from source to target volumes. This option presumes that the volumes are already synchronized.
-cascade (Optional). Enables a remote mirror and copy target volume to be a remote mirror and copy source volume for a different remote mirror and copy volume relationship. The default value for this parameter is disabled. -tgtonline (Optional). Establishes a remote mirror and copy volume relationship, including when the target volume is online to host systems. This parameter applies to S/390 or zSeries volumes and does not apply to Open Systems volumes. The default value for this parameter is disabled. -tgtread (Optional). Allows host servers to read from the remote mirror and copy target volume. For a host server to read the volume, the remote mirror and copy pair must be in a full-duplex state. This parameter applies to open systems volumes and does not apply to IBM S/390 or zSeries volumes. The default value for this parameter is disabled. -critmode (Optional). Protects the source volume from receiving new data. If the last path fails between the pairs and results in the inability to send information to the target, the source is protected. Current updates and subsequent attempts to update the source fail with a unit check on S/390. The default value for this parameter is disabled. Note: This parameter applies only to S/390 or zSeries volumes. Critical mode operates in one of three ways depending on the setting of the LCU critical mode and the setting of the -critmode parameter in this command. The following table presents an overview of how the critical volume mode works.
Critical Mode Normal LCU, Critical Heavy Disabled or Enabled Mkpprc critmode Disabled Description v Suspends the primary volume. v Allows write operations to the primary volume. Critical Volume Disabled Enabled v Suspends the primary volume when the last path to the secondary volume has failed. v Inhibits write operations to the primary volume.
482
Critical Mode Critical Heavy
LCU, Critical Heavy Enabled
Mkpprc critmode Enabled
Description v Suspends the primary volume when the secondary volume cannot be updated for any reason. v Inhibits write operations to the primary volume.
Notes: 1. Use the -critmode parameter only for log devices, not for devices that the system requires. In extreme cases, the host system might have to be IPLed in order to recover a device that is write inhibited. Whenever possible, use the freezepprc command as an alternative to using the -critmode parameter. 2. The -critmode parameter cannot be used with Global Copy or remote copy and mirror cascading volumes. 3. To reset a volume that is write inhibited because of critical mode, you can issue the mkpprc, pausepprc, or rmpprc command to this volume. 4. Use automation software as part of any solution that includes critical mode. Automation software is not a part of the software that is provided with the storage unit; you must supply it. However, IBM has offerings to assist with this automation. For more information, contact your IBM storage representative. -suspend (Optional). Suspends the remote mirror and copy relationship when the task completes. This parameter is not valid for a Global Copy (Extended Distance) remote mirror and copy volume relationship. This parameter is not valid for a Metro Mirror (Synchronous) remote mirror and copy volume relationship that is established with the No Copy option. The default value for this parameter is disabled. -resetreserve (Optional - open system volumes only). Allows the establishment of a remote mirror and copy relationship when the volume on the secondary logical subsystem is reserved by another host. This parameter can only be used with open system volumes. If this option is not specified and the volume on the secondary logical subsystem is reserved, the command fails. -wait (Optional). Delays the command response until the remote copy and mirror volumes are in one of the final states: simplex, full duplex, suspended, secondary full duplex, secondary suspended or secondary simplex (until the pair is not in the Copy Pending state). The default value for this parameter is disabled. Notes: 1. This parameter cannot be used with the -type gcp or -mode nocp parameters.
483
2. When you use the -wait parameter, you must wait until the original command completely processes before you can issue a new command. 3. If you are running in single-shot mode, you can periodically issue the lspprc command to check the remote mirror and copy volume pair state, and then continue with new commands when the correct state is reached. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required). Specifies the remote mirror and copy volume relationship for the source and target volume pairs with the specified IDs. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair IDs with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified pair: IBM.1750-68FA120/0100:IBM.1750-68FA150/ 0100 Example of a shortened version: 0100:0100 Example of multiple pairs: 0101:0101 0102:0102 0103:0103
Additional processing tips

The following examples represent some CLI volume format options that you might want to incorporate in your processing: Processing multiple volumes The following two examples are ways that this circumstance might be
484
processed, and both are correct. The first method might be fine if you were managing a few volumes, while the second allows you to process hundreds or thousands of volumes more efficiently. v mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A type mmir
-mode full -tgtread 1000:1205 1001:1206 1002:1207 1003:1208 1004:1209 ....... and so on v mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A type mmir -mode full -tgtread 1000-1004:1205-1209
Using the grouping method in your command You can also group the volumes. However, the order of the volumes is critical when you group them, and they must be contiguous. The following shows how to code for grouping:
mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A type mmir -mode full -tgtread 1000-1004:1205-1209 1100-1104:1300-1304
Example (1750)
Invoking the mkpprc command
The resulting output (an example only)

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 CMUC00153I 0100:0100 CMUC00153I 0101:0101 CMUC00153I 0102:0102 CMUC00153I 0103:0103 mkpprc: Remote Mirror successfully created. mkpprc: Remote Mirror successfully created. mkpprc: Remote Mirror successfully created mkpprc: Remote Mirror successfully created and Copy volume pair relationship and Copy volume pair relationship and Copy volume pair relationship and Copy volume pair relationship
freezepprc
The freezepprc command creates a new remote mirror and copy consistency group. It places the source logical subsystem (LSS) in the long busy state so that no I/Os can be directed to it. It also removes remote mirror and copy paths between the source LSS and target LSS and sets the queue full condition for the primary volume. This causes the host to queue writes to the primary volume until the queue full condition is reset. During the queue full condition, the primary volume reports long busy status.
freezepprc -dev storage_image_ID -remotedev storage_image_ID
Source_LSS_ID:Target_LSS_ID -srcss ss_ID -tgtss ss_ID - . . .
Parameters
Note: When specifying SSIDs, the command is limited to one LSS pair.
485
-dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified source LSS ID. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional). Specifies the target storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified target LSS ID or if the -dev parameter is used. Example: IBM.1750-68FA150 -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 Source_LSS_ID:Target_LSS_ID . . . | (Required). Specifies that a consistency group for the source and target LSSs with the IDs specified be placed in a long busy state. Accepts fully qualified LSS IDs, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. A remote mirror and copy path LSS pair ID consists of two LSS IDs, one designated as the source LSS and the other as the target LSS for a remote mirror and copy path relationship. The two LSS IDs must be separated with a colon and no spaces. The first LSS ID is the source LSS. The second LSS ID is the target LSS. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range 00 - 1F (1750 only). If you specify the dash (-), this parameter information is automatically supplied. Example of a pair: 00:00 Example of multiple pairs: 00:00 01:01 02:02
Example (1750)
Invoking the freezepprc command
dscli>freezepprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 01:01
486
Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror and Copy consistency group 01:01 successfully created.
pausepprc
The pausepprc command pauses an existing remote mirror and copy volume pair relationship. Or, this command can be used to pause a single volume ID. To use with a single volume you must specify either the -at src parameter option or the -at tgt parameter option. If neither of these options are specified in the command, single volumes are not valid.
pausepprc -dev storage_image_ID -remotedev storage_image_ID
-at
src
tgt
-unconditional
-srcss
ss_ID
-tgtss
ss_ID
Parameters
Note: When specifying SSIDs, the command is limited to one LSS pair. -dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional most times, however required as noted). Specifies the target storage image ID, which includes manufacturer, type, and serial number. Note: The -remotedev parameter is required when volume pairs are specified and the -dev parameter is specified as well. Example: IBM.1750-68FA120 -at src | tgt (Optional). src Select the -at source parameter option to initiate a suspend action from the source volume. After the task successfully runs, the source and target volumes are in the suspend state. The -at source parameter option can also be used with single volumes. When you specify a single volume using this option, the volume is treated as a source and the target is treated as a null. tgt Select the -at target parameter option to initiate a suspend action from the target volume. After the command successfully runs, the target volume is in the suspend state, but there is no guarantee that the source volume is suspended as well. For a suspend action that is issued to the target, the source can remain in the active state.
487
The -at target parameter option can also be used with single volumes. When you specify a single volume using this parameter option, the volume is treated as a target and the source is treated as a null. -unconditional (Optional). Use this parameter to indicate that a source or target volume has been selected individually, and not as a pair. The -unconditional parameter is valid only if the -at parameter is selected. When you specify the -unconditional parameter, you can specify only the source volume ID if the -at source parameter option is selected, or specify only the target volume ID if the -at target parameter option is selected. Do not use volume pair IDs. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required). Specifies that a remote mirror and copy volume relationship for the source and target volume pairs with the IDs specified be paused. Note: Provide a single volume ID instead of a volume pair if you use the -unconditional parameter. Specifying pairs results in a format error. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied. Note: Requests directed to target volumes are sent to the Storage Image identified by the -dev parameter or embedded in the fully qualified single volume IDs. Example of a fully qualified pair: IBM.1750-68FA120/0100:IBM.1750-68FA150/ 0100
488
Example of a shortened version: 0100:0100 Example of multiple pairs: 0101:0101 0102:0102 0103:0103
Example (1750)
Invoking the pausepprc command
dscli>pausepprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror and Copy pair IBM.1750-68FA120/0100:0103 successfully paused.
resumepprc
The resumepprc command resumes a remote mirror and copy (formerly PPRC) relationship for a volume pair. | | | | | | | | | |
resumepprc -dev storage_image_ID -remotedev storage_image_ID -type mmir gcp
-cascade
-tgtonline
-tgtread
-critmode
-suspend
-resetreserve
-wait
-srcss
ss_ID
-tgtss
ss_ID
Parameters
Notes: 1. When you specify subsystem IDs, the source and target volumes are restricted to 1 LSS for the source and 1 LSS for the target. 2. When you use the -wait parameter, periodically issue the lspprc command. This command allows you to verify which of the states that the pair has reached during processing. 3. You cannot issue other commands while the -wait parameter is processing. The entire transaction must complete before you can proceed with commands other than status commands like list commands or show commands. -dev storage_image_ID (Optional) Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional) Specifies the target storage image ID, which includes manufacturer,
489
machine type, and serial number. This parameter is required if you do not specify a fully qualified target volume ID or if you specify the -dev parameter. -type mmir | gcp (Required) Modifies one or more remote mirror and copy volume relationships to be either Metro Mirror (synchronous) or Global Copy (extended distance) relationships. mmir Metro Mirror processing maintains the remote mirror and copy relationship in a consistent (synchronous) manner when the updates are committed to the target. This process becomes slower as the physical distance between source and target increases. Global Copy processing maintains the remote mirror and copy relationship in a nonsynchronous manner when the updates are committed to the source. Updates to the target volume are performed at a later point in time. The original order of updates is not strictly maintained.
gcp
-cascade (Optional) Enables a remote mirror and copy target volume to be a remote mirror and copy source volume for a different remote mirror and copy volume relationship. -tgtonline (Optional) Establishes a remote mirror and copy volume relationship, including when the target volume is online to host systems. This parameter applies to S/390 or zSeries volumes. It does not apply to Open Systems volumes. | | | | | | -tgtread (Optional) Allows host servers to read from the remote mirror and copy target volume. For a host server to read the volume, the remote mirror and copy pair must be in a full-duplex state. This parameter applies to open systems volumes and does not apply to IBM S/390 or zSeries volumes. The default value for this parameter is disabled. -critmode (Optional) Protects the source volume from receiving new data. If the last path fails between the pairs which results in the inability to send information to the target, the source is protected. Current updates and subsequent attempts to update the source fail, with a unit check on S/390. -suspend (Optional) Specifies that the remote mirror and copy relationship be suspended when the task completes. This parameter is not valid for a Global Copy (extended distance) remote mirror and copy volume relationship. This parameter is not valid for a Metro Mirror (synchronous) remote mirror and copy volume relationship that is established with the No Copy option. -resetreserve (Optional) Establishes the remote mirror and copy relationship when the volume on the secondary logical subsystem is reserved by another host. If this parameter is not specified and the volume on the secondary logical subsystem is reserved, the command fails. This parameter can only be used with fixed block volumes. -wait (Optional). Specifies that the command response be delayed until the remote copy and mirror volumes are in one of the final states: simplex, full duplex, suspended, secondary full duplex, secondary suspended or secondary simplex
490
(until the pair is not in the Copy Pending state). This parameter cannot be used with the -type gcp or -mode nocp parameters. -srcss SS_ID (Optional) Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss SS_ID (Optional) Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required) Specifies that a remote mirror and copy volume relationship for the source and target volume pairs with the specified IDs be resumed. This parameter accepts fully qualified volume IDs, which includes storage image IDs or a shortened version without storage image IDs, if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs: one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E, and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the resumepprc command
dscli>resumepprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100
| | | | | | | |

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror and Copy volume pair IBM.1750-68FA120/0100:0103 relationship successfully resumed. This message is being returned before the copy completes.
rmpprc
The rmpprc command removes a Remote Mirror and Copy volume pair relationship. Or, this command can be used to remove a single volume ID (which might be useful when a disaster occurs and you want to specify only the available volume and not both the primary and secondary). To use with a single volume,
491
you must specify either the -at src parameter option or the -at tgt parameter option. If neither of these options are specified in the command, single volumes are not valid. The -unconditional parameter must be specified when you designate a single volume; otherwise an error occurs and the command process fails.
rmpprc -dev storage_image_ID -remotedev storage_image_ID
-at
src
tgt
-unconditional
-quiet
-srcss
ss_ID
SourceVolumeID:TargetVolumeID -tgtss ss_ID - . . .
Parameters
Notes: 1. When you specify subsystem IDs, the source and target volumes are restricted to 1 LSS for the source and 1 LSS for the target. 2. If there is a communication problem between the primary server and the secondary server (2-site configuration) when the rmpprc command is issued, the following actions occur: v Error message CMUN03012E is issued. This error message indicates that there was a communication problem between the primary and secondary server and that the transaction has failed. However, a partial removal of the pair relationship has occurred. v The pair relationship is ended on either the primary volumes or the secondary volumes and the volumes that had the relationship removed enter a simplex state. If this circumstance has occurred, reissue the rmpprc command for each volume that did not have its pair relationship removed. This transaction involves using the -at src or -at tgt parameter and the -unconditional parameter. The following represents the format of the rmpprc command when you must remove a partial pair relationship: v If the source volume has not been removed from the pair relationship, enter the rmpprc command at the dscli command prompt with the following parameters and variables:
dscli>rmpprc -dev storage_image_ID -at src -unconditional SourceVolumeID
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
v If the target volume has not been removed from the pair relationship, enter the rmpprc command at the dscli command prompt with the following parameters and variables:
dscli>rmpprc -dev storage_image_ID -at tgt -unconditional SourceVolumeID
The value of the storage image ID must be the secondary server. The management console must be able to communicate with the secondary server for this command to process successfully. 3. If a disaster occurs involving a 3-site configuration, the rmpprc command with the -at tgt and -unconditional parameters are used in the recovery process.
492
-dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source volume ID or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional most times, however required as noted). Specifies the target storage image ID, which includes manufacturer, machine type, and serial number. Note: The -remotedev parameter is required when volume pairs are specified and the -dev parameter is specified, as well. Example: IBM.1750-68FA150 -at src | tgt (Optional). src Select the -at src parameter option to initiate a break action from the source volume. After the task successfully runs, the source and target volumes are in the simplex state. Select the -at tgt parameter option to initiate a break action from the target volume. After the command successfully runs, the target volume is in the simplex state, but there is no guarantee that the source volume state will change. For a break action issued to the target, the source can remain in the suspend state. The -at tgt parameter option can also be used with single volumes but you must also specify the -unconditional parameter. When you specify a single volume using this parameter, the volume is treated as a target and the source is treated as a null. -unconditional (Optional). Use this parameter to indicate that a source or target volume has been selected individually, and not as a pair. The -unconditional parameter is valid only if the -at parameter is selected. When you specify this parameter, you can specify only the source volume ID if the -at src parameter is selected, or specify only the target volume ID if the -at tgt parameter is selected. Do not use volume pair IDs. -quiet (Optional). Specifies that the confirmation prompt for this command be turned off. -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1.
tgt
493
Example: 0010 SourceVolumeID:TargetVolumeID . . . | (Required). Specifies the Remote Mirror and Copy volume relationship for the source and target volume pairs with the IDs specified that is to be removed. Note: Provide a single volume ID instead of a volume pair if you use the -unconditional parameter. Specifying pairs will result in a format error. This parameter accepts fully qualified volume IDs, which includes storage image IDs, or a shortened version without storage image IDs if the -dev parameter is specified. You must separate multiple remote mirror and copy pair IDs with spaces. A remote mirror and copy pair ID consists of two volume IDs, one designated as the source and the other as the target volume for a remote mirror and copy relationship. You must separate the two volume IDs of a remote mirror and copy pair ID with a colon and no space. The first volume ID is the source volume. The second volume ID is the target volume. The volume ID is a 32-bit number that can be represented as 4 hexadecimal digits in the form of XYZZ, where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). If you specify the dash (-), this parameter information is automatically supplied.
Example (1750)
Invoking the rmpprc command

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to delete the Remote Mirror and Copy volume pair relationship 0100:0100? [y/n]: Y Remote Mirror and Copy pair IBM.1750-68FA120/0100:0100 successfully removed.
unfreezepprc
The unfreezepprc command resumes I/O activity on a storage unit where the freezepprc command has been issued. The unfreezepprc command resets the queue full condition for the primary volume. All queued writes to the source volume are written.
unfreezepprc -dev storage_image_ID -remotedev storage_image_ID
Source_LSS_ID:Target_LSS_ID -srcss ss_ID -tgtss ss_ID - . . .
Parameters
Notes:
494
1. This command affects all remote copy and mirror primary volumes that are contained by the LSS(s) that are defined by the Source_LSS_ID:Target_LSS_ID source volume. 2. When specifying subsystem IDs, the command is limited to one LSS pair. 3. Resuming I/O activity on a storage unit where the freezepprc command has been issued is sometimes referred to as the thaw operation. -dev storage_image_ID (Optional). Specifies the source storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified source LSS ID or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -remotedev storage_image_ID (Optional). Specifies the target storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified target LSS ID or if the -dev parameter is used. Example: IBM.1750-68FA120 -srcss ss_ID (Optional). Specifies the subsystem ID of the primary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 -tgtss ss_ID (Optional). Specifies the subsystem ID of the secondary logical subsystem in the format 0x0001 - 0xFFFF. This value is required for the IBM System Storage Enterprise Storage Server versions 2.4.0 and 2.4.1. Example: 0010 Source_LSS_ID:Target_LSS_ID . . . | (Required). Specifies that a consistency group for the source and target LSSs with the IDs specified be removed from the long busy state. This parameter accepts fully qualified LSS IDs, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. A remote mirror and copy path LSS pair ID consists of two LSS IDs, one designated as the source LSS and the other as the target LSS for a remote mirror and copy path relationship. The two LSS IDs must be separated with a colon and no spaces. Multiple remote mirror and copy path LSS pair IDs must be separated with a space between each value. The first LSS ID is the source LSS. The second LSS ID is the target LSS. The fully qualified LSS ID format is storage_image_ID/xx, where xx is a hexadecimal number in the range 00 - 1F (1750 only). If you specify the dash (-), this parameter information is automatically supplied.
495
Example pair: 00:00 Example of multiple pairs: 00:00 01:01 02:02
Example (1750)
Invoking the unfreezepprc command
dscli>unfreezepprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 01:01

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Remote Mirror and Copy pair ID 01:01 successfully thawed.
Global Mirror commands

This section contains commands that are used to create, manage, and delete Global Mirror relationships and to display Global Mirror information. Use the following commands to create, manage, and delete Global Mirror relationships and to display Global Mirror information: v mkgmir v pausegmir v resumegmir v rmgmir v showgmir v showgmircg v showgmiroos The mkgmir command starts Global Mirror processing for a specified session. The pausegmir command pauses Global Mirror processing for the specified session. There are 2 primary reasons to pause Global Mirror processing: v To repair a part of the Global Mirror infrastructure, such as: Global Copy volume pairs or FlashCopy pairs v To make modifications to the Global Mirror tuning parameters The resumegmir command resumes Global Mirror processing for a specified session. If you have issued a pausegmir command to pause Global Mirror processing, issue the resumegmir command to continue Global Mirror processing. The rmgmir command ends Global Mirror processing for the specified session. The showgmir command generates two reports. The first report displays the detailed properties about the current Global Mirror operations that are associated with a specified logical subsystem ID. The second report displays the performance metrics for the current Global Mirror operations that are associated with a specified logical subsystem ID. The shogmircg command generates a report that displays the consistency group status for the specified Global Mirror session.
496
The showgmiroos command generates a report that displays the number of unsynchronized (out of sync) tracks for the specified Global Mirror session.
mkgmir
The mkgmir command starts Global Mirror for a specified session.
mkgmir -dev storage_image_ID -lss LSS_ID -cginterval -session -coordinate milliseconds -drain seconds seconds
session_ID
Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID . . . -
Parameters
Note: If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must not enable the write acceleration feature. The mkgmir command might fail if the write acceleration feature is enabled. -dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID, which includes a storage image ID. Example: IBM.1750-68FA120 -lss LSS_ID (Required). Specifies the master logical subsystem (LSS) that receives the mkgmir command. This parameter accepts a fully qualified master LSS ID, which includes either the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -cginterval seconds (Optional). Specifies the consistency group interval time, in seconds. This number specifies how long to wait between the formation of consistency groups. If this number is not specified or is set to zero, consistency groups are formed continuously. The consistency group interval setting is required for a start action. If not specified, the default interval is zero. The consistency group interval setting can be modified for a resume action; otherwise, the interval that is specified for the start action is maintained. The maximum value is 65 535 seconds. -coordinate milliseconds (Optional). Specifies the maximum coordination interval, in milliseconds. This value indicates the maximum time that Global Mirror processing queues Primary/Host/IO to start forming a consistency group. The coordination interval setting is required for a start action. If this value is not specified, the default interval is 50 milliseconds. The coordination interval setting can be modified for a resume action: otherwise, the interval that is specified for the start action is maintained. The maximum value is 65 535 milliseconds.
497
-drain seconds (Optional). Specifies the maximum consistency group drain time in seconds and the maximum amount of time that the consistent set of data is allowed to drain to the remote site before failing the current consistency group. The drain time setting is required for a start action. If the drain time is not specified, the default drain time is 30 seconds. The drain time setting can be modified for a resume action; otherwise, the time that is specified for the start action is maintained. -session session_ID (Required). Specifies that Global Mirror for the specified session be started or resumed. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal range or the 1 - 255 decimal range. Example: 01 Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID . . . | (Optional). Specifies one or more Global Mirror associations. A Global Mirror association consists of two fully qualified LSS IDs. The first is designated as the master resource and the second is the subordinate resource between which a PPRC path has been established. An LSS ID is two characters in the 00 - 1F (1750 only) hexadecimal range. You must separate the fully qualified LSS IDs of a Global Mirror association with a colon and no spaces. The master resource must be identical for all relationships. If you specify the dash (-), this parameter information is automatically supplied. Example of one Global Mirror association with a single subordinate in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 Example of multiple Global Mirror associations with two subordinates in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 IBM.1750-68FA120/00: IBM.1750-68FA150/01
Example (1750)
Invoking the mkgmir command
dscli>mkgmir -dev IBM.1750-68FA120 -lss 10 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Global Mirror for session 01 successfully started.
pausegmir
The pausegmir command pauses Global Mirror for the specified session.
pausegmir -dev storage_image_ID -lss ID -session session_ID
498
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID. Example: IBM.1750-68FA120 -lss ID (Required). Specifies the master logical subsystem (LSS) that receives the pausegmir command. Accepts a fully qualified master LSS ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -session session_ID (Required). Specifies the session ID for which the Global Mirror process is to be paused. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal range or the 1 - 255 decimal range. Example: 01 Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID . . . | (Optional). Specifies one or more Global Mirror path associations. A Global Mirror (Asynchronous PPRC) path association consists of two fully qualified LSS IDs, one designated as the master resource and the other as the subordinate resource between which a remote copy and mirror path has been established. A LSS ID is two hexadecimal characters in the range 00 - 1F (1750 only). You must separate the fully qualified LSS IDs of a Global Mirror path association with a colon and no spaces. The master resource must be identical for all relationships. If you specify the dash (-), this parameter information is automatically supplied. Example of one Global Mirror association with a single subordinate in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 Example of multiple Global Mirror associations with two subordinates in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 IBM.1750-68FA120/00: IBM.1750-68FA150/01
Example (1750)
Invoking the pausegmir command

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Global Mirror for session 01 successfully paused.
resumegmir
The resumegmir command resumes Global Mirror processing for a specified session.
499
resumegmir -dev storage_image_ID
-lss
LSS_ID
-session -cginterval seconds -coordinate milliseconds -drain seconds
session_ID
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, machine type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID or you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -lss LSS_ID (Required). Specifies the master logical subsystem (LSS) that is to receive the resumegmir command. Accepts a fully qualified LSS ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The shortened version is two hexadecimal digits in the range 00 - 1F (1750 only). Example of a fully qualified LSS ID: IBM.1750-68FA120/10 Tuning parameters consist of the following three values: -cginterval seconds , -coordinate milliseconds , -drain seconds Tuning parameters have default values applied to them from the microcode. However, you can choose to change those values. You must designate a value for each of the parameters even if you are changing only one value. For example, if you decide to change only the value on the -cginterval parameter from 0 to 1, your command must include the default values for the other two parameters. Your command would look like the following:
dscli>resumegmir IBM.1750-68FA120/10 -cginterval 1 -coordinate 50 -drain 30 -session 01 IBM.1750-68FA120/00:IBM.1750-68FA150/00
-cginterval seconds: Specifies the consistency group interval time, in seconds. This number specifies how long to wait between the formation of consistency groups. If this number is not specified or is set to zero, consistency groups are formed continuously. The default value is 0. The maximum value is 65 535 seconds. -coordinate milliseconds: Specifies the maximum coordination interval, in milliseconds. This value indicates the maximum time that Global Mirror processing queues Primary/Host/IO to start forming a consistency group. The default value is 50 milliseconds. The maximum value is 65 535 milliseconds. -drain seconds: Specifies the maximum consistency group drain time in seconds and the maximum amount of time that the consistent set of data is allowed to drain to the remote site before failing the current consistency group. The default drain time is 30 seconds.
500
-session session_ID (Required). Specifies the Global Mirror session that is to be started. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal range or the 1 - 255 decimal range. Example: 01 Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID . . . | (Optional). Specifies one or more Global Mirror path associations. A Global Mirror path association consists of two fully qualified LSS IDs. The first is designated as the master resource and the second is the subordinate resource between which a PPRC path has been established. A LSS ID is two hexadecimal characters in the range 00 - 1F (1750 only). You must separate the fully qualified LSS IDs of a Global Mirror association with a colon and no spaces. The master resource must be identical for all relationships. If you specify the dash (-), this parameter information is automatically supplied. Example of one Global Mirror association with a single subordinate in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 Example of multiple Global Mirror associations with two subordinates in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 IBM.1750-68FA120/00: IBM.1750-68FA150/01
Example (1750)
Invoking the resumegmir command

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Global Mirror for session 01 successfully resumed.
rmgmir
The rmgmir command ends Global Mirror processing for the specified session.
rmgmir -dev -session storage_image_ID -quiet -force -subordinate -lss ID
session_ID
Parameters
Note: Although this command might interrupt the formation of a consistency group every attempt is made to preserve the previous consistent copy of the data on the FlashCopy target volumes. If, due to failures, this command cannot complete without compromising the consistent copy the command
501
stops processing and an error code is issued. If this occurs, reissue this command (rmgmir) with the -force parameter to force the command to stop the Global Mirror process. -dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID. Example: IBM.1750-68FA120 -quiet (Optional). Turns off the confirmation prompt for this command. -force (Optional). Forces the Global Mirror process to stop regardless of the state of the Global Mirror associations. -subordinate (Optional). Indicates that the -lss parameter specifies a subordinate LSS ID. -lss ID (Required). Specifies the logical subsystem (LSS) that is participating in the Global Mirror session. Accepts a fully qualified LSS ID, which includes the storage image ID or a shortened version without the storage image ID, if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -session session_ID (Required). Specifies the session ID for which the Global Mirror path association will be removed. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal or 1 - 255 decimal ranges. Example: 01 Master_Control_Path_LSS_ID:Subordinate_Control_Path_LSS_ID . . . | (Optional). Specifies one or more Global Mirror path associations. A Global Mirror path association consists of two fully qualified LSS IDs. The first is designated as the master resource and the second is the subordinate resource between which there is a remote mirror and copy path. A LSS ID is two hexadecimal characters in the range 00 - 1F (1750 cli). You must separate the fully qualified LSS IDs of a Global Mirror association with a colon and no spaces. The master resource must be identical for all relationships. If you specify the dash (-), this parameter information is automatically supplied. Example of one Global Mirror path association with a single subordinate in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 Example of multiple Global Mirror path associations with two subordinates in the configuration: IBM.1750-68FA120/00: IBM.1750-68FA150/00 IBM.1750-68FA120/00: IBM.1750-68FA150/01
Example (1750)
Invoking the rmgmir command
502
Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to stop Session ID 01? [y/n]: Y Global Mirror for Session ID 01 successfully stopped.
showgmir
The showgmir command displays detailed properties and performance metrics for a Global Mirror logical subsystem ID.
showgmir -dev storage_image_ID -metrics LSS_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified logical subsystem (LSS) ID. Example: IBM.1750-68FA120 -metrics (Optional). Specifies that the logical subsystem ID and its performance statistics be displayed. LSS_ID | (Required). Specifies the logical subsystem (LSS) that receives the showgmir command. This parameter accepts a fully qualified LSS ID, which includes the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. The LSS ID is two hexadecimal digits in the range 00 - 1F (1750 only). If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified LSS ID: IBM.1750-68FA120/10
Example (metrics not specified)

For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the showgmir command. A separate example is not shown for the 1750 as the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the showgmir command
dscli>showgmir -dev IBM.2107-75FA120 10

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120
503
ID
Master Count
Master Session ID 01
Copy State
Fatal Reason
CG Interval 60
Global Mirror Interval 50
CG Drain Time 240
Current Time 01/03 /2005 08:00:00 MST 0
IBM. 1 210775FA120 /10
Running 00
CG Time 01/03 /2005 07:58:00 MST 0
CG Failed Attempt 0
Successful CG Percentage 100
FlashCopy Sequence Number 10
Master ID IBM. 210775FA120
Subordinate Count 1
Master SSID 0010
Subordinate SSID 0020

ID Specifies the LSS ID which consists of a Storage Image ID followed by two hexadecimal characters 00 - 1F (1750 only) that identify a Global Mirror (Asynchronous PPRC) master LSS ID.
Master Count Specifies the number of Global Mirror (Asynchronous PPRC) masters. This value could be null (-) if none exist. Master Session ID Identifies the session ID that you assigned, 01-FF (1-255 decimal). Copy State Identifies the Global Mirror (Asynchronous PPRC) copy state. The value displayed is one of the following Running Running indicates that the remote copy and mirror copy process is running. Paused Paused indicates that the remote copy and mirror copy process is paused. Fatal Fatal indicates that the remote copy and mirror copy process is failed. Pause In Progress Pause In Progress indicates that the remote copy and mirror copy process is in the process of pausing. Fatal Reason Specifies a reason code for the failure. CG Interval Indicates the interval time between attempts to form a consistency group, up to 65 535 seconds.
504
Global Mirror Interval Indicates the extended distance consistency maximum coordination interval, up to 65 535 milliseconds. CG Drain Time The CG drain time is the maximum time that the consistent set of data is allowed to drain to the remote site before failing the current consistency group, the maximum value is 65,535 seconds. Current Time Indicates the time stamp for when this report was generated. The date is displayed in the MM/DD/YYYY format. The time is displayed in the HH:MM:SS format on a 24 hour clock. Note: Daylight Savings is set to 1 if the clock is to be automatically adjusted at applicable times between standard and daylight savings times. Set to 0 if the clock is not to be automatically adjusted for daylight savings time. CG Time Indicates the time recorded when the last successful Consistency Group was formed. CG Failed Attempt Indicates the number of unsuccessful attempts to form a Consistency Group since the last time a Consistency Group was formed. Successful CG Percentage Indicates the percentage of attempts to form a Consistency Group that was successful, from 0% to 100%. FlashCopy Sequence Number Specifies the FlashCopy sequence number associated with the current Consistency Group. Note: This value does not apply to a 2105 so a null (-) is displayed when a 2105 is associated with this reporting. Master ID Identifies the Global Mirror (Asynchronous PPRC) master Storage_Image_ID. Subordinate Count Specifies the count of subordinate associations. The master-subordinate association fields repeat according this count. Master SSID Identifies the SSID value that is associated with the master LSS ID. Subordinate SSID Identifies the SSID value that is associated with the subordinate LSS ID. This field repeats for each master-subordinate path association.
Example (metrics specified)

The following tables represent the headers that are displayed on the output report that is associated with the showgmir command using the -metrics parameter. A separate example is not shown for the 1750 as the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the showgmir command
505
dscli>showgmir -dev IBM.2107-75FA120 -metrics 10

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Last Successful CG Form Time 01/13 /1970 13:08:37 PST
ID IBM. 210775FA120 /10
Total Failed CG Count 2
Total Successful CG Count 3
Successful CG Percentage 40
Failed CG after Last Success 2
Coord. Time (milliseconds) 50
Interval Time (seconds) 5
Max Drain Time (seconds) 240
First Failure Control Unit IBM. 210775FA120
First Failure LSS 0x05
First Failure Status Error
First Failure Reason Long Busy
First Failure Master State Error Recovery
Last Failure Control Unit IBM. 210775FA120
Last Failure LSS 0x05
Last Failure Status Error
Last Failure Reason Long Busy
Last Failure Master State Error Recovery
Previous Failure Control Unit IBM. 210775FA120
Previous Failure LSS 0x05
Previous Failure Status Error
Previous Failure Reason Long Busy
Previous Failure Master State Error Recovery

ID Identifies the LSS ID. This ID consists of an Storage_Image_ID followed by two hexadecimal characters 00 - 1F (1750 only) that identify a Global Mirror (Asynchronous PPRC) master LSS ID.
Total Failed CG Count Specifies the total number of Consistency Groups that did not complete in the user specified drain time. Total Successful CG Count Identifies the total number of Consistency Groups that completed before the user specified drain time. Successful CG Percentage Identifies the percentage of attempts that were successful in forming a consistency group. Failed CG after Last Success Specifies the total number of failed Consistency Groups after the last successful completion. Last Successful CG Form Time Identifies the last successful Consistency Group completion time.
506
Coord. Time (milliseconds) Specifies the value in milliseconds that indicates the maximum amount of time Global Mirror will queue Primary/Host I/O to start forming a consistency group. Default is 50 milliseconds. Interval Time (seconds) Specifies the value in seconds that indicates how long to wait between formation of Consistency groups. Max Drain Time (seconds) Specifies the value in seconds that indicates the maximum amount of time that Global Mirror will allow for the consistent set of data to drain to the remote site. First Failure Control Unit Identifies the Control Unit MTS that has caused the first failure of the consistency group formation. First Failure LSS Identifies the LSS number that has caused the first failure of the consistency group formation. First Failure Status Indicates the first failure status of the consistency group formation. The First Failure Reason and First Failure Master State fields display data only when this field contains Error. First Failure Reason Specifies the error reason of the first failure of the consistency group formation attempt. First Failure Master State Identifies the master state for the first Global Mirror failure. Last Failure Control Unit Identifies the Control Unit MTS that has caused the last failure of the consistency group formation. Last Failure LSS Identifies the LSS number that has caused the last failure of the consistency group formation. Last Failure Status Indicates the last failure status of the consistency group formation. The Last Failure Reason and Last Failure Master State fields display data only when this field contains Error. Last Failure Reason Specifies the error reason of the last failure of the consistency group formation attempt. Last Failure Master State Identifies the master state for the last Global Mirror failure. Previous Failure Control Unit Identifies the Control Unit MTS that has caused the previous failure of the consistency group formation. Previous Failure LSS Identifies the LSS number that has caused the previous failure of the consistency group formation.
507
Previous Failure Status Indicates the previous failure status of the consistency group formation. The Previous Failure Reason and Previous Failure Master State fields display data only when this field contains Error. Previous Failure Reason Specifies the error reason of the previous failure of the consistency group formation attempt. Previous Failure Master State Specifies the master state for the previous Global Mirror failure.
showgmircg
The showgmircg command displays consistency group status for the specified Global Mirror session.
showgmircg -dev storage_image_ID - -lss LSS_ID session_ID . . .
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID, which includes a storage image ID. Example: IBM.1750-68FA120 -lss LSS_ID (Required). Specifies the master logical subsystem (LSS) that receives the showgmircg command. LSS ID consists of two hexadecimal characters in the range of 00 - 1F (1750 only). Accepts a fully qualified master LSS ID, which includes either the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 session_ID . . . | (Required). Specifies one or more sessions to display. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal range or the 1 - 255 decimal range. If you specify the dash (-), this parameter information is automatically supplied. Example: 01
Example
A separate example is not shown for the 1750 as the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the showgmircg command
dscli>showgmircg dev IBM.2107-75FA120 -lss 01 10
508
Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 LSS ID IBM.2107-75FA120/10 Session 01 CG Status 0

The following supplies information that you can use to help you understand the output that is generated from this command. LSS ID Indicates the logical subsystem ID. Session Indicates the Global Mirror session number. CG Status Indicates the Global Mirror Consistency Group status (primarily used by Field Engineering).
showgmiroos
The showgmiroos command displays the number of unsynchronized (out of sync) tracks for the specified Global Mirror session.
showgmiroos -dev session_ID - storage_image_ID -scope si lss -lss LSS_ID
Parameters
Note: You might want to use this command to assist you in the following circumstances: v To see how data is transferring. The showgmiroos command lets you see how far behind the remote site is from the local site in the transfer of data. The displayed value represents how many tracks must be transferred to catch up (be synchronized). v You are not able to form consistency groups because you have exceeded the maximum drain time. The number of tracks that are not synchronized might be an indicator that you must adjust some values to allow for complete processing. -dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID, which includes a storage image ID. Example: IBM.1750-68FA120 -scope si | lss (Required) Specifies the scope of the data to be returned: storage image (si) or logical subsystem (lss). -lss LSS_ID (Required). Specifies the master logical subsystem (LSS) that receives the showgmiroos command. Accepts a fully qualified master LSS ID, which
509
includes either the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. The LSS ID is two hexadecimal digits in the range 00 - 1F (1750 only). Example of a fully qualified LSS ID: IBM.1750-68FA120/10 session_ID (Required). Specifies the session to display. A session ID is a Global Mirror session number that you assign in the 01 - FF hexadecimal range or the 1 - 255 decimal range. If you specify the dash (-), this parameter information is automatically supplied.
Example
A separate example is not shown for the 1750 as the information is the same for both. The only difference is the machine type designation, 2107 versus 1750. Invoking the showgmiroos command
dscli>showgmiroos dev IBM.2107-75FA120 -scope si -lss 10 01

Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Scope IBM.2107-75FA120 Session 01 OutOfSyncTracks 3

The following supplies information that you can use to help you understand the output that is generated from this command. Scope Indicates the scope of the returned information (storage image or logical subsystem). Session Indicates the Global Mirror session number. OutOfSyncTracks Indicates the number of unsynchronized tracks.
Global Mirror session commands

This section contains commands that are used to create, modify, and delete Global Mirror sessions and to display Global Mirror session information. Use the following commands to create, modify, and delete Global Mirror sessions and to display Global Mirror session information: v mksession v chsession v lssession v rmsession The mksession command opens a Global Mirror session. The chsession command allows you to modify a Global Mirror session.
510
The lssession command generates a report that displays a list of Global Mirror sessions for a logical subsystem (LSS) and information regarding the volumes associated with each session in the list. The rmsession command closes an existing Global Mirror session.
chsession
The chsession command allows you to modify a Global Mirror session.
chsession -dev -volume volume_ID . . . storage_image_ID Session_ID - -lss ID -action add remove
Parameters
-dev storage_image_ID (Optional). Specifies the ID of the storage image containing the logical subsystem. The storage image ID includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the LSS ID and you do not specify a value for the devid variable in your profile file. Example: IBM.1750-68FA120 -lss ID (Required). The logical subsystem (LSS) ID for the Global Mirror session. The format of the LSS ID is a hexadecimal number in the range 00 - 1F (1750 only). Accepts a fully qualified LSS ID, which includes either the storage image ID or a shortened version without the storage image ID if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -action add | remove (Required). add remove Specifies that volumes be removed from the session. -volume volume_ID . . . (Required). Specifies an array of one or more volume IDs or volume ID ranges to be added or removed for the Global Mirror session. All volumes must share a common logical subsystem. To specify a range of volume IDs, you must separate the volume IDs with a hyphen. To specify a combination of one or more volume IDs and a range of volume IDs, separate the volume IDs and ranges with commas. Do not qualify the volume ID with the storage image ID. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). Example of a volume ID: 0010 Example of a range of volume IDs: 0010-001F Specifies that volumes be added to the session.
511
Example of multiple volume IDs and ranges: 0100-010F,0180-018F,0120 Session_ID | (Required). Specifies the Global Mirror session that is modified for this session ID. A session ID is a hexadecimal number in the range 01 - FF. If you specify the dash (-), this parameter information is automatically supplied. Example of a session ID: 01
Example (1750)
Invoking the chsession command
dscli>chsession -dev IBM.1750-68FA120 -lss 10 -action add -volume 1000-1010 01

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Global Mirror session 01 successfully modified.
mksession
The mksession command opens a Global Mirror session.
mksession -dev storage_image_ID -lss ID -volume volume_ID . . . Session_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical subsystem. Example: IBM.1750-68FA120 -lss ID (Required). Creates a Global Mirror session for this logical subsystem. Accepts a fully qualified LSS ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified. The LSS ID is a hexadecimal number in the range of 00 - 1F (1750 only). Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -volume volume_ID . . . (Optional). Specifies an array of one or more volume IDs or a range of volume IDs to be included in the Global Mirror session. All volumes must share a common logical subsystem. To specify a range of volume IDs, you must separate the volume IDs with a hyphen. To specify a combination of one or more volume IDs and a range of volume IDs, separate the volume IDs and ranges with commas. Do not qualify the volume ID with the storage image ID. The volume ID is a 32 bit number that can be represented as 4 hexadecimal digits in the form of
512
XYZZ where X is the address group (0 - 1), XY together is the logical subsystem number 00 - 1E (for 1750) , and ZZ is the volume number (00 - FF). Example of a volume ID: 0010 Example of a range of volume IDs: 0010-001F Example of multiple volume IDs and ranges: 0100-010F,0180-018F,0120 Session_ID | (Required). Specifies the session ID for which Global Mirror processing is allowed. A session ID is a hexadecimal number in the range 01 - FF. If you specify the dash (-), this parameter information is automatically supplied. Example of a session ID: 01
Example (1750)
Invoking the mksession command
dscli>mksession -dev IBM.1750-68FA120 -lss 10 volume 1000-100F 01

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Global Mirror session ID 01 successfully opened.
lssession
The lssession command displays a list of Global Mirror sessions for a logical subsystem (LSS) and information regarding the volumes of each session in the list.
lssession -dev storage_image_ID -s -l LSS_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for the logical subsystem. Example: IBM.1750-68FA120 -s -l (Optional). Displays the session IDs. You cannot use the -l and the -s parameters together. (Optional). Displays the default output. You cannot use the -l and the -s parameters together.
LSS_ID | (Required). Specifies the logical subsystem (LSS) ID for the Global Mirror session. The format of the LSS ID is a hexadecimal value in the range 00 - 1F (1750 only). This parameter accepts a fully qualified LSS ID, which includes the storage image ID, or a shortened version without the storage image ID if the -dev parameter is specified.
513
If you specify the dash (-), this parameter information is automatically supplied. Example of a fully qualified LSS ID: IBM.1750-68FA120/10
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. The following tables represent the headers that are displayed on the output report that is associated with the lssession command using the -l parameter. A separate example is not shown for the 1750 because the information is the same for both machine types. The only difference is the machine type designation, 2107 versus 1750. When you use the -s parameter with the lssession command only 3 ID items are displayed in the resulting report: LSSID, SessionID, and VolumeID. A separate example is shown for this scenario. Invoking the lssession command using the -l parameter

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 Volume Status Active
LSSID IBM.210775FA120 /10 IBM.210775FA120 /10 IBM.210775FA120 /10 IBM.210775FA120 /10 IBM.210775FA120 /10 IBM.210775FA120 /10
Session 01
Status Normal
Volume IBM.210775FA120 /1001 IBM.210775FA120 /1002 IBM.210775FA120 /1003 IBM.210775FA120 /1011 IBM.210775FA120 /1012 IBM.210775FA120 /1013
01
Normal
Active
01
Normal
Active
02
Normal
Active
02
Normal
Remove Pending Join Pending
02
Normal
Primary Status Primary Full Duplex
Secondary Status Secondary Simplex
FirstPass Complete True
AllowCascading Disabled
514
Primary Status Primary Full Duplex Primary Full Duplex Primary Full Duplex Primary Simplex Primary Simplex
Secondary Status Secondary Simplex Secondary Simplex Secondary Simplex Secondary Simplex Secondary Simplex
FirstPass Complete True
AllowCascading Disabled
True
Disabled
True
Disabled
True
Disabled Disabled
False
Invoking the lssession command using the -s parameter

dscli>lssession -s dev IBM.2107-75FA120 10

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: IBM.2107-75FA120 LSSID 10 10 10 10 10 10 Session 01 01 01 02 02 02 Volume 1001 1002 1003 1011 1012 1013

LSSID Specifies the unique identifier that is assigned to this logical subsystem object. The LSS ID is a hexadecimal value in the range 00 - 1F (1750 only). Session Specifies the Session ID number that you assigned in the 01 - FF hexadecimal range or the 1 - 255 decimal range. Status Specifies the state of the session. One of the following values is displayed: CG in progress Indicates that the consistency group of the session is in progress. Increment Pending Indicates that the Increment process is in progress.
515
Normal Indicates that the session is in normal state. Volume Specifies the volume ID. If no volume is active for the session a null (-) value is displayed. Volume Status Specifies the status of the volume in the session. One of the following values is displayed: Join Pending Indicates that the volume is not active for the current session. However, it will be added to the session in the next cycle. Remove Pending Indicates that the volume is active for the current session. However, it will be removed in the next cycle. Active Indicates that the volume is an active member of the session. Primary Status Specifies the primary remote copy and mirror status of the volume. One of the following values is displayed: Primary Simplex Indicates that the volume is not part of a remote mirror and copy relationship. Primary Copy Pending Indicates that the volume is primary in a remote mirror and copy relationship and the relationship is in a Copy Pending state. Primary Full Duplex Indicates that the volume is primary in a remote mirror and copy relationship and the relationship is in a Full Duplex state. Primary suspended Indicates that the volume is primary in a remote mirror and copy relationship and the relationship is suspended. - (null) Indicates that there are no active volumes for the session. Secondary Status Specifies the primary remote copy and mirror status of the volume. One of the following values is displayed: Secondary Simplex Indicates that the volume is not part of a remote mirror and copy relationship. Secondary Copy Pending Indicates that the volume is secondary in a remote mirror and copy relationship and the relationship is in a Copy Pending state. Secondary Full Duplex Indicates that the volume is secondary in a remote mirror and copy relationship and the relationship is in a Full Duplex state. Secondary suspended Indicates that the volume is secondary in a remote mirror and copy relationship and the relationship is suspended.
516
- (null) Indicates that there are no active volumes for the session. FirstPass Complete Specifies whether the first cycle of the volume in the global mirror relationship has ended. The value displayed is either True or False. AllowCascading Specifies whether the volume can be a secondary in a remote mirror and copy relationship. The value displayed is either Enabled or Disabled.
rmsession
The rmsession command closes an existing Global Mirror session.
rmsession -dev storage_image_ID -lss ID -quiet Session_ID -
Parameters
-dev storage_image_ID (Optional). Specifies the ID of the storage image that contains the logical subsystem. The storage image ID includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified LSS ID. Example: IBM.1750-68FA120 -lss ID (Required). Specifies the logical subsystem (LSS) ID for the Global Mirror session that is being closed. The format of the LSS ID is a hexadecimal value in the range 00 - 1F (1750 only). This parameter accepts a fully qualified LSS ID, which includes the storage image ID, or shortened version without the storage image ID if the -dev parameter is specified. Example of a fully qualified LSS ID: IBM.1750-68FA120/10 -quiet (Optional). Turns off the confirmation prompt for this command. Session_ID | (Required). Specifies the session ID on which Global Mirror processing is to be closed. A session ID is a hexadecimal number in the range 01 - FF or a decimal number in the range 01 - 255 that you assigned. If you specify a dash (-), this parameter information is automatically supplied. Example of a session ID: 01
Example (1750)
Invoking the rmsession command
dscli>rmsession -dev IBM.1750-68FA120 -lss 10 01

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Are you sure you want to stop Global Mirror Session ID 01? y/n Y Global Mirror Session ID 01 successfully stopped.
517
Audit commands
This section contains commands that are used for audit logging. Use the offloadauditlog command to create activity reports for the consoles and storage units. The offloadauditlog command generates an activity report for a console that includes basic information, such as, a list of who logged in, when they logged in, and what they did during their session.
offloadauditlog
The offloadauditlog command provides an activity report for a console (identified as smc1 or smc2). The report includes basic information, such as, a list of who logged in, when they logged in, and what they did during their session.
offloadauditlog -logaddr smc1 smc2 audit_log_file -quiet
Parameters
Notes: 1. Only users with administrator authority are authorized to use this command. 2. A separate log entry is added each time a resource is created, deleted, modified. Entries are added to the audit file only after the operation has completed. 3. You must periodically extract the log using the offloadauditlog command and save the log file in a directory of your choice. The log file is automatically reduced (old entries removed first) by the subsystem so that it does not consume more than 50 megabytes of disk storage. When the log is 60% full, an entry (Audit_Log_At_60%) is placed in the audit log. Another entry is added when the log is 75% (Audit_Log_At_75%) full. At 100%, the log is reduced to 50% full. -logaddr smc1|smc2 (Required) Specifies that the audit log be offloaded for the designated storage management console. The designated storage management console must be configured and available to offload the audit log successfully. -quiet (Optional) Specifies that the confirmation prompt be turned off. audit_log_file (Required) Specifies the file name to which the audit log entries are extracted. Note: If you specify a file name that contains prior log entries, these entries are overwritten with the current data.
Example
Invoking the offloadauditlog command
518
dscli>dscli> offloadauditlog logaddr smc1 auditlog-200509.txt

Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0: Audit log successfully offloaded from smc1 to file auditlog-200509.txt.
Representative report The following is an example of the report information that is extracted when you use the offloadauditlog command (the wrapping is done simply for clarity and is not representative of your actual report):
U,2005/10/04 15:08:46:834 MST,admin,1,,W,1002,User_Login_Fail,,1, "IP = N996304B.tucson.ibm.com/9.11.178.201" U,2005/10/04 15:29:37:432 MST,admin,1,,W,1001,User_Login_Expire,,0, "IP = N996304B.tucson.ibm.com/9.11.178.201" U,2005/10/04 15:32:56:979 MST,admin,1,,N,1000,User_Login,,0, "IP = N996304B.tucson.ibm.com/9.11.178.201" U,2005/10/04 15:34:21:020 MST,admin,1,,N,1000,User_Login,,0, "IP = N996304B.tucson.ibm.com/9.11.178.201" U,2005/10/05 16:54:32:171 MST,admin,1,,N,1103, User_Password_Change,,be741104,"userName = admin" S,2005/10/06 00:01:10:239 MST,,1,,W,1200,Audit_Log_At_60%,,,"" U,2005/10/06 00:23:09:817 MST,admin,1,IBM.2107-AZ12341,N,2050, Array_Create,A0,0,"A0" U,2005/10/06 00:23:10:518 MST,admin,1,IBM.2107-AZ12341,N,2060, Rank_Create,R0,-1,"R0" U,2005/10/06 00:23:12:110 MST,admin,1,IBM.2107-AZ12341,N,2070, XPool_Create,P0,0,"P0" U,2005/10/06 00:23:12:761 MST,admin,1,,N,2073,XPool_Assign_Rank,,,"" U,2005/10/06 00:23:16:947 MST,admin,1,IBM.2107-AZ12341,N,2090, Volume_Create,1000,0,"1000" U,2005/10/06 00:23:17:187 MST,admin,1,IBM.2107-AZ12341,N,2090, Volume_Create,1001,,"1001" S,2005/10/06 00:23:24:508 MST,,1,,W,1201,Audit_Log_At_75%,,,"" U,2005/10/06 12:47:16:345 MST,admin,1,IBM.2107-AZ12341,N,2092, Volume_Delete,2005,0,"2005" U,2005/10/06 12:47:16:656 MST,admin,1,IBM.2107-AZ12341,N,2092, Volume_Delete,2006,-1,"2006"
Audit Log file definitions

Fields are output in comma-separated (CSV) format. This format makes it easy to import the file into a spreadsheet. The Input Parms field is a special case. It uses the CSV format internally to separate one input field from the next. To manage this, the entire Input Parms field is enclosed in double quotation marks.
519
Field Source
Format 1 char
Description Specifies the source of the log entry: S Represents a server event that is not associated with a user action Represents a user-requested action Represents a continuation line for additional input attributes. There can be multiple C entries for a given user-requested (U) log entry.
Timestamp
YYYY/MM/DD HH:MM:SS:MMM TMZ 1 - 16 char 1 char, a 1 or 2
Represents the date, time, and time zone of the log entry. Represents the user account that is making the request. Represents the management console that processed the user request. Represents the storage image ID that consists of the following values: manufacture, type, and serial number. Represents the following message types: N = notification, W = warning, and C = critical. Represents the unique identifier that is associated with the activity that is represented by the log entry. A text description that corresponds to the Entry ID. Represents a unique identifier that identifies the object. Represents the final result code.
User MC
Device
16 char
NWC
1 char
Entry ID
4 char
Entry name Object ID
20 char max 5 char max
Exit code
8 char
520
Field Input Parameters
Format 160 char max
Description Represents unformatted text that includes input parameters in the format: attr1 = value1, attr2 = value2 with a comma (,) separator between parameters and double quotation marks around the entire field.
DS6000 remote support and notification commands

This section contains commands that are used to setup your system to enable remote support and notification. Remote support can include outbound support (call home) or inbound support (remote service that is performed by an IBM service representative). Use the following commands to configure settings for remote support for the DS6000: v setplex v showplex v setdialhome v setsmtp v setsnmp v setsim v setcontacinfo v showcontactinfo v testcallhome The setplex command allows you to modify the 1750 storage complex settings. You can associate a unique name with the 1750, which allows you to open a secure shell connection to a storage unit for remote support. The showplex command generates a report that displays the detailed properties of the specified 1750 storage complex. The report that is generated by this command also reflects the changes that you have made with the setdialhome, setsim, setsmtp, setsnmp, and setplex commands. The setdialhome command activates the Call Home function. The setsmtp command allows you to modify the storage image Simple Mail Transport Protocol (SMTP) and activate the e-mail notification settings. The setsnmp command activates the Simple Network Management Protocol (SNMP) trap notification feature, which sends notifications using SNMP when a problem occurs on a storage unit. The setsim command activates the SIM notification feature for zSeries hosts. A SIM is a service information message that contains data storage and data retrieval errors.
521
The setcontactinfo command allows you to supply contact information for your storage system administrator. When you use any of the remote support features, this information is sent to IBM so that an IBM service representative can contact you. The showcontactinfo command generates a report that displays customer contact information for the storage complex. The testcallhome command initiates a call home test by creating a test problem record.
setplex
The setplex command allows you to modify the 1750 storage complex settings. You can associate a unique name with the 1750 which allows you to open a secure shell connection to a storage unit for remote support.
setplex -name storage_complex_name -desc storage_complex_description
storage_image_ID -acct account -allowrssh enable disable
Parameters
Note: You can view the changes of a processed setplex command by issuing the showplex command. -name storage_complex_name (Optional) Specifies the user-defined name for the storage complex. -desc storage_complex_description (Optional) Specifies the user-defined description for the storage complex. -acct account (Optional) Specifies the user-defined account number. -allowrssh enable | disable (Optional) Specifies that a secure shell connection to the storage unit be opened. storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the values associated with the manufacturer, machine type, and serial number.
Example
Invoking the setplex command
dscli>setplex -name primary_1750 desc Production volumes acct IBM Storage -allowrssh enable IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Storage Plex primary_1750 successfully modified
522
showplex
The showplex DS6000 command displays detailed properties of a 1750 storage complex. Detailed properties include your names, descriptions, and notification settings for the storage complex.
showplex storage_image_ID -
Parameters
Note: The showplex command displays the current settings for the parameters that are associated with the setplex, setdialhome, setsim, setsmtp, and setsnmp commands. Issue the showplex command after you have processed each of these commands so that you can view that your changes have been activated in your system. storage_image_ID | (Required) Specifies the storage image ID. A storage image ID consists of the values for manufacturer, machine type, and serial numbers. If you specify the dash (-), this parameter information is automatically supplied.
Example
For this command and all other DS CLI show commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. Invoking the showplex command

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 Allowrssh Dialhome Disabled SNMPinfo 9.11.123. 123:500 SNMPcomname SNMP community
Name storage unit 1
Desc My storage unit 1
Acct
SNMP Disabled
ABC Disabled Company
SMTPserver
SIM DASDlevel
SIMDASDnotify 1
SIMmedialevel None
SIMmedianotify 1
SIMsulevel None
SIMsunotify 1
eMailnotify Enabled
Dialhomemodem Enabled
9.11.123. None 123:300

Name Specifies the name that you have assigned to the designated storage unit. Desc Specifies the description that you have assigned to the designated storage unit.
523
Acct
Specifies the account name that you have assigned to the designated storage unit.
Allowrssh Specifies whether you can open access to the remote support shell connection (RSSH) to the designated storage unit. Dialhome Specifies, if enabled, that the action to call home is activated when a problem is encountered. SNMP Specifies whether you want the SNMP traps that are generated by the storage-complex to be sent to the IP address that you have designated with the setsnmp command. SNMPinfo Specifies the SNMP IP address and port information where SNMP alerts are sent. The IP address and port information are separated with a colon. Multiple IP address and port pairs are separated with commas and no space before or after each comma. SNMPcomname Specifies the SNMP community name. An SNMP community is the group that devices and management stations that run SNMP belong to. An SNMP community helps define where information is sent. The community name identifies the group, and an SNMP device or agent can belong to more than one SNMP community. SNMP does not respond to requests from management stations that do not belong to one of its communities. There are two SNMP default communities: v Write = private v Read = public SMTPserver Specifies the SMTP IP address and port. SIMDASDlevel Specifies the service information message (SIM) reporting level for DASD SIMs. One of the following values is displayed: acute serious Indicates an irrecoverable error or a data check with loss of access to data. moderate Indicates that a system path is not operational and performance might be degraded. service Indicates a recoverable error, equipment checks, or data checks. You can defer repair. none Indicates that there are no problems. Indicates an irrecoverable error with possible loss of data.
SIMDASDnotify Specifies the maximum number of DASD service information messages that are sent after the first message.
524
SIMMedialevel Specifies the SIM reporting level for media SIMs. One of the following values is displayed: acute serious Indicates an irrecoverable error or a data check with loss of access to data. moderate Does not apply to SIM media. service Indicates a recoverable error, equipment checks, or data checks. You can defer repair. none Indicates that there are no problems. Does not apply SIM media.
SIMMedianotify Specifies the maximum number of media service information messages that are sent after the first message. SIMsulevel Specifies the SIM reporting level for storage unit SIMs. One of the following values is displayed: acute serious Indicates an irrecoverable error or a data check with loss of access to data. moderate Indicates that a system path is not operational and performance might be degraded. service Indicates a recoverable error, equipment checks, or data checks. You can defer repair. none Indicates that there are no problems. Does not apply SIM storage unit level.
SIMsunotify Specifies the maximum number of additional storage unit service information messages that are sent after the first message. eMailnotify Specifies, if enabled, that when service is required problem notifications be sent to an e-mail address that is specified by the -contactemail parameter of the setcontactinfo command. Dialhomemodem Specifies that an IP connection is available that allows the use of a modem in the Call Home support program. Note: You cannot use the DS CLI to configure the modem or to test modem availability and connection. Use the DS Storage Manager to establish these settings.
525
setdialhome
The setdialhome command activates the Call Home feature.
setdialhome -action enable disable storage_image_ID
Parameters
Notes: 1. The setdialhome command is not associated with the modem Call Home feature. DS CLI cannot be used to configure the modem or test modem availability and connection. 2. Before using the setdialhome command, you must ensure the following: v The setsmtp command must be enabled. v The required contact information must be set in place through the use of the setcontactinfo command. This information consists of the following: Company name Country State or province Primary contact phone number 3. You can view the changes of a processed setdialhome command by issuing the showplex command. -action enable | disable (Optional) Enables or disables the Call Home feature. storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the values associated with the manufacturer, machine type, and serial number.
Example
Invoking the setdialhome command
dscli>setdialhome -action enabled IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The dial home settings were successfully modified
setsmtp
The setsmtp DS6000 command modifies the storage image Simple Mail Transport Protocol (SMTP) and activates the e-mail notification settings.
setsmtp -server smtp_server_IP:port_number -emailnotify on off
526
storage_image_ID
Parameters
Note: You can view the changes of a processed setsmtp command by issuing the showplex command. -server smtp_server_IP:port_number . . . (Optional) Specifies the SMTP port and IP address where a message is sent in the event of a problem. You must separate the IP address and the port with a colon. Do not include blank spaces. Example: 9.11.242.56:500 -emailnotify on | off (Optional) Specifies that an e-mail notification be sent to the e-mail address that is specified by the setcontactinfo command with the -contactemail parameter. Note: Before you process the setsmtp command with this parameter, run the showcontactinfo command to ensure that a contact e-mail address has been defined. If a contact e-mail address has not been defined, process the setcontactinfo command with the -contactemail parameter to allow you to receive notifications. storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the values associated with the manufacturer, machine type, and serial number.
Example
Invoking the setsmtp command
dscli>setsmtp server 9.11.242.12:500 IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SMTP settings were successfully modified
setsnmp
The setsnmp command activates the Simple Network Management Protocol (SNMP) trap notification feature, which sends notifications using SNMP when a problem occurs on a storage unit. Use the command to set the SNMP addresses for the notifications. This command is only used with the DS6000.
setsnmp -action enable disable -info snmp_IP:port . . . storage_image_ID -comname snmp_community_name
527
Parameters
Note: You can view the changes of a processed setsnmp command by issuing the showplex command. -action enable | disable (Optional) Enables or disables the SNMP notification feature. -info snmp_IP:port . . . (Optional) Specifies the SNMP port and IP address where a message is sent in the event of a problem. You must separate the IP address and the port with a colon. Multiple SNMP IP addresses and port pairs must be separated with commas. Do not include white spaces. Example: 9.11.242.56:500,9.11.242.79:501 -comname snmp_community_name (Optional) Specifies the SNMP community name. storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the values associated with the manufacturer, machine type, and serial number.
Example
Invoking the setsnmp command
dscli>setsnmp info 9.11.242.7:161 IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SNMP settings were successfully modified
setsim
On zSeries hosts, data storage and data retrieval errors are recorded and can be offloaded. A service information message (SIM) provides the error information. The setsim command activates the SIM notification feature.
setsim -dasdlevel acute moderate none serious service -dasdnotify dasd_max_notifications
-medialevel
acute moderate none serious service
-medianotify
media_max_notifications
528
storage_image_ID -sulevel acute moderate none serious service -sunotify su_max_notifications
Parameters
Note: You can view the changes of a processed setsim command by issuing the showplex command. -dasdlevel acute | moderate | none | serious | service (Optional) Specifies the reporting level for DASD service information messages. -dasdnotify dasd_max_notifications (Optional) Specifies the maximum number of times that service information messages are offloaded for DASD service information messages. You can enter 0 to 5. -medialevel acute | moderate | none | serious | service (Optional) Specifies the reporting level for media service information messages. -medianotify media_max_notifications (Optional) Specifies the maximum number of times that service information messages are offloaded for media service information messages. You can enter 0 to 5. -sulevel acute | moderate | none | serious | service (Optional) Specifies the reporting level for storage unit service information messages. -sunotify dasd_max_notifications (Optional) Specifies the maximum number of times that service information messages are offloaded for storage unit service information messages. You can enter 0 to 5. storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the values associated with the manufacturer, machine type, and serial number.
Example
Invoking the setsim command
dscli>setsim dasdnotify 3 IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The SIM settings were successfully modified
setcontactinfo
The setcontactinfo DS6000 command provides contact information for your storage system administrator. When you use any of the remote support features, this information is sent to IBM so that an IBM service representative can contact you.
529
setcontactinfo -companyname company_name -companyaddr company_address
-shipphone
phone_number none
-shipext
extension_number none
-shiploc
building_location
-shipcity
city
-shipstate
state_or_province
-shippostalcode
postal_code
-shipcountry
country
-contactname
contact_name
-contactpriphone
primary_phone_number
-contactpriext
primary_extension_number none
-contactaltphone
alternate_phone_number none
-contactaltext
alternate_extension_number none
-contactemail
primary_email_address
storage_image_ID
Parameters
-companyname company_name (Required, if it is not currently set) Specifies your company name. This parameter is required only if the information has not previously been designated. -companyaddr company_address (Optional) Specifies the address of the company. Enclose the address in double quotation marks. Example 9000 S. Rita Rd Tucson AZ 85744 -shipphone phone_number | none (Optional) Specifies the telephone number to contact regarding the equipment parts that are being shipped. You can enter a country code, an area code, and a telephone number. Separate each code of the telephone number with a hyphen (for example, 520-555-5555). Notes: 1. The phone number can be no more than 22 characters. 2. Specify -shipphone none if you want to delete the ship phone contact number. When you specify -shipphone none, the ship phone number and the ship phone contact extension number is set to zero. 3. If you want to change the ship phone contact number, enter a new number for the command. The new number overrides what is there currently. This does not change the ship phone contact extension number. You must specify that separately.
530
For example, your current ship phone contact number and extension is 520-555-5555 4398 and you want to change it to 520-888-8888 2411. Enter the DS CLI setcontactinfo command as follows:
dscli>setcontactinfo -shipphone 520-888-8888 -shipext 2411 IBM.1750-68FA120
-shipext extension_number | none (Optional) Specifies the extension number of the ship phone contact number. Notes: 1. The extension number can be no more than 6 characters. 2. Specify -shipext none when you want to delete the extension number. 3. Specify -shipext and the extension number when you want to override an existing extension number. 4. You cannot specify the extension number by itself. There must be an entry for the ship phone contact number. -shiploc building_location (Required, if it is not currently set) Specifies the building location where your equipment parts are generally shipped. Enclose the location in double quotation marks. This parameter is required only if the information has not previously been designated. -shipcity city (Optional) Specifies the city where your equipment parts are generally shipped. Example: Tucson -shipstate state_or_province (Required, if it is not currently set) Specifies the state or province where your equipment parts are generally shipped. This parameter is required only if the information has not previously been designated. Example: Arizona -shippostalcode postal_code (Optional) Specifies the zip or postal code that is associated with the state or province where your equipment parts are shipped. -shipcountry country (Required, if it is not currently set) Specifies the country or region where your equipment parts are shipped. This parameter is required only if the information has not previously been designated. Table 5 on page 533 provides a list of the ISO country or region codes that you can use. This field also directs the Call Home e-mail records to the appropriate e-mail receiver for the geography of the machine. -contactname contact_name (Optional) Specifies the name of the storage system administrator who can be contacted by IBM service personnel. -contactpriphone primary_phone_number (Required, if it is not currently set) Specifies the primary telephone number for IBM service personnel to use to contact the storage system administrator.
531
You can enter a country or region code, an area code, and a telephone number. Separate each code of the telephone number with a hyphen (for example, 520-555-5555). Notes: 1. The phone number, including the country code, cannot be more than 22 characters. 2. An account cannot exist without a primary contact phone number. This number can never be set to zero. 3. Specify the -contactpriphone parameter and the new phone number to change the existing primary phone contact number. The new number overrides the existing number. -contactpriext extension_number | none (Optional) Specifies the extension number of the primary contact phone number. Notes: 1. The extension number can be no more than 6 characters. 2. Specify -contactpriext none when you want to delete the extension number. 3. Specify -contactpriext and the extension number when you want to override an existing extension number. 4. You cannot specify the extension number by itself. There must be an entry for the primary contact phone number. -contactaltphone alternate_phone_number | none (Optional) Specifies an alternate telephone number for IBM service personnel to use to contact the storage system administrator. You can enter a country or region code, an area code, and a telephone number. Separate each code of the telephone number with a hyphen (for example, 520-555-4444). Notes: 1. The phone number can be no more than 22 characters. 2. Specify -contactaltphone none if you want to delete the alternate phone contact number. When you specify -contactaltphone none, the alternate phone number and the alternate phone contact extension number is set to zero. 3. If you want to change the alternate phone contact number, enter a new number for the command. The new number overrides the number that is currently there. This does not change the alternate phone contact extension number. You must specify that separately. For example, your current ship phone contact number and extension is 520-555-5555 4398 and you want to change it to 520-888-8888 2411. Enter the DS CLI setcontactinfo command as follows:
dscli>setcontactinfo -contactaltphone 520-888-8888 -contactaltext 2411 IBM.1750-68FA120
-contactaltext extension_number | none (Optional) Specifies the extension number of the alternate contact phone number.
532
Notes: 1. The extension number can be no more than 6 characters. 2. Specify -contactaltext none when you want to delete the extension number. 3. Specify -contactaltext and the extension number when you want to override an existing extension number. 4. You cannot specify the extension number by itself. There must be an entry for the alternate contact phone number. -contactemail primary_email_address (Optional) Specifies the e-mail address for IBM service personnel to use to contact the storage system administrator. This e-mail address is also used when you activate the system problem notification program. Notes: 1. This parameter is required if you intend to use the Call Home function. 2. This parameter is required if you intend to designate the -emailnotify parameter of the setsmtp command. storage_image_ID (Required) This parameter accepts a fully qualified storage image ID. A storage image ID consists of the manufacturer, machine type, and serial number.
Example
Invoking the setcontactinfo command
dscli>setcontactinfo companyname IBM shipstate AZ -shiploc "bldg1300" -shipcountry US contactpriphone 520-799-8001 IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The contact information settings were successfully modified Table 5. Country and Region Codes ISO Country or Region Code AF AL DZ AS AD AO AI AQ AG AR AM AW Business Unit EMA EMA EMA APS EMA EMA LAG LAG LAG LAG EMA LAG Country or Region Name Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba State
533
Table 5. Country and Region Codes (continued) ISO Country or Region Code AU AT AZ BS BH BD BB BY BE BZ BJ BM BT BO BA BW BV BR IO BN BG BF BI KH CM CA CA CA CA CA CA CA CA CA CA CA CA CA CV Business Unit APS EMA EMA LAG EMA APS LAG EMA EMA LAG EMA LAG APS LAG EMA EMA APS LAG APS APS EMA EMA APS APS EMA CAN CAN CAN CAN CAN CAN CAN CAN CAN CAN CAN CAN CAN EMA Country or Region Name Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Brunei Darussalam Bulgaria Burkina Faso Burundi Cambodia Cameroon Alberta British Columbia Manitoba New Brunswick Newfoundland Nova Scotia Northwest Territorie Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Cape Verde AB BC MB NB NL NS NT NU ON PE QC SK YT State
534
Table 5. Country and Region Codes (continued) ISO Country or Region Code KY CF TD CL CN CX CC CO KM CD CG CK CR CI HR CU CY CZ DK DJ DM DO EC EG SV GQ ER EE ET FK FO FJ FI FR GF PF TF GA GM Business Unit LAG EMA EMA LAG APN APS APS LAG APS EMA EME APS LAG EMA EMA LAG EMA EMA EMA EMA LAG LAG LAG EMA LAG EMA EMA EMA EMA APS EMA APS EMA EMA LAG APS APS EMA EMA Country or Region Name Cayman Islands Central African Republic Chad Chile China/Hong Kong Christmas Islands Cocos (Keeling) Island Colombia Comoros Congo Democratic Republic Congo Peoples Republic Cook Islands Costa Rica Cote dIvoire (Ivory Croatia Cuba Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands (Malvinas) Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia State
535
Table 5. Country and Region Codes (continued) ISO Country or Region Code GE DE GH GI GR GL GD GP GU GT GN GW GY HT HM VA HN HK HU IS IN ID IR IQ IE IL IT JM JP JO KZ KE KI KP KR KW KG LA LV Business Unit EMA EMA EMA EMA EMA EMA LAG LAG APS LAG EMA APS LAG LAG APS EMA LAG APN EMA EMA APS APS EMA EMA EMA EMA EMA LAG APN EMA EMA EMA EMA APN APN EMA EMA APN EMA Country or Region Name Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Holy See (Vatican City State) Honduras Hong Kong Hungary Iceland India Indonesia Iran (Islamic Republic of) Iraq Ireland Israel Italy Jamaica Japan Jordan Kazakhstan Kenya Kiribati Korea Democratic Peoples Republic of Korea Republic of Kuwait Kyrgyzstan Lao Peoples Democratic Republic Latvia State
536
Table 5. Country and Region Codes (continued) ISO Country or Region Code LB LS LR LY LI LT LU MO MK MG MW MY MV ML MT MH MQ MR MU YT MX FM MD MC MN MS MA MZ MM NA NR NP NL AN NC NZ NI NE NG Business Unit EMA EMA EMA EMA EMA EMA EMA APS EMA APS EMA APS APS EMA EMA APS LAG EMA LAG APS LAG APS EMA EMA APN EMA EMA EMA APS EMA APS APS EMA LAG APS APS LAG EMA EMA Country or Region Name Lebanon Lesotho Liberia Libyan Arab Jamahiriya Liechtenstein Lithuania Luxembourg Macau Macedonia Former Yugoslav Republic of Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Federated States of Moldava Republic of Monaco Mongolia Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria State
537
Table 5. Country and Region Codes (continued) ISO Country or Region Code NU NF MP NO OM PK PW PS PA PG PY PE PH PN PL PT PR QA RE RO RU RW SH KN LC PM VC WS SM ST SA SN CS SC SL SG SK SI Business Unit EMA EMA APS EMA EMA EMA APS EMA LAG EMA LAG LAG APS APS EMA EMA DOM EMA EMA EMA EMA EMA EMA LAG APS LAG LAG APS EMA APS EMA EMA EMA EMA EMA APS EMA EMA Country or Region Name Niue Norfolk Island Northern Mariana Island Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Reunion Romania Russian Federation Rwanda Saint Helena Saint Kitts and Nevis Saint Lucia Staint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principle, Democratic Republic of Saudi Arabia Senegal Serbia and Nontenegro Seychelles Sierra Leone Singapore Slovakia Slovenia State
538
Table 5. Country and Region Codes (continued) ISO Country or Region Code SB SO ZA GS ES LK SD SR SJ SZ SE CH SY TW TJ TZ TH TL TG TK TO TT TN TR TM TC TV UG UA AE GB US US US US US US US Business Unit APS EMA EMA APS EMA APS EMA APS EMA EMA EMA EMA EMA APS EMA EMA APS EMA EMA APS APS LAG EMA EMA EMA APS APS EMA EMA EMA EMA DOM DOM DOM DOM DOM DOM DOM Country or Region Name Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Islands Swaziland Sweden Switzerland Syrian Arab Republic Taiwan Tajikistan Tanzania United Republic of Thailand Timor-Leste (East Timor) Togo Tokelau Tonga Trinidad and Tobago, Republic of Tunisia Turkey Turkmenistan Turks and Caicos Island Tuvalu Uganda Ukraine United Arab Emirates United Kingdom Alaska Alabama Arkansas Arizona California Colorado Connecticut AK AL AR AZ CA CO CT State
539
Table 5. Country and Region Codes (continued) ISO Country or Region Code US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US US Business Unit DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM DOM Country or Region Name District of Columbia Delaware Florida Georgia Hawaii Iowa Idaho Illinois Indiana Kansas Kentucky Louisiana Massachusetts Maryland Maine Michigan Minnesota Missouri Mississippi Montana North Carolina North Dakota Nebraska New Hampshire New Jersey New Mexico Nevada New York Ohio Oklahoma Oregon Pennsylvania Puerto Rico Rhode Island South Carolina South Dakota Tennessee Texas Utah State DC DE FL GA HI IA ID IL IN KS KY LA MA MD ME MI MN MO MS MT NC ND NE NH NJ NM NV NY OH OK OR PA PR RI SC SD TN TX UT
540
Table 5. Country and Region Codes (continued) ISO Country or Region Code US US US US US US UM UY UZ VU VE VN VG VI WF EH YE ZM ZW Business Unit DOM DOM DOM DOM DOM DOM DOM LAG EMA APS LAG APS LAG LAG APS EMA EMA EMA EMA Country or Region Name Virginia Vermont Washington Wisconsin West Virginia Wyoming United States Minor Uruguay Uzbekistan Vanuatu Venezuela Viet Nam Virgin Islands (British) Virgin Islands (U.S.) Wallis and Futuna Island Western Sahara Yemen Zambia Zimbabwe State VA VT WA WI WV WY
showcontactinfo
The showcontactinfo command displays customer contact information for the storage image.
showcontactinfo storage_image_ID
Parameters
storage_image_ID (Required) Accepts a fully qualified storage image ID. A storage image ID consists of manufacturer, machine type, and serial number.
Example
Invoking the showcontactinfo command

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 companyname IBM companyaddr 9000 S. Rita Rd Tucson Az 85744 shipphone 1-520-7998001shiploc Lab 2000
541
shipcity Tucson shipstate AZ shippostalcode 85744 shipcountry US contactname John Doe contactpriphone 1-520-7998001contactaltphone 1-520-7998002contactemail johndoe@us.ibm.com
testcallhome
The testcallhome DS6000 command initiates a call home test by creating a test problem record.
testcallhome storage_image_ID -
Parameters
Note: The Call Home function has a modem call home feature. The testcallhome command cannot be used to test the modem connection. You must use the DS Storage Manager to configure and test the modem call home feature. storage_image_ID (Required) This parameter accepts a fully qualified storage image ID. A storage image ID consists of manufacturer, machine type, and serial number. If you specify the dash (-), this parameter information is automatically supplied.
Example
Invoking the testcallhome command
dscli>testcallhome IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 A test problem record was successfully created.
DS6000 PE package commands

This section contains commands that are used to create and send information logs to IBM which are then used for problem analysis and resolution. Note: The group of commands described in this section are not supported on a System i system. Use the following commands to create, copy, and send PE packages for the DS6000: v lspe v lsss v mkpe v offloadss v sendpe
542
v sendss The lspe command generates a report that is used by a DS6000 user to find previously created PE package files that are ready to send to IBM. The lsss command generates a report that is used by a DS6000 user to find previously created offloaded statesave files that are ready to send to IBM. The mkpe command creates and copies PE packages from DS6000 nodes to the destination directory on a management node. You must have administrator authority to use the mkpe command. The offloadss command copies state information from nodes to the destination directory on a management node. The sendpe command is used by a DS6000 user to send a previously created PE package to IBM. You must have administrator authority to use the sendpe command. The sendss command is used by a DS6000 user to send previously created offloaded statesave files to IBM. You must have administrator authority to use the sendss command.
offloadss
The offloadss DS6000 command copies state information from nodes to the destination directory on a management node.
offloadss -noftp -retry count storage_image_ID
Parameters
Notes: 1. This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. 2. Only a person with administrator authority can initiate this command. 3. The statesave information is collected in the %MR1750_SM_HOME%\ send2IBM directory and automatically sent to the IBM support Web address. As with the use of the mkpe command, the files that are sent by FTP transfer are automatically moved to the master console subdirectory %MR1750_SM_HOME%\send2IBM\sent\ -noftp (Optional) Specifies that the ftp transfer to IBM be disabled. The default is that ftp transfer is enabled unless this parameter is specified. Note: You cannot use this parameter with the -retry parameter. -retry count (Optional) Specifies the number of times that FTP can be tried after the original FTP transfer has failed. You can specify a value of 0 - 3 with 0 being the default. If you specify 0, no additional FTP transfers are attempted after the initial FTP transfer attempt. Note: You cannot use this parameter with the -noftp parameter.
543
storage_unit_ID (Required) Specifies the storage image ID. A storage image ID consists of manufacturer, machine type, and serial number.
Example
Invoking the offloadss command
dscli>offloadss IBM.1750685FA120

Date/Time: Sun Jan 09 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 offloadss: The following files offloaded from 1750-68FA120: /Program Files/IBM/DS6000StorageManager/SM/send2IBM/ 175051113AB15A.IBM.0.NOPMH.20050327243603.cl0.dumptrace.tgz offloadss: statesave FTPed to IBM: 175051113AB15A.IBM.0.NOPMH.20050327243603.cl0.dumptrace.tgz offloadss: successfully completed.
mkpe
The mkpe command creates and copies PE packages from DS6000 nodes to the destination directory on a management node. The mkpe command is also used to create a PE package from the log and configuration files contained on the storage management console, and the package does not contain any files that are copied from the DS6000 nodes.
mkpe -noftp -retry count -smconly
storage_image_ID -customer customer_name
Parameters
Notes: 1. This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. 2. You must have administrator authority to use the mkpe command. 3. The PE package information is collected on the MC in subdirectory %MR1750_SM_HOME%\send2IBM. You use the mkpe command to collect the information and create the PE package which is then transferred using FTP to the IBM support Web address. 4. PE package files that are successfully transferred to IBM support are automatically moved to the MC subdirectory, %MR1750_SM_HOME%\ send2IBM\sent\. 5. When there is a transfer failure (after attempts to use FTP for the designated number of times), you can use the sendpe command to send the package file later. 6. The mkpe command is processed in the background on the storage server side. This processing can take more than an hour to complete. A message is displayed when the mkpe command is issued that indicates
544
a period of time might pass before the command processing is completed. If you specify the -smconly parameter in your command, no message is displayed. -noftp (Optional) Specifies that the FTP transfer to IBM be disabled. The default is that the FTP transfer is enabled until this parameter is specified. You can send the PE package later by using the sendpe command when you specify the -noftp parameter. A typical use of this parameter is when your MC is located in a network that does not have direct access to the Internet or to IBM support. Another use for this parameter might be when you are experiencing connection problems with IBM. You can create the PE package and send it later using the sendpe command. Note: You cannot use the -noftp parameter with the -retry parameter. -retry count (Optional) Specifies that the FTP transfer to IBM be retried (after the original attempt fails) up to a maximum of three times. The default value is zero (no additional transfer attempts after the initial failure). Note: You cannot use the -retry parameter with the -noftp parameter. -smconly (Optional) Specifies that a PE package be created that includes copies of the log and configuration files that are contained only on the MC. There are no files that are copied from the DS6000 storage nodes for inclusion in this PE package. Note: You must include the -customer parameter when you use the -smconly parameter. -customer customer_name (Required when the -smconly parameter is specified) Specifies the customer name that is associated with the MC PE package. This name must be communicated to or received from IBM support because it is used to identify the PE package. Note: The customer name can contain up to 15 alphanumeric or nonalphanumeric characters. The nonalphanumeric characters must be represented by an underscore. For example, if the original name is global2warm*hot, it is represented as global2warm_hot. Example of a completed MC only pe package file:
1750511SMC0000.mine4results.000.NOPMH.051028223544. cl0.SMCLog.zip
storage_image_ID (Required) Specifies the storage image ID. A storage image ID consists of the manufacturer, machine type, and serial numbers.
Example
The following examples show how you might use the mkpe command in three different situations:
545
Invoking the mkpe command to create, copy and send a PE package from DS6000 nodes to IBM support
dscli>mkpe IBM.1750-68FA120

Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 CMUC00246I mkpe: The task might take more than 1 hour to complete. The following PE package successfully generated and copied from 1750-68FA120: c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A. IBM.0.NOPMH.20050328223544.cl0.pe.zip c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A. IBM.0.NOPMH.20050328223807.cl1.pe.zip PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223807.cl1.pe.zip mkpe successfully completed.
Invoking the mkpe command to create and copy a PE package from DS6000 nodes to the management console.
dscli>mkpe -noftp IBM.1750-68FA120

Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 CMUC00246I mkpe: The task might take more than 1 hour to complete. The following PE package successfully generated and copied from 1750-68FA120: c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A. IBM.0.NOPMH.20050328223544.cl0.pe.zip c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A. IBM.0.NOPMH.20050328223807.cl1.pe.zip mkpe successfully completed.
Invoking the mkpe command to create an MC PEpackage and send it to IBM with a retry count of 3:
dscli>mkpe smconly customer mine4results retry 3 IBM.1750-68FA120

Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 The following SMC PE package successfully generated: c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/1750511SMC0000. mine4results.000.NOPMH.051028223544.cl0.SMCLog.zip PE package successfully sent to IBM: 1750511SMC0000.mine4results.000.NOPMH.051028223544. cl0.SMCLog.zip mkpe successfully completed.
546
sendss
The sendss command is used by a DS6000 user with administrator authority to send previously created offloaded statesave files to IBM. This might be necessary if there was an error during the original FTP of the statesave file.
sendss -retry count - statesave_filename . . .
Parameters
Notes: 1. This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. 2. Only DS6000 users that have administrator authority are authorized to use this command. 3. Use the lsss command with the -state ready parameter to list the statesave files that can be sent to IBM. 4. After the files are sent to IBM, the copies on your system are automatically moved to the %MR1750_SM_HOME%\send2IBM\sent directory. -retry count (Optional) Specifies the number of times to keep trying to send the files by FTP if FTP fails. You can specify a value of 0 - 3. The default is 0 and indicates that you do not want additional attempts to send the files by FTP to take place after the original attempt. statesave_name | ... | (Required) Specifies the file that is to be sent to IBM. A typical filename might look like the following:
175051113AB15A.IBM.0.NOPMH.050318180713.cl0.dumptrace.tgz
Example
Invoking the sendss command
dscli>sendss -retry 3 175051113AB15A.IBM.0.NOPMH.050318180713.cl0.dumptrace.tgz

sends: Statesave sent to IBM: 175051113AB15A.IBM.0.NOPMH.050318180713.cl0.dumptrace.tgz sendss: successfully completed.
sendpe
The sendpe command is used by a DS6000 user with administrator authority to send a previously created PE package to IBM. This might be necessary because there was an error during the original FTP transfer of the package.
sendpe -retry count - pepackage_name . . .
547
Parameters
Notes: 1. 2. 3. 4. 5. This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. Only DS6000 users who have administrator authority can use this command. Use the lspe command with the -state ready parameter to list the PE package files that you want to send to IBM. The PE package files that can be sent have a file extension of pe.zip or SMClog.zip. After the files are sent to IBM, the copies on your system are automatically moved to the %MR1750_SM_HOME%\send2IBM\sent directory.
-retry count (Optional) Specifies that the FTP transfer to IBM be retried (after the original attempt fails) up to a maximum of three times. The default value is zero (no additional transfer attempts after the initial failure). pepackage_name | ... | (Required) Specifies the file that is to be sent to IBM. A typical file name might look like the following:
175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip
Example
Invoking the sendpe command
dscli>sendpe -retry 3 175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip

Date/Time: Sun Aug 11 02:23:49 PST 2004 DSCLI Version: 5.0.0.0 DS: IBM.1750-68FA120 PE package successfully sent to IBM: 175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip sendpe successfully completed.
lsss
The lsss command is used by a DS6000 user to find previously created offloaded statesave files that are ready to send to IBM. These files were created with the offloadss command and must be sent to IBM because there was an error during the original FTP transfer of the statesave file.
lsss -s -l -state ready sending copying sent
Parameters
Note: This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit.
548
-s -l
(Optional) Specifies that only the statesave file names be displayed. You cannot use the -l and the -s parameters together. (Optional) Specifies that the default output plus additional attributes that are identified as long output be displayed. You cannot use the -l and the -s parameters together.
-state ready | sending | copying | sent (Optional) Specifies that the report displays statesave files that meet the designated criteria. For example, if you specify the -state ready parameter, the report returns only those statesave file names that are ready to be sent to IBM. Each option (ready, sending, copy, and sent) that is associated with this parameter represents a specific status that you can designate to narrow the search criteria. The lsss command uses this criteria to search for statesave files. The following values are associated with each option: Ready Specifies that you want to see the files that have been offloaded from the 1750, but not yet sent to IBM. Sending Specifies that the file is in the process of being transferred to IBM. Copying Specifies that the statesave file is in the process of being copied from either of the two storage management consoles. Sent Specifies that the statesave file has been transferred to IBM.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. Invoking the lsss command
dscli>lsss -l -state ready

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: Statesave 175051113 AB15A.IBM. 0.NOPMH. 050318180 713.cl0.dumptrace.tgz 175051113 AB15A.IBM. 0.NOPMH. 050318180 713.cl1.dumptrace.tgz State Ready Lasttime 10/23/2005 00:00:00 PST Size (KB) 5000
Ready
10/23/2005 00:00:10 PST
5000

Statesave Specifies the name of the statesave file.
549
State
Specifies the status that is associated with the statesave file.
Lasttime Specifies the last modified timestamp of the designated statesave file. Size (KB) Specifies the size of the designated statesave file.
lspe
The lspe command is used by a DS6000 user to find previously created PE package files that are ready to send to IBM. These files were created with the mkpe command and must be sent to IBM because there was an error during the original FTP of the PE package file.
lspe -s -l -state ready sending copying sent
Parameters
Note: This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit. -s -l (Optional) Specifies that only the PE package file names be displayed. You cannot use the -l and the -s parameters together. (Optional) Specifies that the default output plus additional attributes that are identified as long output be displayed. You cannot use the -l and the -s parameters together.
-state ready | sending | copying | sent (Optional) Specifies that the report display PE package files that meet the designated criteria. For example, if you specify the -state ready parameter, the report returns only those PE package file names that are ready to be sent to IBM. Each option (ready, sending, copying, and sent) that is associated with this parameter represents a specific status that you can designate to narrow the search criteria. The lspe command uses this criteria when it searches for PE package files. The following values are associated with each option: Ready Specifies that the PE package file was created but not yet sent to IBM. Sending Specifies that the file is in the process of being transferred to IBM. Copying Specifies that the PE package file is in the process of being copied from either of the two storage management consoles. Sent Specifies that the PE package file has been transferred to IBM.
Example
For this command and all other DS CLI list commands, the results are shown in table format to provide clarity. The actual reports do not display as tables. Invoking the lspe command
550
dscli>lspe -l -state ready

Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0 DS: PE Package 175051113 AB15A.IBM. 0.NOPMH. 200503282 23544. cl0.pe.zip 1750511SMC 0000.tucson. 000.NOPMH. 20051023000 000.cl0. SMCLog.zip State Ready Date 10/23/2005 00:00:00 PST Size (KB) 800
Ready
10/23/2005 00:00:10 PST
300

PE Package Specifies the name of the PE package file. State Date Specifies the status associated with the PE package file. Specifies the last modified timestamp of the designated PE package file.
Size (KB) Specifies the size of the designated PE package file.
DS6000 problem log commands

This section contains commands that can track and close problems that might be encountered during the operation of your system. Problems are designated by type and include the following values: hardware, software, test, heartbeat and data loss. Use the following commands to list the problem logs for the DS6000: v closeproblem v lsproblem The closeproblem command removes the problem record from the storage unit. The lsproblem command generates a report that lists which problems and a few of the details about the problem such as how often the problem has occurred or which component type has detected the problem.
closeproblem
The closeproblem command modifies the status of a problem in the problem log file to closed.
closeproblem -dev storage_image_ID -quiet -node node_Num problem_ID
551
Parameters
Note: You cannot specify a range of problem IDs. -dev storage_image_ID (Optional) Specifies the storage image ID, which includes manufacturer, type, and serial number. This parameter is required if you do not specify a fully qualified ID for all ID values that take a storage image ID in the command input required for this command. -quiet (Optional) Specifies that the confirmation prompt for this command be turned off. -node node_Num (Required) Specifies the ID of the node on which the problem record was created. The node number, along with the problem ID uniquely identifies a problem record. problem_ID (Required) Specifies the problem entry to be closed. The format of the problem ID is yyyy-mm-dd-hh.mm.ss.us
Example
Invoking the closeproblem command
dscli>closeproblem -dev IBM.1750-68FA121 -node 0 2005-01-01-12.30.00.000001

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA121 Are you sure you want to close problem 2004-01-01-12.30.00.000001 ? y/n Y Problem 2005-01-01-12.30.00 was successfully closed.
lsproblem
The lsproblem command lists problem logs. This command is exclusive to the DS6000.
lsproblem -s -l -from date -to date -state open closed storage_image_ID
Parameters
-s -l (Optional) Displays problem IDs. You cannot use the -l and the -s parameters together. (Optional) Displays the default output and attributes that are identified as long output. You cannot use the -l and the -s parameters together.
-from date (Optional) To print problem IDs for a range of dates, enter the start date (in the format of mm/dd/yyyy) for the range. For example, 06/11/2005. -to date (Optional) To print problem IDs for a range of dates, enter the end date (in the format of mm/dd/yyyy) for the range. For example, 08/24/2005.
552
-state open | closed (Optional) The problem state that you want to print in the log. storage_image_ID (Required) Specifies a storage image ID. Accepts a fully qualified storage image ID. A storage image ID consists of manufacturer, machine type, and serial number.
Example
The following tables represent the headers that are displayed on the output report associated with the lsproblem command using the -l parameter. Invoking the lsproblem command
dscli>lsproblem -l IBM.1750-68FA120

Date/Time: Sun Aug 11 02:23:49 PST 2004 DS CLI Version: 5.0.0.0 DS: IBM.1750-68FA120 ID 2004-02-12 -01.23.45 .66666 Node 0 Type H/W Sev Problem Occur 1 State Open
Frus 1
FruList
SRN BE804900
First time 2004-02-1201.23.45 .66666
Last time 2004-02-1201.23.45 .66666
Detector SES
Report column definitions ID Node Specifies the identification number that is assigned to the problem. Specifies the node (0 or 1) on which the problem record is created. The node number, along with the Problem ID, uniquely identifies a problem record. Specifies the type of problem. One of the following choices is displayed: v H/W v S/W v Test v Heartbeat v Data Loss SEV Specifies the severity of the problem. One of the following choices is displayed: v Problem v v v v Event Attention Test Heartbeat
Type
Occur Specifies the number of times that the problem occurs.

553
State FRUs
Specifies the state of the problem as being open or closed. Specifies the number of FRUs that are suspended for causing the problem.
FRUList Specifies the list of FRUs that are candidates for replacement in order to solve the problem. This list also specifies the FRUs that have been replaced and identifies those that need to be replaced. SRN Specifies the SRN (service reference number), also known as SRC, which is a 4-byte value.
Firsttime Specifies the first timestamp of the problem. Lasttime Specifies the last timestamp of the problem. Detector Specifies the component type that found the problem. One of the following choices is displayed: v Harvest v RAS v AH v Bering v SES
554
Chapter 9. Command-line interface scenarios

These scenarios describe some typical configuration and configuration management tasks. You can use them as models for writing your own scripts. The following tasks are illustrated: v Determining the physical configuration characteristics of a storage unit. v Determining the current logical storage and Copy Services configuration settings. v Creating new logical storage and Copy Services configuration settings. v Modifying or deleting logical storage and Copy Services configuration settings.
Modifying fixed block volume groups

This scenario describes how to modify fixed block storage within a storage unit. To modify fixed block volume groups, you must have the command-line interface prompt, and you must be connected to a storage unit that will be used for open systems host system storage. Adding volumes to a volume group and removing volumes from a volume group are typical storage management tasks. The volumes that are added to a volume group can be unassigned to a volume group, or they can be volumes that are assigned to a volume group but you want to move them to a different volume group. In either case, you are responsible for managing how the volumes are allocated to volume groups and how the volumes are reserved for future allocation. It is better that you maintain unassigned volumes in a volume group that is not accessible by any host system, thereby controlling the accessibility of volumes that are reserved for future allocation. You can assign a fixed block volume to multiple volume groups. This might be necessary for some host system applications. However, damage to volume data can occur if a volume is accessed by different host systems using different file management systems. To assign a fixed block volume to multiple volume groups, perform the following steps: 1. Find the fixed block volumes that are to be assigned to a volume group using the following command. dscli> lsfbvol -dev ID -datatype 512 | 520p | 520u -extpool ID The command creates a list of all volumes of the specified volume type within the specified extent pool. It includes only the volumes that are contained by the specified storage image. 2. Retrieve the current volume group volume map using the following command. dscli> showvolgrp -dev ID volume_group_ID The command creates a list of volumes that are assigned to the target volume group. 3. Modify the volume group using the following command. dscli> chvolgrp -dev ID -action add | remove | replace -volume ID,ID,...,ID volume_group_ID You can add or remove volume IDs to the list in order to add or remove volumes. This command applies the updated volume ID list.
555
Deleting data storage configurations

This section describes how you can delete or remove fixed block or count key data storage within a storage unit by using the command-line interface. This applies to entire configurations and not just the removal of a volume or volume group. Before you begin, you must be logged into the DS CLI application in interactive command mode. You must also be connected to a storage image that is used for open systems host system storage. Deleting data storage configurations involves the following steps: 1. Remove host access to the volumes that will be removed. v For fixed block storage , the SCSI host port IDs must be removed. v For count key data storage, the CKD volumes are automatically removed from the FICON/ESCON-All volume group ID (10) when the CKD volumes are deleted. 2. Remove the volume groups. v For fixed block storage, if all of the fixed block volumes are being removed, the associated volume groups must be removed. v The FICON/ESCON-All volume group is automatically removed when the last CKD volume is removed. 3. Remove the volumes. This applies to both fixed block and count key data storage. 4. Remove the logical control units (CKD only). Note: Logical subsystems (LSS) are automatically removed when the fixed block volumes are removed. 5. Remove the ranks. 6. Remove the arrays. 7. Remove the extent pools. When all the steps have been completed, the array sites that have been freed are designated as unassigned. They can be redefined to make new fixed block or CKD storage resources.
Deleting a fixed block data storage configuration

Complete this task to delete a fixed block data storage configuration. To delete fixed block data storage, you must have the command-line interface prompt, and you must be connected to a storage unit that contains configured storage. Deleting a storage configuration involves several steps that systematically remove host access to the data storage, and then removes the storage elements (arrays, ranks, extent pools, volumes, and volume groups) in order to restore the physical resource to an equivalent to new state. To delete fixed block data storage, perform the following steps: 1. Remove host access to the volumes that will be removed. This generally requires the issuance of the lshostconnect command and the rmhostconnect command.
556
a. Issue the lshostconnect command to display a list of SCSI host port IDs that are associated with the storage to be removed. Enter the lshostconnect command at the dscli command prompt as follows:
dscli>lshostconnect -dev IBM.175068FA120 -l -portgrp 1
Notes: 1) The -portgrp port_grp_number parameter is used to only list those port IDs that are associated with a port group number that you assigned when you originally created the host connection. 2) The -l parameter is used to generate the detailed status report for each host connection. b. Issue the rmhostconnect command to delete the SCSI host port IDs that are associated with the storage volumes to be removed. Enter the rmhostconnect at the dscli command prompt as follows:
dscli>rmhostconnect -dev IBM.175068FA120 1
Notes: 1) The host_connect_ID parameter (1 in the command example) is required and is a unique identifier (0 - 65 534) within the scope of a storage unit. 2) A message is displayed with a request that you confirm the deletion of the host connection. 2. Find the volume groups and volume group storage maps by issuing the lsvolgrp and showvolgrp commands. a. Issue the lsvolgrp command to display a list of defined volume group IDs and their characteristics. Enter the lsvolgrp command at the dscli command prompt as follows:
dscli>lsvolgrp -dev IBM.175068FA120 -l
b.
Issue the showvolgrp command to display the detailed properties of the volume group that you want to delete. Enter the showvolgrp command at the dscli command prompt as follows:
dscli>showvolgrp -dev IBM.175068FA120 -lunmap V1001
Repeat the showvolgrp command for each volume group you want to delete. Note: The Volume_Group_ID (V1001) parameter is required. The shortened form is allowed when you designate the -dev parameter. c. Copy the list of volumes within the volume group for later use when you analyze which volumes that you want to remove. 3. Remove the volume groups, as a means to remove volume access by host systems, by issuing the rmvolgrp command. Enter the rmvolgrp command at the dscli command prompt as follows:
dscli>rmvolgrp -dev IBM.175068FA120 V123-V125
Notes: a. All volume groups that are specified for deletion must belong to the same storage unit. b. The Volume_Group_ID parameter (V123-V125 in the example) is required. The shortened version of the ID is allowed if you designate the -dev parameter.
557
c. The example command shows a range of volume group IDs. If you have another volume group or another volume group range, you must add a blank between the designations (for example, V123-V125 V130-V133 V135) d. A message is displayed for each deleted volume group ID or range of volume group IDs. The message requests that you confirm the deletion. 4. Remove the fixed block volumes by issuing the rmfbvol command. This action enables the removal of the associated ranks, arrays and extent pools. Enter the rmfbvol command at the dscli command prompt as follows:
dscli>rmfbvol -dev IBM.1750-68FA120 0100 0101
Notes: a. The associated logical subsystem (LSS) is automatically removed when the last volume that is contained by the LSS is removed. b. The Volume_ID parameter (represented by 0100 0101 in the example) is required when you issue the rmfbvol command. The shortened version of the ID is allowed if you designate the -dev parameter. c. A message is displayed for each volume that is deleted. The message requests that you confirm the deletion. 5. Remove the ranks by issuing the lsrank and rmrank commands. a. Issue the lsrank command to display a list of rank IDs to be removed. Use the command parameters to develop a selective list of rank IDs. Enter the lsrank command at the dscli prompt as follows:
Note: Rank IDs that indicate extents used = 0 are eligible to be removed. If extents used are greater than 0 then rank segments are currently assigned to existing volume IDs. b. Issue the rmrank command to remove the ranks that are assigned to the arrays. Enter the rmrank command at the dscli prompt as follows:
Notes: 1) The rank_ID parameter (R23 in the example) is required. The shortened version of the ID is allowed if you designate the -dev parameter. 2) You must remove the ranks before you can remove the arrays and extent pools. 3) The processing time that is associated with the rmrank command can be lengthy and might inhibit your use of the array on which this command is being processed. 4) When the rmrank command is issued, the following processing occurs: v The rank is unassigned from the array. v The rank is removed. When this is successful, a message is displayed. This part of the process does not take long; however, the processing that is associated with this command is not complete even though you have received a message that the rank was removed. v The array is formatted. This processing can take some time. During this processing the array cannot be removed or
558
assigned to another rank. Also, until this process is fully completed, the rank is listed as assigned to the array from which it is has been removed. v You can check the progress of the rmrank command by logging onto another session of DS CLI. Issue the lsarray command against the storage unit where the rank or ranks are being deleted. When you no longer see the rank that is assigned to the array from which you removed it, the remove rank process is complete. 6. Remove the arrays by issuing the lsarray and rmarray commands. a. Issue the lsarray command to obtain a list of array IDs to be removed. Enter the lsarray command at the dscli prompt as follows:
Notes: 1) The -state unassigned parameter allows you to narrow your list to just the array IDs that are not assigned to a rank ID. 2) If you issue the lsarray command without using the -state parameter, it is possible you will see a list of arrays that have a state of unavailable. This is generally a good indication that the ranks have not been removed and that the drives are still formatting. You must wait until the ranks have been removed and the drives have been formatted before you can proceed. 3) Proceed to the next step (remove arrays) only after all the associated arrays are displayed with a state of unassigned. b. Issue the rmarray command to delete the unassigned arrays so that the array sites can be redefined as new arrays. Enter the rmarray command at the dscli command prompt as follows:
dscli>rmarray -dev IBM.1750-68FA120 A44-A48 A51
Notes: 1) The example command displays the use of a range of array IDs plus one additional array ID.(A44-A48 A51). A range of arrays requires the use of a hyphen and a space between the next array or another range of arrays. 2) A message is displayed for each array being deleted that requests your confirmation before processing. 7. Remove the extent pools by issuing the lsextpool and rmextpool commands. a. Issue the lsextpool command to obtain a list of extent pool IDs to be removed. Enter the lsextpool command at the dscli command prompt as follows:
dscli>lsextpool -dev IBM.1750-68FA120 -l -stgtype fb
Note: v The -stgtype fb parameter allows you to narrow the list so that it displays only those extent pools that are assigned for use with fixed block volumes. v Extent pool IDs that indicate assigned ranks = 0 are eligible to be removed. If the assigned ranks are greater than 0, the extent pool potentially contains assigned storage volumes. The rank indicator must be 0 before you can remove the extent pool.
559
b. Issue the rmextpool command to delete extent pool IDs that do not contain assigned rank IDs. Enter the rmextpool command at the dscli command prompt as follows:
dscli>rmextpool -dev IBM.1750-68FA120 P21-P25 P30
Notes: 1) All rank assignments must be deleted before the extent pool can be deleted. 2) The example command displays the use of a range of extent pool IDs plus one additional extent pool ID (P21-P25 P30). A range of extent pool IDs requires the use of a hyphen and a space between the next extent pool ID or next range of extent pool IDs.
Deleting a count key data storage configuration

Complete this task to delete a count key data storage (CKD) configuration. To delete CKD storage, you must have the command-line interface prompt, and you must be connected to a storage unit that contains configured storage. Deleting a CKD storage configuration starts with the removal of the CKD volumes and proceeds with the removal of each of the other elements (ranks, arrays, and extent pools) in order to restore the physical resource to an equivalent to new state. Note: There is no reason to remove the volume groups because the internal code automatically assigns and unassigns CKD volumes to the FICON/ESCON-All volume group ID (10). To delete CKD storage, perform the following steps: 1. Remove the CKD volumes by issuing the lsckdvol and rmckdvol commands. a. Issue the lsckdvol command to display a list of CKD volume IDs. Analyze the list to determine which IDs can be removed. Enter the lsckdvol command at the dscli command prompt as follows:
dscli>lsckdvol -dev IBM.175068FA120 -lcu 00 -l
Notes: 1) You can narrow the list of volume IDs for the designated storage unit by using the supported parameters of the lsckdvol command. 2) The example displays the use of the -lcu parameter with a value of 00. Logical control unit (LCU) values are in the range 00 - 1E. You must specify a specific LCU; otherwise, the entire storage unit is queried, which results in a longer processing time. b. Issue the rmckdvol command to delete volumes. This action enables the removal of the associated ranks, arrays, and extent pools. Enter the rmckdvol command at the dscli command prompt as follows:
dscli>rmckdvol -dev IBM.1750-68FA120 0100 0101
Note: v The Volume_ID parameter (represented by the values 0100 0101 in the command example) is required when you issue the rmckdvol command.
560
v A message is displayed for each volume that is being deleted. The message requests that you confirm the deletion. 2. Issue the rmlcu command to delete LCUs so that the address groups can be redefined for use with fixed block or CKD volumes. Enter the rmlcu command at the dscli command prompt as follows:
dscli>rmlcu -dev IBM.2107-68FA120 00-03 08
Note: The example command displays the use of a range of LCU IDs plus one additional LCU ID (00-03 08). A range of LCU IDs requires the use of a hyphen. If you add an additional LCU ID or a range of LCU IDs, you must allow a space between the next LCU ID or another range of LCU IDs. 3. Remove the ranks by issuing the lsrank and rmrank commands. a. Issue the lsrank command to display a list of rank IDs to be removed. Use the lsrank command parameters to develop a selective list of rank IDs. Enter the lsrank command at the dscli command prompt as follows:
Note: Rank IDs that indicate extents used = 0 are eligible to be removed. If the displayed value for extents used is greater than 0, it indicates that the ranks are currently assigned to existing volume IDs. b. Issue the rmrank command to remove the ranks that are assigned to the arrays. Enter the rmrank command at the dscli prompt as follows:
Notes: 1) You must remove the ranks before you can remove the arrays and extent pools. 2) The processing time that is associated with the rmrank command can be lengthy and might inhibit your use of the array on which this command is being processed. 3) When the rmrank command is issued, the following processing occurs: v The rank is unassigned from the array. v The rank is removed. When this is successful, a message is displayed. This part of the process does not take long; however, the processing that is associated with this command is not complete even though you have received a message that the rank was removed. v The array is formatted. This processing can take some time. During this processing the array cannot be removed or assigned to another rank. Also, until this process is fully completed, the rank is listed as assigned to the array from which it is has been removed. v You can check the progress of the rmrank command by logging onto another session of DS CLI. Issue the lsarray command against the storage unit where the rank or ranks are being deleted. When you no longer see the rank that is assigned to the array from which you removed it, the remove rank process is complete. 4. Remove the arrays by issuing the lsarray and rmarray commands.
561
a. Issue the lsarray command to obtain a list of array IDs to be removed. Enter the lsarray command at the dscli prompt as follows:
Notes: 1) The -state unassigned parameter allows you to narrow your list to just the array IDs that are not assigned to a rank ID. 2) If you issue the lsarray command without using the -state parameter, it is possible you will see a list of arrays that have a state of unavailable. This is generally a good indication that the ranks have not been removed and that the drives are still formatting. You must wait until the ranks have been removed and the drives have been formatted before you can proceed. Proceed to the next step (remove arrays) only after all the associated arrays are displayed with a state of unassigned. b. Issue the rmarray command to delete the unassigned arrays so that the array sites can be redefined as new arrays. Enter the rmarray command at the dscli command prompt as follows:
dscli>rmarray -dev IBM.1750-68FA120 A44-A48 A51
Notes: 1) The example command displays the use of a range of array IDs plus one additional array ID (A44-A48 A51). A range of arrays requires the use of a hyphen and a space between the next array or another range of arrays. 2) A message is displayed for each array being deleted that requests your confirmation before processing. 5. Remove the extent pools by issuing the lsextpool and rmextpool commands. a. Issue the lsextpool command to obtain a list of extent pool IDs to be removed. Enter the lsextpool command at the dscli command prompt as follows:
dscli>lsextpool -dev IBM.1750-68FA120 -stgtype fb -l
Notes: 1) Use the -stgtype fb parameter to narrow the list so that it displays only those extent pools that are assigned for use with fixed block volumes. 2) Extent pool IDs that indicate assigned ranks = 0 are eligible to be removed. If the value for assigned ranks is greater than 0, the extent pool potentially contains assigned storage volumes. The rank indicator must be 0 before you can remove the extent pool. b. Issue the rmextpool command to delete extent pool IDs that do not contain assigned rank IDs. Enter the rmextpool command at the dscli command prompt as follows:
dscli>rmextpool -dev IBM.1750-68FA120 P21-P25 P30
Notes: 1) All rank assignments must be deleted before the extent pool can be deleted. 2) The example command displays the use of a range of extent pool IDs plus one additional extent pool ID (P21-P25 P30). A range of extent pool IDs requires the use of a hyphen. When you
562
add an additional extent pool ID or another range of extent pool IDs, you must put a space between the current extent pool ID value and the next extent pool ID value.
Processing remote FlashCopy (inband) transactions

This scenario describes how to successfully process remote FlashCopy (formerly known as inband FlashCopy) transactions. These transactions can only be processed using the DS CLI remote FlashCopy commands. These transactions cannot be managed through the GUI. You must be logged into the DS CLI application in interactive command mode. Remote FlashCopy commands are issued to a source volume of a remote mirror and copy volume pair on a local storage unit. This enables a FlashCopy pair to be established at the remote site and eliminates the need for a network connection to the remote site solely for the management of FlashCopy. The following steps are based on an example that uses the sites LSS 22 and LSS 2A. 1. You must determine which volumes are available for use and then establish a remote mirror and copy path between LSS 22 and LSS 2A. a. Issue the lsavailpprcport command to obtain a report that lists which volumes are available for use. Enter the lsavailpprcport command at the dscli command prompt with the following parameters and variables: | |
dscli> lsavailpprcport -dev IBM.1750-1300861 -remotedev IBM.1750-1300871 -remotewwnn 5005076303FFC03D 22:2A
The following report is generated.

Local port I0030 I0031 I0100 I0101 Attached port I0031 I0030 I0101 I0100 Type FCP FCP FCP FCP
b. Issue the mkpprcpath command to establish the remote mirror and copy path between LSS 22 and LSS 2A. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables: | | | | | | |
dscli>mkpprcpath -dev IBM.1750-1300861 -remotedev IBM.1750-1300871 -remotewwnn 5005076303FFC03D -srclss 22 -tgtlss 2A I0030:I0031 I0100:I0101
The following confirmation is displayed if your command input is correct.

Date/Time: February 7, 2005 4:25:04 PM IST IBM DSCLI Version: 0.0.0.0 DS: IBM.1750-1300861 CMUC00149I mkpprcpath: Remote Mirror and Copy path 22:2A successfully established.
2. Issue the mkpprc command to establish a remote mirror and copy pair (2200 to 2A00). Enter the mkpprc command at the dscli command prompt with the following parameters and variables: | | | | | |
dscli>mkpprc -dev IBM.1750-1300861 -remotedev IBM.1750-1300871 -type mmir 2200:2A00

Date/Time: February 7, 2005 4:25:33 PM IST IBM DSCLI Version: 0.0.0.0 DS: IBM.1750-1300861 CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 2200:2A00 successfully created.
563
3. Issue the mkremoteflash command to use LSS 22 on the local site as a conduit LSS for new remote Flash Copy relationships on the remote storage unit. These new relationships use volume 2A00 as their source. The target can be any other volume on the remote storage unit (in this scenario, 2A01). Enter the mkremoteflash command at the dscli command prompt with the following parameters and variables: | | | | | |
dscli>mkremoteflash -dev IBM.1750-1300871 -conduit IBM.1750-1300861/22 -record 2A00:2A01

Date/Time: February 7, 2005 4:28:11 PM IST IBM DSCLI Version: 0.0.0.0 DS: IBM.1750-1300871 CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2A00:2A01 successfully created. Use the lsremoteflash command to determine copy completion.
4. Issue the resyncremoteflash command because the remote FlashCopy relationship (2A00:2A01) was created with the -record parameter. Enter the resyncremoteflash command at the dscli command prompt with the following parameters and variables: | |
dscli>resyncremoteflash -dev IBM.1750-1300871 -conduit IBM.1750-1300861/22 -record 2A00:2A01

CMUC00175I resyncremoteflash: Remote FlashCopy volume pair 2A00:2A01 successfully resynched. Use the lsremoteflash command to determine copy completion.
5. Issue the lsremoteflash command to verify that the transaction has processed as you intended. Enter the lsremoteflash command at the dscli command prompt with the following parameters and variables: |
dscli>lsremoteflash -dev IBM.1750-1300871 -conduit IBM.1750-1300861/22 2A00:2A01
The following report is displayed if your command input is correct.

ID 2A00:2A01 SrcLSS 2A Sequence Num 0 ActiveCopy Disabled Recording Enabled
Persistent Enabled
Revertible Disabled
SourceWrite Enabled Disabled
TargetWrite Enabled Disabled
Background Copy Enabled
Metro Mirror test scenario: failback operation from local to remote site
This scenario describes the steps required to test the failover and failback procedures in which a failback is done from the local site to the remote site. This test allows you to bring up a test application on the remote volumes. Then, after the test is complete, resynchronize the remote volumes from the local (production) volumes by copying only changed tracks. Assume the following for this scenario: v Production is running at Site A (the local site). v You have simulated a disaster by disabling the links between the local and remote storage units. Complete these steps for the failover and failback test scenario. (The parameters and values included in this scenario are examples.)
564
1. Freeze updates to the primary (A) volumes in Metro Mirror relationships across the affected LSSs. This process ensures that the secondary (B) volumes will be consistent at the time of the freeze. (One command per LSS is required.) Enter the freezepprc command at the dscli command prompt with the following parameters and variables:
freezepprc -dev IBM.2107-130165X -remotedev IBM.2107-75ALA2P 07:12
The following represents an example of the output:

CMUC00161W freezepprc: Remote Mirror and Copy consistency group 07:12 successfully created.
As a result of the freeze action, the following processing occurs: v I/O processing to the Metro Mirror volume pairs is temporarily queued during the time that updates are frozen. v The volume pairs that are associated with the source and target LSSs are suspended. During this time, updates are collected using the change recording feature on the Site A volumes. v The established paths between the LSS pairs are disabled. 2. Resume operations following a freeze. Issue the unfreezepprc command to allow I/O activity to resume for the specified volume pairs. Enter the unfreezepprc command at the dscli command prompt with the following parameters and variables: Note: This action is sometimes referred to as a thaw operation.
dscli> unfreezepprc -dev IBM.2107-130165X -remotedev IBM.2107-75ALA2P 07:12

CMUC00198I unfreezepprc: Remote Mirror and Copy pair 07:12 successfully thawed.
3. At Site B (remote site), issue a failover command to the B to A volume pairs. Enter the failoverpprc command at the dscli command prompt with the following parameters and variables:
dscli> failoverpprc -dev IBM.2107-75ALA2P -remotedev IBM.2107-130165X -type mmir 1200-125f:1a00-1a5f

CMUC00196I failoverpprc: Remote Mirror and Copy pair 1200:1A00 successfully reversed. CMUC00196I failoverpprc: Remote Mirror and Copy pair 1201:1A01 successfully reversed.
When this command processes, the following occurs: v The B volumes become suspended primary volumes. Updates are collected using the change recording feature on the volumes. v The A volumes are suspended primary volumes. 4. Allow test I/O to start at Site B. 5. When testing is complete, perform the following steps: a. Quiesce test I/O at Site B (remote site). b. Enable the remote mirror and copy links between the storage units across the two sites. (The paths will not reestablish automatically.) c. Reestablish paths between the local and remote site LSSs that contain the Metro Mirror volume pairs. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables:
dscli> mkpprcpath -dev IBM.2107-130165X -remotedev IBM.2107-75ALA2P -remotewwnn 5005076303FFC550 -srclss 07 -tgtlss 12 -consistgrp I0102:I0031 I0002:I0102

565
CMUC00149I mkpprcpath: Remote Mirror and Copy path 07:12 successfully established.
6. At the local site, issue a failback command to the A to B volume pairs. Enter the failbackpprc command at the dscli command prompt with the following parameters and variables
dscli> failbackpprc -dev IBM.2107-130165X -remotedev IBM.2107-75ALA2P -type mmir 1a00-1a5f:1200-125f

CMUC00197I failbackpprc: Remote Mirror and Copy pair 1200:1A00 successfully failed back. CMUC00197I failbackpprc: Remote Mirror and Copy pair 1201:1A01 successfully failed back.
When this command processes, the following occurs: v Updates that are made to the volumes at Site B are recorded with the change recording feature. Changed tracks of data are copied from the Site A volumes to Site B volumes. v When the copy process is complete, the Site A volumes will be synchronized with the Site B volumes. 7. Production I/O continues to the A volumes.
Allowed remote mirror and copy volume pair conversions

This topic describes allowed volume pair conversions using the remote mirror and copy function. You can convert remote mirror and copy volume pairs between copy modes. For example, you can convert volume pairs in Global Copy to Metro Mirror mode and vice versa. If you create a Global Copy volume pair where the source volume was associated with a Model 1750 storage unit and the target volume was associated with an ESS 2105 Model 800 or 750, you can convert that volume pair to Metro Mirror mode. Before you establish remote mirror and copy volume pairs, logical paths must be established between the source and target logical subsystem (LSS). I/O ports must be available and configured before you can establish paths between the source and target LSSs. Each LSS with source volumes requires at least one path to be established to the LSS that holds the target volumes. The following mkpprcpath command establishes remote mirror and copy paths:
dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID
Example
dscli>mkpprcpath -dev IBM.1750-75FA120 -remotedev IBM.1750-68FA150 -srclss 00 -tgtlss 00 -remotewwnn 12341234000A000F I1A10:I2A20
Convert Metro Mirror volume pairs to Global Copy mode

You can convert a Metro Mirror volume pair to Global Copy mode. For example, because Global Copy can operate at very long distances, well beyond the 300 km (maximum supported distance for Metro Mirror), you might want to convert some Metro Mirror volume pairs, which contain less critical application data, to Global Copy mode.
566
The following mkpprc command converts Metro Mirror volume pairs Global Copy mode:
dscli> mkpprc -dev storage_image_ID -remotedev storage_image_ID -type gcp SourceVolumeID:TargetVolumeID
Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100 -type gcp 0101:0101 0102:0102 0103:0103
Convert Global Copy volume pairs to Metro Mirror mode

There are two common situations when you would convert a Global Copy volume pair to a Metro Mirror mode: v You have used Global Copy to complete the bulk transfer of data in the creation of many copy pairs, and you now want to convert some or all of those pairs to Metro Mirror mode. This process resynchronizes the volume pairs by copying all changed data from the source volumes to the target volumes. v You have Global Copy pairs for which you want to make FlashCopy backups on the remote site. You convert the pairs temporarily to synchronous mode in order to obtain a point-in-time consistent copy. The following mkpprc command converts Global Copy volume pairs to Metro Mirror mode:
dscli> mkpprc -dev storage_image_ID -remotedev storage_image_ID -type mmir SourceVolumeID:TargetVolumeID
Example
567
568
Chapter 10. Messages in the CLI and management console server

When you use the command-line interface and the management console, the applications provide messages regarding the application processes, status, and errors. This section also provides information about how the DS CLI manages OpenVMS messages. The user interfaces and the supporting software issue three types of messages: Informational messages These messages are identified by the letter I at the end of the message identifier. They provide information about system activities as they take place. For instance, an informational message might report that a volume was successfully created. No user action is necessary. Warning messages These messages are identified by the letter W at the end of the message identifier. They warn that user activated activities might have consequences that you do not anticipate. Warning messages normally provide the opportunity to continue an activity or to cancel it. Error messages These messages are identified by the letter E at the end of the message identifier. They indicate that an error has occurred. Refer to the explanations and recommended actions in this document to resolve the problem. For the list of individual messages see the IBM System Storage DS6000 Information Center.
OpenVMS messages and exit codes

On OpenVMS host systems, the DS CLI application provides additional system messages in the OpenVMS message format. For example, %facility-levelidentification, text Each DS CLI message is also communicated by OpenVMS system services. This ensures that messages appear on the screen and in batch logs according to OpenVMS standards. This allows the OpenVMS command SET MESSAGE and customer-written tools which scan for such messages to work correctly. The following mapping between DS CLI and OpenVMS messages applies: v The facility is IBMDSCLI. v The level is I (Informational), W (Warning), or E (Error), according to the DS CLI severity level. v The identification is the DS CLI message identifier. v The text is a is a generic text, identifying the DS CLI message. After displaying the OpenVMS message, the normal DS CLI message is displayed unchanged. This ensures that the DS CLI messages are identical across platforms and that you can reference the DS CLI documentation. When you exit the DS CLI, it provides a condition code according to OpenVMS standards instead of the normal DS CLI exit value. The following rules apply:
569
v A single-shot DS CLI command returns the condition code of the DS CLI message for this command. If there are multiple messages, the code with the highest severity is displayed. v The DS CLI in interactive mode always returns the OpenVMS generic success status: %X00000001. v The DS CLI in script mode returns either the OpenVMS generic success code or cancels the script while returning the highest severity code of the failed command. This ensures that the DCL symbol $STATUS contains a value that can be evaluated by OpenVMS utilities as usual.
570
Accessibility
Accessibility features provide users who have disabilities with the ability to successfully access information and use technology. Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully.
Features
These are the major accessibility features in the IBM System Storage DS6000 information: v You can use screen-reader software and a digital speech synthesizer to hear what is displayed on the screen. IBM Home Page Reader version 3.0 has been tested. v You can operate features using the keyboard instead of the mouse.
Navigating by keyboard
You can use keys or key combinations to perform operations and initiate menu actions that can also be done through mouse actions. You can navigate the IBM System Storage DS6000 information from the keyboard by using the shortcut keys for your browser or Home Page Reader. See your browser Help for a list of shortcut keys that it supports. See the following Web site for a list of shortcut keys supported by Home Page Reader: http://www-306.ibm.com/able/ solution_offerings/keyshort.html
Accessing the publications

You can find HTML versions of the IBM System Storage DS6000 information at the following Web site: http://www.ehone.ibm.com/public/applications/publications/ cgibin/pbi.cgi You can access the information using IBM Home Page Reader 3.0.
571
572
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATIONS AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been
573
estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
Terms and conditions

Permissions for the use of these publications is granted subject to the following terms and conditions. Personal Use: You may reproduce these Publications for your personal, non commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these Publications, or any portion thereof, without the express consent of IBM. Commercial Use: You may reproduce, distribute and display these Publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these Publications, or reproduce, distribute or display these Publications or any portion thereof outside your enterprise, without the express consent of IBM. Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the Publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the Publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED AS-IS AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
574
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: v AIX v DB2 v DFSMS/MVS v DFSMS/VM v DS4000 v DS6000 v DS8000 v e (logo) v Enterprise Storage Server v ES/9000 v ESCON v FICON v FlashCopy v Graphically Dispersed Parallel Sysplex v HACMP v i5/OS v IBM v IntelliStation v v v v v v v v v v v v v v v v v v v v MVS/ESA Netfinity NetVista Operating System/400 OS/400 RS/6000 S/390 Seascape SNAP/SHOT SP System/390 System p5 System Storage Versatile Storage Server Virtualization Engine VSE/ESA z/Architecture z/OS z/VM zSeries
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Notices
575
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
Electronic emission notices

This section contains the electronic emission notices or statements for the United States and other countries.
Federal Communications Commission (FCC) statement

This equipment has been tested and complies with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, might cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Properly shielded and grounded cables and connectors must be used to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors, or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the users authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device might not cause harmful interference, and (2) this device must accept any interference received, including interference that might cause undesired operation.
Industry Canada compliance statement

This Class A digital apparatus complies with Canadian ICES-003. Cet appareil numrique de la classe A est conform la norme NMB-003 du Canada.
European community compliance statement

This product is in conformity with the protection requirements of EC Council Directive 89/336/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any
576
failure to satisfy the protection requirements resulting from a nonrecommended modification of the product, including the fitting of non-IBM option cards.
Germany only
Zulassungsbescheinigung laut Gesetz ueber die elektromagnetische Vertraeglichkeit von Geraeten (EMVG) vom 30. August 1995. Dieses Geraet ist berechtigt, in Uebereinstimmung mit dem deutschen EMVG das EG-Konformitaetszeichen - CE - zu fuehren. Der Aussteller der Konformitaetserklaeung ist die IBM Deutschland. Informationen in Hinsicht EMVG Paragraph 3 Abs. (2) 2:
Das Geraet erfuellt die Schutzanforderungen nach EN 50082-1 und EN 55022 Klasse A.
EN 55022 Klasse A Geraete beduerfen folgender Hinweise: Nach dem EMVG:

"Geraete duerfen an Orten, fuer die sie nicht ausreichend entstoert sind, nur mit besonderer Genehmigung des Bundesministeriums fuer Post und Telekommunikation oder des Bundesamtes fuer Post und Telekommunikation betrieben werden. Die Genehmigung wird erteilt, wenn keine elektromagnetischen Stoerungen zu erwarten sind." (Auszug aus dem EMVG, Paragraph 3, Abs.4) Dieses Genehmigungsverfahren ist nach Paragraph 9 EMVG in Verbindung mit der entsprechenden Kostenverordnung (Amtsblatt 14/93) kostenpflichtig.
Nach der EN 55022:

"Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funkstoerungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Massnahmen durchzufuehren und dafuer aufzukommen."
Anmerkung:
Um die Einhaltung des EMVG sicherzustellen, sind die Geraete wie in den Handbuechern angegeben zu installieren und zu betreiben.
Japanese Voluntary Control Council for Interference (VCCI) class A statement
Notices
577
Korean Ministry of Information and Communication (MIC) statement

Please note that this device has been certified for business use with regard to electromagnetic interference. If you find this is not suitable for your use, you may exchange it for one of residential use.
Taiwan class A compliance statement
VS07171L
Taiwan Contact Information

This topic contains the product service contact information for Taiwan.
IBM Taiwan Product Service Contact Information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd., Taipei Taiwan Tel: 0800-016-888
578
f2c00790
Glossary
This glossary includes terms for the IBM System Storage and other Resiliency Family products. This glossary includes selected terms and definitions from: v The American National Standard Dictionary for Information Systems, ANSI X3.1721990, copyright 1990 by the American National Standards Institute (ANSI), 11 West 42nd Street, New York, New York 10036. Definitions derived from this book have the symbol (A) after the definition. v IBM Terminology, which is available online at the following Web site: http://www306.ibm.com/ibm/terminology/index.html. Definitions derived from this source have the symbol (GC) after the definition. v The Information Technology Vocabulary developed by Subcommittee 1, Joint Technical Committee 1, of the International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC JTC1/SC1). Definitions derived from this book have the symbol (I) after the definition. Definitions taken from draft international standards, committee drafts, and working papers that the ISO/IEC JTC1/SC1 is developing have the symbol (T) after the definition, indicating that final agreement has not been reached among the participating National Bodies of SC1. This glossary uses the following cross-reference forms: See Refers the reader to one of two kinds of related information: v A term that is the expanded form of an abbreviation or acronym. This expanded form of the term contains the full definition. v A synonym or more preferred term See also Refers the reader to one or more related terms. Contrast with Refers the reader to a term that has an opposite or substantively different meaning.
Numerics
750 A model of the Enterprise Storage Server featuring a 2-way processor with limited physical storage capacity. This model can be updated to the model 800. A model of the Enterprise Storage Server featuring a standard processor or an optional Turbo processor. The Model 800 supports RAID 5, RAID 10, and 15000 rpm drives. Model 800 supersedes Model F20. The machine type for the IBM System Storage DS6000 series. Models for the DS6000 include the 511 and EX1. The machine number for the IBM TotalStorage Enterprise Storage Server. Models of the Enterprise Storage Server are expressed as the number 2105 followed by Model <xxx>, such as 2105 Model 800. The 2105 Model 100 is an Enterprise Storage Server expansion enclosure that is typically referred to simply as the Model 100. A hardware machine type for the IBM System Storage DS8000 series. Hardware models for the 2107 include base units and expansion units 92E and 9AE. A function authorization machine type for the IBM System Storage DS8000 series. The 2244 function authorization machine type corresponds with the 2107 hardware machine type and is used only for purposes of billing and authorizing the licensed functions on the 2107. Function authorization models for the 2244 are related to the type of licensed functions that you order. For example, Model RMC is for the remote mirror and copy function on a 2107 storage unit. The machine number of an IBM disk storage system. The Enterprise Storage Server, when interfaced to IBM zSeries hosts, is set up to appear as one or more
800
1750
2105
2107
2244
3390
579
3390 devices, with a choice of 3390-2, 3390-3, or 3390-9 track formats. 3990 7133 The machine number of an IBM control unit. The machine number of an IBM disk storage system. The Model D40 and 020 drawers of the 7133 can be installed in the 2105-100 expansion enclosure of the ESS.
establishes the procedures by which accredited organizations create and maintain voluntary industry standards in the United States. (A) anonymous In the DS Storage Manager, the label on an icon that represents all connections that are using fibre-channel adapters between the storage unit and hosts but are not completely defined to the storage unit. See also anonymous host, pseudo host, and access-any mode. anonymous host Synonym for pseudo host. Contrast with anonymous and pseudo host. ANSI See American National Standards Institute. APAR See authorized program analysis report. (GC) API See application programming interface.
A
access 1) To obtain computing services or data. 2) In computer security, a specific type of interaction between a subject and an object that results in flow of information from one to the other. access-any mode One of the two access modes that can be set for the storage unit during initial configuration. It enables all fibre-channel-attached host systems with no defined access profile to access all logical volumes on the storage unit. With a profile defined in DS Storage Manager for a particular host, that host has access only to volumes that are assigned to the WWPN for that host. See also pseudo host and worldwide port name. ACK agent See request for acknowledgment and acknowledgment. A program that automatically performs some service without user intervention or on a regular schedule. See also subagent. A message or log that a storage unit generates as the result of error event collection and analysis. An alert indicates that a service action is required.
application programming interface An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program. arbitrated loop A fibre-channel topology that enables the interconnection of a set of nodes. See also point-to-point connection and switched fabric. array An ordered collection, or group, of physical devices (disk drive modules) that is used to define logical volumes or devices. In the storage unit, an array is a group of disks that the user designates to be managed by the RAID technique. See also redundant array of independent disks.
alert
allegiance For zSeries, a relationship that is created between a device and one or more channel paths during the processing of certain conditions. See also implicit allegiance, contingent allegiance, and reserved allegiance. allocated storage The space that is allocated to volumes but not yet assigned. Contrast with assigned storage. American National Standards Institute (ANSI) An organization of producers, consumers, and general interest groups that
ASCII (American National Standard Code for Information Interchange) The standard code, using a coded character set consisting of 7-bit coded characters (8 bits including parity check), that is used for information interchange among data processing systems, data communication systems, and associated equipment. The ASCII set consists of control characters and graphic characters. (A) Some organizations, including IBM, have used the parity bit to expand the basic code set. assigned storage The space that is allocated to a volume and that is assigned to a port.
580
authorized program analysis report (APAR) A request for correction of a defect in a current release of an IBM-supplied program. (GC) availability The degree to which a system or resource is capable of performing its normal function. See data availability.
cache memory Memory, typically volatile memory, that a storage server uses to improve access times to instructions or data. The cache memory is typically smaller and faster than the primary memory or storage medium. In addition to residing in cache memory, the same data also resides on the storage devices in the storage unit. cache miss An event that occurs when a read operation is sent to the cluster, but the data is not found in cache. Contrast with cache hit. call home A communication link established between the storage product and a service provider. The storage product can use this link to place a call to IBM or to another service provider when it requires service. With access to the machine, service personnel can perform service tasks, such as viewing error logs and problem logs or initiating trace and dump retrievals. (GC) See also heartbeat and remote technical assistance information network. cascading 1) Connecting network controllers to each other in a succession of levels to concentrate many more lines than a single level permits. 2) In high-availability cluster multiprocessing (HACMP), pertaining to a cluster configuration in which the cluster node with the highest priority for a particular resource acquires the resource if the primary node fails. The cluster node relinquishes the resource to the primary node upon reintegration of the primary node into the cluster. catcher A server that service personnel use to collect and retain status data that an DS6000 sends to it. CCR CCW CD See channel command retry. See channel command word. See compact disc.
B
bay The physical space that is used for installing SCSI and fibre-channel host adapter cards. The DS6000 has four bays, two in each cluster. See also service boundary. The smallest unit of computer information, which has two possible states that are represented by the binary digits 0 or 1. See also byte. A string of data elements recorded or transmitted as a unit. The elements may be characters, words, or physical records. (GC) A group of consecutive bytes used as the basic storage unit in fixed-block architecture (FBA). All blocks on the storage device are the same size (fixed size). See also fixed-block architecture and data record. byte A string that represents a character and usually consists of eight binary digits that are treated as a unit. A byte is the smallest unit of storage that can be addressed directly. (GC) See also bit.
bit
block
C
cache A special-purpose buffer storage, smaller and faster than main storage, used to hold a copy of instructions and data obtained from main storage and likely to be needed next by the processor. (GC)
cache fast write A form of the fast-write operation in which the storage server writes the data directly to cache, where it is available for later destaging. cache hit An event that occurs when a read operation is sent to the cluster, and the requested data is found in cache. Contrast with cache miss.
central electronics complex The set of hardware facilities that are associated with a host computer.
Glossary
581
channel The part of a channel subsystem that manages a single I/O interface between a channel subsystem and a set of control units. channel command retry (CCR) The protocol used between a channel and a control unit that enables the control unit to request that the channel reissue the current command. channel command word (CCW) A data structure that specifies an I/O operation to the channel subsystem. channel path The interconnection between a channel and its associated control units. channel subsystem The part of a host computer that manages I/O communication between the program and any attached control units. channel-subsystem image For zSeries, the logical functions that a system requires to perform the function of a channel subsystem. CKD CLI cluster 1) A partition capable of performing all DS6000 functions. With two clusters in the DS6000, any operational cluster can take over the processing of a failing cluster. cluster processor complex The unit within a cluster that provides the management function for the DS6000. It consists of cluster processors, cluster memory, and related logic. command-line interface (CLI) An interface that defines a set of commands and enables a user (or a script-like language) to issue these commands by typing text in response to the command prompt (for example, DOS commands or UNIX shell commands). See also Copy Services command-line interface. compact disc An optically read disc, typically storing approximately 660 MB. CD-ROM (compact disc read-only memory) refers See count key data. See command-line interface. See also Copy Services command-line interface.
to the read-only format used to distribute DS6000 code and documentation. compression 1) The process of eliminating gaps, empty fields, redundancies, and unnecessary data to shorten the length of records or blocks. 2) Any encoding that reduces the number of bits used to represent a given message or record. (GC) concurrent copy A facility on a storage server that enables a program to make a backup of a data set while the logical volume remains available for subsequent processing. The data in the backup copy is frozen at the point in time that the server responds to the request. concurrent installation of licensed internal code Process of installing licensed internal code on a DS6000 while applications continue to run. concurrent maintenance Service that is performed on a unit while it is operational. concurrent media maintenance Service performed on a disk drive module (DDM) without losing access to the data. configure In storage, to define the logical and physical devices, optional features, and program products of the input/output subsystem through the user interface that the storage unit provides for this function. consistency group A group of volumes participating in FlashCopy relationships in a logical subsystem, across logical subsystems, or across multiple storage units that must be kept in a consistent state to ensure data integrity. consistency group interval time The value in seconds that indicates the length of time between the formation of consistency groups. consistent copy A copy of a data entity (a logical volume, for example) that contains the contents of the entire data entity at a single instant in time.
582
console A user interface to a server, for example, the interface provided on a personal computer. See also IBM System Storage Management Console. contingent allegiance In mainframe computing, a relationship that is created in a control unit between a device and a channel when the channel accepts unit-check status. The allegiance causes the control unit to guarantee access; the control unit does not present the busy status to the device. The allegiance enables the channel to retrieve sense data that is associated with the unit-check status on the channel path associated with the allegiance. (GC) control path The route that is established from the master storage unit to the subordinate storage unit when more than one storage unit participates in a Global Mirror session. If there is only one storage unit (the master) in the Global Mirror session, no control path is required. control unit (CU) 1) A device that coordinates and controls the operation of one or more input/output devices, and synchronizes the operation of such devices with the operation of the system as a whole. 2) For zSeries, a storage server with ESCON or OEMI interfaces. The control unit adapts a native device interface to an I/O interface that a zSeries host system supports. 3) The portion of the storage unit that supports the attachment of emulated count key data devices over FICON or OEMI interfaces. See also cluster. control-unit-initiated reconfiguration (CUIR) A software mechanism that the DS6000 uses to request that an operating system of a zSeries host verify that one or more subsystem resources can be taken offline for service. The DS6000 can use this process to automatically vary channel paths offline and online to facilitate bay service or concurrent code installation. Depending on the operating system, support for this process might be model dependent, might depend on the IBM
TotalStorage Enterprise Storage Server Subsystem Device Driver, or might not exist. Coordinated Universal Time (UTC) The international standard of time that is kept by atomic clocks around the world. Copy Services A collection of optional software features, with a Web-browser interface, used for configuring, managing, and monitoring data-copy functions. Copy Services CLI See Copy Services command-line interface. Copy Services domain See Copy Services server group. Copy Services client Software that runs on each DS6000 cluster in the Copy Services server group and that performs the following functions: v Communicates configuration, status and connectivity information to the Copy Services server v Performs data-copy functions on behalf of the Copy Services server Copy Services command-line interface (Copy Services CLI) The command-line interface software that is provided with DS6000 Copy Services and used for invoking Copy Services functions from host systems attached to the DS6000. See also command-line interface. Copy Services server A cluster that the Copy Services administrator designates to perform the DS6000 Copy Services functions. Copy Services server group A collection of user-designated DS6000 clusters participating in Copy Services functions that a designated, active, Copy Services server manages. A Copy Services server group is also called a Copy Services domain. See also domain. count field The first field of a count key data (CKD) record. This eight-byte field contains a four-byte track address (CCHH). It defines the cylinder and head that are associated with the track, and a one-byte record number (R) that identifies the record on the track. It defines a one-byte
Glossary
583
key length that specifies the length of the records key field (0 means no key field). It defines a two-byte data length that specifies the length of the records data field (0 means no data field). Only the end-of-file record has a data length of zero. count key data (CKD) In mainframe computing, a data-record format employing self-defining record formats in which each record is represented by up to three fields: a count field that identifies the record and specifies its format, an optional key field that identifies the data area contents, and an optional data field that typically contains the user data. For CKD records on the storage unit, the logical volume size is defined in terms of the device emulation mode (3390 or 3380 track format). The count field is always 8 bytes long and contains the lengths of the key and data fields, the key field has a length of 0 to 255 bytes, and the data field has a length of 0 to 65 535 or the maximum that will fit on the track. See also data record. CPC CRC CU See cluster processor complex. See cyclic redundancy check. See control unit.
D
DA See device adapter. daisy chain See serial connection. DASD See direct access storage device. DASD fast write (DFW) A function of a storage server in which active write data is stored in nonvolatile cache, thus avoiding exposure to data loss. data availability The degree to which data is available when needed, typically measured as a percentage of time that the system would be capable of responding to any data request (for example, 99.999% available). data compression A technique or algorithm used to encode data such that the encoded result can be stored in less space than the original data. The original data can be recovered from the encoded result through a reverse technique or reverse algorithm. See also compression. Data Facility Storage Management Subsystem (DFSMS) An operating environment that helps automate and centralize the management of storage. To manage storage, DFSMS provides the storage administrator with control over data class, storage class, management class, storage group, and automatic class selection routine definitions. data field The optional third field of a count key data (CKD) record. The count field specifies the length of the data field. The data field contains data that the program writes. data record The basic unit of zSeries storage on a DS6000, also known as a count-key-data (CKD) record. Data records are stored on a track. The records are sequentially numbered starting with 0. The first record, R0, is typically called the track descriptor record and contains data that the operating system normally uses to
CUIR See control-unit initiated reconfiguration. custom volume A volume in count-key-data (CKD) format that is not a standard volume, which means that it does not necessarily present the same number of cylinders and capacity to its assigned logical control unit as provided by one of the following standard zSeries volume types: 3390-2, 3390-3, 3390-9, 3390-2 (3380-track mode), or 3390-3 (3380-track mode). See also count-key-data, interleave, standard volume, and volume. CUT See Coordinated Universal Time.
cyclic redundancy check (CRC) A redundancy check in which the check key is generated by a cyclic algorithm. (T) cylinder A unit of storage on a CKD device with a fixed number of tracks.
584
manage the track. See also count-key-data and fixed-block architecture. data set FlashCopy For zSeries hosts, a feature of FlashCopy that indicates how many partial volume FlashCopy relationships are active on a volume. data sharing The ability of multiple host systems to concurrently utilize data that they store on one or more storage devices. The storage unit enables configured storage to be accessible to any, or all, attached host systems. To use this capability, the host program must be designed to support data that it is sharing. DDM See disk drive module. DDM group See disk pack. dedicated storage Storage within a storage unit that is configured such that a single host system has exclusive access to the storage. demote To remove a logical data unit from cache memory. A storage server demotes a data unit to make room for other logical data units in the cache or because the logical data unit is not valid. The storage unit must destage logical data units with active write units before they can be demoted. See also destage. destage To move data from an online or higher priority to an offline or lower priority device. The storage unit stages incoming data into cache and then destages it to disk. device For zSeries, a disk drive. device adapter (DA) A physical component of the DS6000 that provides communication between the clusters and the storage devices. The DS6000 has eight device adapters that it deploys in pairs, one from each cluster. Device adapter pairing enables the DS6000 to access any disk drive from either of two paths, providing fault tolerance and enhanced availability.
device ID The unique two-digit hexadecimal number that identifies the logical device. device interface card A physical subunit of a storage cluster that provides the communication with the attached device drive modules. device number For zSeries, a four-hexadecimal-character identifier, for example 13A0, that the systems administrator associates with a device to facilitate communication between the program and the host operator. The device number is associated with a subchannel. device sparing A subsystem function that automatically copies data from a failing device drive module to a spare device drive module. The subsystem maintains data access during the process. DFS See distributed file service.
DFSMS See Data Facility Storage Management Subsystem. direct access storage device (DASD) 1) A mass storage medium on which a computer stores data. 2) A disk device. disk cage A container for disk drives. Each disk cage supports eight disk packs (64 disks). disk drive Standard term for a disk-based nonvolatile storage medium. The DS6000 uses hard disk drives as the primary nonvolatile storage media to store host data. disk drive module (DDM) A field replaceable unit that consists of a single disk drive and its associated packaging. disk drive module group See disk pack. disk drive set A specific number of identical disk drives that have the same physical capacity and rpm.
Glossary
585
disk pack A group of disk drive modules (DDMs) installed as a unit in a DDM bay. disk group A collection of 4 disk drives that are connected to the same pair of IBM Serial Storage adapters and can be used to create a RAID array. A disk group can be formatted as count key data or fixed block, and as RAID or non-RAID, or it can be left unformatted. A disk group is a logical assemblage of disk drives. Contrast with disk pack. distributed file service (DFS) A service that provides data access over IP networks. DNS domain 1) That part of a computer network in which the data processing resources are under common control. 2) In TCP/IP, the naming system used in hierarchical networks. 3) A Copy Services server group, in other words, the set of clusters the user designates to be managed by a particular Copy Services server. domain name system (DNS) In TCP/IP, the server program that supplies name-to-address translation by mapping domain names to internet addresses. The address of a DNS server is the internet address of the server that hosts the DNS software for the network. dotted decimal notation A convention used to identify IP addresses. The notation consists of four 8-bit numbers written in base 10. For example, 9.113.76.250 is an IP address that contains the octets 9, 113, 76, and 250. drawer A unit that contains multiple device drive modules and provides power, cooling, and related interconnection logic to make the device drive modules accessible to attached host systems. drive 1) A peripheral device, especially one that has addressed storage media. See also disk drive module. See domain name system.
2) The mechanism used to seek, read, and write information on a storage medium. DS6000 See IBM System Storage DS6000. DS6000 Batch Configuration tool A program that automatically configures a DS6000. The configuration is based on data that IBM service personnel enter into the program. DS Storage Manager See IBM System Storage DS Storage Manager. duplex 1) Regarding Copy Services, the state of a volume pair after Remote Mirror and Copy has completed the copy operation and the volume pair is synchronized. 2) In general, pertaining to a communication mode in which data can be sent and received at the same time. dynamic sparing The ability of a storage server to move data from a failing disk drive module (DDM) to a spare DDM while maintaining storage functions.
E
E10 E20 EC The predecessor of the F10 model of the Enterprise Storage Server. See also F10. The predecessor of the F20 model of the Enterprise Storage Server. See also F20. See engineering change.
ECKD See extended count key data. eight pack See disk pack. electrostatic discharge (ESD) An undesirable discharge of static electricity that can damage equipment and degrade electrical circuitry. emergency power off (EPO) A means of turning off power during an emergency, usually a switch. enclosure A unit that houses the components of a storage subsystem, such as a control unit, disk drives, and power source. end of file A coded character recorded on a data
586
medium to indicate the end of the medium. On a count-key-data direct access storage device, the subsystem indicates the end of a file by including a record with a data length of zero. engineering change (EC) An update to a machine, part, or program. Enterprise Systems Architecture/390 (ESA/390) An IBM architecture for mainframe computers and peripherals. Processor systems that follow the ESA/390 architecture include the ES/9000 family. See also z/Architecture. EPO See emergency power off.
extent pool A groups of extents. See also extent.
F
fabric In fibre channel technology, a routing structure, such as a switch, receives addressed information and routes to the appropriate destination. A fabric can consist of more than one switch. When multiple fibre-channel switches are interconnected, they are said to be cascaded. failback Pertaining to a cluster recovery from failover following repair. See also failover. failover Pertaining to the process of transferring all control to a single cluster when the other cluster in the storage unit fails. See also cluster and failback. fast write A write operation at cache speed that does not require immediate transfer of data to a disk drive. The subsystem writes the data directly to cache, to nonvolatile storage, or to both. The data is then available for destaging. A fast-write operation reduces the time an application must wait for the I/O operation to complete. FATA FBA FC See fibre-channel ATA. See fixed-block architecture. See feature code. Note: FC is a common abbreviation for fibre channel in the industry, but the DS6000 customer documentation library reserves FC for feature code.
ERDS See error-recording data set. error-recording data set (ERDS) On zSeries hosts, a data set that records data-storage and data-retrieval errors. A service information message (SIM) provides the error information for the ERDS. error recovery procedure Procedures designed to help isolate and, where possible, to recover from errors in equipment. The procedures are often used in conjunction with programs that record information on machine malfunctions. ESA/390 See Enterprise Systems Architecture/390. ESD eServer See IBM eServer. ESSNet See IBM TotalStorage Enterprise Storage Server Network. express configuration A method for configuring a storage complex, where the storage server simplifies the task by making several configuration decisions for the user. extended count key data (ECKD) An extension of the count key data (CKD) architecture. extent A continuous space on a disk that is occupied by or reserved for a particular data set, data space, or file. The unit of increment is a track. See also multiple allegiance and parallel access volumes. See electrostatic discharge.
FC-AL See Fibre Channel ATA. FCP FCS See Fibre Channel Protocol. See Fibre Channel standard.
feature code (FC) A code that identifies a particular orderable option and that is used by service personnel to process hardware and software orders. Individual optional features are each identified by a unique feature code. fibre channel A data-transmission architecture based on the ANSI Fibre Channel standard, which
Glossary
587
supports full-duplex communication. The DS6000 supports data transmission over fiber-optic cable through its fibre-channel adapters. See also Fibre Channel Protocol and Fibre Channel standard. fibre-channel ATA (FATA) A hard drive that combines a fibre channel interface with an ATA drive. FATAs, which provide the high performance and capacity of an ATA drive, can be used wherever fibre channel drives can connect. Fibre Channel Arbitrated Loop (FC-AL) An implementation of the Fibre Channel Standard that uses a ring topology for the communication fabric. Refer to American National Standards Institute (ANSI) X3T11/93-275. In this topology, two or more fibre-channel end points are interconnected through a looped interface. This topology directly connects the storage unit to an open systems host without going through a fabric switch. Fibre Channel Connection (FICON) A fibre-channel communications protocol that is designed for IBM mainframe computers and peripherals. It connects the storage unit to one or more S/390 hosts using a FICON S/390 channel either directly or through a FICON switch. Fibre Channel Protocol (FCP) A protocol used in fibre-channel communications with five layers that define how fibre-channel ports interact through their physical links to communicate with other ports. Fibre Channel standard (FCS) An ANSI standard for a computer peripheral interface. The I/O interface defines a protocol for communication over a serial interface that configures attached units to a communication fabric. The protocol has two layers. The IP layer defines basic interconnection protocols. The upper layer supports one or more logical protocols (for example, FCP for SCSI command protocols and SBCON for zSeries command protocols). Refer to American National Standards Institute (ANSI) X3.230-199x. See also Fibre Channel Protocol. fibre-channel topology An interconnection topology supported
on fibre-channel adapters. See also point-to-point connection, switched fabric, and arbitrated loop. Fibre Channel Switched Fabric (FC-SF) An implementation of the Fibre Channel Standard that connects the storage unit to one or more open systems hosts through a fabric switch or connects one or more S/390 hosts that run LINUX on an Fibre Channel Protocol S/390 channel. FICON See fibre-channel connection. FiconNet In the DS Storage Manager, the label on a pseudo host icon that represents a host connection that uses the FICON protocol and that is not completely defined on the DS6000. See also pseudo host and access-any mode. field replaceable unit (FRU) An assembly that is replaced in its entirety when any one of its components fails. In some cases, a field replaceable unit might contain other field replaceable units. (GC) FIFO See first-in-first-out.
File Transfer Protocol (FTP) In TCP/IP, an application protocol used to transfer files to and from host computers. See also Transmission Control Protocol/Internet Protocol. firewall A protection against unauthorized connection to a computer or a data storage system. The protection is usually in the form of software on a gateway server that grants access to users who meet authorization criteria. first-in-first-out (FIFO) A queuing technique in which the next item to be retrieved is the item that has been in the queue for the longest time. (A) fixed-block architecture (FBA) An architecture for logical devices that specifies the format of and access mechanisms for the logical data units on the device. The logical data unit is a block. All blocks on the device are the same size (fixed size). The subsystem can access them independently.
588
fixed-block device An architecture for logical devices that specifies the format of the logical data units on the device. The logical data unit is a block. All blocks on the device are the same size (fixed size); the subsystem can access them independently. This is the required format of the logical data units for host systems that attach with a SCSI or fibre-channel interface. See also fibre channel and small computer systems interface. FlashCopy An optional feature of the DS6000 that can make an instant copy of data, that is, a point-in-time copy of a volume. FlashCopy relationship A mapping of a FlashCopy source volume and a FlashCopy target volume that allows a point-in-time copy of the source volume to be copied to the target volume. FlashCopy relationships exist from the time that you initiate a FlashCopy operation until the storage unit copies all data from the source volume to the target volume or until you delete the FlashCopy relationship, if it is persistent. FRU FTP See field replaceable unit. See File Transfer Protocol.
Global Copy An optional capability of the DS6000 remote mirror and copy feature that maintains a fuzzy copy of a logical volume on the same DS6000 or on another DS6000. In other words, all modifications that any attached host performs on the primary logical volume are also performed on the secondary logical volume at a later point in time. The original order of update is not strictly maintained. See also Remote Mirror and Copy and Metro Mirror. Global Mirror An optional capability of the remote mirror and copy feature that provides a 2-site extended distance remote copy. Data that is written by the host to the storage unit at the local site is automatically maintained at the remote site. See also Metro Mirror and Remote Mirror and Copy. group In DS6000 documentation, a nickname for two different kinds of groups, depending on the context. See disk pack or Copy Services server group.
H
HA See host adapter. HACMP See high availability cluster multiprocessing. hard disk drive (HDD) 1) A storage medium within a storage server used to maintain information that the storage server requires. 2) A mass storage medium for computers that is typically available as a fixed disk (such as the disks used in system units of personal computers or in drives that are external to a personal computer) or a removable cartridge. hardware service manager An option on an AS/400 or iSeries host that enables the user to display and work with system hardware resources and to debug input-output processors (IOP), input-output adapters (IOA), and devices. HCD HDA HDD See Hardware Configuration Data. See head disk assembly. See hard disk drive.
full duplex See duplex. fuzzy copy A function of the Global Copy feature wherein modifications to the primary logical volume are performed on the secondary logical volume at a later time. The original order of update is not strictly maintained. See also Global Copy.
G
GB See gigabyte. GDPS See Geographically Dispersed Parallel Sysplex. Geographically Dispersed Parallel Sysplex (GDPS) A zSeries multisite application-availability solution. gigabyte (GB) A gigabyte of storage is 109 bytes. A gigabyte of memory is 230 bytes.
Glossary
589
hdisk An AIX term for storage space. head disk assembly (HDA) The portion of an HDD associated with the medium and the read/write head. heartbeat A status report sent at regular intervals from the DS6000. The service provider uses this report to monitor the health of the call home process. See also call home, heartbeat call home record, and remote technical assistance information network. heartbeat call home record Machine operating and service information sent to a service machine. These records might include such information as feature code information and product logical configuration information. hierarchical storage management 1) A function in storage management software, such as Tivoli Storage Management or Data Facility Storage Management Subsystem/MVS (DFSMS/MVS), that automatically manages free space based on the policy that the storage administrator sets. 2) In AS/400 storage management, an automatic method to manage and distribute data between the different storage layers, such as disk units and tape library devices. high availability cluster multiprocessing (HACMP) Software that provides host clustering, so that a failure of one host is recovered by moving jobs to other hosts within the cluster. high-speed loop (HSL) A hardware connectivity architecture that links system processors to system input/output buses and other system units. home address A nine-byte field at the beginning of a track that contains information that identifies the physical track and its association with a cylinder. hop Interswitch connection. A hop count is the number of connections that a particular block of data traverses between source and destination. For example, data
traveling from one hub over a wire to another hub traverses one hop. host See host system.
host adapter A physical subunit of a storage server that provides the ability to attach to one or more host I/O interfaces. host name The Internet address of a machine in the network. The host name can be entered in the host definition as the fully qualified domain name of the attached host system, such as mycomputer.city.company.com, or as the subname of the fully qualified domain name, for example, mycomputer. See also host system. host processor A processor that controls all or part of a user application network. In a network, the processing unit in which the data communication access method resides. See also host system. host system A computer, either of the mainframe (for example, zSeries) or of the open-systems type, that is connected to the DS6000. Hosts are connected through FICON or fibre-channel interfaces. hot plug Pertaining to the ability to add or remove a hardware facility or resource to a unit while power is on. HSL See high-speed loop.
I
i5/OS The IBM operating system that runs the IBM i5/OS and eServer i5 server families of servers.
IBM eServer The IBM brand name for a series of server products that are optimized for e-commerce. The products include the iSeries, pSeries, xSeries, and zSeries. IBM product engineering (PE) The third-level of IBM service support. Product engineering is composed of IBM engineers who have experience in supporting a product or who are knowledgeable about the product.
590
IBM Serial Storage adapter A physical adapter based on the IBM Serial Storage architecture. IBM Serial Storage adapters connect disk drive modules to DS6000 clusters. IBM System Storage The brand name used to identify storage products from IBM, including the IBM System Storage DS6000. See also IBM System Storage DS6000 and IBM System Storage DS Storage Manager. IBM System Storage DS6000 A member of the IBM System Storage Resiliency Family of storage servers and attached storage devices (disk drive modules). The DS6000 delivers high-performance, fault-tolerant storage and management of enterprise data, affording access through multiple concurrent operating systems and communication protocols. High performance is provided by multiple symmetrical multiprocessors, integrated caching, RAID support for the disk drive modules, and disk access through a high-speed serial storage architecture interface. IBM System Storage DS CLI The command-line interface (CLI) that is specific to the DS6000. IBM System Storage DS Storage Manager (DS Storage Manager) Software with a Web-browser interface for configuring the DS6000. IBM HyperPAV See HyperPAV. IBM TotalStorage Enterprise Storage Server Network (ESSNet) A private network providing Web browser access to the Enterprise Storage Server. IBM installs the ESSNet software on an IBM workstation called the IBM TotalStorage ESS Master Console, supplied with the first ESS delivery. IBM System Storage Management Console (MC) An IBM workstation that acts as the focal point for configuration, Copy Services management, and maintenance for the DS6000 . It includes a Web browser that provides links to the user interface, including the DS Storage Manager and the DS6000 Copy Services.
IBM System Storage Multipath Subsystem Device Driver (SDD) IBM software that provides multipath configuration support for a host system that is attached to storage devices. SDD provides enhanced data availability, dynamic input/output load balancing across multiple paths, and automatic path failover protection. IBM System Storage Resiliency Family A set of hardware and software features and products, as well as integrated software and services that are available on the IBM System Storage DS6000 and the IBM TotalStorage Enterprise Storage Server, Models 750 and 800. IML See initial microcode load.
implicit allegiance In Enterprise Systems Architecture/390, a relationship that a control unit creates between a device and a channel path when the device accepts a read or write operation. The control unit guarantees access to the channel program over the set of channel paths that it associates with the allegiance. initial microcode load (IML) The action of loading microcode for a computer into that computers storage. initial program load (IPL) The action of loading software into a computer, typically an operating system that controls the computer. initiator A SCSI device that communicates with and controls one or more targets. Contrast with target. i-node The internal structure in an AIX operating system that describes the individual files in the operating system. It contains the code, type, location, and owner of a file. input/output (I/O) Pertaining to (a) input, output, or both or (b) a device, process, or channel involved in data input, data output, or both. input/output configuration data set A configuration definition built by the I/O configuration program (IOCP) and stored on disk files associated with the processor controller.
Glossary
591
interleave To automatically create two striped partitions across the drives in a RAID-5 array, both of which use the count-key-data (CKD) record format. Internet Protocol (IP) In the Internet suite of protocols, a protocol without connections that routes data through a network or interconnecting networks and acts as an intermediary between the higher protocol layers and the physical network. The upper layer supports one or more logical protocols (for example, a SCSI-command protocol and a zSeries command protocol). Refer to ANSI X3.230-199x. The IP acronym is the IP in TCP/IP. See also Transmission Control Protocol/Internet Protocol. invalidate To remove a logical data unit from cache memory because it cannot support continued access to the logical data unit on the device. This removal might be the result of a failure within the storage server or a storage device that is associated with the device. I/O See input/output.
I/O processor (IOP) Controls input-output adapters and other devices. I/O sequential response time The time an I/O request is queued in processor memory waiting for previous I/Os to the same volume to complete. IP IPL iSeries An IBM eServer product that emphasizes integration. It is the successor to the AS/400 family of servers. See Internet Protocol. See initial program load.
J
Java Virtual Machine (JVM) A software implementation of a central processing unit (CPU) that runs compiled Java code (applets and applications). (GC) JVM See Java Virtual Machine.
K
KB See kilobyte. key field The second (optional) field of a count key data record. The key length is specified in the count field. The key length determines the field length. The program writes the data in the key field and uses the key field to identify or locate a given record. The subsystem does not use the key field. kilobyte (KB) 1) For processor storage, real, and virtual storage, and channel volume, 210 or 1024 bytes. 2) For disk storage capacity and communications volume, 1000 bytes. Korn shell Interactive command interpreter and a command programming language. KPOH See thousands of power-on hours.
I/O adapter (IOA) An input-output adapter on the PCI bus. IOCDS See input/output configuration data set. IOCP See I/O Configuration Program.
I/O Configuration Program (IOCP) A program that defines to a system all the available I/O devices and channel paths. I/O device An addressable read and write unit, such as a disk drive device, magnetic tape device, or printer. I/O interface An interface that enables a host to perform read and write operations with its associated peripheral devices. I/O Priority Queueing A facility in the Workload Manager of zSeries that enables the system administrator to set priorities for queueing I/Os from different system images. See also multiple allegiance and parallel access volumes.
L
LAN See local area network. last-in first-out (LIFO) A queuing technique in which the next item to be retrieved is the item most recently placed in the queue. (A)
592
LBA LCU
See logical block address. See logical control unit.
least recently used (LRU) 1) The algorithm used to identify and make available the cache space that contains the least-recently used data. 2) A policy for a caching algorithm that chooses to remove from cache the item that has the longest elapsed time since its last access. LED See light-emitting diode.
single host-accessible emulated I/O device. The associated storage is referred to as a logical volume. The logical device is mapped to one or more host-addressable units, such as a device on a zSeries I/O interface or a logical unit on a SCSI I/O interface, such that the host initiating I/O operations to the I/O-addressable unit interacts with the storage on the associated logical device. logical partition (LPAR) For zSeries, a set of functions that create the programming environment in which more than one logical partition (LPAR) is established on a processor. An LPAR is conceptually similar to a virtual machine environment except that the LPAR is a function of the processor. Also, the LPAR does not depend on an operating system to create the virtual machine environment. (DS8000 series only) logical path 1) The relationship between a channel image and a control-unit image that designates the physical path to be used for device-level communications between these images. The logical path is established as part of the channel and control-unit initialization procedures by the exchange of link-level frames. 2) With the Remote Mirror and Copy feature, the relationship between a source logical subsystem (LSS) and a target LSS that is created over a physical path through the interconnection fabric that is used for Remote Mirror and Copy functions. An LSS is a primary control unit, which performs the functions of a channel image. logical subsystem (LSS) A topological construct that consists of a group of up to 256 logical devices. A DS6000 can have (if CDK only) up to 32 CKD-formatted logical subsystems (8192 CKD logical devices) or (if FBA only) up to 32 fixed-block logical subsystems (8192 fixed-block logical devices). If mixed CKD and FBA, a DS6000 can have up to 16 CKD-formatted logical subsystems (4096 CKD logical devices) and up to 16 fixed-block logical subsystems (4096 fixed-block logical devices). The logical subsystem facilitates configuration of the DS6000 and might have other
Glossary
licensed machine code Microcode that IBM does not sell as part of a machine, but licenses to the customer. LMC is implemented in a part of storage that is not addressable by user programs. Some IBM products use it to implement functions as an alternate to hard-wired circuitry. LIFO See last-in first-out.
light-emitting diode (LED) A semiconductor chip that gives off visible or infrared light when activated. local area network (LAN) A computer network located on a users premises within a limited geographic area. local e-mail An e-mail configuration option for storage servers that are connected to a host-system network that does not have a domain name system (DNS) server. logical address On an ESCON interface, the portion of a source or destination address in a frame used to select a specific channel-subsystem or control-unit image. logical block address (LBA) The address assigned by the DS6000 to a sector of a disk. logical control unit (LCU) See control-unit image. logical data unit A unit of storage that is accessible on a given device. logical device The facilities of a storage server (such as the DS6000) associated with the processing of I/O operations directed to a
593
implications relative to the operation of certain functions. There is a one-to-one mapping between a CKD logical subsystem and a zSeries control-unit image. For zSeries hosts, a logical subsystem represents a logical control unit (LCU). Each control-unit image is associated with only one logical subsystem. See also control-unit image. logical unit In open systems, a logical disk drive. logical unit number (LUN) In the SCSI protocol, a unique number that is used on a SCSI bus to enable it to differentiate between separate devices, each of which is a logical unit. logical volume The storage medium that is associated with a logical disk drive. A logical volume typically resides on one or more storage devices. The DS6000 administrator defines this unit of storage. The logical volume, when residing on a RAID-formatted array, is spread over the drives in the array. logical volume manager (LVM) A set of system commands, library routines, and other tools that allow the user to establish and control logical volume storage. The LVM maps data between the logical view of storage space and the physical disk drive module. longitudinal redundancy check (LRC) 1) A method of error checking during data transfer that involves checking parity on a row of binary digits that are members of a set that forms a matrix. Longitudinal redundancy check is also called a longitudinal parity check. 2) A mechanism that the DS6000 uses for locating errors. The LRC checks the data as it progresses from the host, through theDS6000 controller, into the device adapter, and to the array. longwave laser adapter A connector that is used between a host and the DS6000 to support longwave fibre-channel communication.
loop
The physical connection between a pair of device adapters in the DS6000. See also device adapter.
LPAR See logical partition. LRC LRU LSS LUN LVM See longitudinal redundancy check. See least recently used. See logical subsystem. See logical unit number. See logical volume manager.
M
machine level control (MLC) A database that contains the EC level and configuration of products in the field. machine reported product data (MRPD) Product data gathered by a machine and sent to a destination such as an IBM support server or RETAIN. These records might include such information as feature code information and product logical configuration information. mainframe A computer, usually in a computer center, with extensive capabilities and resources to which other computers may be connected so that they can share facilities. (T) maintenance analysis procedure (MAP) A hardware maintenance document that gives an IBM service representative a step-by-step procedure for tracing a symptom to the cause of a failure. management console See IBM System Storage Management Console. management information base (MIB) 1) A collection of objects that can be accessed by means of a network management protocol. (GC) 2) The MIB record conforms to the Open Systems Interconnection (OSI) standard defined by the International Organization for Standardization (ISO) for the exchange of information. See also simple network management protocol. MAP See maintenance analysis procedure.
master storage unit The physical unit that controls the
594
creation of consistency groups in a Global Mirror session. The master storage unit sends commands to subordinate storage units. A storage unit can be a master for only one Global Mirror session. Contrast with subordinate storage unit. maximum consistency group drain time The value in seconds that indicates the maximum time that writes from the local site are delayed to the remote site while the current consistency group is being formed at the remote site. When this time is exceeded, the current attempt to form a consistency group is ended and another attempt is started. If this time is exceeded five times, this maximum time is ignored on the next attempt to form a consistency group. The default value is the larger of four minutes or two times the consistency group interval time if this value is set to zero. maximum coordination time The value in milliseconds that indicates the maximum time that is allowed for host I/O to be delayed during the coordination of the primary volumes of an Global Mirror session. The default is 50 milliseconds if this value is set to zero. MB MC MCA See megabyte. See IBM System Storage Management Console. See Micro Channel architecture.
megabyte (MB) 1) For processor storage, real and virtual storage, and channel volume, 220 or 1 048 576 bytes. 2) For disk storage capacity and communications volume, 1 000 000 bytes. Metro Mirror A function of a storage server that maintains a consistent copy of a logical volume on the same storage server or on another storage server. All modifications that any attached host performs on the primary logical volume are also performed on the secondary logical volume. See also Remote Mirror and Copy and Global Copy. MES MIB See miscellaneous equipment specification. See management information base.
Micro Channel architecture (MCA) The rules that define how subsystems and adapters use the Micro Channel bus in a computer. The architecture defines the services that each subsystem can or must provide. Microsoft Internet Explorer Web browser software manufactured by Microsoft. migration The replacement of a system or subsystem with a different type of system or subsystem, such as replacing a SCSI host adapter with a fibre-channel host adapter. In the context of data migration regarding the DS6000, the transfer of data from one storage unit to another, such as from a 3390 to the DS6000. MIH See missing-interrupt handler.
MDM See Multiple Device Manager. mean time between failures (MTBF) 1) A projection of the time that an individual unit remains functional. The time is based on averaging the performance, or projected performance, of a population of statistically independent units. The units operate under a set of conditions or assumptions. 2) For a stated period in the life of a functional unit, the mean value of the lengths of time between consecutive failures under stated conditions. (I) (A) medium For a storage unit, the disk surface on which data is stored.
mirrored pair Two units that contain the same data. The system refers to them as one entity. mirroring In host systems, the process of writing the same data to two disk units within the same auxiliary storage pool at the same time. miscellaneous equipment specification (MES) IBM field-installed change to a machine. missing-interrupt handler (MIH) An MVS and MVS/XA facility that tracks I/O interrupts. MIH informs the operator
Glossary
595
and creates a record whenever an expected interrupt fails to occur before a specified elapsed time is exceeded. MLC See machine level control.
multiple virtual storage (MVS) Implies MVS/390, MVS/XA, MVS/ESA, and the MVS element of the zSeries operating system. multiplex The action of transmitting simultaneously. multiport serial adapter (MSA) An adapter on the IBM System Storage Management Console that has multiple ports to which aDS6000 can be attached. multiprocessor A computer that includes two or more processors that have common access to a main storage. For the DS6000, the multiprocessors operate in parallel. MVS See multiple virtual storage.
mobile solutions terminal (MoST) The mobile terminal used by service personnel. mode conditioning patch cable A cable that converts a single-mode signal from a longwave adapter into a light signal that is appropriate for multimode fibre. Another mode conditioning patch cable is required at the terminating end of the multimode fibre to convert the signal back to a single-mode signal for a longwave adapter. Model 100 A 2105 Model 100, often simply referred to as a Mod 100, is an expansion enclosure for the Enterprise Storage Server. See also 2105. MoST See mobile solutions terminal. MRPD See machine reported product data. MSA See multiport serial adapter.
N
name server A server that stores names of the participating DS6000 clusters. near-line A type of intermediate storage between online storage (which provides constant, rapid access to data) and offline storage (which provides infrequent data access for backup purposes or long-term storage). Netfinity IBM Intel-processor-based server; predecessor to the IBM xSeries server. Netscape Navigator Web browser software manufactured by Netscape. network manager A program or group of programs that is used to monitor, manage, and diagnose the problems of a network. (GC) node The unit that is connected in a fibre-channel network. A DS6000 is a node in a fibre-channel network.
MTBF See mean time between failures. Multipath Subsystem Device Driver See IBM System Storage DS6000 Multipath Subsystem Device Driver. multiple allegiance A DS6000 hardware function that is independent of software support. This function enables multiple system images to concurrently access the same logical volume on the DS6000 as long as the system images are accessing different extents. See also extent and parallel access volumes. Multiple Device Manager (MDM) A component of the IBM TotalStorage Productivity Center that allows administrators to configure, manage, and monitor the performance of SAN storage devices from a single console. multiple relationship FlashCopy An option of the DS6000 that creates backup copies from one source to multiple targets by simultaneously establishing multiple FlashCopy relationships.
non-RAID A disk drive set up independently of other disk drives and not set up as part of a disk pack to store data using the redundant array of disks (RAID) data-striping methodology. nonremovable medium A recording medium that cannot be added to or removed from a storage device.
596
nonvolatile storage (NVS) Memory that stores active write data to avoid data loss in the event of a power loss. NVS See nonvolatile storage.
O
octet In Internet Protocol addressing, one of the four parts of a 32-bit integer presented in dotted decimal notation. See also dotted decimal notation.
OEMI See original equipment manufacturers information. open system A system whose characteristics comply with standards made available throughout the industry and that therefore can be connected to other systems complying with the same standards. Applied to the DS6000, such systems are those hosts that connect to the DS6000 through SCSI or FCP protocols. See also small computer system interface and Fibre Channel Protocol. organizationally unique identifier (OUI) An IEEE-standards number that identifies an organization with a 24-bit globally unique assigned number referenced by various standards. OUI is used in the family of 802 LAN standards, such as Ethernet and Token Ring. original equipment manufacturers information (OEMI) A reference to an IBM guideline for a computer peripheral interface. The interface uses ESA/390 logical protocols over an I/O interface that configures attached units in a multidrop bus topology. OS/390 The IBM operating system that includes and integrates functions that many IBM software products (including the MVS operating system) previously provided for the IBM S/390 family of enterprise servers. OUI See organizationally unique identifier.
parallel access volumes (PAV) A licensed function of the DS6000 that enables OS/390 and z/OS systems to issue concurrent I/O requests against a count key data logical volume by associating multiple devices of a single control-unit image with a single logical device. Up to eight device addresses can be assigned to a PAV. The PAV function enables two or more concurrent write operations to the same logical volume, as long as the write operations are not to the same extents. See also extent, I/O Priority Queueing, and multiple allegiance. parity A data checking scheme used in a computer system to ensure the integrity of the data. The RAID implementation uses parity to re-create data if a disk drive fails. path group In zSeries architecture, a set of channel paths that are defined to a control unit as being associated with a single logical partition (LPAR). The channel paths are in a group state and are online to the host. See also logical partition. path group identifier In zSeries architecture, the identifier that uniquely identifies a given logical partition (LPAR). The path group identifier is used in communication between the LPAR program and a device. The identifier associates the path group with one or more channel paths, thereby defining these paths to the control unit as being associated with the same LPAR. See also logical partition. PAV PCI PDU PE See parallel access volumes. See peripheral component interconnect. See protocol data unit. See IBM product engineering.
peripheral component interconnect (PCI) An architecture for a system bus and associated protocols that supports attachments of adapter cards to a system backplane. persistent FlashCopy A state where a FlashCopy relationship remains indefinitely until the user deletes it. The relationship between the source
P
panel The formatted display of information that appears on a display screen.
Glossary
597
and target volumes is maintained after a background copy completes. physical path A single path through the I/O interconnection fabric that attaches two units. For Copy Services, this is the path from a host adapter on one DS6000 (through cabling and switches) to a host adapter on anotherDS6000. pinned data Data that is held in cache until either an error condition is corrected and it can be moved to disk storage or until the data is discarded by a host command. Pinned data conditions can only occur on an ESS Model 800 during fast-write or dual-copy functions. planar The main printed circuit board (PCB) that other PCBs or assemblies plug into. The planar distributes both power and signals and therefore creates a common communications path to whichever device that plugs into it. point-in-time copy A FlashCopy option that creates an instantaneous view of original source data at a specific moment in time. point-to-point connection A fibre-channel topology that enables the direct interconnection of ports. See also arbitrated loop and switched fabric. port A physical connection on a host adapter to the cable that connects the DS6000 to hosts, switches, or another DS6000. The DS6000 uses SCSI and ESCON host adapters that have two ports per adapter, and fibre-channel host adapters that have one port. See also ESCON, fibre-channel, host adapter, and small computer system interface.
predictable if it does a format write operation for the first data record on the track. primary control unit The DS6000 to which a Remote Mirror and Copy primary device is physically attached. processor complex A partition of a storage server that is capable of performing all defined functions of the storage server. Multiple processor complexes provide redundancy. product engineering See IBM product engineering. program On a computer, a generic term for software that controls the operation of the computer. Typically, the program is a logical assemblage of software modules that perform multiple related tasks. program-controlled interruption An interruption that occurs when an I/O channel fetches a channel command word with the program-controlled interruption flag on. program temporary fix (PTF) A temporary solution to, or bypass of, a problem diagnosed by IBM as the result of a defect in a current unaltered release of a licensed program. (GC) promote To add a logical data unit to cache memory. protected volume In AS/400, a disk storage device that is protected from data loss by RAID techniques. An AS/400 host does not mirror a volume configured as a protected volume, while it does mirror all volumes configured as unprotected volumes. The DS6000, however, can be configured to indicate that an AS/400 volume is protected or unprotected and give it RAID protection in either case. protocol data unit (PDU) A unit of data specified in the protocol of a given layer and consisting of protocol control information for the layer and, possibly, user data for the layer. pSeries The product name of an IBM eServer
POST See power-on self test. power-on self test (POST) A diagnostic test that servers or computers run when they are turned on. predictable write A write operation that can cache without knowledge of the existing format on the medium. All write operations on FBA DASD devices are predictable. On CKD DASD devices, a write operation is
598
product that emphasizes performance. It is the successor to the RS/6000 family of servers. pseudo host A host connection that is not explicitly defined to the DS6000 and that has access to at least one volume that is configured on the DS6000. The FiconNet pseudo host icon represents the FICON protocol. The pseudo host icon labeled Anonymous represents hosts connected through the FCP protocol. Anonymous host is a commonly used synonym for pseudo host. The DS6000 adds a pseudo host icon only when it is set to access-any mode. See also access-any mode. PTF See program temporary fix.
drives when it assigns arrays to a device adapter pair (DA pair). See also device adapter, RAID 5, and redundant array of independent disks. random access A mode of accessing data on a medium in a manner that requires the storage device to access nonconsecutive storage locations on the medium. rank One or more arrays that are combined to create a logically contiguous storage space.
redundant array of independent disks (RAID) A methodology of grouping disk drives for managing disk storage to insulate data from a failing disk drive. refresh FlashCopy target volume An option (previously called incremental FlashCopy) of the DS6000 that creates a point-in-time data copy without copying an entire volume for each point-in-time copy. Remote Mirror and Copy A feature of a storage server that constantly updates a secondary copy of a logical volume to match changes made to a primary logical volume. The primary and secondary volumes can be on the same storage server or on separate storage servers. See also Global Mirror, Metro Mirror and Global Copy. remote technical assistance information network (RETAIN) The initial service tracking system for IBM service support, which captures heartbeat and call-home records. See also support catcher and support catcher telephone number. REQ/ACK See request for acknowledgment and acknowledgment. request for acknowledgment and acknowledgment (REQ/ACK) A cycle of communication between two data transport devices for the purpose of verifying the connection, which starts with a request for acknowledgment from one of the devices and ends with an acknowledgment from the second device. The REQ and ACK signals help to provide uniform timing to support synchronous data transfer between an
Glossary
PV Links Short for Physical Volume Links, an alternate pathing solution from Hewlett-Packard that provides for multiple paths to a volume, as well as static load balancing.
R
R0 rack See track-descriptor record. See enclosure.
RAID See redundant array of independent disks. RAID is also commonly expanded to redundant array of inexpensive disks. See also array. RAID 5 A type of RAID that optimizes cost-effective performance while emphasizing use of available capacity through data striping. RAID 5 provides fault tolerance for up to two failed disk drives by distributing parity across all the drives in the array plus one parity disk drive. The DS6000 automatically reserves spare disk drives when it assigns arrays to a device adapter pair (DA pair). See also device adapter, RAID 10, and redundant array of independent disks. RAID 10 A type of RAID that optimizes high performance while maintaining fault tolerance for up to two failed disk drives by striping volume data across several disk drives and mirroring the first set of disk drives on an identical set. The DS6000 automatically reserves spare disk
599
initiator and a target. The objective of a synchronous data transfer method is to minimize the effect of device and cable delays. reserved allegiance For zSeries, a relationship that is created in a control unit between a device and a channel path, or path group, when the device completes a Sense Reserve command. The allegiance causes the control unit to guarantee access (that is, busy status is not presented) to the device. Access is over the set of channel paths that are associated with the allegiance; access is for one or more channel programs until the allegiance ends. RETAIN See remote technical assistance information network.
protocol used to transport data between an open-systems host and a fibre-channel adapter on an DS6000. See also Fibre Channel Protocol and small computer system interface. SCSI host systems Host systems that are attached to the DS6000 with a SCSI interface. Such host systems run on UNIX, i5/OS, Windows NT, Windows 2000, or Novell NetWare operating systems. SCSI ID A unique identifier assigned to a SCSI device that is used in protocols on the SCSI interface to identify or select the device. The number of data bits on the SCSI bus determines the number of available SCSI IDs. A wide interface has 16 bits, with 16 possible IDs. SDD See IBM Subsystem Multipathing Device Driver.
S
S/390 IBM enterprise servers based on Enterprise Systems Architecture/390 (ESA/390). S/390 is the currently accepted shortened form of the original name System/390.
secondary control unit The DS6000 to which a Remote Mirror and Copy secondary device is physically attached. self-timed interface (STI) An interface that has one or more conductors that transmit information serially between two interconnected units without requiring any clock signals to recover the data. The interface performs clock recovery independently on each serial data stream and uses information in the data stream to determine character boundaries and inter-conductor synchronization. sequential access A mode of accessing data on a medium in a manner that requires the storage device to access consecutive storage locations on the medium. sequential access method (SAM) An access method for storing, deleting, or retrieving data in a continuous sequence based on the logical order of the records in the file. serial connection A method of device interconnection for determining interrupt priority by connecting the interrupt sources serially.
S/390 storage Storage arrays and logical volumes that are defined as connected to S/390 servers. This term is synonymous with count-key-data storage. SAID See system adapter identification number. SAM SAN See sequential access method. See storage area network.
SBCON See Single-Byte Command Code Sets Connection. screen The physical surface of a display device upon which information is shown to users. SCSI See small computer system interface.
SCSI device A disk drive connected to a host through an I/O interface using the SCSI protocol. A SCSI device is either an initiator or a target. See also initiator and small computer system interface. SCSI-FCP Synonym for Fibre Channel Protocol, a
600
server A host that provides certain services to other hosts that are referred to as clients. A functional unit that provides services to one or more clients over a network. (GC) service boundary A category that identifies a group of components that are unavailable for use when one of the components of the group is being serviced. Service boundaries are provided on the DS6000, for example, in each host bay and in each cluster. service clearance The area that is required to open the service covers and to pull out components for servicing. service information message (SIM) A message sent by a storage server to service personnel through an zSeries operating system. service personnel A generalization referring to individuals or companies authorized to service the DS6000. The terms service provider, service representative, and IBM service support representative (SSR) refer to types of service personnel. See also service support representative. service processor A dedicated processing unit that is used to service a storage unit. service support representative (SSR) Individuals or a company authorized to service the DS6000. This term also refers to a service provider, a service representative, or an IBM service support representative (SSR). An IBM SSR installs the DS6000. SES session A collection of volumes within a logical subsystem that are managed together during the creation of consistent copies of data. All volumes in a session must transfer their data successfully to the remote site before the increment can be called complete. SFP Small form factor pluggables. SCSI Enclosure Services.
The storage has a uniform appearance to all hosts. The host programs that access the storage must have a common model for the information on a storage device. The programs must be designed to handle the effects of concurrent access. shortwave laser adapter A connector that is used between host and DS6000 to support shortwave fibre-channel communication. SIM See service information message.
Simple Network Management Protocol (SNMP) In the Internet suite of protocols, a network management protocol that is used to monitor routers and attached networks. SNMP is an application layer protocol. Information on devices managed is defined and stored in the applications Management Information Base (MIB). (GC) See also management information base. simplex volume A volume that is not part of a FlashCopy, XRC, or PPRC volume pair. small computer system interface (SCSI) A standard hardware interface that enables a variety of peripheral devices to communicate with one another. (GC) smart relay host A mail relay or mail gateway that has the capability to correct e-mail addressing problems. SMIT See System Management Interface Tool. SMP SNMP See Simple Network Management Protocol. SNMP agent A server process that resides on a network node and is responsible for communicating with managers regarding that node. The node is represented as a managed object, which has various fields or variables that are defined in the appropriate MIB. SNMP manager A managing system that runs a managing application or suite of applications. These applications depend on Management Information Base (MIB) objects for information that resides on the managed system. Managers generate requests for
Glossary
See symmetrical multiprocessor.
shared storage Storage that is configured so that multiple hosts can concurrently access the storage.
601
this MIB information, and an SNMP agent on the managed system responds to these requests. A request can either be the retrieval or modification of MIB information. software transparency Criteria applied to a processing environment that states that changes do not require modifications to the host software in order to continue to provide an existing function. source device One of the devices in a dual-copy or remote-copy volume pair. All channel commands to the logical volume are directed to the source device. The data on the source device is duplicated on the target device. See also target device. spare A disk drive on the DS6000 that can replace a failed disk drive. A spare can be predesignated to allow automatic dynamic sparing. Any data preexisting on a disk drive that is invoked as a spare is destroyed by the dynamic sparing copy process. STI
3390-3, 3390-9, 3390-2 (3380-track mode), or 3390-3 (3380-track mode), by presenting the same number of cylinders and capacity to the host as provided by the native zSeries volume type of the same name. See self-timed interface.
storage area network A network that connects a companys heterogeneous storage resources. storage capacity The amount of data that a storage medium can hold; usually expressed in kilobytes, megabytes, or gigabytes. storage complex A configuration of one or more storage units that is managed by a management console. storage device A physical unit that provides a mechanism to store data on a given medium such that it can be subsequently retrieved. See also disk drive module. storage extent The minimum contiguous range of storage on a physical storage device, array, or rank that can be allocated to a local volume storage image A partitioning of a storage unit that provides emulation of a storage server with one or more storage devices that provides storage capability to a host computer. You can configure more than one storage image on a storage unit. (DS8000 series only) storage server A physical unit that manages attached storage devices and provides an interface between them and a host computer by providing the function of one or more logical subsystems. The storage server can provide functions that the storage device does not provide. The storage server has one or more clusters. storage unit A physical unit that consists of a storage server that is integrated with one or more storage devices that provide storage capability to a host computer.
spatial reuse A feature of serial storage architecture that enables a device adapter loop to support many simultaneous read/write operations. See also serial storage architecture. SSID SSR See subsystem identifier. See service support representative.
stacked status For zSeries, the condition when the control unit is in a holding status for the channel, and the last time the control unit attempted to present the status, the channel responded with the stack-status control. stage operation The operation of reading data from the physical disk drive into the cache. staging To move data from an offline or low-priority device back to an online or higher priority device, usually on demand of the system or on request of the user. standard volume A volume that emulates one of several zSeries volume types, including 3390-2,
602
storage unit identifier A unique identifier for a storage unit that consists of a manufacturer, a model number, a type number, a plant of manufacture, and a sequence number. striping A technique that distributes data in bit, byte, multibyte, record, or block increments across multiple disk drives. subagent An extension to an SNMP agent that permits a user to dynamically add, or in some cases replace, additional management variables in the local MIB, thereby providing a means of extending the range of information that network managers can access. See also agent. subchannel A logical function of a channel subsystem associated with the management of a single device. subordinate storage unit The physical unit that receives commands from the master storage unit and is specified when a Global Mirror session is started. The subordinate storage unit forms consistency groups and performs other Global Mirror processing. A subordinate storage unit can be controlled by only one master storage unit. Contrast with master storage unit. subsystem identifier (SSID) A number that uniquely identifies a logical subsystem within a computer installation. support catcher See catcher. support catcher telephone number The telephone number that connects the support catcher server to the DS6000 to receive a trace or dump package. See also support catcher and remote technical assistance information network. switched fabric A fibre-channel topology in which ports are interconnected through a switch. Fabric switches can also be interconnected to support numerous ports on a single network. See also arbitrated loop and point-to-point connection.
symmetrical multiprocessor (SMP) An implementation of a multiprocessor computer consisting of several identical processors configured in a way that any subset of the set of processors is capable of continuing the operation of the computer. TheDS6000 contains four processors set up in SMP mode. synchronous write A write operation whose completion is indicated after the data has been stored on a storage device. System/390 See S/390. system adapter identification number (SAID) The unique identification number that is automatically assigned to each DS6000 host adapter for use by Copy Services. System Management Interface Tool (SMIT) An interface tool of the AIX operating system for installing, maintaining, configuring, and diagnosing tasks. System Modification Program A program used to install software and software changes on MVS systems.
T
target A SCSI device that acts as a subordinate to an initiator and consists of a set of one or more logical units, each with an assigned logical unit number (LUN). The logical units on the target are typically I/O devices. A SCSI target is analogous to a zSeries control unit. See also small computer system interface. target device One of the devices in a dual-copy or remote-copy volume pair that contains a duplicate of the data that is on the source device. Unlike the source device, the target device might only accept a limited subset of data. See also source device. TB TCP/IP See Transmission Control Protocol/Internet Protocol. terabyte (TB) 1) Nominally, 1 000 000 000 000 bytes, which is accurate when speaking of bandwidth and disk storage capacity. See terabyte.
Glossary
603
2) For DS6000 cache memory, processor storage, real and virtual storage, a terabyte refers to 240 or 1 099 511 627 776 bytes. terminal emulator A function of the management console that allows it to emulate a terminal. thousands of power-on hours (KPOH) A unit of time used to measure the mean time between failures (MTBF). time sharing option (TSO) An operating system option that provides interactive time sharing from remote terminals. System Storage See IBM System Storage. TPF track See transaction processing facility. A unit of storage on a CKD device that can be formatted to contain a number of data records. See also home address, track-descriptor record, and data record.
provides a reliable host-to-host protocol between hosts in packet-switched communications networks and in interconnected systems of such networks. It uses the Internet Protocol (IP) as the underlying protocol. Transmission Control Protocol/Internet Protocol (TCP/IP) 1) A combination of data-transmission protocols that provide end-to-end connections between applications over interconnected networks of different types. 2) A suite of transport and application protocols that run over the Internet Protocol. (GC) See also Internet Protocol and Transmission Control Protocol. transparency See software transparency. TSO See time sharing option.
track-descriptor record (R0) A special record on a track that follows the home address. The control program uses it to maintain certain information about the track. The record has a count field with a key length of zero, a data length of 8, and a record number of 0. This record is sometimes referred to as R0. transaction processing facility (TPF) A high-availability, high-performance IBM operating system, designed to support real-time, transaction-driven applications. The specialized architecture of TPF is intended to optimize system efficiency, reliability, and responsiveness for data communication and database processing. TPF provides real-time inquiry and updates to a large, centralized database, where message length is relatively short in both directions, and response time is generally less than three seconds. Formerly known as the Airline Control Program/Transaction Processing Facility (ACP/TPF). Transmission Control Protocol (TCP) A communications protocol used in the Internet and in any network that follows the Internet Engineering Task Force (IETF) standards for internetwork protocol. TCP
turbo processor A faster multiprocessor that has six processors with common access to the main storage.
U
UFS UNIX filing system. Ultra-SCSI An enhanced small computer system interface. unconfigure To delete the configuration. unit address For zSeries, the address associated with a device on a given control unit. On OEMI interfaces, the unit address specifies a control unit and device pair on the interface. unprotected volume An AS/400 term that indicates that the AS/400 host recognizes the volume as an unprotected device, even though the storage resides on a RAID-formatted array and is, therefore, fault tolerant by definition. The data in an unprotected volume can be mirrored. Also referred to as an unprotected device. upper-layer protocol The layer of the Internet Protocol (IP) that supports one or more logical protocols
604
(for example, a SCSI-command protocol and an ESA/390 command protocol). Refer to ANSI X3.230-199x. UTC See Coordinated Universal Time.
worldwide node name (WWNN) A unique 64-bit identifier for a host that contains a fibre-channel port. See also worldwide port name. worldwide port name (WWPN) A unique 64-bit identifier associated with a fibre-channel adapter port. It is assigned in an implementation- and protocol-independent manner. See also worldwide node name write hit A write operation in which the requested data is in the cache. write penalty The performance impact of a classical RAID-5 write operation. WWNN See worldwide node name. WWPN See worldwide port name.
V
virtual machine facility A virtual data processing machine that appears to the user to be for the exclusive use of that user, but whose functions are accomplished by sharing the resources of a shared data processing system. An alternate name for the VM/370 IBM operating system. vital product data (VPD) Information that uniquely defines the system, hardware, software, and microcode elements of a processing system. VM The root name of several IBM operating systems, such as VM/XA, VM/ESA, VM/CMS, and z/VM. See also virtual machine facility. For zSeries, the information recorded on a single unit of recording medium. Indirectly, it can refer to the unit of recording medium itself. On a nonremovable-medium storage device, the term can also indirectly refer to the storage device associated with the volume. When multiple volumes are stored on a single storage medium transparently to the program, the volumes can be referred to as logical volumes. volume group A collection of either physical or logical volumes. volume label A unique identifier that a user assigns to a logical volume. VPD See vital product data.
X
xSeries The product name of an IBM eServer product that emphasizes industry-standard server scalability and self-managing server technologies. It is the successor to the Netfinity family of servers.
volume
Z
z/Architecture An IBM architecture for mainframe computers and peripherals. The IBM eServer zSeries family of servers uses the z/Architecture architecture. It is the successor to the S/390 and 9672 family of servers. See also iSeries. zoning In fibre-channel environments, the grouping of multiple ports to form a virtual, private, storage network. Ports that are members of a zone can communicate with each other, but are isolated from ports in other zones. z/OS An operating system for the IBM eServer product line that supports 64-bit real storage.
VSE/ESA An IBM operating system, the letters of which represent virtual storage extended/enterprise systems architecture.
W
weight distribution area The area that is required to distribute the weight of the storage unit.
z/OS Global Mirror A function of a storage server that assists a control program to maintain a
Glossary
605
consistent copy of a logical volume on another storage unit. All modifications of the primary logical volume by any attached host are presented in order to a single host. The host then makes these modifications on the secondary logical volume. This function was formerly called extended remote copy or XRC. zSeries An IBM eServer family of servers that emphasizes near-zero downtime. IBM enterprise servers based on z/Architecture. zSeries storage Storage arrays and logical volumes that are defined in the DS6000 as connected to zSeries servers.
606
Index Numerics
1750-511 and 1750-522 (DS6800) 2 1750-EX1 and 1750-EX2 expansion enclosures 3 Cisco MDS 9216 Multilayer Fabric Switch 23, 481, 497 ckd creating LCU 113 CKD deleting configurations 556 volume removal 372 CKD configuration error 115 CKD configuration error, correcting 116 ckd volume creating arrays 111 CKD volume rank 112 ckd volumes, creating 115 clearvol 417 CLI calculating hexadecimal values 230 displaying WWNN 148 pause 155 postinstallation 50 resuming Metro Mirror relationship 154 CLI commands on a command line 51 CLI commands, overview 211 CLI default configuration profile file 61 CLI help 56 CLI history function 54 CLI interactive mode 54 CLI, command-line interface 10 closeproblem 551 command flags 211 command line presentation 51 commands applykey 265 chckdvol 364 chextpool 345 chfbvol 387 chhostconnect 299 chlcu 355 chlss 383 chpass 254 chrank 333 chsession 511 chsi 281 chsu 275 chuser 255 chvolgrp 408 clearvol 417 closeproblem 551 commitflash 419 commitremoteflash 437 diagsi 282 dscli 247 exit 249 failbackpprc 468 failoverpprc 471 freezepprc 485 help 250 lsaddressgrp 353 lsarray 325 lsarraysite 320 commands (continued) lsavailpprcport 455 lsckdvol 365 lsddm 271 lsextpool 346 lsfbvol 388 lsflash 422 lshostconnect 304 lshosttype 318 lshostvol 308 lsioport 290 lskey 266 lslcu 357 lslss 384 lspe 550 lsportprof 310 lspprc 474 lspprcpath 457 lsproblem 552 lsrank 334 lsremoteflash 442 lsserver 283 lssession 513 lssi 285 lsss 548 lsstgencl 268 lssu 276 lsuser 257 lsvolgrp 410 managehostconnect 311 managepwfile 258 mkaliasvol 373 mkarray 329 mkckdvol 370 mkesconpprcpath 461 mkextpool 348 mkfbvol 394 mkflash 426 mkgmir 497 mkhostconnect 312 mklcu 359 mkpe 544 mkpprc 481 mkpprcpath 463 mkrank 338 mkremoteflash 446 mksession 512 mkuser 260 mkvolgrp 411 offloadauditlog 518 overview structure 211 pausegmir 498 pausepprc 487 quit 250 resumegmir 500 resumepprc 489 resyncflash 420 resyncremoteflash 439 reverseflash 429 revertflash 431 revertremoteflash 449
A
accessibility 571 account information 71 account setup 60 Activation (DSFA), Disk Storage Feature 8 add volumes to session, CLI 170 adding ranks to extent pool, DS CLI 127 address group 99 AIX CLI installation considerations 24 LIBPATH handling 24 AIX LIBPATH 42 alert traps 73 alias volumes 370 API, DS Open 11 applykey 265 arrays status 124 arrays, creating (ckd) 111 arrays, creating (FB) 97 arrays, deleting 125 assigning ranks 112 audit report, console 518
B
background copy 200
C
calculating hexadecimal values 230 Call Home account information 71 activating 72 testing 72 Call Home, CLI enabling 526 changing volume states Metro Mirror (DS CLI) 157, 166 chckdvol 364 checking command usage 54 chextpool 345 chfbvol 387 chhostconnect 299 chlcu 355 chlss 383 chpass 254 chrank 333 chsession 511 chsi 281 chsu 275 chuser 255 chvolgrp 408 Copyright IBM Corp. 2004, 2006
607
commands (continued) rmarray 329 rmckdvol 372 rmextpool 349 rmfbvol 397 rmflash 432 rmgmir 501 rmhostconnect 315 rmlcu 361 rmpprc 492 rmpprcpath 465 rmrank 339 rmremoteflash 450 rmsession 517 rmuser 262 rmvolgrp 413 sendpe 547 sendss 547 setcontactinfo 529 setdialhome 526 setflashrevertible 435 setioport 294 setoutput 251 setplex 522 setremoteflashrevertible 452 setrmpw 263 setsim 528 setsmtp 526 setsnmp 527 showarray 330 showarraysite 323 showckdvol 374 showcontactinfo 541 showextpool 350 showfbvol 399 showgmir 503 showgmircg 508 showgmiroos 509 showhostconnect 316 showioport 295 showlcu 362 showlss 385 showpass 263 showplex 523 showrank 340 showsi 287 showsu 278 showuser 264 showvolgrp 414 testcallhome 542 unfreezeflash 435 unfreezepprc 494 ver 267 commitflash 419 commitremoteflash 437 concurrent copy modifying timeout value (DS CLI) 158 conduit LSS 563 configuration DS Storage Manager 9 reconfiguration 9 configuration error 103 Configuration overview 18 configuration profile file 61 configuring fibre-channel I/O ports 106, 117
configuring I/O port, System i 106, 117 connection ID, caution 299 consistency group 195 modifying timeout value (DS CLI) 158 consistency group parameters, CLI 171 consistency groups creating (DS CLI) 161 console audit report 518 console mode installation, DS CLI 33 contact information, CLI 68 controlling CLI page help 56 conversions Global Copy to Metro Mirror 566 Metro Mirror to Global Copy 566 converting Metro Mirror (DS CLI) 164 volume pairs 164 Copy Services across 2105 and 1750 167 across 2105 and 2107 167 disaster recovery 16 licensed functions 17 overview 12 correcting path-related configuration error 150 wrong value for remote WWNN 150 wrong value for target LSS ID 150 correcting a CKD configuration error 116 correcting fixed block configuration error 103 correcting FlashCopy relationships, commitflash command 198 correcting FlashCopy relationships, revertflash command 197 count key data volumes creating extent pools 110 create FlashCopy relations, Global Mirror 182 create Global Copy pairs 181 create paths, Global Mirror 179 creating ckd volumes 115 consistency group (DS CLI) 153, 161 extent pools, fixed block 96 fixed block volume groups 103 fixed block volumes 99 FlashCopy relationship 135 LUN volumes 101 Metro Mirror volume pair using a 2105 (DS CLI) 167 persistent FlashCopy 136 ranks for CKD volumes 112 SCSI host port connections 107 volume groups for System i 105 creating a rank, DS CLI 98 creating arrays (ckd) 111 creating arrays (FB) 97 creating extent pools, CKD 110 critical heavy mode 481 critical mode setting (DS CLI) 159 critical volume mode 481 customer name for SMC PE package 88
D
DDM status 123 decimal 230 default CLI settings 61 default directories 51 default report format 251 delete arrays 125 delete extent pools, DS CLI 123 delete LCUs 133 delete ranks 130 deleting FlashCopy relationships 138 paths 151 single volume relationship (DS CLI) 166 volume pair (DS CLI) 157 deleting CKD configurations 560 deleting fixed block configuration 556 delim report format 251 determining available I/O ports 164 diagsi 282 disaster recovery Copy Services 16 drain time 204 failback scenario (DS CLI) 162 failover (DS CLI) 163 failover B volumes to A volumes 194 first pass 204 OOS 204 quiesce your system 204 disaster recovery, Global Mirror background copy 200 begin the failback recovery process 202 checking status 193 consistency group analysis 195 correcting FlashCopy relationships, commitflash command 198 end Global Mirror processing 192 fast reverse restore 199 Global Copy failback 207 Global Copy failover 207 process overview 191 reestablish FlashCopy relationships, B to C 201 reestablishing paths 205 resume Global Mirror processing 208 resume Global Mirror processing at the A site 208 resynchronize B volumes to A volumes 203 revertflash and FlashCopy relationships 197 disk drive module 123 Disk Storage Feature Activation (DSFA) 8 displaying paths 148 DS CLI console mode installation 33 create paths 149 creating volume pairs 152, 156 default directories 51 determining 164
608
DS CLI (continued) first time login 51 graphical mode installation 27 I/O ports 164 installation on Linux 33 interactive mode 54 limitations 23 OpenVMS messages 569 persistent setup, OpenVMS 49 script mode 53 session limitation 23 silent mode installation 39 silent mode installation, DS CLI 39 single-shot mode 53 DS CLI command format 51 DS CLI commands System i 118 DS CLI exit codes 57 DS CLI installation AIX considerations 24 default directories 24 HP Tru64 considerations 24 mounting the installation CD 24 preparing for 24 System i considerations 24 DS CLI Tasks Global Mirror add volumes to session 170 create FlashCopy relationships 182 create Global Copy pairs 181 create session 183 end a session 185 end processing, no script 178 end processing, script mode 177 modify tuning parameters 171 pausing processing 175 query Global Mirror session 175 remove FlashCopy relationships 186 remove Global Copy relationships 187 remove paths 188 remove volumes 184 resume processing 176 setup, creating paths 179 start processing 176 view session 174 DS CLI Tasksmodify topology Global Mirror 172 DS command-line interface 10 DS Open API 11 DS Storage Manager 9 DS6000 major features 1 DS6000 interfaces 9 dscli 247 dscli command 247 DSFA, Disk Storage Feature Activation 8
extent extent extent CLI extent extent
pool modifications, CLI 121 pool names 96 pool, adding ranks with DS 127 pools, delete with DS CLI 123 pools, System i 96
FTP transfer failed, statesave file 91 FTP, problem determination process 85 functions Copy Services 12
G
Global Copy creating volume pairs 156 Global Copy failback 207 Global Copy failover 207 Global Copy pairs, create 181 Global Mirror 16 Global Mirror - CLI add volumes to session 170 create FlashCopy relationships 182 create Global Copy pairs 181 create session 183 end processing, no script 178 end processing, script mode 177 end session 185 modify topology 172 modify tuning parameters 171 pausing processing 175 query session 175 remove FlashCopy relationships 186 remove Global Copy pair 187 remove paths 188 remove volumes 184 resume processing 176 setup environment, paths 179 start processing 176 view session 174 Global Mirror processing, ending 192 graphical mode installation, DS CLI 27
F
failback disaster recovery scenario (DS CLI) 162 local to remote 564 failback recovery process 202 failbackpprc 468 failover disaster recovery (DS CLI) 163 failover and fallback 16 failoverpprc 471 fast reverse restore 199 FATA disk drives 1 feature licensing 8 Fibre Channel Protocol 11 fibre-channel ATA (FATA) disk drives 1 fibre-channel I/O ports configuring 106, 117 fc-al 106, 117 ficon 106, 117 scsi-fcp 106, 117 FICON 11 finding PE package files 550 finding statesave files 548 first pass 204 first time login 51 fixed block deleting configurations 556 fixed block configuration error, correcting 103 fixed block volume creating arrays 97 fixed block volume groups, creating 103 fixed block volume groups, modifying 555 fixed block volumes creating extent pools 96 fixed block volumes, creating 99 FlashCopy background copy 143 creating a FlashCopy relationship 135 deleting relationships 138 persistent creating 136 refreshing target volumes 140 reversing relationship 141 revertible option 142 revertible option defined 142 setflashrevertible 142 target volumes on Metro Mirror source 145 removing write inhibits 144 viewing information about FlashCopy relationships 137 FlashCopy relationships, create 182 force parameter 468, 471 freezepprc 485 FTP transfer failed, pe package 89
H
help 250 help, CLI 56 hex 230 hexadecimal 230 host systems adapter types 11 HP-UX volume restriction 299
I
I/O ports available 164 i5/OS command format 53 green screen, DS CLI 118 library QDSCLI 118 removing DS CLI directly 79 silent mode CLI installation 39 i5/OS password file directory 258 IBMDSCLI$STARTUP.COM procedure 49 implementation, RAID 7 inband transactions 139, 563 incremental FlashCopy copying updated tracks only 140 incrementalresync 481 Index
E
end Global Mirror script mode 177 ending Global Mirror processing 192 exception events 73 exit 249 exit codes, obtaining 57
609
installing the CLI 50 interactive mode history function 54 setoutput command 54 interfaces, DS6000 9 Internet Explorer 4 iSeries i5/OS password file directory 258 issuing DS CLI commands 118 i5/OS 118
J
JVM not found error 42
lsproblem 552 lsrank 334 lsremoteflash 442 lsserver 283 lssession 513 lssi 285 command 148 lsss 548 lsstgencl 268 lssu 276 lsuser 257 lsvolgrp 410 LUN sizes 394 LUN volumes, creating 101
multiple ranks status 129
N
near-line 1 Netscape Navigator 4 nonrevertible 197, 198 Novell DS CLI graphical installation 27
O
offloadauditlog 518 offloaded statesave files 547 OpenVMS DS CLI message considerations 569 ECOs for installation 44 IBMDSCLI$STARTUP.COM procedure 49 installing CLI 44 lshostvol command considerations 308 mounting the installation CD 44 persistent setup 49 Polycenter software installation utility 44 preparing for CLI installation 44 operational limitations 23 OS/400 DS CLI graphical installation 27 os400all 105 os400mask 105 out-of-sync 204 overview Copy Services 12
M K
keyboards accessibility features 571 managehostconnect 311 management console 4 managepwfile 258 message types 569 Metro Mirror consistency groups 153 creating volume pairs 152 FlashCopy target on Metro Mirror source 145 scenario 564 mkaliasvol 373 mkarray 329 mkckdvol 370 mkesconpprcpath 461 mkextpool 348 mkfbvol 394 mkflash 426 mkgmir 497 mkhostconnect 312 mklcu 359 mkpe 544 mkpprc 481 volume pairs 152, 156 mkpprcpath 463 creating paths 149 mkrank 338 mkremoteflash 446 mksession 512 mkuser 260 mkvolgrp 411 Models 1750-511 and 1750-522 2 Models 1750-EX1 and 1750-EX2 3 modify extent pool, CLI 121 modify a rank, CLI 127 modify an LCU, CLI 131 modify topology, CLI 172 modify tuning parameters, CLI 171 modifying concurrent copy timeout value (DS CLI) 158 consistency group timeout (DS CLI) 158 critical mode setting (DS CLI) 159 fixed block volume groups 555 timeout values (DS CLI) 158 z/OS Global Mirror (DS CLI) 159 mounting the installation CD 24 multiple LCU status 132
L
LCU creation 113 LCU status 132 LCU status, one 133 LCU, modify with CLI 131 LCUs, deleting 133 legal terms and conditions 574 library QDSCLI 118 licensed functions 8 Copy Services 17 limitations remote FlashCopy 139 Linux DS CLI installation, console mode lshostvol command considerations 308 Linux password file directory 258 lock account 255 logical control unit creation 113 logical control unit properties 133 lsaddressgrp 353 lsarray 325 lsarraysite 320 lsavailpprcport 455 lsckdvol 365 lsddm 271 lsextpool 346 lsfbvol 388 lsflash 422 lshostconnect 304 lshosttype 318 lshostvol Linux considerations 308 OpenVMS considerations 308 lsioport 290 lskey 266 lslcu 357 lslss 384 lspe 550 lsportprof 310 lspprc 474 lspprcpath 457 command 148
P
password file directories i5/OS 258 LINUX 258 UNIX 258 Windows 258 paths creating 149 deleting 151 displaying 148 lspprcpath 161 mkpprcpath 149 port considerations 149 view existing 161 Paths correcting configuration error 150 pausegmir 498 pausepprc 487 suspending volumes 155 pe package 544 pe package files 547 performance features 6 persistent FlashCopy creating 136 persistent setup 49 planning licensed functions 8 Polycenter software installation utility 44 postinstallation CLI 50
33
610
postinstallation tasks 50 primary volumes 194 problem determination process, FTP processing tips 3 site recovery 481 cascade 481 incrementalresync 481 multiple volumes 481 volume grouping method 481
85
Q
query Global Mirror session 175 quiesce your system 204 quit 250
R
RAID implementation 7 RAID 10 overview 8 RAID 5 overview 8 RAID overview 7 rank configuration 98, 112 rank group 1 or 1 112 rank status, one 129 rank, create with DS CLI 98 rank, modify with CLI 127 ranks status 129 ranks, deleting 130 reestablishing remote mirror and copy paths 205 relationship reversing FlashCopy 141 release rank, CLI 127 remote FlashCopy limitations 139 remote FlashCopy transactions 563 Remote Mirror and Copy relationships viewing (DS CLI) 163 remote support contact information 68 remove arrays 125 remove LCUs 133 remove ranks 130 removing uncorrupted incremental backup 144 write inhibits from FlashCopy target volumes 144 removing DS CLI, i5/OS 79 report formats controlling 54 default 251 delim 251 setoutput command 251 stanza 251 XML 251 requirements management console 4 reserve rank, CLI 127 resume Global Mirror processing 176 resumegmir 500 resumepprc 489 resuming volumes 154
resync target volumes in FlashCopy relationship 140 resyncflash 420 resynchronize B volumes to A volumes 203 resyncremoteflash 439 reverse a FlashCopy relationship 199 reverseflash 429 revertflash 431 revertremoteflash 449 rmarray 329 rmckdvol 372 rmextpool 349 rmfbvol 397 rmflash 432 rmgmir 501 rmhostconnect 315 rmlcu 361 rmpprc 492 rmpprcpath 465 rmrank 339 rmremoteflash 450 rmsession 517 rmuser 262 rmvolgrp 413
S
S/390 messages 73 script mode 53 script mode, end processing 177 SCSI host port connections creating 107 secure shell connection 71 sending a pe package 89 sending a statesave file 91 sendpe 547 sendss 547 serial number, obtaining 55 Service information messages 73 setcontactinfo 529 setdialhome 526 setflashrevertible 435 setioport 294 setoutput 251 setplex 522 setremoteflashrevertible 452 setrmpw 263 setsim 528 setsmtp 526 setsnmp 527 setup, account 60 showarray 330 showarraysite 323 showckdvol 374 showcontactinfo 541 showextpool 350 showfbvol 399 showgmir 503 showgmircg 508 showgmiroos 509 showhostconnect 316 showioport 295 showlcu 362 showlss 385 showpass 263
showplex 523 showrank 340 showsi 287 showsu 278 showuser 264 showvolgrp 414 SIM messages 73 single volume relationship deleting (DS CLI) 166 single-shot mode command format, i5/OS 53 command format, Windows 53 SMC pe package 544 SMC PE package 88 SNMP notifications 73 stanza report format 251 starting FlashCopy 143 status information, fixed block volume 388 stop the process Global Mirror 501 storage image ID, obtaining 55 support operations SNMP notifications 73 support options, CLI Call Home activation 72 e-mail notifications 70 SMTP 70 system compatibility 4 System i bypassing uninstaller 79 CLI installation considerations 24 configuring I/O port 106, 117 creating FlashCopy relationships 135 Global Copy pairs 156 Metro Mirror pairs 152 DS CLI commands 118 extent pool considerations 96 host connections 107 interactive mode 54 issuing 118 LUN volumes 101 lunmapping 414 os400all 105 os400mask 105 postinstallation tasks 50 removing CLI, direct method 79 removing CLI, remote method 79 script mode 53 serial number reporting 287 showvolgrp 414 single-shot mode 53 volume group creation external load source consideration 105 multipath consideration 105
T
target volume commit changes 147 discard changes 146 FlashCopy commit changes 147 discard changes 146 Index
611
testcallhome 542 thaw operation 494, 564 timeout connection 61 timeout values modifying concurrent copy (DS CLI) 158 consistency group (DS CLI) 158 critical mode enabled (DS CLI) 158 z/OS Global Mirror (DS CLI) 158 topology defined, CLI 172 Trademarks 575 troubleshooting DS CLI commands, FTP 85 Troubleshooting DS CLI commands, no ftp 92 tuning parameters, CLI 171
write inhibits (continued) removing from FlashCopy target volumes 144 wwnn displaying for paths 148
X
XML report format 251
Z
z/OS Global Mirror modifying critical mode setting (DS CLI) timeout value (DS CLI) 159 zones WWPN 11 zSeries system messages 73 159
U
unassign rank, CLI 127 unattended (silent) mode installation 39 unattended (silent) mode installation, DS CLI 39 unfreezeflash 435 unfreezepprc 494 uninstall.dat 79 uninstall.jar 79 UNIX DS CLI graphical installation 27 UNIX password file directory 258 unlock account 255
V
ver 267 view a specific LCU 133 view a specific rank 129 view array sites status 124 view arrays status 124 view LCU status 132 view ranks status 129 view session, CLI 174 viewing existing paths 161 information about FlashCopy relationships 137 Remote Mirror and Copy relationships (DS CLI) 163 volume format processing options 481 volume pair deleting (DS CLI) 157 volume removal, CKD 372 volumes FlashCopy target volumes commit changes 147 discard changes 146 volumes, alias 370
W
Windows DS CLI graphical installation 27 Windows password file directory 258 write acceleration restriction 23, 481, 497 write inhibits mkflash command 144
612
Readers comments we would like to hear from you

IBM System Storage DS6000 Command-Line Interface Users Guide Version 1 Release 2 Publication No. GC26-7922-00 We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. For technical questions and information about products and prices, please contact your IBM branch office, your IBM business partner, or your authorized remarketer. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. Comments:
Thank you for your support. Submit your comments using one of these channels: v Send your comments to the address on the reverse side of this form. If you would like a response from IBM, please fill in the following information:
Name Company or Organization Phone No.
Address
E-mail address
___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You

GC26-7922-00
Cut or Fold Along Line
Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation Information Development Department 61C 9032 South Rita Road Tucson, AZ 85775-4401
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
GC26-7922-00
Cut or Fold Along Line
Printed in USA
GC26-7922-00

DS6000

Uploaded by

Document Informationclick to expand document informationThis edition replaces GC26-7681-06 and all previous versions. This edition also applies to all subsequent releases and modifications until otherwise indicated in new editions.

Document Informationclick to expand document information

Copyright:

Available Formats

DS6000

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DS6000

Uploaded by

Copyright:

Available Formats

IBM System Storage DS6000

Command-Line Interface Users Guide

IBM System Storage DS6000

Command-Line Interface Users Guide

Chapter 4. Providing PE package and state save information . . . . . . . . 85

Chapter 5. Configuring and managing logical storage . . . . . . . . . . . 95

Chapter 6. Copy Services functions

Chapter 7. Recovering from a disaster using Global Mirror . . . . . . . . . 191

DS6000 CLI Users Guide

Chapter 8. CLI commands . . . . . . 211

Chapter 9. Command-line interface scenarios . . . . . . . . . . . . . 555

560 563 564 566

. 576 . 576 . 576 . 577 . 578 . 578 . 578

DS6000 CLI Users Guide

About this guide

Copyright IBM Corp. 2004, 2006

DS6000 CLI Users Guide

Notices and publication information

Product recycling and disposal

Copyright IBM Corp. 2004, 2006

Battery return program

DS6000 CLI Users Guide

Please recycle batteries.

Conventions used in this guide

Notices and publication information

DS6000 series library

IBM System Storage DS Application Programming Interface Reference

DS6000 CLI Users Guide

Other IBM publications

IBM Enterprise Storage Server

Implementing Copy Services 0n S/390

Notices and publication information

Title IBM TotalStorage ESS Implementing Copy Services in an Open Environment

Fibre Channel Connection (FICON) I/O Interface: Physical Layer

This publication provides information about fibre-optic and ESCON-trunking systems.

DS6000 CLI Users Guide

Title IBM TotalStorage ESS Implementing Copy Services in an Open Environment

Implementing Fibre Channel Attachment on the ESS

Device Support Facilities: Users Guide and Reference

z/OS Advanced Copy Services

ES/9000, ES/3090: IOCP User Guide Volume A04

IOCP Users Guide, IBM e(logo)server zSeries 800 and 900

Notices and publication information

Title IOCP Users Guide, IBM e(logo)server zSeries

Order Number SB10-7037

z/Architecture Principles of Operation

DS6000 CLI Users Guide

Title IBM OS/390 Hardware Configuration Definition Users Guide

Order Number SC28-1848

Device Support Facilities: Users Guide and Reference

IBM TotalStorage Solutions Handbook

Ordering IBM publications

Notices and publication information

IBM publications center

DS6000 CLI Users Guide

How to send your comments

Notices and publication information

DS6000 CLI Users Guide