HP - PerformanceControlUG Rootsan Technologies PVT LTD

HP StorageWorks
Performance Control XP user guide
Part number: T1605-96005

Fourth edition: June 2006
Legal and notice information
© Copyright 2005, 2006 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor’s standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
shall not be liable for technical or editorial errors or omissions contained herein.
Adobe® and Acrobat® are registered trademarks of Adobe Systems Incorporated.
Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd. The Hitachi Data Systems design mark is a trademark and service
mark of Hitachi, Ltd.
Hi-Track is a registered trademark of Hitachi Data Systems Corporation.
Hitachi Graph-Track, Hitachi Freedom Storage and Hitachi Lightning 9900 are trademarks of Hitachi Data Systems Corporation.
ESCON, z/OS, and S/390 are registered trademarks or trademarks of International Business Machines Corporation (IBM).
HP-UX is a product name of Hewlett-Packard Company.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.
Netscape Navigator is a registered trademark of Netscape Communications Corporation in the United States and other countries.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of X/Open Company Limited in the United States and other countries and is licensed exclusively through X/Open
Company Limited.
Windows and Windows NT are registered trademarks of Microsoft Corporation.
Performance Control XP user guide

Contents
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Performance Control XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Optimal performance of high-priority hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Automatically disabling upper limit control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview of Performance Control XP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Procedure for one-to-one connections between HBAs and ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Procedure for many-to-many connections between HBAs and ports. . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Notes on using Performance Control XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Performance Control XP restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Using Performance Control XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Starting Performance Control XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pane contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Top section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Tree section (WWN tab only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Bottom section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Managing traffic between HBAs and ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting the priority of ports on arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Measuring traffic between host bus adapters and ports for many-to-many connections . . . . . . . . . . . . . 23
Analyzing traffic statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Setting upper limit values for traffic at non-prioritized ports or WWNs . . . . . . . . . . . . . . . . . . . . . . . . 24
Setting thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Changing PFC names of host bus adapters (many-to-many connections only). . . . . . . . . . . . . . . . . . . . 25
Replacing host bus adapters (many-to-many connections only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Grouping host bus adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Adding multiple HBAs to a PFC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Switching the priority of PFC groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Setting upper limit values for HBAs in a PFC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Renaming PFC groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deleting PFC groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3 Troubleshooting Auto LUN/Performance Control Base Monitor and Performance

Control XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
A Performance Control Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Overview of Auto LUN XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 31
Exporting monitoring data to files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 31
Files to be exported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 32
Preparing for using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 45
Requirements for using the Export Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 45
Installing the Export Tool on a Windows computer . . . . . . . . . . . . . . . . . . . . . .. .. . .. . ...... 46
Performance Control XP user guide 3

Installing the Export Tool on a UNIX computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Using the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Preparing a command file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Preparing a batch file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Running the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Command reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Command syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
The svpip subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
The retry subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The login subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The show subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The group subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
The shortrange subcommand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
The longrange subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
The outpath subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
The option subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The apply subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The set subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4
The help subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
The java command for exporting data In files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Troubleshooting the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
B Limitations for storage partition administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Limitations of Auto LUN XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Limitations of the Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figures
1 Network A (one-to-one connections between HBAs and ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Priority specified in the Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Traffic at ports on network A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 Network B (many-to-many connections between HBAs and ports). . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Specifying host bus adapters to be monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 Priority specified in the Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 Traffic at ports on network B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8 Setting upper limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
9 Graphs indicating changes in port traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10 Port tab in the Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
11 WWN tab in the Performance Control pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
12 Add WWN dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
13 Change WWN and PFC Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
14 Add New PFC Group dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
15 Change Upper Limit dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
16 Change PFC Group Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
17 Sample text file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
18 Sample command file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
19 Scripts in batch files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
20 Scripts in batch files (when specifying the proxy host’s host name) . . . . . . . . . . . . . . . . . . . . . . . . . . 50
21 Scripts in batch files (when specifying the IP address of a proxy host). . . . . . . . . . . . . . . . . . . . . . . . 51
22 An example of executing a batch file (on a Windows computer) . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
23 Sample command prompt outputs when the Export Tool runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
24 Sample batch file including a reference to termination code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
25 Examples of comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
26 Information output by the show subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
27 Starting and ending times for collecting monitoring data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
28 Starting and ending time for collecting monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
29 An example of a text file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Tables
1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
2 Auto LUN XP panes and monitoring data that can be saved by the Export Tool . . . . . . . . . . . . . . . . . 32
3 Files containing statistics about resource usage and write pending rates . . . . . . . . . . . . . . . . . . . . . . . 33
4 Files containing statistics about parity, external volume, and V-VOL groups . . . . . . . . . . . . . . . . . . . . 35
5 Files containing statistics about logical volumes in parity, external volume, or V-VOL groups . . . . . . . . 36
6 Files containing statistics about ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7 Files containing statistics about host bus adapters connected to ports . . . . . . . . . . . . . . . . . . . . . . . . 37
8 Files containing statistics about LU paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9 Files containing statistics about SPM groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10 Files containing statistics about host bus adapters belonging to SPM groups . . . . . . . . . . . . . . . . . . . 38
11 Files containing statistics about remote copy operations by Continuous Access XP and TrueCopy

for z/OS (in the whole array) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
for z/OS (at LU paths) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
for z/OS (at logical volumes controlled by a particular CU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
for z/OS (at CLPR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
15 Files containing statistics about remote copy operations by Continuous Access XP Journal and
Universal Replicator for z/OS (in the whole array) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16 Files containing statistics about remote copy operations by Continuous Access XP and Universal
for z/OS (at journal groups) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Universal Replicator for z/OS (at LU paths). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Universal Replicator for z/OS (at logical volumes controlled by a particular CU) . . . . . . . . . . . . . . . . . 45
19 Errors for which the Export Tool retries processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
20 Estimate examples of time required for exporting files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
21 Termination codes that the Export Tool returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
22 Subcommand list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
23 Syntax descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
24 Operands of the group subcommand and saved monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . 59
25 Monitoring items to which the longrange subcommand can be applied. . . . . . . . . . . . . . . . . . . . . . 70
26 Troubleshooting the Export Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
27 Messages to be issued by the Export Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
28 Limitations for storage partition administrators (Auto LUN XP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6
About this guide
This guide provides information about:
• Understanding Performance Control XP
• Starting Performance Control XP
• Using the Performance Control pane
• Managing traffic between HBAs and ports
• Grouping host bus adapters
• Troubleshooting Auto LUN/Performance Control Base Monitor and Performance Control XP
• Using the Performance Export Tool to export monitoring data to files
• Troubleshooting the Performance Export Tool
• Understanding limitations for storage partition administrators
Supported storage platforms and firmware

In this guide, the term array refers to the following storage platforms:
• HP StorageWorks XP12000 Disk Array
For information about required firmware versions, see the HP StorageWorks XP Remote Web Console
user guide for XP12000/XP10000/SVS200.
Intended audience
This guide is intended for customers and HP-authorized service providers with knowledge of:
• Disk array hardware and software
• Data processing and RAID storage subsystems and their basic functions
NOTE: The functions described in this manual may be limited, depending on your assigned level of user
access. Some users will have read-only access while others will have limited or full array access. For
additional information on users and user groups, please see the HP StorageWorks XP Remote Web
Console user guide for XP12000/XP10000/SVS200.
Prerequisites
Prerequisites for using this product include:
• Installing the HP StorageWorks disk array(s)
• Installing the license key for this product
Related documentation
The following documents provide related information:
• HP StorageWorks XP glossary
• HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200
• HP StorageWorks Auto LUN XP user guide for the XP12000/XP10000
• HP StorageWorks Auto LUN XP user guide for the XP1024/XP128
• HP StorageWorks LUN Configuration and Security Manager XP user guide for the
XP12000/XP10000/SVS200
• HP StorageWorks LUN Configuration and Security Manager XP user guide for the XP1024/XP128

You can find these documents at http://www.hp.com/support/rwc/manuals
Document conventions and symbols

Table 1 Document conventions
Convention Element
Blue text: Table 1 Cross-reference links and e-mail addresses
Blue, underlined text: (http://www.hp.com) Web site addresses
Bold text • Keys that are pressed

• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as
menu and list items, buttons, and check boxes
Italic text Text emphasis
Monospace text • File and directory names

• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text • Code variables
• Command variables
Monospace, bold text Emphasized monospace text
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT: Provides clarifying information or specific instructions.
NOTE: Provides additional information.
TIP: Provides helpful hints and shortcuts.
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/.
Collect the following information before calling:
• Technical support registration number (if applicable)
• Product serial numbers
• Product model names and numbers
• Error messages
• Operating system type and revision level
• Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
8
Subscription service
HP recommends that you register your product at the Subscriber’s Choice for Business web site:
http://www.hp.com/go/e-updates.
After registering, you will receive e-mail notification of product enhancements, new driver versions,
firmware updates, and other product resources.
HP web sites
For additional information, see the following HP web sites:
• http://www.hp.com
• http://www.hp.com/go/storage
• http://www.hp.com/service_locator
• http://www.hp.com/support/manuals
• http://www.hp.com/support/downloads
• http://www.hp.com/support/rwc/manuals
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to
storagedocs.feedback@hp.com. All submissions become the property of HP.

10
1 Performance Control XP
Use Performance Control XP to ensure that I/O operations for hosts requiring high performance receive
higher priority than I/O operations for other hosts.
Optimal performance of high-priority hosts

In a storage area network (SAN) environment, arrays are usually connected to several host servers. Some
types of host servers might require high performance, while the performance of other hosts is less critical.
For example, production servers, such as database servers and application servers, perform daily
business tasks requiring top performance. When performance of these servers drops, productivity in
critical business activities decreases. Therefore, system administrators must maintain performance of
production servers at optimal levels.
Computer systems in business organizations often include lower-priority servers, such as development
servers. Development servers are used for developing, testing, and debugging business applications. If
performance levels of development servers drops, developers are unhappy, but the productivity of critical
business applications is not affected. Therefore, production servers are given higher priority than
development servers.
Use Performance Control XP to limit I/O requests from development servers to arrays and limit the amount
of data transferred between development servers and arrays. Production servers can expect faster
response times and better performance.
Throughout this chapter, the term upper limit control refers to limiting performance of low-priority host
servers to maintain performance of high-priority host servers.
Automatically disabling upper limit control

While upper limit control improves performance of production servers, it is not always useful. Upper limit
control is not required when production servers are not busy. For example, if the number of production
server I/O operations is very high from 9:00 a.m. to 3:00 p.m. and decreases sharply thereafter, upper
limit control suppresses performance of development servers even after 3:00 p.m. Development servers
should be free from upper limit control when production servers are not busy.
Performance Control XP provides a function called threshold control that automatically disables upper limit
control when traffic between production servers and arrays decreases to a certain level. A threshold is a
value indicating the conditions at which upper limit control is disabled. For example, if you apply a
threshold of 500 IO/s (500 I/O operations per second) to the entire array, the I/O rate of development
servers is not limited when the number of I/Os from all production servers is below 500 IO/s. If the
number of production server I/Os increases beyond 500 IO/s, upper limit control is restored to limit the
number of I/Os from development servers.
The threshold can control the I/O rate (number of I/Os per minute) or transfer rate (amount of data
transferred per second). For example, if a you set a threshold of 20 MB/s (20 megabytes per second) for
an array, the I/O rate limit for development servers is disabled when the amount of data transferred
between the array and all production servers is below 20 MB/s.
Overview of Performance Control XP procedures

The procedure for using Performance Control XP depends on the type of connection established between
host bus adapters (HBAs) and array ports. For one-to-one connections between HBAs and ports, use the
Port tab of the Performance Control pane. For many-to-many connections between HBAs and ports, use
the WWN tab of the Performance Control pane.

Procedure for one-to-one connections between HBAs and ports
Figure 1 shows an example of a network where each host bus adapter is connected to only one port on
the array. (Henceforth, this network is referred to as network A.) Host bus adapters and array ports are
connected directly, rather than through hubs and switches.
Figure 1 Network A (one-to-one connections between HBAs and ports)

In this example, setting up Performance Control XP requires the following major steps:
1. Set the priority of array ports. Use the Port tab of the Performance Control pane to specify the priority
of each port on the array.
In network A, ports 1A and 1C are connected to high-priority production servers. Port 2A is connected
to a low-priority development server. Therefore, ports 1A and 1C should be given high priority, and
port 2A should be given low priority.
Figure 2 shows a portion of the Performance Control pane. Prio. indicates that the port is given high
priority, and Non-Prio. indicates that the port is given low priority.
NOTE: Throughout this chapter, prioritized port refers to a high-priority port and non-prioritized
port refers to a low-priority port.
Figure 2 Priority specified in the Performance Control pane

2. Monitor traffic at ports. Obtain statistics about traffic at each port on the array.
Auto LUN provides two types of traffic statistics: I/O rate (number of I/Os per second) and transfer
rate (amount of data transferred between a host and array). When viewing traffic statistics in the
Performance Control pane, select the I/O or transfer rate. The Port-LUN tab of the Performance
Monitor pane displays a line graph illustrating changes in traffic.
Figure 3 shows changes in the I/O rate for the three ports (1A, 1C, and 2A). At first the I/O rate for
ports 1A and 1C was approximately 400 IO/s and the I/O rate for port 2A was approximately
100 IO/s. However, the I/O rate for port 2A gradually increased and the I/O rate for ports 1A and
1C decreased, lowering the performance of the high-priority production servers. As network
administrator, you might want to maintain the I/O rate for prioritized ports 1A and 1C at 400 IO/s.
To do this, set an upper limit to the I/O rate for port 2A.
For detailed information about monitoring traffic, see ”Setting the priority of ports on arrays” on
page 22 and ”Measuring traffic between host bus adapters and ports for many-to-many connections”
on page 23.
Figure 3 Traffic at ports on network A

3. Set an upper limit to traffic at non-prioritized ports. To maintain I/O rates at prioritized ports, set
upper limit values to the I/O rate for non-prioritized ports.
When you first set an upper limit, HP recommends an upper limit of approximately 90 percent of peak
traffic. In network A, the peak I/O rate for the non-prioritized port (2A) is 200 IO/s, so the
recommended upper limit is 180 IO/s.
For detailed information, see ”Setting upper limit values for traffic at non-prioritized ports or WWNs”
on page 24.
4. Check the result of applying upper limit values. After applying upper limit values, measure traffic at
ports by viewing traffic statistics for prioritized ports 1A and 1C to check whether the host
performance has improved to a desirable level.
In network A, if the desirable I/O rate (400 IO/s for ports 1A and 1C) has not been achieved,
change the upper limit for port 2A to a lower value and apply the new upper limit to the array. In
network A, if the upper limit is set to 180 IO/s but the I/O rate for 1A and 1C is still below 400 IO/s,
reduce the upper limit until the I/O rate reaches 400 IO/s.
5. If necessary, apply a threshold. To use threshold control, set threshold values in the Port tab in the
Performance Control pane. You can set threshold values in either of the following ways:
• Set one threshold for each prioritized port.
In network A, if you set a threshold of 200 IO/s for port 1A and 100 IO/s for port 1C, the upper
limit on the non-prioritized port (2A) is disabled when either of the following conditions is met:
• I/O rate for port 1A is 200 IO/s or lower
• I/O rate for port 1C is 100 IO/s or lower
• Set only one threshold for the entire array.
In network A, if you set a threshold of 500 IO/s for the array, the upper limit on the non-prioritized
port (2A) is disabled when the sum of the I/O rates for all prioritized ports (1A and 1C) falls below
500 IO/s.
For detailed information, see ”Setting thresholds” on page 25.
Procedure for many-to-many connections between HBAs and ports

Figure 4 shows an example of a network where a production server and development server are
connected to the array. (Henceforth, this network is referred to as network B.) The host bus adapter

(wwn01) in the production server is connected to four array ports (1A, 1C, 1A, and 2C). The host bus
adapters (wwn02 and wwn03) in the development server are connected to the same four ports.
Figure 4 Network B (many-to-many connections between HBAs and ports)

In this example, setting up Performance Control XP requires the following major steps:
1. Find WWNs of host bus adapters. Before using Performance Control XP, find the Worldwide Name
(WWN) of each host bus adapter in the host servers. WWNs are 16-digit hexadecimal numbers
identifying host bus adapters. For detailed information about finding WWNs, see the
HP StorageWorks LUN Configuration and Security Manager XP user guide for the specific array.
2. Monitor all traffic between host bus adapters and ports. You must monitor all host bus adapters
connected to ports in the array. In the WWN tab of the Performance Control pane, place the host bus
adapters connected to each port below the Monitor icons.
In network B, the four ports are connected to three host bus adapters (wwn01, wwn02, and wwn03).
Place the host bus adapter for wwn01, wwn02, and wwn03 below the Monitor icons for the four ports
(shown in Figure 5).
Figure 5 Specifying host bus adapters to be monitored

For detailed instructions, see ”Measuring traffic between host bus adapters and ports for many-to-many
connections” on page 23.
NOTE: Performance Control XP cannot monitor and control the performance of hosts that have
host bus adapters placed below the Non-Monitor icon.
3. Set the priority of host bus adapters. In the WWN tab of the Performance Control pane, specify the
priority of each host bus adapter.
In network B, the production server is given high priority and the development server is given low
priority. If your network is configured as in Figure 5, you must give high priority to wwn01 and low
priority to wwn02 and wwn03.
To set the priority of host bus adapters, take the following steps (see Figure 6):
a. In the WWN tab, click one of the four ports to which the HBAs are connected (1A, 1C, 3A, or 3C).
b. Set wwn01 to Prio., and set wwn02 and wwn03 to Non-Prio.
Figure 6 Priority specified in the Performance Control pane
NOTE: Throughout this chapter, prioritized WWN refers to a high-priority host bus adapter (such
as wwn01) and non-prioritized port refers to a low-priority host bus adapter (such as wwn02 or
wwn03).
4. Monitor traffic between host bus adapter and ports. Obtain statistics about traffic between host bus
adapter and ports.
There are two types of traffic statistics: I/O rate (number of I/Os per second) and transfer rate (amount
of data transferred between a host and array). When viewing traffic statistics in the Performance
Control pane, select I/O or transfer rate.
If your network is configured like network B, measure the traffic between the three host bus adapters
(wwn01, wwn02, and wwn03) and the four ports (1A, 1C, 2A, and 2C).
Figure 7 illustrates the I/O rate at the paths between port 1A and the host bus adapters. Initially the
I/O rate on the path between 1A and the prioritized WWN (wwn01) was approximately 400 IO/s,
while the I/O rate on the path between 1A and the non-prioritized WWNs (wwn02 and wwn03) was
approximately 100 IO/s. However, the I/O rate for non-prioritized WWNs gradually increased,
while the I/O rate of the prioritized WWN gradually decreased, causing performance of the
high-priority production server to suffer. As network administrator, you might want to maintain the I/O
rate for the prioritized WWN (wwn01) at 400 IO/s.
For detailed information, see ”Measuring traffic between host bus adapters and ports for many-to-many
connections” on page 23 and ”Analyzing traffic statistics” on page 24.
Figure 7 Traffic at ports on network B

5. Set an upper limit to traffic between ports and the non-prioritized WWN. To maintain sufficient I/O
rates at prioritized WWNs, set upper limit values for the I/O rate for non-prioritized WWNs. When
you first set an upper limit, HP recommends that the upper limit be approximately 90 percent of peak
traffic.
In network B, the peak I/O rate is 200 IO/s on the paths between the non-prioritized WWNs
(wwn02 and wwn03) and all four ports on the array (1A, 1C, 2A, and 2C). Therefore, the
recommended upper limit for non-prioritized WWNs is 720 IO/s (200 x 4 x 0.90).
If your network is configured like network B, perform the following steps (see Figure 8):
a. In the WWN tab, click one of the four ports to which the HBAs are connected (1A, 1C, 2A, or 2C).
b. Set an upper limit for the non-prioritized WWNs (wwn02 and wwn03).
Figure 8 Setting upper limits

Figure 9 shows the result of setting an upper limit of 720 IO/s to the paths between 1A and the
non-prioritized WWNs. For details, see ”Setting upper limit values for HBAs in a PFC group” on
page 27.
6. Check the result of applying upper limit values. Measure traffic at ports and view traffic statistics for
the prioritized WWN to check whether host performance improved to a desirable level.
In network B, the desirable I/O rate for the prioritized WWN is 400 IO/s. If production server
performance has not achieved the desired level, lower the value of the upper limit and apply the new
upper limit to the array. In network B, if the upper limit is set to 720 IO/s but the I/O rate for wwn01
remains below 400 IO/s, lower the upper limit until the I/O rate reaches 400 IO/s.
7. If necessary, apply a threshold. Set a threshold in the WWN tab of the Performance Control pane.
In the WWN tab, specify only one threshold for the entire array, regardless of the number of
prioritized WWNs. For example, if there are three prioritized WWNs in the network and the
threshold is 100 IO/s, the upper limit on non-prioritized WWNs is disabled when the sum of the I/O
rates for all prioritized WWNs goes below 100 IO/s.
For details, see ”Setting thresholds” on page 25.
Notes on using Performance Control XP

• Selection of CU group. When selecting one of the following CU groups, the SPM button is deactivated
(grayed out) and cannot be selected:
• CU group 1 (CU 40-7F)
• CU group 2 (CU 80-BF)
• CU group 3 (CU C0-FE)
• User types. Users belonging to the StorageAdmins group cannot use Performance Control XP. For
more information about limitations, see the HP StorageWorks Command View XP user guide for XP
Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for the specific array.
• I/O rates and transfer rates. Performance Control XP is based on I/O and transfer rates measured by
Auto LUN/Performance Control Base Monitor. Auto LUN/Performance Control Base Monitor
measures I/O and transfer rates every second, and calculates the average I/O and average transfer
rates for every gathering interval (specified between 1 and 15 minutes) regularly.
Suppose that 1 minute is specified as the gathering interval and the I/O rate at port 1-A changes as
illustrated in Figure 9 Graph 1. When displaying the I/O rate graph for 1A in Auto LUN/Performance
Control Base Monitor, the line in the graph indicates changes in the average I/O rate calculated
every minute (see Graph 2). If you click the Detail check box in the Auto LUN pane, the graph displays
changes in maximum, average, and minimum I/O rates in one minute.
Performance Control XP applies upper limits and thresholds to the average I/O or transfer rate
calculated every gathering interval. For example, in Figure 9 (which has a gathering interval of 1
minute), if you set an upper limit of 150 IO/s to port 1A, the highest data point in the line CL1-A in
Graph 2 and the line Ave.(1 min) in Graph 3 is around 150 IO/s. The lines Max (1 min.) and Min (1
min.) in Graph 3 might exceed the upper limit.
Graph 1: Actual I/O rate (measured every second)
Graph 2: I/O rate displayed in Performance Control XP (with Detail option)
Graph 3: I/O rate displayed in Performance Control XP (without Detail option)

Figure 9 Graphs indicating changes in port traffic
• Continuous Access. Performance Control XP monitors write I/O requests issued from initiator ports of
the array.
NOTE: When using continuous access functions, Performance Control XP monitors write I/O
requests issued from initiator ports to the array.
If you specify an RCU target port as a prioritized port, I/O requests from the initiator port will be a
target of threshold control. If you specify an RCU target port as a non-prioritized port, I/O requests
from the initiator port will not be a target of upper limit control.
Performance Control XP restrictions

The following restrictions apply to the Performance Control XP panes:

• You cannot drag and drop objects. You must use the buttons.
• After clicking Performance Control to access Performance Control XP or clicking Plan to access
AutoLUN Plan, a new browser opens. While working in the new browser, the main Command View
XP or XP Remote Web Console window is inactive. You must exit secondary windows to return to the
main Command View XP or XP Remote Web Console window.
• The Close button ( ) on the Auto LUN and Performance Control panes remains active even if you
click Apply, and processing is being executed. If you click Close after clicking Apply, the pane closes,
but processing continues.
• For the first two operations only, the word “Processing” appears on the message dialog box of the
Auto LUN and Performance Control panes. This message does not appear for the third and later
operations.
2 Using Performance Control XP
Starting Performance Control XP
1. In the Auto LUN pane, click WWN or Port-LUN.
2. Click the PFC button. The Performance Control pane appears.
Performance Control pane

The Performance Control pane contains two tabs: Port and WWN.
• Use the Port tab to set the limit on performance of non-prioritized ports and set the threshold on
performance of prioritized ports.
Figure 10 Port tab in the Performance Control pane

• Use the WWN tab to set the limit on performance of non-prioritized WWNs and set the threshold on
performance of prioritized WWNs.
Figure 11 WWN tab in the Performance Control pane
Pane contents
The Port and WWN tabs contain several sections:
Top section
• Current Control Status at the top of the pane displays one of the following values:
• Port Control: System performance is controlled by the upper limits and threshold specified in the
Port tab
• WWN Control: System performance is controlled by the upper limits and threshold specified in the
WWN tab
• No Control: System performance is not controlled by Performance Control XP
If WWN Control appears when the Port tab is active, click Apply to switch control so that Port Control
appears. Conversely, if Port Control appears when the WWN tab is active, click Apply to switch
control so that WWN Control appears.
• Use Control List near the upper right corner of the tab to limit the number of ports or WWNs shown in
the table:
• All: Shows all the ports or WWNs
• Prio.: Shows only prioritized ports or WWNs
• Non-Prio.: Shows only non-prioritized ports or WWNs
If you change a port’s settings, the port remains in the table regardless of the selection in the list.
Tree section (WWN tab only)
• The tree in the upper-left of the WWN tab lists ports and host bus adaptors connected to the array’s
ports.
• Icons representing ports on the array appear below the Subsystem folder.

• If you double-click a port, the tree collapses to display two items: Monitor and Non-Monitor. The
table on the right displays a list of host bus adapters that are connected to the specified port and
can be monitored by Performance Control XP.
• If you double-click Monitor, the tree view and table display a list of host bus adapters that are
connected to the specified port and can be monitored by Performance Control XP.
• If you double-click Non-Monitor, the tree view and table display a list of host bus adapters that are
connected to the specified port and cannot be monitored by Performance Control XP.
• If many-to-many connections are established between host bus adapters (HBAs) and array ports,
ensure that all connected HBAs are displayed under Monitor.
NOTE: The list to the right of the tree changes depending on the item selected.
NOTE: If a host bus adapter’s WWN is displayed in red in the tree view, the host bus adapter is
connected to two or more ports, but upper limits and/or thresholds do not control traffic between
the HBA and some ports. If many-to-many connections are established between host bus adapters
(HBAs) and array ports, ensure that all connected HBAs are monitored. For information about
controlling the traffic between the HBA and connected ports, see ”Troubleshooting Auto
LUN/Performance Control Base Monitor and Performance Control XP” on page 29.
• The tree in the lower-left of the WWN tab lists PFC groups and host bus adapters (WWNs) in each
PFC group.
• PFC groups, which contain one or more WWNs, appear below the Subsystem folder. For details
about PFC groups, see ”Grouping host bus adapters” on page 26.
• If you double-click a PFC group ( ), host bus adapters in the PFC group appear. WWNs and
nicknames appear to the right of the host bus adapter icon ( ). WWNs uniquely identify host
bus adapters. The system administrator can assign nicknames, so users can easily identify each
host bus adapter.
• The Add WWN button between the trees adds a host bus adapter to a PFC group. Before using this
button, select a host bus adapter ( ) from the upper-left tree view and a PFC group ( ) from the
lower-left tree view.
Table section
• Use the list at the top left of the tables to change the type of performance statistics displayed in the
table:
• IOPS (I/Os per second) displays I/O rates for ports or WWNs (host bus adapters). The I/O rate
indicates number of I/Os per second.
• MB/s (megabytes per second) displays transfer rates for ports. The transfer rate indicates amount
of data transferred via a port in one second.
• 100KB/s (100 kilobytes per second) displays transfer rates for WWNs (host bus adapters). The
transfer rate indicates amount of data transferred via a port in one second.
• The table displays a list of ports or WWNs and indicates the I/O or transfer rate for each. The
measurement unit for the values in the table are specified by the list at the upper-left corner of the tab.
The table can display the following columns:
• Port: In the Port tab, indicates ports on the array.
• Port: In the WWN tab, indicates the port to which the HBA is connected.
• Group: In the WWN tab, indicates the PFC group to which the host bus adapter belongs. This
column appears when a port is selected in the upper-left tree view, and does not appear when a
PFC group is selected in the lower-left tree view.
• Ave.: Average I/O or transfer rate for the specified period.
• Max.: Maximum I/O or transfer rate for the specified period.
• Attribute: Priority of each port or WWN. Prio. indicates a prioritized port or WWN. Non-Prio.
indicates a non-prioritized port or WWN.

• Threshold: In the Port tab, specifies the threshold for I/O and transfer rates for each prioritized
port. Use the IOPS column to specify the threshold for I/O rates. Use the MB/s column to specify
the threshold for transfer rates. To specify a threshold, double-click a cell to display the cursor in
the cell.
• Upper: Specifies the upper limit on I/O and transfer rates for each non-prioritized port or WWN.
Use the IOPS column to specify the upper limit for I/O rates. Use the MB/s column (or 100KB/s
column for WWN) to specify the upper limit for transfer rates. To specify an upper limit,
double-click a cell to display the cursor in the cell.
NOTE: The Upper columns are not displayed in the WWN tab if a PFC group is selected in the
lower-left tree view.
Bottom section
• If you click the All Thresholds check box and enter a threshold value in the text box, the threshold value
is applied to the entire array. To specify the threshold for I/O rates, select IOPS from the list on the
right of the text box. To specify the threshold for transfer rates, select MB/s (or 100KB/s in the WWN
tab) from the list. For example, if you specify 128 IOPS in All Thresholds, the upper limits on
non-prioritized ports are disabled when the sum of I/O rates for all the prioritized ports is below 128
IOPS.
• The Delete ports if CHA is removed check box deletes settings on ports in channel adapters that have
been removed.
Buttons
• Apply: Applies settings in this pane to the array.
• Reset: Restores original settings in the pane.
• Initialize: Changes settings in this pane as explained below, and applies the resulting settings to the
array:
• All ports or WWNs become prioritized ports or WWNs.
• The threshold value for all ports in the Port tab becomes 0 (zero).
NOTE: The pane displays a hyphen (-) instead of 0 (zero).
• If you check the All Thresholds check box, the check mark disappears.
• Close: Closes the Performance Control pane.
Managing traffic between HBAs and ports

If one-to-one connections are established between host bus adapters (HBAs) and array ports, use the Port
tab in the Performance Control pane to measure and analyze traffic.
If many-to-many connections are established between host bus adapters (HBAs) and array ports, use the
WWN tab in the Performance Control pane to measure and analyze traffic.
Setting the priority of ports on arrays

If a one-to-one connection is established between HBAs and ports, you must measure traffic between
high-priority HBAs and prioritized ports and between low-priority HBAs and non-prioritized ports.
1. Start Performance Control XP (”Starting Performance Control XP” on page 19). The Performance
Control pane appears.
2. Click Port.
3. Select All from the list at the top right corner of the pane.
4. Right-click a high-priority port, and select Non-Prio. ->> Prioritized. If there is more than one
high-priority port, repeat this operation.
Prio. appears in the Attribute column.

5. Right-click a low-priority port, and select Prio. ->> Non-Prio. If there is more than one low-priority port,
repeat this operation.
Non-Prio. appears in the Attribute column.
6. Click Apply. Settings on the pane are applied to the array.
7. For instructions on measuring traffic (I/O and transfer rates), see the HP StorageWorks Auto LUN XP
user guide for the specific array.
Measuring traffic between host bus adapters and ports for many-to-many
connections
If a many-to-many connection is established between host bus adapters (HBAs) and ports, you must
measure traffic between each HBA and the port to which the HBA is connected.
2. Click WWN.
4. In the upper-left tree view, double-click a port.
5. Double-click Non-Monitor below the specified port. Host adapters that are not being monitored are
displayed under Non-Monitor.
6. Right-click Monitor, and select Add WWN. The Add WWN dialog box where you can add a
prioritized or non-prioritized WWN to the Monitor branch appears.
Figure 12 Add WWN dialog box

7. Specify the WWN and PFC name (16-character maximum), and click OK. The specified WWN
appears below Monitor.
NOTE: To simplify managing HBAs, use the same name for the PFC name and HBA nickname.
NOTE: Performance Control XP does not monitor HBAs below Non-Monitor. You cannot set upper
limits and thresholds to HBAs that are not monitored. To move an HBA (WWN) from Monitor to
Non-Monitor, select an HBA from below Monitor, right-click Monitor, and select Delete WWN. You
can monitor up to 32 HBAs (WWNs) for each port.
8. Click Monitor. The table on the right lists HBAs that are displayed below Monitor.
9. Right-click a prioritized WWN, and select Non-Prio. ->> Prioritized. If there is more than one
high-priority port, repeat this operation.
Prio. appears in the Attribute column.
10.Right-click a non-prioritized WWN, and select Prio. ->> Non-Prio. If there is more than one
non-prioritized WWN, repeat this operation.
Non-Prio. appears in the Attribute column.
11.Repeat step 4 through step 10 for all ports except the one selected in step 4.
12.Click Apply in the Performance Control pane. Settings on the pane are applied to the array.

13.For instructions on measuring traffic (for example, I/O and transfer rates), see the HP StorageWorks
Auto LUN XP user guide for the specific array.
Analyzing traffic statistics

With one-to-one connections, traffic statistics consist of the number of I/Os made via ports and the amount
of data transferred via ports. Analyze traffic statistics to determine upper limit values that should be
applied to I/O or transfer rates for non-prioritized ports.
With many-to-many connections, traffic statistics consist of the number of I/Os made via ports from HBAs
and the amount of data transferred between ports and HBAs. Analyze traffic statistics to determine upper
limit values that should be applied to I/O or transfer rates for low-priority HBAs.
The following is the procedure for using the Performance Control pane to analyze traffic statistics. Note
that you can also use the Auto LUN pane to analyze traffic statistics. Auto LUN/Performance Control Base
Monitor displays a line graph indicating traffic changes. (For more information, see the HP StorageWorks
Auto LUN XP user guide for the specific array.)
2. Click Port (for a one-to-one connection) or WWN (for a many-to-many connection).
4. Do either of the following:
• To analyze I/O rates, select IOPS from the list at the upper-left corner of the table.
• To analyze transfer rates, select MB/s in the Port tab or 100KB/s in the WWN tab from the list at
the upper-left corner of the table.
The table displays traffic statistics (for example, I/O or transfer rates).
5. Analyze the information in the table, and determine upper limit values that should be applied to
non-prioritized ports or WWNs. If necessary, determine threshold values that should be applied to
prioritized ports or WWNs. For details, see ”Procedure for one-to-one connections between HBAs and
ports” on page 12 (for ports) or Procedure for many-to-many connections between HBAs and ports,
page 13 (for WWNs).
Setting upper limit values for traffic at non-prioritized ports or WWNs

After analyzing traffic statistics about prioritized and non-prioritized ports and WWNs, you must set
upper limit values to I/O or transfer rates. Upper limit values for I/O rates suppress the number of I/Os
from low-priority host servers, which provides better performance for high-priority host servers. Upper limit
values for transfer rates suppress the amount of data that should be transferred between the array and
low-priority ports, which provides better performance for high-priority host servers.
2. Click Port (for a one-to-one connection) or WWN (for a many-to-many connection).
• To limit the I/O rate, select IOPS from the list at the upper-left corner of the table.
• To limit the transfer rate, select MB/s (or 100KB/s for WWNs) from the list at the upper-left corner
of the table.
4. Locate the non-prioritized port or WWN.
The Attribute column indicates whether ports or WWNs are prioritized or non-prioritized. If you
cannot find non-prioritized ports or WWNs, check the list at the top right corner of the pane. If it
displays Prioritize, select All or Non-Prioritize from the list.
• To limit the I/O rate, double-click the desired cell in the IOPS column in Upper, and enter the upper
limit in the cell.
• To limit the transfer rate, double-click the desired cell in the MB/s column (or 100KB/s column for
WWNs) in Upper, and enter the upper limit in the cell.
The upper limit value you entered is shown in blue.

6. Click Apply. The settings in the pane are applied to the array. The upper limit value you entered turns
black.
Setting thresholds
If threshold control is used, upper limit control is automatically disabled when traffic between production
servers and the array is reduced to a specified level. For details, see ”Automatically disabling upper limit
control” on page 11, and ”Procedure for one-to-one connections between HBAs and ports” on page 12
or ”Procedure for many-to-many connections between HBAs and ports” on page 13.
2. Click Port (for one-to-one connection) or WWN (for many-to-many connection).
• To disable the upper limit on I/O rates, select IOPS from the list at the upper-left corner of the table.
• To disable the upper limit on transfer rates, select MB/s (or 100KB/s for WWNs) from the list at the
upper-left corner of the table.
4. To set a threshold for a WWN, skip to step 7.
• To set a threshold for a prioritized port, locate the desired prioritized port, which is indicated by
Prio. in the Attribute column. Double-click the cell in the IOPS or MB/s column in Threshold, and
enter the threshold value.
CAUTION: If you enter 0 (zero) in a cell, the cell displays a hyphen (-) and the threshold for the
prioritized port becomes ineffective. If the threshold for any prioritized port is ineffective, threshold
control will not be performed, but upper limit control will be performed.
• To set a threshold to the entire array, click the All Thresholds check box, enter the threshold value
in the text box, and select IOPS or MB/s from the list in All Thresholds.
6. Skip to step 10.
7. Select the All Thresholds check box.
• To disable the upper limit on I/O rates, select IOPS from the list below the check box.
• To disable the upper limit on transfer rates, select 100KB/s from the list below the check box.
9. Enter the threshold in the text box.
10.Click Apply. Settings in the pane are applied to the array.
Changing PFC names of host bus adapters (many-to-many connections only)

Use the Performance Control pane to assign a PFC name to a host bus adapter (HBA). Although you can
identify HBAs by WWNs (Worldwide Names), you can identify HBAs more easily if you assign PFC
names. WWNs are 16-digit hexadecimal numbers and cannot be changed. However, PFC names should
not necessarily be 16-digit hexadecimal numbers and can be changed.
The following is the procedure for changing an existing PFC name. For details about assigning PFC
names, see ”Measuring traffic between host bus adapters and ports for many-to-many connections” on
page 23.
2. Click WWN.
3. In the upper-left tree view, click a host bus adapter ( ) from below the Monitor branch, and
right-click the selection.

4. Select Change WWN & PFC Name. The Change WWN and PFC Name dialog box appears.
Figure 13 Change WWN and PFC Name dialog box

5. Enter a new PFC name (up to eight characters) in the PFC Name box, and click OK.
6. In the Performance Control pane, click Apply. Settings in the pane are applied to the array.
Replacing host bus adapters (many-to-many connections only)

If a host bus adapter fails, replace the adapter with a new one. After you finish the replacement, delete
the old host bus adapter from the Performance Control pane, and register the new host bus adapter.
Use the following procedure to quickly and easily remove the old adapter and register a new one.
2. Click WWN.
3. In the upper-left tree view, click the old host bus adapter ( ) below the Monitor branch, and
right-click the selection.
4. Select Change WWN & PFC Name. The Change WWN and PFC Name dialog box appears
(Figure 13).
5. Enter the WWN of the new host bus adapter in the WWN box.
6. If necessary, enter a new PFC name (up to eight characters) in the PFC Name box.
7. Click OK.
Grouping host bus adapters

Use Performance Control XP to create a PFC group that contain multiple host bus adapters. All host bus
adapters (HBAs) in one PFC group must be of the same priority. Prioritized WWNs (for example,
high-priority HBAs) and non-prioritized WWNs (for example, low-priority HBAs) cannot be mixed in one
PFC group.
You can use a PFC group to switch the priority of multiple HBAs from prioritized to non-prioritized, or vice
versa. You can also use a PFC group to set the same upper limit value to all HBAs in the group.
Adding multiple HBAs to a PFC group

2. Click WWN.
3. In the lower-left tree view, right-click the Subsystem folder.
4. Select Add New PFC Group. The Add New PFC Group dialog box appears.
Figure 14 Add New PFC Group dialog box

5. Enter the name of the PFC group, and click OK. A PFC group is created and a PFC group icon ( )
is added to the lower-left tree view.
6. Select an HBA ( ) from the upper-left tree view, and select a PFC group from the lower-left tree
view. Click Add WWN.
Repeat this operation until all desired HBAs are added to the PFC group.
NOTE: Select a host bus adapter from below the Monitor branch. You cannot add HBAs from
below the Non-Monitor branch to PFC groups.
7. Click Apply. Settings are applied to the array.
Switching the priority of PFC groups

All host bus adapters (HBAs) in one PFC group must have the same priority. Prioritized WWNs (for
example, high-priority HBAs) and non-prioritized WWNs (for example, low-priority HBAs) cannot be
mixed in a given PFC group.
Use a PFC group to switch the priority of several HBAs from prioritized to non-prioritized, or vice versa.
2. Click WWN.
3. In the lower-left tree view, right-click a PFC group ( ).
• To switch the priority from prioritized to non-prioritized, select Prio. ->> Non-Prio.
• To switch the priority from non-prioritized to prioritized, select Non-Prio. ->> Prioritized.
5. Click Apply. Settings in the pane are applied to the array.
Setting upper limit values for HBAs in a PFC group

If all host bus adapters in a PFC group are non-prioritized WWNs (for example, low-priority HBAs), set
an upper limit value to HBA performance (I/O or transfer rate). You can assign one upper limit value for
each PFC group.
For example, suppose the upper limit value 100 IOPS is assigned to a PFC group consisting of four host
bus adapters. If the sum of the I/O rate of the four HBAs reaches 100 IOPS, Performance Control XP
controls the system so that the sum of the I/O rates does not exceed 100 IOPS.
2. Click WWN.
3. In the lower-left tree view, click the Subsystem folder or PFC group ( ).
4. If you selected the Subsystem folder, take the following steps:
a. Select IOPS or 100KB/s (MB/s on XP12000) from the list at the upper-left corner of the table. IOPS
assigns an upper limit to the I/O rate. 100KB/s assigns an upper limit to the transfer rate.
b. To assign an upper limit to the I/O rate, enter the upper limit value in the IOPS column. To assign
an upper limit to the transfer rate, enter the upper limit value in the 100KB/s column.
NOTE: If you cannot see the IOPS or 100KB/s column, scroll to the left. The column is located at
the right side of the table.
If you selected a PFC group, take the following steps:

a. Right-click the selected PFC group, and select Change Upper Limit. The Change Upper Limit dialog
box appears.
Figure 15 Change Upper Limit dialog box

b. To assign an upper limit to the I/O rate, enter the upper limit value, select IOPS from the list, and
click OK.
To assign an upper limit to the transfer rate, enter the upper limit value, select 100KB/s from the
list, and click OK.
5. In the Performance Control pane, click Apply. Settings are applied to the array.
Renaming PFC groups

2. Click WWN.
4. Select Change Name. The Change PFC Group Name dialog box appears.
Figure 16 Change PFC Group Name dialog box

5. Enter the new name, and click OK.
6. In the Performance Control pane, click Apply. Settings are applied to the array.
Deleting PFC groups

2. Click WWN.
4. Select Delete.

3 Troubleshooting Auto LUN/Performance Control
Base Monitor and Performance Control XP
If the WWN of a host bus adapter is displayed in red in the WWN tree view, the host bus adapter is
connected to two or more ports, but Performance Control XP does not control traffic between the HBA and
some ports. To control traffic between the HBA and all connected ports, take the following steps:
1. Start Performance Control XP, and ensure that the WWN tab is displayed.
2. In the upper-left tree view, double-click all ports to which the HBA is connected.
3. Double-click all Monitor and Non-Monitor entries that appear below the specified ports.
4. If you find HBAs below the Non-Monitor entries, drag them to Monitor.
5. Ensure that the HBA appears below each of the Monitor entries, and click Apply.
While displaying Auto LUN/Performance Control Base Monitor in short range, if I/O workloads between
hosts and the array become heavy, the array gives higher priority to I/O processing than monitoring
processing; therefore, some monitoring data might be missing. If monitoring data is missing frequently,
use the Gathering Interval option in the Monitoring Options pane to increase the collection interval.
The display on the LDEV, Port-LUN, and WWN tabs is fixed to in short range.

30 Troubleshooting Auto LUN/Performance Control Base Monitor and Performance Control XP
A Performance Control Export Tool
This appendix provides additional instructions for using the Performance Control Export Tool.
This appendix makes the following assumptions:
• You have a background in data processing and understand arrays and their basic functions.
• You are familiar with Command View XP or XP Remote Web Console.
• You have read and understand the HP StorageWorks Command View XP user guide for XP Disk
Arrays or the HP StorageWorks XP Remote Web Console user guide for the specific array.
• You are familiar with the operating system (for example, Windows® and Solaris®) and web browser
software (for example, Internet Explorer and Netscape) on the system hosting the Command View XP
or XP Remote Web Console software.
Overview of Auto LUN XP

You can use Auto LUN XP to monitor and tune array performance. Its major components are:
• Auto LUN XP
• HP Performance Control XP (henceforth, referred to as PFC)
You can use Auto LUN XP to obtain usage statistics about physical hard disk drives, logical volumes,
processors, or other resources in your array. You can also obtain statistics about workloads on disk drives
and traffic between hosts and the array. The Auto LUN XP pane displays a line graph indicating changes
in the usage rates, workloads, or traffic. You can view information in the pane, analyze trends in disk
I/Os, and detect peak I/O time. If the system performance is low, you can use information in the pane to
detect bottlenecks in the system.
You can use Auto LUN XP to balance the workload among hard disk drives, logical volumes, and
processors to remove bottlenecks from your system. If Auto LUN XP indicates that a large number of I/O
operations are made to some hard disk drives, you can use Auto LUN XP to distribute workloads to other
disk drives.
For more information about Auto LUN XP, see the HP StorageWorks LUN Configuration and Security
Manager XP user guide for the specific arrays. For more information about Performance Control XP, see
”Performance Control XP” on page 11.
Exporting monitoring data to files

Use the Export Tool to export monitoring data (statistics) displayed in the Auto LUN XP pane to text files.
You can also use the Export Tool to export monitoring data on remote copy operations performed by
Continuous Access XP, TrueCopy for z/OS®, Continuous Access XP Journal, and Universal Replicator for
z/OS. Once you export the monitoring data to text files, you can import it into word processor
documents. You can also import the monitoring data into spreadsheet or database software for analysis.

Here is an example of a text file imported into spreadsheet software:
Figure 17 Sample text file
NOTE:
• When running the Export Tool, text files are usually compressed in a ZIP-format archive file. To open a
text file, you must decompress the ZIP file to extract the text files.
• Text files are in CSV (comma-separated value) format, in which values are delimited by commas. You
can use many spreadsheet applications to open CSV files.
• Do not run multiple instances of the Export Tool simultaneously. If you run multiple instances, the SVP
might be overloaded and a timeout error might occur.
Files to be exported
You can use the Export Tool to save monitoring data in the Auto LUN XP pane into files (see Table 3
through Table 10). You can also use the Export Tool to save monitoring data about remote copy
operations into files (see Table 11 through Table 18). The Export Tool usually compresses monitoring data
in ZIP files. To use a text editor or spreadsheet software to view or edit the monitoring data, you usually
need to decompress the ZIP files to extract CSV files. However, if you want the Export Tool to save
monitoring data in CSV files instead of ZIP files, you can force the Export Tool to do so.
Table 2 shows the correspondence between the Auto LUN XP panes and the monitoring data that the
Export Tool can save. For details on the ZIP files and CSV files that are saved, see the tables indicated in
the See column.
Table 2 Auto LUN XP panes and monitoring data that can be saved by the Export Tool
Pane Monitoring data See

Physical tab in the Auto Statistics about resource usage and write pending rates Table 3
LUN XP pane
32 Performance Control Export Tool

Table 2 Auto LUN XP panes and monitoring data that can be saved by the Export Tool (continued)
Pane Monitoring data See

LDEV tab in the Auto LUN Statistics about parity groups, external LU groups, or V-VOL groups Table 4
XP pane
Statistics about logical volumes in parity groups, in external LU Table 5
groups, or in V-VOL groups
Port-LUN tab in the Auto Statistics about ports Table 6

LUN XP pane
Statistics about host bus adapters connected to ports Table 7
Statistics about LU paths Table 8
WWN tab in the Auto Statistics about SPM groups Table 9

LUN XP pane
Statistics about host bus adapters belonging to SPM groups Table 10
CA Monitor pane and Statistics about remote copy operations by Continuous Access XP Table 11
TCz Monitor pane and TrueCopy for z/OS (in the whole array)
Statistics about remote copy operations by Continuous Access XP Table 12

and TrueCopy for z/OS (at LU paths)
and TrueCopy for z/OS (at logical volumes controlled by a
particular CU)

and TrueCopy for z/OS (at CLPR)
CAXJ Monitor pane Statistics about remote copy operations by Continuous Access XP Table 15
and URz Monitor pane Journal and Universal Replicator for z/OS (at CLPR)
Journal and Universal Replicator for z/OS (at journal groups)

Journal and Universal Replicator for z/OS (at LU paths)
Journal and Universal Replicator for z/OS (at logical volumes
controlled by a particular CU)
Table 3 Files containing statistics about resource usage and write pending rates
ZIP file CSV file Data saved in the file

PhyPG_dat.ZIP PHY_Long_PG.csv Usage rates for parity groups in long
range
PHY_Short_PG.csv Usage rates for parity groups in short

range
PhyLDEV_dat.ZIP PHY_Long_LDEV_x-y.csv Usage rates for logical volume in a parity

group in long range
PHY_Short_LDEV_x-y.csv Usage rates for logical volumes in a

parity group in short range
PhyExG_dat.ZIP PHY_ExG_Response.csv Response time for external LU groups

(unit is microseconds1)
PHY_ExG_Trans.csv Amount of transferred data for external
LU groups (unit is KB/sec)

Table 3 Files containing statistics about resource usage and write pending rates (continued)

PhyExLDEV_dat.ZIP PHY_ExLDEV_Response_x-y.csv Response time for logical volumes in an
external LU group (unit is microseconds1)
PHY_ExLDEV_Trans_x-y.csv Amount of data transferred for logical

volumes in an LU volume group (unit is
KB/sec)
PhyProc_dat.ZIP PHY_Long_CHP.csv Usage rates for channel processors in

long range
PHY_Short_CHP.csv Usage rates for channel processors in
short range
PHY_Long_DKP.csv Usage rates for disk processors in long

range
PHY_Short_DKP.csv Usage rates for disk processors in short

range
PHY_Long_DRR.csv Usage rates for DRRs (data recovery and

reconstruction processors) in long range
PHY_Short_DRR.csv Usage rates for DRRs (data recovery and

reconstruction processors) in short range
PhyCSW_dat.ZIP PHY_Long_MPA_CSW.csv • Usage rates for access paths between

channel adapters and cache
memories in long range
• Usage rates for access paths between
disk adapters and cache memories in
long range
PHY_Short_MPA_CSW.csv • Usage rates for access paths between

channel adapters and cache
memories in short range
disk adapters and cache memories in
short range
PHY_Long_MPA_SMA.csv • Usage rates for access paths between

channel adapters and the shared
memory in long range
disk adapters and the shared
memory in long range
PHY_Short_MPA_SMA.csv • Usage rates for access paths between

channel adapters and the shared
memory in short range
disk adapters and the shared
memory in short range
PHY_Long_CSW_CMA.csv Usage rates for access paths between

cache switches and cache memories in
long range
PHY_Short_CSW_CMA.csv Usage rates for access paths between

cache switches and cache memories in
short range
PHY_Long_Write_Pending_Rate.csv Write pending rates in long range
PHY_Short_Write_Pending_Rate.csv Write pending rates in short range

1. 1 microsecond is one-millionth of 1 second.

NOTE:
• The letters x-y in the CSV filename indicate a parity group or external LU group.
• Statistics in long range and short range are stored for resource usage and write pending rates.
Table 4 Files containing statistics about parity, external volume, and V-VOL groups

PG_dat.ZIP PG_IOPS.csv Number of read and write operations per second
PG_TransRate.csv Size of data transferred per second (unit is KB/sec)
PG_Read_IOPS.csv Number of read operations per second
PG_Seq_Read_IOPS.csv Number of sequential read operations per second
PG_Rnd_Read_IOPS.csv Number of random read operations per second
PG_CFW_Read_IOPS.csv Number of read operations in “cache-fast-write” mode per

second
PG_Write_IOPS.csv Number of write operations per second
PG_Seq_Write_IOPS.csv Number of sequential write operations per second
PG_Rnd_Write_IOPS.csv Number of random write operations per second
PG_CFW_Write_IOPS.csv Number of write operations in “cache-fast-write” mode per

second
PG_Read_Hit.csv Read hit ratio
PG_Seq_Read_Hit.csv Read hit ratio in sequential access mode
PG_Rnd_Read_Hit.csv Read hit ratio in random access mode
PG_CFW_Read_Hit.csv Read hit ratio in “cache-fast-write” mode
PG_Write_Hit.csv Write hit ratio
PG_Seq_Write_Hit.csv Write hit ratio in sequential access mode
PG_Rnd_Write_Hit.csv Write hit ratio in random access mode
PG_CFW_Write_Hit.csv Write hit ratio in “cache-fast-write” mode
PG_BackTrans.csv Number of data transfer operations between cache memories

and disk drives (for example, parity, external LU, or V-VOL
groups) per second
PG_C2D_Trans.csv Number of data transfer operations from cache memories and

disk drives (for example, parity, external LU, or V-VOL groups)
PG_D2CS_Trans.csv Number of data transfer operations from disk drives (for

example, parity, external LU, or V-VOL groups) to cache
memories in sequential access mode
PG_D2CR_Trans.csv Number of data transfer operations from disk drives (for

example, parity, external LU, or V-VOL groups) to cache
memories in random access mode
PG_Response.CSV Response time of parity, external LU, or V-VOL groups (unit is

microseconds1)
1. 1 microsecond is one-millionth of 1 second

Table 5 Files containing statistics about logical volumes in parity, external volume, or V-VOL groups

LDEV_IOPS.ZIP LDEV_IOPS_x-y.csv Number of read and write operations
per second
LDEV_TransRate.ZIP LDEV_TransRate_x-y.csv Size of data transferred per second

(unit is KB/sec)
LDEV_Read_IOPS.ZIP LDEV_Read_IOPS_x-y.csv Number of read operations per

second
LDEV_Seq_Read_IOPS.ZIP LDEV_Seq_Read_IOPS_x-y.csv Number of sequential read operations
per second
LDEV_Rnd_Read_IOPS.ZIP LDEV_Rnd_Read_IOPS_x-y.csv Number of random read operations

per second
LDEV_CFW_Read_IOPS.ZIP LDEV_CFW_Read_IOPS_x-y.csv Number of read operations in

“cache-fast-write” mode per second
LDEV_Write_IOPS.ZIP LDEV_Write_IOPS_x-y.csv Number of write operations per

second
LDEV_Seq_Write_IOPS.ZIP LDEV_Seq_Write_IOPS_x-y.csv Number of sequential write

operations per second
LDEV_Rnd_Write_IOPS.ZIP LDEV_Rnd_Write_IOPS_x-y.csv Number of random write operations

per second
LDEV_CFW_Write_IOPS.ZIP LDEV_CFW_Write_IOPS_x-y.csv Number of write operations in
“cache-fast-write” mode per second
LDEV_Read_Hit.ZIP LDEV_Read_Hit_x-y.csv Read hit ratio
LDEV_Seq_Read_Hit.ZIP LDEV_Seq_Read_Hit_x-y.csv Read hit ratio in sequential access

mode
LDEV_Rnd_Read_Hit.ZIP LDEV_Rnd_Read_Hit_x-y.csv Read hit ratio in random access mode
LDEV_CFW_Read_Hit.ZIP LDEV_CFW_Read_Hit_x-y.csv Read hit ratio in “cache-fast-write”

mode
LDEV_Write_Hit.ZIP LDEV_Write_Hit_x-y.csv Write hit ratio
LDEV_Seq_Write_Hit.ZIP LDEV_Seq_Write_Hit_x-y.csv Write hit ratio in sequential access

mode
LDEV_Rnd_Write_Hit.ZIP LDEV_Rnd_Write_Hit_x-y.csv Write hit ratio in random access

mode
LDEV_CFW_Write_Hit.ZIP LDEV_CFW_Write_Hit_x-y.csv Write hit ratio in “cache-fast-write”

mode
LDEV_BackTrans.ZIP LDEV_BackTrans_x-y.csv Number of data transfer operations

between cache memories and disk
drives (for example, logical LUs) per
second
LDEV_C2D_Trans.ZIP LDEV_C2D_Trans_x-y.csv Number of data transfer operations

from cache memories and disk drives
(for example, logical LUs)
LDEV_D2CS_Trans.ZIP LDEV_D2CS_Trans_x-y.csv Number of data transfer operations

from disk drives (for example, logical
LUs) to cache memories in sequential
access mode

Table 5 Files containing statistics about logical volumes in parity, external volume, or V-VOL groups

LDEV_D2CR_Trans.ZIP LDEV_D2CR_Trans_x-y.csv Number of data transfer operations
from disk drives (for example, logical
LUs) to cache memories in random
access mode
LDEV_Response.ZIP LDEV_Response_x-y.csv Response time of logical LUs (unit is

microseconds1)
NOTE: The letters x-y in the CSV filenames indicate a parity group. For example, if the filename is
LDEV_IOPS_1-2.csv, the file contains the I/O rate for each logical volume in the parity group 1-2.
Table 6 Files containing statistics about ports

Port_dat.ZIP Port_IOPS.csv Number of read and write operations per second
Port_KBPS.csv Size of data transferred per second (unit is KB/sec)
Port_Response.csv Response time of ports (unit is microseconds1)

Table 7 Files containing statistics about host bus adapters connected to ports

PortWWN_dat.ZIP PortWWN_xx_IOPS.csv I/O rate (that is, number of read and write operations
per second) for HBAs connected to a port
PortWWN_xx_KBPS.csv Size of data transferred per second between a port and

HBAs connected to that port (unit is KB/sec)
PortWWN_xx_Responsecsv Response time between a port and HBAs connected to

that port (unit is microseconds1)
NOTE:
• The letters xx in the CSV filename indicate a port name. For example, if the filename is
PortWWN_1A_IOPS.csv, the file contains the I/O rate for each host bus adapter connected to the
CL1-A port.
• If files are exported to a Windows computer, CSV filenames may end with numbers (for example,
PortWWN_1A_IOPS-1.csv and PortWWN_1a_IOPS-2.csv).

Table 8 Files containing statistics about LU paths

LU_dat.ZIP LU_IOPS.csv Number of read and write operations per second
LU_TransRate.csv Size of data transferred per second (unit is KB/sec)
LU_Seq_Read_IOPS.csv Number of sequential read operations per second
LU_Rnd_Read_IOPS.csv Number of random read operations per second
LU_Seq_Write_IOPS.csv Number of sequential write operations per second
LU_Rnd_Write_IOPS.csv Number of random write operations per second
LU_Seq_Read_Hit.csv Read hit ratio in sequential access mode
LU_Rnd_Read_Hit.csv Read hit ratio in random access mode
LU_Seq_Write_Hit.csv Write hit ratio in sequential access mode
LU_Rnd_Write_Hit.csv Write hit ratio in random access mode
LU_C2D_Trans.csv Number of data transfer operations from cache memories and

disk drives (for example, LUs)
LU_D2CS_Trans.csv Number of data transfer operations from disk drives (for

example, LUs) to cache memories in sequential access mode
LU_D2CR_Trans.csv Number of data transfer operations from disk drives (for

example, LUs) to cache memories in random access mode
LU_Response.csv Response time of LU paths (unit is microseconds1)

Table 9 Files containing statistics about SPM groups

PPCG_dat.ZIP PPCG_IOPS.csv Number of read and write operations per second
PPCG_KBPS.csv Size of data transferred per second (unit is KB/sec)
PPCG_Response.csv Response time of SPM groups (unit is microseconds1)

Table 10 Files containing statistics about host bus adapters belonging to SPM groups

PPCGWWN_dat.ZIP PPCGWWN_xx_IOPS.csv I/O rate (that is, number of read and
write operations per second) for HBAs
belonging to an SPM group
PPCGWWN_xx_KBPS.csv Transfer rate for HBAs belonging to an

SPM group (unit is KB/sec)
PPCGWWN_xx_Response.csv Response time of HBAs belonging to an

SPM group (unit is microseconds1)
PPCGWWN_NotGrouped_IOPS.csv I/O rate (that is, number of read and
write operations per second) for HBAs
that do not belong to any SPM group
PPCGWWN_NotGrouped_100KBPS.csv Transfer rate for HBAs that do not belong

to any SPM group (the unit is KB/sec)
PPCGWWN_NotGrouped_Response.csv Response time of HBAs that do not belong
to any SPM group (unit is microseconds1)

NOTE:
• The letters xx in the CSV filename indicate the name of an SPM group.
• If files are exported to a Windows computer, CSV filenames may end with numbers (for example,
PPCGWWN_mygroup_IOPS-1.csv and PPCGWWN_MyGroup_IOPS-2.csv).

Table 11 Files containing statistics about remote copy operations by Continuous Access XP and
TrueCopy for z/OS (in the whole array)

RemoteCopy_dat.ZIP RemoteCopy.csv The following data in the whole array is saved:
• Usage rate for sidefile cache
• Total number of remote I/Os (read and write operations)
• Total number of remote read I/Os
• Total number of remote write I/Os
• Number of errors that occur during remote I/O
• Number of initial copy remote I/Os
• Number of hits of initial copy remote I/Os
• Average transfer rate (KB/sec) for initial copy remote I/Os
• Response time (milliseconds1) for initial copy
• Number of migration copy remote I/Os
• Number of hits of migration copy remote I/Os
• Number of update copy remote I/Os
• Number of hits of update copy remote I/Os
• Average transfer rate (KB/sec) for update copy remote I/Os
• Response time (milliseconds1) for update copy
• Number of restore copy remote I/Os
• Number of hits of restore copy remote I/Os
• Number of asynchronous update copy remote I/Os
• Number of asynchronous recordsets
• Average transfer rate (KB/sec) for asynchronous update
copy remote I/Os
• Response time (milliseconds1) for asynchronous update
copy
• Number of scheduled recordsets
• Number of recordsets that do not arrive during the schedule
• Number of remaining recordsets when the schedule is
completed
• Number of job activations of consistency manager
• Percentage of completion of copy operations (that is,
number of synchronized pairs / total number of pairs)
• Number of tracks that have not yet been copied by the
initial copy or resync copy operation
1. 1 millisecond is one-thousandth of 1 second

TrueCopy for z/OS (at LU paths)

RCLU_dat.ZIP RCLU_All_RIO.csv Total number of remote I/Os (read and write
operations)
RCLU_All_Read.csv Total number of remote read I/Os
RCLU_All_Write.csv Total number of remote write I/Os
RCLU_RIO_Error.csv Number of errors that occur during remote I/O
RCLU_Initial_Copy_RIO.csv Number of initial copy remote I/Os
RCLU_Initial_Copy_Hit.csv Number of hits of initial copy remote I/Os
RCLU_Initial_Copy_Transfer.csv Average transfer rate (KB/sec) for initial copy

remote I/Os
RCLU_Initial_Copy_Response.csv Response time (milliseconds1) for initial copy at LU

paths
RCLU_Migration_Copy_RIO.csv Number of migration copy remote I/Os
RCLU_Migration_Copy_Hit.csv Number of hits of migration copy remote I/Os
RCLU_Update_Copy_RIO.csv Number of update copy remote I/Os
RCLU_Update_Copy_Hit.csv Number of hits of update copy remote I/Os
RCLU_Update_Copy_Transfer.csv Average transfer rate (KB/sec) for update copy

remote I/Os
RCLU_Update_Copy_Response.csv Response time (milliseconds1) for update copy at

LU paths
RCLU_Restore_Copy_RIO.csv Number of restore copy remote I/Os
RCLU_Restore_Copy_Hit.csv Number of hits of restore copy remote I/Os
RCLU_Asynchronous_RIO.csv Number of asynchronous update copy remote

I/Os
RCLU_Recordset.csv Number of asynchronous recordsets
RCLU_Asynchronous_Copy_ Average transfer rate (KB/sec) for asynchronous

Transfer.csv update copy remote I/Os
RCLU_Asynchronous_Copy_Respons Response time (milliseconds1) for asynchronous

e.csv update copy at LU paths
RCLU_Scheduling_Recordset.csv Number of scheduled recordsets
RCLU_Scheduling_Miss_Recordset Number of recordsets that do not arrive during the

.csv schedule
RCLU_Remained_Recordset.csv Number of remaining recordsets when the

schedule is complete
RCLU_Scheduling_Attempt.csv Number of job activations of consistency manager
RCLU_Pair_Synchronized.csv Percentage of completion of copy operations (that

is, number of synchronized pairs / total number of
pairs)
RCLU_Out_of_Tracks.csv Number of tracks that have not yet been copied

by the initial copy or resync copy operation

TrueCopy for z/OS (at logical volumes controlled by a particular CU)

RCLDEV_All_RIO.ZIP RCLDEV_All_RIO_xx.csv Total number of remote I/Os (read and write
operations)
RCLDEV_All_Read.ZIP RCLDEV_All_Read_xx.csv Total number of remote read I/Os
RCLDEV_All_Write.ZIP RCLDEV_All_Write_xx.csv Total number of remote write I/Os
RCLDEV_RIO_Error.ZIP RCLDEV_RIO_Error_xx.csv Number of errors that occur during remote I/O
RCLDEV_Initial_Copy_ RCLDEV_Initial_Copy_ Number of initial copy remote I/Os

RIO.ZIP RIO_xx.csv
RCLDEV_Initial_Copy_ RCLDEV_Initial_Copy_ Number of hits of initial copy remote I/Os

Hit.ZIP Hit_xx.csv
RCLDEV_Initial_Copy_ RCLDEV_Initial_Copy_ Average transfer rate (KB/sec) for initial copy

Transfer.ZIP Transfer_xx.csv remote I/Os
RCLDEV_Initial_Copy_ RCLDEV_Initial_Copy_ Response time (milliseconds1) for initial copy at

Response.ZIP Response_xx.csv logical volumes
RCLDEV_Migration_ RCLDEV_Migration_Copy_ Number of migration copy remote I/Os

Copy_RIO.ZIP RIO_xx.csv
RCLDEV_Migration_ RCLDEV_Migration_Copy_ Number of hits of migration copy remote I/Os

Copy_Hit.ZIP Hit_xx.csv
RCLDEV_Update_Copy_ RCLDEV_Update_Copy_RIO_ Number of update copy remote I/Os

RIO.ZIP xx.csv
RCLDEV_Update_Copy_ RCLDEV_Update_Copy_Hit_ Number of hits of update copy remote I/Os

Hit.ZIP xx.csv
RCLDEV_Update_Copy_ RCLDEV_Update_Copy_ Average transfer rate (KB/sec) for update copy

Transfer.ZIP Transfer_xx.csv remote I/Os
RCLDEV_Update_Copy_ RCLDEV_Update_Copy_ Response time (milliseconds1) for update copy at

Response.ZIP Response_xx.csv logical volumes
RCLDEV_Restore_Copy_ RCLDEV_Restore_Copy_ Number of restore copy remote I/Os

RIO.ZIP RIO_xx.csv
RCLDEV_Restore_Copy_ RCLDEV_Restore_Copy_ Number of hits of restore copy remote I/Os

Hit.ZIP Hit_xx.csv
RCLDEV_Asynchronous_ RCLDEV_Asynchronous_ Number of asynchronous update copy remote

RIO.ZIP RIO_xx.csv I/Os
RCLDEV_Recordset.ZIP RCLDEV_Recordset_xx.csv Number of asynchronous recordsets
RCLDEV_Asynchronous_ RCLDEV_Asynchronous_ Average transfer rate (KB/sec) for asynchronous

Copy_Transfer.ZIP Copy_Transfer_xx.csv update copy remote I/Os
RCLDEV_Asynchronous_ RCLDEV_Asynchronous_ Response time (milliseconds1) for asynchronous

Copy_Response.ZIP Copy_Response_xx.csv update copy at logical volumes
RCLDEV_Scheduling_ RCLDEV_Scheduling_ Number of scheduled recordsets

Recordset.ZIP Recordset_xx.csv
RCLDEV_Scheduling_Mi RCLDEV_Scheduling_Miss_ Number of recordsets that do not arrive during the

ss_Recordset.ZIP Recordset_xx.csv schedule
RCLDEV_Remained_Reco RCLDEV_Remained_ Number of remaining recordsets when the
rdset.ZIP Recordset_xx.csv schedule is complete
RCLDEV_Scheduling_At RCLDEV_Scheduling_Attem Number of job activations of consistency manager

tempt.ZIP pt_xx.csv

TrueCopy for z/OS (at logical volumes controlled by a particular CU) (continued)

RCLDEV_Pair_Synchron RCLDEV_Pair_Synchronize Percentage of completion of copy operations (that
ized.ZIP d_xx.csv is, number of synchronized pairs / total number of
pairs)
RCLDEV_Out_of_Tracks RCLDEV_Out_of_Tracks_xx Number of tracks that have not yet been copied by
.ZIP .csv the initial copy or resync copy operation
NOTE: The letters xx in the CSV filenames indicate a CU image number. For example, if the filename is
RCLDEV_All_RIO_10.csv, the file contains the total number of remote I/Os of the logical volumes
controlled by the CU that has an image number of 10.
.
TrueCopy for z/OS (at CLPR)

RCCLPR_dat.ZIP RCCLPR_SideFile.csv Sidefile usage rate per CLPR (unit is%)
Table 15 Files containing statistics about remote copy operations by Continuous Access XP Journal and
Universal Replicator for z/OS (in the whole array)

UniversalReplicator.ZIP UniversalReplicator.csv The following data in the whole array is
saved:
• Number of read I/Os per second
• Number of read hit records per second
• Number of write I/Os per second
• Number of write hit records per second
• Amount of data read per second (unit is
KB/sec)
• Amount of data written per second (unit
is KB/sec)
• Initial copy hit rate (unit is percent)
• Average transfer rate for initial copy
operations (unit is KB/sec)
• Number of asynchronous remote I/Os
per second at the primary array
• Number of journals at the primary array
• Average transfer rate for journals in the
primary array (unit is KB/sec)
• Remote I/O process time on the primary
array (unit is milliseconds1)
• Number of asynchronous remote I/Os
per second at the secondary array
• Number of journals at the secondary
array
• Average transfer rate for journals in the
secondary array (unit is KB/sec)
• Remote I/O process time on the
secondary array (unit is milliseconds1)

Universal for z/OS (at journal groups)

URJNL_dat.ZIP URJNL_Read_Record.csv Number of read I/Os per second
URJNL_Read_Hit.csv Number of read hit records per second
URJNL_Write_Record.csv Number of write I/Os per second
URJNL_Write_Hit.csv Number of write hit records per second
URJNL_Read_Transfer.csv Amount of data read per second (unit is

KB/sec)
URJNL_Write_Transfer.csv Amount of data written per second (unit is

KB/sec)
URJNL_Initial_Copy_Hit.csv Initial copy hit rate (unit is percent)
URJNL_Initial_Copy_Transfer.csv Average transfer rate for initial copy

operations (unit is KB/sec)
URJNL_MCU_Asynchronous_RIO.csv Number of asynchronous remote I/Os per

second at the primary array
URJNL_MCU_Asynchronous_Journal.csv Number of journals at the primary array
URJNL_MCU_Asynchronous_Copy_ Average transfer rate for journals in the

Transfer.csv primary array (unit is KB/sec)
URJNL_MCU_Asynchronous_Copy_ Remote I/O process time on the primary

Response.csv array (unit is milliseconds1)
URJNL_RCU_Asynchronous_RIO.csv Number of asynchronous remote I/Os per
second at the secondary array
URJNL_RCU_Asynchronous_Journal.csv Number of journals at the secondary array
URJNL_RCU_Asynchronous_Copy_ Average transfer rate for journals in the

Transfer.csv secondary array (unit is KB/sec)
URJNL_RCU_Asynchronous_Copy_ Remote I/O process time on the secondary

Response.csv array (unit is milliseconds1)
URJNL_MCU_Journal_Filling.csv Data usage rate for master journals (unit is
percent)
URJNL_MCU_JNCB_Filling.csv Metadata usage rate for master journals

(unit is percent)
URJNL_RCU_Journal_Filling.csv Data usage rate for restore journals (unit is

percent)
URJNL_RCU_JNCB_Filling.csv Metadata usage rate for restore journals

(unit is percent)

Universal Replicator for z/OS (at LU paths)

URLU_dat.ZIP URLU_Read_Record.csv Number of read I/Os per second
URLU_Read_Hit.csv Number of read hit records per second
URLU_Write_Record.csv Number of write I/Os per second
URLU_Write_Hit.csv Number of write hit records per second
URLU_Read_Transfer.csv Amount of data read per second (unit is KB/sec)
URLU_Write_Transfer.csv Amount of data written per second (unit is KB/sec)
URLU_Initial_Copy_Hit.csv Initial copy hit rate (unit is percent)
URLU_Initial_Copy_Transfer.csv Average transfer rate for initial copy operations

(unit is KB/sec)
Universal Replicator for z/OS (at logical volumes controlled by a particular CU)

URLDEV_Read_Record.ZIP URLDEV_Read_Record_xx.csv Number of read I/Os per second
URLDEV_Read_Hit.ZIP URLDEV_Read_Hit_xx.csv Number of read hit records per second
URLDEV_Write_Record.ZIP URLDEV_Write_Record_xx.csv Number of write I/Os per second
URLDEV_Write_Hit.ZIP URLDEV_Write_Hit_xx.csv Number of write hit records per second
URLDEV_Read_Transfer.ZIP URLDEV_Read_Transfer_xx.csv Amount of data read per second (unit is

KB/sec)
URLDEV_Write_Transfer.ZIP URLDEV_Write_Transfer_xx.csv Amount of data written per second (unit

is KB/sec)
URLDEV_Initial_Copy_Hit.ZIP URLDEV_Initial_Copy_Hit_xx.csv Initial copy hit rate (unit is percent)
URLDEV_Initial_Copy_ URLDEV_Initial_Copy_Transfer_ Average transfer rate for initial copy

Transfer.ZIP xx.csv operations (unit is KB/sec)
NOTE: The letters xx in CSV filenames indicate a CU image number. For example, if the filename is
URLDEV_Read_Record_10.csv, the file contains the number of read I/Os (per second) of the logical
volumes controlled by the CU that has an image number of 10.
Preparing for using the Export Tool

This section explains how to prepare for using the Export Tool.
Requirements for using the Export Tool
The following components are required to use the Export Tool:
• A Windows computer or a UNIX® computer
The Export Tool runs on Windows computers and UNIX computers that can run Command View XP or
XP Remote Web Console. If your Windows or UNIX computer is unable to run Command View XP or
XP Remote Web Console, your computer is unable to run the Export Tool. For more information about
computers that can run Command View XP or XP Remote Web Console, see the HP StorageWorks
Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console
user guide for the specific arrays.
• Java™ Runtime Environment (JRE)

To be able to use the Export Tool, you must install Java Runtime Environment on your Windows or
UNIX computer. If your computer runs Command View XP or XP Remote Web Console, JRE is already
installed on your computer and you can install the Export Tool. If your computer does not run
Command View XP or XP Remote Web Console but contains an appropriate version of JRE, you can
install the Export Tool on your computer.
NOTE: The JRE version required for running the Export Tool is the same as the JRE version
required for running Command View XP or XP Remote Web Console. For detailed information
about the JRE version required for running Command View XP or XP Remote Web Console, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP
Remote Web Console user guide for the specific arrays.
• A user ID exclusively for use with the Export Tool

To use the Export Tool, you must create a user ID that will be used exclusively with the Export Tool.
When you create the user ID, note the following:
• Permissions for local array programs
If you use the Export Tool only to save monitoring data to files, do not assign any permission to the
user ID for use with the Export Tool. If a user ID having permission is used with the Export Tool, the
array configuration might be changed in an unfavorable way by an unidentified user.
If you use the Export Tool to save monitoring data, start or stop monitoring, and change the
gathering interval with the set subcommand, the user ID must have at least one of the permissions
for Auto LUN XP, Continuous Access XP, TrueCopy for z/OS, Continuous Access XP Journal, and
Universal Replicator for z/OS.
• User types
You can specify any user type for the user ID for use with the Export Tool.
If you specify storage administrator for the user ID, all the monitoring data described from
Table 3 to Table 18 can be saved into files.
If you specify storage partition administrator for the user ID, the monitoring data that
can be saved and the Export Tool functions are limited. For more information, see ”Limitations of
the Export Tool” on page 82.
For more information about creating user IDs, see the HP StorageWorks LUN Configuration and
Security Manager XP user guide for the specific array. For more information about Performance
Control XP, see ”Performance Control XP” on page 11.
• The Export Tool program
The Export Tool is contained in the HP StorageWorks RAID Manager XP Library CD. For detailed
information about how to install the Export Tool on a Windows computer, see ”Installing the Export
Tool on a Windows computer” on page 46. For detailed information about how to install the Export
Tool on a UNIX computer, see section ”Installing the Export Tool on a UNIX computer” on page 47.
Installing the Export Tool on a Windows computer
1. Create a directory on your Windows computer.
In later steps, you will install the Export Tool on the new directory.
2. Insert the Program Products CD into the CD-ROM drive.
3. Locate the self-extracting file export.EXE in the directory \program\monitor\win_nt in your
CD-ROM disc, and then copy export.EXE to the new directory you created earlier.
4. Double-click export.EXE on your computer.
The Export Tool is installed. Also, a new directory named export is created.
NOTE:
• The export directory contains a couple of files, which includes runUnix.bat. HP recommends
deleting runUnix.bat because this file is no longer needed.

• The Export Tool program is a Java class file and is located in the export\lib directory.
Installing the Export Tool on a UNIX computer

1. Create a directory on your UNIX computer.
In later steps, you will install the Export Tool on the new directory.
2. Insert the Program Products CD in the CD-ROM drive.
• If you are using Solaris, locate the archive file export.tar in the directory
/export_tool/solaris in your CD-ROM disc, and copy export.tar to the new directory you
created earlier.
• If you are using HP-UX, locate the archive file export.tar in the directory /export_tool/hp-ux
in your CD-ROM disc, and copy export.tar to the new directory you created earlier.
4. Decompress export.tar on your computer.
The Export Tool is installed. Also, a new directory named export is created.
NOTE:
• The export directory contains a couple of files, which include runWin.bat. HP recommends
deleting runWin.bat because this file is no longer needed.
• The Export Tool program is a Java class file and is located in the export/lib directory.
Using the Export Tool

To export monitoring data, you must prepare a command file and a batch file. This section explains how
to prepare a command file and a batch file, and then explains how to run the Export Tool.
Preparing a command file
To run the Export Tool, you must write scripts for exporting monitoring data. When writing scripts, you
must write several subcommands in a command file. When you run the Export Tool, subcommands in the
command file execute sequentially, and monitoring data is saved in files.
Here is a sample command file:
svpip 158.214.135.57 ; Specifies IP address of SVP

login expusr passwd ; Logs user into SVP
show ; Outputs storing period to standard output
group PhyPG Long ; Specifies type of data to be exported and type of
; storing period
group RemoteCopy ; Specifies type of data to be exported
shortrange 200410010850:200410010910
; Specifies term of data to be exported for data stored
; in short range
longrange 200409301430:200410011430
; Specifies term of data to be exported for data stored
; in long range
outpath out ; Specifies directory in which files will be saved
option compress ; Specifies whether to compress files
apply ; Executes processing for saving monitoring data in files
Figure 18 Sample command file
NOTE: In this file, a semicolon (;) indicates the beginning of a comment. Characters from a semicolon to
the end of the line are regarded as a comment.

Subcommands in this command file are explained as follows:
• svpip 158.214.135.57
Specifies that you are logging into the SVP whose IP address is 158.214.135.57. You must log into
the SVP when using the Export Tool.
The svpip subcommand specifies the SVP’s IP address. You must include the svpip subcommand in
your command file. For detailed information, refer to ”The svpip subcommand” on page 56.
• login expusr passwd
Specifies that you use the user ID expusr and the password passwd to log into the SVP.
The login subcommand logs the specified user into the SVP. You must include the login
subcommand in your command file. For detailed information, see ”The login subcommand” on
page 57.
CAUTION: When writing the login subcommand in your command file, you must specify a user
ID that should be used exclusively for running the Export Tool. See ”Files to be exported” on
page 32 for reference.
CAUTION: Secure files containing user IDs and password to prevent the information from being
compromised and used for access by unauthorized people.
• show
Checks the SVP to find the period of monitoring data stored in the SVP and data collection interval
(called the gathering interval in Auto LUN XP), and then outputs them to the standard output (for
example, the command prompt) and log file.
Auto LUN XP collects statistics by the two types of storing periods: in short range and in long range.
The show subcommand displays the storing periods and the gathering intervals for these types of
monitoring data.
The following is an example of information that the show subcommand outputs:
Short Range From: 2004/10/01 01:00 - To: 2004/10/01 15:00Interval : 1min

Long Range From: 2004/09/01 00:00 - To: 2004/10/01 15:00Interval : 15min
Remote Copy From: 2004/09/30 00:00 - To: 2004/10/01 15:00
Short Range indicates the storing period and gathering interval for monitoring data stored in short
range. Long Range indicates monitoring data stored in long range. In this example, monitoring data
in short range is stored every 1 minute in the term of 1:00-15:00 on Oct. 1, 2004. Also, monitoring
data in long range is stored every 15 minutes from Sep. 1, 2004, 0:00 through Oct. 1, 2004,
15:00. When running the Export Tool, you can export monitoring data within these periods into files.
All monitoring items are stored in short range, but part of the monitoring items is stored in the short
range and long range. For details on monitoring items that can be stored in long range, see ”The
longrange subcommand” on page 70.
Using the show subcommand is not mandatory, but HP recommends you include the show
subcommand in your command file. If an error occurs when running the Export Tool, you might be
able to find the error cause by checking the log file for information issued by the show subcommand.
For detailed information, see ”The show subcommand” on page 57.
• group PhyPG Long and group RemoteCopy
Specifies the type of data you want to export. Specify an operand following group to define the type
of data to be exported. Basically, monitoring data stored in short range is exported, but you can
export monitoring data stored in long range when specifying some of the operands.
The group PhyPG Long subcommand in Figure 18 specifies to export usage statistics about parity
groups in long range. Also, the group RemoteCopy subcommand specifies to export statistics about
remote copy operations by Continuous Access XP and TrueCopy for z/OS in short range. You can
specify multiple lines of the group subcommand to export multiple monitoring items at the same time.

For detailed information, see ”The group subcommand” on page 58.
• shortrange 200410010850:200410010910, and
longrange 200409301430:200410011430, and
remotecopyrange 200409301430:200410011430
The shortrange and longrange subcommands specify the monitoring data term to be exported.
Use these subcommands to narrow the export-target term within the stored data. You can specify both
the shortrange and longrange subcommands at the same time. The difference between these
subcommands is as follows:
• The shortrange subcommand is valid for monitoring data in short range. You can use this
subcommand to narrow the export-target term for all the monitoring items you can specify by the
group subcommand.
Specify a term within Short Range From XXX To XXX which is output by the show
subcommand.
• The longrange subcommand is valid for monitoring data in long range. You can use this
subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyCSW operand with
the Long option in the group subcommand. (The items that can be saved by these operands are
the monitoring data displayed in the Physical tab of the Auto LUN XP pane with selecting
longrange.)
Specify a term within Long Range From XXX To XXX which is output by the show
subcommand.
In Figure 18, the shortrange 200410010850:200410010910 subcommand specifies the term
8:50-9:10 on Oct. 1, 2004. This subcommand is applied to the group RemoteCopy subcommand
in this example. When running the Export Tool, it exports statistics about remote copy operations by
Continuous Access XP and TrueCopy for z/OS in the term specified by the shortrange
subcommand.
Also, in Figure 18, the longrange 200409301430:200410011430 subcommand specifies the
term from Sep. 30, 2004, 14:30 to Oct. 1, 2004, 14:30. This subcommand is applied to the group
PhyPG Long subcommand in this example. When running the Export Tool, it exports usage statistics
about parity groups in the term specified by the longrange subcommand.
If you run the Export Tool without specifying the shortrange or longrange subcommand,
monitoring data in the whole storing period (data in the period displayed by the show subcommand)
is exported.
For detailed information, see ”The shortrange subcommand” on page 67 and ”The longrange
subcommand” on page 70.
• outpath out
Specifies files should be saved in the directory named out in the current directory.
The outpath subcommand specifies the directory in which files should be saved. For detailed
information, see ”The outpath subcommand” on page 72.
• option compress
Specifies that the Export Tool should compress monitoring data in ZIP files.
The option subcommand specifies whether files are saved in ZIP or CSV format. For detailed
information, see ”The option subcommand” on page 72.
• apply
Saves monitoring data in files. For detailed information, see ”The apply subcommand” on page 73.
When installing the Export Tool, the file command.txt is stored in the export directory. The command.txt
file contains sample subcommands for your command file. HP recommends customizing the
subcommands in command.txt according to your needs. For detailed information about subcommand
syntax, see ”Command reference” on page 54.
Preparing a batch file
To run the Export Tool, you need a batch file. The Export Tool starts and saves monitoring data in files
when you execute the batch file.

The installation directory for the Export Tool (that is, the export directory) contains two batch files:
runWin.bat and runUnix.bat. If your computer runs Windows, use runWin.bat. If your computer runs
UNIX, use runUnix.bat.
Figure 19 illustrates scripts in runWin.bat and runUnix.bat. These batch files include a command line
that executes a java command. When executing your batch file, the java command executes
subcommands specified in your command file, and saves monitoring data in files.
Batch file for Windows computers (runWin.bat)
java -classpath "./lib/JSanExport.jar;./lib/JSanRmiServer.jar"

-Dmd.command=command.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain ↵
pause ↵
Batch file for UNIX computers (runUnix.bat)
#! /bin/sh ↵
java -classpath "./lib/JSanExport.jar:./lib/JSanRmiServer.jar"
Figure 19 Scripts in batch files
NOTE: The ↵ symbol indicates the end of a command line.
If the computer that runs the Export Tool communicates directly with the SVP, you usually do not need to
change scripts in runWin.bat and runUnix.bat. However, you might need to edit the java command
script in your text editor in some circumstances, for example:
• If your command file name is not command.txt
• If you moved your command file to a different directory
• If you do not want to save log files in the log directory
• If you want to name log files as you like
If the computer that runs the Export Tool communicates with the SVP via a proxy host, you must edit the
java command script in your text editor. When editing the java command script, you must specify the
proxy host’s host name (or IP address) and port number. For example, if the host name is Jupiter and
the port number is 8080, the resulting command script is as follows:

-Dhttp.proxyHost=Jupiter -Dhttp.proxyPort=8080 -Dmd.command=command.txt
-Dmd.logpath=log sanproject.getmondat.RJMdMain ↵
pause ↵
#! /bin/sh ↵
Figure 20 Scripts in batch files (when specifying the proxy host’s host name)
If the proxy host’s IP address is 158.211.122.124 and the port number is 8080, the resulting command
script is as follows:


-Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Dmd.command=command.txt
pause ↵
#! /bin/sh ↵
-Dhttp.proxyHost=158.211.122.124 -Dhttp.proxyPort=8080 -Dmd.command=command.txt
Figure 21 Scripts in batch files (when specifying the IP address of a proxy host)
For detailed information about syntax of the java command, see ”The java command for exporting data
In files” on page 75.
Running the Export Tool
To run the Export Tool and save monitoring data in files, you must execute your batch file. To execute your
batch file, you must enter the name of the batch file at the command prompt, and press Enter (see
Figure 22 for reference). If you are using a Windows computer, you can double-click the batch file to
execute the batch file.
c:\WINDOWS> cd c:\export ← Go to the directory containing runWin.bat

c:\export> runWin.bat ← Execute runWin.bat
Figure 22 An example of executing a batch file (on a Windows computer)

When the Export Tool starts exporting monitoring data, dots (...) are issued to the standard output (for
example, the command prompt). The dots increment as export processing continues (see Figure 23). If an
internal error occurs, the exclamation mark (!) is issued to the standard output and the Export Tool
attempts to restart exporting data. If the export processing restarts, dots reappear and increment until
export processing finishes.
[ 2] svpip 158.214.135.57
[ 3] login User = expusr, Passwd = [****************]
:
:
[ 6] group Port
:
:
[20] apply
Start gathering port data
Target = 16, Total = 16
+----+----+----+----+----+----+----+----+----+----+
...........................!
.................................
End gathering port data
Figure 23 Sample command prompt outputs when the Export Tool runs
When the Export Tool successfully finishes, monitoring data is usually compressed in ZIP-format archive
files. To obtain CSV files, you must decompress ZIP files and extract CSV files out of the ZIP files. If the
operating system on your computer does not include a feature for decompressing ZIP files, you must
obtain software for decompressing files.

For a complete list of files to be saved by the Export Tool, see ”Files to be exported” on page 32.
Notes
• When an internal error shown in Table 19 occurs during export processing, the exclamation mark (!)
appears and retries export processing. By default, the Export Tool can retry processing up to three
times. If export processing does not finish after three retries or if an internal error occurs other than
those in Table 19, the Export Tool does not retry the processing. In this case, you must quit the
command prompt and run the Export Tool again. However, you can change the maximum number of
retries using the retry subcommand. For detailed information, see ”The retry subcommand” on
page 56.
If the error persists, contact your HP account support representative.
Table 19 Errors for which the Export Tool retries processing
Error message ID Cause of error

0001 4001 An error occurred.
0001 5400 Since the server is busy, monitoring data cannot be obtained.
0001 5508 An administrator is changing a system environment file.
0002 2016 Array is refreshing, or user-specified settings are being registered.
0002 5510 Array is refreshing, or another user is changing configuration.
0002 6502 Now processing.
0002 9000 Another user has lock.
0003 2016 SNMP or SVP has lock.
0003 2033 Server is not ready yet, or internal processing is being executed.
0003 3006 An error occurred.
0405 8003 Array status is invalid.
5205 2003 An internal process is being executed, or maintenance is in progress.
5205 2033 Server is now gathering the latest data.
5305 2033 Server is now gathering the latest data.
5305 8002 Array status is invalid.
• If you specify the nocompress operand for the option subcommand, the Export Tool saves files in
CSV format instead of ZIP format (for detailed information, see ”The option subcommand” on
page 72). Note that, when files are saved in CSV format instead of ZIP format, the file-saving process
would take longer and the resulting files would be larger.
• Files the Export Tool saves are often very large. The total file size for all files can be as large as
approximately 2 GB. For this reason, the export process might take a long time (see Table 20). To
export statistics spanning a long time period, HP recommends using the Export Tool more than one
time, rather than using the tool only one time to export the whole statistics. For example, to export
statistics spanning 24 hours, you could run the Export Tool eight times; each time the Export Tool runs,
the tool should export statistics spanning three hours.
Table 20 Estimate examples of time required for exporting files
Operand for Estimated time Remarks

the group
subcommand
Port 5 minutes Assumes the Export Tool should save statistics about 128 ports within a
24-hour period.
PortWWN 5 minutes Assumes the Export Tool should save statistics about 128 ports within a
24-hour period.

Table 20 Estimate examples of time required for exporting files (continued)
Operand for Estimated time Remarks

the group
subcommand
PPCG 5 minutes Assumes:
• There are eight SPM groups, and eight WWNs are registered on each
SPM group.
• There is a WWN that is not registered on any SPM group.
• The Export Tool should save statistics about SPM groups and WWNs
described above within a 24-hour period.
LDEV 60 minutes Assumes:
• The Export Tool should save statistics about 8,192 logical volumes
within a 24-hour period.
• The Export Tool is used eight times. Each time the Export Tool is used,
the tool obtains statistics within a 3-hour period.
LU 60 minutes Assumes:
• The Export Tool should save statistics about 12,288 LUs within a
24-hour period.
• The Export Tool is used eight times. Each time the Export Tool is used,
the tool obtains statistics within a 3-hour period.
• Whenever the Export Tool runs, it creates a new log file on your computer. Therefore, if you run the
Export Tool repeatedly, the size of free space on your computer is reduced. To secure free space on
your computer, HP strongly recommends deleting log files regularly. For information about the
directory containing log files, see ”The java command for exporting data In files” on page 75.
• For information about solving errors with the Export Tool, see ”Troubleshooting the Export Tool” on
page 76.
• The Export Tool returns a termination code when the Export Tool finishes (see Table 21).
Table 21 Termination codes that the Export Tool returns
Termination code Meaning

0 The Export Tool finished successfully.
1 An error occurred when the set subcommand (see ”The set subcommand” on page 73)
executed, because an attempt to switch to Modify mode failed. Some other user might
have been logged on in Modify mode.
2 An error occurred due to some reason unrelated to SVP modes (that is, View mode and
Modify mode).
3 An error occurred due to more than one reason. One of the reasons is that an attempt to
switch to Modify mode failed when the set subcommand (see ”The set subcommand” on
page 73) executed. Some other user might have been logged on in Modify mode.
4 The user ID has no permissions for Auto LUN XP, Continuous Access XP, and TrueCopy for
z/OS.
If you want to use a reference to a termination code in your batch file, do the following:
• In a Windows batch file, write %errorlevel% in the batch file.
• In a UNIX Bourne shell script, write %? in the shell script.
• In a UNIX C shell script, write %status in the shell script.

A reference to a termination code is used in the following example of a Windows batch file. If this
batch file executes and the Export Tool returns the termination code 1 or 3, the command prompt
displays a message that indicates the set subcommand fails.

if %errorlevel%==1 echo THE SET SUBCOMMAND FAILED ↵
if %errorlevel%==3 echo THE SET SUBCOMMAND FAILED ↵
pause ↵
Figure 24 Sample batch file including a reference to termination code
Command reference
This section explains details about subcommands you can write in your command file and the java
command you should use in your batch file. Table 22 lists the subcommands explained in this section. The
java command is explained in ”The java command for exporting data In files” on page 75.
Table 22 Subcommand list
Subcommand Function See

svpip Specifies the IP address of the SVP to be logged into. ”The svpip subcommand” on
page 56
retry Makes settings on retries of export processing. ”The retry subcommand” on

page 56
login Logs the specified user into the SVP. ”The login subcommand” on
page 57
show Checks the SVP to find the period of monitoring data ”The show subcommand” on
stored in the SVP and the data collection interval (called page 57
the gathering interval), and then outputs them to the
standard output and log file.
group Specifies the type of data to be exported. ”The group subcommand” on

page 58
shortrange Specifies the term of monitoring data to be exported for ”The shortrange subcommand”
short range monitoring data. on page 67
longrange Specifies the term of monitoring data to be exported for ”The longrange subcommand”
long range monitoring data. on page 70
outpath Specifies the directory in which files should be saved. ”The outpath subcommand” on
page 72
option Specifies whether to save files in ZIP or CSV format. ”The option subcommand” on
page 72
apply Saves monitoring data in files. ”The apply subcommand” on

page 73
set Starts or ends monitoring an array and also specifies the ”The set subcommand” on
gathering interval in short range monitoring. page 73
help Displays the online Help for subcommands. ”The help subcommand” on
page 74
Command syntax
This section explains the syntax of subcommands you can write in the command file. This section also
explains the syntax of the java command you should use in the batch file.

• Conventions used in this section
This section uses the following symbols and typefaces to explain syntax:
• Δ
Indicates a space.
• bold
Indicates characters you must type as they are.
• italics
Indicates a type of operand. You do not need to type characters in italics as they are.
• [ ]
Indicates one or more operands that can be omitted.
If two or more operands are enclosed by square brackets and are delimited by vertical bars (|),
you can select one of the operands. For detailed information, see Table 23.
• { }
Indicates you must select one operand from the operands enclosed by the braces. Two or more
operands are enclosed by the braces and are delimited by vertical bars (|). For detailed
information, see Table 23.
Indicates that a previously used operand can be repeated. For detailed information, see Table 23.
Table 23 Syntax descriptions
Syntax The syntax indicates that you can write the following script
connectΔip-address connect 123.01.22.33
destinationΔ[directory] • destination
• destination c:\temp
compressΔ[yes|no] • compress
• compress yes
• compress no
answerΔ{yes|no} • answer yes

• answer no
portsΔ[name][Δ...] • ports
• ports port-1
• ports port-1 port-2
• Notes on writing script in the command file

Note the following when writing script in the command file:
• Ensure that only one subcommand is used on one line.
• Empty lines in any command file are ignored.
• Use a semicolon (;) to insert a comment in the command file. If you enter a semicolon on one line,
the remaining characters in that line are regarded as a comment.
;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; COMMAND FILE: command.txt ;;;;
;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
svpip 158.214.135.57 ; IP address of SVP
login expusr "passwd" ; Log onto SVP
Figure 25 Examples of comments

• Viewing the online Help for subcommands
You can display the online Help to view the syntax of subcommands when working at the command
prompt. To view the online Help, you must use the Export Tool’s help subcommand. For detailed
information, see ”The help subcommand” on page 74.

The svpip subcommand
Syntax
svpipΔ{ip-address|host-name}
Description
The svpip subcommand specifies the SVP’s IP address or host name.
Operands
ip-address
Specifies the SVP’s IP address.
host-name
Specifies the SVP’s host name.
If the host name includes any character that is not alphanumeric or a period, the host name must be
enclosed by double quotation marks (").
Example
The following example specifies the SVP’s IP address as 158.214.127.170.
svpip 158.214.127.170
The retry subcommand

Syntax
retryΔ[time=m]Δ[count=n]
Description
The retry subcommand makes settings on retries of export processing.
When an internal error occurs during export processing, the Export Tool stops processing and retries
export processing. By default, the Export Tool can retry processing up to three times, but you can change
the maximum number of retries using the retry subcommand.
By default, the interval between one retry and the next retry is two minutes. You can change the interval
using the retry subcommand.
The retry subcommand must execute before the login subcommand executes.
Operands
time=m
Specifies the interval between retries in minutes.
m is a value within the range of 1 to 59.
If this operand is omitted, the interval between retries is two minutes.
count=n
Specifies the maximum number of retries.
If n is 0, the number of retries is unlimited.
If this operand is omitted, the maximum number of retries is 3.

Example
In the following command file, the interval between retries is five minutes and the maximum number of
retries is 10.
svpip 158.214.135.57
retry time=5 count=10
login expusr passwd
show
group Port
shortrange 200404010850:200404010910
outpath out
option compress
apply
The login subcommand

Syntax
loginΔuseridΔpassword
Description
The login subcommand uses a user ID and password to log the specified user in the SVP.
The svpip subcommand must execute before the login subcommand executes.
The login subcommand fails if monitoring data does not exist in the SVP.
Operands
userid
Specifies the user ID for the SVP.
If the user ID includes any non-alphanumeric character, the user ID must be enclosed by double
quotation marks (").
NOTE: Be sure to specify a user ID that should be used exclusively with the Export Tool. For
detailed information, see ”Requirements for using the Export Tool” on page 45.
password
Specifies the password of the user.
If the password includes any non-alphanumeric character, the password ID must be enclosed by
double quotation marks (").
Example
This example logs the user expusr into the SVP whose IP address is 158.214.127.170. The password
is pswd.
svpip 158.214.127.170
login expuser pswd
The show subcommand

Syntax
show
Description
The show subcommand outputs the following information to the standard output (for example, to the
command prompt):

• Period during which monitoring data was collected onto the SVP (storing period).
• Interval at which the monitoring data was collected (gathering interval).
Auto LUN XP collects statistics by the type of storing period: in short range and in long range. In
short-range monitoring, monitoring data between 1 and 15 days is stored in the SVP. In long-range
monitoring, monitoring data up to three months is stored in the SVP.
The show subcommand displays the storing period and gathering interval for these types of monitoring
data: in short range and in long range.
For example, the show command outputs the following information:
Short Range From: 2004/10/01 01:00 - To: 2004/10/01 15:00Interval : 1min

Long Range From: 2004/09/01 00:00 - To: 2004/10/01 15:00Interval : 15min
Remote Copy From: 2004/09/30 00:00 - To: 2004/10/01 15:00
Short Range indicates the storing period and gathering interval of monitoring data stored in short
range. Long Range indicates those of monitoring data stored in long range. When running the Export
Tool, you can export monitoring data within these periods into files. If you use the shortrange or
longrange subcommand, you can also narrow the term of data to be exported (see ”The shortrange
subcommand” on page 67 or ”The longrange subcommand” on page 70).
From indicates the starting time for collecting monitoring data. To indicates the ending time for collecting
monitoring data.
Interval indicates the interval at which the monitoring data was collected (gathering interval. For
example, Interval : 15 min. indicates that monitoring data was collected at 15-minute intervals.
Storing periods output by the show subcommand is the same as the information displayed in the
Monitoring Term area of the Auto LUN XP pane (see Figure 26).
Figure 26 Information output by the show subcommand

The login command must execute before the show subcommand executes.
The group subcommand

Syntax
groupΔ{PhyPGD[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...]|
PhyLDEVΔ[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...] |
PhyExGΔ[[exg-id]:[exg-id]][Δ...]|
PhyExLDEVΔ[[exg-id]:[exg-id]][Δ...]|
PhyProcΔ[Short|Long]|
PhyCSWΔ[Short|Long]|
PGΔ[[parity-group-id|V-VOL-group-id|exg-id]:
[[parity-group-id|V-VOL-group-id|exg-id]][Δ...]|
LDEVΔ[[parity-group-id|V-VOL-group-id|exg-id]
[[parity-group-id|V-VOL-group-id|exg-id]][Δ...]|
PortΔ[[port-name]:[port-name]][Δ...]|

PortWWNΔ[[port-name]:[port-name]][Δ...]|
LUΔ[[port-name.host-group-id]:[port-name.host-group-id]][Δ...]|
PPCGΔ[[SPM-group-name]:[SPM-group-name]][Δ...]|
PPCGWWNΔ[[SPM-group-name]:[SPM-group-name]][Δ...]|
RemoteCopy Δ|
RCLU Δ[ [port-name.host-group-id]:[port-name.host-group-id]][Δ...]|
RCLDEV Δ[[CU-id]:[CU-id]][Δ...]|
RCCLPR Δ|
UniversalReplicatorΔ|
URJNL Δ[[JNL-group-id]:[JNL-group-id]][Δ...]|
URLU Δ[ [port-name.host-group-id]:[port-name.host-group-id]][Δ...]|
URLDEV Δ[[CU-id]:[CU-id]][Δ...]
}
Description
The group subcommand specifies the type of monitoring data you want to export. This command uses an
operand (such as PhyPG and PhyLDEV above) to specify the type of monitoring data.
Table 24 shows monitoring data that can be saved into files by each operand, and the saved ZIP files.
For details on the monitoring data saved in these files, see the tables indicated in the See column.
Table 24 Operands of the group subcommand and saved monitoring data
Operand Pane of Auto Monitoring data saved in Saved ZIP file See
LUN XP the file
PhyPG Physical tab in the Usage statistics about parity PhyPG_dat.ZIP1 Table 3
Auto LUN XP pane groups
PhyLDEV Usage statistics about logical PhyLDEV_dat.ZIP1

volumes
PhyExG Usage conditions about PhyExG_dat.ZIP

external LU groups
PhyExLDEV Usage conditions about PhyExLDEV_dat.ZIP

external LUs
PhyProc Usage statistics about PhyProc_dat.ZIP1

channel processors, disk
processors, and data
recovery and reconstruction
processors
PhyCSW Usage statistics about access PhyCSW_dat.ZIP1
paths and write pending rate
PG LDEV tab in the Statistics about parity, PG_dat.ZIP Table 4
Auto LUN XP pane external LU, or V-VOL groups
LDEV Statistics about logical LDEV_XXXXX.ZIP2 Table 5

volumes in parity, external
LU, or V-VOL groups
Port Port-LUN tab in the Statistics about ports Port_dat.ZIP Table 6

Auto LUN XP pane
PortWWN Statistics about host bus PortWWN_dat.ZIP Table 7
adapters connected to ports
LU Statistics about LU paths LU_dat.ZIP Table 8

Table 24 Operands of the group subcommand and saved monitoring data (continued)
Operand Pane of Auto Monitoring data saved in Saved ZIP file See
LUN XP the file
PPCG WWN tab in the Statistics about SPM groups PPCG_dat.ZIP Table 9
Auto LUN XP pane
PPCGWWN Statistics about host bus PPCGWWN_dat.ZIP Table 10
adapters belonging to SPM
groups
RemoteCopy CA Monitor pane Statistics about remote copy RemoteCopy_dat.ZIP Table 11

and TCz Monitor operations by Continuous
pane Access XP and TrueCopy for
z/OS (in the whole array)
RCLU Statistics about remote copy RCLU_dat.ZIP Table 12
operations by Continuous
Access XP and TrueCopy for
z/OS (at LU paths)
RCLDEV Statistics about remote copy RCLDEV_XXXXX.ZIP3 Table 13
z/OS (at logical volumes
controlled by a particular CU)
RCCLPR Statistics about remote copy RCCLPR_dat.ZIP Table 14
z/OS (at CU)
Universal CAXJ Monitor Statistics about remote copy UniversalReplicator.ZIP Table 15
Replicator pane and URz operations by Continuous
Monitor pane Access XP Journal and
Universal Replicator for z/OS
(in the whole array)
URJNL Statistics about remote copy URJNL_dat.ZIP Table 16

Access XP Journal and
(at journal groups)
URLU Statistics about remote copy URLU_dat.ZIP Table 17

(at LU paths)
URLDEV Statistics about remote copy URLDEV_XXXXX.ZIP4 Table 18

(at logical volumes controlled
by a particular CU)
1. When specifying the PhyPG, PhyLDEV, PhyProc, or PhyCSW operand, you can select the storing period for monitoring data to
be exported from short range or long range. When specifying other operands, monitoring data in short range is exported.
2. A ZIP file whose name begins with LDEV.asdfasd.
3. A ZIP file whose name is beginning with RCLDEV_.
4. A ZIP file whose name is beginning with URLDEV_.

You can use the group subcommand more than one time in a command file. For example, you can write
the following script:
group PortWWN CL1-A:CL1-B

group PPCG spmg01:spmg02
group RemoteCopy
If an operand is used more than one time in a command file, the last operand takes effect. In the following
example, the first group subcommand does not take effect, but the second group subcommand takes
effect:

Operands
PhyPGr[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...]
Use this operand to export statistics about parity group usage rates, which appear in the Physical tab
of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is PhyPG_dat.ZIP.
For details on statistics exported by this operand, see Table 3.
You can use the Short or Long option to select the storing period of monitoring data to be exported.
If you specify Short, the exported file contains statistics in short range for up to 15 days. If you
specify Long, the exported file contains statistics in long range for up to three months (that is, up to 93
days). If neither Short nor Long is specified, statistics both in the short and long ranges are
exported.
When specifying the parity-group-id variable, you can narrow the range of parity groups whose
monitoring data is exported. parity-group-id is a parity group ID. The colon (:) indicates a
range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.
Ensure that the parity-group-id value on the left of the colon is smaller than the
parity-group-id value on the right of the colon. For example, you can specify PhyPG 1-1:1-5,
but you cannot specify PhyPG 1-5:1-1. Also, you can specify PhyPG 1-5:2-1, but you cannot
specify PhyPG 2-1:1-5.
If parity-group-id is not specified, monitoring data for all parity groups is exported.
PhyLDEVΔ[Short|Long]Δ[[parity-group-id]:[parity-group-id]][Δ...]
Use this operand to export statistics about logical volume usage rates, which appear in the Physical
tab of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is
PhyLDEV_dat.ZIP. For details on statistics exported by this operand, see Table 3.
days). If neither Short nor Long is specified, statistics both in the short and long range are exported.
When specifying the parity-group-id variable, you can narrow the range of parity groups whose
monitoring data is exported. parity-group-id is a parity group ID. The colon (:) indicates a
range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5.
Ensure that the parity-group-id value on the left of the colon is smaller than the
parity-group-id value on the right of the colon. For example, you can specify
PhyLDEV 1-1:1-5, but you cannot specify PhyLDEV 1-5:1-1. Also, you can specify
PhyLDEV 1-5:2-1, but you cannot specify PhyLDEV 2-1:1-5.
If parity-group-id is not specified, monitoring data for all logical volumes is exported.
PhyExGΔ[[exg-id]:[exg-id]][Δ...]
Use this operand to export statistics about external LU groups, which appear in the Physical tab of the
Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is PhyExG_dat.ZIP. For
details on statistics exported by this operand, see Table 3.

When specifying the exg-id variable, you can narrow the range of external LU groups whose
monitoring data are exported. exg-id is an ID of an external LU group. The colon (:) indicates a
range. For example, E1-1:E1-5 indicates external LU groups from E1-1 to E1-5.
Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of
the colon. For example, you can specify PhyExG E1-1:E1-5, but you cannot specify
PhyExG E1-5:E1-1. Also, you can specify PhyExG E1-5:E2-1, but you cannot specify
PhyExG E2-1:E1-5.
If exg-id is not specified, monitoring data for all external LU groups is exported.
PhyExLDEVΔ[[exg-id]:[exg-id]][Δ...]
Use this operand to export statistics about logical volumes in external LU groups, which appear in the
Physical tab of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is
PhyExLDEV_dat.ZIP. For details on statistics exported by this operand, see Table 3.
When specifying exg-id variable, you can narrow the range of external LU groups whose
monitoring data are exported. exg-id is an ID of an external LU group. The colon (:) indicates a
range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5.
Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of
the colon. For example, you can specify PhyExLDEV E1-1:E1-5, but you cannot specify
PhyExLDEV E1-5:E1-1. Also, you can specify PhyExLDEV E1-5:E2-1, but you cannot specify
PhyExLDEV E2-1:E1-5.
If exg-id is not specified, monitoring data for all external LUs is exported.
PhyProcΔ[Short|Long]
Use this operand to export the following statistics, which appear in the Physical tab of the Auto LUN
XP pane:
• Usage rates of channel processors
• Usage rates of disk processors
• Usage rates of DRRs (data recovery and reconstruction processors)
When statistics are exported to a ZIP file, the file name is PhyProc_dat.ZIP. For details about
statistics exported by this operand, see Table 3.
PhyCSWΔ[Short|Long]
Use this operand to export the following statistics, which appear in the Physical tab of the Auto LUN
XP pane:
• Usage rates of access paths between channel adapters and cache memories
• Usage rates of access paths between disk adapters and cache memories
• Usage rates of access paths between channel adapters and the shared memory
• Usage rates of access paths between disk adapters and the shared memory
• Usage rates of access paths between cache switches and cache memories
• Write pending rates
When statistics are exported to a ZIP file, the file name is PhyCSW_dat.ZIP. For details about statistics
exported by this operand, see Table 3.
PGΔ[[parity-group-id|V-VOL-group-id|exg-id]:
[parity-group-id|V-VOL-group-id|exg-id]][Δ...]

Use this operand to export statistics about parity, external LU, or V-VOL groups, which appear in the
LDEV tab of the Auto LUN XP pane. When statistics are exported to a ZIP file, the file name is
PG_dat.ZIP. For details about statistics exported by this operand, see Table 4.
When specifying the parity-group-id, exg-id, or V-VOL-group-id variables, you can
narrow the range of parity, external LU, or V-VOL groups whose monitoring data is exported.
parity-group-id is a parity group ID. exg-id is an ID of an external LU group.
V-VOL-group-id is a V-VOL group ID. The colon (:) indicates a range. For example, 1-1:1-5
indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to
E1-5. V1-1:V5-1 indicates V-VOL groups from V1-1 to V5-1.
Ensure that the parity-group-id, exg-id, or V-VOL-group-id value on the left of the colon is
smaller than the parity-group-id, exg-id, or V-VOL-group-id value on the right of the
colon. For example, you can specify PG 1-1:1-5, but you cannot specify PG 1-5:1-1. Also, you
can specify PG 1-5:2-1, but you cannot specify PG 2-1:1-5.
If neither of parity-group-id, exg-id, nor V-VOL-group-id is specified, monitoring data for
all parity, external LU, and V-VOL groups is exported.
LDEVΔ[[parity-group-id|V-VOL-group-id|exg-id]:
[parity-group-id|V-VOL-group-id|exg-id]][Δ...]
Use this operand to export statistics about logical volumes, which appear in the LDEV tab of the Auto
LUN XP pane. When statistics are exported to a ZIP file, multiple ZIP files with names beginning with
LDEV_ are output. For more information about statistics exported by this operand, see Table 6.
When specifying the parity-group-id, exg-id, or V-VOL-group-id variable, you can narrow
the range of parity, external LU, or V-VOL groups whose monitoring data is exported.
parity-group-id is a parity group ID. exg-id is an ID of an external LU group.
V-VOL-group-id is a V-VOL group ID. The colon (:) indicates a range. For example, 1-1:1-5
indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external LU groups from E1-1 to E1-5.
V1-1:V5-1 indicates V-VOL groups from V1-1:V5-1.
Ensure that the parity-group-id, exg-id, or V-VOL-group-id value on the left of the colon is
smaller than the parity-group-id, exg-id, or V-VOL-group-id value on the right of the colon.
For example, you can specify LDEV 1-1:1-5, but you cannot specify LDEV 1-5:1-1. Also, you
can specify LDEV 1-5:2-1, but you cannot specify LDEV 2-1:1-5.
If neither of parity-group-id, exg-id, or V-VOL-group-id is specified, monitoring data for all
logical volumes (including external LUs and V-VOL groups) is exported.
PortΔ[[port-name]:[port-name]][Δ...]
Use this operand to export port statistics, which appear in the Port-LUN tab of the Auto LUN XP pane.
When statistics are exported in a ZIP file, the file name is Port_dat.ZIP. For details about statistics
exported by this operand, see Table 6.
When specifying the port-name variable, you can narrow the range of ports whose monitoring data
is exported. port-name is a port name. The colon (:) indicates a range. For example,
CL3-a:CL3-c indicates ports from CL3-a to CL3-c.
Ensure that the port-name value on the left of the colon is smaller than the port-name value on the
right of the colon. Note that the smallest port-name value is CL1-A and the largest port-name
value is CL4-r. The following formula illustrates which value is smaller than which value:
CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r
For example, you can specify Port CL1-C:CL2-A, but you cannot specify Port CL2-A:CL1-C.
Also, you can specify Port CL3-a:CL3-c, but you cannot specify Port CL3-c:CL3-a.
If port-name is not specified, monitoring data for all ports is exported.
PortWWNΔ[[port-name]:[port-name]][Δ...]
Use this operand to export statistics about host bus adapters (WWNs) connected to ports, which
appear in the Port-LUN tab of the Auto LUN XP pane. When statistics are exported in a ZIP file, the file
name is PortWWN_dat.ZIP. For details about statistics exported by this operand, see Table 7.
When specifying the port-name variable, you can narrow the range of ports whose monitoring data
is exported. port-name is a port name. The colon (:) indicates a range. For example,
CL3-a:CL3-c indicates ports from CL3-a to CL3-c.

Ensure that the port-name value on the left of the colon is smaller than the port-name value on the
right of the colon. Note that the smallest port-name value is CL1-A and the largest port-name
value is CL4-r. The following formula illustrates which value is smaller than which value:
For example, you can specify PortWWN CL1-C:CL2-A, but you cannot specify
PortWWN CL2-A:CL1-C. Also, you can specify PortWWN CL3-a:CL3-c, but you cannot specify
PortWWN CL3-c:CL3-a.
If port-name is not specified, monitoring data for all host bus adapters is exported.
LUΔ[[port-name.host-group-id]:[port-name.host-group-id]][Δ...]
Use this operand to export statistics about LU paths, which appear in the Port-LUN tab of the Auto LUN
XP pane. When statistics are exported in a ZIP file, the file name is LU_dat.ZIP. For details about
When specifying the port-name.host-group-id variable, you can narrow the range of LU paths
whose monitoring data is exported. port-name is a port name. host-group-id is the ID of a host
group (that is, a host storage domain). The host group (host storage domain) ID must be a
hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03
indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C
port.
Ensure that the value on the left of the colon is smaller than the value on the right of the colon. Note
that the smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following
formula illustrates which port-name value is smaller than which port-name value:
For example, you can specify LU CL1-C.01:CL2-A.01, but you cannot specify
LU CL2-A.01:CL1-C.01. Also, you can specify LU CL1-C.01:CL1-C.03, but you cannot
specify LU CL1-C.03:CL1-C.01.
If port-name.host-group-id is not specified, monitoring data for all LU paths is exported.
PPCGΔ[[SPM-group-name]:[SPM-group-name]][Δ...]
Use this operand to export statistics about SPM groups, which appear in the WWN tab of the Auto
LUN XP pane. When statistics are exported in a ZIP file, the file name is PPCG_dat.ZIP. For details
about statistics exported by this operand, see Table 2.
When specifying the SPM-group-name variable, you can narrow the range of SPM groups whose
monitoring data is exported. SPM-group-name is the name of an SPM group. If the name includes
any non-alphanumeric character, the name must be enclosed by double quotation marks ("). The
colon (:) indicates a range. For example, Grp01:Grp03 indicates a range of SPM groups from
Grp01 to Grp03.
Ensure that the SPM-group-name value on the left of the colon is smaller than the SPM-group-name
value on the right of the colon. Note that numerals are smaller than letters and lowercase letters are
smaller than uppercase letters. In the following formulas, values are arranged so that smaller values
are on the left and larger values are on the right:
• 0 < 1 < 2 < …< 9 < a < b < …< z < A < B < … < Z
• cygnus < raid < Cancer < Pisces < RAID < RAID5
Regardless of whether you specify or omit SPM group names, the exported CSV files contain statistics
about host bus adapters that do not belong to any SPM groups. The exported CSV files use the
heading named Not Grouped to indicate statistics about these host bus adapters.
If SPM-group-name is not specified, monitoring data for all SPM groups is exported.
PPCGWWNΔ[[SPM-group-name]:[SPM-group-name]][Δ...]
Use this operand to export statistics about host bus adapters (WWNs) belonging to SPM groups,
which appear in the WWN tab of the Auto LUN XP pane. When statistics are exported in a ZIP file,
the file name is PPCGWWN_dat.ZIP. For details about statistics exported by this operand, see Table 10
on page 38.
When specifying the SPM-group-name variable, you can narrow the range of SPM groups whose
monitoring data is exported. SPM-group-name is the name of an SPM group. If the name includes

any non-alphanumeric character, the name must be enclosed by double quotation marks ("). The
colon (:) indicates a range. For example, Grp01:Grp03 indicates a range of SPM groups from
Grp01 to Grp03.
Ensure that the SPM-group-name value on the left of the colon is smaller than the SPM-group-name
value on the right of the colon. Note that numerals are smaller than letters and lowercase letters are
smaller than uppercase letters. In the following formulas, values are arranged so that smaller values
are on the left and larger values are on the right:
• 0 < 1 < 2 < …< 9 < a < b < …< z < A < B < … < Z
• cygnus < raid < Cancer < Pisces < RAID < RAID5
If SPM-group-name is not specified, monitoring data for all host bus adapters is exported.
RemoteCopy
Use this operand to export statistics about remote copy operations, which appear in the CA Monitor
pane and the TCz Monitor pane. By using this operand, you can export monitoring data about remote
copy operations performed by Continuous Access XP and TrueCopy for z/OS in the whole array.
When statistics are exported to a ZIP file, the file name is RemoteCopy_dat.ZIP. For details about
statistics exported by this operand, see Table 11 on page 40.
RCLUrΔ[[port-name.host-group-id]:[port-name.host-group-id]][Δ...]|
copy operations performed by Continuous Access XP and TrueCopy for z/OS at each LU path. When
statistics are exported to a ZIP file, the file name is RCLU_dat.ZIP. For details about statistics exported
by this operand, see Table 12.
whose monitoring data is exported. port-name is a port name. host-group-id is the ID of a host
group. The host group ID must be a hexadecimal numeral. The colon (:) indicates a range. For
example, CL1-C.01:CL1-C.03 indicates the range from host group #01 of the CL1-C port to host
group #03 of the CL1-C port.
that the smallest port-name value is CL1 A and the largest port-name value is CL4 r. The following
For example, you can specify RCLU CL1-C.01:CL2-A.01, but you cannot specify
RCLU CL2-A.01:CL1-C.01. Also, you can specify RCLU CL1-C.01:CL1-C.03, but you cannot
specify RCLU CL1-C.03:CL1-C.01.
If port-name.host-group-id. is not specified, monitoring data for all LU paths is exported.
RCLDEV Δ[[CU-id]:[CU-id]][Δ...]|
copy operations performed by Continuous Access XP and TrueCopy for z/OS at logical volumes
controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files with names
beginning with RCLDEV_ are output. For details about statistics exported by this operand, see
Table 13.
When specifying the CU-id variable, you can narrow the range of CUs that control the logical
volumes whose monitoring data is exported. CU-id is an ID of a CU. The colon (:) indicates a range.
For example, 00:05 indicates CUs from 00 to 05.
Ensure that the CU-id value on the left of the colon is smaller than the CU-id value on the right of the
colon. For example, you can specify RCLDEV 00:05, but you cannot specify RCLDEV 05:00.
If CU-id is not specified, monitoring data for all logical volumes is exported.
RCCLPR
Use this operand to export statistics about remote copy operations, which appear in the Continuous
Access XP pane and the TCz Monitor pane. By using this operand, you can export monitoring data
about remote copy operations performed by Continuous Access XP and TrueCopy for z/OS at each

CLPR. When statistics are exported to a ZIP file, the file name is RCCLPR_dat.ZIP. For details about
NOTE: Monitoring data is grouped by SLPR, and is exported per CLPR. If there are two SLPRs that are
SLPR0 (corresponding to CLPR0 and CLPR2) and SLPR1 (corresponding to CLPR1), those CLPRs are
arranged as follows: CLPR0,CLPR2,CLPR1.
Continuous Access XP Journal

Use this operand to export statistics about remote copy operations, which appear in the CAXJ Monitor
pane and the URz Monitor pane. By using this operand, you can export monitoring data about remote
copy operations performed by Continuous Access XP Journal and Universal Replicator for z/OS in the
whole array. When statistics are exported to a ZIP file, the file name is UniversalReplicator.ZIP.
For details about statistics exported by this operand, see Table 15.
URJNL Δ[[JNL-group-id]:[JNL-group-id]][Δ...]|
copy operations performed by Continuous Access XP Journal and Universal Replicator for z/OS at
each journal group. When statistics are exported to a ZIP file, the file name is URJNL_dat.ZIP. For
details about statistics exported by this operand, see Table 16 on page 44.
When specifying the JNL-group-id variable, you can narrow the range of journal groups whose
monitoring data is exported. JNL-group-id is a journal group number. The colon (:) indicates a
range. For example, 00:05 indicates journal groups from 00 to 05.
Ensure that the JNL-group-id value on the left of the colon is smaller than the JNL-group-id
value on the right of the colon. For example, you can specify URJNL 00:05, but you cannot specify
URJNL 05:00.
If JNL-group-id is not specified, monitoring data for all journal volumes is exported.
URLU Δ[[port-name.host-group-id]:[port-name.host-group-id]][Δ...]|
each LU path. When statistics are exported to a ZIP file, the file name is URLU_dat.ZIP. For details
about statistics exported by this operand, see Table 17.
whose monitoring data is exported. port-name. host-group-id is the ID of a host group. The
host-group-id must be a hexadecimal numeral. The colon (:) indicates a range. For example,
CL1-C.01:CL1-C.03 indicates the range from host group #01 of the CL1-C port to host group #03
of the CL1-C port.
that the smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following
For example, you can specify URLU CL1-C.01:CL2-A.01, but you cannot specify
URLU CL2-A.01:CL1-C.01. Also, you can specify URLU CL1 C.01:CL1 C.03, but you cannot
specify URLU CL1-C.03:CL1-C.01.
If port-name.host-group-id is not specified, monitoring data for all LU paths is exported.
URLDEV Δ[[CU-id]:[CU-id]][Δ...]
logical volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files
with names beginning with URLDEV_ are output. For details about statistics exported by this operand,
see Table 18.

When specifying the CU-id variable, you can narrow the range of CUs that control the logical
volumes whose monitoring data is exported. CU-id is an ID of a CU. The colon (:) indicates a range.
For example, 00:05 indicates CUs from 00 to 05.
Ensure that the CU-id value on the left of the colon is smaller than the CU-id value on the right of the
colon. For example, you can specify URLDEV 00:05, but you cannot specify URLDEV 05:00.
If CU-id is not specified, monitoring data for all logical volumes is exported.
Example
The following example exports statistics about host bus adapters and SPM groups. This example also
exports statistics in the Physical tab of the Auto LUN XP pane:
group PortWWN
group PPCG
group Physical
The following example exports statistics about three ports (CL1-A, CL1-B, and CL1-C):
group Port CL1-A:CL1-C
The following example exports statistics about six ports (CL1-A to CL1-C, and CL2-A to CL2-C)
group Port CL1-A:CL1-C CL2-A:CL2-C
The following example exports statistics about the parity group 1-3:
group PG 1-3:1-3
The following example exports statistics about the parity group 1-3 and other parity groups whose ID is
larger than 1-3 (for example, 1-4 and 1-5):
group PG 1-3:
The following example exports statistics about the external LU groups E1-1 to E1-5:
group PG E1-1:E1-5
The following example exports statistics about the parity group 1-3 and other parity groups whose ID is
smaller than 1-3 (for example, 1-1 and 1-2):
group LDEV :1-3
The following example exports statistics about LU paths for the host group (host storage domain) ID 01 for
the port CL1-A:
group LU CL1-A.01:CL1-A.01
The shortrange subcommand

Syntax
shortrangeΔ[[yyyyMMddhhmm][{+|-}hhmm]:[yyyyMMddhhmm][{+|-}hhmm]]
Description
The shortrange subcommand specifies the term of monitoring data exported into files. Use this
subcommand to narrow the export-target term within the stored data.
The shortrange subcommand is valid for monitoring data in short range. The monitoring data in short
range is the contents appears in the following panes:
• The Auto LUN XP pane when selecting shortrange as the storing period

• The CA Monitor and TCz Monitor panes
• The CA Journal Monitor and URz Monitor panes
All monitoring items are stored in short range. Therefore, you can use the shortrange subcommand
whichever operand you specify to the group subcommand. If you run the Export Tool without specifying
the shortrange subcommand, data stored in the whole monitoring term is exported.
The login subcommand must execute before the shortrange subcommand executes.
Operands
The value on the left of the colon (:) specifies the starting time of the period. The value on the right of the
colon specifies the ending time of the period. Specify the term within “Short Range From XXX To
XXX” which is output by the show subcommand.
If no value is specified on the left of the colon, the starting time for collecting monitoring data is assumed.
If no value is specified on the right of the colon, the ending time for collecting monitoring data is assumed.
The starting and ending times for collecting monitoring data appear in the Monitoring Term area in the
Auto LUN XP pane (see Figure 27).
Figure 27 Starting and ending times for collecting monitoring data

yyyyMMddhhmm
yyyyMMdd indicates the year, month, and day. hhmm indicates the hour and minute.
If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is
assumed. If yyyyMMddhhmm is omitted on the right of the colon, the ending time for collecting
monitoring data is assumed.
+hhmm
Adds time (hhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,
200401230000+0130 indicates Jan. 23, 2004, 01:30.
Adds time to the starting time for collecting monitoring data if yyyyMMddhhmm is omitted.
-hhmm
Subtracts time (hhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,
200401230000-0130 indicates Jan. 22, 2004, 22:30.
Subtracts time from the ending time for collecting monitoring data, if yyyyMMddhhmm is omitted.
NOTE: If the last two digits of the time on the left or right of the colon (:) are not a multiple of the
sampling interval, the time automatically changes so the last two digits are a multiple of the sampling
interval. If this change occurs to the time on the left of the colon, the time is smaller than the original time.
If this change occurs to the time on the right of the colon, the time is larger than the original time. The
following are examples:
• If the time on the left is 10:15, the time on the right is 20:30, and the sampling interval is 10 minutes:
The time on the left changes to 10:10 because the last two digits of the time are not a multiple of 10
minutes. The time on the right remains unchanged because the last two digits of the time are a multiple
of 10 minutes.

• If the time on the left is 10:15, the time on the right is 20:30, and the sampling interval is 7 minutes:
The time on the left changes to 10:14 because the last two digits of the time are not a multiple of 7
minutes. The time on the right changes to 20:35 because of the same reason.
Example
The following examples assume that:
• Starting time for collecting monitoring data is Jan. 1, 2004, 00:00
• Ending time for collecting monitoring data is Jan. 2, 2004, 00:00
shortrange 200401010930:200401011730
The Export Tool saves monitoring data within the range of Jan. 1, 9:30-17:30.
shortrange 200401010930:
The Export Tool saves monitoring data within the range of Jan. 1, 9:30 to Jan. 2, 00:00.
shortrange :200401011730
shortrange +0001:
shortrange -0001:
shortrange :+0001
shortrange :-0001
shortrange +0101:-0101
shortrange 200401010900+0130:200401011700-0130
shortrange 200401010900-0130:200401011700+0130
shortrange 200401010900-0130:

The longrange subcommand
Syntax
longrangeΔ[[yyyyMMddhhmm][{+|-}ddhhmm]:[yyyyMMddhhmm][{+|-}ddhhmm]]
Description
The longrange subcommand specifies a term of monitoring data to be exported into files. Use this
subcommand to narrow the export-target term within the stored data.
The longrange subcommand is valid for monitoring data in long range. Monitoring data in long range
is the contents displayed in the Physical tab of the Auto LUN XP pane with selecting longrange as the
storing period. Monitoring items whose data can be stored in long range are limited. Table 25 shows
monitoring items to which the longrange subcommand can be applied, and also shows operands to
export those monitoring items.
Table 25 Monitoring items to which the longrange subcommand can be applied
Monitoring data Operands of the group subcommand

Usage statistics about parity groups PhyPG Long
Usage statistics about logical volumes PhyLDEV Long
Usage statistics about channel processors, disk processors, and data PhyProc Long
recovery and reconstruction processors
Usage statistics about access paths and write pending rate PhyCSW Long
If you run the Export Tool without specifying the longrange subcommand, data stored in the whole
monitoring term is exported.
The login subcommand must execute before the longrange subcommand executes.
Operands
The value on the left of the colon (:) specifies the starting time period. The value on the right of the colon
specifies the ending time period. Specify the term within Long Range From XXX To XXX which is
output by the show subcommand.
If no value is specified on the left of the colon, the starting time for collecting monitoring data is assumed.
If no value is specified on the right of the colon, the ending time for collecting monitoring data is assumed.
The starting and ending times for collecting monitoring data appear in the Monitoring Term area in the
Auto LUN XP pane (see Figure 28).
Figure 28 Starting and ending time for collecting monitoring data

yyyyMMddhhmm
yyyyMMdd indicates the year, month, and day. hhmm indicates the hour and minute.
If yyyyMMddhhmm is omitted on the left of the colon, the starting time for collecting monitoring data is
assumed. If yyyyMMddhhmm is omitted on the right of the colon, the ending time for collecting
monitoring data is assumed.
+ddhhmm

Adds time (ddhhmm) to yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,
200401120000+010130 indicates Jan. 13, 2004, 01:30.
Adds time to the starting time for collecting monitoring data if yyyyMMddhhmm is omitted.
-ddhhmm
Subtracts time (ddhhmm) from yyyyMMddhhmm if yyyyMMddhhmm is specified. For example,
200401120000-010130 indicates Jan. 10, 2004, 22:30.
Subtracts time from the ending time for collecting monitoring data if yyyyMMddhhmm is omitted.
NOTE: Ensure that mm is 00, 15, 30, or 45. If you do not specify mm in this way, the value on the left of
the colon (:) is rounded down to one of the four values. Also, the value on the right of the colon is
rounded up to one of the four values. For example, if you specify 200401010013:200401010048, the
specified value is regarded as 200401010015:200401010100.
Example
The following examples assume:
• Starting time for collecting monitoring data is Jan. 1, 2004, 00:00
• Ending time for collecting monitoring data is Jan. 2, 2004, 00:00
longrange 200401010930:200401011730
longrange 200401010930:
longrange :200401011730
longrange +000015:
longrange -000015:
longrange :+000015
longrange :-000015
longrange +000115:-000115
longrange 200401010900+000130:200401011700-000130
longrange 200401010900-000130:200401011700+000130

longrange 200401010900-000130:
The outpath subcommand

Syntax
outpathΔ[path]
Description
The outpath subcommand specifies the directory to which monitoring data is exported.
Operands
path
Specifies the directory in which files are saved.
If the directory includes any non-alphanumeric character, the directory must be enclosed by double
quotation marks ("). To specify a back slash (\) in the character string enclosed by double quotation
marks, repeat the back slash twice (\\).
If the specified directory does not exist, this subcommand creates a directory that has the specified
name.
If this operand is omitted, the current directory is assumed.
Example
The following example saves files in the directory C:\Project\out in a Windows computer:
outpath "C:\\Project\\out"
The following example saves files in the out directory in the current directory:
outpath out
The option subcommand

Syntax
optionΔ[compress|nocompress]Δ[ask|clear|noclear]
Description
The option subcommand specifies the following:
• Whether to compress monitoring data in ZIP files
• Whether to overwrite or delete existing files and directories when saving monitoring data in files
Operands
The following operands specify whether to compress CSV files into ZIP files. If none of these operands is
specified, compress is assumed:
compress
Compresses data in ZIP files. To extract CSV files out of a ZIP file, you must decompress the ZIP file.
nocompress
Does not compress data in ZIP files and saves data in CSV files.
The following operands specify whether to overwrite or delete an existing file or directory when the Export
Tool saves files. If none of these operands is specified, ask is assumed:
ask

Displays a message asking whether to delete existing files or directories.
clear
Deletes existing files and directories, and saves monitoring data in files.
noclear
Overwrites existing files and directories.
Example
The following example saves monitoring data in CSV files, not in ZIP files:
option nocompress
The apply subcommand

Syntax
apply
Description
The apply subcommand saves monitoring data specified by the group subcommand into files.
The login subcommand must execute before the apply subcommand executes.
The apply subcommand does nothing if the group subcommand executes.
Settings made by the group subcommand are reset when the apply subcommand finishes.
The set subcommand

Syntax
setΔ[switch={m|off}]
Description
The set subcommand starts or ends monitoring the array (that is, starts or ends collecting performance
statistics). The set subcommand also specifies the gathering interval (interval of collecting statistics) in
short range monitoring.
To use the set subcommand, you must use the login subcommand (see ”The login subcommand” on
page 57) to log onto the SVP. Ensure that the set subcommand executes immediately before the Export
Tool finishes.
Executing the set subcommand generates an error in the following conditions:
• Some other user is being logged onto the SVP in Modify mode
• Maintenance operations are being performed at the SVP
If an error occurs, do the following:
• Ensure that all users logged onto the SVP are not in Modify mode. If any user is logged on in Modify
mode, ask the user to switch to View mode.
• Wait until maintenance operations finish at the SVP, so the set subcommand can execute.
NOTE:
• The batch files can include script that execute when an error occurs. For information about writing
such a script in the batch file, see ”Notes” on page 52.
• When the set subcommand starts or ends the monitoring or changes the gathering interval after the
Auto LUN XP pane is started, the contents displayed in the Auto LUN XP pane does not automatically
change with the set subcommand operation. To display the current monitoring status in the Auto LUN
XP pane, click the Refresh button.

Operands
switch={m|off}
To start monitoring, specify the gathering interval (interval of collecting statistics) of monitoring data at
m. Specify a value between 1 and 15 minutes. m is the gathering interval in short range monitoring by
Auto LUN XP. Note that the gathering interval in long range is fixed to 15 minutes.
To end monitoring, specify off.
If this operand is omitted, the set subcommand does not make settings for starting or ending
monitoring.
Example
The following command file saves port statistics, and ends monitoring ports:
svpip 158.214.135.57
login expusr passwd
show
group Port
shortrange 200404010850:200404010910
apply
set switch=off
The following command file starts monitoring remote copy operations. The sampling time interval is 10
minutes.
svpip 158.214.135.57
login expusr passwd
set switch=10
The help subcommand

Syntax
help
Description
The help subcommand displays the online Help for subcommands.
To view the online Help, HP recommends creating a batch file and command file that are exclusively used
for displaying online Help. For detailed information, see the following example.
Example
In this example, a command file (cmdHelp.txt) and batch file (runHelp.bat) are created in the
C:\export directory in a Windows computer:
• Command file (c:\export\cmdHelp.txt):
help
• Batch file (c:\export\runHelp.bat):

-Dmd.command=cmdHelp.txt -Dmd.logpath=log sanproject.getmondat.RJMdMain ↵
pause ↵
NOTE: The ↵ symbol in this batch file example indicates the end of a command line.
In this example, you must do either of the following to view the online Help:
• Double-click runHelp.bat.

• Go to the c:\export directory at the command prompt, enter runHelp or runHelp.bat and
press Enter.
The java command for exporting data In files

Syntax
javaΔ-classpathΔclass-pathΔproperty-parametersΔsanproject.getmondat.
RJMdMain
Description
This java command starts the Export Tool.
To start the Export Tool, you must write this java command in the batch file, and run the batch file.
Operands
class-path
Specifies the path to the Export Tool’s class file.
The path must be enclosed in double quotation marks (").
property-parameters
You can specify the following parameters. At least you must specify -Dmd.command.
• -Dhttp.proxyHost=host-name-of-proxy-host, or
-Dhttp.proxyHost=IP-address-of-proxy-host
Specifies the proxy host’s host name or IP address. You must specify this parameter if the computer
that runs the Export Tool communicates with the SVP via a proxy host.
• -Dhttp.proxyPort=port-number-of-proxy-host
Specifies the proxy host’s port number. You must specify this parameter if the computer that runs
the Export Tool communicates with the SVP via a proxy host.
• -Dmd.command=path-to-command-file
Specifies the path to the command file.
• -Dmd.logpath=path-to-log-file
Specifies the path to log files. A log file is created whenever the Export Tool executes.
If this parameter is omitted, log files are saved in the current directory.
• -Dmd.logfile=name-of-log-file
Specifies the name of the log file.
If this parameter is omitted, log files are named exportMMddHHmmss.log. MMddHHmmss indicates
when the Export Tool executed. For example, the log file export0101091010.log contains log
information about Export Tool execution at Jan. 1, 09:10:10.
Example
The following example assumes that the computer running the Export Tool communicates with the SVP via
a proxy host. In this example, the proxy host’s host name is Jupiter, and the proxy host’s port name is
8080.

In the following example, a log file named export.log is created in the log directory below the current
directory when the Export Tool executes.

-Dmd.command=command.txt -Dmd.logfile=export.log -Dmd.logpath=log
sanproject.getmondat.RJMdMain ↵

Troubleshooting the Export Tool

Table 26 explains possible problems with the Export Tool and probable solutions to the problems.
Table 26 Troubleshooting the Export Tool
Possible problem Probable cause and recommended action

You cannot run the batch file. • The path to the Java Virtual Machine (java.exe)
might not be defined in the PATH environment
variable. If this is true, you must add that path to the
PATH environment variable. For information about
adding a path to the environment variable, see the
operating system’s documentation.
• An incorrect version of Java Runtime Environment
(JRE) might be installed on your computer. To check
the JRE version, enter the following command at the
Windows command prompt or the UNIX console
window:
java -version
If the version is incorrect, install the correct version
of JRE.
The Export Tool stops and processing does not continue. The command prompt window might be in pause mode.
The command prompt window was displaying the The command prompt window is in pause mode if you
export processing progress, but the window stopped click the command prompt window when the Export
displaying the progress before processing stopped. The Tool is running.
progress information does not seem to be updated To cancel pause mode, you must activate the command
anymore. prompt window, and press ESC.
If a timeout of RMI occurs during pause mode, the login
is canceled and an error occurs when you cancel pause
mode after the timeout. The error message ID is
(0001, 4011).
An error occurs and processing stops. If the error message ID is (0001 4011), the user is
forcibly logged off and processing stops because the
Export Tool did not issue any request to the SVP. The
computer running the Export Tool could be slow.
Confirm whether you are using a computer that is not
supported, or whether the computer is slow. Run the
Export Tool again. If the error persists, contact your
HP account support representative.
If the error message ID is (0002, 5510), probable
error causes and solutions are:
• An internal process is being performed in the array.
Alternatively, another user is changing
configurations. Wait for a while, and run the Export
Tool again.
• Maintenance operations are being performed on
the array. Wait until the maintenance operations
finish, and run the Export Tool again.
If the error message ID is none of the above, see
Table 27.

Table 26 Troubleshooting the Export Tool (continued)
Possible problem Probable cause and recommended action

Monitoring data in the CSV file includes "-1". The value "-1" indicates that Auto LUN XP failed to
obtain monitoring data for some reasons. Probable
reasons are:
• Auto LUN XP attempted to obtain statistics when an
operation for rebooting the array is in progress.
• A heavy workload is imposed on the array.
The Check License row in the log file says The Export Tool terminated abnormally due to an error.
UnmarshalException. The versions of the DKCMAIN/SVP program and the
export tool are not compatible. Verify that you are using
the correct versions.
If an error occurs when running the Export Tool, error messages are issued to the standard output (for
example, the command prompt) and the log file. Table 27 lists the Export Tool messages and
recommended actions against errors.
Table 27 Messages to be issued by the Export Tool
Possible problems Probable causes and recommended action

Connection to the server has not been established. Connection to the server has not been established. Use
the login subcommand.
Execution stops. Execution stops.Remove errors.
Illegal character: "character" An illegal character is used. Use legal characters.
Invalid length: token The length is invalid. Specify a value that has a correct
length.
Invalid range: range The specified range is invalid. Specify the correct range.
Invalid value: "value" The specified value is invalid. Specify a correct value.
Login failed An attempt to log into the SVP failed. Probable causes
are:
1. An incorrect operand is used for the svpip
subcommand.
2. An incorrect operand is used for the login
subcommand.
3. The specified user ID is used by another person, and
the person is being logged in.
4. Two users are currently displaying the Auto LUN XP
pane.
5. Two users are currently executing the Export Tool.
NOTE: If the error cause is 4 or 5 above, do either of

the following:
• Ask one of the users to display another pane.
• Ask one of the users to log off.
• Wait for one of the users to quit the Export Tool.
Missing command file The command file is not specified. Specify the name of
the command file correctly.
Missing group name No operand is specified in the group subcommand.

Specify operands for the subcommand.
Missing host name No host name is specified. Please specify a host name.

Table 27 Messages to be issued by the Export Tool (continued)

Missing output directory No directory is specified for saving files. Specify the
directory for saving files.
Missing password The Export Tool cannot find the user ID, which is used to
log into the SVP. Specify the password.
Missing svpip The svpip subcommand is not used. Use the svpip
command.
Missing time range Specify the time range.
Missing user ID The Export Tool cannot find the user ID, which is used to
log into the SVP. Specify the user ID.
Out of range: range The value is outside the range.

If the shortrange subcommand or the longrange
subcommand is used, specify a value within the range
from the monitoring start time to the monitoring end
time.
If the set subcommand is used with the switch
operand, specify a value within the range of 1 to 15.
Permission Denied. The user ID does not have the required permission.
The user ID must have at least one of the permissions for
Auto LUN XP, TrueCopy for z/OS, Continuous Access XP
Journal, and Universal Replicator for z/OS.
RMI server error (part-code, error-number) An error occurs at the RMI server. For detailed
information, contact your HP account support
representative.
Unable to display help message The Export Tool cannot display the online Help due to a
system error.
Unable to get serial number The Export Tool cannot obtain the serial number due to
a system error.
Unable to get time range for monitoring The SVP does not contain monitoring data.
Unable to read command file: file The Export Tool cannot read the command file. Specify
the name of the command file correctly.
Unable to use the command: command The specified subcommand is unavailable because you
logged in as a storage partition administrator.
Unable to use the group name: operand The specified subcommand of the group subcommand
is unavailable because you logged in as a storage
partition administrator.
Unknown host: host The Export Tool cannot resolve the host name. Specify
the correct host name.
Unsupported command: command The Export Tool does not support the specified
command. Specify a correct command.
Unsupported operand: operand The specified operand is not supported.Correct the

specified operand.
Unsupported option: option The specified option is not supported. Correct the
specified option.

Table 27 Messages to be issued by the Export Tool (continued)

Some file exists in path. Files exist in path.
What do you do? clear(c)/update(u)/stop(p)
• To clear the files, press the c key.
You selected “action”. Is it OK? (y/n)
• To overwrite the files, press the u key.
• To stop the operation, press the p key.
When pressing a key, a message appears and asks
whether to perform the specified action.
• To perform the specified action, press the y key.
• To cancel the specified action, press the n key.
Specify the following subcommand before login The retry subcommand is written in an incorrect
subcommand: retry position in the command file.
Write the retry subcommand before the login
subcommand.
Start gathering group data The Export Tool starts collecting data specified by the
Target = xxx, Total = yyy group subcommand.
End gathering group data
The number of targets is xxx and the total number is
yyy (see Note below).
The Export Tool ends collecting data.
NOTE: For example, suppose the array contains 100

parity groups and the command file contains the
following command line:
group PG 1-1:1-2
The Export Tool displays the message "Target=2,
Total=100", which means the group subcommand
specifies two parity groups and the total number of
parity groups in the array is 100.
Syntax error: "line" A syntax error is detected in a command line in the

command file. Check the command line for the syntax
error, and correct the script.
Note that some operands must be enclosed by double
quotation marks ("). Check the command line to find
whether double quotation marks are missing.

B Limitations for storage partition administrators
If the user type of your user ID is storage partition administrator, you can use only Auto LUN XP and the
Export Tool from the Auto LUN XP programs. In this case, you cannot use Auto LUN XP or Performance
Control XP.
Also, when logging in as a storage partition administrator, the available functions of Auto LUN XP and the
Export Tool are limited. This appendix explains these limitations of Auto LUN XP and the Export Tool.
Limitations of Auto LUN XP

The Auto LUN XP functions that are limited when you logged in as a storage partition administrator are
shown in Table 28. For the Auto LUN XP pane displayed when logging in as a storage partition
administrator, see Figure 29.
Table 28 Limitations for storage partition administrators (Auto LUN XP)
Pane Limited function

Physical tab in the Auto LUN XP pane • The tree and list display only information in the SLPR (storage
management logical partition) allocated to the user ID.
• The Auto LUN XP button is not displayed (see Figure 29). Therefore,
the user cannot start Auto LUN XP.
LDEV tab in the Auto LUN XP pane The tree and list display only information in the SLPR allocated to the user
ID.
Port-LUN tab in the Auto LUN XP pane • The tree and list display only information in the SLPR allocated to the
user ID.
• The SPM button is not displayed (see Figure 29). Therefore, the user
cannot start Performance Control XP.
WWN tab in the Auto LUN XP pane The WWN tab is not displayed (see Figure 29). The user cannot view
traffics between host bus adapters and ports.
CA Monitor pane These panes are not displayed (see Figure 29). The user cannot view
TCz Monitor pane information about remote copy operations performed by Continuous
CA Journal Monitor pane Access XP, TrueCopy for z/OS, Continuous Access XP Journal, and
URz Monitor pane Universal Replicator for z/OS.
Monitoring Options pane The Monitoring Options pane is not displayed (see Figure 29). The user
cannot start or stop monitoring, or change the gathering interval.

Figure 29 An example of a text file
Limitations of the Export Tool

The following Export Tool functions are limited when logging in as a storage partition administrator:
• Only monitoring data about the SLPR allocated to the user ID can be exported into files.
• When a storage partition administrator uses the group subcommand with specifying the PPCG or
PPCGWWN operand to export monitoring data about SPM groups or host bus adapters belonging to
these SPM groups, an error occurs in the following conditions:
• One SPM group contains multiple host bus adapters that are allocated to different SLPRs.
• One host bus adapter is connected to multiple ports that exist in different SLPRs.
• Monitoring data about remote copy operations performed by Continuous Access XP, TrueCopy for
z/OS, Continuous Access XP Journal, and Universal Replicator for z/OS (see Table 11 to Table 18)
cannot be exported.
• A storage partition administrator cannot use the set subcommand to start or stop monitoring, or
change the gathering interval.
82 Limitations for storage partition administrators

Index
A outpath subcommand 72
apply subcommand 73 retry subcommand 56
audience, documentation 7 running 51
Auto LUN XP 31, 32, 81 semicolons 47
set subcommand 73
B shortrange subcommand 67
show subcommand 57
batch files
svpip subcommand 56
preparing 49
syntax 54
running 51
system requirements 45
syntax 54
termination codes 53
troubleshooting 76
time required 52
troubleshooting 76
C
user IDs 46
command files, preparing 47 ZIP files 32
commands, Export Tool external volume statistics 35
54 extracting ZIP files 32
comma-separated value files 32
comments, inserting 47 F
Continuous Access XP 31, 40
feedback, documentation 9
Continuous Access XP Journal 31
firmware, supported 7
conventions
document 8
G
text symbols 8
CSV files 32 group subcommand 58
customer support 8
H
D HBAs
deleting PFC groups 28 grouping 26
development servers 11 many-to-many port connections 13
document one-to-one port connections 12
conventions 8 PFC names 25
feedback 9 prioritizing PFC groups 27
prerequisites 7 replacing 26
related documentation 7 SPM group statistics 38
statistics 37
E traffic management 22
traffic statistics 24
errors, Export Tool 52, 76
upper limit values 27
Export Tool
help subcommand 74
about 31
help, obtaining 8, 9
apply subcommand 73
host bus adapters (HBAs)
batch files 49
grouping 26
command files, preparing 47
many-to-many port connections 13
commands 54
one-to-one port connections 12
errors 52, 76
PFC names 25
group subcommand 58
prioritizing PFC groups 27
help subcommand 74
replacing 26
installing on UNIX 47
SPM group statistics 38
installing on Windows 46
statistics 37
java command for exporting data 75
traffic management 22
limitations 81, 82
login subcommand 57
longrange subcommand 70
option subcommand 72

HP prerequisites 7
storage web site 9 prioritized port 12
Subscriber’s Choice for Business web site 9 prioritized WWN 15
technical support 8 production servers 11
I R
I/O rate 12, 16 related documentation 7
installing Export Tool remote copy operations statistics 40
UNIX 47 requirements, Export Tool 45
Windows 46 resource usage statistics 33
restrictions 17
J retry subcommand 56
java command for exporting data in files 75
S
L semicolons 47
limitations 81 servers, production and development 11
logical volumes, statistics 36 set subcommand 73
login subcommand 57 shortrange subcommand 67
longrange subcommand 70 show subcommand 57
LU path statistics 38 SPM group statistics 38
spreadsheets, exporting to 31
M starting Performance Control 19
monitoring data. See statistics statistics
Auto LUN XP 32
N exporting 31
external volume 35
non-prioritized port 12, 15
host bus adapters (HBAs) 37, 38
logical volumes 36
O
LU paths 38
option subcommand 72 parity 35
outpath subcommand 72 ports 37
remote copy operations 40
P resource usage 33
parity statistics 35 SPM groups 38
partition administrators 81, 82 traffic 24
Performance Control pane 19 Universal Replicator for z/OS 43
PFC groups V-VOL groups statistics 35
adding HBAs 26 write pending rates 33
deleting 28
prioritizing 27
renaming 28
PFC names 25
Port tab, Performance Control pane 19
ports
many-to-many HBA connections 13
one-to-one HBA connections 12
statistics 37
threshold control 25
84
storage partition administrators 81, 82
storage platforms, supported 7
Subscriber’s Choice for Business, HP 9
supported storage platforms and firmware 7
svpip subcommand 56
symbols in text 8
syntax, command 54
system requirements, Export Tool 45
T
technical support, HP 8
termination codes, Export Tool 53
text files, exporting to 31
text symbols 8
threshold control 11, 25
time required for exporting files 52
transfer rate 12, 16
troubleshooting
Export Tool 76
Performance Control XP 29
TrueCopy for z/OS 31, 40
U
Universal Replicator for z/OS 31, 43
UNIX, installing Export Tool 47
upper limit control 11
user IDs
creating 46
limitations 81, 82
V
V-VOL groups statistics 35
W
web sites
HP documentation 9
HP storage 9
HP Subscriber’s Choice for Business 9
Windows, installing Export Tool 46
write pending rates 33
WWN tab, Performance Control pane 20
WWNs
threshold control 25
Z
ZIP-format files 32

86

HP - PerformanceControlUG Rootsan Technologies PVT LTD

Uploaded by

Document Information

Original Description:

Original Title

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

HP - PerformanceControlUG Rootsan Technologies PVT LTD

Uploaded by

Copyright:

Available Formats

HP StorageWorks

Performance Control XP user guide

Part number: T1605-96005

Performance Control XP user guide

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Performance Control XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Using Performance Control XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 Troubleshooting Auto LUN/Performance Control Base Monitor and Performance

Performance Control XP user guide 3

B Limitations for storage partition administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Performance Control XP user guide 5

Supported storage platforms and firmware

Performance Control XP user guide 7

Document conventions and symbols

Blue, underlined text: (http://www.hp.com) Web site addresses

Bold text • Keys that are pressed

Italic text Text emphasis

Monospace text • File and directory names

Monospace, bold text Emphasized monospace text

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

Performance Control XP user guide 9

Optimal performance of high-priority hosts

Automatically disabling upper limit control

Overview of Performance Control XP procedures

Performance Control XP user guide 11

Figure 1 Network A (one-to-one connections between HBAs and ports)

Figure 2 Priority specified in the Performance Control pane

Figure 3 Traffic at ports on network A

Procedure for many-to-many connections between HBAs and ports

Performance Control XP user guide 13

Figure 4 Network B (many-to-many connections between HBAs and ports)

Figure 5 Specifying host bus adapters to be monitored

Figure 6 Priority specified in the Performance Control pane

Figure 7 Traffic at ports on network B

Performance Control XP user guide 15

Figure 8 Setting upper limits

Notes on using Performance Control XP

Graph 1: Actual I/O rate (measured every second)

Graph 2: I/O rate displayed in Performance Control XP (with Detail option)

Graph 3: I/O rate displayed in Performance Control XP (without Detail option)

Performance Control XP restrictions

Performance Control XP user guide 17

Performance Control pane

Figure 10 Port tab in the Performance Control pane

Performance Control XP user guide 19

Figure 11 WWN tab in the Performance Control pane

20 Using Performance Control XP

Performance Control XP user guide 21

NOTE: The pane displays a hyphen (-) instead of 0 (zero).

Managing traffic between HBAs and ports

Setting the priority of ports on arrays

22 Using Performance Control XP

Figure 12 Add WWN dialog box

Performance Control XP user guide 23

Analyzing traffic statistics

Setting upper limit values for traffic at non-prioritized ports or WWNs

24 Using Performance Control XP

Changing PFC names of host bus adapters (many-to-many connections only)

Performance Control XP user guide 25

Figure 13 Change WWN and PFC Name dialog box