tsm solutions by ibm

TSM Solutions for mySAP

TM

© 2008 IBM Corporation

FlashCopy SolutionsformySAPTM Environments

TSM for ACS Workshop

Tivoli Software

October 2008 | Andreas Uhl, Enterprise Solution Development

Date ____________________________ Workshop Location ____________________________ Instructors ____________________________ ____________________________

Participant Handbook Course Version: 1.1 October 2008 Course Duration: 3 Day(s)

Unit 1: Overview TSM for ACS TSM for ACS Workshop

2 © 2008 IBM. All rights reserved October 2008


© 2008 IBM. All rights reserved iii

Contents

WORKSHOP OVERVIEW V Workshop Goals vi Workshop Objectives vi

SECTION 1: PRODUCT OVERVIEW - TSM FOR ACS 1

Unit 1 Overview TSM for ACS................................................................. 3 Unit Objectives 3

SECTION 2: PRODUCT INTERNALS - TSM FOR ACS 13

Unit 2 Implementation / Configuration................................................. 15 Unit Objectives 15 Product Overview 15 Prerequisites for TSM for ACS for mySAP 17 Configuration of TSM for ACS for mySAP 23 Installation / Configuration of TSM for ACS for mySAP 27

Unit 3 Configuration DS Open API CIM Agent.................................... 41 Unit Objectives 41 CIM Agent configuration overview 41 ESS/DS User Setup 45 ESS/DS CIM Agent configuration 46 CIM Agent Setup - CIM Agent 5.1.0.x 47 CIM Agent User Setup - CIM Agent 5.1.0.x 50 CIM Agent ESS/DS configuration – CIM Agent 5.1.0.x 51 CIM Agent Setup - CIM Agent 5.2.x – 5.4.x 52 CIM Agent User Setup - CIM Agent 5.2.x – 5.4.x 56 CIM Agent ESS/DS configuration – CIM Agent 5.2.x – 5.4.x 56

Unit 4 User Interface.............................................................................. 57 Unit Objectives 57 User Interface 57

Unit 5 FlashCopy Backup...................................................................... 63 Unit Objectives 63 FlashCopy Backup 63

Unit 6 FlashCopy Restore ..................................................................... 67 Unit Objectives 67 FlashBack Restore 67

Unit 7 Backup and Restore Cycle......................................................... 71 Unit Objectives 71 Backup Cycle 71 Restore Cycle 75



Backup and Restore Cycle 76 FlashCopy Agent 77

SECTION 3: TROUBLESHOOTING - TSM FOR ACS 79

Unit 8 Troubleshooting.......................................................................... 81 Unit Objectives 81 Problem Isolation Flow 82 Log- and Trace-Files 84 Troubleshoot the Phases of FlashCopy Backup 85

Unit 9 Troubleshooting TSM for ACS with DS Open API CIM Agent119 Unit Objectives 119 Problem Isolation Flow 120 DS Open API CIM Agent 5.1.0.x log files 120 DS Open API CIM Agent 5.2.1.x - 5.4.0.x log files 122 Troubleshoot the Phases of FlashCopy Backup 127

Unit 10 Appendix: CIM Agent 5.1.0.x NIResult Codes ...................... 145

Unit 11 Appendix: CIM Agent 5.4.0.x Return Codes ...................... 153


© 2008 IBM. All rights reserved v

Workshop Overview Workshop Overview

Section 1

Product Overview – TSM for ACS Day 1

Unit 1 Overview TSM for ACS

Section 2

Product Internals – TSM for ACS Day 1

Unit 1 Implementation / Configuration TSM for ACS with DS Open API CIM Agent

Unit 2 Configuration of DS Open API CIM Agent

Unit 3 User Interface

Unit 4 FlashCopy Backup

Table 1: Workshop Overview – Day 1

Section 2

Product Internals – TSM for ACS Day 2

Unit 1 FlashCopy Restore

Unit 2 Backup / Restore Cycle

Section 3

Troubleshooting – TSM for ACS Day 2

Unit 1 Troubleshooting TSM for ACS




Section 3

Troubleshooting – TSM for ACS Day 3

Unit 1 Troubleshooting TSM for ACS with DS Open API CIM Agent


Target Audience

This Workshop is intended for the following audiences: • SAP Administrators • DB2 Administrators • TSM Administrators • Operating System Administrators • Storage Administrators • Operators

Workshop Prerequisites

Required Knowledge

• Basic SAP Basis Technology knowledge • Basic DB2 knowledge • Basic TSM knowledge • Basic AIX knowledge • Basic Storage knowledge (ESS 800 / DS 8000)

Recommended Knowledge

Experience in administering SAP systems on DB2 UDB on AIX

Workshop Goals

This workshop will prepare you to: • Perform advanced administrative tasks that affect the TSM for ACS technical

infrastructure, configuration, operation and troubleshooting.

Workshop Objectives

After completing this workshop, you will be able to: • Install and Configure TSM for ACS • Run FlashCopy Backups/Restores of SAP DB2 V9 databases with TSM for

ACS • Monitor FlashCopy Backups/Restores • Troubleshoot FlashCopy Backups/Restores

TSM for ACS Workshop Workshop Objectives

October 2008 © 2008 IBM. All rights reserved 1

Section 1: Product Overview - TSM for ACS

TSM for ACS Workshop Unit Objectives


Unit 1

Overview TSM for ACS

Unit Objectives

After completing this unit, you will be able to:

• Describe the basic concepts for TSM for ACS The previous release of this product was entitled Tivoli® Storage Manager for Hardware: Data Protection for FlashCopy Devices. With version 5.4.0, the product name has been changed to Tivoli Storage Manager for Advanced Copy Services to employ Data Protection for Snapshot Devices (abbreviated as DP for Snapshot Devices) as a generic term that covers the following components offered for V5.4:

• Data Protection for FlashCopy Devices for mySAP • Data Protection for N Series Snapshot for mySAP

In the following Tivoli Storage Manager for Advanced Copy Services – Data Protection for Snapshot Devices for mySAP will be abbreviated with TSM for ACS for mySAP, TSM ACS mySAP or even TSM ACS.



The following pages are taken from an standard sales and marketing presentation for TSM ACS.

Tivoli Software

FlashCopy Solutions for mySAPTM Environments | TSM for ACS Workshop © 2008 IBM Corporation

Agenda

� Market Forces and FlashCopy Solutions Concepts

– Storage Management Business Challenges

– SAP Infrastructure Trends

– Virtualization requires flexible processes

– Comparison of Traditional Tape vs FlashCopy Backup/Restore

� FlashCopy Solutions Highlights� Outstanding FlashCopy Support with DB2 9.5

Tivoli Software


Increasing Complexity

� Shrinking maintenance windows� Need for flexible operations� Mgmt. of federated applications� Product incompatibilities

Data Growth• 60 – 80% annual data

growth• More and larger applications• Compliance• Storage replication (HA,

DR)

Cost Pressure• For every 1$ purchasing

hardware customers are spending 5$ during operations

• Virtualization• Automation of tasks

Business Challenges, SLAs• Zero tolerance for business downtime• More online hours• Smaller RTOs• Smaller windows for release upgrades

Growing SAP landscapes• Federated SOA applications• Growing number SAP systems• Release upgrade complexity

Storage management challenges



Tivoli Software


Requirements

• Flexibility• Productivity• Business Continuity

SAP Infrastructure Trends and Solutions

Challenges

• Complexity• Interoperability• Data Growth

Power 5/Power 6 & Storage

Vir

tua

liza

tion

Market Forces

• Ability to Act• Availability of the business• Regulations

• Cost of operations• Cost of outages• Cost of infrastructure

TSM FlashCopy Solutions

operational flexibility for system administration processese.g. backup/recovery (long running, resource binding)

Tivoli Software


Separation of backup from production processing

� production copy for access by an auxiliary server � instantaneous physical copy via FlashCopy technique� unimpacted application - flexible system administration

Complete workflow

� dynamic logical copy with application awareness� reversed process for Flashback restore� added-value services, e.g. DB verify, cloning

Automated, production-oriented process� control of all steps and system interactions� robust and dependable standard product � immediately usable – no scripting

FlashCopy Solutions - ‘Backup goes Virtual‘



Tivoli Software


AuxiliaryServer

mySAPDBServer

Disk Subsystem

incl. mount on aux. server 6h15m (disk)backup duration

till start of roll fwd recovery8h< 12mrestore window

load on aux. srvr<= 40%<5%CPU load - backup

using incr. FC6h<1hrestore latency

log volume for consistency6h1mdatabase backup window

commentsTapeFlashCopy

Example: 2.5 TB DB2 in a typical environment – Tape: 4 x LTO3FC: SVC + DS8000)

Traditional Tape vs FlashCopy Backup/Restore

Tivoli Software


� Market Forces and FlashCopy Solutions Concepts� FlashCopy Solutions Highlights

– Modular Components for Evolutionary Growth

– Function Menu

– Business Resilience a la carte

� Outstanding FlashCopy Support with DB2 9.5

Agenda



Tivoli Software


AdministrationAssistant

TSM for ACS TSM for ERP

Centralized

SAP backup management

• operations monitoring• performance monitoring• performance tuning• remote configuration• reporting

FlashCopy Support

• impact free backup• minute restore• seamless integration with tape

backup• SAP System cloning• Available on DS6000, DS8000

SAN VC, ESS-800

TSM Backup

• Performance (~2 TB/h)• Productivity:

• Integration into SAP Workflows• Versioning

• Relyability:• Multiple redo-log copies• Multiple server

Flash

Copy

Full Platform Coverage

• DataBases• Oracle• DB2• SAP DB

• All SAP supported onUnix and Windows

DP for mySAP

2:1

2:1

TSM

Server

2:1

2:1

TSM

Server

Compression

Compression

Multiple PathMultiplexing Multiple Server

Overview: TSM Backup & Recovery of SAP Environments

Tivoli Software


� minimum production impact (Backup and Recovery)

� maximum administration flexibility (adhoc execution)

FlashCopy Solutions for SAP Environmentsnew generation of IT Management Processes to complement Virtualisation

2.5 TB200 GB 600 GB

A

B

B CB

A

C C

A

Re

sto

ration

tim

e

DB size

SLA6 h

restoration

batch update

12.0024.00

on-line

batch processing

SAP productioncycle

3 33disk only

disk and tape1

1

disk and delayed tape 2

FlashCopy backup Backup Window



Tivoli Software


FC Clone toclone system

prepareclone

Redirected Restore

0:00 0:000:00Production schedule

backup to

tape (TSM)prepare for cloning

day 4day 1 day 2

clean-updatabase postprocess clone

S S

day 3

restore toclone system

prepareclone sys.

daily work hours

FlashCopypostprocess clone

dev

test

prod

eduProduction

Clone

Cloning in an SAP System landscape

Tivoli Software


mySAPProduction

SVC

LVM Mirroring

SVC

12

BackupStorage

&Tape

Library

TSM

LVM mirroring provides for seamless take-over. Mirror rebuilt in backgroundafter problem fixed.

FlashCopy Solutions added-value- backup needs 1 mirror copy FC only- alternating FC for 2 backup generations

on disk for fast Flashback

12

FC BACKUP

Tues

Thu

Sat

FC BACKUPMo

Wed

Fri

FlashCopy Solutions and Storage HA



Tivoli Software


SAPProduction

SVC

LVM Mirroring

SVC

12

BackupStorage

&Tape

Library

TSM

12

FC BACKUP

Tues

Thu

Sat

FC BACKUPMo

Wed

Fri

SAPTakeOver

HACMP Cluster

FlashCopy Solutions and Storage plus Server HA

Tivoli Software


DR SitePrimary Site

BackupStorage

&Tape

Library

TSM

mySAPProduction

LVM Mirroring

mySAPTakeOver

BackupStorage

&Tape

Library

TSMHACMP Cluster

continuous Log Archive 1 copy to each site

SVCSVC

12

12

FC Backup

Tues

Thu

Sat

FC BackupMo

Wed

Fri

FlashCopy Solutions and full HA with DR



Tivoli Software


Agenda

� Market Forces and FlashCopy Solutions Concepts� FlashCopy Solutions Highlights� Outstanding FlashCopy Support with DB2 9.5

– DB2 9.5 native support for FlashCopy backups

– Product extensions with TSM for ACS

– Comparison

Tivoli Software


DB2 9.5: Two complementary backup concepts

� DB2 V 9.5 will ship two complementary backup modules

– A backup adapter for traditional backups to TSM– db2 backup db <SID> use TSM

– db2 backup db <SID> load /usr/tivoli/tsm/tdpr3/db2/libtdpdb264.a

– An embedded version of TSM for ACS to create FlashCopy and snapshot backups (N-Series NFS support is included)

– db2 backup db <SID> use snapshot

� TSM for ACS V 5.5 will enhance the embedded module

– Deeper exploitation of copy services from the storage device

– Integration of snapshot backups with tape backups(requires a TSM Server)

(1)

(2)

TSM

server

1

DB

ServerTape

Library

Tape

LibraryNetwork

DB BackupImage



Tivoli Software


DB2 9.5 Integrated FlashCopy

� Embedded version is part of DB2 Premium Availability Feature

– Included in DB2 Enterprise Edition

– Included if DB2 license purchased from SAP

– Requires FlashCopy (for DS8K, DS6K, ESS, SVC) or N-Series snapshot restore feature to be licensed

– Does not require TSM Server in the environment

� Ease of use

– Part of DB2 Install procedure

– Installation does not require a secondary server anymore

– FlashCopy backups are recorded in the DB2 backup history

– Single backup command even for partitioned and distributed databases– db2 backup db <SID> use snapshot on all dbpartitionnums

Tivoli Software


TSM for ACS 5.5 extensions for DB2 9.5

� Seamless upgrade path– TSM for ACS and DB2 integrated FlashCopy are built on same code

– TSM Server remains optional� Support for multiple backup generations� Support of LVM mirrored environments

– FlashCopy of individual LVM mirrors possible� Single machine installation for “snapshot-only” environments

– Even for distributed DB2 databases� Ability to create backups to TSM from a secondary system

– Use snapshot backup as source for TSM backup

– Move backup workload from production host to a secondary host– Separate schedule for TSM backups and snapshot backups– Retry support for offloaded TSM backups

– Ability to mount/unmount snapshots on the secondary system



Tivoli Software


DB2 Premium Availability Feature

(Included in DB2 Enterprise Edition)FlashCopy license

TSM for ACS license

DB2 Premium Availability Feature

(Included in DB2 Enterprise Edition)FlashCopy license

License requirements

Fully integrated support for performing backup to TSMfrom a secondary host.

N/A. No integrated support for backup to tape.

Backup to tape offloaded from production server

Fully integrated support for backup of snapshot image to

TSM. A single backup command can drive the snapshot

backup together with the backup to TSM.

No integrated support. Traditional and

snapshot backups are complementary

but not integrated.

Integrated backup of snapshot image

to tape

Supports snapshots from either source or target mirror

sets.

•Currently for AIX LVM mirroring

•Future for DS / SVC metro & global mirror & N-series

SnapMirror

No supportSnapshot support Integrated with

Mirroring

YesNo supportIncremental FlashCopy support for DS storage devices

No product Limit. ACS will support as many versions as

the storage device and available resources allow.

Max 2 snapshot versions supportedlocal snapshot backup versions

TSM for ACS extensionsVersion embedded into DB2Functional Item

Features of the embedded vs. the enhanced version



Section 2: Product Internals - TSM for ACS



Unit 2

Implementation / Configuration

Unit Objectives


• Describe the concepts for TSM for ACS in detail • Install and configure TSM for ACS • List the basic requirements for using TSM for ACS

Product Overview

Operating Environment

The operating environment consists of the DB2 RDBMS executing on an AIX server attached to one of the supported storage systems. This AIX server is the production system. Another AIX server, the backup system, is also attached to the same storage system to back up FlashCopy copies of the production system to the TSM server. This is done by the concerted action of TSM for ACS for mySAP and TSM for ERP - Data

Protection for mySAP (shared vendor library and prole).

TSM for ACS supports the following storage system:

• IBM ESS Model 800

• IBM DS6000 and IBM DS8000

• IBM SAN Volume Controler (SVC)

TSM for ACS requires DP for mySAP to perform the actual backup or restore to or from the TSM server.

Unit 2: Implementation / Configuration TSM for ACS Workshop


The following figure depicts the hardware and software environment in which TSM for ACS operates.

Figure 1: Product Overview

The products and hardware elements shown in the figure above have to be available on the production and backup systems.

Prior to any involvement of TSM for ACS, the production system will have access to the DB2 database running the mySAP application transactions. The backup system at this time will have the software products installed but no access to any DB2 database files.

DB2 Backup Options with Copy Services

When you create a FlashCopy (locally or remotely), the storage system creates a logical copy of a logical disk (or set of disks) over a window of time without freezing or inhibiting application changes to those disks, and therefore requires proper synchronization with the database system. DB2 provides capabilities to ensure this synchronization.

Two commands are available that can be used to facilitate hot backups of DB2. When the following command is issued, database writes are prevented, but the database remains online and available for reads:

db2 set write suspend for database

In an SAP mySAP e-business solution, the hourglass might be displayed for SAPGUI users while the database is in write-suspend mode. Once the source database has been

TSM for ACS Workshop Prerequisites for TSM for ACS for mySAP


placed in a write-suspended state, a FlashCopy backup can be started. The source database can then be fully enabled again by issuing the command:

db2 set write resume for database

Any changes directed toward the data during the write suspend are then applied and all transactions from SAPGUI users will continue.

The capability is provided to back up a database from a FlashCopy. This makes it possible to offload DB2 backups from the production system to the backup system, thus not impacting the production system at all except for the amount of time required to split a copy of the database.

Prerequisites for TSM for ACS for mySAP

Overview

The two-system environment consists of a production system (which contains the database server) and a backup system.

The production system will have a disk setup for the mySAP database such that the database files will be allocated on so-called source volumes; the backup system will only see the database disks (target volumes) after a FlashCopy has been done on the production system.

Multiple sets of target volumes can be used, in order to have different generations of disk copy backups.

Understanding the behavior of TSM for ACS allows you to set up the disk environment properly. When TSM for ACS performs a FlashCopy Backup,

• all the tablespace container files and • all files in the local database directory

must be transferred via FlashCopy to the backup system.

Because the totality of all these database files will be involved in the FlashCopy disk process, some rules must be followed:

• The above files (or the underlying physical volumes) must be on so-called source volumes, which will be copied to target volumes as a result of a FlashCopy request.

• No other files from other applications should be allocated on the set of the above physical volumes, to avoid complications with these files in the case of a FlashCopy Restore (FlashBack Restore).

Combined with other requirements such as database performance, the planning of the overall disk environment could now be undertaken as discussed in the next sections.



Hardware Requirements

� Please check the latest Prerequisite Checklist

http://www-01.ibm.com/support/docview.wss?rs=3043&uid=swg21316079 Note: The numbers in parentheses refer to the notes following the table.

Database Storage System

Component

ESS 800

DS6000/

DS8000 SVC

Production

System

(PS)

Backup

System

(BS)

Takeover

System

(HACMP)

Processor IBM eServer(TM) pSeries(R) (RS/6000(R))

x x x

Storage system options

FC 1830-1835 (7)

2244-PTC (7)

x x x

Storage system microcode and LIC

(8) (8) (8) x x x

Connection of processor to storage system

SCSI or Fibre Channel adapters (1) x x x,

Disk space 100 MB (3) x x x

Memory 256 MB (4) x x x

DS Open API CIM Agent

SVC master console

x x x LAN connection to:

NFS (PS to BS) x x x

LAN or SAN connection to:

TSM Server x (2) x (2) x

LVM mirrors (6)

Two mirror sets (if used) x x x

HACMP (5) x x x x

Table 4: Hardware Requirements

Notes:

1. Source volumes accessible to PS, target volumes accessible to BS. Sources and targets must not be accessible to both systems simultaneously. Source and target volume pairs must have the same size and reside in the same hardware unit.



2. On the PS, to the TSM Server for restore and backup/restore of log files (using the DB2 log file manager). On the BS, to TSM Server for backup, if not installed on BS.

3. Applies to each TSM for ACS version level installed. In order to avoid an uncontrolled termination of TSM for ACS (or the called system commands) due to lack of space, TSM for ACS issues a warning message (IDS1310W) if an essential file system has less than 50 MB free space. If the available space is less than 5 MB, TSM for ACS terminates with an error message (IDS1311E); in this case, the affected file system first needs to be increased prior to rerunning TSM for ACS.

4. However, check the mySAP DB server memory requirements, which normally are in the range 1-2 GB, depending on workload objectives.

5. Three pSeries systems are required when planning for a high availability environment where a primary and takeover system with HACMP will become established with HACMP. Each needs to play the role of the production system depending on which is currently the active system. The takeover system for the production server cannot be the backup system.

6. For details, see Installation and User’s Guide, Chapter 8. TSM for ACS Functionality for AIX LVM Mirrored Environments.

7. The FlashCopy LIC or the equivalent point-in-time copy (PTC) function is required. For the ESS, at least microcode V2 is required.

8. See the Preinstallation Checklist file and/or the README file on the installation CD or at the support Web site for microcode and LIC levels required.

Software Requirements

� Please check the latest Prerequisite Checklist

http://www-01.ibm.com/support/docview.wss?rs=3043&uid=swg21316079 Notes:

1. The following Software Requirements are based on the product TSM for ACS for mySAP Version 5.4.2.0

2. The levels shown specify the minimum required. For the latest supported levels, check the README file or refer to the support Web page.

3. Unless otherwise stated, software required on both the production and backup systems must be installed and configured identically on each system.

4. The numbers in parentheses refer to the notes following the table.


Component

ESS 800

DS6000/

DS8000 SVC

Production

System

Backup

System

Operating System

AIX (32- or 64- 5.2. ML05, 5.3 ML01 (2) x x




Component

ESS 800

DS6000/

DS8000 SVC

Production

System

Backup

System

bit)

Multipath Subsystem Device Driver (SDD) (12)

1.6.0.2+ (optional) 1.6.0.2+ x x

Multipath Subsystem Device Driver Path Control Module (SDDPCM) (12)

2.1.0.1+ (optional) 2.1.0.1+

(optional) x x

Locale en_US.ISO8859-1 (3) x x

JFS/JFS2 x (13) x x

NFS x x x

Tivoli Storage Manager (TSM)

TSM Server 5.2+ x (optional,

see 2)

TSM Backup/Archive Client

5.4+ x x

TSM API 5.4+ (5) x x

Data Protection for mySAP (DB2)

5.5.0.2 (8) x x

Data Protection for IBM Disk Storage and SAN VC for mySAP (DB2 UDB)

5.4.2.0 x x

Database Software

SAP R/3 or mySAP (6)

R/3: 4.6B to 4.6D or mySAP e-business solution (such as BW) or SAP NetWeaver

x

DB2 UDB Enterprise Server Edition (ESE) 32- or

DB2 UDB ESE V8.1 FP7, or later (32 bit or 64 bit) DB2 UDB ESE V8.2 or DB2 V9 (64 bit) - for DB2 V9 FP2 a special DB2 build

x x




Component

ESS 800

DS6000/

DS8000 SVC

Production

System

Backup

System

64-bit is required for APAR IY95759

Storage System Interface

ESS Copy Services Command-Line Interface (CLI) (7)

2.4.1.50

DS Open API CIM Agent (10)

5.1.0.73 5.2.1.139 5.3.0.150 (5.4.0.86)

(9) (9)

CIM Agent for SVC (11)

SVC 4.2.1 with SVC

master console level >= 4.2.1.829

CIM Server Runtime Environment (Pegasus) (1)

2.5.1.21 2.6.1.20

x x

CIM Server Base Providers for AIX (Pegasus)

1.2.6.21 1.2.7.20

x x

OpenSSL (4) 0.9.7.x with CIM Pegasus 2.5.1.21 0.9.8.x with CIM Pegasus 2.6.1.20

x x

Table 5: Software Requirements

Notes:

1. FC 0949 (AIX 5.2), FC 0968 (AIX 5.3). From the AIX Expansion Pack CD (not part of the TSM for ACS package) or can be downloaded from: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=aixpegcim Consisting of:

o sysmgt.pegasus.cimserver.rte o sysmgt.pegasus.osbaseproviders



Only the client libraries are used in a TSM for ACS environment. Therefore, the term CIM Client is used instead of CIM Server to refer to the software following installation.

2. See the README file and/or the Preinstallation Checklist for current maintenance level and PTF information. Virtual I/O for HBAs is not supported.

3. Check with

locale -a

4. Available on the "AIX Toolbox for Linux Applications for POWER(TM) Systems" CD. Installation is required by Pegasus.

5. As required by version of DP for mySAP installed (including 32- or 64-bit configuration). Included in Backup-Archive Client and Server package.

6. SAP on production system (with SAP-approved DB2 version). The SAP Admin Tools can be installed for DB2 V8.1. They are not recommended by SAP with DB2 V8.2 and no longer supported with DB2 V9 with its own log file management (see the DP for mySAP documentation for more information).

7. For ESS 800 only: IBM 2105 ESS Storage Management CLI and Copy Services CLI for AIX. The code level must correspond to that of the microcode installed in the ESS clusters. See Hardware Requirements. Installation required only on the machine hosting the DS Open API CIM Agent. Must be installed prior to installing the CIM Agent.

8. Corresponding to OS level and DB2 level (32- or 64-bit). 9. Installable on any supported host accessible to both systems. Installation on

the PS is not recommended, due to the load imposed by Java(TM) on the CIMOM component. User ID required for TSM for ACS access.

10. Includes DS Open API, ESS NI Client, CIMOM, SLP. User ID required for TSM for ACS access. Installable on any host accessible to PS or BS. Installation on the PS is not recommended due to the loading imposed by Java on the CIMOM.

11. Installed as part of SVC. User ID required allowing access by TSM for ACS. 12. TSM for ACS supports SDD and SDDPCM. Either can be used in this case,

but neither is required. 13. The database must reside on a Journaled File System (JFS or JFS2)9. The DB2

database must not be installed o on raw devices o in mirrored AIX LVM environments other than that described in

Installation and User’s Guide, Chapter 8. TSM for ACS Functionality for AIX LVM Mirrored Environments)

o using the JFS2 file system inline logs

TSM for ACS Workshop Configuration of TSM for ACS for mySAP


Environment Requirements

� Please check the latest Prerequisite Checklist � AIX Base System Locale ISO Code Set - U.S. English

(the command 'locale -a' must show that the locale en_US.ISO8859-1 is

available) � TSM ACS on the backup system initiates its work on the production system

via TSM ACS acsprole process running on PS; on the PS for that reason – for correct environment settings, the /etc/environment file needs to be

set up as follows: ENV=$HOME/.profile � the PATH environment variable must include the /usr/sbin directory for the

userid running the TSM ACS function; e.g. PATH=${PATH}:/usr/sbin

export PATH have to be added to the $HOME/.profile if the Korn shell is used The ulimits of the 'db2<sid>' user and 'root' on the production and backup systems should be at least the following (check with ulimit -a):

data seg size (kbytes) unlimited

max memory size (kbytes) 131000

stack size (kbytes) 131000

Depending on the user's shell and OS level, the output of ulimit -a can vary.

Configuration of TSM for ACS for mySAP

Combined with other requirements such as database performance, the planning of the overall disk environment could now be undertaken as discussed in the next section.

ESS/DS Setup

� The IBM ESS/DS is configured so that the following conditions are satisfied:

– The ESS/DS LUNs used by the production database are accessible to the production system [they are used by the FlashCopy process]

– The IBM ESS/DS LUNs used as target volumes by the FlashCopy process must be accessible to the backup system

– The size of each ESS/DS target volume must match the size of its ESS/DS source volume

� DS Open API CIM Agent – ensure that the ESS/DS is configured in the CIM Agent

For details on configuration of DS Open API CIM Agent see Unit 3: Configuration of DS Open API CIM Agent.



File system Setup

For planning purposes, it is advisable to subdivide the disk environment (spread over the 2 systems) into the following categories.

1. Local disks on the production system (p_disk category)

Besides the OS disks, you will also have here the disks where DB2 and mySAP executables will be placed during DB2/mySAP installation.

2. Source volumes (disks) on the production system (db_disk category)

These will contain all files such as tablespace containers and the local database directory. All the disks that make up the volume groups in which those files reside must be logical volumes in the respective storage system, which become the source volumes in the FlashCopy operation.

At least the same number of target volumes (constituting one target set) must be planned and made available for the planned subsequent FlashCopy operations. Those volumes will become available, with the image copies, on the backup system after the FlashCopy has been initiated by TSM for ACS.

3. 'Shared disks' on the production system (NFS_disk category)

Via NFS mount, the backup system must have access to a directory of the production system:

/db2/<SID>/dbs

This directory, part of the local disk setup of the production system, will be exported on the production system such that it can be NFS-mounted on the backup system with root access. This directory is used by DP for mySAP and TSM for ACS.

4. Supplementary local disks on the production system (p_db_disk category)

These will contain the log, log archive, and retrieve directories.

5. Local disks on the backup system (b_disk category)

In addition to the operating system disks, you will also have here the disks on which DB2 executables will be placed during the installation.

6. Disks for the TSM server (optional, TSM_disk category)

If the TSM server is planned to run on the backup host, you will plan for an additional disk category (TSM_disk category) for the TSM DB/log/storage disks.

TSM for ACS Workshop Configuration of TSM for ACS for mySAP


The following figure show the summary of the above described disk categories:

Figure 2: File system Setup

AIX LVM Setup

As discussed in the section above the disks of the db_disk category will be flashcopied from the source to the target volumes. For that reason all these disk off db_disk category must be separated from other disks that are not part of the FlashCopy. This is done with the AIX Logical Volume Manager (LVM).

� Volume Group and File System Layout – define within the db_disk category the VGs to cover the requirements

for the TSM ACS FlashCopy Backup and FlashBack Restore processes � db_disk category

– one or more VG(s) for the DB tablespace files and DB local database directory

– /db2/<SID>/sapdata1 .... /db2/<SID>/sapdata<N> in VG1 – /db2/<SID>/saptemp1 in VG2 – /db2/<SID>/db2<sid> in VG3

� p_db_disk category – one or more VG(s) for the DB log files file systems:

– /db2/<SID>/log_dir in VG4 – /db2/<SID>/log_archive and /db2/<SID>/log_retrieve in VG5

Note: Each jfslog LV (used in the above VGs in db_disk category) with all its LPs is

not allowed to be spread over more than one ESS/DS volume (striping not allowed for

jfslog LV)



As a minimum TSM for ACS requires one Volume Group (VG) which contains all the DB tablespace files including temporary tablespaces and the DB local database directory. It is not allowed to have other file in this VG. You can also separate all the sapdata filesystems in separate VGs.

NFS Setup

TSM for ACS requires at least on filesystem to be NFS shared between the production system and the backup system. By using NFS shares TSM for ACS can use one shared repository (also named idssave and specified by the .fcs profile parameter IDS_CONTROL_FILE). In addition the encrypted passwords must be stored in the NFS share in the file specified with the profile parameter CONFIG_FILE.

� The production and backup system need to share for backup and restore / recovery purpose the following files:

– DP for mySAP profile (.utl) including its configuration file (.bki) – TSM ACS profile (.fcs), TSM ACS target volumes file (.fct),

IDS_CONTROL_FILE, etc. � Those files reside in the following directory and need for share purposes be set

up on the production system as an NFS export: – /db2/<SID>/dbs

It is required that the NFS exports on the production system are created with root access. Otherwise TSM ACS will fail in creating files on the backup system.

Limitations

� What is not supported with TSM ACS FlashCopy of

– DBs residing on raw devices – DB data tablespaces of type SMS (temp tablespaces like PSAPTEMP

can be SMS) – Soft links to DB2 UDB DB files

The normal mySAP setup of the DB2 UDB tablespace containers does not use links.

TSM for ACS Workshop Installation / Configuration of TSM for ACS for mySAP


Installation / Configuration of TSM for ACS for mySAP

It is recommended that the prerequisite products be installed and customized in the following sequence:

1. Installation and configuration on the production system

a. Install DB2 V9 and SAP b. Install TSM BA client with TSM API

i. create dsm.sys and dsm.opt ii. create TSM management classes and TSM nodes

c. Install TSM for ERP i. InstallShield (InstallAnywhere) installation with TSM

configuration. Make sure you use /db2/<SID>/dbs as configuration directory. Otherwise you must make sure that the TSM for ERP configuration files are NFS shared to the backup system

d. Install TSM for ACS i. InstallShield installation

ii. run setup.sh from the installation directory iii. adapt the TSM for ACS profile (.fcs) and the TSM ACS target

volumes file (.fct) iv. run TSM for ACS configure function to setup the TSM ACS

socket servers on production system 2. Installation and configuration on the backup system

a. Install DB2 V9 b. Install TSM for ACS

i. InstallShield installation (do not run setup.sh yet) ii. run setupDB2BS script to configure the backup system

c. Install TSM BA client with TSM API i. create dsm.sys and dsm.opt

d. Install TSM for ERP i. InstallShield (InstallAnywhere) installation with upgrade

installation (the TSM configuration is already NFS shared and can be reused on backup system)

e. Install TSM for ACS i. run setupDB2BS from the installation directory

ii. run setup.sh from the installation directory

Installation and Configuration on Production System

� Installation and Configuration on Production System – DB2 V9 and mySAP | R/3 according to the

– File system requirements of TSM ACS – 'mySAP | R/3 Installation for UNIX' manual which also covers

the DB2 UDB part



• Tivoli Storage Manager products o TSM Server on your backup system (might not apply if already

available or on a different host) o TSM Backup-Archive clients and the TSM API on the production and

backup systems.

For information regarding installation procedures for these software applications, see Tivoli Storage Manager for UNIX and Linux Backup-

Archive Clients Installation and User's Guide V5.3 (or its predecessor TSM for UNIX Using the Backup-Archive Clients) and TSM Using the

Application Program Interface.

• DP for mySAP on the production and backup systems

For information regarding installation, see Tivoli Storage Manager for

Enterprise Resource Planning: Data Protection for mySAP Installation and

User's Guide for DB2 UDB.

When installing DP for mySAP, you must provide the correct path to the DP

for mySAP profile /db2/<SID>/dbs, which will be NFS-mounted on the backup system. Make sure that the specified path has been created on the production system before starting the installation. Otherwise, you will have to customize two different DP for mySAP profiles on the production and backup systems.

� Installation and Configuration on Production System

– TSM B/A client with API component (will be used by TSM ERP - DP for mySAP)

– TSM ERP - DP for mySAP (with /db2/<SID>/dbs as path for configuration files) – TSM ACS (installation including running 'setup.sh')

- cd /usr/tivoli/tsm/acssap/db2 - run 'setup.sh' - prepare the profile (.fcs) and the target volumes file (.fct) - on PS run tdphdwdb2 with function 'configure' (to set the passwords for DB2 UDB user and CIM user and to create and start the TSM ACS socket server on PS)

At this time you should be able to run on the (1-system) environment

– the db2 backup and restore commands and – DB2 logfile management using native TSM agent or TSM ERP – DP

for mySAP together with DP for mySAP once you have configured the profile

vendor.env (DP for mySAP vendor initialization file for DB2 V9) init<SID>.utl (profile of DP for mySAP) and the dsm.sys / dsm.opt (TSM API profiles)



Note: the TSM node configuration parameter passwordaccess can be set to prompt or generate; DP for mySAP can handle this. DP for mySAP needs to run on PS as well as on the BS.

When passwordaccess generate should be used, you need to setup the TSM nodes with the proxynode and asnode options like shown in the sample below.

This example shows the administrative client server commands to back up in TSM for ACS environments, using two nodes on the two TSM for ACS systems (production and backup system) which participate in the TSM for ACS operations.

1. The administrator defines three nodes on the Tivoli Storage Manager server: node_1, node_2 and node_acs. node_1 and node_2 are only used for authentication; all filespaces are stored with node_acs.

REGISTER NODE node_1 mysecretpa5s

REGISTER NODE node_2 mysecretpa5s

REGISTER NODE node_acs mysecretpa5s

2. The administrator defines a proxynode relationship between the nodes:

GRANT PROXYNODE TARGET=node_acs AGENT=node_1, node_2

3. The administrator defines the node name and asnode name for each of the machines in their respective dsm.sys files:

nodename node_1

asnodename node_acs



The following figure shows the relationships of the profiles of TSM for ACS, DP for mySAP, and the TSM API with TSM for ACS for a two-system environment:

Figure 3: Profiles

Utilizing the storage system capabilities, such as FlashCopy and withdraw, for disk copy backups, with succeeding backups to external media (using TSM and DP for mySAP), you involve a two-system environment (see Figure above), in which the various control files and profiles contain information needed by both systems. The ideal setup is to have the DP for mySAP and TSM for ACS profiles and control files

set up on NFS shares, so that all DP tools (tdphdwdb2, splitint, prole, shared

vendor library) use the same profiles and control files, regardless of the system the tool has been started on.

In addition, DP for mySAP and TSM for ACS use the same profiles, regardless of whether they were started on the production or backup system.

Such a setup will allow the FlashCopy function of the storage system to be integrated transparently into TSM for ACS and DP for mySAP in such a way that the DB administrator can perform all the mySAP DBA tasks he is accustomed to doing, such as:

• administering a DB2 database on the production system



• initiating backups with Copy Services capabilities on the backup system using TSM for ACS and DP for mySAP, or backups without Copy Services capabilities on the production system with TSM for ACS and with DP for mySAP.

• running and controlling backups/archiving of the log files on the production system

• restoring/recovering the database on the production system with Copy Services capabilities using TSM for ACS FlashBack Restore, or restoring/recovering the database on the production system on the basis of the objects that were backed up to TSM

Installation and Configuration on the Backup System

� Installation and Configuration on the Backup System – Install DB2 V9 – Install TSM for ACS for mySAP (without running 'setup.sh') – cd /usr/tivoli/tsm/acssap/db2 – Configure TSM for ACS for mySAP by running 'setupDB2BS' which

will perform mainly the following step (among others): – Create DB2 V9 entries in /etc/services (sapdb2<SID>,

DB2_db2<sid>...) – Create userids and groups – Create mountpoints for all DB files to be flashed

(/db2/<SID>/sapdata<N>,...) – Create NFS mount /db2/<SID>/dbs and mount this NFS file system – Copy logon profiles and mySAP environment scripts from PS to BS – Create DB2 V9 instance db2<sid> with or without DPF – Catalog DB <SID> for remote connection to PS

– Install and customize TSM B/A client with API component (will be used by DP for mySAP)

– Install DP for mySAP – Customize TSM for ACS for mySAP

– run 'setup.sh'

– check the environment requirements and adjust where needed (see slide 'Setup 3')



TSM for ACS for mySAP profile (.fcs)

This profile is defined by the user with all the information TSM for ACS needs to successfully perform the following functions:

• run a FlashCopy from source to target volumes • withdraw the source/target volume relation • inquire about the status of the backup cycles • delete an entry from the TSM for ACS control file

Like the other profiles of DP for mySAP (.utl), the TSM for ACS profile is normally used in conjunction with only one database, i.e., for only one SID. The profile is

identified by the value of the parameter -p of the TSM for ACS program tdphdwdb2.

Structure of the TSM for ACS Profile

Comments can be used at any place within the profile; they are indicated by a '#' sign in the first column of a line.

Note: Tab characters are not permitted.

In order to cover future development additions, the profile has been broken up into the following topics:

• global • DB2 • copyservices_data

Each topic has a unique set of specific parameters. All parameters belonging to a topic are enclosed by a topic begin statement (>>> topicname) and a topic end statement (<<< topicname). The base structure for the topics is as follows:

# Global topic

>>> global

parameter_line 1

...

parameter_line n

<<< global

# DB2 topic

>>> DB2

parameter_line 1

...

parameter_line n

<<< DB2

# copyservices_data topic

>>> copyservices_data

parameter_line 1

...

parameter_line n

<<< copyservices_data



1) The VOLUMES_FILE parameter points to the TSM ACS target volumes file, which contains a list of target volumes (TARGET_VOLUME)

2) File respectively directory must be shared between PS and BS

3) The CONFIG_FILE parameter points to the TSM ACS configuration file, which contains the encrypted passwords for the CIM-user and for user db2<sid> (BS --> PS)

4) New parameter with TSM ACS 5.4.2.0

TAB characters are not allowed !!!

TSM ACS for mySAP profile (.fcs) LOGON_HOST_PROD LOGON_HOST_BACK IDS_CONTROL_FILE

2)

BACKUP_MAX CONFIG_FILE

2), 3)

WORK_DIR 2)

LOG_TRACE_DIR 2)

TRACE PROLE_SERVICE_NAME TDPR3_CONFIG_FILE COPYSERVICES_HARDWARE_TYPE VOLUMES_FILE

1), 2)

PRIMARY_COPYSERVICES_SERVERNAME SECONDARY_COPYSERVICES_SERVERNAME

4)

COPYSERVICES_USERNAME COPYSERVICES_PROTOCOL COPYSERVICES_SERVERPORT BACKGROUNDMONITOR_REFRESH_DELAY

4)

FLASHCOPY_TYPE DB2_REMOTE_DBALIAS - DB2_NUM_BUFFERS DB2_TDPR3_LIB - DB2_BUFFER_SIZE DB2_PARALLELISM - DB2_EEE_SYNCTIMEOUT DB2_VENDOR_ENV - DB2_NUM_SESSIONS DB2_EEE_PARALLEL_BACKUP - DB2_EEE_PARALLEL_RESTORE, DB2_AUTHENTICATION - DB2_RESTART_TSM_BACKUP DB2_FLASHBACK_WITHOUT_TSM_QUERY

4)



TSM for ACS for mySAP target volumes file (.fct)

The TSM for ACS target volumes file, which is referenced by the TSM for ACS profile (.fcs) when running a FlashCopy backup, is the file in which the customer needs to specify the target volumes he plans to use in such a backup.

Within one FlashCopy backup, a set of target volumes (a target set) will be needed for a FlashCopy operation with a set of source volumes making up the. More than one target set can be defined for use in different FlashCopy backups (see Installation and User’s Guide, Chapter 10. Multiple Backup Generations (Target Sets) on Disk); in the past a maximum of two targets sets were possible when running the TSM for ACS functionality for AIX LVM mirrored environments (see Installation and User’s Guide, Chapter 8. TSM for ACS Functionality for AIX LVM Mirrored Environments).

The volumes in each target set used in one backup need to be specified in a similar way in a separate target set topic. A target set topic is delimited by a topic begin string (>>>) and a topic end string (<<<), each followed by the target set topic name. The target set topic names start with the prefix 'volumes_set_' and are appended with a target set number x (also referenced in some documentation as a data container ID) to differentiate the various target set topics, where it is recommended to use one- or two-digit values.

Note: Tab characters are not permitted.

In each topic, use one TARGET_VOLUME parameter for each target volume to be used in this target set. A target set topic appears as follows:

>>> volumes_set_1

TARGET_VOLUME ...

.

.

.

TARGET_VOLUME ...

<<< volumes_set_1

If you plan to use a second target set (multiple target sets), you just add the next target set topic in the file:

>>> volumes_set_2

TARGET_VOLUME ...

.

.

,

TARGET_VOLUME ...

<<< volumes_set_2

Comments can be used only before the first target set topic; they are indicated by the "#" character in the first column of a line. Tab characters are not permitted.



TSM ACS for mySAP target volumes file (.fct)

>>> volumes_set_1

# target source size

TARGET_VOLUME 7515089110C - -

TARGET_VOLUME 7515089170A - -

:

TARGET_VOLUME 7515089100C - -

<<< volumes_set_1

Sample after TSM ACS FlashCopy’s execution and source and size value by TSM ACS has been added >>> VOLUMES_SET_1

# target source size

TARGET_VOLUME 7515089110C 7515089110D Size=2.6_GB

TARGET_VOLUME 7515089170A 75150891715 Size=6.1_GB

:

TARGET_VOLUME 7515089100C 7515089100D Size=6.1_GB

<<< VOLUMES_SET_1

TAB characters are not allowed !!!



Special Environments

DB2 V9 with DPF

Figure 4: Special Environments - DB2 V9 with DPF



AIX LVM mirroring

Advantages of the Special Handling of AIX LVM Mirrored Environments

The LVM mirroring functionality offers the following advantages:

• Only one of the 2 AIX LVM LV mirrors becomes the subject of a triggered FlashCopy process, which

o saves the number of needed target volumes o shortens the FlashCopy process o avoids unnecessary performance degradation within the storage system o avoids AIX LVM conflicts when at least one stale physical partition is

produced within one or more AIX LVs on the backup system. • Late failures within the FlashCopy operation due to unsuitable setups can be

avoided; by checking the proper disk setup and customization, TSM for ACS terminates in case of unsuitable conditions and therefore avoids unnecessary cleanup activities on the backup system.

• All AIX LVM mirrors on the production system therefore stay synchronized during the FlashCopy backup process. The FlashCopy backup process at no time compromises the high availability purpose the AIX mirrors were set up for. It is not necessary to resynchronize the LVs after the FlashCopy backup request.

• Online or offline FlashCopy backups can be taken in the same manner as before; there is no change in the backup/restore procedures as outlined in the applicable chapters.

• TSM for ACS provides information about asymmetrical AIX LVM mirror setups when encountered, which can not only prevent the FlashCopy backup from running in unfavorable situations but can also reveal a general deficiency of the high availability setup as well.

• The software allows one copy set to be used in a FlashCopy backup to more than one target set in one hardware unit, thus increasing the earlier maximum number of disk backup levels from 2 to n.

• TSM for ACS needs only one of the 2 copy sets for a Flashback Restore, thereby

o offering the possibility that 'n' FlashCopy backup versions can be eligible for a Flashback Restore

o enabling much faster return to production mode after an outage (everything for the synchronization of the VG will be prepared in advance; however the synchronization can be initiated by the DBA at a more suitable time later).



The following figure shows a typical setup as it could run with the TSM for ACS mirroring functionality:

Figure 5: Special Environments - AIX LVM mirroring (1)

� The TSM ACS Copy Set Parameter –n with its value 1 or 2 on the tdphdwdb2 command causes TSM ACS to use either the topic volumes_set_1 or volumes_set_2 with all its target/(source) volumes within the TSM ACS target volumes file (.fct). If the selected topic contains the parameter HARDWARE_ID_LVM_MIRROR (its value specifies an ESS/DS serial number) then TSM ACS turns on its functionality for AIX LVM mirrored environments and checks on

– a proper AIX LVM mirror setup for all DB LVs – Mirror Write Consistency is set to YES – Quorum is set to OFF – all PPs synchronized (prior and after the FlashCopy) – Schedule Policy is used

� DS Setup (2 DS units are required) A complete copy set must reside in the selected DS unit. One mirror of each DB LV (including the jfslog LVs) must reside in one of the 2 DS units. Symmetrical mirror setup is the ideal one and normally the one TSM ACS should work with; in case of asymmetrical setups in worst case no FlashCopy can be done.



HACMP with AIX LVM mirroring

Figure 6: Special Environments – HACMP

This is a high-availability environment with 2 AIX mirrors distributed over 2 hardware units using HACMP and running production on the primary machine. Note that instead of the 2 machines running with HACMP, a single-machine environment could also be used for the DB server activities connected to an AIX LVM mirror setup. The takeover machine currently does not perform any DB related activities; however, in case of an HACMP takeover, there are no special considerations for this machine compared to the primary system discussion.

The database files that are the object of the FlashCopy backup process reside on logical volumes (LVs) that are mirrored by the AIX LVM. Because all file systems are running as JFS, a mirrored jfslog LV for each volume group is required as well. The sum of all these LVs in one of the mirrors constitutes a complete copy set; a copy set resides on a set of source volumes, which themselves, when a symmetrical setup is in place, are completely located within one of the 2 hardware units. The other copy set is located with its source volumes in the other unit.

Both copy sets can be used alternately in different FlashCopy backup runs when TSM for ACS initiates the FlashCopy process.



Although both copy sets are consistently mirrored on the production system by AIX LVM, only one will be required for the FlashCopy process and the subsequent DP backup running on the backup system.



Unit 3

Configuration

DS Open API CIM Agent

Unit Objectives

After completing this unit, you will be able to: • Describe basic concepts of DS Open API CIM Agent • Describe the configuration parameters for TSM for ACS with the DS Open

API CIM Agent • Configure DS Open API CIM Agent

CIM Agent configuration overview

Understanding the Hardware Interface and Common Information Model (CIM)

Prior to V5.3.1, TSM for ACS supported only the ESS and employed the ESS Copy Services Command Line Interface (CLI) to communicate with this storage system.

Starting with V5.3.1, storage-system support has been retained for the ESS Model 800 and extended to the ESS successors DS6000 and DS8000 as well as to the SAN Volume Controller (SVC). A common, modular mechanism called the Hardware Common Interface (HCI) now provides the link between TSM for ACS and these hardware options for the purpose of managing disk volumes and controlling FlashCopy operations. Support for the ESS 800 is now provided via the HCI.

Note: For an ESS Model 800 configuration, installation of the ESS CLI interface software continues to be required in conjunction with the DS Open API CIM Agent.

Unit 3: Configuration DS Open API CIM Agent TSM for ACS Workshop


The following figure depicts the hardware interface for the ESS / DS configurations.

Figure 7: CIM Agent configuration overview

The key user-visible component of the hardware interface is the implementation of the Common Information Model (CIM). The CIM is a conceptual information framework for describing management properties (in this case, for managing disk storage). It is not bound to a particular implementation. The CIM design allows for the interchange of management information between management systems and applications through the Common Information Model Object Manager (CIMOM), which is an object management engine that exists between the managed system and the management application.

The CIM implementation employed by TSM for ACS focuses on storage systems and is compliant with the Storage Management Initiative Specification (SMI-S) defined by the Storage Networking Industry Association (SNIA). SMI-S is based on a number of existing technologies or industry standards that include the following:

Common Information Model (CIM)

An object model for data storage and management developed by the Distributed Management Task Force (DMTF). CIM makes it possible to organize devices and components of devices in an object-oriented pattern.

Web-Based Enterprise Management (WBEM)

A tiered enterprise management architecture also developed by the DMTF. This architecture provides the management design framework that consists of

TSM for ACS Workshop CIM Agent configuration overview


devices, device providers, the object manager, and the messaging protocol for the communication between client applications and the object manager. In the case of the CIM, the object manager is the CIMOM and the messaging protocol is CIM-over-HTTP. The CIM-over-HTTP approach specifies that the CIM data is encoded in XML and sent in specific messages between the client applications and the CIMOM over the IP network in a SAN.

Service Location Protocol (SLP)

A directory service that the client application calls to locate the CIMOM.

There is a tailored CIM interface, referred to as the CIM Agent, for the selected storage system. The CIM Agent resides on the storage-system host and comprises the following major components:

• CIM object manager (CIMOM) • Service Location Protocol (SLP) • Provider for the specific storage system

The immediate CIM interface for TSM for ACS is OpenPegasus, which is an open-source implementation of the Distributed Management Task Force (DMTF) CIM and Web-based Enterprise Management (WBEM) standards. The Pegasus CIM Server is installed on the TSM for ACS AIX hosts to interface with TSM for ACS and the CIM Agent. However, only the client libraries of the CIM Server package are used by TSM for ACS, and these libraries are referred to in this environment as the CIM Client.

Pegasus is designed to be inherently portable and builds and runs on the AIX, Linux(R), and Windows(R) operating systems. The CIM Standard Schema provides the actual model descriptions. The CIM schema supplies a set of classes with properties and associations that provide a conceptual framework within which it is possible to organize the available information about the managed environment. Platform-specific objects, such as AIX, that must be managed are defined as extensions to this standard CIM model. Providers collect the management data from the underlying platform resources and populate the CIM objects described in the conceptual CIM model. These objects are then ready to be served by the CIMOM to the client management applications for managing the resources of the underlying platform. This mechanism provides an open-standard way for a management application to manage the resources of the underlying platform.

Understanding the CIM Agent

A CIM Agent allows the use of common building blocks, rather than proprietary software or device-specific programming interfaces, to manage CIM-compliant devices. A CIM Agent typically involves the following components:

CIM object manager (CIMOM) client application device

The storage server that processes and hosts the client application requests.



Device provider

A device-specific handler that serves as a plug-in for the CIM. That is, the CIMOM uses the handler to interface with the device.

Service Location Protocol (SLP)

A directory service that the client application calls to locate the CIMOM.

Agent code

An open-systems standard that interprets CIM requests and responses as they transfer between the client application and the device.

CIM object manager (CIMOM)

The common conceptual framework for data management that receives, validates, and authenticates the CIM requests from the client application. It then directs the requests to the appropriate component or device provider.

Client application

A storage management program (such as TSM for ACS) that initiates CIM requests to the CIM agent for the device.

Device

The storage server that processes and hosts the client application requests. In the TSM for ACS framework, a device can be an ESS 800, DS6000, DS8000, or a SAN Volume Controller.

The interactions involving the CIM Agent are as follows:

1. The client application (in this case, TSM for ACS) locates the CIMOM by calling an SLP directory service. When the CIMOM is first invoked, it registers itself to the SLP Service Agent and supplies its location, IP address, port number, and the type of service it provides, thus enabling discovery by the client application.

2. With this information, the client application starts to communicate directly with the CIMOM by sending it CIM requests.

3. As requests arrive, the CIMOM validates and authenticates each request. It then directs the requests to the appropriate functional component of the CIMOM or to a device provider. A device can be a storage server such as the DS8000.

4. The provider makes calls to a device-unique programming interface on behalf of the CIMOM to satisfy client application requests.

TSM for ACS Workshop ESS/DS User Setup


ESS/DS User Setup

� See ‘DS Open Application Programming Interface Reference’ GC35-0493-03 for complete installation instructions for CIM agent.

� To allow the CIM Agent to communicate with a DS / ESS you must first

define a DS-user / ESS-user: � define a DS-user e.g. using the DScli:

/opt/ibm/dscli/dscli

dscli> mkuser -pw <password> -group admin <DS-user> � you can change the password settings for the DS-user. e.g. you can set

the expiration to 0 and you can avoid the locking of a DS-user in case of failed logins by using the DScli command: dscli> chpass -expire 365 -fail 5

dscli> chpass -expire 0 -fail 0

DS Storage manager and DS CLI user management

User management can be done using the DS CLI or the DS GUI. An administrator user ID is pre-configured during the installation of the DS8000, using the following defaults: User ID admin Password admin Attention: The password of the admin user ID will need to be changed before it can

be used. The GUI will force you to change the password when you first log in. The DS CLI will allow you to log in, but will not allow you to issue any other commands until you have changed the password.

As an example, to change the admin user’s password to passw0rd, use the following command:

chuser -pw passw0rd admin

Once you have issued that command, you can then issue any other command. During the planning phase of the project, a worksheet or a script file was established with a list of all people who need access to the DS GUI or DS CLI. The supported roles are:

• Administrator has access to all available commands. • Physical operator has access to maintain the physical configuration (Storage

Complex, Storage Image, Array, rank, and so on). • Logical operator has access to maintain the logical configuration (logical

volume, host, host ports, and so on). • Copy Services operator has access to all Copy Services functions and the same

access as the monitor group. • Monitor group has access to all read-only list and show commands.



• No access could be used by the administrator to temporarily deactivate a user ID.

General password settings include the time period in days after which passwords expire and a number that identifies how many failed logins are allowed. Whenever a user is added, a password is entered by the administrator. During the first sign-in, this password needs to be changed by the user. The user ID is deactivated if an invalid password is entered more times then as defined by the administrator for the password settings. Only a user with administrator rights can then reset the user ID with a new initial password. If the access is denied for the administrator due to the number of invalid tries, a procedure can be obtained from your IBM representative to reset the administrator’s password. The password for each user account is forced to adhere to the following rules:

• The length of the password must be between six and 16 characters. • It must begin and end with a letter. • It must have at least five letters. • It must contain at least one number. • It cannot be identical to the user ID.

mkuser

This command creates a user account that can be used with both DS CLI and the DS GUI. In the example below we create a user called <DS-user>, who is in the admin group. His temporary password is <password>. chpass

This command lets you change two password rules: password expiration (days) and failed logins allowed. In the example below we change the expiration to 365 days and 5 failed logon attempts. If you set both values to zero, then passwords never expire and unlimited logon attempts are allowed. This is not recommended.

ESS/DS CIM Agent configuration

If the storage system supported is an ESS or DS, install the DS Open API CIM Agent on a system with access to both the production and backup systems via HTTP. For the installation procedure, refer to the IBM TotalStorage DS Open Application Programming Interface Reference, GC35-0493. This manual also contains the procedure for configuring the agent to run in non-SSL mode, if this has not already been done. In addition, refer to the appropriate CIM Agent and TSM for ACS README files for any additional information.

The DS Open API CIM Agent can be co-located with the CIM Client. In this case, installation on the backup system is preferred, because installing it on the production system can be detrimental due to the system loading imposed by Java on the CIMOM.

The CD image for the DS Open API CIM Agent, as well as updates and other information, can be obtained at the following URL:

http://www.ibm.com/servers/storage/support/software/cimdsoapi/installing.html

TSM for ACS Workshop CIM Agent Setup - CIM Agent 5.1.0.x


Note: The DS Open API CIM Agent requires the prior installation of the ESS Copy Services Command Line Interface (CLI) if an ESS 800 storage system is configured. The functions of this package for a DS storage system are performed by the ESS Network Interface (NI).

CIM Agent Setup - CIM Agent 5.1.0.x

Verifying the CIM agent 5.1.0.x installation on AIX

This subsection includes the steps necessary to verify that your CIM agent is installed correctly on your AIX operating system. To verify correct CIM agent installation follow these steps:

1. Verify the installation of the service location protocol (SLP). Open a Command Prompt window and type the following command to verify that SLP is started:

# ps -ef | grep slpd

If the SLP daemon is started, the following output is displayed:

root 26438 26986 0 12:36:44 pts/3 0:00 grep slpd

daemon 20730 1 0 12:51:47 - 0:00 /opt/IBM/cimagent/slp/slpd

2. Verify the installation of the CIM agent. Check that the CIMOM daemon is installed and started by typing the following command: # ps -ef | grep CIMOM

The following is a sample output:

root 32518 1 0 15:52:05 - 0:08 /opt/IBM/cimagent/ibmjava131

/jre/bin/java -Xms128m -Xmx256m -cp /opt/IBM/cimagent/lib/xml4j-4_0_5/

xercesImpl. jar:/opt/IBM/cimagent/lib/xml4j-4_0_5/xmlParserAPIs.jar:/op

t/IBM/cimagent/ibmjava131/jre/lib/ext/ibmjsse.jar:/opt/IBM/cimagent/lib

/JCE/IBMJCEfw.jar:/opt/IBM/cimagent/lib/JCE/IBMJCEProvider.jar:/opt/IBM

/cimagent/lib/JCE/local_policy.jar:/opt/IBM/cimagent/lib/JCE/US_export_

policy.jar:/opt/IBM/cimagent/lib/JCE/ibmpkcs.jar:/opt/IBM/cimagent/ibmj

ava131/jre/lib/rt.jar:/opt/IBM/cimagent/ibmica.jar com.ibm.cimom.CIMOM

root 28838 23968 0 15:57:21 pts/0 0:00 grep cimom

3. Start the CIMOM, if it is not started, by typing the following command:

# <dest-path>/startcimom

where <dest-path> is the destination directory where the CIM agent is installed.

Configuring the CIM agent 5.1.0.x on AIX

This subsection includes the steps to configure the CIM agent after it has been successfully installed. This task is performed after successful installation of the CIM agent. This installation program performs the following tasks:

• Copies the directories and files from the CIM agent CD-ROM into the chosen destination directory



• Updates some script files using the selected destination • Compiles the MOF files, creates the persistent subdirectory in the destination

directory • Generates a certificate called truststore in the destination directory, only for the

server Note: For a client installation, you must copy this certificate from the server and install it in the destination directory on the client machine if you intend to run in secure mode.

Steps:

Perform the following steps to configure the CIM agent: Note: In addition to the configuration steps below, you can use the modifyconfig

command to change the configuration of some of the parameters that were configured during installation. You can change the CIM agent port value, protocol (HTTP/HTTPS), and enable or disable the debug option.

1. Configure the CIM agent for each storage unit that the CIM agent can access. a Type the following command:

# <dest-path>/setdevice

where <dest-path> is the destination directory where the CIM agent is installed. The following is a sample output:

Application setdevice started in interactive mode

To terminate the application enter: exit

To get a help message enter: help

>>>

b Obtain an IP address, user name, and password for each storage unit that the CIM agent will manage.

c Type the following command for each storage unit:

>>>addess <9.111.111.111> <essuser> <esspass>

where

9.111.111.111 represents the IP address of the storage unit essuser represents the DS Storage Manager user name esspass represents the DS Storage Manager password for the user name The following is a sample output:

A provider entry for IP 9.111.111.111 successfully added

d Type the following command for each storage unit server that is configured for Copy Services:

>>> addessserver <9.111.111.111> <essuser> <esspass> <9.222.222.222>

where

TSM for ACS Workshop CIM Agent Setup - CIM Agent 5.1.0.x


9.111.111.111 represents the IP address of the storage unit essuser represents the DS Storage Manager user name esspass represents the DS Storage Manager password for the user name 9.222.222.222 represents the alternate IP address of the storage unit

Note: Specifying an alternate IP address is optional. The alternate IP address is used if a connection cannot be made using the primary IP address.


An essserver entry for IP 9.111.111.111 successfully added

where

9.111.111.111 is the IP address. e Type the exit command to exit the CIMOM configuration program. A file

named provider-cfg.xml is created in the destination directory. 2. Once you have defined all of the storage unit servers, you must stop and start the

CIMOM to make the CIMOM initialize the settings for the storage unit servers. Because the CIMOM collects and caches the information from the defined storage units at startup time, the CIMOM might take longer to start the next time you start it.

3. Configure the CIMOM for each user that you want to have authority to use the CIMOM by running the CIMOM configuration program.

During the CIM agent installation, the default user name to access the CIM agent CIMOM is created. The default user name is “superuser” with a default password of “passw0rd”. You must use the default user name and password when using the setuser command for the first time after installation. Once you have added other users, you can initiate the setuser command using a user name that you defined instead of the default. a Start the CIMOM, if it is not started, by typing the following command:

# <dest-path>/startcimom


b Type the following command:

# <dest-path>/setuser -u superuser -p passw0rd


The following is a sample output: Application setuser started in interactive mode

To terminate the application enter: exit

To get a help message enter: help

>>>

Restriction: You cannot delete or modify the current user logged in using the setuser command.

c Obtain a user name and password for each user that can manage the CIMOM. Type the following command for each user:

>>>adduser <cimuser> <cimpass>



where cimuser represents the new user name to access the CIM agent CIMOM cimpass represents the password for the new user name to access the CIM agent CIMOM.


An entry for user cimuser successfully added

where cimuser is your new user name. d When you have completed adding new users to access the CIM agent

CIMOM, issue the exit command. e You can change the default password for ″superuser″ by starting the setuser

command for a user that you added in step c above. Then issue the following command to change the password:

>>>chuser superuser <newpasswd>

where newpasswd is the new password for the superuser. Or, delete the superuser by issuing the following command:

>>>deluser superuser

Type the exit command to exit the CIMOM configuration program. If you are able to perform all of the configuring tasks successfully, the CIM agent has been successfully installed on your AIX operating system.

CIM Agent User Setup - CIM Agent 5.1.0.x

� After installing the CIM agent, a default CIM-user is defined as: username: superuser password: passw0rd (with a zero instead of o) You can add a new CIM-user with the following command: /opt/IBM/cimagent/setuser -u superuser -p passw0rd

>>> adduser <CIM-user> <password>

� This CIM-user is used by TSM for ACS to connect to the CIM Agent and the

CIM-user is the one you need to specify in the TSM for ACS profile parameter COPYSERVICES_USERNAME

TSM for ACS Workshop CIM Agent ESS/DS configuration – CIM Agent 5.1.0.x


CIM Agent ESS/DS configuration – CIM Agent 5.1.0.x

� Configure the DS6000/DS8000 with the CIM agent: After creating the DS-user you can create the DS entry in the CIM Agent configuration. For the definition, you have to use the command: /opt/IBM/cimagent/setdevice

>>> addessserver <DS-IP-name> <DS-user> <password>

where <DS-user> is the user you can use for the DS Web Interface connection

� Configure the ESS 800 with the CIM agent: After creating the ESS-user you can create the ESS entry in the CIM Agent configuration. For the definition, you have to use the command: /opt/IBM/cimagent/setdevice

>>> addessserver <ESS-IP-name> <ESS-user> <password>

>>> addess <ESS-IP-name> <ESS-user> <password>

where <ESS-user> is the user you can use for the ESS Web Interface (ESS Storwatch) connection

Configuring the CIM agent to run in insecure mode (HTTP vs. HTTPS)

Some vendor software might not be capable of communicating with the CIM agent in a secure fashion. If you wish to, you can still use this vendor software by configuring the CIM agent to run with only basic user and password security. Perform the following steps to configure in insecure mode:

1. Type the stopcimom command in the destination directory to stop the CIMOM. 2. Find the cimom.properties file in the target directory and edit it with a tool such

as vi editor. The following is an example:

ServerCommunication=HTTP

Port=5988

DigestAuthentication=False

3. Type the startcimom command to restart the CIMOM. 4. Verify that the server started on Port 5988 by opening the cimom.log file.



CIM Agent Setup - CIM Agent 5.2.x – 5.4.x

Verifying the CIM agent 5.1.0.x installation on AIX

This section provides the steps to verify that your CIM agent is installed correctly on your AIX operating system.

To verify correct CIM agent installation follow these steps:

1. Verify the installation of the service location protocol (SLP). Open a Command Prompt window and type the following command to verify that SLP is started: # ps -ef | grep slpd

If the SLP daemon is started, the following output is displayed: root 13760 15324 0 13:20:48 pts/0 0:00 grep slpd

daemon 18546 1 0 Apr 10 - 0:01 /opt/IBM/dsagent/slp/sbin/slpd

2. Verify the installation of the CIM agent. Check that the cimserver daemon is installed and started by typing the following command: # ps -ef | grep cimserv

The following is a sample output: root 13758 15324 0 13:20:09 pts/0 0:00 grep cimserv

root 14758 1 0 13:16:55 - 0:34 [cimserve]

3. You must set environment variables before you can issue any of the CIM agent management commands: source <dest-path>/config/envConf


4. Start the CIM agent, if it is not started, by typing the following command: # startagent

Note: If you are currently residing in /cdrom/AIX, you must exit the /cdrom directory by typing cd /. You cannot unmount the CD if you are still residing in /cdrom/AIX. When you are finished with the CIM agent CD, you can release the CD with the umount command, for example: # umount /dev/cd0

# umount /cdrom

If you are able to perform all of the verification tasks successfully, the CIM agent has been successfully installed on your AIX operating system.

TSM for ACS Workshop CIM Agent Setup - CIM Agent 5.2.x – 5.4.x


Configuring the CIM agent 5.1.0.x on AIX

This section includes the steps to configure storage units and user accounts for CIM agent after it has been successfully installed. You can change the CIM agent port value, protocol (HTTP/HTTPS), and enable or disable the debug option. Steps: Perform the following steps to configure ESS and DS user accounts for the CIM agent: 1. Ping each ESS and DS that the CIM agent will manage by typing the following

command: a. Open a command prompt window.

b. Issue a ping command; for example:

# ping 9.11.111.111

where 9.11.111.111 is an ESS processor complex or DS master console IP address.

c. Check that you can see reply statistics from the IP address. The following is example output: Pinging 9.11.111.111 with 32 bytes of data:

Reply from 9.11.111.111: bytes=32 time<10ms TTL=255




If you see other messages that indicate that the request has timed out, see your Network Administrator for help on establishing network connectivity before you configure storage units.

2. Type the following command to configure the CIM agent for each ESS or DS server that the CIM agent can access: dscimcli mkdev <ip> -type <type> -user <user> -password <password>

ip

For an ESS configuration server, this is the IP address of the primary processor card. For an ESS copy services server, this is the IP address of the primary copy services server. For a DS server, this is the IP address of the primary hardware or software master console (HMC/SMC). type

For an ESS configuration server, this is ess.



For an ESS copy services server, this is esscs. For DS, this is ds. user/password

For an ESS configuration server, this is the specialist or ESSCLI user name and password. For an ESS copy services server, this is the specialist or ESS copy services server user name and password. For a DS server, this is the storage manager GUI or DSCLI user name and password.

3. After you have defined all of the ESS and DS servers, type the following command to verify that the devices were correctly added and have successfully connected: dscimcli lsdev -l

The following is example output: Type IP IP2 user name Storage Image Status Code Level Min Codelevel

==== =============== ======== ================ ========== ========= ============

DS 9.11.111.111 - admin IBM.2107-1234567 successful 5.1.0.309 5.1.0.309

If the status is failed, there was a failure when the CIM agent attempted to connect to the storage device. If the CIM agent is unable to connect during mkdev, an error is returned immediately. If the device shows as failed in lsdev -l, it is likely that you added the device earlier (for example, during the installation wizard) and the connection is now failed. To ensure that your storage device’s management interface is functioning, use the command line interface (ESSCLI or DSCLI) or graphical interface (ESS Specialist or DS Storage Manager) to attempt to log into the device from the server where the CIM agent is hosted. If you are unable to connect via the native command line interface or graphical interface, there is likely an error in the network or the storage device. If you are able to connect via the native interfaces, there is likely an error in the CIM agent. Contact your service representative for assistance. Note: Because the CIM agent periodically collects and caches information from the defined storage units, the CIM agent might periodically take longer to respond to requests; for example, immediately after adding a new storage unit.

4. Configure the CIMOM for each user that you want to have authority to use the CIMOM by running the CIMOM configuration program. During the CIM agent installation, the default user name to accesses the CIM agent CIMOM is created. The default user name is “superuser” with a default password of “passw0rd”. You must use the default user name and password when you use the mkuser command for the first time after installation. After you have added other users, you can initiate the mkuser command using a user name that

TSM for ACS Workshop CIM Agent Setup - CIM Agent 5.2.x – 5.4.x


you have defined instead of using the default. a. Start the CIM agent, if it is not started, by typing the following command:

# startagent

b. Type the following command to create the new user: # dscimcli mkuser cimuser -password cimpass

The following is example output: User created.

Restriction: You cannot delete or modify the current user using the mkuser

command.

c. You can change the default password for ″superuser″ by starting the mkuser

command for a user that you added. Issue the following command to change the password: # dscimcli chuser superuser -password passw0rd -newpassword <newpassword>

where newpasswd is the new password for the superuser.

d. You can delete the superuser by issuing the following command: # dscimcli rmuser superuser

e. Type the exit command to exit the CIMOM configuration program.

If you are able to perform all of the configuring tasks successfully, the CIM agent has been successfully installed on your AIX operating system.



CIM Agent User Setup - CIM Agent 5.2.x – 5.4.x

� After installing the CIM agent, a default CIM-user is defined as: username: superuser password: passw0rd (with a zero instead of o) You can add a new CIM-user with the following commands started as root: . /opt/IBM/dsagent/config/envConf

dscimcli mkuser <CIM-user> -password <password>

� This CIM-user is used by TSM for ACS to connect to the CIM Agent and the CIM-user is the one you need to specify in the TSM for ACS profile parameter COPYSERVICES_USERNAME

CIM Agent ESS/DS configuration – CIM Agent 5.2.x – 5.4.x

� Configure the DS6000/DS8000 with the CIM agent: After creating the DS-user you can create the DS entry in the CIM Agent configuration. For the definition, you have to use the command: . /opt/IBM/dsagent/config/envConf

dscimcli mkdev <DS-IP-name> -type ds –user <DS-user> -password <password>

where <DS-user> is the user you can use for the DS Web Interface connection

� Configure the ESS 800 with the CIM agent: After creating the ESS-user you can create the ESS entry in the CIM Agent configuration. For the definition, you have to use the command: . /opt/IBM/dsagent/config/envConf

dscimcli mkdev <DS-IP-name> -type ess –user <ESS-user> -password <password>

dscimcli mkdev <DS-IP-name> -type esscs –user <ESS-user> -password <password>

where <ESS-user> is the user you can use for the ESS Web Interface (ESS Storwatch) connection



Unit 4

User Interface

Unit Objectives


• Describe the user interface of TSM for ACS

TSM for ACS is split into the two components splitint and tdphdwdb2. While

splitint represents the part controlled by the storage system, which is database

independent, tdphdwdb2 is the DB2 dependent part and the user interface.

User Interface

� TSM ACS for mySAP provides a DBA administration tool for backup and

restore / recovery of DB2 UDB databases. � Backups with TSM ACS can be scheduled in a regular basis � Restores with TSM ACS are interactively menu driven processes which can

not be scheduled. – The main menu for the restore is presented from which the SAP database

administrator can select the backup to be restored: IBM Tivoli Storage Manager for Advanced Copy Services Data Protection for FlashCopy Devices for mySAP(R) on DB2

(TDPHDWDB2)

FlashCopy Backup utility for IBM Tivoli Storage Manager

- Version 5, Release 4, Level 2.0 for AIX (32 Bit) -

Build: 354 generated at 00:56:08 on Jul 30 2008

(c) Copyright IBM Corporation, 2000, 2007, All Rights Reserved.

--------------------------------------------------------------------------------

B a c k u p H i s t o r y f o r E S E D a t a b a s e

SystemID: AS1

--------------------------------------------------------------------------------

Backup timestamp(ID) Type TSM FlashCopy RTime(min) 1st active Log

--------------------------------------------------------------------------------

[1] - 03.09.2008 21:44:55 DB online ok running 32.5 S0001787.LOG

[2] - 02.09.2008 14:08:01 DB offline ok invalid

[3] - 02.09.2008 13:53:05 DB online - invalid

[4] - 02.09.2008 13:41:17 DB online - invalid

[5] - 02.09.2008 11:27:12 DB N/A - invalid

[d] - show details

[r] - refresh display

[o] - choose from older backups

[#] - restore the database with line number #

[f] - show FlashCopy backups only (target set state IN_USE)

[x] - exit tdphdwdb2

Enter your selection:

Unit 4: User Interface TSM for ACS Workshop


Functions

Functions of the TSM for ACS command 'tdphdwdb2'

TSM for ACS provides the command tdphdwdb2 to run functional requests for the storage system:

• FlashCopy source volumes of a storage system containing the DB2 database objects (such as tablespace containers) for a full backup to target volumes of a storage system

• (FlashBack) Restore target volumes of a storage system, containing the DB2 database objects of a previously taken FlashCopy Backup, in reverse to the source volumes of a storage system on the production system.

• Restart failed offloaded TSM backups • Withdraw the FlashCopy source/target volume relationship after the backup

has been performed on the backup system or before starting a new FlashCopy Backup.

• Withdraw_Force to run the unmount function and withdraw the FlashCopy source/target volume relationship after the backup has been performed on the backup system or before starting a new FlashCopy Backup. It differs from 'withdraw' in that the states of the BSI and PSI are ignored.

• Query whether the setup will allow running the FlashCopy. The query function is planned only for setup checks and will not subsequently be used in the normal backup procedures.

• Unmount file systems and vary off volume groups • Inquire about the status of the backup cycles. • (TS_)Inquire about the status of one or all target sets • Modify the copy rate of an SVC FlashCopy process.

The storage-system-specific part of TSM for ACS and its functions have been

designed for use within tdphdwdb2.

TSM for ACS Workshop User Interface


All functions are called from tdphdwdb2 and are shown in following picture.

Syntax of the TSM for ACS command 'tdphdwdb2'

Figure 8: Syntax Diagram

new with TSM ACS 5.4.2.0



The following functions are available with TSM ACS component 'tdphdwdb2' � backup -t flashcopy (can only be issued on the backup system)

– creates a new backup if latest backup status is valid – creates on the PS a file list of all DB2 UDB DB files and identifies on the PS

based upon this file list the ESS/DS (source) volumes and performs the FlashCopy; creates on the BS VGs and mounts the file systems

– performs a DB2 UDB database backup on BS using TSM for ERP

� flashcopy (can only be issued on the backup system) – creates a new backup cycle if latest backup cycle is valid – creates on the PS a file list of all DB2 UDB DB files and identifies on the PS

based upon this file list the ESS/DS (source) volumes and performs the FlashCopy; creates on the BS VGs and mounts the file systems

� restart_backup (can only be issued on the backup system) – performs a restart of a previously failed DB2 UDB database backup on BS

using TSM for ERP

� backup -t online | offline (can only be issued on the production system) – performs a DB2 UDB database backup on PS using TSM for ERP without

using FlashCopy functionality

The following functions are available with TSM ACS component 'tdphdwdb2' � restore (can only be issued on the production system)

– interactively menu driven process – checks for valid backups taken with TSM ACS (TSM backup types and

FlashCopy backup types) – in case of TSM backup type to be restored, call DB2 UDB restore command

which calls DP for mySAP – in case of FlashCopy backup type to be restored, call TSM ACS component

splitint to perform an FlashCopy from the ESS/DS (target) volumes back to the ESS/DS (source) volumes

– creates a new restore cycle (only in case of FlashBack Restore)

� withdraw (can only be issued on the backup system) – unmounts the file systems and exports VGs, removes the AIX hdisks/vpaths

(rmdev) and withdraws the ESS/DS source/target volume relationship

� unmount (can only be issued on the backup system) – unmounts the file systems and exports VGs, removes the AIX hdisks/vpaths

(rmdev)

TSM for ACS Workshop User Interface


The following functions are available with TSM ACS component 'tdphdwdb2'

� configure (can only be issued on the production system) – creates the TSM ACS socket servers on the production system – stores the passwords which are required to run

- remote DB2 API calls on the production system from the backup system - CIM Agent requests (within the query/backup/flashcopy/withdraw functions) to the CIM Agent

� password – stores the passwords which are required to run

- remote DB2 API calls on the production system from the backup system - CIM Agent requests (within the query/backup/flashcopy/withdraw functions) to the CIM Agent

� query (can only be issued on the backup system) – allows to run partially the flashcopy function (without FlashCopy etc.) ;

DB is not be put into suspend mode � inquire

– shows information about all backup and restore cycles or about a specific backup and restore cycle (based on BSN backup sequence number or DP for mySAP backup timestamp)

� ts_inquire – shows information about all target sets and their states

Note: - backup (FlashCopy Backup), flashcopy, withdraw and unmount change the PSI and BSI status - restore (FlashBack Restore) change the RSI status (see backup and restore cycle); example for a function call: cd /db2/<SID>/dbs/

./tdphdwdb2 –p /db2/<SID>/dbs/init<SID>.fcs –f flashcopy



Unit 5

FlashCopy Backup

Unit Objectives


• Describe the FlashCopy Backup process in detail

FlashCopy Backup

The backup function is used to perform a backup of the SAP DB2 UDB database.

If no option is given, tdphdwdb2 performs a backup of FlashCopy with unmount and/or withdrawal of the target volumes. The default cleanup work depends on the FLASHCOPY_TYPE specified in the TSM for ACS profile. In the case of NOCOPY, an unmount and withdrawal will be done. In the case of COPY or INCR, only an unmount will be done.

You can specify the type option -t flashcopy and the parameter nounmount in

conjunction with nowithdraw, which prevents the unmount and withdrawal after the backup. You can further specify the parameter unmount with the parameter nowithdraw, which unmounts the targets after the backup but does not withdraw them. These options are only possible when the function is initiated on the backup system.

When performing a Backup with option FlashCopy and with FLASHCOPY_TYPE 'COPY' or 'INCR', you will get a point-in-time copy of your production database. You can use this point-in-time disk copy for a later FlashCopy Restore (FlashBack Restore) when the copy process in the background is finished.

Unit 5: FlashCopy Backup TSM for ACS Workshop


Figure 9: TSM for ACS for mySAP - FlashCopy Backup

Once initiated on the backup system (either without any options or with type option

-t flashcopy [no/unmount] [no/withdraw]), the backup function of tdphdwdb2 will perform the following actions:

• use DB2 remote connection to get the filenames of the relevant database files from the DB2 production system

• send a message to the TSM ACS acsprole process (started on production

system via /etc/inittab) which then starts a new splitint process on the production system.

• splitint started with the list of files to get the disk volumes which will be the candidates for the subsequent FlashCopy

o checks the status of the previous backup cycle to determine whether a new backup cycle can be started. If the status of a previous backup is other than PSI_FLASHCOPY_QUERY or PSI_UNMOUNT_DONE (in the case of a FLASHCOPY_TYPE of COPY or INCR), or PSI_WITHDRAW_DONE (in the case of a FLASHCOPY_TYPE of

NOCOPY), splitint will terminate with RC != 0 to indicate to tdphdwdb2 that the previous request failed or file systems are still mounted. As a consequence, tdphdwdb2 will also fail. The user will be asked to first use the withdraw function.

Note:

In case multiple target sets are specified in the TSM for ACS target volumes file, this check will be done for volumes of the target set used, depending on

TSM for ACS Workshop FlashCopy Backup


� whether specific or automated target selection is desired, and � the outcome of the selection algorithm

o checks the RSI (Restore Status Indicator) for a still-active background copy initiated by a FlashBack Restore. If the value is

� RSI_START: terminate (a FlashCopy of a previous FlashBack Restore has not yet completed)

� RSI_INVALID: issue a warning, reset the RSI, and continue � anything else: continue

o starts a new backup cycle • send a message to the TSM ACS socket servers on the production system to

put the DB2 production database in 'write suspend' mode.

• prepare the 'flashcopy' call of splitint with the list of disk volumes that will be the candidates for the subsequent FlashCopy. The flashcopy request is

based on information tdphdwdb2 will find in the profile it is using (NOCOPY/COPY/INCR).

• on the production system, perform, based on the file list received by

tdphdwdb2, a FlashCopy for all the disk volumes (source) over which the various files are spread

• send a message to the TSM ACS socket servers on the production system to put the DB2 production database in 'write resume' mode.

• and after calling splitint with a flashcopy request: o check the return code from splitint:

if nonzero, terminate with error messages

if 0, continue

• On the backup system, start the FlashCopy agent process on the backup system to observe the FlashCopy in the storage system (only if the FlashCopy type is set to 'COPY' or 'INCR')

• perform the following task to allow files (on the target volumes) to be read:

cfgmgr -v -l fsci/scsi ...

1. Run 'cfgmgr' to identify the new volumes 2. Import all necessary volume groups if required 3. Mount all necessary file systems 4. Set the status of the current backup cycle to 'PSI_MOUNT_DONE'.

5. return control to tdphdwdb2 with RC=0, which can now call DP for mySAP to back up the files

• check on the backup system for the existence of all database files on so-called

target volumes, which it had asked splitint (with option 'flashcopy') to create using a FlashCopy

• call the db2 backup command, which calls DP for mySAP to back up the database

• after DP for mySAP has finished the backup, call splitint again to unmount file systems, export volume groups, and withdraw target volumes if not prevented with the given options.

• finish the tdphdwdb2 run (remove any lock files).

Unit 5: FlashCopy Backup TSM for ACS Workshop




Unit 6

FlashCopy Restore

Unit Objectives


• Describe the FlashBack Restore process in detail

FlashBack Restore

The restore function can be used to restore and recover the production database. TSM for ACS supports two types of restore:

• Restore from TSM • FlashCopy Restore (FlashBack Restore) from a previously taken FlashCopy

Backup

tdphdwdb2 guides you through the restore and recovery process with a menu driven user interface.

Figure 10: TSM for ACS for mySAP - FlashBack Restore

Unit 6: FlashCopy Restore TSM for ACS Workshop


Once a FlashCopy type backup of the database has been selected on the production system by the administrator for a restore, tdphdwdb2 performs the following tasks as they are depicted in Figure above.

1. Stop the database

2. Call splitint with its flashback function; splitint will a. perform some checks against the production system environment,

display information about the file systems involved and issue the break message IDS1084I to allow either

� stopping before applying any changes to the production system or

� continuing to run with no other intervention possibility up to step 3c

splitint will check:

� the RSI (Restore Status Indicator) for valid values. The administrator will be informed with message IDS1089I in case a previous FlashBack Restore left the system in a state where the administrator needs to decide to continue or to stop the newly started FlashBack Restore, depending on the state.

� whether all source volumes used in the FlashCopy Backup are still assigned to the production system. Although it is unlikely that they were unassigned and given to another system,

splitint will check and terminate if the administrator cleaned up the production system at the AIX disk storage management level (AIX device and vpath removed). If he failed to do the

cleanup, splitint cannot detect this unlikely change and will fail in step 2c, leaving the production system in a damaged state that cannot be fixed by splitint as long the relevant source volume is not reassigned to the production system and can be used there.

Next, splitint issues the break message IDS1084I. This allows the administrator to enter

� 'cont' to continue with step 2b up to step 3c (next break message)

� 'stop' to terminate the FlashBack Restore

The decision should be based on the information displayed up to this point (or written to the restore log).

Prior to this break message splitint displays

� the currently visible file systems on the volume groups which were backed up, via message EEP0293I

� the file systems which will be restored, via message EEP0294I; these are the file systems it had backed up with the FlashCopy

TSM for ACS Workshop FlashBack Restore


function and that will be made available again when running step 2c) and 2d) of the FlashCopy Restore (see below)

If changes to the storage structure of the DB volume groups have been applied since the FlashCopy Backup, the administrator might be required to redo those changes as discussed below. Possible storage structure changes are

� adding/removing a volume to/from a VG (including unassigning the volume)

� creating/removing file systems (to add/drop tablespaces) � extending file systems (e.g. to add new tablespaces)

The administrator must make his decision (for a 'cont' or 'stop' reply) based on the requirement that

� all source /target volumes used in the FlashCopy Backup still be available and not in use elsewhere.

� resources (file systems and the underlying LVs/VGs/volumes) be available for the DB at a later point in time (step 3d) during the rollforward recovery; this recovery will be done as specified within the menu when the FlashBack Restore was started ; in step 3c, a breakpoint message (IDS2522I) will allow the administrator to manually perform reasonable AIX disk storage management activities after step 2d has been executed.

The 'cont' reply can be given:

� if no changes to the file systems were done and the file systems and sizes listed under EEP0293I and EEP0294I are therefore the same (the normal restore situation)

� if tablespaces in new or extended file systems were created; before the next break message (see step 3c) has been answered to continue, in order to start with the rollforward recovery, all AIX definitions must be manually redone as they were after the FlashCopy Backup

� if system resources (file systems and the underlying LVs/volume(s) have been removed, but the volume(s) they resided on are still assigned to the production system and can still be used there; after the FlashBack Restore, the system resources will appear as they were at FlashCopy Backup time.

The 'stop' reply must given if the source volumes on which a previously available file system (listed under EEP0294) was allocated

� are already in use in another VG (which was not a VG of the DB backup) or

� have been assigned to and are being used in another system.

Unit 6: FlashCopy Restore TSM for ACS Workshop


The only way to use the FlashBack Restore is to make all the original source volumes available to the production system again. Make sure that once they are assigned back to the production system they are not used in another VG when running the FlashBack Restore; the FlashCopy in step 2c would fail, leaving behind an unusable AIX disk storage management environment.

b. disable production system resources � unmount the file systems making up the database � vary off the VGs of the database � export the VGs of the database

c. perform FlashBack � start the FlashCopy using the source volumes of the FlashCopy

Backup as the target volumes and the target volumes of this run as the source volumes

� if this FlashCopy starts and then fails

� the RSI will be set to RSI_INVALID and � the FlashBack Restore will terminate with error

message EEP0302E � if the FlashCopy is started successfully, the FlashCopy agent on

the production system will be started with RSI value RSI_START

Note:

Once the background copy running in the storage system has completed, the FlashCopy agent will set the RSI to

RSI_DISKONLY.

d. enable production resources used by the database

� importvg (varyonvg) the VGs � mount the file systems

� give control back to the calling tdphdwdb2 component 3. Start the rollforward recovery (only if the option rollforward is selected):

a. start the database manager

b. initialize the database with db2inidb as mirror only in the case that a FlashCopy without backup to TSM was done at backup time

c. display the breakpoint message IDS2522I and continue when the ENTER key has been pressed.

Notes:

i. This breakpoint will allow the administrator to provide the AIX changes (such as add volumes, ..., file systems) as was done after the FlashCopy Backup, for the objects now subject to the restore.

ii. Volumes and LVs of the production system which were not in the VGs of the database at FlashCopy Backup time need special administrator attention.

d. start the rollforward recovery with db2 rollforward db



Unit 7

Backup and Restore Cycle

Unit Objectives


• Describe the concept of Backup and Restore Cycles

This section describes the role of a backup and a restore cycle including the control elements such as PSI, BSI and RSI together with the FlashCopy agent.

Using TSM for ACS for backup purposes will primarily allow first to FlashCopy source volumes to target volumes on a production system and make the target volumes available on a backup system. There, TSM for ACS will import volume groups and mount the file systems. After the backup has been done, the disk environment on the backup system can be restored to its initial state with respect to the DB2 database files, in which

• no file systems remain mounted • no volume groups remain imported and • no logical volumes remain available (only if the FLASHCOPY_TYPE is

NOCOPY).

TSM for ACS uses a progress status indicator (PSI) to control the status of the involved volumes and of the AIX storage management environment left once a TSM for ACS function completed, thus allowing the next TSM for ACS function to be started only when the PSI has a proper value.

A special FlashCopy Restore (FlashBack Restore) is integrated in this product, which integrates the FlashCopy target volumes (created with the COPY or INCR option) in a disk-to-disk restore process as long as those target volumes are still in the state they were in after successful completion of the FlashCopy operation from the respective source volumes. The background copy within the storage system has been completed.

Backup Cycle

In order to monitor on the backup system the status of the target volumes (such as mounted file systems) involved in a backup and to run controlled tdphdwdb2 requests, TSM for ACS will establish, for each new FlashCopy Backup request, a new backup cycle after checking whether a preceding request has left the disk environment of the backup system in a state that a new tdphdwdb2 can be started and completed again. If

Unit 7: Backup and Restore Cycle TSM for ACS Workshop


TSM for ACS encounters a situation where a new tdphdwdb2 will fail, it will terminate this request, asking the database administrator first to

• check the procedure setup, or • recover from an unexpected failure within the tdphdwdb2 run (such as a power

failure) that left the disk environment in a state that must be cleaned up.

A new FlashCopy backup request, creating a new backup cycle, can be successfully initiated only if the following two conditions are fulfilled:

1. The preceding backup cycle successfully terminated with the required TSM for ACS function according to the FLASHCOPY_TYPE value as follows:

o In the case of NOCOPY, the withdraw function (sets the PSI to PSI_WITHDRAW_DONE) or

o In the case of INCR or COPY, the unmount function (sets the PSI to PSI_UNMOUNT_DONE). In addition to the completed backup cycle, a background copy must have completed. The BSI value is either BSI_DISKONLY or BSI_DISKANDTAPE

2. In the case of a FlashBack Restore that started a restore cycle within the preceding backup cycle, the restore cycle has terminated completely (RSI_DISKONLY).

Such a restore cycle can only be seen when a backup with the FLASHCOPY_TYPE value of INCR or COPY has been used for a restore (FlashBack Restore).

A backup cycle is identified with a unique backup sequence number (BSN); within a specific backup cycle. Control elements are used such as

• a PSI to record the status of the used source/volume pairs and the status of the AIX storage management environment on the backup system

• a BSI to record the status of a backup object (FlashCopy and/or TSM type) with respect to its usability for a future restore

• a RSI to record the usability of a restored FlashCopy type object with regard to its progress and usability for a new FlashCopy Backup following a FlashBack Restore.

TSM for ACS Workshop Backup Cycle


Possible values for the PSI, BSI and RSI are shown below:

• PSI (Progress Status Indicator) o PSI_PREPARE_FLASHCOPY 0 o PSI_FLASHCOPY_QUERY 1 o PSI_FLASHCOPY_STARTED 2 o PSI_FLASHCOPY_DONE 3 o PSI_MOUNT_STARTED 4 o PSI_MOUNT_DONE 5 o PSI_UNMOUNT_DONE 6 o PSI_WITHDRAW_STARTED 7 o PSI_WITHDRAW_DONE 8

• BSI (Backup Status Indicator) o BSI_START S o BSI_DISKANDTAPE B o BSI_TAPEONLY T o BSI_DISKONLY D o BSI_INVALID I

• RSI (Restore Status Indicator) o RSI_START S o RSI_DISKONLY D o RSI_INVALID I

Backup Cycle (NOCOPY)

Figure 11: Backup Cycle (NOCOPY)



Backup Cycle (COPY)

Figure 12: Backup Cycle (COPY)

Backup Cycle (INCR)

Figure 13: Backup Cycle (INCR)

TSM for ACS Workshop Restore Cycle


Restore Cycle

A restore cycle will be started using the BSN of a backup cycle

• once, using the TSM for ACS 'restore' function, a backup eligible for FlashBack Restore is chosen by the administrator for a restore and

• when, within the further restore process flow, TSM for ACS has been allowed to continue at breakpoint message IDS1084I.

A backup will become eligible for a FlashBack Restore only if

• it was done using the COPY or INCR option within the TSM for ACS profile and

• the FlashCopy agent started within the backup flow has signaled that it detected that the background copy process has been completed for all source/target pairs (the final BSI value must be BSI_DISKANDTAPE or BSI_DISKONLY)

A FlashBack Restore can be performed only with the latest available backup cycle and only if the following conditions exist for the last FlashCopy or FlashCopy Backup request:

• the selected backup is eligible for a FlashBack Restore and • the PSI has, after a successful backup request, been set to

PSI_MOUNT_DONE, PSI_UNMOUNT_DONE, or PSI_WITHDRAW_DONE

A restore cycle is considered to be completed only after the FlashCopy agent started within the FlashBack Restore has detected that all background copies have completed. Once the FlashCopy agent has detected the completion, it will change the initial RSI value (RSI_START) to RSI_DISKONLY. After a successfully terminated TSM for ACS FlashBack Restore you can restart the mySAP database and its applications even if the restore cycle is not yet completed; however you still have to wait for the completion of the restore cycle before the database can again be backed up with TSM for ACS.



Figure 14: Restore Cycle

Backup and Restore Cycle

The BSN of a backup and restore cycle will be

• kept in the TSM for ACS control file (see IDS_CONTROL_FILE parameter of the TSM for ACS profile)

• written to the TSM for ACS run logs

The status of the backup and restore cycles can be checked with TSM for ACS. The last line of the 'inquire' function output shows the latest and current backup and restore cycles with the backup sequence number (BSN), backup status indicator (BSI), restore status indicator (RSI) and progress status indicator (PSI).

The maximum number of backup cycles recorded and kept in the TSM for ACS control file is defined with the BACKUP_MAX parameter in the TSM for ACS profile.

TSM for ACS Workshop FlashCopy Agent


Note: Do not edit/change the contents of the TSM for ACS control file; otherwise, you might hamper or prevent the controlling functions of the TSM for ACS product. Use the TSM for ACS 'inquire' function if you want to see the contents of this control file.

Figure 15: Backup and Restore Cycle

FlashCopy Volume and Backup System Environment Control � a backup cycle starts with a successful TSM ACS call with function

'flashcopy/backup' and ends with an TSM ACS call with function 'withdraw'; each successfully started backup cycle gets a BSN (backup sequence number) assigned. A PSI (progress status indicator) is used by TSM ACS to control whether

– the AIX LVM environment on the backup system can be (re)used for a new backup cycle

– the used target volumes are not in an source/target relationship The PSI, the BSN and other important values like FLASHCOPY_TYPE parameter (COPY or NOCOPY) value are kept in the file specified in IDS_CONTROL_FILE

FlashBack Volume and Production System Environment Control � a restore cycle starts with a successful TSM ACS call 'tdphdwdb2 –f restore' and

ends when the FlashCopy background copy process is finished. � a FlashBack Restore can only be started, if the following conditions are fulfilled

– the FlashCopy Backup run, selected for a FlashBack Restore, was of FLASHCOPY_TYPE COPY / INCR

– the FlashCopy background copy process is finished – the disk backup on the target volumes is still valid

FlashCopy Agent

Within a FlashCopy Backup (if the option COPY or INCR has been used), as well as in a FlashBack Restore, a FlashCopy Agent will be started that will, even if the called TSM for ACS function has already completed, periodically check for the completion



of the background copy processes; once it has detected that all of these processes have completed for all volumes, the FlashCopy agent will

• set the BSI to BSI_DISKONLY or BSI_DISKANDTAPE (in the case of a FlashCopy Backup)

• set the RSI to RSI_DISKONLY (in the case of a FlashBack Restore)

In this way, TSM for ACS knows when the copy process is complete. The purpose of the FlashCopy agent is to ensure that TSM for ACS will not initiate a FlashCopy for a set of source/target volumes as long as the FlashCopy for the same set of source/target volumes in the other direction has not yet completed for all volumes.

The FlashCopy agent will periodically write its results into a log and end its processing once the copy for all source/target pairs has finished.

Monitoring of the FlashCopy Background Copy Process � TSM ACS has implemented a function to monitor the FlashCopy background copy

process. This function is called FlashCopy Agent. It will be started – after TSM ACS has successfully established a FlashCopy in case of a

FlashCopy or FlashCopy Backup request (only in case of FLASHCOPY_TYPE COPY / INCR)

– after TSM ACS has successfully established a FlashCopy in case of a FlashBack Restore

� The FlashCopy Agent will check periodically, if a source target volume relationship is still active for all source and target volumes within the FlashCopy

� If the FlashCopy Agent detects that no source target volume relationships are open any longer, it changes the status of

– the BSI (backup status indicator) in case of a FlashCopy or FlashCopy Backup

– the RSI (restore status indicator) in case of a FlashBack Restore

This monitoring functionality enables TSM ACS to track each FlashCopy and FlashBack and to check, if new FlashCopy Backup and FlashBack Restores can be started.

TSM for ACS Workshop FlashCopy Agent


Section 3: Troubleshooting - TSM for ACS



Unit 8

Troubleshooting

Unit Objectives


• Describe the flow for problem isolation with TSM for ACS • Describe the log / trace files of TSM for ACS • Describe identify and solve problems with TSM for ACS

This unit gives you information on how to resolve errors that might occur during Backup / Restore process. In general, problems related to this product can be distinguished into these categories:

1. Setup and configuration problems 2. Defects of this product or a product it is interacting with

This unit will help you with setup and configuration problems. If an error occurs, always first check the description of the respective error message, issued by the system. Besides being displayed on the screen, the error messages also can be found in log files. For these log files and for a description of the error messages, see Installation and User’s Guide, Appendix B. Data Protection for FlashCopy Devices for mySAP (DB2) Messages. Solve the problem indicated in the error message and retry the action.

Unit 8: Troubleshooting TSM for ACS Workshop


Problem Isolation Flow

During work with TSM for ACS for mySAP you may run into problems during backing up or restoring of your DB2 database. Following graphic will help you to isolate FlashCopy Backup problems:

Figure 16: Problem Isolation - Flow of error analysis

Problem Resolution During Operation

This unit is intended to support isolation of problems which seem to occur without reason during an operation the system has performed successfully many times before. Computers are deterministic machines. If an operation is performed more than once using the same input in the same environment it will produce the same result. Unfortunately today's computing environments consist of a large number of components containing a huge number of volatile parameters often influencing each other. For problem determination the above abstract assessment results in the following very practical actions depending on if the problem seems to be stochastic or if it can be reproduced.

TSM for ACS Workshop Problem Isolation Flow


Reproducible (Repeatable) Problems

If a problem seems to occur repeatable without reason during an operation the system performed successfully many times before, you should ask yourself:

1. What did you change at the setup of TSM for ACS for mySAP ? 2. What did you change at the setup of DP for mySAP ? 3. What did you change at the setup of involved components (DB2, SAP, TSM,

DS Open API CIM Agent, operating system, network, hardware) ? 4. Did you extend your production database (e.g. new datafiles, filesystem,

logical volumes, volume groups) 5. Did you apply any patches or updates to any components in the system ?

If you are sure you changed nothing, ask the same questions to your coworkers and system administrators (DBAs, Storage admin, Network admin, TSM admin, etc.). If this is without satisfying result, it may be an option to observe the last modified time

stamp of the configuration files (init<SID>.fcs, init<SID>.fct, vendor.env, init<SID>.utl, dsm.sys, dsm.opt, /etc/services, /etc/inittab, ...).

The following UNIX command lists you all files in the directory /etc which have been modified during the last 5 days:

find /etc -type f -ctime 5 -print

Also there might be changes to the system that are caused by the system. Samples for such changes are:

• disks are running full. Action: Check with UNIX command df • networks slow down. Action: check for reasons like additional hosts,

additional applications, defects in software or hardware. • TSM server is slowing down. Action: check if additional clients and/or

additional operations have been added. Have a look in the TSM servers activity log.

If you are able to find any changes made to the system roll them back one at a time and try to reproduce the problem. In most cases you will find the one change or set of changes which caused the problem to occur. Now you can decide if you need those changes or can fix their symptoms. Otherwise if you need to implement those changes and can not prevent their symptoms you can now contact support for the effected components.

Random problems

If a problem seems to occur stochastic (sometimes it works, sometimes it does not) without reason during an operation which the system has performed successfully many times before, you should try to find out: What is different when the problem occurs ? Compare the logs of the application in question

(tdphdwdb2_<p/b>_<function>_<timestamp>.log/.trace, splitint_<p/b>_<function>_<timestamp>.log/.trace,

tdpdb2.<SID>.NODE<number>.log, db2diag.log, TSM activity log, etc.) to find



out differences between successful and unsuccessful runs. Try to find a pattern for the occurrence of the problem:

• Is it always occurring at the same time ? • Is it always occurring after you run some other or the same operation ? • Is it always occurring if some other application / process is running in parallel ?

If it is occurring always at the same time review if there are any scheduled processes (virus checker, automatic updates, batch jobs). The above mentioned logs may help you with this.

Log- and Trace-Files

The TSM for ACS commands tdphdwdb2 and splitint create log files when running the various functions (except for inquire and password) on the machine where the functions are initiated. When running the function 'flashcopy', tdphdwdb2 and splitint will have two different logs:

• one recording all the activities on the backup system

• the other recording all the activities for the time splitint is running on the production system

You can find the logs and traces in the directories specified in parameter LOG_TRACE_DIR of the TSM for ACS profile. If no parameter is specified, the logs and traces will be placed in the directory as specified in the parameter WORK_DIR of the TSM for ACS profile. The file naming convention for logs and traces is as follows:

• tdphdwdb2_p_<tdphdwdb2 function>.<date time stamp>.log • tdphdwdb2_p_<tdphdwdb2 function>.<date time stamp>.trace • tdphdwdb2_b_<tdphdwdb2 function>.<date time stamp>.log • tdphdwdb2_b_<tdphdwdb2 function>.<date time stamp>.trace • splitint_p_<splitint function>.<date time stamp>.log • splitint_p_<splitint function>.<date time stamp>.trace • splitint_b_<splitint function>.<date time stamp>.log • splitint_b_<splitint function>.<date time stamp>.trace

where

• _b_ indicates the backup system and • _p_ indicates the production system

TSM for ACS Workshop Troubleshoot the Phases of FlashCopy Backup


Figure 17: Log- and Trace-Files

Troubleshoot the Phases of FlashCopy Backup

A FlashCopy Backup run can be divided into different phases • Initialization Phase • Getresources Phase • FlashCopy Phase • Setrecources Phase • TSM backup Phase

The following subsections describe the different phases and give detailed problem analysis and problem resolution strategies for each phase.

Initialization Phase

In the Initialization Phase tdphdwdb2 is called on the backup system with the function backup or flashcopy. The Initialization Phase can be split into the following steps:

• Check profile parameter • Check DB2 instance on backup system • Check DP for mySAP version • Check DB2 client connection to the production database • Get a list of database files from the production database • Check connection to production system through the TSM ACS acsprole

process running on the production system

� TSM ACS for mySAP

• Profile (init<SID>.fcs)

• Target Volumes File (init<SID>.fct)

• Log files (<program>_<p/b>_<function>_<timestamp>.log)

<program>_<p/b>_<function>_<timestamp>.log

tdphdwdb2 splitint

p – production system b – backup system

backup flashcopy unmount withdraw runagent initsocket

YYYYMMDDHHMMSS

• Traces (<program>_<p/b>_<function>_<timestamp>.trace)

• Switch on trace by setting the profile parameter TRACE to YES

• Sample: tdphdwdb2_p_flashcopy_20060523125702.trace

• Sample: tdphdwdb2_b_backup_20060523133015.log

• Location for these logs is LOG_TRACE_DIR or if not specified the path where the profile resides in



The following pages show the most typical problems which can occur in the Initialization Phase of a FlashCopy Backup.

Figure 18: Problem Isolation – Initialize

Authorization problems

The most typical problem which may reoccur on a regular basis is a problem with the authentication of the db2<sid> user on the backup and/or production system. Passwords must be changed on a regular basis and if this password change is not published to TSM for ACS for mySAP, the next FlashCopy Backup will fail.



Figure 19: Authorization problems

The following 3 reason codes are the most typical ones. (1). RC 24: USERNAME AND/OR PASSWORD INVALID

This error occurs if an incorrect db2<sid> user name is specified in the profile parameter LOGON_HOST_PROD or if the password specified with the

tdphdwdb2 configure function is incorrect. Perform the following steps to verify: Check if the db2<sid> user specified in the profile parameter LOGON_HOST_PROD is the same as the database user on the production system. If the users are identical then the password of the db2<sid> user is no longer correct. Solution: • To solve this problem correct the profile parameter LOGON_HOST_PROD • Change the password stored in the IDS_CONTROL_FILE (.fcp) with the

command: tdphdwdb2 –f configure -p <profile>

or tdphdwdb2 –f password -p <profile>

(2). RC 1: PASSWORD EXPIRED

This error can occur on a regular basis, if the password of the db2<sid> user on the production system or on the backup system is changed. Solution: • To solve this problem change the expired password on the production and/or

backup system with the OS command passwd

...

DB2 instance db2g01 is using DB2 UDB Version 9.1.0.5

Checking DB2 Instance Bitwidth...

DB2 instance db2g01 is running in 64 bit mode.

DP for mySAP Version 5.5.0.found

IDS2005I Start of tdphdwdb2 program at: 09/18/08-10:27:53 .

Backup type flashcopy

DB2 instance db2g01 is a EEE instance.

Default database path: /db2/G01

TCPIP service name: sapdb2G01

Checking for the node directory entry REMG01 ...

---- error report ----

app. message = attach API called

line = 6140

file = dbclient.cpp

SQLCODE = -30082

SQL30082N Attempt to establish connection failed with security reason "24"

("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

IDS2124I Exiting with return code 2.


("PASSWORD EXPIRED"). SQLSTATE=08001

1

2


("UNSUPPORTED FUNCTION"). SQLSTATE=08001 3



• Change the password stored in the IDS_CONTROL_FILE (.fcp) with the command: tdphdwdb2 –f configure -p <profile>

or tdphdwdb2 –f password -p <profile>

(3). RC 17: UNSUPPORTED FUNCTION

This error is the result of a mismatch of the DB2 authentication method on the production database instance and the backup database instance, e.g. on the production database instance the authentication is set to SERVER_ENCRYPT (DB2 database manager parameter AUTHENTICATION) but on the backup server the database directory entry R_<SID> is configured with authentication SERVER.

Perform the following steps to verify: � on PS: db2 get dbm cfg | grep AUTHENTICATION

Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT

� on BS: db2 list db directory

Database 2 entry:

Database alias = R_E01

Database name = E01

Node name = REME01

Database release level = a.00

Comment = the production database

Directory entry type = Remote

Authentication = SERVER

Catalog database partition number = -1

Solution: To solve this problem perform the following 2 steps. 1. On the backup system remove the database directory entries R_<SID> and

R_<SID>_<NNNN> (where <NNNN> must be replaced by all DB2 partition numbers) To uncatalog the above mentioned database directory entries run as db2<sid> the command: db2 uncatalog db R_<SID>

db2 uncatalog db R_<SID>_<NNNN>

2. Set the TSM for HW/ACS profile (.fcs) parameter

DB2_AUTHENTICATION SERVER_ENCRYPT in the DB2 section of the profile and start a new FlashCopy Backup run. This will create new catalog entries R_<SID> and R_<SID>_<NNNN> with the correct authentication method used on the production system.



DB2 is not started on the production system

If a FlashCopy Backup is started while the production database instance is not started, TSM ACS mySAP will fail with the following message (1):

Figure 20: DB2 is not started on the production system

Solution: Start the production database and instance with the db2start command on the production system and restart the FlashCopy Backup command.

TSM ACS mySAP socket server not started on PS

If a FlashCopy Backup is started while the TSM ACS mySAP socket server on the production system is not started, TSM ACS mySAP will fail with the following message (1):

Figure 21: TSM ACS mySAP socket server not started on PS

Solution: Start the TSM ACS mySAP socket server on the production system and restart the FlashCopy Backup command. These socket servers are started through /etc/inittab.

...







DB2 instance db2g01 is a EEE instance.

Default database path: /db2/G01

TCPIP service name: sapdb2G01

Checking for the node directory entry REMG01 ...

IDS2502E Attachment to production DB2 instance REMG01 failed.

Please check if the database manager on production system

is started.


1

...







ERROR: connect() failed

IDS2555E Connection to production system via socket failed...

IDS2124I Exiting with return code 2. 1



0x8000000 storDef was changed prior to rollforward

0x10000000 dms rebalancer is active

0x20000000 TBS deletion in progress

0x40000000 TBS creation in progress

Table 6: DB2 Tablespace States

The most usual states are ‘Backup in progress’ and ‘Offline and not accessible’. Solution: Fix the reason for the state of the tablespace(s) or wait until the backup is finished and restart the FlashCopy Backup again.

TSM for ACS hangs at startup

If a FlashCopy Backup is started while the AIX rpc.lockd service on the production system is not started, TSM ACS mySAP will hang at startup and the log and trace will show the following message (1):

Figure 23: TSM for ACS hangs at startup

Solution: Check on the production system for the existence of the process rpc.lockd with the following command: root@p670-lun1:/>ps -ef|grep rpc.lockd

This should give the output: root 319724 221234 0 21:19:34 pts/3 0:00 grep rpc.lockd

root 839930 106606 0 Oct 03 - 0:00 /usr/sbin/rpc.lockd -d 0

If the rpc.lockd process is not show, then start it with the command: startsrc –s rpc.lockd





Profile p670-lun1/initAB7.fcs

Log file splitint_?_20080819025829.log

Trace file splitint_?_20080819025829.trace

IDS1411I The intended FlashCopy type has a value of 'COPY'.

Function flashcopy

Log file tdphdwdb2_?_20080819025829.log

Trace file tdphdwdb2_?_20080819025829.trace

1

09/18/2008 02:58:30.634 : idscntl.cpp (4814): Exit: function CIdsCntl::InitHWCommonInterface()() rc=0

09/18/2008 02:58:30.634 : idscntl.cpp (4836): Enter: function CIdsCntl::InitLsmLunManager()()

09/18/2008 02:58:30.634 : lunmanager.cpp ( 288): Enter: function CLsmLunManager::lsmInitialize()

09/18/2008 02:58:30.634 : lsmfctfile.cpp ( 182): Enter: function CLsmFctFile::setDataContainerPrefix()

09/18/2008 02:58:30.635 : lsmfctfile.cpp ( 199): Exit: function CLsmFctFile::setDataContainerPrefix()

rc=0

09/18/2008 02:58:30.635 : lsmfctfile.cpp ( 225): Enter: function CLsmFctFile::setTargetIdentifier()

09/18/2008 02:58:30.635 : lsmfctfile.cpp ( 270): Exit: function CLsmFctFile::setTargetIdentifier() rc=0

09/18/2008 02:58:30.635 : lunmanager.cpp ( 376): Exit: function CLsmLunManager::lsmInitialize() rc=0

09/18/2008 02:58:30.635 : lunmanager.cpp ( 457): Enter: function CLsmLunManager::lsmLockLocalRepository()

tdphdwdb2_b_flashcopy_20080918025829.trace



TSM for ACS fails to start splitint on production system

TSM for ACS can fail with the following message (1) or (2) if the TSM ACS acsprole configuration is incorrect:

Figure 24: TSM for ACS fails to start splitint on production system

Solution for message (1): This message indicates that the TSM ACS acsprole process on the production system is not running or that the either profile parameter PROLE_SERVICE_NAME or LOGON_HOST_PROD is set incorrect. 1. Verify that acsprole is running on production system with the following command: root@p670-lun1:/>ps -ef|grep acsprole

This should give the output: root 602334 221234 0 21:32:15 pts/3 0:00 grep acsprole

db2ab7 1036522 1 0 Oct 03 - 0:29 /db2/AB7/dbs/acsprole -p tsmacsdb2 tdpr3db264

acsprole is started through /etc/inittab. Check the /etc/inittab for this process. If acsprole cannot be found in the /etc/inittab you need to start the TSM ACS installation script setup.sh which creates the entry in the /etc/inittab. 2. If acsprole is running, check that the parameter PROLE_SERVICE_NAME has the same value as the value specified in the acsprole –p <servicename> command in the /etc/inittab. This value must also be specified in the /etc/services on production and backup system. This is normally done by calling setup.sh on production system and setupDB2BS on the backup system. 3. Check if LOGON_HOST_PROD is set correctly and correct it if needed. Solution for message (2): This message indicates that the TSM ACS acsprole configuration on the production system is incorrect. Typically this message occurs, if TSM ACS tdphdwdb2 on the backup system send a message to the wrong TSM ACS acsprole process. This can happen if multiple TSM ACS installations are running in parallel on the same production system for different SID. Only one of these TSM ACS installations can use the default PROLE_SERVICE_NAME tsmacsdb2 while the others must be

IDS1035I The IDS control file exists and a new backup cycle entry has been created.

IDS1101I New assigned Backup Sequence Number 00006

IDS1026I Start of splitint on the production system ...

BKI2001E: Socket error while connecting to ProLE at p670-lun1:tsmacsdb2: Connection refused

IDS2124I Exiting with return code 2. 1

IDS1035I The IDS control file exists and a new backup cycle entry has been created.

IDS1101I New assigned Backup Sequence Number 00007

IDS1026I Start of splitint on the production system ...

BKI1016W: The tracefilename '/db2/AB7/dbs/logtraces/acsagent_p_flashcopy_20081003145819.trace' could not

be opened for writing!

BKI4002E: Error during write of file ' /tmp/aaa5pQo7a'. Reason: errno(1) Not owner


2



manually reconfigured to use different service names and TCPIP ports. If wrong acsprole is used to start TSM ACS on the production system, then this acsprole opens a temporary file with the different user which will then fail to change the owner. This results in message (2). Make sure that the different TSM ACS installations are using different service names and TCPIP service ports and that the PROLE_SERVICE_NAME is set correctly according to the changed service names.

Getresources Phase

In the Getresources Phase splitint is started on the production system with the function getresources. The Getresources Phase can be split into the following steps:

• Check the connection to the DS Open API CIM Agent • Get the status and other properties of the source and target volumes through

DS Open API CIM Agent calls • Determine the FlashCopy source volumes (from a list of database files) • Search for a matching target volume for each of the source volumes • Check LVM mirroring configurations for VGs and LVs

The following pages show the most typical problems which can occur in the Getresources Phase of a FlashCopy Backup.

Figure 25: Problem Isolation – Getresources



Unsupported volume group rootvg

• The following error message (1) is displayed, if TSM ACS detects, that at least one of the DB2 database files or the DB2 local database directory is located in a filesystem residing in the rootvg.

Figure 26: Unsupported volume group rootvg

Solution: Correct the DB2 filesystem setup and make sure that it is created according to the filesystem and volume group layout described in Unit 2.

Error while querying volume properties

The following error message (1) is displayed if a target volume specified in the TSM ACS target volumes file (.fct) is specified incorrectly. The typical reason is that there is a misspelling in one of the source or target volumes and these volumes cannot be found in the specified ESS/DS. As shown in this example below, there is a list of 10 DS volumes specified in the .fct file.

Figure 27: Error while querying volume properties

IDS2121I Getting the source volumes ...

Function query

Subfunction performsplit

Backup list /db2/ABI/dbs/work/tdphdwdb2_lst

EEP0143E Unsupported volume group rootvg has been detected.


IDS1028E Splitint ended with errors on the production system.


1


Function getresources_prod


Backup list /tmp/aaa76QoEa

EEP0156I Finding the serial numbers ...

EEP0649E Error while querying volume properties of volume 75123454300.

Please verify that the volume specified in the target volumes file exists.

IDS1401E The target set '1' does not match the source volumes.



1

initAB7.fct

>>> volumes_set_1

TARGET_VOLUME 75123454300 75034614200 10737418240_Bytes










<<< volumes_set_1



On the first look these DS volumes are looking quite good. But at a deeper look e.g. in the target volumes file (init<SID>.fct) it is easier to find the typo. The DS volume 75123454300 has an invalid DS serial number 7512345 which should be 7503461. Solution: Fix this typo in the target volumes file and rerun the FlashCopy Backup.

No target volume found for source volume

The following error message (1) is typically displayed if a source volume (2) does not have a matching target volume in the target volumes file (init<SID>.fct).

Figure 28: No target volume found for source volume

Solution: Add a new target volume to the target volumes file with the same size as the source volume (2). The new target volume(s) must be added in the correct target set (in case that multiple target sets are used, e.g. for AIX LVM mirroring environments). To identify which target set needs the adaption, check the target data container number (1) in the error message. This number must match with the volumes_set_<Number>.


EEP2060W Cannot find a volume in the target data container 1 to match with the source

75034614208.




1

initAB7.fct

>>> volumes_set_1









#TARGET_VOLUME 75034614308 75034614208 10737418240_Bytes

#TARGET_VOLUME 75034614309 75034614209 10737418240_Bytes <<< volumes_set_1

2



LVM mirrored but not specified in .fct

The following error message (1) is pointing to a setup problem with AIX LVM mirroring. It tells that the production database is placed on source volumes which are LVM mirrored to another storage system and that the target volumes file does not reflect this with the profile parameter HARDWARE_ID_LVM_MIRROR. This parameter configures TSM for ACS for mySAP for environments where the production source volumes are LVM mirrored to another storage system.

Figure 29: LVM mirrored but not specified in .fct

Solution: Add the parameter HARDWARE_ID_LVM_MIRROR in the target volumes file in the correct volumes_set_<NUMBER> section. Specify the storage system serial number of the mirrored storage system as the value for this parameter.

IDS1015I Start of splitint program at: 09/19/08-15:09:56 .


Function getresources_prod


Backup list /tmp/baaY6QoEb


IDS1133E Some of the production logical volumes are mirrored. You have to set the

hardware unit ID in the parameter HARDWARE_ID_LVM_MIRROR for the corresponding target

set in the .fct-file '/db2/E01/dbs/initE01.fct'.



1

initE01.fct

>>> volumes_set_1

TARGET_VOLUME 44F22031 - -

TARGET_VOLUME 45022031 - -






<<< volumes_set_1



Not LVM mirrored but specified in .fct

The following error message (1) is pointing to a setup problem with AIX LVM mirroring. It tells that the production database is placed on source volumes which are not LVM mirrored to another storage system but that in the target volumes file the profile parameter HARDWARE_ID_LVM_MIRROR is set. This parameter configures TSM for ACS for mySAP for environments where the production source volumes are LVM mirrored to another storage system. But in this case, the production system is not LVM mirrored.

Figure 30: Not LVM mirrored but specified in .fct

Solution: Remove the parameter HARDWARE_ID_LVM_MIRROR from the target volumes file in the correct volumes_set_<NUMBER> section.


IDS1404I The target set with ID '2' is selected for this run.

Matching pair tgt: <44F22031> src: <11023376> size: <6246_MB>

Matching pair tgt: <45022031> src: <11123376> size: <6246_MB>





IDS1138E The parameter HARDWARE_ID_LVM_MIRROR for the target set '2' is set in

the .fct-file '/db2/E01/dbs/initE01.fcs', but the production logical volumes are not

mirrored.




1

initE01.fct

>>> volumes_set_2

HARDWARE_ID_LVM_MIRROR 22031

TARGET_VOLUME 44F22031 - -






TARGET_VOLUME 47222031 - - <<< volumes_set_2



LVs must have 2 LVM copies

The following error message (1) is pointing to a setup problem with AIX LVM mirroring. The production database is placed on source volumes which are LVM

mirrored across two storage systems. But the logical volumes lve01stale and

lve01stale2 have one LVM mirror copy only. The output (2) shows that both logical volumes are located on one physical volume only.

Figure 31: LVs must have 2 LVM copies

Solution: Create a second copy for each of both logical volumes. Check the output (2) to determine on which storage system the second mirror copy must be created.

EEO0156I Finding the serial numbers ...

EEO0154I <LV ><COPY><PV ><SERIALNR><STATUS >

EEO0154I <loglv22 ><1 ><vpath29 ><31123376>< >

EEO0154I <loglv22 ><2 ><vpath51 ><44822031>< >

EEO0154I <lve01stale ><1 ><vpath8 ><13E23376>< >

EEO0154I <lve01stale2 ><1 ><vpath58 ><48422031>< >

EEO0154I <db2e0100 ><1 ><vpath4 ><11523376>< >

EEO0154I <db2e0100 ><2 ><vpath49 ><44622031>< >

EEO0154I <loglv24 ><1 ><vpath30 ><31223376>< >

EEO0154I <loglv24 ><2 ><vpath53 ><44A22031>< >

EEO0154I <db2e0103 ><1 ><vpath6 ><11723376>< >

EEO0154I <db2e0103 ><2 ><vpath52 ><44922031>< >

EEO0154I <db2e0104 ><1 ><vpath32 ><31423376>< >

EEO0154I <db2e0104 ><2 ><vpath54 ><44B22031>< >

EEO0154I <db2e0105 ><1 ><vpath31 ><31323376>< >

EEO0154I <db2e0105 ><2 ><vpath55 ><44C22031>< >

EEO0160I <lve01stale >

VOLUME GROUP : sapfcl1

COPIES : 1

SCHED POLICY : parallel

STALE PPs : 0

MIRROR WRITE CONSISTENCY: on/ACTIVE

EEO0166E Logical volume lve01stale must have at least 2 copies.

EEO0160I <lve01stale2 >


COPIES : 1


STALE PPs : 0


EEO0166E Logical volume lve01stale2 must have at least 2 copies.




1

2



LVs must not have stale PPs


mirrored across two storage systems. But the logical volumes lve01stale and

lve01stale2 have stale physical partitions on one of the LVM mirror copies. The output (2) shows that both logical volumes have stale PPs on different storage systems.

lve01stale has stale PPs on ESS with ID 22031 and lve01stale2 has stale PPs on ESS with ID 23376. Depending on the target volumes set specified in the command line (-n <TargetSet>) or automatically selected by TSM for ACS for mySAP, one of both volumes causes the FlashCopy Backup run to fail with error message (3)

Figure 32: LVs must not have stale PPs

Solution:

Synchronize at least the logical volume lve01stale2 with stale PPs on the ESS with

ID 23376. The logical volume lve01stale with stale PPs on the ESS with ID 22031 does not cause TSM for ACS for mySAP to fail in this case, because the ESS with ID 23376 is selected for this FlashCopy Backup run. But as soon as ESS with ID 22031 is used for a next FlashCopy Backup run, this run will fail. So it is recommended to synchronize this logical volume as well. To allow for high availability failovers, stale PPs should be avoided in any case.



EEO0154I <loglv22 ><1 ><vpath29 ><31123376>< >

EEO0154I <loglv22 ><2 ><vpath51 ><44822031>< >


EEO0154I <lve01stale ><2 ><vpath58 ><48422031><stale >


EEO0154I <lve01stale2 ><2 ><vpath8 ><13E23376><stale >

EEO0154I <db2e0100 ><1 ><vpath4 ><11523376>< >

EEO0154I <db2e0100 ><2 ><vpath49 ><44622031>< >

EEO0154I <db2e0103 ><1 ><vpath6 ><11723376>< >

EEO0154I <db2e0103 ><2 ><vpath52 ><44922031>< >

EEO0154I <db2e0104 ><1 ><vpath32 ><31423376>< >

EEO0154I <db2e0104 ><2 ><vpath54 ><44B22031>< >

EEO0154I <db2e0105 ><1 ><vpath31 ><31323376>< >

EEO0154I <db2e0105 ><2 ><vpath55 ><44C22031>< >



COPIES : 2


STALE PPs : 1


EEO0170W Logical volume lve01stale has 1 stale partitions.

EEO0160I <lve01stale2 >


COPIES : 2


STALE PPs : 1


EEO0170W Logical volume lve01stale2 has 1 stale partitions.

EEP0176E Some of the partitions of lve01stale2 are stale on the specified hardware unit

23376.




1

2

3



Copy Set must completely reside on one ESS/DS


mirrored across two storage systems. The logical volumes lve01stale and

lve01stale2 are not mirrored correctly across both storage systems. The output (2) shows that both logical volumes have two mirror copies on two physical volumes. But

both mirror copies are located on the same ESS. Both mirror copies of lve01stale

are located on ESS with ID 23376 and both mirror copies of lve01stale2 are located on ESS with ID 22031. As in the example above, only one of both logical volumes causes TSM for ACS for mySAP to fail in this scenario because of the selected target volumes set. In this case ESS ID 23376 is selected for the FlashCopy

Backup run and this result is a failure with logical volume lve01stale2.

Figure 33: Copy Set must completely reside on one ESS/DS

Solution:

Remove one copy of logical volume lve01stale2 and create a new second copy of this logical volume on the ESS with ID 23376.

To allow for high availability failovers, the second logical volume lve01stale must also be cleaned up (remove the second copy and recreate a second copy on the other ESS).



EEO0154I <loglv22 ><1 ><vpath29 ><31123376>< >

EEO0154I <loglv22 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0101 ><1 ><vpath29 ><31123376>< >

EEO0154I <db2e0101 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0102 ><1 ><vpath5 ><11623376>< >

EEO0154I <db2e0102 ><2 ><vpath50 ><44722031>< >

EEO0154I <loglv26 ><1 ><vpath8 ><13E23376>< >

EEO0154I <loglv26 ><2 ><vpath58 ><48422031>< >


EEO0154I <lve01stale ><2 ><vpath4 ><11523376>< >



EEO0154I <db2e0100 ><1 ><vpath4 ><11523376>< >

EEO0154I <db2e0100 ><2 ><vpath49 ><44622031>< >

EEO0154I <loglv24 ><1 ><vpath30 ><31223376>< >


EEO0154I <db2e0103 ><1 ><vpath6 ><11723376>< >

EEO0154I <db2e0103 ><2 ><vpath52 ><44922031>< >

EEO0154I <db2e0104 ><1 ><vpath32 ><31423376>< >

EEO0154I <db2e0104 ><2 ><vpath54 ><44B22031>< >

EEO0154I <db2e0105 ><1 ><vpath31 ><31323376>< >

EEO0154I <db2e0105 ><2 ><vpath55 ><44C22031>< >

EEP0174E None of the mirror copies of the logical volume lve01stale2 resides completely

on the specified hardware unit 23376.




1

2



LVM mirroring scheduling policy must be parallel

The following error message (1) is pointing to a setup problem with AIX LVM mirroring. The production database is placed on source volumes which are LVM mirrored across two storage systems. But the LVM mirroring scheduling policy

(sequential) selected for volume group sapfcl1 is not supported by TSM for ACS for mySAP. Valid values for scheduling policy are: parallel, parallel/parallel or striped.

Figure 34: LVM mirroring scheduling policy must be parallel

Solution: Change the LVM mirroring scheduling policy the one of the valid values.



EEO0154I <loglv22 ><1 ><vpath29 ><31123376>< >

EEO0154I <loglv22 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0101 ><1 ><vpath29 ><31123376>< >

EEO0154I <db2e0101 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0102 ><1 ><vpath5 ><11623376>< >

EEO0154I <db2e0102 ><2 ><vpath50 ><44722031>< >


EEO0154I <loglv26 ><2 ><vpath58 ><48422031>< >




EEO0154I <lve01stale2 ><2 ><vpath8 ><13E23376>< >

EEO0154I <db2e0100 ><1 ><vpath4 ><11523376>< >

EEO0154I <db2e0100 ><2 ><vpath49 ><44622031>< >

EEO0154I <loglv24 ><1 ><vpath30 ><31223376>< >


EEO0154I <db2e0103 ><1 ><vpath6 ><11723376>< >

EEO0154I <db2e0103 ><2 ><vpath52 ><44922031>< >

EEO0154I <db2e0104 ><1 ><vpath32 ><31423376>< >

EEO0154I <db2e0104 ><2 ><vpath54 ><44B22031>< >

EEO0154I <db2e0105 ><1 ><vpath31 ><31323376>< >

EEO0154I <db2e0105 ><2 ><vpath55 ><44C22031>< >



COPIES : 2

SCHED POLICY : sequential

STALE PPs : 0


EEO0168E Logical volume lve01stale must have the parallel or striped scheduling policy.




1

2



LVM mirror write consistency must be on


mirrored across two storage systems. But the LVM mirroring write consistency (off)

selected for volume group sapfcl1 is not supported by TSM for ACS for mySAP.

Figure 35: LVM mirror write consistency must be on

Solution: Switch the LVM mirroring write consistency on for the specified volume group.

Quorum of VGs must be off


mirrored across two storage systems. But the quorum for volume group sapfcl1 is not supported by TSM for ACS for mySAP.

Figure 36: Quorum of VGs must be off

Solution: Switch the quorum off for the specified volume group.



EEO0154I <loglv22 ><1 ><vpath29 ><31123376>< >

EEO0154I <loglv22 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0101 ><1 ><vpath29 ><31123376>< >

EEO0154I <db2e0101 ><2 ><vpath51 ><44822031>< >

EEO0154I <db2e0102 ><1 ><vpath5 ><11623376>< >

EEO0154I <db2e0102 ><2 ><vpath50 ><44722031>< >


EEO0154I <loglv26 ><2 ><vpath58 ><48422031>< >




EEO0154I <lve01stale2 ><2 ><vpath8 ><13E23376>< >

EEO0154I <db2e0100 ><1 ><vpath4 ><11523376>< >

EEO0154I <db2e0100 ><2 ><vpath49 ><44622031>< >

EEO0154I <loglv24 ><1 ><vpath30 ><31223376>< >


EEO0154I <db2e0103 ><1 ><vpath6 ><11723376>< >

EEO0154I <db2e0103 ><2 ><vpath52 ><44922031>< >

EEO0154I <db2e0104 ><1 ><vpath32 ><31423376>< >

EEO0154I <db2e0104 ><2 ><vpath54 ><44B22031>< >

EEO0154I <db2e0105 ><1 ><vpath31 ><31323376>< >

EEO0154I <db2e0105 ><2 ><vpath55 ><44C22031>< >



COPIES : 2


STALE PPs : 0

MIRROR WRITE CONSISTENCY: off

EEO0172E Logical volume lve01stale must have mirror write consistency on.


IDS1028E Splitint ended with errors on the production system. IDS1024I Exiting with return code 2.

1


EEO0164E Quorum of the volume group sapfcl1 must be off.




1



FlashCopy Phase

In the FlashCopy Phase splitint is running on the production system with the function flashcopy. The FlashCopy Phase can be split into the following steps:

• Suspend the production database • Flush the filesystems on the production system • Initiate the FlashCopy • Resume the production database write activities

The following pages show the most typical problems which can occur in the FlashCopy Phase of a FlashCopy Backup.

Figure 37: Problem Isolation - FlashCopy



DB2 database cannot be suspended

The following error message (1) is shown, when the DB2 database or one of the DB2 database partitions on the production system could not be suspended. The most usual reasons for this error are:

• database (or one database partition) is not in normal state (the state is e.g. Backup in progress, Rollforward pending, …)

• database (or one database partition) is not started • network problems

Figure 38: DB2 database cannot be suspended

Solution: Wait until the database (all database partitions) is back in normal state or solve the problem with the database or network and rerun the FlashCopy Backup afterwards.


...

Matching pair tgt: <75207816300> src: <75207816200> size: <10737418240_Bytes>










DB2 instance db2ab7 is a EEE instance.

Default database path: /db2/AB7

TCPIP service name: sapdb2AB7

Checking system database directory

Checking local database directory /db2/AB7

IDS1602I Waiting for SyncPoint 1 on all EEE nodes...

...

Get first active logfile for database AB7 NODE0000 ...

set client connection to Node 0

First active logfile for DB AB7 is: S0000002.LOG


...


...

IDS2560I Suspend database AB7 NODE0000 write activities...

IDS0099I message_id = REQ_DB_SUSPEND

IDS0099I status = MSG_OK

IDS0099I message_id = ANS_DB_SUSPEND

IDS0099I status = MSG_ERROR

IDS2550E Database AB7 can not be set to write suspend mode


1



FlashCopy failed with RC != 0

The following error message (1) is shown, when the FlashCopy cannot be initiated for all or some of the FlashCopy source/target volumes. This error can have multiple reasons. The most usual ones are:

• target volume is reserved • source volume in already in another incremental source/target relation with

another target volume • source volume is already used as target volume for another FlashCopy or

PPRC relation • target volume is already used as source volume for another FlashCopy or

PPRC relation • target volume is already used as a target volume for another FlashCopy or

PPRC relation • source and target volumes are not in same LSS (can only occur if FlashCopy

V1 is licensed but not FlashCopy V2)

Figure 39: FlashCopy failed with RC != 0

For the solution of the most usual reasons see Unit 9 – Troubleshooting TSM ACS with DS Open API CIM Agent.

IDS2560I Suspend database AB7 NODE0000 write activities...

IDS0099I message_id = REQ_DB_SUSPEND


IDS0099I message_id = ANS_DB_SUSPEND



...

IDS2122I Flashcopying the sources to the target volumes ...

Function flashcopy_prod


Backup list /tmp/eaaRKQoae

EEP0272I Flushing the buffers to disk...

IDS1030I FlashCopy started ...

EEP1625I Number of volumes to be processed by Flashcopy: 10

EEP0354I Performing COPY FlashCopy of source volume 75207816200 to target volume 75207816300

…


EEP1626E An unexpected error was encountered processing a TSM for ACS function.

TDP function name : DsHWInterface::hwStartCopy

TDP function : CIM Error. Failed to execute

IBMTSDS_StorageConfigurationService::AttachReplicas , return: 8001

TDP return code : 32769

TDP file : DsHWInterface.cpp (3878)

IDS1200E The exception 'CIdsException' was thrown.

Reason: Unexpected data ID 11 passed in CIdsDataFile::GetLsmMultiData()


Resume database AB7 NODE0000 write activities...

IDS0099I message_id = REQ_DB_RESUME


IDS0099I message_id = ANS_DB_RESUME




1



DB2 database cannot be resumed

The following error message (1) is shown, when the DB2 database or one of the DB2 database partitions on the production system could not be resumed. The most usual reasons for this error are:

• database (or one database partition) is not in suspend state • database (or one database partition) is not started • network problems

Figure 40: DB2 database cannot be resumed

Solution: Depending on the cause of the problem, it could happen that the database is still suspended. In this case, the following commands can be started to resume the database write activities: As db2<sid> user on the production system call the command: cd /db2/<SID>/dbs

./tdphdwdb2 –f db_resume –s <DB2 partition number> –p <profile> If this command does not resume the database activities, then the following command can be used: db2 terminate ; export DB2NODE=<DB2 partition number> ; db2 connect

to <SID>

If the connect is possible, then the following command can be used to resume this database partition: db2 set write resume for database

If a connection to the database partition is not possible, then the database must be restarted with the following command: db2 restart <SID> write resume

IDS2122I Flashcopying the sources to the target volumes ...

Function flashcopy_prod


Backup list /tmp/caaE6Qoac

EEP0272I Flushing the buffers to disk...

IDS1030I FlashCopy started ...












IDS1031I FlashCopy successful.


...

IDS2562I Resume database AB7 NODE0000 write activities...




IDS0099I status = MSG_ERROR

IDS2550E Database AB7 can not be set to write suspend mode


1



Setresources Phase

In the Setresources Phase splitint is running on the backup system after the phases getresources and flashcopy. The Setresources Phase can be split into the following steps:

• Cleanup by removing the target volumes from AIX ODM • Configure all disk devices in the AIX ODM • Cleanup by removing all volumes with duplicate PVIDs from AIX ODM • Import/Recreate the volume groups • Mount the filesystems

The following pages show the most typical problems which can occur in the Setresources Phase of a FlashCopy Backup.

Figure 41: Problem Isolation - Setresources



No target volume found

The error message (1) below has the following reason: • None of the target volumes is attached to the backup system

This error message may also be caused by the following: • The TSM ACS mySAP script ‘hdwmap.sh’ could not be started

Figure 42: No target volume found

Solution: Verify that the target volumes are attached to the backup system with the following commands as user root on the backup system: • (SDD): check for the existence of the target volumes specified in (2) with the

command root@p670-lun1:/>datapath query device |grep SERIAL SERIAL: 75034614000

SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…

• (SDDPCM): check for the existence of the target volumes specified in (2) with the command root@p670-lun1:/>pcmpath query device |grep SERIAL SERIAL: 75034614000

SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…

In addition, as user root, run the following command:







...

IDS2562I Resume database AB7 NODE0000 write activities...






...


...


...


IDS1027I Splitint ended successfully on the production system.

IDS1540I Start of fcagent on the backup system ...

IDS2123I Enabling the volumes and filesystems ...

IDS0099I message_id = REQ_SYNC_START_RESTART


IDS0099I message_id = ANS_SYNC_START_RESTART


Function setresources

Backup list /db2/AB7/dbs/save/tdpessdb2_lst

IDS1075I Creating a semaphore for the critical part of importing/exporting ...

IDS1076I Trying to set the semaphore for the critical part of importing/exporting ...

IDS1046I Start of listing of importing volume groups/mounting file systems ...

EEP0126I Trying to find new devices to match the source device. This process will take some

time......

/tmp/kaapnUoEk[2]: /db2/AB7/dbs/hdwmap.sh: not found

/tmp/kaapnUoEk[2]: /db2/AB7/dbs/hdwmap.sh: not found

EEP0358E No target volume is available. Terminating......

IDS1077I Semaphore released.


2

1



• (SDD): check also with the command /db2/<SID>/dbs/hdwmap.sh vpath0 11E23376 hdisk2 hdisk56 hdisk110

vpath1 11F23376 hdisk3 hdisk57 hdisk111

vpath2 12023376 hdisk4 hdisk58 hdisk112

vpath35 31C23376 hdisk37 hdisk91 hdisk145

vpath36 31D23376 hdisk38 hdisk92 hdisk146


• (SDDPCM) check also with the command /db2/<SID>/dbs/hdwmap.sh hdisk2 11E23376 hdisk3 11F23376

hdisk4 12023376

hdisk37 31C23376

hdisk38 31D23376

hdisk48 34F23376 If all target volumes can be found in the output of the script ‘hdwmap.sh’ then check in the trace file tdphdwdb2_b_flashcopy/backup_<timestamp>.trace

Figure 43: No target volume found

if the volumes can be found there at (1). If no volume is listed in the trace file, then the script ‘hdwmap.sh’ could not be started successfully. In this case check the following as user db2<sid> on the backup system: echo $PATH db2e01@t1:/db2/E01/dbs>echo $PATH

/usr/bin:/etc:/usr/local/bin:/usr/sbin:/usr/ucb:/usr/bin/X11:/

sbin:/db2/E01/bin:/usr/bin/X11:.:/usr/sap/E01/SYS/exe/run:/db2

/E01/sqllib/bin:/db2/E01/sqllib/adm:/db2/E01/sqllib/misc Check the output of the PATH variable for the existence of ‘.’ (the current directory). If the current directory is not added to the search path, then the script ‘hdwmap.sh’ cannot be found. Add the’.’ (current directory) to the PATH variable of the user db2<sid> and rerun the FlashCopy Backup.

03/09/2008 14:16:57.472 : aix/hdwvm.cpp (3735): Enter: function HdwVm::createSerialNumberMap()

03/09/2008 14:16:57.472 : hdwutil.cpp ( 894): Enter: function HdwUtil::issueSystemCmd()

03/09/2008 14:16:57.485 : hdwutil.cpp ( 939): HdwUtil::issueSystemCmd hdwmap.sh | awk '$1 ~

/vpath|hdisk/ { print $0 }' >>/tmp/gaagGmlEg 2>>/tmp/haagGmlEh

echo hdwIntRC: $? >> /tmp/haagGmlEh

03/09/2008 14:16:57.493 : hdwutil.cpp (2527): Enter: function HdwUtil::runSystemCmd()

03/09/2008 14:16:57.642 : hdwutil.cpp (2531): Exit: function HdwUtil::runSystemCmd() rc=0

03/09/2008 14:16:57.644 : hdwutil.cpp (1050): HdwUtil::issueSystemCmd hdwIntRC: 0

03/09/2008 14:16:57.644 : hdwutil.cpp (1122): Exit: function HdwUtil::issueSystemCmd() rc=0

03/09/2008 14:16:57.644 : aix/hdwvm.cpp (3842): Exit: function HdwVm::createSerialNumberMap() rc=0

1



Importing of Volume Group failed – missing volumes

The following error message (1) is shown, when some target volumes are attached to the backup system and some target volumes are not attached. The result may be that some volume groups cannot be imported.

Figure 44: Importing of Volume Group failed – missing volumes

If TSM for ACS for mySAP V5.3.0.1 is used with ESS CLI then verify that all target volumes used as FlashCopy targets (2) are attached to the backup system with the following commands as user root: • (SDD): check for the existence of the target volumes specified in (2) with the


SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…


SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…

In addition, as user root, run the following command: • (SDD): check also with the command

/db2/<SID>/dbs/hdwmap.sh vpath0 11E23376 hdisk2 hdisk56 hdisk110






• (SDDPCM) check also with the command /db2/<SID>/dbs/hdwmap.sh hdisk2 11E23376









...

EEP0126I Trying to find new devices to match the source device. This process will take some

time.......

EEP0148I Importing volume groups now...

EEP0400E Error on running command: importvg -y TC4tdp1 -n vpath79

EEP0402I 0516-052 varyonvg: Volume group cannot be varied on without a

EEP0402I quorum. More physical volumes in the group must be active.

EEP0402I Run diagnostics on inactive PVs.

EEP0402I 0516-780 importvg: Unable to import volume group from vpath79.

EEP0402I hdwIntRC: 1

EEP0312E Importing the volume group from hdisk vpath79 failed.



1

2



hdisk3 11F23376

hdisk4 12023376

hdisk37 31C23376

hdisk38 31D23376

hdisk48 34F23376 Solution: If not all target volumes can be found in the output of the command listed above, then you need to attach the missing volumes with the ESS Specialist or the ESS CLI (for ESS volumes) or with the DS Web Gui or dscli (for DS volumes).

Importing of Volume Group failed – volumes not accessible

The following error message (1) is shown, when target volumes attached to the backup system cannot be accessed. The result may be that some volume groups cannot be imported. This error message is potentially the result of a corruption in the AIX ODM.

Figure 45: Importing of Volume Group failed – volumes not accessible

In the example above, the physical volume vpath79 is one of the target volumes specified in the target volumes file (.fct). This volume is attached to the backup system and it is visible for AIX. TSM ACS mySAP detects this target volume and tries to import a volume group from this volume. But the low-level AIX command within the importvg command fail to access the volume. The reason for this cannot be determined exactly. Normally a manual cleanup of the AIX ODM would fix this problem:

1. unmount all filesystem belonging to volume groups residing on ESS/DS volumes (take care that rootvg is not touched)

2. vary off all volume groups residing on ESS/DS volumes (take care that rootvg is not touched)

3. remove all multi path devices (vpath<NN> in case of SDD) (take care that rootvg is not touched)

4. remove all hdisks with disk type ‘IBM FC 2105’ and ‘IBM FC 2107’ Be careful to not remove the disks of rootvg or local volume groups.

5. afterwards you should have a clean set of hdisks in the AIX ODM (check with lspv should show only disks of rootvg and local volume groups)

6. run the cfgmgr command 7. afterwards all hdisks and vpath devices should be visible again. 8. vary on all volume groups which are vary off previously

EEP0126I Trying to find new devices to match the source device. This process will take

some time.......


EEP0400E Error on running command: importvg -y TC4tdp1 -n vpath79

EEP0402I 0516-024 lqueryvg: Unable to open physical volume.

EEP0402I Either PV was not configured or could not be opened. Run

EEP0402I diagnostics.

EEP0402I 0516-024 lqueryvg: Unable to open physical volume.

EEP0402I Either PV was not configured or could not be opened. Run

EEP0402I diagnostics.

EEP0402I 0516-1140 importvg: Unable to read the volume group descriptor area

EEP0402I on specified physical volume.


EEP0312E Importing the volume group from hdisk vpath79 failed.



1



9. if this step fails, then the manual cleanup didn’t fix the AIX ODM problem or the problem resides on another part on AIX, e.g. maybe AIX kernel. Then a reboot of the backup system is needed to cleanup the system. After the reboot, everything should work fine

10. if the above procedure does not fix the problem then do a reboot of the backup system (if not already done in 9.)



Filesystem check / mount fails - jfs log wrapped

The following error message (1) was seen in older TSM ACS version using ESS CLI, when many filesystems (>10) in the same volume group use the same jfs/jfs2 log volume and when many ESS volumes (>150) are used on the production system. The combination of both can produce inconsistent filesystems or jfs/jfs2 log volumes.

Figure 46: Filesystem check / mount fails - jfs log wrapped

The reason for this behavior is that the FlashCopy with ESS CLI of a huge number of ESS volumes can take several minutes and the FlashCopy with ESS CLI will be performed on a volume by volume base. The time when the first ESS volume is FlashCopied and the time when the last ESS volume is FlashCopied can be significantly different. If the jfs/jfs2 log volume is one of the last ESS volumes to be FlashCopied, then it may happen, that the jfs log volume is already overwritten (log wrapped…) with changes in the filesystems. In this case the following message (1) is shown in the trace file.

Figure 47: Filesystem check / mount fails - jfs log wrapped (cont.)

Solution: There are multiple solutions for this problem:

EEP0124I Mounting filesystem : /oracle/REP/sapdata82.




EEP0402I Replaying log for /dev/larep07sap85lv.

EEP0400E Error on running command: mount /oracle/REP/sapdata85

EEP0402I logform: 0507-507 Log device is currently used by mounted file systems

EEP0402I Failure replaying log: -3

EEP0402I mount: 0506-324 Cannot mount /dev/larep07sap85lv on /oracle/REP/sapdata85: The

media is not formatted or the format is not correct.


EEP0025E Filesystem consistency check failed.



1

1

02/21/2006 13:04:25.179 : hdwutil.cpp ( 839): Enter: function HdwUtil::issueSystemCmd()

Enter: function HdwUtil::issueSystemCmd()

HdwUtil::issueSystemCmd print 'yes' | fsck -f /oracle/REP/sapdata85 >>/tmp/gaaRTApEg 2>>/tmp/haaRTApEh

echo hdwIntRC: $? >> /tmp/haaRTApEh

Enter: function HdwUtil::runSystemCmd()

Exit: function HdwUtil::runSystemCmd() rc=0

HdwUtil::issueSystemCmd logform: 0507-507 Log device is currently used by mounted file systems

HdwUtil::issueSystemCmd hdwIntRC: 0

HdwUtil::issueSystemCmd

HdwUtil::issueSystemCmd ****************

HdwUtil::issueSystemCmd The current volume is: /dev/larep07sap85lv

HdwUtil::issueSystemCmd i/o error log reading page 0x1c3a

HdwUtil::issueSystemCmd logRead: logwrap

HdwUtil::issueSystemCmd log wrapped...

HdwUtil::issueSystemCmd log read failed 0x1c3b098

HdwUtil::issueSystemCmd logredo: log rec bad or i/o error...logFormatting...

HdwUtil::issueSystemCmd logredo: logform failed

HdwUtil::issueSystemCmd logredo failed (rc=-3). fsck continuing.

HdwUtil::issueSystemCmd **Phase 1 - Check Blocks, Files/Directories, and Directory Entries

HdwUtil::issueSystemCmd **Phase 2 - Count links

HdwUtil::issueSystemCmd **Phase 3 - Duplicate Block Rescan and Directory Connectedness

HdwUtil::issueSystemCmd **Phase 4 - Report Problems

HdwUtil::issueSystemCmd **Phase 5 - Check Connectivity

HdwUtil::issueSystemCmd **Phase 7 - Verify File/Directory Allocation Maps

HdwUtil::issueSystemCmd **Phase 8 - Verify Disk Allocation Maps

HdwUtil::issueSystemCmd **Phase 9 - Reformat File System Log

HdwUtil::issueSystemCmd 29163520 kilobytes total disk space.

HdwUtil::issueSystemCmd 5 kilobytes in 10 directories.

HdwUtil::issueSystemCmd 28368964 kilobytes in 8 user files.

HdwUtil::issueSystemCmd 789588 kilobytes are available for use.

HdwUtil::issueSystemCmd File system is clean.

HdwUtil::issueSystemCmd Superblock is marked dirty; FIX? All observed inconsistencies have been repaired.

HdwUtil::issueSystemCmd

Exit: function HdwUtil::issueSystemCmd() rc=0

Enter: function HdwUtil::skipErrorMsg()

Exit: function HdwUtil::skipErrorMsg() rc=0 Exit: function HdwUtil::runCommand() rc=0



• reduce the number of ESS volumes (not very feasible) • reduce the number of filesystems (not very feasible) • use jfs2 inline logs for each filesystem (not supported yet by DP for FC for

mySAP) • create dedicated jfs log volumes for each of the filesystems (or at least for

more then one filesystem) • upgrade TSM ACS to version 5.4.2.0 and use FlashCopy on ESS via DS Open

API CIM Agent (this reduces the time for the FlashCopy from minutes to seconds)

Filesystem check / mount fails - FS is unknown

The following error message (1) can be shown in different error scenarios. The following two scenarios show typical configuration problems which will result in such an error that a filesystem cannot be found.

Figure 48: Filesystem check / mount fails - FS is unknown

The first configuration problem results in a volume group which looks like shown in

(2). Logical volume lvE01sapdata1 does not have a mount point in the output above but the logical volume itself exists in the volume group. The reason for this problem can be a configuration problem on the production system or a problem with some FlashCopy target volumes.


some time.......


EEP0149I Newly imported volume group: E01_0tdp1


EEP0124I Mounting filesystem : /db2/E01/db2e01.

EEP0124I Mounting filesystem : /db2/E01/sapdata1.

EEP0400E Error on running command: mount /db2/E01/sapdata1

EEP0402I mount: 0506-334 /db2/E01/sapdata1 is not a known file system.





1

t1:root:/opt/ibm/ESScli#lsvg -l E01_0tdp2

E01_0tdp2:

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT

loglv14 jfslog 1 1 1 closed/syncd N/A

loglv08 jfs2log 1 1 1 closed/syncd N/A

lvE01sapdata1 jfs 147 147 1 closed/syncd N/A

lvE01sapdata2 jfs 108 108 1 closed/syncd /db2/E01/sapdata2





lvE01sapdatat jfs 34 34 1 closed/syncd /db2/E01/sapdatat

2



The following output shows a difference between lvE01sapdata1 (1) and

lvE01sapdata2 (2), when looking on the volume group on the production system

and comparing two logical volumes of this volume group. lvE01sapdata1 does not have a LABEL defined. When FlashCopying a volume group with such a ‘no labeled’ logical volume, the importvg command on the backup system can not completely import the filesystem from this logical volume. The label is needed for importing this filesystem correctly.

Figure 49: Filesystem check / mount fails - FS is unknown (cont.)

Solution: On the production system add the missing LABEL to the logical volume with the following command: chlv –L <mount point> <LV name>

In the above example the command would look like: chlv –L /db2/E01/sapdata1 lvE01sapdata1

Afterwards a new FlashCopy Backup will work.

2

t1:root:/opt/ibm/ESScli#lslv lvE01sapdata1

LOGICAL VOLUME: lvE01sapdata1 VOLUME GROUP: E01datavg

LV IDENTIFIER: 00588d2a00004c00000000fb825be1f5.9 PERMISSION: read/write

VG STATE: active/complete LV STATE: closed/syncd

TYPE: jfs WRITE VERIFY: off

MAX LPs: 512 PP SIZE: 32 megabyte(s)

COPIES: 1 SCHED POLICY: parallel

LPs: 147 PPs: 147

STALE PPs: 0 BB POLICY: relocatable

INTER-POLICY: minimum RELOCATABLE: yes

INTRA-POLICY: middle UPPER BOUND: 32

MOUNT POINT: N/A LABEL:


EACH LP COPY ON A SEPARATE PV ?: yes

Serialize IO ?: NO

t1:root:/opt/ibm/ESScli#lslv lvE01sapdata2

LOGICAL VOLUME: lvE01sapdata2 VOLUME GROUP: E01datavg

LV IDENTIFIER: 00588d2a00004c00000000fb825be1f5.8 PERMISSION: read/write

VG STATE: active/complete LV STATE: closed/syncd

TYPE: jfs WRITE VERIFY: off

MAX LPs: 512 PP SIZE: 32 megabyte(s)

COPIES: 1 SCHED POLICY: parallel

LPs: 147 PPs: 147

STALE PPs: 0 BB POLICY: relocatable

INTER-POLICY: minimum RELOCATABLE: yes

INTRA-POLICY: middle UPPER BOUND: 32

MOUNT POINT: N/A LABEL: /db2/E01/sapdata2


EACH LP COPY ON A SEPARATE PV ?: yes

Serialize IO ?: NO

1



The second configuration problem results in a volume group which looks like shown in (2, 3) below. The volume group could be imported (with warnings but not with errors) but the detailed view on the physical volumes in the volume groups shows that one of the target volumes is missing on the backup system.

Figure 50: Filesystem check / mount fails - FS is unknown (cont.)

If TSM for ACS for mySAP V5.3.0.1 is used with ESS CLI then verify that all target volumes used as FlashCopy targets (2) are attached to the backup system with the following commands as user root: • (SDD): check for the existence of the target volumes specified in (2) with the


SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…


SERIAL: 75034614003

SERIAL: 75034614200

SERIAL: 75034614201

SERIAL: 75034614202

…

In addition, as user root, run the following command: • (SDD): check also with the command

/db2/<SID>/dbs/hdwmap.sh vpath0 11E23376 hdisk2 hdisk56 hdisk110




some time.......




EEP0124I Mounting filesystem : /db2/E01/db2e01.

EEP0124I Mounting filesystem : /db2/E01/sapdata1.

EEP0400E Error on running command: mount /db2/E01/sapdata1

EEP0402I mount: 0506-334 /db2/E01/sapdata1 is not a known file system.





1

t1:root:/home/root#lsvg -p E01_0tdp2

E01_0tdp2:

PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION

vpath80 active 63 53 13..03..12..12..13

vpath79 missing 63 54 13..04..12..12..13 2

t1:root :/home/root#varyoffvg E01_0tdp2

t1:root :/home/root#varyonvg E01_0tdp2

PV Status: hdisk16 000c6d7c56df6edc PVACTIVE

hdisk15 000c6d7c56df6f83 PVMISSING

varyonvg: Volume group TC4tdp1 is varied on. 3






• (SDDPCM) check also with the command /db2/<SID>/dbs/hdwmap.sh hdisk2 11E23376 hdisk3 11F23376

hdisk4 12023376

hdisk37 31C23376

hdisk38 31D23376

hdisk48 34F23376

Solution: If not all target volumes can be found in the output of the command listed above, then you need to attach the missing volumes with the ESS Specialist or the ESS CLI (for ESS volumes) or with the DS Web Gui or dscli (for DS volumes).

TSM Backup Phase

In the TSM Backup Phase tdpessdb2 is calling db2 on the backup system to start a backup of the FlashCopied database to TSM. The following pages show the most typical problems which can occur in the TSM Backup Phase of a FlashCopy Backup.

Figure 51: Problem Isolation – TSM Backup



TSM backup failed

Details on the troubleshooting of the TSM backup phase are not part of this workshop

Figure 52: TSM backup failed

Check the TSM for ERP manual and its troubleshooting chapter.


...

IDS2307I Issuing DB2 command 'db2 backup db E01 load

/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a OPEN 002 SESSIONS OPTIONS /db2/E01/dbs/vendor.env

WITH 002 BUFFERS BUFFER 01024 PARALLELISM 001

echo hdwIntRC: $?' ...

SQL2062N An error occurred while accessing media "VENDOR". Reason code:

"11".

hdwIntRC: 4

IDS2500E DB2 command failed:'db2 backup db E01 load

/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a OPEN 002 SESSIONS OPTIONS /db2/E01/dbs/vendor.env

WITH 002 BUFFERS BUFFER 01024 PARALLELISM 001'.

...

IDS1047I End of listing.

IDS1025I Time stamp: 09/24/08-09:43:00.


...


1



Unit 9

Troubleshooting

TSM for ACS with DS Open API CIM Agent

Unit Objectives

After completing this unit, you will be able to: � Describe the log / trace files of the DS Open API CIM Agent � Describe identify and solve problems with TSM ACS in combination with DS

Open API CIM Agent

This unit gives you information on how to resolve errors that might occur during Backup / Restore process with TSM for ACS using DS Open API CIM Agent. In general, problems related to this product can be distinguished into these categories:

1. Setup and configuration problems 2. Defects of this product or a product it is interacting with

This unit will help you with setup and configuration problems. If an error occurs, always first check the description of the respective error message, issued by the system. Besides being displayed on the screen, the error messages also can be found in log files. For these log files and for a description of the error messages, see Installation and User’s Guide, Appendix B. Data Protection for FlashCopy Devices for mySAP (DB2) Messages. Solve the problem indicated in the error message and retry the action.

Unit 9: Troubleshooting TSM for ACS with DS Open API CIM Agent TSM for ACS Workshop


Problem Isolation Flow

During work with TSM for ACS for mySAP using DS Open API CIM Agent you may run into problems during backing up or restoring of your DB2 database. Following graphic will help you to isolate CIM Agent related FlashCopy Backup problems:

Figure 53: Problem Isolation - Flow of error analysis

DS Open API CIM Agent 5.1.0.x log files

Use the CIM Agent log files to collect CIM Agent diagnostic data.

Collecting CIM Agent diagnostic data

To collect diagnostic data, follow these steps:

1. Adjust the log setting values:

a. In the CIM Agent installation directory (usually C:/Program Files/IBM/cimagent), log settings are set in a file named

TSM for ACS Workshop DS Open API CIM Agent 5.1.0.x log files


logger.properties. The following values are the default for CIM Agent V1.2.1.38 and above. If the values in your configuration are different, change the values to the following:

message.file.maxFiles = 20

This number indicates the maximum number of 1 MB cimom.log files that are kept. Adjust this number according to activity and disk space.

message.logger.level = DEBUG_MAX This setting allows all debugging messages to be logged. This can lower performance. You can change this setting to DEBUG_MIN when the system stabilizes.

trace.file.maxFiles = 40

This number indicates the maximum number of 1 MB providerTrace.log files that are kept. Adjust this number according to activity and disk space.

trace.logger.level = DEBUG_MAX This setting allows all debugging traces to be logged. This can lower performance. You can change this setting to DEBUG_MID when the system stabilizes.

2. Collect the data when the error occurred: a. Obtain the application logs and determine the timestamp when the

error was encountered.

b. Obtain all cimom.log, cimom1.log, and so on, and

providerTrace.log, providerTrace1.log, and so forth (found in the CIMOM installation directory, usually C:/Program Files/IBM/cimagent).

c. Obtain the client log (log/niClient.log) (found in the CIMOM installation directory, usually C:/Program Files/IBM/cimagent).

To collect CIM Agent diagnostic data, run the collectLog utility:

1. Go to the cimagent directory. (In Windows, this is usually C:\Program Files\IBM\cimagent.)

2. Use the following command to zip all log files in this directory and its

subdirectories into a zip file called collectedLogs.zip. Store the zip file in the target directory (if not given, the default is the cimagent directory):

o For Windows, run collectLogs.bat <target_directory>. o For Linux, run ./collectLogs.sh <target_directory>. o For AIX, run ./collectLogs <target_directory>.

3. Review and change any logging settings (controlled by the file

logger.properties in the cimagent directory).

Default values:

message.file.maxFiles = 20

This number indicates the maximum number of 1 MB cimom.log files that are kept. You can adjust this number according to activity and disk space. message.logger.level = DEBUG_MAX This value allows all debugging messages to be logged. If performance slows, you can change it to DEBUG_MIN after the system stabilizes.



trace.file.maxFiles = 40

This number indicates the maximum number of 1 MB providerTrace.log files that are kept. You can adjust this number according to activity and disk space. race.logger.level = DEBUG_MAX This value allows all debugging traces to be logged. If performance slows, you can change it to DEBUG_MIN after the system stabilizes.

� CIM Agent 5.1.0.x

• Configuration File (cimom.properties)

• ESS/DS Provider Configuration File (provider-cfg.xml) • Log files

• cimom.log main CIM Agent log file • providerTrace.log ESS/DS provider detailed trace file • internalService.log trace file showing internal commands

like query relations • security.log log file for security issues • service.log less important • indication.log less important

• Per default the location for these logs is the install directory of the CIM Agent (on AIX per default: /opt/IBM/cimagent). A different location can be specified in the file logger.properties with the parameters (sets the log path to /opt/IBM/cimagent/logs/cim): • message.file.fileDir=logs/cim • trace.file.fileDir=logs/cim • internalService.file.fileDir=logs/cim • security.file.fileDir=logs/cim • service.file.fileDir=logs/cim • security.file.fileDir=logs/cim

Figure 54: DP for DS/ESS for mySAP – profile parameter

DS Open API CIM Agent 5.2.1.x - 5.4.0.x log files

Use the CIM Agent log files to collect CIM Agent diagnostic data.

CIM Agent log files

A collectlogs script is provided with the CIM Agent to get all of the necessary logs and zip them up. The log files of interest are: provider.log, seascape.log (ESS)

Intended for users. Contains major errors that occur and possible informational messages for the user.

providerTrace.log, seascapeTrace.log (ESS)

TSM for ACS Workshop DS Open API CIM Agent 5.2.1.x - 5.4.0.x log files


Intended for support or L3 development to use for debugging. Traces the path of the code.

• To enable full logging issue:

dscimcli chconfig -tracemask all -tracecomponent all

• To enable performance level logging issue:

dscimcli chconfig -tracemask perf -tracecomponent cpa

cimserver.log

Captures stdout and stderror of the cimserver binary. Contains information about when the CIM Agent was last started and stopped, what ports and protocols it is listening on, and if there were any core dumps, and the

location of the core dump files. The collectlogs script does not collect the core dump files, so if core dumps were generated, the user will need to send those to IBM support separately.

hwlayer.log

Logs the calls made to the storage subsystem. niClient.log

Logs the calls made to the storage subsystem.

Troubleshooting the problem

Before troubleshooting the problem, refer to the CIM Agent documentation on the recommended maximum number of subsystems or volumes to monitor per CIM Agent. Reference the section under IBM CIM Agent Server Capacity Guidelines in the following Web site: http://www-1.ibm.com/support/docview.wss?uid=ssg1S1002988&rs=1103. The CIM Agent might respond slowly or run out of memory if overloaded. Contact your IBM support center should you run into this problem. Here are some hints and tips on troubleshooting the problem:

1. Look in the provider.log for obvious errors:

• Some messages may indicate user errors.

• NIUnavailableServerException indicates a problem between the CIM Agent and the HMC or SMC.

• NITimeoutException indicates a problem between the HMC or SMC and c0 or c1.

2. If the user is getting a return code, look for the code (in hexadecimal) in the

provider.log and providerTrace.log to see if there is a more detailed message. To verify the CIM agent configuration and connectivity, issue command dscimcli lsdev –l



If you are running dscimcli from a different server as the CIM agent, then the command format is: dscimcli -s https://<hmc ip>:6989 lsdev –l

• If a "cannot connect to" response is received, check for a connection problem from the AIX server to the CIM agent.

• If a response to the command is received, there is a good connection but the returned Status is displayed as "failed", then the problem is below the CIM Agent and possibly within the storage subsystem.

For more detailed information on dscimcli commands and responses, go to the CIM Agent support for DS Open API Web site. Click on the Install/use tab, Documentation link, and select the DS Open Application Programming Interface 5.x Reference link. For additional CIM Agent information, from the CIM Agent support for DS Open API Web site, click on the Technical notes link. Select the IBM CIM Agent for DS Open API FAQ link.

3. To confirm that the services on the device are running properly, use esscli and ESS Specialist for the ESS storage subsystem, and use DS CLI or the DS Storage Manager GUI for the DS storage subsystem. The DS CLI is preferred method to use over the DS GUI. The DS Open Application Programming Interface 5.2.1 Reference contains

information for dscimcli commands regarding the esscli and ESS Specialist.

4. If there are particular instances of classes that a customer says are missing, use the CLI (Pegasus CLI) to double check the missing classes.

What to check and collect for a CIM Agent problem

If you determine that the problem is with the CIM Agent, follow these steps: 1. Check the CIM Agent documentation and README files 2. Collect the CIM Agent logs:

Go to this directory: cd /opt/IBM/dsagent

Some environment variables need to be set first. export DSAGENT_HOST=/opt/IBM/dsagent

export PATH=$PATH:$DSAGENT_HOME/bin

Run collectlogs

TSM for ACS Workshop DS Open API CIM Agent 5.2.1.x - 5.4.0.x log files


The collectlogs command collects DS Open API CIM agent logs after a failure has

occurred. The collected files will be placed into a zip file in the $DSAGENT_HOME/log directory.

Common user errors

Why am I getting out-of-memory conditions with the DS6000 or DS8000 and

CIM Agents?

If you are getting out-of-memory conditions, try increasing the Java heap size for the CIM agent. Determine the size of the Java heap by issuing: dscimcli lsconfig

Increase the Java heap size by an increment of 256 MB. For example, if the maximum heap size is "-Xmx256", change this to "-Xmx512" by issuing: dscimcli chconfig -jvmargs -Xmx512 If you have enough memory, try increasing this to 1.5 GB of RAM with "-Xmx1536" by issuing: dscimcli chconfig -jvmargs -Xmx1536

After issuing the dscimcli command, restart the CIM Agent.

Things to check

These are some things to check:

• Are there port conflicts? CIMOM by default uses ports 5988 and/or 5989 to talk to CIM clients. This is configurable, but problems can occur if you are not aware of other applications using the same ports. IBM Director is a known application which uses the same ports by default.

• Are there SLP conflicts?

• Is the correct version of the CIM Agent installed?

o Check the IBM TotalStorage Productivity Center support matrix.

o Verify that the customer's device model is supported by this CIM Agent.

• Check if the CIM Agent is running, or might not be configured with the device correctly. Issue: dscimcli lsdev -l

• Make sure the correct interop namespace is /root/ibm.

• The SLP discovery might not be working. Have the user manually enter the CIM Agent information in the CIM Agent login panel.



� CIM Agent 5.2.1.x – CIM Agent 5.4.0.x • Configuration File (only through dscimcli) • ESS/DS Provider Configuration File (only through dscimcli) • Log files

• provider.log ESS/DS provider log file • providerTrace.log ESS/DS provider detailed trace file • niClient.log communication log file • niTransmission.log communication log file • niCA.log configuration advisor log. Less important

• Per default the location for these log files is the log directory in the install directory of the CIM Agent (on AIX per default: /opt/IBM/dsagent/log).

• Tracing is switched of per default. To enable CIM tracing the following commands should be used (CIM tracing degrades the CIM performance):

• dscimcli chconfig -tracecomponent <comma_separated_list> (possible values: all, none, cpa, cim, sea, jni, servicemanager, slp)

• dscimcli chconfig -tracemask <comma_separated_list> (possible values: all, none, entryexit, fine, debug, perf)

• for full tracing run the command dscimcli chconfig –tracecomponent all -tracemask all

Figure 55: DP for DS/ESS for mySAP – target volumes file



Troubleshoot the Phases of FlashCopy Backup

A FlashCopy Backup run can be divided into different phases • Initialization Phase • Getresources Phase • FlashCopy Phase • Setrecources Phase • TSM backup Phase

The following subsections describe the different phases and give detailed problem analysis and problem resolution strategies for any CIM Agent related problems for each phase. For all other problems see the Unit 8: Troubleshooting - TSM for ACS.

Initialization Phase (CIM Agent)

In the Initialization Phase tdphdwdb2 is called on the backup system with the function backup or flashcopy. The Initialization Phase can be split into the following steps:

• Check profile parameter • Check DB2 instance on backup system • Check DP for mySAP version • Check DB2 client connection to the production database • Get a list of database files from the production database • Check connection to production system via TSM ACS acsprole • Check connection to the DS Open API CIM Agent



The following pages show the most typical problems which can occur in the Initialization Phase of a FlashCopy Backup in conjunction with the DS Open API CIM Agent.

Figure 56: Problem Isolation – Initialize

DS Open API CIM Agent connection problems

The following two figures show the most typical error messages when the connection to the DS Open API CIM Agent failed. There can be multiple different reasons for the failing DS Open API CIM Agent connection:



1. Bad DS Open API CIM Agent server address specified

Figure 57: CIM Agent connection problem

In the sample output above, an ‘Invalid locator’ was specified. ‘unknown.host’ is an invalid TCPIP name. Solution: Correct the TSM for ACS profile parameter

PRIMARY_COPYSERVICES_SERVERNAME.

IBM Tivoli Storage Manager for Advanced Copy Services

Data Protection for FlashCopy Devices for mySAP(R) on DB2

(TDPHDWDB2)









IDS1409E Unable to connect to the copy services server.


Reason:


1

10/03/2008 21:10:39.408 : DsInstance.cpp ( 138): 10/03/2008 21:10:39.408 : HWCommonInterface.cpp( 317):

HWInterface::hwInit(): hwSvrName=<unknown.host>, hwUsrName=<acsuser>, hwPasswd=<****>,hwSvrPort=<5989>

10/03/2008 21:10:39.408 : HWCommonInterface.cpp(1780): DsHWInterface::hwSystemInit(): Entering.....

10/03/2008 21:10:39.408 : HWCommonInterface.cpp(1797): DsHWInterface::hwSystemInit(): instanceData: 30170E38

10/03/2008 21:10:39.409 : HWCommonInterface.cpp(1823): DsHWInterface::hwSystemInit(): connecting to primary

CIM Server: p670-test

10/03/2008 21:10:39.409 : HWCommonInterface.cpp(1833): DsHWInterface::hwSystemInit(): hwCommProtocol=<HTTPS>

hwCertFile=<NO_CERTIFICATE>

10/03/2008 21:10:39.496 : HWCommonInterface.cpp(1869): DsHWInterface::hwSystemInit(): Exiting with error: CIM

Error <PGS00410: LOCATOR IS NOT VALID: unknown.host:5989> while trying to connect to primary CIM Agent:

<unknown.host> at port: <5989> using username: <acsuser>.. rc = <6119>

10/03/2008 21:10:39.497 : DsInstance.cpp ( 166): 10/03/08-21:10:39 IDS1409E: Unable to connect to the copy

services server.

10/03/08-21:10:39 IDS2200E: The exception 'CIdsException' was thrown. Reason: 10/03/08-21:10:39 IDS2124I: Exiting with return code 2.

2



2. DS Open API CIM Agent down 3. Incorrect TCPIP port specified 4. Incorrect CIM agent server address specified The above 3 configuration failures result in the same error message below:

Figure 58: CIM Agent connection problem (cont.)

To verify the current problem, first check that the ESS/DS CIM Agent (CIMOM) daemon is installed and started by typing the following command:

# ps -ef | grep cim


root 1143010 1 0 Oct 04 - 22:08 [cimserve]

Solution: If the CIM Agent is not running, then start it with the command

. /opt/IBM/dsagent/config/envConf

startagent If the CIM Agent is running, then check the TCPIP port on which the CIM Agent is running. This can be verified with the following command . /opt/IBM/dsagent/config/envConf

dscimcli lsconfig The sample output below shows that the CIM Agent is listening on port 5988 (HTTP) and on port 5989 (HTTPS): Property Current Value After Restart

============== ======================================== ========================================

insecureport 5988 5988

secureport 5989 5989

certificate certname certname

enablesecure true true

enableinsecure true true

loglevel warn warn

tracemask all all

tracecomponent cpa,cim,sea,jni,servicemanager,slp cpa,cim,sea,jni,servicemanager,slp



(TDPHDWDB2)











Reason:


1


CIM Server: 9.155.66.113



10/03/2008 21:22:44.269 : HWCommonInterface.cpp(1869): DsHWInterface::hwSystemInit(): Exiting with error: CIM

Error <PGS08001: CIM HTTP OR HTTPS CONNECTOR CANNOT CONNECT TO 9.155.66.113:5989. CONNECTION FAILED.> while

trying to connect to primary CIM Agent: <9.155.66.113> at port: <5989> using username: <acsuser>.. rc = <6119>


services server.


2



jvmarg -Xms128m -Xmx512m -Djava.net.preferIPv6S -Xms128m -Xmx512m -Djava.net.preferIPv6S

tack=true -Xrs tack=true -Xrs

essdutycycle 10 10

dsdutycycle 10 10

slpregips none none

essperfstatsip none none Solution:

Correct the TSM for ACS profile parameter COPYSERVICES_SERVERPORT. If the CIM Agent is running and the TCPIP port of the CIM Agent is correct then check for the correct CIM Agent address in the parameter PRIMARY_COPYSERVICES_SERVERNAME Solution: Correct the TSM for ACS profile parameter

PRIMARY_COPYSERVICES_SERVERNAME.

DS Open API CIM Agent authentication problem

The following error message (1) is displayed, if the user and or password specified for the DS Open API CIM Agent is incorrect.

Figure 59: CIM Agent authentication problem

The CIM Agent user is specified with the TSM for ACS profile parameter COPYSERVICES_USERNAME. Check this parameter first. To check if the password is correctly known, type the following command:

. /opt/IBM/dsagent/config/envConf

dscimcli -s <hostname> -u <CIMuser>:<password> lsconfig

If the password is correct, then the lsconfig output will be displayed.



(TDPHDWDB2)











Reason:


1

10/03/2008 21:35:26.179 : DsInstance.cpp ( 138): 10/03/2008 21:35:26.180 : HWCommonInterface.cpp( 317):

HWInterface::hwInit(): hwSvrName=<p670-lun1>, hwUsrName=<test>, hwPasswd=<****>,hwSvrPort=<5989>

10/03/2008 21:35:26.180 : HWCommonInterface.cpp(1780): DsHWInterface::hwSystemInit(): Entering.....

10/03/2008 21:35:26.180 : HWCommonInterface.cpp(1797): DsHWInterface::hwSystemInit(): instanceData: 30170F18


CIM Server: p670-lun1



10/03/2008 21:35:26.223 : HWCommonInterface.cpp(2339): DsHWInterface::hwGetVersionInfo(): Entering.....

10/03/2008 21:35:26.228 : HWCommonInterface.cpp(2398): DsHWInterface::hwGetVersionInfo(): Exiting with error:

CIM Error <HTTP Error (401 Unauthorized).> while querying value of cim version.. rc = <6119>


services server.


2



If the password is incorrect, a output similar to the following is shown:

Property Current Value After Restart

============== ======================================== ========================================

/opt/IBM/dsagent/pegasus/bin/dscimcli Pegasus Exception: HTTP Error (401 Unauthorized).. Cmd =

lsconfig

The password can be changed with the chuser command. After changing the password or after verifying that the password is correct, TSM for ACS must be updated with the correct password information. For that, the following command must be started as DB2 instance user:

cd /db2/<SID>/dbs

./tdphdwdb2 –f password –p <profile>

This calls the function password of TSM for ACS which asks for the passwords of the DB2 instance owner and of the CIM Agent. After the passwords are updated successfully with TSM for ACS, the authentication problem should be solved.



Getresources Phase (CIM Agent)

In the Getresources Phase tdphdwdb2 is started on the production system with the function getresources. The Getresources Phase can be split into the following steps:

• Check the connection to the CIM Agent • Get the status and other properties of the source and target volumes through

CIM Agent • Determine the FlashCopy source volumes (from a list of database files) • Search for a matching target volume for each of the source volumes • Check LVM mirroring configurations for VGs and LVs

The following pages show the most typical problems which can occur in the Getresources Phase of a FlashCopy Backup with DS Open API CIM Agent.

Figure 60: Problem Isolation – Getresources



CIM Agent query failed - default timeout 6 min

The following error message (1) is displayed, if the CIM Agent request does not respond in a defined period of time (per default this timeout is 6 min.).

Figure 61: CIM Agent query failed - default timeout 6 min

It may happen, that a query to the ESS/DS takes more than 6 min. to respond, if a very high number of ESS/DS volumes is used in a FlashCopy Backup or Restore operation. Solution: Increase the timeout with the TSM for ACS profile parameter COPYSERVICES_TIMEOUT to a value that is sufficient. Sometimes the CIM Agent is hanging or the DS HMC is hanging. Then restarting the CIM Agent and rebooting the DS HMC should solve this problem.


IDS1404I The target set with ID '1' is selected for this run.

Matching pair tgt: <75140318A00> src: <751403136C0> size: <1073741824_Bytes>

Matching pair tgt: <75140318B80> src: <75140313740> size: <1073741824_Bytes>

Matching pair tgt: <75140318A01> src: <75140313640> size: <8589934592_Bytes>


Matching pair tgt: <75140318B00> src: <751403136C1> size: <8589934592_Bytes>

Matching pair tgt: <75140318B01> src: <75140313741> size: <8589934592_Bytes>


Matching pair tgt: <75140318B81> src: <751403137C0> size: <8589934592_Bytes>

EEP0648E An unexpected error was encountered.

TDP function name : DsHWInterface::HwGetFCS

TDP function : CIM Error: <connection timed out>.




IDS1028E Splitint ended with errors on the production system. IDS2124I Exiting with return code 2.

1



CIM Agent query failed – CIM Agent problem

The following error message (1) is displayed, if the CIM Agent encounters a problem for example in connecting to one of the configured DS.

Figure 62: CIM Agent query failed – CIM Agent problem

In this sample above TSM ACS gets an error when searching for the properties of a specific volume. When looking in the trace file of the FlashCopy Backup run (tdphdwdb2_p_flashcopy_<timestamp>.trace) and searching for the error message EEP0649E, then the reason for the error message (1) can be found some lines above (2). The message there states Can't find System for LUN <75207816300>

Looking again some lines above, the list of known ESS/DS storage subsystems is shown (3). When comparing the list of DS with the LUN 75207816300, the mismatch between the LUN id and the DS serial number is obvious. There is no DS with the serial number 7520781. A typo in the serial number is excluded here (this is handled in the previous Unit). For that reason we can now expect a problem in the CIM Agent configuration.


EEP0649E Error while querying volume properties of volume 75207816300.





1

10/04/2008 11:21:54.132 : HWCommonInterface.cpp(5668): DsHWInterface::hwFillVolumeProperties(): Entering.....

10/04/2008 11:21:54.132 : HWCommonInterface.cpp(5897): DsHWInterface::HwQryVolumeSize()(): Entering with volume: <75207816300>.

10/04/2008 11:21:54.132 : HWCommonInterface.cpp(5990): DsHWInterface::HwQryVolumeProperties(): Entering.....

10/04/2008 11:21:54.132 : HWCommonInterface.cpp(1385): DsHWInterface::HwGetSCS(): Entering.....

10/04/2008 11:21:54.206 : HWCommonInterface.cpp(1415): DsHWInterface::HwGetSCS(): Name : StorageConfigurationService for

IBM.2107-7503461

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1419): DsHWInterface::HwGetSCS(): SystemName : IBM.2107-7503461

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1440): DsHWInterface::HwGetSCS(): found system IBM.2107-7503461

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1475): DsHWInterface::HwGetSCS(): Exiting.

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1633): DsHWInterface::HwGetVolumeCop(): Entering with serialNumber:

<75207816300>

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1385): DsHWInterface::HwGetSCS(): Entering.....

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1389): DsHWInterface::HwGetSCS(): Exiting, scsCop already set.

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(1678): DsHWInterface::HwGetVolumeCop(): Can't find System for LUN <75207816300>

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(6053): DsHWInterface::HwQryVolumeProperties(): Exiting with error: . rc = <6119>

10/04/2008 11:21:54.207 : HWCommonInterface.cpp(5927): DsHWInterface::HwQryVolumeSize()(): Exiting with rc = 6119

10/04/2008 11:21:54.208 : HWCommonInterface.cpp(5745): DsHWInterface::hwFillVolumeProperties(): Exiting with rc = 6119

10/04/08-11:21:54 EEP0649E Error while querying volume properties of volume 75207816300.


10/04/2008 11:21:54.208 : lunmanager.cpp (2454): Exit: function CLsmLunManager::lsmIsDataContainerMatching() rc=6119

10/04/08-11:21:54 IDS1401E: The target set '2' does not match the source volumes.

2

3



When looking further in this problem the next step would be to check the CIM Agent configuration for the correct setup of the DS. We expect in this sample 2 DS to be configured. As show below, there are two DS configured in the CIM Agent (1). But the command dscimcli lsdev –l gives a status ‘failed’ for DS 9.155.62.97. This is obviously the cause of the TSM ACS problem with the volume.

Figure 63: CIM Agent query failed – CIM Agent problem (cont.)

Further analysis in the provider.log log file of the CIM Agent shows, that the DS 9.155.62.97 gets timeouts and is therefore quarantined. Solution: To solve the problem, the root cause of the CIM Agent communication problem needs to be verified by CIM Agent support and DS Support.

root@p670-lun1:/opt/IBM/dsagent>dscimcli lsdev

Type IP IP2 Username

===== ======================================= ======================================= =========

DS 9.155.62.97 - acsuser

DS 9.155.70.26 - acsuser

root@p670-lun1:/opt/IBM/dsagent>dscimcli lsdev -l

Type IP IP2 Username Storage

Image Status Code Level Min Codelevel

===== ======================================= ======================================= =========

================ ========== ============== ==============

DS 9.155.62.97 - acsuser -

failed - -

DS 9.155.70.26 - acsuser

IBM.2107-7503461 successful 5.4.2.253 5.1.0.309

1

2008-10-04T13:46:58:097634 0x507 ERROR JNI com.ibm.storage.ess.ni.exception.NITimeoutServerException: completionStatus = 0

Additional info:

com.ibm.storage.ess.ni.client.extensions.services.NIHMCServiceInvocationHandler.processResults(Unknown Source)

com.ibm.storage.ess.ni.client.extensions.services.NIInvocationHandler.invoke(Unknown Source)

com.ibm.storage.ess.ni.client.extensions.services.NIHMCServiceInvocationHandler.invoke(Unknown Source)

$Proxy6.getAllESS(Unknown Source)

2008-10-04T13:46:58:098374 0x507 FATAL JNI Exception: com.ibm.storage.ess.ni.exception.NITimeoutServerException; Message:

completionStatus = 0

Additional info: ; DMTF return code: 49158; Description: Timeout during communication with the storage device.

2008-10-04T13:46:58:098667 0x507 ERROR CPA Exception caught essni/essniapi/ESSNIConnectionManager.cpp:1359 DTMF:49158

Timeout during communication with the storage device.

2008-10-04T13:46:58:098743 0x507 WARN CPA Unable to retreive ESSIDs from 9.155.62.97

2008-10-04T13:46:58:099072 0x507 WARN CPA Exception while retreiving NIESSIDs. 9.155.62.97 Phase: 2

2008-10-04T13:46:58:279793 0x507 WARN CPA Exception connecting to device 9.155.62.97 Phase: 2

2008-10-04T13:46:58:279900 0x507 ERROR CPA Exception caught essni/essniapi/ESSNIConnectionManager.cpp:662 DTMF:49158 Timeout

during communication with the storage device.

2008-10-04T13:46:58:281728 0x507 WARN CPA Connection Created, IP:9.155.62.97 Status: QUARANTINED

2

3

/opt/IBM/dsagent/log/provider.log



FlashCopy Phase (CIM Agent)

In the FlashCopy Phase tdphdwdb2 is running on the production system with the function flashcopy. The FlashCopy Phase can be split into the following steps:

• Suspend the production database • Flush the filesystems on the production system • Initiate the FlashCopy with CIM Agent • Resume the production database write activities

The following pages show the most typical problems which can occur in the FlashCopy Phase of a FlashCopy Backup with DS Open API CIM Agent.

Figure 64: Problem Isolation – FlashCopy



FlashCopy failed in AttachReplicas or ModifySynchronizations

The following error message (1) is shown, when the FlashCopy cannot be initiated for successfully for all source target relations.

Figure 65: FlashCopy failed in AttachReplicas – VOLUME_RESERVED

The TDP Return code shown in (1) has a value 4. The following table lists all possible CIM Agent Return Codes and the corresponding explanation for it. In this case, CIM Agent Return Code 4 means simply ‘Failed’. The table below has 3 columns. The first is the CIM Agent 5.1.0.x Return Code, which is given as a decimal or hexadecimal number. The second column shows the CIM Agent 5.2.1.x – 5.4.0.x Return Code which is given as a decimal or hexadecimal number. And the last column is a short explanation of the Return code. CIM 5.1.0.x CIM 5.4.0.x Explanation 0 0 Job Completed with No Error 1 1 Not Supported 2 2 Unspecified Error 3 3 Timeout 4 4 Failed 5 5 Invalid Parameter 6 6 In Use .. .. DMTF Reserved 0x1000 0x1000 Method Parameters Checked - Job Started 0x1001..0x7FFF 0x1001..0x7FFF Method Reserved 0x8100 0x930C One or more parameters are in wrong SystemScope

0x8420 Not enough CandidateConnections to establish PPRC path

0x8421 Failed to establish PPRC path 0x8422 0x9019 Invalid option for Copy Services 0x8425 Invalid source volume

0x8426 Invalid target volume

0x8427 Invalid source or target volume 0x842B 0x9017 Invalid CopyType 0x842D 0x930B Number of SourceInfo or TargetInfo is wrong

03/28/06-09:29:23 EEP0272I Flushing the buffers to disk...

03/28/06-09:29:23 IDS1030I: FlashCopy started ...

03/28/06-09:29:23 EEP1625I Number of volumes to be processed by Flashcopy: 4

03/28/06-09:29:23 EEP0354I Performing INCR FlashCopy of source volume 75232910912 to target volume

75232910516


75232910136


75232911105


75232910716

03/28/06-09:29:24 EEP0648E An unexpected error was encountered.


TDP function : CIM Error. Failed to execute AttachReplicas().

CIM Error Code : NIResults : <0x9065 0x9065 0x9065 0x9065>

TDP return code : 4


03/28/06-09:29:24 IDS1602I: Waiting for SyncPoint 5 on all EEE nodes...

03/28/06-09:29:25 IDS2562I: Resume database T30 NODE0000 write activities...

03/28/06-09:29:25 IDS0099I: message_id = REQ_DB_RESUME

03/28/06-09:29:25 IDS0099I: status = MSG_OK

03/28/06-09:29:25 IDS0099I: message_id = ANS_DB_RESUME

03/28/06-09:29:25 IDS0099I: status = MSG_OK



03/28/06-09:29:25 IDS2124I: Exiting with return code 2.

1



0x8501...0x8600 Device Connection error

0x8601...0x86FF Device Exception 0x8700 0x8001 Partially successful > 0x9000 0xB000…0xFFFF Device specific error code

Table 7: CIM Agent Return Codes

To get a more detailed information of the FlashCopy error, TSM for ACS provide more information in the error message (1) or in the trace file. The CIM Error Code NIResults, in the above example

<0x9065 0x9065 0x9065 0x9065>

provides the result of each of the 4 FlashCopy relations. NIResults is the result what the CIM Agent gets back from the ESSNI server in the ESS/DS for each of the FlashCopy relations. All 4 FlashCopies

source volume 75232910912 to target volume 75232910516




failed with the same NIResult Code 0x9065. As show in the table above, CIM return codes > 0x9000 indicate a device specific error code. The device specific return codes are made of the hexadecimal numbers 0x90 and 65. In Appendix A and B: a complete list of device specific return codes of the CIM Agents 5.1.0.x and 5.4.0.x for ESS/DS is attached. The most common device specific return codes for ESS/DS are shown in the table below: CIM

5.1.0.x

Code

CIM

5.4.0.x

Code NIResult short name NIResult description

0x9065 0xB016 VOLUME_RESERVED

Action failed because volumes is in RESERVED state, or a target Fixed Block volume is either not ready or cannot be reserved to another initiator.

0x9085 0xB01B INVALID_FLASHCOPY_TARGET FlashCopy target is a PPRC or XRC primary

0x90AE 0xB038 FLC_TARGET_EXISTS FlashCopy target cannot be the target of a new establish

0x90AF 0xB039 FLC_SOURCE_EXISTS

FlashCopy source cannot be the source of a new establish, or flash copy source is identical to flash copy target.

0x90B6 0x9040 EXISTING_FLASHCOPY_STATE The FlashCopy establish or withdraw prohibited by the existing FlashCopy state

Table 8: FlashCopy failed in AttachReplicas – common CIM Agent Return Codes



In the example below, the TDP Return code shown in (1) has a value 34560 (or hexadecimal 0x8700). TDP Return Code 0x8700 of CIM Agent 5.1.0.x means partially successful. Some of the FlashCopy relations could be established successful but other could not be established. In this case 5 FlashCopy relations could be established with NIResults = 0 and 2 failed to establish with NIResults = 0x90b6.

Figure 66: FlashCopy failed in AttachReplicas - EXISTING_FLASHCOPY_STATE

NIResults = 0x90b6 means EXISTING_FLASHCOPY_STATE which indicates, that the FlashCopy source volume has already an existing FlashCopy relation with type INCREMENTAL with a different target volume than the one specified in the current FlashCopy relation. This must fail because the ESS and DS does not allow to have multiple INCREMENTAL relation from the same source volume with different target volumes. The following is a error scenario with CIM Agent 5.4.0.x. where the FlashCopy request was started while a DS µCode upgrade was running. The resulting CIM Agent return code (shown in the trace file) is: 0xB313 The storage unit is busy. Wait for a few seconds, and resubmit the task.

Figure 67: FlashCopy failed in AttachReplicas - BUSY_STATE

09/11/08-14:10:49 IDS1030I FlashCopy started ...


EEP0354I Performing INCR FlashCopy of source volume 00527760 to target volume 10927760


EEP0354I Performing INCR FlashCopy of source volume 10A27760 to target volume 20927760


EEP0354I Performing INCR FlashCopy of source volume 30227760 to target volume 00E27760

EEP0354I Performing INCR FlashCopy of source volume 10E27760 to target volume 00627760

EEP0354I Performing INCR FlashCopy of source volume 10827760 to target volume 10B27760

09/11/08-14:10:54 EEP0648E An unexpected error was encountered.

09/11/08-14:10:54 TDP function name : DsHWInterface::hwStartCopy

TDP function : CIM Error. Failed to execute AttachReplicas().

CIM Error Code : NIResults : <0x0 0x90b6 0x90b6 0x0 0x0 0x0 0x0>



1














TDP function : CIM Error. Failed to execute IBMTSDS_StorageConfigurationService::AttachReplicas , return: 4

TDP return code : 4


IDS1200E: The exception 'CIdsException' was thrown.


IDS1024I: Exiting with return code 2.

1

10/02/2008 18:28:40.704 : HWCommonInterface.cpp(3869): DsHWInterface::hwStartCopy(): Executed AttachReplicas() method, rc =

0x4.

10/02/2008 18:28:40.791 : HWCommonInterface.cpp(6174): DsHWInterface::hwGetErrorCode(): Entering.....

10/02/2008 18:28:40.791 : HWCommonInterface.cpp(6178): DsHWInterface::hwGetErrorCode(): ParameterName: <ReturnCodes>

Value: <45843 45843 45843 45843 45843 45843 45843 45843 45843 45843 >

10/02/2008 18:28:40.806 : HWCommonInterface.cpp(6229): DsHWInterface::hwGetErrorCode(): < 0xb313: b313>

10/02/2008 18:28:40.806 : HWCommonInterface.cpp(6240): DsHWInterface::hwGetErrorCode(): Exiting

10/02/2008 18:28:40.806 : HWCommonInterface.cpp(3883): DsHWInterface::hwStartCopy(): Exiting with rc = <0x4>: EEP1626E An

unexpected error was encountered processing a TSM for ACS function.



TDP return code : 4


2



Solution: Just wait until the DS µCode upgrade has finished and restart the FlashCopy Backup. The following sample shows a similar error as we had listed before with CIM Agent 5.1.0.x where a FlashCopy should be established while one of the target volumes was already in a source/target relation.

Figure 68: FlashCopy failed in AttachReplicas - FLC_TARGET_EXISTS

With CIM Agent 5.4.0.x this results in return code 0xB038 Copy Services operation failure: already a FlashCopy target A similar error can happen at FlashCopy Restore. In the sample below, the FlashCopy Restore failed to execute ModifySynchronizations with NIResults 0x9065 for some FlashCopy relations. Again this is a VOLUME_RESERVED state for these two volumes. The word ‘reverse’ (2) indicates that it is a FlashCopy Restore in this case.

Figure 69: FlashCopy Restore failed in ModifySynchronizations


04/21/06-07:59:50 EEP0354I Performing INCR reverse FlashCopy of source volume 75232910516 to

target volume 75232910912











04/21/06-07:59:52 CIM Error. Failed to execute ModifySynchronizations().

CIM Error Code : NIResults : <0x0 0x9065 0x9065 0x0 0x0 0x0>

04/21/06-07:59:57 IDS1024I: Exiting with return code 1. 1

2













TDP function name : DsHWInterface::hwStartCopy TDP function : CIM Error. Failed to execute IBMTSDS_StorageConfigurationService::AttachReplicas , return: 8001



IDS1200E: The exception 'CIdsException' was thrown.


IDS1024I: Exiting with return code 2.

1

10/02/2008 22:16:16.834 : HWCommonInterface.cpp(3869): DsHWInterface::hwStartCopy(): Executed AttachReplicas() method, rc

= 0x8001.

10/02/2008 22:16:16.838 : HWCommonInterface.cpp(6174): DsHWInterface::hwGetErrorCode(): Entering.....

10/02/2008 22:16:16.838 : HWCommonInterface.cpp(6178): DsHWInterface::hwGetErrorCode(): ParameterName: <ReturnCodes> Val

ue: <45112 0 0 0 0 0 0 0 0 0 >

10/02/2008 22:16:16.839 : HWCommonInterface.cpp(6229): DsHWInterface::hwGetErrorCode(): < 0x0: 0>

10/02/2008 22:16:16.839 : HWCommonInterface.cpp(6229): DsHWInterface::hwGetErrorCode(): <0xb038: b038>

10/02/2008 22:16:16.839 : HWCommonInterface.cpp(6240): DsHWInterface::hwGetErrorCode(): Exiting

10/02/2008 22:16:16.839 : HWCommonInterface.cpp(3883): DsHWInterface::hwStartCopy(): Exiting with rc = <0x8001>: EEP1626E

An unexpected error was encountered processing a TSM for ACS function.





2



Solution: The solution of the problem depends on the reason of the failed FlashCopy. In the following, a solution for the most usual problem is given:

0x9065 VOLUME_RESERVED This error can happen in case of FlashCopy Backup as well as in case of FlashBack Restore. In both cases perform the following steps: 1. Determine which source/target volumes are involved in the failed FlashCopy Check the time, when the AttachReplicas or ModifySynchronizations call is executed. In the example above the ModifySynchronizations call is started at 04/21/06-07:59:50. With this time information, the CIM Agent log and trace files must be searched. First check the files providerTrace.log and providerTrace<N>.log for this timestamp. The following command can also help to check which of the providerTrace<N>.log files is the one of interest:

grep ‘0x9065‘ providerTrace*.log

Replace the NIResults code with the current failure code. This should produce an output like:

providerTrace1.log: 2006-04-21 07:59:51.933+00:00 E tid:117 Error

Code 0x9065 [36965] -> VOLUME_RESERVED 0x9065 [36965] ……

providerTrace1.log: 2006-04-21 07:59:51.934+00:00 E tid:117 Error

Code 0x9065 [36965] -> VOLUME_RESERVED 0x9065 [36965] ……

Here the short description of the CIM error code 0x9065 is shown also. It may happen that the time shown in the providerTrace<N>.log differs from the time shown in the TSM for ACS trace file. This depends on the local time settings on the CIM Agent server and the TSM for ACS server. With the time found in the providerTrace1.log in the sample above, the internalService<N>.log files must be searched for the same time, e.g. with the command

grep ‘2006-04-21 07:59‘ internalService*.log

This should point to the correct internalService.log file. When looking into this file, the following is shown: 2006.04.21 07:59:51,GMT+00:00+00:00 I tid:117 Calling

NIFlashCopyService.establish() Params:

* Source: IBM.2107-7523291/0516; Target: IBM.2107-7523291/0912






* NIFlashCopyEstablishIncrement

* NIFlashCopyEstablishPersistent

* NIFlashCopyEstablishRecordChanges

2006.04.21 07:59:51,GMT+00:00+00:00 I tid:117 Result from



NIFlashCopyService.establish() is: Size is 6

0SUCCES

165 (101)

265 (101)

3SUCCES

4SUCCES

5SUCCES In the sample above, the FlashCopy relations 1 and 2 returned hexadecimal 65 as error code (which is 101 in decimal). And FlashCopy relations 1 and 2 are the source volumes 2309 and 2308 and target volumes 2304 and 2305 of the DS with ID 7523291. 2. Determine why the target volumes are reserved Depending on the FlashCopy operation (Backup or Restore) the reservation state of the target volume must be verified on the backup system or on the production system. It is shown here only for the backup system but is it the same approach for the production system. On the backup system run the following command as user root:

/db2/<SID>/dbs/hdwmap.sh

This produces an output similar to the following:

t1:root:/# /db2/<SID>/dbs/hdwmap.sh

VpathName Serial VolumeNames

----------- ------ -----------



vpath11 752329117E2 hdisk13 hdisk67 hdisk121

...

If the DS volumes with serial number 75232912304 and 75232912305 cannot be found, then a cfgmgr command needs to be started followed by the

/db2/<SID>/dbs/hdwmap.sh. The following output is show for the command:

t1:root:/# /db2/<SID>/dbs/hdwmap.sh | grep –E ‘2304|2305‘



vpath35 and vpath36 are the target volumes which are reserved. 3. Remove the reservation of the target volumes There are two possibilities why a target volume is reserved. Either it is currently used in a volume group (and the volume group is varied on) or the reservation state of the target volume could not be released by AIX while varying the volume group off. The latter is an error of AIX and/or ESS and should result in a error message in AIX error report (errpt). If the volume is still active in a volume group (can be verified with the

command lspv | grep vpath35), then just vary off this volume group and

export it from the backup system (varyoffvg <VGname> ; exportvg

<VGname>). This removes the reservation state from the target volume.



If the volume does not belong to a volume group, then the reservation state can

be checked and released with the command lquerypr (if called without any argument, it display a help on how to use this command). 4. Re-run the FlashCopy Backup or the FlashBack Restore The FlashCopy Backup or FlashBack Restore can be restarted after successfully releasing the reservation state of the target volume.



Unit 10

Appendix: CIM Agent 5.1.0.x

NIResult Codes

NIResult Code

NIResult short name NIResult description

11 NOT_READY_FOR_RESYNC

The volumes, for which an attempt to resync PPRC was made, were not in a state to be resynced. The source or target was not suspended.

12 VOLUMES_NOT_SIMPLEX The attempt to establish a PPRC pair on volumes not in the simplex state.

13 VOLUME_LONG_BUSY

For PPRC establish, this occurs when one of the volumes is already participating in an Extended Remote Copy or Concurrent Copy State For FlashCopy, this occurs when the volume is in the long busy state, not yet configured, not formatted, or the Source and Target volumes are of different types.

15 PINNED_DATA The establish PPRC command failed because one of the volumes is suspended with pinned data.

16 INVALID_PPRC_SECONDARY Invalid PPRC secondary. The address of the PPRC secondary is invalid.

1B NO_PPRC_EXISTS Attempt to suspend or terminate volumes that are not in a PPRC relationship.

1C PPRC_COPY_PENDING The attempt to suspend a volume failed because the relationship is still copy pending.

22 DEVICE_STATUS_CANNOT_BE_DETERMINED

A device specified in an Establish Peer-to-Peer Remote Copy Pair order, a DSO Establish FlashCopy order, or any of the volume specified in a Manage Session Members command is unconfigured, is in CE Mode, is in the 'Status Cannot be Determined' state, or is of the wrong type.

26 VOLUME_MISMATCH

The attempt to establish a PPRC pair failed because one of the following cases: * The capacity of the volumes does not match. The source must be equal or smaller than the target * The type of the volumes does not match

37 CODE_LOAD_IN_PROGRESS Action failed because microcode code load is in progress.

51 PATH_LIMITED_EXCEEDED

The attempt to establish the path failed because the attempt would cause more than 4 paths from a single local adapter or more than 8 to any attached adapter.

52 CHANNEL_EXTENDER_ERROR

The channel extender being used for the action is reporting an error. One of the following conditions is occurring: * Abnormal conditions at the secondary * Failed communication path * Failed communications with secondary

53 INVALID_SSID One of the SSID supplied does not match what is stored in the ESS or the LSS is not a valid configured LSS.

Unit 10: Appendix: CIM Agent 5.1.0.x NIResult Codes TSM for ACS Workshop


54 SECONDARY_ERROR

An error on the secondary caused the command to fail. Either cache is not enabled on the secondary or Nonvolatile storage on the secondary is not available.

55 PATH_ESTABLISH_FAILED The path established failed. Query the paths to determine the state of the failed path.

56 PINNED_DATA_DURING_ESTABLISH Pinned data caused the establish action to fail.

57 WRITE_PROHIBITED_BY_SUSPEND Action failed because volume was suspended

58 PREEXISTING_PPRC Action conflicts with existing PPRC relationship on volumes

59 PAIRS_REMAIN Path terminate failed because PPRC pairs are currently using the path

5A PATH_TIMEOUT Action failed because communication to secondary timed out

60 TARGET_ONLINE Action failed because target is online to a host

62 LSS_OWNERSHIP The action failed because of a mismatch LSS

65 VOLUME_RESERVED

Action failed because volumes is in RESERVED state, or a target Fixed Block volume is either not ready or cannot be reserved to another initiator.

80 SPECIAL_INTERCEPT_SET

A FlashCopy request from ESSNI will be rejected if SIC (Special Intercept Condition) is set for the source or target volume. If an account requires to establish or withdraw a FlashCopy on a V=R guest device, they must either detach the volume from the host at which point they may use ESSNI, or use host commands to accomplish the task.

82 RELATIONSHIP_COUNT_EXCEEDED Action failed because maximum number of FlashCopy relationships have already been established

83 BATTERY_FEATURE_UNAVAILABLE FlashCopy Battery feature not installed

84 INVALID_FLASHCOPY_VOLUMES The Establish FlashCopy action failed because the volumes are not the same capacity or are on different LSS

85 INVALID_FLASHCOPY_TARGET FlashCopy target is a PPRC or XRC primary

86 FEATURE_NOT_INSTALLED Feature not installed

87 VOLUME_IN_USE Volume in use by XRC or TDMF

8A VOLUME_NOT_RESTORABLE Restore action failed because volumes was not in a Persistent FlashCopy relationship whose background copy completed

8B CRITICAL_VOLUME_MODE_UNAVAILABLE Action failed because critical volume mode cannot be specified with non-synchronous PPRC

8C FLASH_INITIALIZE_IN_PROGRESS Establish Flash Copy or PPRC pair failed because Flash Initialize was in progress.

8D REMOTE_ESTABLISH_EXISTING Remote Flash Copy establish attempt failed because volume is already in flash copy relationship

8F FLASHCOPY_TARGET_EXISTING PPRC secondary specified for establish is already a FlashCopy target

94 INBAND_PATH_UNAVAILABLE

The inband established because the conduit LSS specified does not have a PPPRC relationship established with the flash copy primary

96 INVALID_PPRC_TRANSITION

An Establish Peer-to-Peer Remote Copy Pair command attempted to perform a transition between modes that is not allowed. The only valid transition to Peer-to-Peer Remote Copy Extended Distance is from a state of suspension.



97 INCREMENT_MISMATCH Attempt to increment a FlashCopy relationship Failed because volumes were in relationship with other volumes

99 ACTION_NOT_SUPPORTED Command not supported by ESS microcode

9A INCREMENT_INTERNAL_ERROR Relationship could not be incremented due to an external error

9B TARGET_RESERVED Action failed because target is reserved

9C FLASHCOPY_ESS_LIMITATION_EXCEEDED

Maximum number of FlashCopy relationships have already been established on the ESS or the Flashinit function is not complete on this volume

9D FLASHCOPY_VOLUME_LIMITATION_EXCEEDED Maximum number of FlashCopy relationship have already been established for this volumes

A0 INVALID_INBAND_FLASHCOPY_SOURCE The FlashCopy source is no the target of the PPRC relationship to which the action was addressed

A1 DUPLICATE_SOURCE_DESTINTATION_PORT

The source and destination ports for a PPRC path over FCP must be unique.Any single port cannot be used as both source and destination.

A2 MIXED_ADAPTERS_SPECIFIED

An Establish PPRC Path command must specify all ESCON paths or all FCP paths. ESCON and FCP paths may not be mixed within the same command.

A3 INVALID_WWNN_FOR_ESS The primary and secondary WWNN (World Wide Node Name) must be a valid WWNN for an ESS box.

A4 INVALID_FCP_CONFIGURATION

If FCP paths are specified in the PPRC Establish Path command, then the protocol of the adapters specified in the command may not be FCAL (Fibre Channel Arbitrated Loop).

A5 INVALID_FLC_EXTENT The FlashCopy operation does not allow the specification of extents - it is only valid for full volume.

A6 FLASHCOPY_TARGET_LIMITATION_EXCEEDED Maximum number of FlashCopy targets for this source have been exceeded

A7 CASCADING_FLASHCOPY_PROHIBITED FlashCopy target cannot be a FlashCopy source or the target of another relationship

A9 FLASHCOPY_INHIBITED FlashCopy establish inhibited on this volume

AD VOLUME_INACCESSIBLE Flashcopy failed because volumes in inaccessible or offline state

AE FLC_TARGET_EXISTS FlashCopy target cannot be the target of a new establish

AF FLC_SOURCE_EXISTS FlashCopy source cannot be the source of a new establish, or flash copy source is identical to flash copy target.

B0 ESCON_FCP_ESTABLISH_COLLISION

An attempt was made to Establish ESCON PPRC paths between two control units with FCP paths already existing between the control units, or an attempt was made to Establish FCP PPRC paths between two control units with ESCON paths already existing between the control units. The World Wide Node Name or Control Unit Serial Number for the secondary control unit could not be obtained, so the determination that the command was acting on an existing association was made based on the secondary SSID which may not be unique.

B1 FCP_FICON_PATH_ESTABLISH_COLLISION An attempt was made to Establish FCP PPRC paths on a port with existing FICON logical paths.



B2 ESCON_FCP_REMOVE_COLLISION

An attempt was made to Establish or Remove ESCON PPRC paths between two control units with FCP paths already existing between the control units, or an attempt was made to Establish or Remove FCP PPRC paths between two control units with ESCON paths already existing between the control units.

B3 PATH_TYPE_MISMATCH Path establish failed for ESCON, because FCP paths exist or the reverse

B4 REVERSE_BITMAP_NON_ZERO Reverse FlashCopy attempt failed because bitmap was not all zeros

B5 NO_VOLUME_ZERO Path establish fails because no volume 0 exists

B6 EXISTING_FLASHCOPY_STATE The FlashCopy establish or withdraw prohibited by the existing FlashCopy state

B7 VM_MINIDISK FlashCopy failed because volumes managed by VM_MINIDISK

B8 INVALID_REVERTIBLE_RELATIONSHIP

A FlashCopy establish was specified with the revertible option for a pair that does not exist or is already revertible, or a FlashCopy withdraw was specified on a pair that is not revertible.

BC FLASH_COPY_FRR_INVALID_STATE A FlashCopy establish with FRR will fail if a FRR is still in progress or if one has already completed.

BF PPRC_RECOVERY_COMMAND_REJECTED

An Establish Peer-to-Peer Remote Copy Pair command specifying PPRC Failover Mode or PPRC Failback Mode was received, but the Peer-to-Peer Remote Copy pair is already in the requested state.

C0 FAILOVER_PRIMARY_INVALID PPRC failover primary supplied does not match the existing PPRC primary for the volume

C1 FAILOVER_SECONDARY_INVALID PPRC failover action failed because volume was not a full duplex PPRC secondary

C2 FAILBACK_PRIMARY_INVALID PPRC failback primary supplied does not match the existing PPRC primary for the volume

C3 FAILBACK_PRIMARY_NOT_SUSPENDED Volume is not a suspended PPRC primary

C4 XDC_CONSISTENCY_CANNOT_MAINTAIN

XDC consistency cannot be maintained due to timeout of paused increment or other problem that has caused the volume to be in an incorrect state.

C5 VOLUMES_IN_SESSION Close session cannot be performed because volumes still exist in the session.

C6 CASCADING_SECONDARY_SYNCHRONOUS Cascading PPRC secondaries may not be primary volumes in a Synchronous PPRC relationship

C7 CASCADING_SECONDARY_NONCASCADE Volume was not established with Cascading option previously

C8 CASCADING_PRIMARY_EXTENDED_DISTANCE Cascading primary cannot be in an existing extended distance relationship

C9 SESSION_ALREADY_OPEN The specified session is already open for the LSS or the maximum number of sessions allowed has been met.

CA VOLUME_IN_SESSION The specified volume is already associated with a session.

CB SESSION_NOT_OPEN The session specified for member management is not open.

CC INVALID_SESSION_STATE XDC Start failed because session or session members are not in the correct state.

CD INVALID_SESSION_STATE_FOR_FLC XDC session not in correct state when the Async master issued establish FlashCopy.

D0 TOPOLOGY_MISSING_PATHS PPRC Paths do not exist for specified topology.



D1 EXISTING_MASTER_PROCESS

A Start/Resume Async command with no modify options was sent to an ESS on which an Async PPRC master process was already running, or a Start/Resume Async command with modify was sent to an ESS, but the parameters did not match the existing configuration or the existing master process was not paused.

D2 NON_EXISTENT_ASYNC_CONFIGURATION A Pause/Terminate Async command specified a configuration that does not exist.

D3 MAX_MASTERS_SPECIFIED A Start/Resume Async command was received by a subordinate ESS which already had 32 masters.

D4 MISMATCHED_SEQUENCE_NUMBERS

Master and/or Subordinate sequence number specified does not match the master/subordinate sequence numbers for the given session ID, or the specified session ID did not match the session ID for the master sequence number.

D6 ALREADY_PROCESSING_ASYNC_COMMAND

An Async subordinate process received an Async PPRC action (establish/withdraw FLC, start increment) while processing a previously received Async PPRC action.

D7 ASYNC_STRUCTURES_UNAVAILABLE

A Start/Resume or Pause/Terminate Async command failed because internal structures could not be updated or accessed due to failure or due to the ESS being in single cluster mode.

D8 CONSISTENT_DATA_COMPROMISED

A Pause/Terminate Async PPRC failed because the termination could not complete without compromising the consistent copy of the data

F02 COPY_SERVICES_SERVER_INTERNAL_ERROR An internal error occurred in the copy services server. Contact IBM Support.

F03 ACTION_NOT_SUPPORTED_BY_ESS Action failed because the microcode level of the ESS did not support this action.

F04 ESS_NOT_FOUND The ESS was not found in the CopyServices domain.

F05 LSS_NOT_FOUND The LSS was not found in the CopyServices domain.

F06 VOLUMES_NOT_FOUND The volumes were not found in the copyservices domain.

F07 PAIR_CAPACITY_MISMATCH The capacity of the targets must be greater than or equal to the size of the sources provided..

F08 ESS_NOT_AVAILABLE Communication was the ESS was unavailable. Retry..

F09 COPY_FEATURE_NOT_INSTALLED Copy Feature was not installed on this ESS.

F0A CKD_MANAGEMENT_DISABLED Management of CKD resources on this ESS is disabled Contact IBM support to enable.

F0B COPY_FEATURE_NOT_SUPPORTED The ESS does not support the action supplied.

F0C PARAMETER_INVALID Format 0 sense error type 04. A data argument of a command is invalid.

F0D PARAMTER_TRACK_INVALID

Format 0 sense error type 0b. Invalid Defective/Alternate Track Pointer. Generated if a defective track is accessed. The subsystem generates an invalid Defective/Alternate Track Pointer as part of RAID Recovery.

F0E PPRC_SECONDARY_COMMAND_INVALID

Format 0 sense error type 0e. Command not allowed on a secondary device has been received by the secondary device.

F0F REDRIVE_COMMAND

Format 0 sense error type f0. Functional code did not accept the command due to being busy. Command must be redriven.



F10 DEVICE_NOT_FOUND

One of the following may have occurred 1) The request was issued to a volume that is not configured 2) The request requires at least one volume to be configured and there are no volumes configured for this LSS 3) If it is not one of the above, an unknown error condition has occurred.

F11 ASYNC_COPY_FEATURE_NOT_INSTALLED The Asynchronous PPRC feature is not installed on this ESS. ´

F12 SESSION_COMMAND_NOT_DEFINED The submitted session command was not properly defined. Verify all parameters and then submit the command again.

F13 SESSION_NUMBER_INVALID The specified session number is invalid. A session number is an integer between 1 and 255 inclusive.

F14 SESSION_MEMBER_NOT_DEFINED The submitted session members are not defined. Verify that the volumes specified are valid.

F15 ASYNC_COMMAND_NOT_DEFINED

The submitted Asynchronous PPRC command was not properly defined. Verify all parameters and then attempt the command again.

F16 MASTER_SERIAL_NUMBER_NOT_DEFINED

The specified Master serial number is not properly defined. Verify that the serial number is correct and then attempt the task again.

F17 SUBORDINATE_COUNT_OUT_OF_RANGE The specified subordinate count is out of range. The subordinate count must be between 0 and 16 inclusive.

F18 FCP_QUERY_NOT_SUPPORTED FCP Connectivity queries are not supported by this ESS.

F19 STATUS_CANNOT_BE_DETERMINED

Status cannot be determined because the cluster processor encounters one of the following problems: 1) unable to locate the Global subsystem status tracks, 2) unable to establish the status of a PPRC pair or a DASD Fast Write volume, 3) unable to access the RAID rank that the data is stored on, 4) unable to access the LSA dir for a LSA Subsystem, 5) unable to synchronize the volume with data in the NVS.

F20 REDRIVE_COMMAND_FEW_SECONDS

Format 0 sense error type f0. Functional code did not accept the command due to being busy. Command may be redriven in a few seconds.

F21 REDRIVE_COMMAND_FEW_MINUTES

Format 0 sense error type f0. Functional code did not accept the command due to being busy. Command may be redriven in a few minutes.

FAA PPRC_XD_INVALID_TRANSITION

For PPRC Extended Distance, an invalid transition between establishment modes was attempted. A transition from Extended Distance to any mode other than PPRC Synchronous mode is not allowed.

BE700064 ALIAS_ADDRESS_NOT_ALLOWED The action failed because the CKD device was specified with an alias address, when it must be a base address.

BE704000 INTERVENTION_REQUIRED

The action failed and intervention is required. Intervention is required due to one of the following: * The addressed device is in CE mode * The addressed device is not ready * The volume configuration of the addressed device is not correct Sense byte 0 = 0x40 specifies intervention is required.

BE701000 EQUIPMENT_CHECK Equipment Error, an unusual hardware condition originated in the channel, storage facility or drive. Contact IBM support.



BE70FF00 PERF_NO_LSS_CONFIGURED The performance statistics request sent requires an LSS to be configured, and there is none configured.

BE70FF01 PERF_RESOURCE_NOT_CONFIGURED The rank, extent pool, or IO port queried for performance statistics is not configured.

Table 9: NIResult Code



Unit 11

Appendix: CIM Agent 5.4.0.x

Return Codes

This is a comprehensive list of all vendor specific return codes supported by the CIM Agent Vendor-specific provider return codes Return Description

code 0x8000 Internal provider error 0x8001 Operation partially succeeded 0x8002 Invalid string format 0x8003 Not supported for ESS machine type. 0x8004 Copy operation failed because the volume is still initializing 0x8005 Not supported for DS machine type. 0x8006 Operation failed because device was quarantined. Check the storage device for internal problems. 0x8007 Internal provider error 0x8008 Primary and secondary IP's must be unique 0x8009 The CIM agent is already configured to manage the devices at the specified IP address(es) 0x9000 Invalid Element Name 0x9001 Invalid StorageID 0x9003 Invalid OtherIDType 0x9004 Invalid Setting 0x9005 Invalid HardwareID 0x9007 Invalid DeviceNumber 0x9008 Invalid InitiatorPortID 0x9009 Invalid ProtocolController 0x900A Invalid VolumeID 0x900B Invalid InPools parameter 0x900C Invalid Size parameter 0x900D Invalid Goal parameter 0x900E At least one parameter must be passed to continue the operation 0x900F Invalid InPool parameter 0x9010 inExtents parameter is not supported 0x9011 Invalid Element Type. 0x9012 Modification of DataTypeSettings for Volume is not supported 0x9013 Invalid quantity 0x9014 InPool must be specified in Volume Creation. InPool cannot be specified in Volume Modification. 0x9015 Modification of Volume Size is not possible 0x9016 Modification of LssNumber is not supported 0x9017 Invalid CopyType specified. 0x9018 At least one Source and one Target must be specified. 0x9019 Invalid Option found. 0x901A Invalid Operation specified. 0x901B At least one Synchronization must be specified. 0x901C Invalid DeviceConfig parameter 0x901D Invalid DeviceType parameter 0x901E Invalid ElementType parameter 0x901F Target volumes cannot be a mix of space efficient and standard 0x9020 Invalid ManifestCollection 0x9021 Not a valid IP address. 0x9022 Element type is invalid. 0x9023 Synchronization passed in is invalid. 0x9024 The specified device is invalid. 0x9025 The specified trace components are invalid 0x9026 The specified volume group type is invalid 0x9027 The specified volume group is invalid 0x9028 The specified host type is invalid 0x9029 VolumeGroup or TargetPortID must be specified 0x902A The specified WWPN is invalid

Unit 11: Appendix: CIM Agent 5.4.0.x Return Codes TSM for ACS Workshop


0x902B unable to remove a device by using backup IP /* * 0x9300 - 0x93FF - argument coexistence error * MISMATCH_<PARAMNAME1>_<PARAMNAME2> */ 0x9300 LUNames does not match DeviceAccess 0x9301 LUNames or TargetPortID must be specified 0x9302 PortProfile does not match VolumeType 0x9303 VolumeType does not match VolumeGroup type 0x9304 VolumeGroup type does not match VolumeGroup of the host port 0x9305 VolumeGroup type does not match volumes number 0x9306 InitiatorPortID does not match protocol controller 0x9307 The ESSID of the machine is not matching with the one's passed in. 0x9308 Data type and extent type do not match. 0x9309 Number of ElementNames does not match the number of Elements. 0x930A Storage Configuration SystemName and Element SystemName should be equal 0x930B Same number of Sources a Targets must be specified. 0x930C Source Volume and Target Volume must belong to same system. 0x930D Source Volume must be located on scope system. 0x930E The ESSID of IP does not match the ESSID of IP2. /* * 0x9400 - 0x94FF - specified object does not exist * NONEXISTENT_<PARAMNAME> */ 0x9400 Nonexistent WWPN. 0x9401 Nonexistent Port Profile. 0x9402 Nonexistent Volume Group 0x9403 Nonexistent Volume. 0x9404 Nonexistent Rank. 0x9405 Nonexistent Extent Pool. 0x9406 Nonexistent Port. 0x9407 Nonexistent Array. 0x9408 Nonexistent Device. 0x9409 Nonexistent IP Address 0x940a Specified Volume does not exist in specified Volume Group. /* * 0x9500 - 0x9AFF - to be defined.... */ 0x9500 All LCU/LSS are taken. 0x9501 New Volume are not available. 0x9502 Operation failed 0x9503 Not enough disk space available. 0x9504 No more LUNs for this LSS/LCU. ** DS device return codes ** 0xB001 Operation failure: unknown. Contact IBM technical support for assistance. 0xB002 Operation failure. Contact IBM technical support for assistance. 0xB003 Copy Services operation failure: not ready for resynchronization 0xB004 Copy Services operation failure: volumes not simplex 0xB005 Copy Services operation failure: The volume is in a long busy state, not yet configured, not yet formatted, or the source and target volumes are of different types. 0xB006 Copy Services operation failure: pinned data 0xB007 Copy Services operation failure: incorrect secondary. Contact IBM technical support for assistance. 0xB008 Copy Services operation failure: device status cannot be determined 0xB009 Copy Services operation failure: source and target volume mismatch 0xB00A Copy Services operation failure: A microcode code load is in progress. 0xB00B The establish Metro Mirror path task cannot be initiated because the task would result in an unsupported configuration of logical subsystem pairs or logical paths. 0xB00C Remote Mirror and Copy operation failure 0xB00D Copy Services operation failure: The Metro Mirror pair does not exist. 0xB00E Copy Services operation failure: secondary error. Contact IBM technical support for assistance. 0xB00F Copy Services operation failure: One or more path establish tasks has failed. 0xB010 Copy Services operation failure: pinned data 0xB011 Copy Services operation failure: writes prohibited by suspend 0xB012 Copy Services operation failure: preexisting Remote Mirror and Copy pair. Contact IBM technical support for assistance. 0xB013 Copy Services operation failure: pairs remain 0xB014 Copy Services operation failure: target online 0xB015 Copy Services operation failure: logical subsystem mismatch. Contact IBM technical support for assistance.



0xB016 Copy Services operation failure: volume reserved. Contact IBM technical support for assistance. 0xB017 Operation failed: A VM host command has set a Special Intercept Condition (SIC) on the source or target volume. 0xB018 Copy Services operation failure: maximum number of FlashCopy relationships exceeded 0xB019 Copy Services operation failure: FlashCopy battery feature not installed 0xB01A Copy Services operation failure: incompatible volumes 0xB01B Copy Services operation failure: incorrect FlashCopy target 0xB01C Copy Services operation failure: feature not installed 0xB01D Copy Services operation failure: volume in use. Contact IBM technical support for assistance. 0xB01E Copy Services operation failure: path not available 0xB01F Copy Services operation failure: incorrect transition. Contact IBM technical support for assistance. 0xB020 Copy Services operation failure: FlashCopy increment mismatch 0xB021 Operation failure: action not supported 0xB022 Copy Services operation failure: volumes not a Remote Mirror and Copy pair 0xB023 Copy Services operation failure: copy pending. Contact IBM technical support for assistance. 0xB024 Copy Services operation failure: path timeout. Contact IBM technical support for assistance. 0xB025 Copy Services operation failure: volume not restorable. Contact IBM technical support for assistance. 0xB026 Copy Services operation failure: critical volume mode unavailable 0xB027 Unable to establish FlashCopy or Remote Mirror and Copy pair. A FlashCopy initialization is in progress. 0xB028 Copy Services operation failure: volume already in FlashCopy relationship 0xB029 Copy Services operation failure: Volume is already a FlashCopy target. 0xB02A Copy Services operation failure: increment failed due to internal error. Contact IBM technical support for assistance. 0xB02B Copy Services operation failure: target reserved. Contact IBM technical support for assistance. 0xB02C Copy Services operation failure: maximum FlashCopy relationships exceeded or initialization in progress 0xB02D Copy Services operation failure: maximum relationships exceeded 0xB02E Copy services operation failure: incorrect FlashCopy source 0xB02F Copy Services operation failure: source is destination 0xB030 Copy Services operation failure: mixed adapters specified 0xB031 Copy Services Operation failure: incorrect WWNN 0xB032 Copy Services operation failure: incorrect fibre-channel protocol configuration 0xB033 Copy Services operation failure: incorrect FlashCopy extent. Contact IBM technical support for assistance. 0xB034 Copy Services operation failure: maximum FlashCopy targets exceeded 0xB035 Copy Services operation failure: cascading FlashCopy prohibited 0xB036 Copy Services operation failure: FlashCopy inhibited. Contact IBM technical support for assistance. 0xB037 Copy Services operation failure: volume inaccessible 0xB038 Copy Services operation failure: already a FlashCopy target 0xB039 Copy Services operation failure: already a FlashCopy source 0xB03A Copy Services operation failure: ESCON - FCP collision. Contact IBM technical support for assistance. 0xB03B Copy Services operation failure: FCP - FICON path collision 0xB03C Copy Services operation failure: ESCON - FCP remove collision. Contact IBM technical support for assistance. 0xB03D Operation failure: path type mismatch. Contact IBM technical support for assistance. 0xB03E Copy Services operation failure: reverse bitmap non-zero. Contact IBM technical support for assistance. 0xB03F Copy Services operation failure: no volume zero on secondary logical subsystem. Contact IBM technical support for assistance. 0xB040 FlashCopy operation failure: action prohibited by current FlashCopy state. Contact IBM technical support for assistance. 0xB041 Copy Services operation failure: VM minidisk. Contact IBM technical support for assistance. 0xB042 Copy Services operation failure: incorrect revertible specification 0xB043 Unable to establish FlashCopy with fast reverse restore: previous FRR 0xB044 Copy Services: recovery command rejected 0xB045 Copy Services operation failure: incorrect failover primary site 0xB046 Operation failure: incorrect failover secondary volume 0xB047 Copy Services operation failure: incorrect failback primary 0xB048 Copy Services operation failure: failback primary volume not suspended 0xB049 Copy Services operation failure: Global Mirror consistency cannot be maintained. Contact IBM technical support for assistance. 0xB04A Copy Services operation failure: volumes in session 0xB04B Copy Services operation failure: cascading secondary synchronous 0xB04C Copy Services operation failure: cascading secondary noncascade 0xB04D Copy Services operation failure: cascading primary 0xB04E Copy Services operation failure: session already open. Contact IBM technical support for assistance. 0xB04F Copy Services operation failure: volume in session 0xB050 Copy Services operation failure: session not open 0xB051 Copy Services operation failure: session or members not in correct state. 0xB052 Copy Services operation failure: incorrect session state for FlashCopy. Contact IBM technical support for assistance. 0xB053 Copy Services operation failure: topology missing paths. Contact IBM technical support for assistance. 0xB054 Copy Services operation failure: master process conflict 0xB055 Copy Services operation failure: configuration does not exist 0xB056 Copy Services operation failure: maximum masters exceeded. Contact IBM technical support for assistance. 0xB057 Copy Services operation failure: sequence number and session ID mismatch 0xB058 Copy Services operation failure: currently processing a previously issued Global Mirror command 0xB059 Copy Services operation failure: Global Mirror structures not available 0xB05A Operation failure: consistent copy would be compromised. Contact IBM technical support for assistance. 0xB05B Copy Services operation failure: warm start occurred. Contact IBM technical support for assistance. 0xB05C Operation failure: action cancelled due to lack of resources. Contact IBM technical support for assistance. 0xB05D Copy Services server internal error. Contact IBM technical support for assistance.



0xB05E Operation failure: action not supported 0xB05F Copy Services operation failure: storage image not found 0xB060 Copy Services operation failure: LSS not found 0xB061 Copy Services operation failure: volumes not found 0xB062 Pair capacity mismatch 0xB063 Copy Services operation failure: storage image not available 0xB064 Copy Services feature not installed. Contact IBM technical support for assistance. 0xB065 CKD management is disabled. Contact IBM technical support for assistance. 0xB066 Copy Services feature not supported. Contact IBM technical support for assistance. 0xB067 Copy Services operation failure: incorrect parameter. Contact IBM technical support for assistance. 0xB068 Copy Services operation failure: incorrect track. Contact IBM technical support for assistance. 0xB069 Copy Services operation failure: secondary command is not valid. Contact IBM technical support for assistance. 0xB06A Copy Services operation failure: busy 0xB06B Copy Services operation failure: device not found 0xB06C Copy Services operation failure: Global Mirror feature not installed 0xB06D Copy Services operation failure: session command not defined. Contact IBM technical support for assistance. 0xB06E Copy Services operation failure: incorrect session ID 0xB06F Copy Services operation failure: session members not defined 0xB070 Copy Services operation failure: Global Mirror command not properly defined. Contact IBM technical support for assistance. 0xB071 Copy Services operation failure: master serial number not defined. Contact IBM technical support for assistance. 0xB072 Copy Services operation failure: subordinate count out of range. Contact IBM technical support for assistance. 0xB073 Copy Services operation failure: FCP connectivity queries are not supported by the storage image. Contact IBM technical support for assistance. 0xB074 Operation failure: status cannot be determined. Contact IBM technical support for assistance. 0xB075 Copy Services operation failure: Global Mirror incorrect transition. Contact IBM technical support for assistance. 0xB076 Array operation failure: Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB077 Unable to repair array. Contact IBM technical support for assistance. 0xB078 Unable to repair array. Contact IBM technical support for assistance. 0xB079 Unable to create array: The maximum number of arrays have been created. 0xB07A Unable to create array: internal interface communication error. Contact IBM technical support for assistance. 0xB07B Unable to create array: The array site is not unassigned. 0xB07C Unable to create array: The RAID type is neither RAID5 nor RAID10. 0xB07D Unable to assign the rank to the extent pool. The rank is already assigned to another extent pool. 0xB07E Unable to create array. Contact IBM technical support for assistance. 0xB07F Operation failure. Contact IBM technical support for assistance. 0xB080 Internal error. Contact IBM technical support for assistance. 0xB081 Operation failure: incorrect RAID type or number of spares. Contact IBM technical support for assistance. 0xB082 Cannot use array sites. These sites are flagged to be serviced. 0xB083 Cannot delete array. The array is flagged to be serviced. 0xB084 Unable to create array. Contact IBM technical support for assistance. 0xB085 Unable to create or delete array: local server offline 0xB086 Unable to create array. Contact IBM technical support for assistance. 0xB087 Unable to create array: memory allocation error. Contact IBM technical support for assistance. 0xB088 Unable to create array. Contact IBM technical support for assistance. 0xB089 Unable to delete array. Contact IBM technical support for assistance. 0xB08A Unable to delete array. Contact IBM technical support for assistance. 0xB08B Unable to delete array. Contact IBM technical support for assistance. 0xB08C Unable to delete array. The array must be in an unassigned state. 0xB08D Unable to delete array. Contact IBM technical support for assistance. 0xB08E Array creation failure: Too many array sites specified. 0xB08F Array site operation failure: The array site is used in another array. 0xB090 Rank repair operation failure: At least one array must be in assigned status. Contact IBM technical support for assistance. 0xB091 Unable to create array. Array sites must be in the same loop. 0xB092 Rank reconfiguration failure: memory allocation error. Contact IBM technical support for assistance. 0xB093 Operation failure: unable to allocate memory. Contact IBM technical support for assistance. 0xB094 Operation failure. Contact IBM technical support for assistance. 0xB095 Operation failure: unable to allocate memory. Contact IBM technical support for assistance. 0xB096 Operation failure. Contact IBM technical support for assistance. 0xB097 Operation failure: unable to allocate memory. Contact IBM technical support for assistance. 0xB098 Rank operation failure: Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB099 Rank reconfiguration failure: The rank is flagged to be serviced. 0xB09A Rank repair operation failure: Service intent flag is set. Contact IBM technical support for assistance. 0xB09B Rank operation failure. Contact IBM technical support for assistance. 0xB09C Rank operation failure. Contact IBM technical support for assistance. 0xB09D Rank operation failure. Contact IBM technical support for assistance. 0xB09E Rank operation failure. Contact IBM technical support for assistance. 0xB09F Rank repair operation failure. Contact IBM technical support for assistance. 0xB0A0 Rank repair operation failure: Unable to establish array site communication session. Contact IBM technical support for assistance. 0xB0A1 Rank repair operation failure: Unable to retrieve adapter name. Contact IBM technical support for assistance. 0xB0A2 Rank operation failure. Contact IBM technical support for assistance.



0xB0A3 Unable to unassign rank. Contact IBM technical support for assistance. 0xB0A4 Unable to unassign rank: Extents are allocated to logical or auxiliary volumes. 0xB0A5 Unable to assign rank to extent pool. Contact IBM technical support for assistance. 0xB0A6 Unable to assign rank to extent pool. Contact IBM technical support for assistance. 0xB0A7 Rank operation failure: device adapter error 0xB0A8 Rank repair operation failure: device adapter error. Contact IBM technical support for assistance. 0xB0A9 Rank repair operation failure: Multiple ranks exist or the rank is still accessible. Contact IBM technical support for assistance. 0xB0AA Rank repair operation failure: Unable to delete RAID array. Contact IBM technical support for assistance. 0xB0AB Rank repair operation failure: Unable to retrieve serial number. Contact IBM technical support for assistance. 0xB0AC Unable to create rank: The maximum number of ranks has been created. 0xB0AD Unable to create rank: Too many arrays are specified. 0xB0AE Unable to delete rank: The rank is still assigned. 0xB0AF Unable to delete rank: Extents are in use. 0xB0B0 Rank operation failure. Contact IBM technical support for assistance. 0xB0B1 Unable to assign rank to extent pool: The extent pool does not exist. 0xB0B2 Unable to assign rank to extent pool: The rank is not in the unassigned state. 0xB0B3 Rank operation failure: rank does not exist. 0xB0B4 Rank operation failure. Contact IBM technical support for assistance. 0xB0B5 Unable to unassign rank 0xB0B6 Rank operation failure: rank does not exist. 0xB0B7 Unable to reserve rank 0xB0B8 Rank operation failure: rank does not exist. 0xB0B9 Unable to release rank 0xB0BA Rank operation failure: extent pool does not exist. 0xB0BB Rank definition failure: extent type mismatch 0xB0BC Rank operation failure. Contact IBM technical support for assistance. 0xB0BD Rank operation failure. Contact IBM technical support for assistance. 0xB0BE Rank operation failure. Contact IBM technical support for assistance. 0xB0BF Rank operation failure. Contact IBM technical support for assistance. 0xB0C0 Unable to create rank: array does not exist. 0xB0C1 Unable to create rank: Array is not unassigned. 0xB0C2 Unable to repair array. Contact IBM technical support for assistance. 0xB0C3 Unable to repair array. Contact IBM technical support for assistance. 0xB0C4 Unable to repair array. Contact IBM technical support for assistance. 0xB0C5 Unable to repair array. Contact IBM technical support for assistance. 0xB0C6 Unable to repair array. Contact IBM technical support for assistance. 0xB0C7 Unable to repair array. Contact IBM technical support for assistance. 0xB0C8 Unable to repair array. Contact IBM technical support for assistance. 0xB0C9 Unable to repair array. Contact IBM technical support for assistance. 0xB0CA Unable to repair array. Contact IBM technical support for assistance. 0xB0CB Unable to repair array. Contact IBM technical support for assistance. 0xB0CC Unable to create rank: not in dual server mode 0xB0CD Unable to delete rank: not in dual server mode 0xB0CE Unable to delete rank 0xB0CF Unable to delete rank. Contact IBM technical support for assistance. 0xB0D0 Unable to create rank: Service intent is set on the array. 0xB0D1 Unable to delete rank: Service intent is set. 0xB0D2 Unable to repair array: Service intent is set. 0xB0D3 Unable to repair array: Service intent is set. 0xB0D4 Unable to repair array: Service intent is set. 0xB0D5 Unable to unfence volume through rank: Service intent is set. 0xB0D6 Unable to assign rank to extent pool: Service intent is set. 0xB0D7 Unable to assign rank to extent pool: Service intent is set on the storage complex. 0xB0D8 Unable to unassign rank: Service intent is set. 0xB0D9 Unable to reserve rank: Service intent is set. 0xB0DA Unable to release rank: Service intent is set. 0xB0DB Unable to create rank. Contact IBM technical support for assistance. 0xB0DC Unable to create rank. Contact IBM technical support for assistance. 0xB0DD Unable to create rank. Contact IBM technical support for assistance. 0xB0DE Unable to create rank. Contact IBM technical support for assistance. 0xB0DF Unable to delete rank. Contact IBM technical support for assistance. 0xB0E0 Rank creation has failed while collecting resource information. 0xB0E1 Unable to delete rank. Contact IBM technical support for assistance. 0xB0E2 Unable to assign rank to extent pool: type mismatch 0xB0E3 Unable to assign rank to extent pool. Contact IBM technical support for assistance. 0xB0E4 Unable to unassign rank. Contact IBM technical support for assistance. 0xB0E5 Unable to reserve rank. Contact IBM technical support for assistance. 0xB0E6 Unable to release rank. Contact IBM technical support for assistance. 0xB0E7 Unable to delete rank. Contact IBM technical support for assistance. 0xB0E8 Unable to delete last rank. Logical subsystem exists. 0xB0E9 Unable to create rank. Contact IBM technical support for assistance. 0xB0EA Unable to reconfigure rank: The rank remains in the failed state. Contact IBM technical support for assistance. 0xB0EB Unable to repair array. Contact IBM technical support for assistance. 0xB0EC Unable to repair array. Contact IBM technical support for assistance.



0xB0ED Unable to repair array. Contact IBM technical support for assistance. 0xB0EE Unable to rebuild array. Contact IBM technical support for assistance. 0xB0EF Rank creation failure: server unavailable. Contact IBM technical support for assistance. 0xB0F0 Rank creation cannot complete. Contact IBM technical support for assistance. 0xB0F1 Rank creation cannot complete. Contact IBM technical support for assistance. 0xB0F2 Rank creation cannot complete. Contact IBM technical support for assistance. 0xB0F3 Rank creation did not complete. Contact IBM technical support for assistance. 0xB0F4 The creation of the rank did not complete due to a device adapter failure. 0xB0F5 Rank creation cannot complete. 0xB0F6 Unable to reconfigure rank: server offline 0xB0F7 Unable to reconfigure rank. Contact IBM technical support for assistance. 0xB0F8 Unable to reconfigure rank. Contact IBM technical support for assistance. 0xB0F9 Unable to reconfigure rank. Contact IBM technical support for assistance. 0xB0FA Rank operation failure. Contact IBM technical support for assistance. 0xB0FB Extent pool operation failure: Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB0FC Rank repair operation failure. Contact IBM technical support for assistance. 0xB0FD Rank repair operation failure. Contact IBM technical support for assistance. 0xB0FE Unable to create extent pool: maximum number of extent pools reached 0xB0FF Unable to create extent pool: incorrect rank group 0xB100 Unable to create extent pool: incorrect extent type 0xB101 Unable to create extent pool: incorrect extent limit enabled value 0xB102 Unable to create extent pool: incorrect extent limit 0xB103 Unable to create extent pool: incorrect extent threshold 0xB104 Unable to delete extent pool. Contact IBM technical support for assistance. 0xB105 Unable to delete extent pool: ranks are assigned 0xB106 Operation failure: unable to allocate memory 0xB107 Operation failure: unable to allocate memory 0xB108 Operation failure: device adapter cannot query data 0xB109 Extent pool operation failure. Contact IBM technical support for assistance. 0xB10A Unable to modify extent pool: incorrect extent limit enabled value 0xB10B Unable to modify extent pool: incorrect extent limit 0xB10C Unable to modify extent pool: incorrect extent threshold 0xB10D Unable to create or delete extent pool: local server offline 0xB10E Unable to create extent pool. Contact IBM technical support for assistance. 0xB10F Unable to delete extent pool. Contact IBM technical support for assistance. 0xB110 Extent pool operation failure 0xB111 Unable to delete extent pool. Contact IBM technical support for assistance. 0xB112 Operation failure. Contact IBM technical support for assistance. 0xB113 Unable to create or modify extent pool: incorrect user name 0xB114 Failed to initialize LPAR. Contact IBM technical support for assistance. 0xB115 Unable to create logical volume: local server offline 0xB116 Unable to delete logical volume: local server offline 0xB117 Logical volume operation failure: Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB118 Operation failure. Contact IBM technical support for assistance. 0xB119 Unable to create logical volume: logical subsystem not in correct state. Contact IBM technical support for assistance. 0xB11A Logical volume operation failure: Base volume is in incorrect state. 0xB11B Unable to modify logical volume: incorrect state. Contact IBM technical support for assistance. 0xB11C Logical volume operation failure: incorrect state. Contact IBM technical support for assistance. 0xB11D Unable to delete CKD base volume. Unable to delete or reassign aliases. 0xB11E Unable to create volume. Not enough extents are available. 0xB11F Unable to complete creation of the volume. Extents are currently being formatted and will be available at a later time. The volume configuration state is \"Configuration Error\". You must remove the volume. 0xB120 Unable to create or modify logical volume: incorrect volume number 0xB121 Unable to create or modify logical volume: incorrect number 0xB122 Unable to create logical volume: the volume number already exists. 0xB123 Unable to create logical volume: extent pool does not exist. 0xB124 Unable to create logical volume: rank group and logical subsystem group mismatch 0xB125 Unable to create logical volume: The data type of the logical volume is incompatible with the extent type of its extent pool. 0xB126 Logical volume operation failure: inconsistent starting and ending logical volume numbers 0xB127 Unable to create CKD logical volume: CKD volumes require a CKD logical subsystem. 0xB128 Unable to create logical volume: Data type is incompatible with data type of other volumes in address group. 0xB129 Unable to create logical volume: incorrect volume type 0xB12A Unable to create logical volume: FB volumes must have an extent pool. 0xB12B Unable to create logical volume: FB volumes must have a data type. 0xB12C Unable to create logical volume: FB volumes must have a requested capacity. 0xB12D Unable to create CKD alias logical volume: no base volume exists. 0xB12E Unable to delete CKD base logical volume: alias assigned 0xB12F Logical volume operation failure: not supported 0xB130 Unable to create or modify logical volume: incorrect user name 0xB131 Unable to modify logical volume: volume type and data type mismatch 0xB132 Unable to modify logical volume. Contact IBM technical support for assistance. 0xB133 Logical subsystem query failure: incorrect LSS ID



0xB134 Query failure: This action is supported only for CKD volumes. 0xB135 Query failure: logical subsystem does not exist. 0xB136 Unable to create volumes: volume type must be specified 0xB137 Unable to create volumes: incorrect volume type 0xB138 Unable to create logical volume: volume type and data type mismatch 0xB139 Logical volume operation failure: incorrect data type. Contact IBM technical support for assistance. 0xB13A Create logical subsystem failure. Contact IBM technical support for assistance. 0xB13B Alias volume creation failure: no logical subsystem exists 0xB13C Unable to create, modify, or delete logical volume: service intent is set on extent pool. 0xB13D Unable to create logical volume. Contact IBM technical support for assistance. 0xB13E Error: The logical volume has been created, but it is not assigned to a volume group. Contact IBM technical support for assistance. 0xB13F Unable to create logical volume 0xB140 Error: The logical volume has been created but it is not assigned to a logical subsystem. Contact IBM technical support for assistance. 0xB141 Error: The logical volume has been created, but it is not assigned to an address group. Contact IBM technical support for assistance. 0xB142 Unable to delete logical volume. Contact IBM technical support for assistance. 0xB143 Unable to delete logical volume. Contact IBM technical support for assistance. 0xB144 Unable to delete logical volume. Contact IBM technical support for assistance. 0xB145 Unable to delete logical volume. 0xB146 Error: The logical volume has been deleted, but the logical subsystem deletion fails. Contact IBM technical support for assistance. 0xB147 Error: The logical volume has been created, but it is not assigned to an extent pool. Contact IBM technical support for assistance. 0xB148 Unable to delete logical volume. Contact IBM technical support for assistance. 0xB149 Unable to create logical volume 0xB14A Unable to create logical volume 0xB14B Unable to create logical volume. Contact IBM technical support for assistance. 0xB14C Unable to create or modify logical volume: CKD base logical volume does not exist. 0xB14D Error: A volume of this type cannot have an alias volume group. 0xB14E Error: A volume of this type cannot have a base logical volume number. 0xB14F Unable to modify logical volume: incorrect data type 0xB150 Error: inconsistent alias and base logical volume numbers 0xB151 Incorrect alias volume group 0xB152 Unable to create or modify CKD alias volume. The base and alias volumes belong to different logical subsystems. 0xB153 Unable to create or modify CKD alias volume. The maximum number of aliases is already assigned to the base volume. 0xB154 Unable to create or modify CKD alias volume. The base volume and alias volume are not in the same volume group. 0xB155 Incorrect logical volume size. See the help text for this message for valid sizes. 0xB156 Failed to initialize LPAR. Contact IBM technical support for assistance. 0xB157 Unable to create logical subsystem: local server offline 0xB158 Unable to delete logical subsystem: local server offline 0xB159 Unable to create, delete, or modify logical subsystem resources. Resource manager unavailable on alternate server. Contact IBM technical support for assistance. 0xB15A Logical subsystem configuration error. Contact IBM technical support for assistance. 0xB15B Operation failure: logical subsystem not in correct state. Contact IBM technical support for assistance. 0xB15C Unable to create logical subsystem: device type mismatch 0xB15D Logical subsystem operation failure: logical subsystem does not exist. 0xB15E Unable to delete logical subsystem: Logical volumes are assigned. 0xB15F Unable to create or modify logical subsystem: incorrect format 0xB160 Unable to create or modify logical subsystem: incorrect format 0xB161 Unable to create logical subsystem: ID already in use. 0xB162 Unable to create logical subsystem: device type format error 0xB163 Unable to create logical subsystem: device type must be CKD 0xB164 Unable to create or modify logical subsystem: incorrect logical subsystem identifier length 0xB165 Unable to create or modify logical subsystem: incorrect logical subsystem identifier format 0xB166 Unable to modify logical subsystem: identifier only for CKD 0xB167 Unable to create or modify logical subsystem 0xB168 Unable to modify logical subsystem: not a CKD volume 0xB169 Unable to modify logical subsystem: cannot set session timeout 0xB16A Unable to modify logical subsystem: cannot set session timeout 0xB16B Unable to modify logical subsystem: incorrect critical mode enabled 0xB16C Unable to modify logical subsystem: incorrect extended long busy enabled parameter 0xB16D Unable to modify logical subsystem: incorrect extended long busy time value 0xB16E Unable to create logical subsystem. Contact IBM technical support for assistance. 0xB16F Unable to delete logical subsystem. Contact IBM technical support for assistance. 0xB170 Unable to modify logical subsystem. Contact IBM technical support for assistance. 0xB171 Logical subsystem query failure. Contact IBM technical support for assistance. 0xB172 Unable to reset Copy Services settings on logical subsystems. Contact IBM technical support for assistance. 0xB173 Unable to reset Copy Services settings on logical subsystem. Contact IBM technical support for assistance. 0xB174 Unable to create or modify logical subsystem: identifier must be nonzero 0xB175 Unable to create or modify logical subsystem: identifier already in use 0xB176 Unable to delete logical subsystem. Contact IBM technical support for assistance. 0xB177 LPAR startup error. Contact IBM technical support for assistance.



0xB178 Failed to initialize LPAR. Contact IBM technical support for assistance. 0xB179 Failed to initialize LPAR. Contact IBM technical support for assistance. 0xB17A Unable to end service: lock still held by other management console 0xB17B Unable to start service: device adapter pair is configuring. 0xB17C Unable to start or end service. Contact IBM technical support for assistance. 0xB17D Unable to start or end service: incorrect parameters. Contact IBM technical support for assistance. 0xB17E Unable to start or end service: incorrect management console ID. Contact IBM technical support for assistance. 0xB17F Service intent is not currently set. Reset ignored. Contact IBM technical support for assistance. 0xB180 Unable to end service: Management console is not authorized. Contact IBM technical support for assistance. 0xB181 Cannot exceed maximum volume group count 0xB182 Unable to create or delete volume group: local server offline 0xB183 Unable to retrieve or assign volumes assigned to volume group: local server offline 0xB184 Unable to retrieve or assign volumes assigned to volume group: local server offline 0xB185 Volume group operation failure: local server offline 0xB186 Volume group operation failure: Host agent Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB187 Unable to create, modify, or delete volume group: version update. Contact IBM technical support for assistance. 0xB188 Volume group query failure. Contact IBM technical support for assistance. 0xB189 Volume group query failure. Contact IBM technical support for assistance. 0xB18A Unable to modify volume group. Contact IBM technical support for assistance. 0xB18B Unable to retrieve volume group information. Contact IBM technical support for assistance. 0xB18C Unable to retrieve volumes assigned to the volume group. Contact IBM technical support for assistance. 0xB18D Unable to retrieve volumes assigned to the volume group: no ranks exist 0xB18E Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB18F Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB190 Unable to assign volume to volume group 0xB191 Unable to retrieve volumes assigned to volume group. Contact IBM technical support for assistance. 0xB192 Unable to assign volume to volume group 0xB193 Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB194 Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB195 Unable to assign volume to volume group 0xB196 Unable to query rank. Contact IBM technical support for assistance. 0xB197 Unable to modify volume group. Contact IBM technical support for assistance. 0xB198 Unable to create volume group. Contact IBM technical support for assistance. 0xB199 Unable to delete volume group. Contact IBM technical support for assistance. 0xB19A Unable to query rank. Contact IBM technical support for assistance. 0xB19B Unable to open a session. Contact IBM technical support for assistance. 0xB19C Unable to query rank. Contact IBM technical support for assistance. 0xB19D Unable to query logical volume. Contact IBM technical support for assistance. 0xB19E Unable to open a session to query a logical volume. Contact IBM technical support for assistance. 0xB19F Operation failure. No ranks exist. Contact IBM technical support for assistance. 0xB1A0 Unable to delete volume group. Contact IBM technical support for assistance. 0xB1A1 Volume group operation failure. Contact IBM technical support for assistance. 0xB1A2 Unable to create logical volume. Contact IBM technical support for assistance. 0xB1A3 Unable to delete logical volume. Contact IBM technical support for assistance. 0xB1A4 Unable to query volume group. Contact IBM technical support for assistance. 0xB1A5 Volume group operation failure. Contact IBM technical support for assistance. 0xB1A6 Unable to retrieve volumes assigned to volume group. Contact IBM technical support for assistance. 0xB1A7 Unable to assign volumes to volume group. Contact IBM technical support for assistance. 0xB1A8 Unable to retrieve volumes assigned to volume group. Contact IBM technical support for assistance. 0xB1A9 Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB1AA Unable to create volume group. Contact IBM technical support for assistance. 0xB1AB Unable to delete volume group. Contact IBM technical support for assistance. 0xB1AC Unable to create volume group: incorrect volume group type 0xB1AD Unable to delete volume group: The volume group is still assigned to a SCSI host port. 0xB1AE Unable to assign volume to volume group: data type mismatch 0xB1AF Unable to delete volume group 0xB1B0 Unable to create volume group: incorrect user name 0xB1B1 Unable to assign volume to volume group. Contact IBM technical support for assistance. 0xB1B2 Unable to query volume groups: incorrect volume number 0xB1B3 Unable to retrieve volumes assigned to volume group. Contact IBM technical support for assistance. 0xB1B4 Unable to assign volumes to volume group. Contact IBM technical support for assistance. 0xB1B5 Unable to assign volumes to volume group 0xB1B6 Unable to retrieve volumes assigned to volume group. Contact IBM technical support for assistance. 0xB1B7 Unable to modify volume group 0xB1B8 Operation failure. Contact IBM technical support for assistance. 0xB1B9 Unable to add logical volume to volume group: incorrect parameter 0xB1BA Unable to remove logical volume from volume group: incorrect parameter. Contact IBM technical support for assistance. 0xB1BB Unable to query volume groups: incorrect parameter. Contact IBM technical support for assistance. 0xB1BC Unable to modify volume group: incorrect user name 0xB1BD Volume group operation failure: incorrect parameter. Contact IBM technical support for assistance. 0xB1BE Volume group operation failure: incorrect parameter. Contact IBM technical support for assistance. 0xB1BF Volume group operation failure. Contact IBM technical support for assistance. 0xB1C0 Volume group operation failure: volume does not exist. Contact IBM technical support for assistance.



0xB1C1 Volume group operation failure: volume does not exist. Contact IBM technical support for assistance. 0xB1C2 Unable to query volume groups: volume does not exist. Contact IBM technical support for assistance. 0xB1C3 Unable to query volume groups. Contact IBM technical support for assistance. 0xB1C4 Unable to delete volume group. Contact IBM technical support for assistance. 0xB1C5 Unable to assign volumes to volume group. Contact IBM technical support for assistance. 0xB1C6 Unable to assign volumes to volume group. Contact IBM technical support for assistance. 0xB1C7 Operation failure. Contact IBM technical support for assistance. 0xB1C8 Delete volume group operation stopped. Previous attempt failed. Contact IBM technical support for assistance. 0xB1C9 Volume group operation failure: incorrect volume configuration. Contact IBM technical support for assistance. 0xB1CA Volume group operation failure: incorrect volume configuration. Contact IBM technical support for assistance. 0xB1CB Unable to query volume groups: incorrect volume configuration. Contact IBM technical support for assistance. 0xB1CC Unable to create a new SCSI host port: maximum count reached 0xB1CD Unable to create, modify, or delete SCSI host port: local server offline 0xB1CE SCSI host port operation failure: Host agent Resource Manager not available on alternate server. Contact IBM technical support for assistance. 0xB1CF Unable to query rank. Contact IBM technical support for assistance. 0xB1D0 Unable to modify volume group. Contact IBM technical support for assistance. 0xB1D1 Unable to create SCSI host port. Contact IBM technical support for assistance. 0xB1D2 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1D3 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1D4 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1D5 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1D6 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1D7 Unable to query rank. Contact IBM technical support for assistance. 0xB1D8 Unable to open a session. Contact IBM technical support for assistance. 0xB1D9 Unable to query rank. Contact IBM technical support for assistance. 0xB1DA Operation failure. Contact IBM technical support for assistance. 0xB1DB Unable to delete SCSI host port. Contact IBM technical support for assistance. 0xB1DC Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB1DD Unable to create SCSI host port. Contact IBM technical support for assistance. 0xB1DE Unable to delete SCSI host port. Contact IBM technical support for assistance. 0xB1DF SCSI host port operation failure. Contact IBM technical support for assistance. 0xB1E0 Unable to create SCSI host port: incorrect volume group identifier 0xB1E1 Unable to modify SCSI host port: incorrect host type 0xB1E2 Unable to create SCSI host port: incorrect WWPN 0xB1E3 Unable to create SCSI host port: incorrect override default priority 0xB1E4 Unable to modify SCSI host port: incorrect volume group ID 0xB1E5 Unable to modify SCSI host port: incorrect port topology 0xB1E6 Unable to modify SCSI host port: incorrect address discovery method 0xB1E7 Unable to modify SCSI host port: incorrect logical block size 0xB1E8 Unable to modify SCSI host port: nonexistent volume group 0xB1E9 Unable to modify SCSI host port: incorrect volume group type 0xB1EA Unable to create SCSI host port: incorrect WWPN 0xB1EB Unable to create SCSI host port: incorrect WWPN 0xB1EC Unable to modify SCSI host port: incorrect port mask 0xB1ED Unable to modify SCSI host port: incorrect value 0xB1EE Unable to modify SCSI host port: logical block size and volume group type mismatch 0xB1EF Unable to modify SCSI host port: incorrect port profile 0xB1F0 Unable to create SCSI host port: incorrect profile 0xB1F1 Unable to modify SCSI host port: logical block size and volume group type mismatch 0xB1F2 Unable to modify SCSI host port: incorrect override default priority value 0xB1F3 Unable to modify SCSI host port: address discovery method and volume group type mismatch 0xB1F4 Unable to modify SCSI host port: address discovery method and volume group type mismatch 0xB1F5 Unable to create SCSI host port: non-unique WWPN 0xB1F6 Operation failure. Contact IBM technical support for assistance. 0xB1F7 Unable to create SCSI host port: incorrect port profile 0xB1F8 Unable to modify SCSI host port: incorrect port profile 0xB1F9 Unable to modify SCSI host port: incorrect user host name 0xB1FA Unable to modify SCSI host port: incorrect user host description 0xB1FB Unable to create SCSI host port: incorrect user host name 0xB1FC Unable to create SCSI host port: incorrect user host description 0xB1FD Unable to create SCSI host port. A colon : cannot be used when specifying a SCSI host port. 0xB1FE Unable to modify SCSI host port. A colon : cannot be used when specifying a SCSI host port. 0xB1FF Unable to delete SCSI host port. Contact IBM technical support for assistance. 0xB200 Unable to delete SCSI host port. Contact IBM technical support for assistance. 0xB201 Unable to modify SCSI host port. Contact IBM technical support for assistance. 0xB202 SCSI host port operation failure. Contact IBM technical support for assistance. 0xB203 Delete SCSI host port operation stopped. Previous attempt failed. Contact IBM technical support for assistance. 0xB204 Operation failure. Contact IBM technical support for assistance. 0xB205 Operation failure. Contact IBM technical support for assistance. 0xB206 Rank creation denied. This rank would exceed the installed LMC feature key enablement. Delete all references to this rank. 0xB207 Internal logical configuration error: Collect a PE package. 0xB208 Unable to create array. At least one and no more than two array sites must be specified. 0xB209 You must enter contact information before you can invoke the Call Home function.



0xB20A Unable to create array. All array sites must be in the same loop. 0xB20B Unable to create logical subsystem: microcode-level error. Contact IBM technical support for assistance. 0xB20C Unable to create rank: failed disk drives detected 0xB20D Unable to create rank: licensed capacity has been exceeded. 0xB20E Unable to create logical subsystem: incorrect address group 0xB20F Unable to delete last rank: A volume group is still defined. 0xB210 Unable to create rank: maximum number of ranks already created 0xB211 Unable to create array. A RAID5 array can have only one spare. 0xB212 Unable to delete volume: The volume does not exist. 0xB213 Internal logical configuration error: Another configuration is in progress. 0xB214 Unable to create rank. Disks are being formatted. 0xB215 A recovery is in progress. Logical configuration commands are blocked. 0xB216 Incorrect configuration: The base and alias/map volumes must be in the same volume group. 0xB217 Incorrect configuration: A volume group cannot contain unconfigured logical volumes. 0xB218 Incorrect configuration: volume group and volume type mismatch 0xB219 Incorrect configuration: 512-byte fixed-block volumes must share data. 0xB21A Incorrect configuration: volume group and volume type mismatch 0xB21B Incorrect configuration: volume group and volume type mismatch 0xB21C Incorrect configuration: volume group and volume type mismatch 0xB21D Incorrect configuration: CKD base logical volumes must share data. 0xB21E Incorrect configuration: volume group and volume type mismatch 0xB21F Unable to create rank. At least one DDM in the array that you specified requires a service procedure. 0xB220 Unable to create rank. The array site does not contain a full complement of DDMs. 0xB221 Unable to delete last rank: A SCSI host port is attached to the rank. 0xB222 Unable to create volume. 0xB223 Unable to create volume. 0xB224 Unable to repair rank. Disk drive modules not found. 0xB225 Unable to bring rank online. Device adapter error. Contact IBM technical support for assistance. 0xB226 Unable to repair rank. One or more disk drive modules is not reporting normal status. 0xB227 Unable to repair rank. Contact IBM technical support for assistance. 0xB228 SCSI host port creation failed. Ensure that both processor cards are operational. 0xB229 Initialization process is not yet complete. 0xB22A Unable to update the number of configured devices. Contact IBM technical support for assistance. 0xB22B Unable to update the number of configured devices. Contact IBM technical support for assistance. 0xB22C Incorrect SCSI host port profile ID. 0xB22D The host worldwide port name (WWPN) that you are submitting is already assigned to one of the storage unit I/O ports. 0xB22E Host port does not exist. 0xB22F Internal error. Contact IBM technical support for assistance. 0xB230 Host connection cannot be added. 0xB231 Host connection cannot be added. Request exceeds the maximum number of allowed hosts. 0xB232 Host connection modification failed due to incorrect SCSI host port configuration information. 0xB233 Host connection deletion failed. 0xB234 Host connection deletion failed due to incorrect SCSI host port configuration information. 0xB235 Task failed. Volume group not found. 0xB236 Task rejected during recovery procedure. 0xB237 Task rejected during initialization. 0xB238 Task failed due to incorrect input. 0xB239 Internal error. Contact IBM technical support for assistance. 0xB23A Insufficient task input. 0xB23B Internal error. Insufficient internal resources. 0xB23C Task rejected due to incorrect input. 0xB23D Internal error. 0xB23E Internal error. 0xB23F Volume group failed to create. Attempted use of a reserved volume group type. 0xB240 Volume group failed to create. Attempted use of an unsupported volume group type. 0xB241 Internal error. 0xB242 Add volume list task failed. Incorrect volume list range. 0xB243 Unsupported task. 0xB244 Internal error. Insufficient internal resources. 0xB245 Internal error. Insufficient internal resources. 0xB246 Internal error. 0xB247 Internal error. Contact IBM technical support for assistance. 0xB248 Operation failure: functional code timeout. Contact IBM technical support for assistance. 0xB249 Operation failure: CKD base required 0xB24A Hardware error: An unusual hardware condition originates in the channel, drive, or storage unit. Contact IBM technical support for assistance. 0xB24B Copy Services error: Intervention is required. 0xB24C Performance statistics cannot be accumulated: LSS not configured 0xB24D Performance statistics cannot be accumulated: resource not configured 0xB24E Operation failure: incorrect parameters 0xB24F Operation failure: Copy Services server failure. Contact IBM technical support for assistance. 0xB250 Operation failure: resource not found. Contact IBM technical support for assistance. 0xB251 Operation failure: internal error. Contact IBM technical support for assistance. 0xB252 Internal Copy Services Error.



0xB253 Operation failure: node agent 0 fails. Contact IBM technical support for assistance. 0xB254 Operation failure: node agent 1 fails. Contact IBM technical support for assistance. 0xB255 Operation failure: name is not unique 0xB256 Operation failure: database creation error. Contact IBM technical support for assistance. 0xB257 Operation failure: addition. Contact IBM technical support for assistance. 0xB258 Internal database overwrite failure: The database exists and overwrite is off. Contact IBM technical support for assistance. 0xB259 Storage unit unavailable 0xB25A Operation failure: unknown storage unit 0xB25B Operation failure: changes are pending 0xB25C XML parse error. Contact IBM technical support for assistance. 0xB25D Operation failure: internal database not open. Contact IBM technical support for assistance. 0xB25E Operation failure: configuration already exists 0xB25F Unable to add logical volume to the logical subsystem (LSS). 0xB260 Operation failure: SCSI host port already exists. 0xB261 Operation failure: incorrect file type. Contact IBM technical support for assistance. 0xB262 Operation failure: user not found in the repository of the peer management console 0xB263 Operation failure: group not found in repository of the peer management console 0xB264 Operation failure: duplicate user name in the repository of the peer management console 0xB265 Operation failure: incorrect password format 0xB266 Operation failure: password same as previous password 0xB267 Operation failure: communication failure between peer management consoles. 0xB268 Operation failure: The repository on the peer management console is not accessible for an unknown reason. Contact IBM technical support for assistance. 0xB269 Operation failure: maximum number of accounts reached on the repository of the peer management console 0xB26A Operation failure: settings entry not found in the repository of the peer management console 0xB26B Operation failure: internal error in the repository of the peer management console. Contact IBM technical support for assistance. 0xB26C Operation failure: request timed out 0xB26D Operation failure: incorrect user account name 0xB26E Operation failure: peer management console is busy 0xB26F Operation failure: user not found in the repository of the local management console 0xB270 Operation failure: group not found in the repository of the local management console. Contact IBM technical support for assistance. 0xB271 Operation failure: duplicate user name in the repository of the local management console 0xB272 Operation failure: the repository of the local management console is not accessible. Contact IBM technical support for assistance. 0xB273 Operation failure: maximum number of accounts reached on the repository of the local management console 0xB274 Operation failure: settings entry not found in the repository of the local management console. Contact IBM technical support for assistance. 0xB275 Operation failure: internal error in the repository of the local management console. Contact IBM technical support for assistance. 0xB276 Operation failure: local busy 0xB277 Operation failure. Contact IBM technical support for assistance. 0xB278 Operation failure. Contact IBM technical support for assistance. 0xB279 Operation failure: retrieving rank. Contact IBM technical support for assistance. 0xB27A A call home service connection could not be established. Check the call home configuration on the management console server. 0xB27B A call home service connection could not be established. Check the call home configuration on the management console server. 0xB27C A call home service connection could not be established because of a modem error. Check your modem and your call home configuration on the management console server. 0xB27D Internal error. Contact IBM technical support for assistance. 0xB27E The task has failed because the required virtual private network configuration information is missing or incorrect. 0xB27F The task has failed because a virtual private network tunnel already exists. 0xB280 The task has failed because another establish virtual private network tunnel task exists. 0xB281 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB282 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB283 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB284 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB285 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB286 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB287 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB288 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB289 A call home service connection could not be established. Check the call home configuration on the management console server. 0xB28A A call home service connection could not be established. Check the call home configuration on the management



console server. 0xB28B A call home service connection could not be established. Check the call home configuration on the management console server. 0xB28C A call home service connection could not be established. Check the call home configuration on the management console server. 0xB28D A call home service connection could not be established. Check the call home configuration on the management console server. 0xB28E Unable to resume enclosure operation: not allowed. Contact IBM technical support for assistance. 0xB28F The resume operation is not allowed for this integrated RAID controller. Contact IBM technical support for assistance. 0xB290 Unable to resume operation: not allowed. Contact IBM technical support for assistance. 0xB291 Unable to resume DDM operation: not allowed. Contact IBM technical support for assistance. 0xB292 Unable to resume operation: not allowed. Contact IBM technical support for assistance. 0xB293 Unable to resume rear display panel operation: not allowed. Contact IBM technical support for assistance. 0xB294 Unable to resume front display panel operation: not allowed. Contact IBM technical support for assistance. 0xB295 Unable to resume battery backup unit: not allowed. Contact IBM technical support for assistance. 0xB296 Unable to install or resume enclosure operation. Contact IBM technical support for assistance. 0xB297 The install or resume operation for the processor card fails. Contact IBM technical support for assistance. 0xB298 Install or resume operation failure. Contact IBM technical support for assistance. 0xB299 Battery activation failure. Contact IBM technical support for assistance. 0xB29A Unable to install or resume operation. Contact IBM technical support for assistance. 0xB29B Unable to install or resume rear display panel operation. Contact IBM technical support for assistance. 0xB29C Unable to install or resume front display panel operation. Contact IBM technical support for assistance. 0xB29D Battery activation failure. Contact IBM technical support for assistance. 0xB29E Unable to prepare enclosure for service: not allowed in current state. Contact IBM technical support for assistance. 0xB29F Unable to prepare integrated RAID controller for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A0 Unable to prepare for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A1 Unable to prepare DDM for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A2 Unable to prepare for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A3 Unable to prepare rear display panel for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A4 Unable to prepare front display panel for service: not allowed in current state. Contact IBM technical support for assistance. 0xB2A5 Unable to prepare battery for service: incorrect state. Contact IBM technical support for assistance. 0xB2A6 Unable to prepare enclosure for service. Contact IBM technical support for assistance. 0xB2A7 Unable to prepare integrated RAID controller for service. Contact IBM technical support for assistance. 0xB2A8 Unable to prepare fibre-channel interface card for service. Contact IBM technical support for assistance. 0xB2A9 Unable to prepare DDM for service. Contact IBM technical support for assistance. 0xB2AA Unable to prepare for service. Contact IBM technical support for assistance. 0xB2AB Unable to prepare rear display panel for service. Contact IBM technical support for assistance. 0xB2AC Unable to prepare front display panel for service. Contact IBM technical support for assistance. 0xB2AD Unable to prepare battery for service. Contact IBM technical support for assistance. 0xB2AE The Create test problem record task has failed because of insufficient resources. Wait a few minutes and then resubmit the task. 0xB2AF The close problem log entry task has failed because the problem log entry that you have selected is already closed or does not exist. 0xB2B0 Feature install activation failure: Unable to decrypt license key. 0xB2B1 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B2 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B3 Feature key validation failure: key type does not match storage type 0xB2B4 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B5 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B6 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B7 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B8 Feature install activation failure. Contact IBM technical support for assistance. 0xB2B9 Feature install activation failure. Contact IBM technical support for assistance. 0xB2BA Feature install activation failure. Contact IBM technical support for assistance. 0xB2BB Unable to modify network port: The specified IP address is not valid. Contact IBM technical support for assistance. 0xB2BC Unable to modify network port: The specified network is not valid. Contact IBM technical support for assistance. 0xB2BD Unable to modify network port. The IP addresses of the two clusters cannot be identical. 0xB2BE Unable to modify network port. Retry. 0xB2BF Unable to prepare for service: The DDM is a component of an array that is rebuilding. 0xB2C0 Unable to prepare for service: The DDM is part of an exposed array. 0xB2C1 Unable to prepare for service: The DDM is part of a degraded array. 0xB2C2 Unable to prepare for service: The DDM is a component of an offline array. 0xB2C3 Unable to prepare for service: The array containing this DDM cannot be determined. 0xB2C4 Unable to prepare for service: No spare DDM can be found in the array. 0xB2C5 Operation failure: unable to connect 0xB2C6 Operation failure: incorrect file or directory 0xB2C7 Operation failure: unable to extract Jar file for package bundle 0xB2C8 Operation failure: incorrect code bundle 0xB2C9 Operation failure: possible incorrect code bundle 0xB2CA Unable to activate code load: incompatible hardware and code versions 0xB2CB Unable to activate code load: incompatible software version in package bundle 0xB2CC Operation failure: unable to copy code



0xB2CD Operation failure: timeout 0xB2CE Operation failure: unknown operating system 0xB2CF Operation failure: thread interrupted. Contact IBM technical support for assistance. 0xB2D0 Operation failure: unable to create PE package. Contact IBM technical support for assistance. 0xB2D1 Operation failure: unable to mark statesave. Contact IBM technical support for assistance. 0xB2D2 Operation failure: unable to copy PE package. Contact IBM technical support for assistance. 0xB2D3 Operation failure: unable to copy statesave. Contact IBM technical support for assistance. 0xB2D4 Operation failure: an external utility does not run 0xB2D5 Operation failure: unable to retrieve password. Contact IBM technical support for assistance. 0xB2D6 Operation failure: unable to retrieve list of storage servers. Contact IBM technical support for assistance. 0xB2D7 Operation failure: unable to retrieve software version. Contact IBM technical support for assistance. 0xB2D8 Operation failure: unable to retrieve list of network ports. Contact IBM technical support for assistance. 0xB2D9 Operation failure: file or directory not found 0xB2DA Operation failure: unable to copy log files. Contact IBM technical support for assistance. 0xB2DB Operation failure: unable to retrieve list of hardware resources. Contact IBM technical support for assistance. 0xB2DC Operation failure: results list is empty. Contact IBM technical support for assistance. 0xB2DD Operation failure: unable to open file. Contact IBM technical support for assistance. 0xB2DE Operation failure: unable to retrieve trace service. Contact IBM technical support for assistance. 0xB2DF Operation failure: unable to copy SA logs to the PE package 0xB2E0 Operation failure: unable to compress all files to zip file. Contact IBM technical support for assistance. 0xB2E1 Operation failure: FTP failure 0xB2E2 Operation failure: environment variable not found 0xB2E3 Operation failure: unable to load code bundle 0xB2E4 Operation failure: console server exception returned to SA. Contact IBM technical support for assistance. 0xB2E5 Operation failure: file list not found. Contact IBM technical support for assistance. 0xB2E6 Operation failure: incorrect FTP directory 0xB2E7 Operation failure: incorrect send2IBM directory 0xB2E8 Operation failure: unable to close file. Contact IBM technical support for assistance. 0xB2E9 Operation failure: FTP connection refused 0xB2EA Unable to access node 0 of the storage unit. This problem might be temporary. 0xB2EB Unable to access node 1 of the storage unit. This problem might be temporary. 0xB2EC There are no statesave files that are ready to copy from the storage unit to the management console. 0xB2ED Unable to copy new code bundle. Another copy is in progress. 0xB2EE Unable to copy new code bundle. A code load is in progress. 0xB2EF LIC feature build key failed. Contact IBM technical support for assistance. 0xB2F0 Incorrect storage image sequence number in the LIC feature key. 0xB2F1 Creation of LIC feature file failed. Contact IBM technical support for assistance. 0xB2F2 Error decrypting LIC feature string or file. Contact IBM technical support for assistance. 0xB2F3 Error encrypting LIC feature string or file. Contact IBM technical support for assistance. 0xB2F4 LIC feature string validation failed. Contact IBM technical support for assistance. 0xB2F5 Incorrect LIC feature type. 0xB2F6 Error opening LIC feature file. Contact IBM technical support for assistance. 0xB2F7 Error writing to the LIC feature file. Contact IBM technical support for assistance. 0xB2F8 LIC feature file validation failed. Contact IBM technical support for assistance. 0xB2F9 Error activating LIC feature file. Contact IBM technical support for assistance. 0xB2FA Error displaying LIC feature information. Contact IBM technical support for assistance. 0xB2FB Error querying LIC feature information. Contact IBM technical support for assistance. 0xB2FC Error determining product information to be used for LIC features. Contact IBM technical support for assistance. 0xB2FD LIC feature storage type is not correct. 0xB2FE Incorrect LIC feature key length. 0xB2FF The LIC feature keys cannot be installed due to default LIC features. Contact IBM technical support for assistance. 0xB300 LIC feature cannot be installed due to the maximum number of logical subsystems for CKD storage. Contact IBM technical support for assistance. 0xB301 The volume group modification or creation task failed. You have specified a volume that does not exist. 0xB302 LIC feature capacity error. Incorrect capacity value for the specified LIC feature type. 0xB303 The modify host adapter port task failed because the host adapter port is not defined. 0xB304 The modify host adapter port task failed because the host adapter port cannot be modified unless both processor cards show normal status. 0xB305 The modify host adapter port task failed because the port failed to change to the offline or online state. 0xB306 The modify host adapter port task failed because the host adapter port type modification failed. 0xB307 Unable to create, delete, or assign a rank while one of the processor cards is inactive. 0xB308 Rank does not exist. 0xB309 The rank is not in an inaccessible state. 0xB30A Internal error. Contact IBM technical support for assistance. 0xB30B Internal error. Contact IBM technical support for assistance. 0xB30C Internal error. Contact IBM technical support for assistance. 0xB30D The extent pool cannot be deleted. Logical volumes are still assigned to the extent pool. 0xB30E Unable to create the SCSI host port. Another SCSI host port exists with the same worldwide port name and a conflicting port ID. 0xB30F Unable to modify the SCSI host port. Another SCSI host port exists with the same worldwide port name and a conflicting port ID. 0xB310 Internal error. Contact IBM technical support for assistance. 0xB311 Internal error. Contact IBM technical support for assistance. 0xB312 Internal error. Contact IBM technical support for assistance. 0xB313 The storage unit is busy. Wait for a few seconds, and resubmit the task.



0xB314 The storage unit is busy. Wait for a few minutes, and resubmit the task. 0xB315 Internal error. Contact IBM technical support for assistance. 0xB316 Internal error. Contact IBM technical support for assistance. 0xB317 Internal error. Contact IBM technical support for assistance. 0xB318 You are attempting to create an array with two array sites, and the disk class of the array sites is not the same. 0xB319 The synchronize security repository task has failed because it exceeds the maximum number of user accounts. 0xB31A The create array task has failed because at least one array site state is not unassigned. 0xB31B The create array task has failed because the characteristics of the array sites do not match. 0xB31C Unable to submit the logical configuration task that you have requested because a discovery task is in progress. 0xB31D You are attempting to enter a notification e-mail address and the task has failed because the e-mail address is not valid. 0xB31E You are attempting to enter a contact information e-mail address and the task has failed because the contact information e-mail address is not valid. 0xB31F The licensed internal code (LIC) activation key task has failed because at least one of the servers of the storage image is not currently operational. 0xB320 You must use the standard ASCII 7-bit character set to enter data. 0xB321 Remote Mirror and Copy activation codes are not supported for this model. 0xB322 Metro Mirror activation codes are not supported for this model. 0xB323 Global Mirror activation codes are not supported for this model. 0xB324 The Apply Activation code task has failed because the capacity that is configured on the storage image exceeds the capacity of the storage scope that is specified in the activation key. 0xB325 The remote power control task has failed because an internal error has occurred. Contact IBM technical support for assistance. 0xB326 The remote manual power control request has failed because the remote power control mode is not set to \"Remote manual\". 0xB327 The remote manual power control request has failed because the local/remote switch on the storage unit is set to Local. 0xB328 The remote manual power control request has failed because either the storage unit power state or the power control mode is transitioning. 0xB329 The request to change the remote power control mode has failed because an internal error has occurred. Contact IBM technical support for assistance. 0xB32A The request to change the remote power control mode has failed because requested mode is not valid or is not supported. 0xB32B The request to change the remote power control mode to \"Remote zSeries\" has failed because the zSeries power feature is not installed. 0xB32C The change power control mode task that you have requested has failed because either the storage unit power state or the power control mode is transitioning. 0xB32D The apply activation code task has failed because the version of microcode on at least one of the partitions is not supported, or the firmware on at least one of the host adapters on the storage unit is not supported. 0xB32E The task has failed because a Resource Manager error has occurred. 0xB32F An internal parameter or value that is used by the task is not correct. 0xB330 The change machine type and machine serial number task has failed. 0xB331 The query volume serial number task has failed. 0xB332 The query rank extents task has failed. 0xB333 The create volume task has failed because the segment pool has no assigned ranks. 0xB334 The reset service intent task has not been initiated because another reset service intent task is accessing all device adapter pairs. 0xB335 The change machine type and machine serial number task has failed. 0xB336 Operation failure: The storage image is not available. 0xB337 Operation failure: The storage image is not available. 0xB338 Operation failure: A LIC parameter is not correct. 0xB339 The expand logical volume task was not initiated because the volume is in a Copy Services relationship. 0xB33A The expand logical volume task was not initiated because there are not enough extents. 0xB33B The expand logical volume task was not initiated because the logical volume capacity that you have requested is less than the current logical volume capacity. 0xB33C The expand logical volume task was not initiated because the logical volume capacity that you have requested is not within the valid capacity range for the volume data type. 0xB33D The expand logical volume task was not initiated. Either the logical volume is not a base volume, or the logical volume data type is neither fixed block nor CKD model 3390. 0xB33E The expand logical volume task was not initiated because there is not enough storage unit resource available. Resubmit the task when the storage unit is less busy. 0xB33F The expand logical volume task was not initiated because at least one device adapter prerequisite condition does not exist. 0xB340 The expand logical volume task was not initiated because at least one logical partition is not fully operational. 0xB341 The expand logical volume task was not initiated. The volume state has been set to NORMAL. 0xB342 The expand logical volume task was not initiated because the configuration state of the logical volume that you have specified is RECONFIGURING ERROR. 0xB343 The expand logical volume task has failed. The task has been resubmitted, and the resubmitted task has also failed. 0xB344 The expand logical volume task has failed. The storage unit cannot return the logical volume capacity definition to the original capacity. 0xB345 The expand logical volume task was not initiated because either the logical volume configuration state or the logical volume data state is not NORMAL. 0xB346 The expand logical volume task has failed. The storage unit cannot return the logical volume capacity definition to the original capacity. 0xB347 The expand logical volume task has failed to initiate the volume flash initialization subtask. 0xB348 The expand logical volume task has failed and the logical volume capacity has reverted back to the original capacity. 0xB349 You cannot change the current logical volume data type to the data type that you have specified because the current



logical volume capacity is not supported by the data type that you have requested. 0xB34A The create rank task has failed because information about ranks is missing or is unavailable. 0xB34B The create rank task has failed because required information about ranks cannot be obtained. 0xB34C The delete rank task has failed because information about the rank is temporarily unavailable. 0xB34D The delete rank task has failed while changing the configuration state. 0xB34E The expand logical volume task has failed because the configuration state is RECONFIGURING and the logical volume capacity that you have requested is not identical to the previously requested capacity. 0xB34F The requested capacity of the logical volume that you have specified is not supported by the host server operating system. 0xB350 You are attempting to configure extents but the IBM Database protection Licensed Internal Code feature is not activated. 0xB351 The task has failed while the database extent configuration was being saved to the storage image. 0xB352 The task has failed because either the storage type of the volume that you have specified is not Fixed Block (FB) or the block size is not 512 bytes. 0xB353 The task has failed because a logical volume that you have specified is not defined to the storage image or the volume state is not Normal. 0xB354 The task has failed because at least one of the volumes in the configuration that you have specified has a volume state of Offline. 0xB355 The extent specification format in the task that you have requested is not supported. 0xB356 The extent specification length in the task request is not supported. 0xB357 The task has failed because the number of extent specifications that you have requested is not supported. 0xB358 The task has failed because the length of the extent specification list is not consistent with the number of extent specifications that you have requested. 0xB359 The task has failed because a nonhexadecimal character has been used in an extent specification. 0xB35A The task has failed because the starting block addresses in the extent specifications that you have requested are not in increasing order. 0xB35B The task has failed because an extent size that you have requested is less than 128 logical blocks. 0xB35C The task has failed because at least two extent specifications overlap. 0xB35D The task has failed because at least one extent specification that you have requested is outside the range of addresses that are contained on the logical volume that you have specified. 0xB35E The task has failed because proprietary application information that is associated with an extent specification is not correct. 0xB35F The task has failed because a reserved or unsupported field that is associated with an extent specification is not set to zero. 0xB360 The task has failed because an internal protocol error has occurred. 0xB361 The task has failed because an internal protocol specifies that write operations are not validated. 0xB362 The task has failed because an internal protocol specifies that read operations are validated. 0xB363 The create extent pool task has failed because the value for an internal variable is not valid. 0xB364 The modify extent pool task has failed because the value for an internal variable is not valid. 0xB365 The create extent pool task has failed because the value that you have entered for threshold percent is not an integer from 0 through 100, inclusive. 0xB366 The modify extent pool task has failed because the value that you have entered for threshold percent is not an integer from 0 through 100, inclusive. 0xB367 The create logical volume task has failed because the storage allocation method is not supported. 0xB368 The create space-efficient logical volume task has failed. Either there is no FB space-efficient storage configured for the FB extent pool, or the state of the FB space-efficient storage for the specified extent pool is not Normal. 0xB369 The create space-efficient logical volume task has failed. Either there is no FB space-efficient storage configured for the FB extent pool, or the state of the FB space-efficient storage for the specified extent pool is not Normal. 0xB36A The create space-efficient logical volume task has failed. Either there is no CKD space-efficient storage configured for the CKD extent pool, or the state of the CKD space-efficient storage for the specified extent pool is not Normal. 0xB36B The create space-efficient logical volume task has failed. Either there is no CKD space-efficient storage configured for the CKD extent pool, or the state of the CKD space-efficient storage for the specified extent pool is not Normal. 0xB36C The logical volume task has not been initiated because a parameter or value that you have specified is not supported. 0xB36D The operation that you have requested is not supported. 0xB36E The create space-efficient storage task has failed because the logical partition server state is not online. 0xB36F The delete space-efficient storage task has failed because the logical partition server state is not online. 0xB370 The task to create, delete or modify space-efficient storage cannot be initiated because the storage agent resource manager is not available on a logical partition. 0xB371 The create space-efficient storage task cannot be initiated because the correct licensed internal code feature key is not installed. 0xB372 The create space-efficient storage task cannot be initiated because a required device adapter precondition does not exist. 0xB373 The create space-efficient storage task has failed because of a device adapter error. 0xB374 The create space-efficient storage task has failed because of a device adapter query error. 0xB375 The delete space-efficient storage task has failed because of a device adapter error. 0xB376 The delete space-efficient storage task cannot be initiated because a required device adapter precondition does not exist. 0xB377 The delete space-efficient storage task cannot be initiated because there is at least one space-efficient logical volume allocated to the space-efficient storage that you have specified. 0xB378 The modify space-efficient storage task has failed because a device adapter error has occurred while you are attempting to modify the user name. 0xB379 The modify space-efficient storage task has failed because an internal error has occurred while you are attempting to modify the repository capacity threshold. 0xB37A The task has failed because a device adapter error has occurred. 0xB37B The task has failed because a device adapter error has occurred.



0xB37C The create space-efficient storage task cannot be initiated because the size of the extent pool is too small to accommodate the amount of space-efficient storage that you have requested. 0xB37D The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB37E The create space-efficient storage task cannot be initiated because extents are currently being formatted and will be available at a later time. 0xB37F The create space-efficient storage task cannot be initiated because the maximum number of ranks has already been configured on the storage image. 0xB380 The create space-efficient storage task cannot be initiated because service intent has been set on the extent pool. 0xB381 The task has failed because an internal error has occurred. 0xB382 The modify space-efficient storage task has failed because the configuration state of the space-efficient storage is not Normal. 0xB383 The space-efficient storage task has failed because the configuration state of the space-efficient storage is not Normal. 0xB384 The create space-efficient storage task cannot be initiated because an internal error has occurred. The value is not a hexadecimal number that is exactly 4 characters in length. 0xB385 The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB386 The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB387 The create space-efficient storage task cannot be initiated because the user name is more than 16 characters in length. 0xB388 The create space-efficient storage task cannot be initiated because the extent pool does not exist. 0xB389 The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB38A The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB38B The create space-efficient storage task cannot be initiated because an error has occurred. A previous configuration task has already configured space-efficient storage on the extent pool that you have specified. 0xB38C The create space-efficient storage task cannot be initiated because the extent pool does not have any ranks configured. 0xB38D The create space-efficient storage task cannot be initiated because the storage allocation method is not supported. 0xB38E The create space-efficient storage task cannot be initiated because the threshold value is not an integer from 0 through 100, inclusive. 0xB38F The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB390 The create space-efficient storage task cannot be initiated because an internal error has occurred. 0xB391 The modify space-efficient storage task cannot be initiated because the user name is more than 16 characters in length. 0xB392 The modify space-efficient storage task cannot be initiated because modification of at least one parameter value that you have specified in the modify task is not supported. 0xB393 The modify space-efficient storage task cannot be initiated because an internal error has occurred. 0xB394 The modify space-efficient storage task cannot be initiated because the threshold value is not an integer from 0 through 100, inclusive. 0xB395 The modify space-efficient storage task cannot be initiated because an internal error has occurred. 0xB396 The create space-efficient storage task cannot be initiated because the repository capacity that you have requested is less than the minimum repository capacity of 16GB. 0xB397 The create space-efficient storage task cannot be initiated because the repository capacity that you have requested is more than the maximum repository capacity. 0xB398 The space-efficient storage task has failed because an internal error has occurred. 0xB399 The create space-efficient storage task has failed because an internal error has occurred. 0xB39A The add space-efficient storage task has failed because an internal error has occurred. 0xB39B The delete space-efficient storage task has failed because an internal error has occurred. 0xB39C The query space-efficient storage task has failed because an internal error has occurred. 0xB39D The query space-efficient storage task has failed because an internal error has occurred. 0xB39E The query space-efficient storage task has failed because an internal error has occurred. 0xB39F The query space-efficient storage task has failed because an internal error has occurred. 0xB3A0 The query space-efficient storage task has failed because an internal error has occurred. 0xB3A1 The space-efficient storage task has failed because an internal error has occurred. 0xB3A2 The space-efficient storage task has failed because an internal error has occurred. 0xB3A3 The query space-efficient storage task has failed because a device adapter error has occurred. 0xB3A4 The query space-efficient storage task has failed because a device adapter error has occurred. 0xB3A5 The create space-efficient logical volume task has failed because the capacity that you have requested exceeds the amount of virtual capacity that can be supported by the space-efficient storage in the extent pool. 0xB3A6 The task cannot be initiated. Either you did not specify the Permit space-efficient Target or Secondary option, or at least one of the options that you have specified is not supported for a space-efficient target or secondary volume. 0xB3A7 The release allocated space subtask has failed. If you submitted a remove FlashCopy command, the remove FlashCopy subtask has succeeded. 0xB3A8 The create space-efficient storage task cannot be completed because the size of the extent pool is too small to accommodate the amount of space-efficient storage that you have requested. 0xB3A9 The create space-efficient storage task cannot be completed because extents are currently being formatted and will be available at a later time. 0xB3AA The create logical volume task cannot be initiated. If you are attempting to create a space-efficient logical volume, the extent allocation method can only be Not Applicable if it is specified. 0xB3AB The create logical volume task cannot be initiated because an alias volume cannot be configured as a space-efficient volume. 0xB3AC The reset service intent task cannot be initiated because a current task is already resetting service intent on all of the device adapter pairs. 0xB3AD The reset service intent task cannot be initiated because information about the local server is unavailable. 0xB3AE The reset service intent task cannot be initiated because a service action is in progress. 0xB3AF The reset service intent task has not reset at least one device adapter pair because at least one device adapter or logical partition is not available. 0xB3B0 The reset service intent task has not reset at least one device adapter pair because information is unavailable for at least one device adapter in the pair. 0xB3B1 Copy Services operation failure: The Change Recording feature is already active and has been defined by a different



Copy Services task type. 0xB3B2 The FlashCopy target is a Global Mirror primary volume. 0xB3B3 The establish Copy Service task cannot be initiated because a volume expansion task is in progress for a volume that you have selected. 0xB3B4 Warmstart failure. 0xB3B5 Operation failure. Contact IBM technical support for assistance. 0xB3B6 Operation failure. 0xB3B7 Operation failure. Contact IBM technical support for assistance. 0xB3B8 At least one of the storage unit server enclosure processor cards is not connected. 0xB3B9 Operation failure. Contact IBM technical support for assistance. 0xB3BA Operation failure. Contact IBM technical support for assistance. 0xB3BB The task cannot be initiated because you have specified an incorrect SNMP address. 0xB3BC The operation has failed to change the Replication Manager password on logical partition 0. Contact IBM technical support for assistance. 0xB3BD The operation has failed to change the Replication Manager password on logical partition 1. Contact IBM technical support for assistance. 0xB3BE The operation has failed to change the Replication Manager password on logical partitions 0 and 1. Contact IBM technical support for assistance. 0xB3BF The serial number is null. Contact IBM technical support for assistance. 0xB3C0 The serial number is not 12 characters in length. Contact IBM technical support for assistance. 0xB3C1 The test Call Home connection has initiated successfully. 0xB3C2 The disconnect virtual private network connection task has failed. 0xB3C3 The disconnect virtual private network connection task has failed because there is no active connection. 0xB3C4 The firmware upgrade has failed because the code bundle could not be unpacked. 0xB3C5 The concurrent firmware upgrade is only valid when the both processor cards are fully operational. 0xB3C6 The audit log location does not exist. 0xB3C7 Failed to write to the audit log file. 0xB3C8 You are not authorized to access the files and directories on the management console. 0xB3C9 The firmware update has failed. There is no response from the storage unit. 0xB3CA The firmware update has failed. No progress reported. 0xB3CB The customer name is not valid. 0xB3CC You are not authorized to create a directory on the management console. 0xB3CD Trace data collection has failed. 0xB3CE The concurrent firmware update operation reports an internal error. The concurrent firmware update did not start because prerequisite conditions are not met, or the concurrent firmware update stopped prematurely. 0xB3CF The nonconcurrent firmware update reports an internal error. The nonconcurrent firmware update did not start, or stopped prematurely. 0xB3D0 You are attempting a service operation that cannot start because it is not supported on the current version of firmware that is installed on the storage unit. 0xB3D1 You are attempting a service operation that cannot start because the storage unit cannot be quiesced. 0xB3D2 You are attempting a service operation that cannot be executed because a storage unit is not defined with the IP address of both processor cards and the machine type and serial number that you are using. 0xB3D3 You are attempting a service operation that cannot start because one of the processor cards on the storage unit is fenced. 0xB3D4 A failure in the storage unit prevented service tracks from being cleared. 0xB3D5 You are attempting a service operation that cannot start because of problems in the storage unit. 0xB3D6 You are attempting a firmware update. This operation did not start or the operation ended prematurely because a hardware problem exists. 0xB3D7 You are attempting a firmware update. This operation did not start or the operation ended prematurely because a software problem exists. 0xB3D8 You are attempting to close a problem that refers to a removed enclosure. The problem cannot be closed because there is a logical configuration of a storage unit that refers to an array in this enclosure. 0xB3D9 The service operation cannot be completed because the guest password that you entered is not correct. 0xB3DA You are attempting to take offline a hardware resource that is in the Failed state. 0xB3DB You are attempting to take offline a hardware resource that is in the Inappropriate state. 0xB3DC You are attempting to take a hardware resource offline but it is no longer present. 0xB3DD You are attempting a firmware update operation. The firmware update operation did not complete because the operation timed out. 0xB3DE You are attempting a firmware update operation. The firmware update operation did not complete because another firmware update operation is in progress. 0xB3DF The reboot service operation failed because the storage unit that you have selected is in single cluster mode. ** Other Return Codes ** 0xBFFF Unknown error code from internal server 0xC000 Internal Exception 0xC001 Wrong username and/or password when trying to connect to the storage device. 0xC002 Internal Exception 0xC003 Internal Exception 0xC004 Internal Exception 0xC005 Internal Exception 0xC006 Timeout during communication with the storage device. 0xC007 Internal Exception 0xC008 Storage device not found at the specified address. 0xC009 Internal Exception



0xC00A Internal Exception 0xC00B Internal Exception 0xC00C Requested function not supported due to backlevel firmware on the storage subsystem. 0xC00D Internal Exception 0xC00E Internal Exception 0xC00F Internal Exception 0xC010 Internal Exception 0xC011 Internal Exception 0xC012 Internal Exception 0xC013 Internal Exception 0xC014 Internal Exception 0xC015 Internal Exception 0xC016 Internal Exception 0xC017 Internal Exception 0xC018 Internal Exception 0xC019 Internal Exception 0xCFFF Unknown Exception ** ESS Return Codes ** ESS code description 0xD000 The required command action is missing. 0xD001 The required command category is missing. 0xD002 The required command flag {0} is missing. 0xD003 The required parameter for command flag {0} is missing. 0xD004 The specified command action {0} is invalid. 0xD005 The specified command category {0} is invalid. 0xD006 The specified command flag {0} is invalid. 0xD007 The specified parameter {0} for command flag {1} is invalid. 0xD008 More than one command action was specified ({0}). 0xD009 More than one command category was specified ({0}). 0xD00A Command flag {0} was specified more than once. 0xD00B The specified command flag {0} and parameter {1} do not match. 0xD00C The argument name is missing at position {0} of parameter {1}. 0xD00D The argument value is missing at position {0} of parameter {1}. 0xD00E The equal sign (=) is missing at position {0} of argument name-value pair {1}. 0xD00F Quotation marks are missing at position {0} of parameter {1}. 0xD010 The required argument name-value pair {0} is missing. 0xD011 The specified argument name {0} is invalid. 0xD012 The specified argument value {0} for argument name {1} is invalid. 0xD013 The specified argument name {0} is invalid for the command action. 0xD014 The argument value, {0}, specified for the argument name {1} is not supported. 0xD015 Argument name {0} was specified more than once. 0xD016 Argument names {0} and {1} are mutually exclusive. 0xD017 The specified duration of {0} hours is lower than the specified frequency of {1} seconds. 0xD018 The specified frequency of {0} seconds is lower than the minimum value allowed of {1}. 0xD019 The format of the specified access file is not supported. 0xD01A The specified flag {0} is not supported within an access file. 0xD01B The required quotation marks are missing on line {0} of the specified access file. 0xD01C Line {0} of the access file is not a valid keylist entry. 0xD01D The specified key {0} for type {1} does not exist in the access file. 0xD01E Line {0} of the specified access file contains a duplicate key {1} for type {2}. 0xD01F The format of the specified access file {0} does not support the -key command flag. 0xD020 An unspecified communication error occurred. 0xD021 The specified server address is unknown to the network. 0xD022 The specified server address was not available. 0xD023 The connection to the specified server was not established. 0xD024 The specified server is currently not available for client requests. 0xD025 The communication to the specified server was not completed. 0xD026 The server response was not successfully processed. 0xD027 The communication to the specified server was terminated prematurely. 0xD028 Information from the server is not current. 0xD029 The server did not respond in time. 0xD02A This version of the CLI is incompatible with the version of the specified server {0}. 0xD02B The versions of the CLI and the Copy Services server do not match. 0xD02C The requested function is not supported by the specified server {0}. 0xD02D The specified host initiator {0} is not defined on the server. 0xD02E The specified host name {0} is not defined on the specified server. 0xD02F The specified host name {0} is SCSI but is not supported. 0xD030 The specified host name {0} is already defined on the server. 0xD031 The specified host initiator {0} is already defined on the server. 0xD032 The specified volume {0} is not found on the server. 0xD033 The specified ESS machine type {0} does not match that of the server. 0xD034 The specified ESS machine serial number {0} does not match that of the server.



0xD035 The specified server address is invalid. 0xD036 Access was denied by the server. 0xD037 The specified port (bay = {0} card = {1} and port = {2}) was not found. 0xD038 The specified number of PAV volumes {0} exceeded the maximum for the base volume {1}. 0xD039 The specified LSS {0} is not defined on the server. 0xD03A The specified volume space {0} is not defined on the server. 0xD03B The specified volume type {0} is not compatible with volume space {1}. 0xD03C The request for creating PAVs failed. 0xD03D More than one CKD LSS was specified. 0xD03E The specified redundancy {0} is not compatible with volume space {1}. 0xD03F No volume space matches the specified volume type {0} and redundancy {1}. 0xD040 The specified volume size of {0} GB is invalid. 0xD041 The specified AS/400 volume size of {0} GB is invalid. 0xD042 Creating volumes failed because the requested number exceeded the maximum of {0} volumes. 0xD043 The specified topology or protocol is incompatible with the current state of the port. 0xD044 The specified profile {0} is not supported by the specified server. 0xD045 The specified PAV {0} does not exist on the specified server. 0xD046 The number of PAVs for LSS {0} exceeded the maximum {1} per volume. 0xD047 The specified volume size of {0} cylinders exceeded for {1} volumes. 0xD048 The specified volume size exceeded the maximum of {0} GB available free space. 0xD049 The specified volume size exceeded the maximum of {0} cylinders of available free space. 0xD04A The specified LSS {0} already contains the maximum number of volumes {1}. 0xD04B The specified number of volume addresses exceeded the maximum of {0} volumes available in the specified LSS. 0xD04C The specified host is not compatible with the volume type {0}. 0xD04D Volume sharing by SCSI-attached OS/400 hosts is not permitted (volume {0}). 0xD04E Disk group {0} is not found. 0xD04F Invalid configuration of disk group, {0} 0xD050 Disk group, {1} is not available. 0xD051 Potential reconfiguration failure will occur for disk group {0} 0xD052 Cannot reconfigure the disk group, {0}. 0xD053 No configuration change is necessary for the command. 0xD054 Email address ({0}) has already been defined, so it cannot be created. 0xD055 Email address ({0}) does not exist, so it cannot be deleted or modified. 0xD056 Pager number ({0}) and pin ({1}) has already been defined, so it cannot be created. 0xD057 Pager number ({0}) and pin ({1}) does not exist, so it cannot be deleted or modified. 0xD058 Unable to create the file {0}. Please make sure that sufficient space is available. 0xD059 The trigger ({0}) specified is invalid. 0xD05A The specified directory ({0}) does not exist, or it does not have write permissions. 0xD05B The user specified diskgroup, {0} has already been configured. 0xD05C The specified userID to be created, {0}, already exists on the specified server. 0xD05D The specified userID to be deleted, {0}, does not exist on the specified server. 0xD05E Cannot create admin with an IP range until an admin without an IP range exists. 0xD05F An admin id cannot delete itself until all other admin ids have been deleted. 0xD060 The specified problem, {0}, does not exist on the specified server. 0xD061 Cannot create the default storwatch id. 0xD062 SNMP address ({0}) has already been defined, so it cannot be created. 0xD063 SNMP address ({0}) does not exist, so it cannot deleted. 0xD064 Cannot send test traps if ESS traps are disabled or no trap addresses are defined. 0xD065 The specified receiver to be created, {0}:{1}, already exists on the specified server. 0xD066 The specified receiver to be deleted, {0}:{1}, does not exist on the specified server. 0xD067 The maximum number of receivers are already configured on the specified server. 0xD068 The specified topology or protocol is incompatible with the specified port. 0xD069 The lss name-value pair is incompatible with the fixed-block volume type. 0xD06A The maximum number of Async PPRC listeners has been reached. Please try again later. 0xD06B An internal error was detected on the server. 0xD06C The esscli application failed to register with CopyServices server. 0xD06D Physical control unit {0} was not found. 0xD06E Failed to get data from the CopyServices server. 0xD06F Failed to establish server connection. Please make sure {0} is up and running. 0xD070 Applet status failed to connect to the server. 0xD071 Failed while disconnecting from the CopyServices server. 0xD072 Server error, failed to get path info. 0xD073 Server error, wrong connection type = {0} for the PPRC path. 0xD074 Server Response is not successful, response = {0}. 0xD075 Registration failure can occur due to one or more of the following reasons:;1. There is a problem in communicating with the server.;2. The given username or password is not correct.;3. The version of the Command Line Interface is incompatible with the version of ESS code. 0xD076 A Username or password was not specified, but the administrative user has enabled the password protection for host commands on the ESS CopyServices Web configuration panel. 0xD077 The performance data received from the ESS is invalid ({0}). 0xD078 No performance data was received during the specified time interval. 0xD079 The server is currently downlevel. Please retry in 5-10 mins. 0xD07A The server is currently obtaining service maintenance. Please retry in 5-10 mins. 0xD07B The chosen Favored Cache Size is larger than the maximum valid size. 0xD07C The input extent and length overlap with an existing extent.



0xD07D The input extent start is larger than the size of the Volume/LUN. 0xD07E The input extent start plus extent length exceeds the size of the Volume/LUN. 0xD07F The chosen volume to add an extent already has the maximum 16 extents defined. 0xD080 The chosen LSS to add an extent already has the maximum 256 extents defined. 0xD081 An internal error was detected by esscli. 0xD082 The Communication sender is not initialized. 0xD083 No information was returned in the response message from the server. 0xD084 The message text resources are unavailable. The esscli installation may be invalid or corrupted. 0xD085 The given port is already used 0xD086 Unable to start a local monitor for receiving the ESS performance data. The specified data collection is cancelled. 0xD087 An error was detected while receiving the collected performance data (code={0}). 0xD088 Unable to determine the IP address of the local machine. This may indicate a problem with the network or the local operating system. 0xD089 Operation Failed. RC={0} 0xD08A Operation Successful. 0xD08B Volume {0} created. 0xD08C Waiting for performance data to be sent from the ESS to port {0}. This could take up to {1} minutes. 0xD08D Received performance data for {0} array(s), {1} volume(s) and {2} PPRC(s) counters. ;Writing to {3}. 0xD08E Performance data collection completed. 0xC100 Access Denied Exception 0xC101 CIM Seascape Exception 0xC102 Seascape Exception 0xC103 Server Response Exception 0xC104 Server Status Exception 0xC105 Shutdown Exception 0xC106 Timeout Exception

tsm solutions by ibm

Documents