Tivoli OMEGAMON XE for Storage on z/OS


Version 4.1.0

Problem Determination Guide

SC32-1836-01
 Tivoli OMEGAMON XE for Storage on z/OS
®


Version 4.1.0

Problem Determination Guide

SC32-1836-01
 Note
Before using this information and the product it supports, read the information in Appendix D, “Notices,” on page 169.

Second Edition (January 2007)

This edition applies to version 4, release 1, modification 0 of IBM Tivoli OMEGAMON XE for Storage on z/OS
(product number 5698-A37) and to all subsequent releases and modifications until otherwise indicated in new
editions.
© Copyright International Business Machines Corporation 2006, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
IBM Tivoli OMEGAMON XE for Storage on z/OS library . . . . . . . . . . . . . . . . . vii
IBM Tivoli Monitoring library . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Other information sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
OMEGAMON II for SMS library . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Accessing terminology online . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Accessing publications online . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Ordering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Tivoli technical training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Conventions used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Typeface conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Operating system-dependent variables and paths . . . . . . . . . . . . . . . . . . . . xi
Transition from Candle to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Part 1. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Overview of messages . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Locations of message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Generating and viewing log files . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Message format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. KS3 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 3. KDF and KDFA Messages . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 4. KDFC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 5. KDFD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 6. KDFH and KDFL Messages . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 7. KDFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 8. KRC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Part 2. Problem determination . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 9. Troubleshooting overview . . . . . . . . . . . . . . . . . . . . . . . . 107

The troubleshooting process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Sources of troubleshooting data. . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Collecting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
About log files for product components . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 10. Troubleshooting installation and configuration . . . . . . . . . . . . . . . 113

Take Action commands show return code 0, but might be unsuccessful . . . . . . . . . . . . 113
A monitored system is displayed in the wrong Tivoli Enterprise Portal . . . . . . . . . . . . . 113
Historical workspaces contain no data . . . . . . . . . . . . . . . . . . . . . . . . 113
Tivoli Enterprise Monitoring Server on z/OS starts normally in a system without the Integrated
Cryptographic Service Facility but does not connect to the Tivoli Enterprise Portal Server . . . . . 113

© Copyright IBM Corp. 2006, 2007 iii

U200 Port in use message found in RKLVLOG, indicating an incorrect default port for TCP/IP profile 114

Chapter 11. Troubleshooting data collection . . . . . . . . . . . . . . . . . . . . . 115

Collection of monitoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
DFSMShsm space-size values exceeded . . . . . . . . . . . . . . . . . . . . . . 115
Workspace displays no data or does not show all the data you expected . . . . . . . . . . 115
Tape collection off; no VTS data occurs . . . . . . . . . . . . . . . . . . . . . . . 115
The timing of tape refreshes is in minutes, but data only changes hourly . . . . . . . . . . . 116
Monitoring agent is running out of storage . . . . . . . . . . . . . . . . . . . . . . 116
Generation of data reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Real-time data reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Short-term historical data reports . . . . . . . . . . . . . . . . . . . . . . . . . 118
Long-term historical data reports . . . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 12. Troubleshooting performance issues . . . . . . . . . . . . . . . . . . . 123

Data set I/O collection tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Performance of the Tivoli Data Warehouse database is degraded or there are gaps where historical
data is unavailable for a specified collection period . . . . . . . . . . . . . . . . . . . 123
Long response times or no results returned when specifying historical collection time spans for some
workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 13. Troubleshooting error conditions . . . . . . . . . . . . . . . . . . . . 125

Understanding abend U0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Workaround . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Determining which volume being processed . . . . . . . . . . . . . . . . . . . . . 125
Monitoring agent receives remote procedure call errors during warehousing, with some requests
timing out and failing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Other Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 14. Troubleshooting specific product features . . . . . . . . . . . . . . . . . 129

Problem determination for the Dataset Attributes Database . . . . . . . . . . . . . . . . . 129
Performance degrades while this feature runs . . . . . . . . . . . . . . . . . . . . 129
Data for the feature is not displayed . . . . . . . . . . . . . . . . . . . . . . . . 129
Data collection for the feature runs too long . . . . . . . . . . . . . . . . . . . . . 129
Data for the feature is not sent to the Tivoli Data Warehouse . . . . . . . . . . . . . . . 130
Data for the feature is displayed incorrectly in the workspace . . . . . . . . . . . . . . . 130
Problem determination for cross-product linking . . . . . . . . . . . . . . . . . . . . . 130
Cross-product links missing from link list . . . . . . . . . . . . . . . . . . . . . . 130
Problems with cross-product linking when linking from an OMEGAMON XE V4.1 workspace to an
OMEGAMON XE V3.1 workspace . . . . . . . . . . . . . . . . . . . . . . . . 131

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on

z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Problem determination flow for an OMEGAMON XE monitoring agent on z/OS . . . . . . . . . 133
Determining whether the problem was caused by an OMEGAMON XE monitoring agent on z/OS 134
Collecting logs for reproducible problems that are reported as Tivoli Enterprise Portal client
problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Unreproducible problems reported as Tivoli Enterprise Portal client problems . . . . . . . . . 137
Problems reported as Tivoli Enterprise Portal Server problems . . . . . . . . . . . . . . 137
Collecting logs on the z/OS system . . . . . . . . . . . . . . . . . . . . . . . . 137
Setting up trace logging for Tivoli OMEGAMON XE for Storage on z/OS . . . . . . . . . . . . 138
Using the KDC_DEBUG environment variable . . . . . . . . . . . . . . . . . . . . 138
Setting up RAS1 tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Setting trace levels on a Tivoli Enterprise Monitoring Server on z/OS using the Configuration Tool 145
Tips regarding the collection of diagnostic data . . . . . . . . . . . . . . . . . . . . . 146

iv IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFDEVIN DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
!Trace in VTAMDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
STBDEBUG(X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Preferred dump options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Understanding RAS1 logs and component prefixes . . . . . . . . . . . . . . . . . . . 147
Format of messages in a RAS1 log . . . . . . . . . . . . . . . . . . . . . . . . 147
Determining which product or component generated a message . . . . . . . . . . . . . . 148
Using the Log and Trace Analyzer tool . . . . . . . . . . . . . . . . . . . . . . . 154
Maintaining the persistent datastore . . . . . . . . . . . . . . . . . . . . . . . . . 154

Appendix B. Historical data collection disk space requirements . . . . . . . . . . . . . 155

Appendix C. Support information . . . . . . . . . . . . . . . . . . . . . . . . . 161

Using IBM Support Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Obtaining fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Obtaining PTFs (Program Temporary Fixes) . . . . . . . . . . . . . . . . . . . . . . 162
Receiving weekly support updates . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Contacting IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Determining the business impact . . . . . . . . . . . . . . . . . . . . . . . . . 164
Describing problems and gathering information . . . . . . . . . . . . . . . . . . . . 164
Submitting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Capturing z/OS logs to send to IBM Software Support . . . . . . . . . . . . . . . . . . 165
Saving the contents of a z/OS log such as RKLVLOG . . . . . . . . . . . . . . . . . 165
Ending one RKLVLOG and starting another . . . . . . . . . . . . . . . . . . . . . 166

Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Contents v
vi IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
About this guide
IBM Tivoli OMEGAMON XE for Storage on z/OS: User’s Guide introduces the features, workspaces,
predefined situations, and attributes, for the IBM® Tivoli® OMEGAMON® XE for Storage on z/OS® product
and supplements the user assistance provided with this product. This document is written for system
programmers.

Users of this book need to be familiar with the following topics:

v The z/OS operating system
v The Microsoft® Windows® operating system
v Performance monitoring concepts

The document assumes no previous experience with Tivoli OMEGAMON products or with IBM Tivoli
Monitoring. To learn about this family of products, access the following Web page: http://www-
306.ibm.com/software/tivoli/solutions/availability/products.html.

Publications
This section lists publications in the Tivoli OMEGAMON XE for Storage on z/OS product, the OMEGAMON
II® for SMS component, and the OMEGAMON XE platform libraries. It also describes how to access Tivoli
publications online and how to order publications.

IBM Tivoli OMEGAMON XE for Storage on z/OS library

The following information sources are available in the IBM Tivoli OMEGAMON XE for Storage on z/OS
library. The books listed here can be ordered on CD using this order number: SCD7-0968-00.
v IBM Tivoli OMEGAMON XE for Storage on z/OS and OMEGAMON II for SMS: Planning, Installation,
and Configuration Guide
Documents the installation and configuration tasks necessary for the implementation of IBM Tivoli
OMEGAMON XE for Storage on z/OS. This document is written for z/OS systems programmers and
others who are responsible for installing and configuring IBM Tivoli OMEGAMON XE for Storage on
z/OS.
v IBM Tivoli OMEGAMON XE for Storage on z/OS: User’s Guide
Introduces the features, workspaces, attributes, and predefined situations for the IBM Tivoli
OMEGAMON XE for Storage on z/OS product and supplements the user assistance provided with this
product. This document is written for system programmers.
v IBM Tivoli OMEGAMON XE for Storage on z/OS: Tuning Guide
Provides information on enhancing the performance of Tivoli OMEGAMON XE for Storage on z/OS so
that you can get the maximum benefit with the least amount of resources.
v IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Contains messages for the IBM Tivoli OMEGAMON XE for Storage on z/OS product and OMEGAMON
II for SMS component and information to help solve problems with the IBM Tivoli OMEGAMON XE for
Storage on z/OS product.
v Tivoli OMEGAMON XE for Storage on z/OS user assistance
Helps operators understand and use the provided data, attributes, commands, and situation to monitor
performance and availability in the context of the product.

IBM Tivoli Monitoring library

The following documents provide information about the IBM Tivoli Monitoring product:
v IBM Tivoli Monitoring Installing and Upgrading OMEGAMON Platform Version 350/360-based Products
and Components, SC32-1975

© Copyright IBM Corp. 2006, 2007 vii

 Describes how to perform an upgrade for your OMEGAMON platform version 350/360-based products
and components to IBM Tivoli Monitoring, version 6.1, or a new installation of the infrastructure provided
by IBM Tivoli Monitoring.
v IBM Tivoli Monitoring: Upgrade Road Map for OMEGAMON XE Version 4.1 Monitoring Agents,
GC32-1980
Describes how to perform an upgrade for your OMEGAMON platform version 350/360-based monitoring
agents on z/OS IBM Tivoli Monitoring, version 6.1, with Fix Pack 3 or an upgrade of IBM Tivoli
Monitoring, version 6.1, to Fix Pack 3.
v Configuring IBM Tivoli Enterprise™ Monitoring Server on z/OS, SC32-9463
Describes how to configure and customize the Tivoli Enterprise Monitoring Server running on z/OS.
v IBM Tivoli Monitoring Installation and Setup Guide, GC32-9407
Provides information about installing and setting up IBM Tivoli Monitoring and upgrading from Candle®
OMEGAMON 350 or 360.
v IBM Tivoli Monitoring Administrator’s Guide, SC32-9408
Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,
including Tivoli Enterprise Portal user administration.
v IBM Tivoli Monitoring User’s Guide, SC32-9409
Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons and detailed
instructions for all Tivoli Enterprise Portal features.
v IBM Tivoli Monitoring Problem Determination Guide, GC32-9458
Provides information and messages to assist users with troubleshooting problems with the software.
v Exploring IBM Tivoli Monitoring, SC32-1803
Provides a series of exercises that help users explore IBM Tivoli Monitoring. After completing the
activities in this workbook, you will have installed and configured your environment, explored both the
graphical and command-line interfaces of the product, used several of the new features in this release
of IBM Tivoli Monitoring (such as creating a monitor based on a custom script), and worked with several
monitoring agents.
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring, GC32-9462
Provides information on how to upgrade from Tivoli Distributed Monitoring.
v Introducing IBM Tivoli Monitoring, GI11-4071
Introduces the components of IBM Tivoli Monitoring and also compares concepts and function of IBM
Tivoli Monitoring to Tivoli Distributed Monitoring.
v IBM Tivoli Universal Agent User’s Guide, SC32-9459
Introduces the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM Tivoli Universal
Agent enables you to use the monitoring and automation capabilities of IBM Tivoli Monitoring to monitor
any type of data you collect.
v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461
Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and provides
descriptions, syntax, and return status codes for the API calls and command-line interface commands.

Other information sources

The following information sources that can help you set up and deploy IBM Tivoli Monitoring, including IBM
Tivoli OMEGAMON XE products:
v Deployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188
v Getting Started with IBM Tivoli Monitoring 6.1 on Distributed Environments, SG24-7143
v IBM Tivoli OMEGAMON XE V3.1.0 Deep Dive on z/OS, SG24-7143
v CCR2™, a monthly e-newsletter for System z™ and zSeries® IT Service Management, Information on
Demand, and Service Oriented Architecture/Enterprise Transformation: http://www.ibm.com/software/
tivoli/features/ccr2/info.html

viii IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
OMEGAMON II for SMS library
Most OMEGAMON II documentation has not been updated. These documents refer to the Candle Support
structure rather than to IBM Software Support. References to Candle Support processes and procedures
are from previous versions of OMEGAMON products. Direct your questions to IBM Software Support. For
details about the IBM support structure, see Appendix C, “Support information,” on page 161.

The following information sources are available in the OMEGAMON II for SMS library. The books listed
here can be ordered on CD using this order number: SCD7-0968-00.
v OMEGAMON II for SMS User’s Guide, GC32-9284
Provides the information necessary for you to quickly start monitoring your storage environment.
v OMEGAMON II for SMS Administrator’s Guide, GC32-9281
Provides the information necessary to customize OMEGAMON II for SMS for your site.
v OMEGAMON II for SMS Tuning Guide, GC32-9283
Provides information on enhancing the performance of OMEGAMON II for SMS. This information allows
you to achieve maximum benefit from OMEGAMON II for SMS while using the minimum amount of
resources.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software.
The Tivoli Software Glossary is available at the following Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient
location. You can access the Terminology Web site at the following Web address:

http://www.ibm.com/software/globalization/terminology

Accessing publications online

The documentation CD or download contains the publications that are in the product library. The format of
the publications is PDF, HTML, or both. Refer to the readme file on the CD for instructions on how to
access the documentation.

IBM posts publications for this and all other Tivoli products, as they become available and whenever they
are updated, to the Tivoli software information center Web site. Access the Tivoli software information
center by first going to the Tivoli software library at the following Web address:

http://publib.boulder.ibm.com/tividd/td/link/tdprodlist.html

In the Tivoli Information Center window, click the Tivoli product manuals link. In the Tivoli Technical
Product Documents Alphabetical Listing window, click the OMEGAMON XE for Storage link to access the
product library at the Tivoli software information center.

Note: If you print PDF documents on other than letter-sized paper, set the option in the File → Print
window that allows Adobe Reader to print letter-sized pages on your local paper.

Ordering publications
You can order many Tivoli publications online at the following Web site: http://www.elink.ibmlink.ibm.com/
public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

About this guide ix

v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli publications. To locate the
telephone number of your local representative, perform the following steps:
1. Go to http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi.
2. Select your country from the list and click Go.
3. Click About this site in the main panel to see an information page that includes the telephone number
of your local representative.

Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to
use software products successfully. With this product, you can use assistive technologies to hear and
navigate the interface. You can also use the keyboard instead of the mouse to operate most features of
the graphical user interface.

For additional information, see the Accessibility Appendix. This appendix is provided only in the user’s
guide.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:

http://www.ibm.com/software/tivoli/education

Support information
Appendix C, “Support information,” on page 161 describes the following options for obtaining support for
IBM products:
v “Using IBM Support Assistant” on page 161
v “Obtaining fixes” on page 162
v “Contacting IBM Software Support” on page 163

Conventions used in this guide

This guide uses several conventions for special terms and actions and for operating system-dependent
commands and paths.

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from
surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,
list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names,
tabs, property sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text (example: a nonswitched line is called a point-to-point line)
v Emphasis of words and letters (words as words example: ″Use the word that to introduce a
restrictive clause.″; letters as letters example: ″The LUN address must start with the letter L.″)

x IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult to distinguish from
surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Operating system-dependent variables and paths

This guide uses the UNIX® convention for specifying environment variables and for directory notation.

When using the Windows command line, replace $variable with %variable% for environment variables and
replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables
are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp
in UNIX.

Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.

Transition from Candle to IBM

IBM acquired Candle Corporation in June 2004. Candle products have new IBM names. In some
publications, the old names are still seen. For example, the old name "CandleNet Portal" might be seen
instead of the new name Tivoli Enterprise Portal. Table 1 shows the mapping of the former Candle names
for OMEGAMON platform components to the new IBM names.
Table 1. Mapping of former Candle names to new IBM names
Candle name IBM Tivoli name
Candle Data Warehouse Tivoli Data Warehouse (not included in the Tivoli
OMEGAMON XE for Storage on z/OS product)
Candle Installation and Configuration Assistance Tool Configuration Tool
(CICAT or ICAT)
Candle Management Server® Tivoli Enterprise Monitoring Server or monitoring server
Candle Monitoring Agent Tivoli Enterprise Monitoring Agent or monitoring agent
®
CandleNet Portal Tivoli Enterprise Portal
CandleNet Portal Client Tivoli Enterprise Portal client or portal client
CandleNet Portal Server Tivoli Enterprise Portal Server or portal server
Candle subsystem OMEGAMON subsystem
CT/Engine ITMS:Engine (IBM Tivoli Management Services: Engine)
event situation event
Event Console Situation Event Console
Manage Candle Services Manage Tivoli Enterprise Monitoring Services
OMEGAMON Platform IBM Tivoli Management Services, which includes the
following components:
v Tivoli Enterprise Portal
v Tivoli Enterprise Portal Server
v Tivoli Enterprise Monitoring Agent
v Tivoli Enterprise Monitoring Server

About this guide xi

Table 1. Mapping of former Candle names to new IBM names (continued)
Candle name IBM Tivoli name
OMEGAMON XE for Storage IBM Tivoli OMEGAMON XE for Storage on z/OS
"Seeding" (initializing the Tivoli Enterprise Monitoring "Adding application support"
Server with situations, templates and other data for
Tivoli OMEGAMON XE for Storage on z/OS)

For a more complete mapping of previous Candle names and new IBM names, refer to
http://www.ibm.com/software/tivoli/products/product-matrix.html.

xii IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Part 1. Messages
This section provides the content of the messages that can be generated by Tivoli OMEGAMON XE for
Storage on z/OS, the Tivoli Enterprise Monitoring Agent, and the OMEGAMON II for SMS component. The
messages are alphabetized and subdivided as follows:
v Chapter 2, “KS3 Messages,” on page 5
v Chapter 3, “KDF and KDFA Messages,” on page 55
v Chapter 4, “KDFC Messages,” on page 71
v Chapter 5, “KDFD Messages,” on page 73
v Chapter 6, “KDFH and KDFL Messages,” on page 91
v Chapter 7, “KDFS Messages,” on page 93
v Chapter 8, “KRC Messages,” on page 103

© Copyright IBM Corp. 2006, 2007 1

2 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 1. Overview of messages
This chapter provides information about the source of messages, message formats, and the Web
application message help for Tivoli OMEGAMON XE for Storage on z/OS, the Tivoli Enterprise Monitoring
Agent, and OMEGAMON II for SMS software.

Locations of message logs

The Tivoli Enterprise Monitoring Agent generates log files that contain messages and trace information.
The log files contain message and trace information about the events and processing being performed.
Log files provide a complete record of system activity, not just of problems. The log files are created when
you start the IBM Tivoli Monitoring components.

When you encounter a problem, check the messages in the log files to determine if the source is a
problem in your environment or with an IBM Tivoli Monitoring product. If you determine that the problem is
caused by a product defect, follow the instructions for contacting IBM Software Support in the Appendix C,
“Support information,” on page 161.

See “Collecting logs for reproducible problems that are reported as Tivoli Enterprise Portal client problems”
on page 134 for the locations of log files. The location of the log depends on the client type and operating
system the client is running on. The following sections provide locations of the fundamental types of logs:
v Logs for components on distributed systems:
– “Collecting logs for the Tivoli Enterprise Portal desktop client” on page 134
– “Collecting logs for the Tivoli Enterprise Portal browser client” on page 135
– “Additional logs to collect: Tivoli Enterprise Portal Server logs, Tivoli Enterprise Monitoring Server
logs, and data warehousing logs” on page 135
v Logs for components on z/OS systems: “Collecting logs on the z/OS system” on page 137
IBM Software Support might request some or all of these files while investigating a problem you have
reported. Also, you might be asked to set a trace in the client and then collect the log. Trace logging is a
fundamental tool for troubleshooting in cases where a problem is reproducible.

Note: Some of the tracing options produce large amounts of trace information. Therefore, monitor the disk
or spool space when activating tracing to prevent your disk or spool from reaching capacity. Return
the trace settings to the default settings after the desired trace information has been collected.

Generating and viewing log files

The log files for the Tivoli OMEGAMON XE for Storage on z/OS Tivoli Enterprise Monitoring Agent are
created as defined in the started procedure when you start the Tivoli Enterprise Monitoring Agent. You can
view the log files with any text editor.

When you investigate problems with the Tivoli OMEGAMON XE for Storage on z/OS Tivoli Enterprise
Monitoring Agent, view the sysout data sets or spool files in the job output and view the z/OS system log
file for any messages that might pertain to the problem.

Message format
The messages for this product are in the following format:
xxxyyyyyz

where:
xxx Alpha-numeric product or component identifier. This product supports three component identifiers:

© Copyright IBM Corp. 2006, 2007 3

 v KS3 for Tivoli OMEGAMON XE for Storage on z/OS
v KDF for OMEGAMON II for SMS
v KRC for OMEGAMON II for SMS
yyyyy Alpha-numeric message ID with three or more alpha-numeric characters.
z One-letter message type. Most, but not all, messages have z, the message type indicator:
v I for informational messages, which typically do not require administrator or operator actions.
v W for warning messages, which typically require actions.
v E for error messages, which indicate a problem that you must resolve before normal operation
can continue.

This book provides the following additional information about these messages, including:
v Message text that is displayed on the same line as the message number
v A description of the system conditions that generated the message
v Suggested responses to the message

4 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Chapter 2. KS3 Messages
This section lists the messages that Tivoli OMEGAMON XE for Storage on z/OS can generate. The
messages are associated with the product components, including the following features:
v Storage Toolkit
v Dataset Attributes Database
v Launch feature for IBM TotalStorage Productivity Center

Explanation: A Terminate request was made either by

KS3A001I DATASET ATTRIBUTE DATABASE
a user or an operator, however a previous Terminate
INITIALIZED
request is still being processed.
Explanation: The Dataset Attribute Database function
System action: The terminate request is ignored.
is starting.
Operator response: Wait for other messages to
System action: None.
indicate that the Dataset Attribute Database function
Operator response: None. This is an informational has terminated. If this message persists and the
message. function does not terminate, contact IBM Software
Support.
KS3A005I IMMEDIATE HALT REQUESTED FOR
DATASET ATTRIBUTE DATABASE KS3A009I DATASET ATTRIBUTE DATABASE
COLLECTION ENDED NORMALLY
Explanation: Dataset Attribute Database collection is Explanation: The Dataset Attribute Database function
stopping because a user or an operator request, the has ended.
specified End time being reached, or an internal error.
System action: None.
System action: None.
Operator response: None. This is an informational
Operator response: None. This is an informational message.
message. Other messages might be displayed to
indicate the specific reason for the immediate halt.
KS3A010E COLLECTION CONTROL SUBTASK
ABENDED WITH [abend_code]
KS3A006E RECURSIVE IMMEDIATE HALT
Explanation: The Dataset Attribute Database
REQUEST
collection function has abended with the indicated code.
Explanation: An immediate halt request was made
System action: The collection control subtask is
either by a user or an operator, however the previous
terminated.
immediate halt request is still being processed.
Operator response: Examine other messages in the
System action: The immediate halt request is ignored.
ITMS:Engine log, RKLVLOG, to determine the cause of
Operator response: Wait for other messages to the abend. Contact IBM Software Support.
indicate that collection has halted. If this message
persists and collection does not halt, issue the S3DA
KS3A011E COLLECTION CONTROL SUBTASK
TERMINATE operator command.
TERMINATED WITH RC=[return_code]
Explanation: The Dataset Attribute Database
KS3A007I DATASET ATTRIBUTE DATABASE
collection function has terminated with the indicated
TERMINATION REQUESTED
return code.
Explanation: A Terminate request was made by an
System action: The collection control subtask is
operator.
terminated.
System action: The Dataset Attribute Database is
Operator response: Examine other messages in the
released and processing is terminated.
ITMS:Engine log, RKLVLOG, or the task JESMSG or
Operator response: None. This is an informational SYSMSG logs to determine the cause of the error.
message. Contact IBM Software Support.

KS3A008E RECURSIVE TERMINATE REQUEST

© Copyright IBM Corp. 2006, 2007 5

KS3A015E • KS3A050I

not returned for display at the Tivoli Enterprise Portal.

KS3A015E COLLECTION CONTROL SUBTASK
ATTACH FAILED WITH Operator response: Examine other messages in the
RC=[return_code] ITMS:Engine log, RKLVLOG, to determine the cause of
the error. Contact IBM Software Support.
Explanation: The creation of the Dataset Attribute
Database collection control subtask failed with the
indicated ATTACH return code. KS3A027E UNABLE TO ALLOCATE BOOKMARK
AREA STORAGE
System action: The collection control subtask is not
started. Explanation: Internal error. The Dataset Attribute
Database summary table interface was unable to
Operator response: Examine other messages in the
allocate storage for its Bookmark area.
ITMS:Engine log, RKLVLOG, or the task JESMSG or
SYSMSG logs to determine the cause of the error. System action: The Summary Table data requested is
Contact IBM Software Support. not returned for display at the Tivoli Enterprise Portal.
Operator response: Examine other messages in the
KS3A016E INVALID POST CODE RECEIVED: ITMS:Engine log, RKLVLOG, to determine the cause of
[post_code] the error. Contact IBM Software Support.
Explanation: The Dataset Attribute Database
collection control subtask presented an invalid internal KS3A028E INVALID SUMMARY TABLE
completion code. REQUESTED: [table_id]
System action: None Explanation: Internal error. The Dataset Attribute
Database summary table interface was invoked with a
Operator response: Examine other messages in the
request for an invalid table.
ITMS:Engine log, RKLVLOG, to determine the cause of
the error. Contact IBM Software Support. System action: The Summary Table data requested is
not returned for display at the Tivoli Enterprise Portal.
KS3A024E DATASET ATTRIBUTE DATABASE Operator response: Examine other messages in the
COLLECTION TERMINATED ITMS:Engine log, RKLVLOG, to determine the cause of
the error. Contact IBM Software Support.
Explanation: The Dataset Attribute Database
collection control task has terminated due to a previous
error. KS3A029E BUFFER TOO SMALL FOR [table_id]
TABLE ENTRY;
System action: Dataset Attribute Database processing
REQUIRED=[size_required],
is terminated and no data from it can be provided.
PROVIDED=[size_provided]
Operator response: Examine other messages in the
Explanation: Internal error. The Dataset Attribute
ITMS:Engine log, RKLVLOG, to determine the cause of
Database summary table interface was invoked with too
the error. Contact IBM Software Support.
small a return area for the requested table.
System action: The Summary Table data requested is
KS3A025E UNABLE TO LOCATE/VALIDATE
not returned for display at the Tivoli Enterprise Portal.
[control_block_id] CONTROL BLOCK
Operator response: Examine other messages in the
Explanation: Internal error. The Dataset Attribute
ITMS:Engine log, RKLVLOG, to determine the cause of
Database summary table interface encountered an
the error. Contact IBM Software Support.
internal error.
System action: The Summary Table data requested is
KS3A050I DATASET ATTRIBUTE DATABASE
not returned for display at the Tivoli Enterprise Portal.
S3DA [command_function] COMMAND
Operator response: Examine other messages in the RECEIVED
ITMS:Engine log, RKLVLOG, to determine the cause of
Explanation: An S3DA command with the indicated
the error. Contact IBM Software Support.
command_function option was received by the Dataset
Attribute Database.
KS3A026E INPUT PARAMETER LIST MISSING
System action: None.
[parmlist_component]
Operator response: None. This is an informational
Explanation: Internal error. The Dataset Attribute
message.
Database summary table interface was invoked with an
invalid parameter list.
System action: The Summary Table data requested is

6 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3A051I • KS3A060I

KS3A051I DATASET ATTRIBUTE DATABASE KS3A055I VALID S3DA COMMAND FUNCTIONS:

S3DA [command_function] COMMAND START/COLLECT-START A
PROCESSED COLLECTION CYCLE
STOP/HALT - STOP A COLLECTION
Explanation: An S3DA command with the indicated
CYCLE
command_function option was processed by the
TERM - TERMINATE ALL DATASET
Dataset Attribute Database.
ATTRIBUTE DATABASE PROCESSING
System action: The action requested by STATUS - DISPLAY COLLECTION
[command_function] is performed. CYCLE STATUS
Operator response: None. This is an informational Explanation: The valid S3DA command functions are
message. listed.
System action: None.
KS3A052W DATASET ATTRIBUTE DATABASE
Operator response: None. Informational message
S3DA [command_function] COMMAND
only.
COULD NOT BE PROCESSED
Explanation: An S3DA command with the indicated
KS3A056E DATASET ATTRIBUTE DATABASE
command_function option was issued but cannot be
S3DA COMMAND IGNORED;
processed.
DATABASE INACTIVE
System action: None. The command is not
Explanation: An S3DA command was issued,
processed.
however the Dataset Attribute Database is inactive.
Operator response: Examine other messages in the
System action: None. The command is not
ITMS:Engine log, RKLVLOG, to determine why the
processed.
command cannot be processed.
Operator response: None.
KS3A053E DATASET ATTRIBUTE DATABASE
S3DA COMMAND FUNCTION NOT KS3A057W DATASET ATTRIBUTE DATABASE
SPECIFIED S3DA START COMMAND IGNORED;
COLLECTION IN PROGRESS
Explanation: An S3DA command was issued without
a command function. Valid command functions are Explanation: An S3DA START command was issued,
displayed in a subsequent message. however Dataset Attribute Database collection is already
in progress.
System action: None. The command is not
processed. System action: None. The command is not processed
and collection continues.
Operator response: Examine subsequent messages
in the ITMS:Engine log, RKLVLOG, to determine valid Operator response: None.
command functions and reissue the S3DA command.
KS3A058W DATASET ATTRIBUTE DATABASE
KS3A054E DATASET ATTRIBUTE DATABASE S3DA STOP COMMAND IGNORED;
S3DA COMMAND FUNCTION INVALID COLLECTION NOT RUNNING
OR OMITTED
Explanation: An S3DA STOP command was issued,
Explanation: An S3DA command was issued with a however Dataset Attribute Database collection is not in
missing or invalid command function. Valid command progress.
functions are displayed in a subsequent message.
System action: None. The command is not
System action: None. The command is not processed.
processed.
Operator response: None.
Operator response: Examine subsequent messages
in the ITMS:Engine log, RKLVLOG, to determine valid
KS3A060I DATASET ATTRIBUTE DATABASE
command functions and reissue the S3DA command.
STATUS
CURRENT STATE: [collection_state]
GENERATED VOLUME TASKS:
[generated_tasks]
COMPLETED VOLUME TASKS:
[completed_tasks]
FAILED VOLUME TASKS: [failed_tasks]

Chapter 2. KS3 Messages 7

KS3A075E • KS3A086W

PROCESSED DATASETS: the error. Contact IBM Software Support.

[processed_datasets]
Explanation: An S3DA STATUS command was KS3A083E INVALID DATASET ALET PASSED:
issued. The current status of collection is displayed. [alet]
System action: None. Explanation: A request was made for detail data from
a specific data set, however the ALET provided is
Operator response: None. Informational message
invalid.
only.
System action: The Dataset Detail Table data
requested is not returned for display at the Tivoli
KS3A075E CANNOT GET WORKG STORAGE
Enterprise Portal.
Explanation: Internal error. The Dataset Attribute
Operator response: If this error was issued in
Database detail table interface was unable to allocate
response to a user-written Query, correct the ALET
storage for its work area.
parm. Otherwise, contact IBM Software Support.
System action: The Dataset Detail Table data
requested is not returned for display at the Tivoli
KS3A084E INVALID DATASET ADDRESS PASSED:
Enterprise Portal.
[address]
Operator response: Examine other messages in the
Explanation: A request was made for detail data from
ITMS:Engine log, RKLVLOG, to determine the cause of
a specific data set, however the Address provided is
the error. Contact IBM Software Support.
invalid.
System action: The Dataset Detail Table data
KS3A076E PUT_PARM FAILURE FOR WORKG
requested is not returned for display at the Tivoli
Explanation: Internal error. The Dataset Attribute Enterprise Portal.
Database detail table interface was unable to set a
Operator response: If this error was issued in
required parameter.
response to a user-written Query, correct the Address
System action: The Dataset Detail Table data parm. Otherwise contact IBM Software Support.
requested is not returned for display at the Tivoli
Enterprise Portal.
KS3A085E ADDRESS AND ALET BOTH
Operator response: Examine other messages in the REQUIRED FOR SPECIFIC DATASET
ITMS:Engine log, RKLVLOG, to determine the cause of RETRIEVAL
the error. Contact IBM Software Support.
Explanation: A request was made for detail data from
a specific data set, however either just the Address or
KS3A077E GET PARM FOR INDEX FAILED ALET was provided. You must specify neither or both.
Explanation: Internal error. The Dataset Attribute System action: The Dataset Detail Table data
Database detail table interface was unable to obtain a requested is not returned for display at the Tivoli
required parameter. Enterprise Portal.
System action: The Dataset Detail Table data Operator response: If this error was issued in
requested is not returned for display at the Tivoli response to a user-written Query, either provide the
Enterprise Portal. missing parameter or remove both the Address and
ALET retrieve the detail data using other attributes.
Operator response: Examine other messages in the Otherwise contact IBM Software Support.
ITMS:Engine log, RKLVLOG, to determine the cause of
the error. Contact IBM Software Support.
KS3A086W AT® LEAST 1 INDEX MUST BE
SPECIFIED FOR DATASET DETAIL
KS3A079E INVALID OR MISSING CONTROL TABLE QUERIES
BLOCK: [control_block_id]
Explanation: A request was made for a data set detail
Explanation: Internal error. The Dataset Attribute data, however no attribute indexes were provided to use
Database detail table interface was unable to validate in selecting detail data to be returned.
the indicated control block.
System action: The Dataset Detail Table data
System action: The Dataset Detail Table data requested is not returned for display at the Tivoli
requested is not returned for display at the Tivoli Enterprise Portal.
Enterprise Portal.
Operator response: If this error was issued in
Operator response: Examine other messages in the response to a user-written Query, provide at least 1
ITMS:Engine log, RKLVLOG, to determine the cause of

8 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3A087E • KS3A113E

attribute and value to use for detail data selection. System action: Processing for the function in process
Otherwise contact IBM Software Support. is halted.
Operator response: Contact IBM Software Support.
KS3A087E UNABLE TO ACQUIRE STACK
STORAGE
KS3A104E [module_name] DA MASTER CB
Explanation: A request was made for a data set detail FAILED VALIDITY CHECK
data, however the database detail retrieval interface
Explanation: Internal error. The indicated control block
was unable to obtain sufficient storage.
was found to be invalid by module [module_name].
System action: The Dataset Detail Table data
System action: Processing for the function in process
requested is not returned for display at the Tivoli
is halted.
Enterprise Portal.
Operator response: Contact IBM Software Support.
Operator response: If this error persists it might be
necessary to increase the storage available to the Tivoli
Enterprise Monitoring Server. Contact IBM Software KS3A105E [module_name] ESTAEX MACRO
Support. FAILED; RC=RETCODE/REASON
Explanation: Internal error. Module [module_name]
KS3A088E INVALID PARMA ADDR FORMAT: was unable to establish its recovery routine.
[input_parm]
System action: Processing for the function in process
Explanation: A request was made for detail data from is halted.
a specific data set, however the Address/ALET provided
is in an invalid format. Operator response: Contact IBM Software Support.

System action: The Dataset Detail Table data

requested is not returned for display at the Tivoli KS3A106E [module_name] UNABLE TO LOCATE
Enterprise Portal. GSA

Operator response: If this error was issued in Explanation: Internal error. The indicated control block
response to a user-written Query, correct the cannot be found by module [module_name].
Address/ALET parm so that it is in the format System action: Processing for the function in process
″:ALET:Address:″. Otherwise contact IBM Software is halted.
Support.
Operator response: Contact IBM Software Support.

KS3A101E [module_name] OM2SM VECTOR NOT

FOUND KS3A107E [module_name] UNABLE TO LOCATE
DACC
Explanation: Internal error. The indicated control block
cannot be found by module [module_name]. Explanation: Internal error. The indicated control block
cannot be found by module [module_name].
System action: Processing for the function in process
is halted. System action: Processing for the function in process
is halted.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support.

KS3A102E [module_name] S3 VECTOR NOT

FOUND KS3A113E [module_name] STORAGE OBTAIN
FAILED WITH RC [return_code]
Explanation: Internal error. The indicated control block
cannot be found by module [module_name]. Explanation: Internal error. An attempt to obtain
storage by module [module_name] failed with return
System action: Processing for the function in process code [return_code].
is halted.
System action: Processing for the function in process
Operator response: Contact IBM Software Support. is halted.
Operator response: Contact IBM Software Support.
KS3A103E [module_name] UNABLE TO LOCATE
DA MASTER CB
Explanation: Internal error. The indicated control block
cannot be found by module [module_name].

Chapter 2. KS3 Messages 9

KS3A114E • KS3A222E

KS3A114E [module_name] GMEM FAILED WITH KS3A202E UNABLE TO ALLOCATE COLLECTION

RC [return_code] CONTROL BLOCKS
Explanation: Internal error. An attempt to obtain Explanation: An attempt to allocate Dataset Attribute
storage by module [module_name] failed with return Database control block storage failed.
code [return_code].
System action: The collection cycle is terminated.
System action: Processing for the function in process
Operator response: This error might be temporary.
is halted.
The error typically occurs when large amounts of
Operator response: Contact IBM Software Support. storage are used by other processes in the address
space when the collection cycle started. If the problem
persists contact IBM Software Support.
KS3A115E [module_name] UNABLE TO OBTAIN
WORKAREA STORAGE
KS3A203E UNABLE TO ALLOCATE
Explanation: Internal error. An attempt to obtain
[dataspace_name] DATASPACE;
workarea storage by module [module_name] failed.
DSAP=[dsap]
System action: Processing for the function in process
Explanation: An attempt to allocate a Dataset
is halted.
Attribute Database data space failed.
Operator response: Contact IBM Software Support.
System action: The collection cycle is terminated.
Operator response: Contact IBM Software Support.
KS3A190E [module_name] ABENDED:
CODE=[abend_code], PSW=[psw]
KS3A204I DATASET ATTRIBUTE
Explanation: Internal error. Module [module_name]
[dataspace_function] DATASPACE:
abnormally terminated with code [abend_code] at
ORIGIN=[dataspace_origin],
location [psw] .
LENGTH=[dataspace_length],
System action: Processing for the function in process NAME=[dataspace_name],
is halted. STOKEN=[dataspace_stoken],
ALET=[dataspace_alet]
Operator response: Contact IBM Software Support.
Explanation: A data space was created with the
indicated attributes for a Dataset Attribute Database
KS3A200I DATASET ATTRIBUTE DATABASE collection cycle.
ON-DEMAND REQUEST RECEIVED
System action: Collection continues using the
Explanation: A request was received to immediately allocated dataspace.
start a Dataset Attribute Database collection cycle, from
either the User Interface window or the S3DA operator Operator response: None.
command.
System action: A collection cycle is started, using the KS3A205E UNKNOWN POST CODE
options currently in effect (for example, Volume/Storage
Explanation: Internal error. The Dataset Attribute
Group exclusion lists or Catalog Collection option).
Database controller was posted with an invalid action
Operator response: None. The status of collection code.
can be obtained by issuing the command
System action: The collection cycle is terminated.
F [taskname], S3DA STATUS
Operator response: Contact IBM Software Support.
KS3A201W ERROR FREEING CONTROL BLOCK
STORAGE; [process] CONTINUES KS3A222E DATASET ATTRIBUTE DATABASE
COLLECTION TERMINATED
Explanation: An attempt to free Dataset Attribute
Database control block storage failed. Explanation: A previously indicated error has caused
the Dataset Attribute Database collection controller to
System action: The indicated process continues.
terminate processing.
Operator response: None. If the condition causing
System action: The collection cycle is terminated.
this message to appear persists over many collection
cycles, storage within the address space might be Operator response: Examine the ITMS:Engine log,
completely filled. Contact IBM Software Support. RKLVLOG, for other messages indicating the original
error. Contact IBM Software Support.

10 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3A225I • KS3A280W

KS3A225I NEXT DATASET ATTRIBUTE KS3A277I DATASET ATTRIBUTE DATABASE

DATABASE COLLECTION CYCLE IN COLLECTION COMPLETE
[wait_time] MINUTES
Explanation: The collection cycle has completed.
Explanation: A request was received to change the
System action: Attribute data from the collection cycle
collection cycle start time, or a cycle has completed and
is now available.
the next cycle has been scheduled.
Operator response: None. Subsequent messages
System action: A collection cycle is scheduled to
indicate the number of volumes and data sets included
begin in [wait_time] minutes.
in the database.
Operator response: None.
KS3A278I [total_tasks] VOLUME TASKS
KS3A251E SMS CLASS MISMATCH DURING GENERATED; [completed_tasks]
SUMMARY MERGE VOLUME TASKS COMPLETED;
[failed_tasks] VOLUME TASKS FAILED;
Explanation: Internal error. A collection control block
[total_datasets] DATASETS
has become corrupted.
PROCESSED
System action: The collection cycle is terminated.
Explanation: The indicated number of volumes and
Operator response: Examine the ITMS:Engine log, data sets were processed during the just-completed
RKLVLOG, for other messages indicating the original Dataset Attribute Database collection cycle.
error. Contact IBM Software Support.
System action: None.
Operator response: None.
KS3A275E TIME MACRO FAILED; DEADLINE
CANNOT BE DETERMINED
KS3A279I [excluded_volumes] VOLUMES
Explanation: Internal error. An attempt to calculate the
EXCLUDED; [total_tasks] VOLUME
specified End time failed.
TASKS GENERATED; [failed_tasks]
System action: The collection cycle continues, VOLUME TASKS FAILED;
however the specified end time cannot be honored. [bypassed_volumes] VOLUMES
BYPASSED; [processed_volumes]
Operator response: Contact IBM Software Support. If VOLUMES PROCESSED;
the collection cycle continues past the time specified by [total_datasets] DATASETS
End Time, you can click the Force Stop button in the PROCESSED
dialog of the user interface to manually stop processing.
Alternatively you can issue the following operator Explanation: The indicated number of volumes and
command: data sets were processed during the just-completed
F taskname,S3DA STOP. Dataset Attribute Database collection cycle. Excluded
volumes are those that were explicitly excluded by the
user interface; Bypassed volumes are those that were in
KS3A276I DATASET ATTRIBUTE DATABASE use and cannot be processed.
COLLECTION CYCLE STARTING;
[volume_count] VOLUMES WILL BE System action: None.
PROCESSED
Operator response: None.
Explanation: A collection cycle has started. Attributes
from data sets on the indicated number of volumes are
KS3A280W DATASET ATTRIBUTE DATABASE
being collected.
COLLECTION DEADLINE REACHED;
System action: The collection cycle continues. IMMEDIATE HALT INITIATED
Operator response: None. The number of volumes to Explanation: The specified End Time has been
be processed might be less than the total number of reached and the collection cycle is not complete.
volumes monitored by the IBM Tivoli OMEGAMON XE
System action: The collection cycle is halted. All
for Storage on z/OS product if you specified Volumes
attributes collected up to this point are available in the
and/or Storage Groups in the User Interface exclusion
database.
lists.
Operator response: None. If collection was halted is
either too early or too late, adjust the End Time
specified in the Dataset Attribute Database User
Interface dialog.

Chapter 2. KS3 Messages 11

KS3A281W • KS3A501E

KS3A281W DATASET ATTRIBUTE DATABASE KS3A292E SUBTASK ENDED WITH ERROR CODE
IMMEDIATE HALT DETECTED; [code]
COLLECTION TERMINATION IN
Explanation: Internal error. A volume collection
PROGRESS
subtask failed with the indicated return code.
Explanation: The collection cycle is halted. The
System action: Collection terminates.
reason for the halt is indicated in a previously-issued
message. Operator response: Contact IBM Software Support.
System action: The collection cycle is halted. All
attributes collected up to this point are available in the KS3A293E DEVICE TABLE UNAVAILABLE;
database. COLLECTION CYCLE CANCELLED
Operator response: None. If the time collection was Explanation: A collection subtask cannot be initiated,
halted is either too early or too late, adjust the End Time as the internal product device table has not yet been
specified in the Dataset Attribute Database User created.
Interface dialog.
System action: The collection cycle is not started.

KS3A282E VOLUME TASK FOR [volser] ABENDED Operator response: This error might occur when a
WITH CODE [abend_code] user or an operator-initiated Start request is issued for
Dataset Attribute Database collection, or a scheduled
Explanation: Internal error. The collection subtask for Start time occurs, before full Tivoli OMEGAMON XE for
the indicated volume abnormally terminated with the Storage product initialization is complete. If this
indicated abend code. condition occurs, configure the manual or scheduled
start to happen after the product is fully initialized. If this
System action: Collection continues for other volume
configuration change does not solve the problem,
tasks. If more than a set number of tasks abend during
contact IBM Software Support.
a collection cycle, the cycle itself is terminated.
Operator response: Examine other messages in the
KS3A294E UNABLE TO OBTAIN VOLUME-LEVEL
ITMS:Engine log, RKLVLOG, to determine the cause of
STV
the error. Contact IBM Software Support.
Explanation: The collection task was unable to obtain
storage for a required control block.
KS3A290E UNABLE TO OBTAIN [size] BYTES FOR
CB STORAGE System action: Collection terminates.
Explanation: The collection task was unable to obtain Operator response: This error might occur because
the indicated amount of storage. of the aggregate storage requirements in the address
space at the time collection started. The problem might
System action: Collection terminates.
not recur on the next collection cycle. Examine other
Operator response: This error might occur because messages in the ITMS:Engine log, RKLVLOG, to
of the aggregate storage requirements in the address determine the cause of the error and contact IBM
space at the time collection started. The problem might Software Support.
not recur on the next collection cycle. Examine other
messages in the ITMS:Engine log, RKLVLOG, to
KS3A299E DATASET ATTRIBUTE DATABASE
determine the cause of the error and contact IBM
COLLECTION CYCLE TERMINATED
Software Support.
Explanation: A previously indicated error has caused
the Dataset Attribute Database collection controller to
KS3A291E SUBTASK ATTACH FAILED WITH RC
terminate processing.
[attach_retcode]
System action: The collection cycle is terminated.
Explanation: An ATTACH for a volume collection
subtask failed with the indicated return code. Operator response: Examine the ITMS:Engine log,
RKLVLOG, for other messages indicating the original
System action: Collection terminates.
error. Contact IBM Software Support.
Operator response: Contact IBM Software Support.
KS3A501E INPUT VWE ADDRESS MISSING OR
INVALID
Explanation: Internal error. A volume collection
subtask cannot locate a required control block.
System action: Collection for the volume terminates.

12 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3A503E • KS3A515W

Other collection tasks continue. the VTOC of the specified volume, for the specified
reason.
Operator response: Examine other messages in the
ITMS:Engine log, RKLVLOG, to determine the cause of System action: Collection for the indicated volume
the error and contact IBM Software Support. terminates. Other collection tasks continue.
Operator response: This message might be issued in
KS3A503E UNABLE TO OBTAIN STORAGE FOR response to a problem with the VTOC of the specified
DSCB BUFFERS ON VOLUME [volser] volume and not a program error. If the volume can be
successfully accessed through other means (for
Explanation: The collection task was unable to obtain
example, ISPF option 3.4), then contact IBM Software
storage for a required control block.
Support.
System action: Collection for the indicated volume
terminates. Other collection tasks continue.
KS3A509E UNABLE TO CREATE NEW
Operator response: This error might occur because DATASPACE; DSAP=[dsap]
of the aggregate storage requirements in the address
Explanation: The current dataspace is full but the
space at the time collection started. The problem might
collection task was unable to create a new one.
not recur on the next collection cycle. Examine other
messages in the ITMS:Engine log, RKLVLOG, to System action: The collection cycle is halted. All
determine the cause of the error and contact IBM attributes collected up to this point are available in the
Software Support. database.
Operator response: This error might occur because
KS3A504E ERROR [return_code/reason_code] of the aggregate storage requirements in the address
ATTEMPTING TO READ VTOC OF space at the time collection started. The problem might
[volser] not recur on the next collection cycle. Examine other
messages in the ITMS:Engine log, RKLVLOG, to
Explanation: The collection task was unable to read
determine the cause of the error and contact IBM
the VTOC of the specified volume, for the specified
Software Support.
reason.
System action: Collection for the indicated volume
KS3A510I NEW DATASPACE [dataspace_name]
terminates. Other collection tasks continue.
ORIGIN=[dataspace_origin],
Operator response: This message might be issued in LENGTH=[dataspace_length],
response to a problem with the VTOC of the specified STOKEN=[dataspace_stoken],
volume and not a program error. If the volume can be ALET=[dataspace_alet]
successfully accessed through other means (for
Explanation: A new dataspace was created with the
example, ISPF option 3.4), contact IBM Software
indicated attributes for a Dataset Attribute Database
Support.
collection cycle.
System action: Collection continues using the newly
KS3A505E UNABLE TO OBTAIN STORAGE FOR
created dataspace.
CSI BUFFER
Operator response: None.
Explanation: Internal error. The collection task was
unable to obtain storage for a required control block.
KS3A515W VOLUME [volser] IS IN USE BY
System action: Collection for this volume terminates.
ANOTHER JOB OR USER AND WILL
Other collection tasks continue.
NOT BE PROCESSED
Operator response: This error might occur because
Explanation: An attempt was made to issue a shared
of the aggregate storage requirements in the address
Enqueue on the specified volume for QNAME
space at the time collection started. The problem might
SYSVTOC, however another job or user has that
not recur on the next collection cycle. Examine other
resource enqueued exclusively.
messages in the ITMS:Engine log, RKLVLOG, to
determine the cause of the error and contact IBM System action: Collection for the specified volume is
Software Support. bypassed. Other volume tasks continue.
Operator response: None.
KS3A506E CVAFSEQ FAILED FOR VOLUME
[volser]; RC=[CVAF_return_code]
CVSTAT=[CVAF_cvstat_code]
Explanation: The collection task was unable to read

Chapter 2. KS3 Messages 13

KS3A520W • KS3D004E

size if the Tivoli Enterprise Monitoring Server startup

KS3A520W COLLECTION TASK TERMINATED FOR
proc does not specify REGION=0M.
VOLUME [volser]
Explanation: A previously issued message has
KS3C003E KS3CIHUB: InsertNodeAtHub call
caused the collection task for the specified volume to
returned with return code
terminate.
Explanation: Module KS3CIHUB issued an
System action: Collection for the specified volume is
InsertNodeAtHubExtended call and received a non-zero
terminated. Other volume tasks continue.
return code. A request was made for a date/time for
Operator response: Examine the ITMS:Engine log, which there is not an applicable record available.
RKLVLOG, for other messages indicating the original
System action: Tivoli OMEGAMON XE for Storage on
error. Contact IBM Software Support.
z/OS continues without returning historical data for this
request.
KS3A550E CVAFDIR FAILED FOR VOLUME
User response: To increase the amount of historical
[volser]; RC=[CVAF_return_code]
data available, expand the Persistent Data Store.
CVSTAT=[CVAF_cvstat_code]
Explanation: The collection task was unable to read
KS3D001E modname : UNABLE TO FIND
the VTOC of the specified volume, for the specified
OM2SMVCT
reason.
Explanation: This is an inernal error.
System action: Collection for the indicated volume
terminates. Other collection tasks continue. System action: Most storage monitoring functions are
disabled.
Operator response: This message might be issued in
response to a problem with the VTOC of the specified User response: Contact IBM Software Support.
volume and not a program error. If the volume can be
successfully accessed through other means (for
example, ISPF option 3.4), then contact IBM Software KS3D002E KS3DINIT : ALLOCATION FAILED FOR
Support. S3VECTOR: SIZE=size, RC=rc
Explanation: An attempt to allocate storage for the S3
KS3C001E modname Unable to acquire the vector table failed.
address of the S3 PDS work area System action: Storage monitoring in Tivoli Enterprise
Explanation: Allocation of the PDS work area Portal is disabled.
normally takes place when the Tivoli Enterprise User response: Contact IBM Software Support.
Monitoring Server is initialized. However, the vector
which should point to this area contains zeros. Possible
values for modname include KS3CPLCU and KS3D003W KS3DINIT : UNABLE TO LOAD
KS3CPCHP. modname

System action: Historical data for Logical Control Explanation: A load failed for the named module.
Units (LCU) are not written to the Persistent Data System action: Most of the modules named by this
Stores until this situation is corrected. message are used to gather data to be written to the
User response: Check for message KS3D002E in the Persistent Data Store for historical reporting. Data
RKLVLOG. If found, take the recommended actions. associated with the module named in this message is
Otherwise, contact IBM Software Support. not written to the PDS until the problem is corrected.
User response: Contact IBM Software Support.
KS3C002E KS3CPLCU Unable to allocate memory
for PDSRec KS3D004E UNABLE TO FIND SE VECTOR
Explanation: The LCU historical retriever was unable Explanation: This is an internal error.
to allocate sufficient Tivoli Enterprise Monitoring Server
Engine storage for a work area. System action: Most storage monitoring functions are
disabled for the Tivoli Enterprise Portal.
System action: Historical data for Logical Control
Units (LCU) are not written to the persistent Data Stores User response: Contact IBM Software Support.
until this situation is corrected.
User response: Increase the value specified in the
MINIMUM parameter of the KDSSYSIN RKANPAR
member. This might also require an increase in region

14 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3D005W • KS3D013E

User response: Contact IBM Software Support. The

KS3D005W KS3DINIT : ALLOCATION FAILED FOR
message type is Tivoli Enterprise Monitoring Server
APPWORK
Engine log, RKLVLOG.
Explanation: An attempt to allocate storage for the
application work area failed.
KS3D010W modname: - pds table RECORDING
System action: Application monitoring is disabled. SKIPPED THIS INTERVAL - reason
User response: Increase the value specified in the Explanation: Module modname has found no entries
MINIMUM parameter of the KDSSYSIN RKANPAR to write to the PDS table pds table. Further information
member. This can also require an increase in region is provided by the information in the reason field.
size, if the Tivoli Enterprise Monitoring Server startup
System action: Tivoli OMEGAMON XE for Storage on
proc does not specify REGION=0M.
z/OS continues without recording historical data for the
given table for this interval.
KS3D006E KS3CINIT - UNABLE TO FIND
User response: If this message persists, Contact IBM
OPERATOR RESOURCE
Software Support. An occurrence of this message
Explanation: An attempt to locate the operator logical during product initialization could be normal.
resource failed.
System action: The Tivoli OMEGAMON XE for KS3D011E modname: - INSERT FAILED FOR pds
Storage on z/OS node is not able to register with the table TABLE INSERT; RC = rc --
hub Tivoli Enterprise Monitoring Server. RECORDING TERMINATING FOR THIS
INTERVAL
User response: Contact IBM Software Support.
Explanation: Module modname has received return
code rc while attempting to write a record to PDS table
KS3D007I KS3CINIT - PROCESSING
pds table.
Explanation: This is an informational message
System action: Tivoli OMEGAMON XE for Storage on
indicating that the Tivoli Enterprise Monitoring Server
z/OS continues without recording historical data for the
initialization routine is running.
given table for the current interval.
System action: Tivoli OMEGAMON XE for Storage on
User response: If this message persists, Contact IBM
z/OS Tivoli Enterprise Monitoring Server initialization
Software Support. An occurrence of this message
has commenced.
during product initialization could be normal.
User response: None. This message is informational.
KS3D012W modname: - RMF SYNCHRONIZATION
KS3D008E modname: - pds table RECORDING FAILED - RECORDING INTERVAL
DISABLED - reason DEFAULTING TO 15 MINUTES

Explanation: Module modname has detected a Explanation: Module modname has not been able to
problem while attempting to write historical data. synchronize historical recording with the RMF interval.
Historical recording for the table pds table has been
System action: Tivoli OMEGAMON XE for Storage on
disabled due to the given reason.
z/OS continues; however, the recording interval for
System action: Tivoli OMEGAMON XE for Storage on historical recording is set to 15 minutes.
z/OS continues without recording historical data for the
User response: If this message persists and RMF
given table.
monitor 1 is active contact IBM Software Support.
User response: Contact IBM Software Support.
KS3D013E modname: ALLOCATION FAILED FOR
KS3D009E modname: - SETUP FAILED FOR pds item, SIZE = size, RC = return code
table INSERTS; RC = rc
Explanation: Module modname was unsuccessful in
Explanation: Module modname has detected a obtaining size number of bytes of storage to allocate
problem while attempting to setup the persistent data the control block item. The request failed with return
store table. The setup call returned with a return code of code return code.
rc. KS3D009E messages normally result when the
System action: Tivoli OMEGAMON XE for Storage on
RMF™ interval ends prior to the complete initialization of
z/OS continues; PDS recording for this interval is
the persistent data store.
skipped.
System action: Tivoli OMEGAMON XE for Storage on
User response: Contact IBM Software Support.
z/OS continues without recording historical data for the
given table.

Chapter 2. KS3 Messages 15

KS3G003I • KS3G009W

KS3G003I [module_name] - STOP REQUEST KS3G007E [module_name] $DGCWRK GMEM

[requested] - DSN GROUP FAILED [RETURN_CODE] - DSN
COLLECTION TERMINATED GROUP COLLECTION TERMINATED
Explanation: A STOP request has been detected by Explanation: Internal error. [module_name] could not
[middle name], and Dataset Group collection is being obtain TEMS-managed storage within the address
terminated, where [requested] is: 0 - NORMAL space to complete Dataset Group initialization.
SHUTDOWN 4 - STORAGE NOT AVAILABLE 8 -
System action: Dataset Group collection is stopped
ENVIRONMENT ERROR 16 - ABEND
until the TEMS is restarted.
System action: Dataset Group collection is stopped
Operator response: Ensure that sufficient storage has
until the ITEMS is restarted.
been specified during product configuration, as per the
Operator response: None, if this message is issued documented guidelines. If changing or increasing
during normal TEMS shutdown (request_code=0). For available storage does not correct the problem, contact
all other request codes, examine the RKLVLOG for IBM Software Support.
other KS3G messages indicating the specific problem
that caused collection to be terminated. Contact IBM
KS3G008E [module_name] DSN GROUP
Software Support.
COLLECTION TERMINATED - OM2SM
VECTOR TABLE NOT FOUND
KS3G004E [module_name] UNABLE TO FIND S3
Explanation: Internal error. The indicated control block
VECTOR - DSN GROUP COLLECTION
could not be found by module [module_name].
TERMINATED
System action: Dataset Group collection is stopped
Explanation: Internal error. The indicated control block
until the TEMS is restarted.
could not be found by module [module_name].
Operator response: Contact IBM Software Support.
System action: Dataset Group collection is stopped
until the TEMS is restarted.
KS3G008W [module_name] USER-SPECIFIED
Operator response: Contact IBM Software Support.
REFRESH INTERVAL LESS THAN
MINIMUM; [interval] MINUTES
KS3G005E [module_name] INVALID REQUEST SUBSTITUTED
CODE [request_code] - DSN GROUP
Explanation: Dataset Group collection control
COLLECTION TERMINATED
contained a refresh interval value less than the
Explanation: Internal error. The indicated invalid minimum allowable interval of 5 minutes.
request code was received by module [module_name].
System action: The indicated value will be used as
System action: Dataset Group collection is stopped the refresh interval.
until the TEMS is restarted.
Operator response: None, unless the specified
Operator response: Contact IBM Software Support. substituted interval is not what is desired. In that case
use the Dataset Group collection control dialog to
specify the desired interval, equal to or greater than 5
KS3G006E SERVICE TASK ATTACH FAILED
minutes.
[attach_code] - DSN GROUP
COLLECTION TERMINATED
KS3G009W [module_name] UNABLE TO
Explanation: Internal error. The dataset group
DETERMINE RMF INTERVAL;
collection subtask could not be attached for the reason
DEFAULTING TO 15 MINUTES
specified in [attach_code].
Explanation: The RMF API was not available to use in
System action: Dataset Group collection is stopped
determining the RMF interval currently in effect.
until the TEMS is restarted.
System action: The interval for Dataset Group
Operator response: For [attach_code] 8, ensure that
collection is set to 15 minutes.
all KS3DGxxx modules were successfully installed into
the data sets specified on the STEPLIB and Operator response: None, unless the specified
RKANMODL DD statements in the TEMS started task substituted interval is not what is desired. In that case
JCL. Contact IBM Software Support. determine why RMF is not active, and use the Dataset
Group collection control dialog to specify a specific
desired interval.

16 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3G030E • KS3G037E

System action: Dataset Group collection is stopped

KS3G030E [module_name] ALESERV MACRO
until the TEMS is restarted.
REQUEST
RC=[return_code,reason_code] Operator response: Contact IBM Software Support.
Explanation: Internal error. The Dataset Group
dataspace could not be created due to the indicated KS3G033E [module_name] Input Parm Error
ALESERV error. Forced Termination
System action: Dataset Group collection is stopped Explanation: Internal error. The Dataset Group
until the TEMS is restarted. collection subtask could not be initiated.
Operator response: Contact IBM Software Support. System action: Dataset Group collection is stopped
until the TEMS is restarted.
KS3G030I DSN GROUPS DATASPACE LOCATED Operator response: Contact IBM Software Support.
AT [dataspace_origin] LENGTH
[dataspace_length]K
KS3G034E [module_name] Storage Obtain Error
Explanation: A dataspace has been allocated to Forced Termination
contain Dataset Group entries; its origin address is
[dataspace_origin] and is [dataspace_length] Kbytes. Explanation: Internal error. The Dataset Group
collection subtask could not be initiated due to
System action: None. insufficient storage.
Operator response: None. See message KS3G031I System action: Dataset Group collection is stopped
for additional dataspace identifying information. This is until the TEMS is restarted.
an informational message stored in the TEMS log file,
RKLVLOG. Operator response: Ensure that sufficient storage has
been specified during product configuration, as per the
documented guidelines. If changing or increasing
KS3G031E [module_name] ESTAEX MACRO available storage does not correct the problem contact
REQUEST IBM Software Support.
RC=[return_code,reason_code]
Explanation: Internal error. The Dataset Group KS3G035E [module_name] Unable to obtain GSA
collection subtask could not be initialized due to the address - Terminating
indicated ESTAEX error.
Explanation: Internal error. The Dataset Group
System action: Dataset Group collection is stopped collection subtask could not be initialized.
until the TEMS is restarted.
System action: Dataset Group collection is stopped
Operator response: Contact IBM Software Support. until the TEMS is restarted.
Operator response: Contact IBM Software Support.
KS3G031I DSN GROUPS DATASPACE
ID=[dataspace_id],
STOKEN=[dataspace_token] KS3G036E [module_name] DSN Group Table Error
- Reason=[reason_code]
Explanation: A dataspace has been allocated to
contain Dataset Group entries; its ID is [dataspace_id] Explanation: Internal error. The Dataset Group
and its token value is [dataspace_token]. collection subtask could not be initialized due to the
indicated reason code.
System action: None.
System action: Dataset Group collection is stopped
Operator response: None. See message KS3G030I until the TEMS is restarted.
for additional dataspace identifying information. This is
an informational message stored in the TEMS log file, Operator response: Contact IBM Software Support.
RKLVLOG.
KS3G037E [detecting_module] Build Error,
KS3G032E [module_name] DSPSERV MACRO missing [missing_module] module
REQUEST Explanation: Possible internal error. The Dataset
RC=[return_code,reason_code] Group collection subtask could not be initialized
Explanation: Internal error. The Dataset Group because the indicated module could not be found.
dataspace could not be created due to the indicated System action: Dataset Group collection is stopped
DSPSERV error. until the TEMS is restarted.
Operator response: Ensure that all KS3SGxxx

Chapter 2. KS3 Messages 17

KS3G038E • KS3G062E

modules were successfully installed into the data sets successfully installed into the dataset specified on the
specified on the STEPLIB and RKANMODL DD RKANMODL DD statements in the TEMS started task
statements in the TEMS started task JCL. If the JCL.
specified module is present in that library, contact IBM
Software Support.
KS3G042E ERROR DURING [module_name]
SDUMPX PROCESSING,
KS3G038E [module_name] Returned error, RC = RC=[sdump_return_code
[return_code]
Explanation: An abend occurred in a Dataset Group
Explanation: Internal error. The indicated Dataset module, however the attempt to take a dump failed with
Group collection subtask module returned the specified the indicated return code.
invalid code.
System action: Abend processing continues.
System action: Dataset Group collection is stopped
Operator response: Examine other console
until the TEMS is restarted.
messages to determine if dump processing encountered
Operator response: Contact IBM Software Support. an out of space or other identifiable condition. If a dump
was produced examine it to determine the cause of the
original abend. Contact IBM Software Support.
KS3G039E [module_name] Invalid interval value -
[interval]
KS3G060E [module_name] DSN Group data
Explanation: Possible internal error. The indicated
collected is incomplete -
Dataset Group collection interval is invalid. Valid
RC=[return_code]
intervals are between 5 and 999 minutes.
Explanation: There is insufficient storage in the
System action: Dataset Group collection is stopped
allocated data space to contain all of the datasets in all
until the TEMS is restarted.
of the specified groups.
Operator response: Check the collection interval
System action: Dataset group processing continues
value specified in the Dataset Group Collection Control
with the datasets that could be contained in the data
dialog and correct it if invalid. If it appears to be correct,
space.
contact IBM Software Support.
Operator response: Examine the installation-specified
maximum data space size and increase it if possible.
KS3G040W [module_name] LOAD FAILED FOR
Delete some dataset groups or make them inactive.
KDFRMFI
Remove some of the dataset masks within the specified
Explanation: Possible internal error. Dataset group groups; Change the dataset masks to limit the number
collection was specified or defaulted as RMF, however of datasets selected from the catalog.
the OMEGAMON XE for Storage RMF interface module
KDFRMFI could not be loaded.
KS3G061E [module_name] Storage Obtain error,
System action: A 15 minute collection interval is used; Data Collection terminating,
processing continues. RC=[return_code]
Operator response: Ensure that module KDFRMFI Explanation: There is insufficient storage in the TEMS
was successfully installed into the dataset specified on address space for the catalog interface to initialize.
the RKANMODL DD statements in the TEMS started
System action: Dataset group processing for this
task JCL. If so, contact IBM Software Support.
collection cycle terminates.
Operator response: Examine the space values
KS3G041W [module_name] COLLECTION
specified for the TEMS address space and the
INTERVAL DEFAULTING TO 15
OMEGAMON for Storage application in RKANPAR, and
MINUTES
increase them if appropriate. If the messages in
Explanation: Possible internal error. Dataset group RKLVLOG indicate that storage is being allocated and
collection was specified or defaulted as RMF, however not released over time, contact IBM Software Support.
the OMEGAMON XE for Storage RMF interface module
KDFRMFI could not be found, or RMF is inactive.
KS3G062E [module_name] Input parameter error,
System action: A 15 minute collection interval is used; Data Collection terminating,
processing continues. RC=[return_code]
Operator response: Ensure that RMF is active on the Explanation: Internal error. The catalog interface
system if RMF interval synchronization is specified for module was invoked with an invalid parameter list.
data collection. Ensure that module KDFRMFI was

18 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3G063E • KS3G096E

System action: Dataset group processing for this System action: Dataset group processing for this
collection cycle terminates. collection cycle terminates.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.

KS3G063E [module_name] Group definitions table KS3G093E IGGCSI00 Returned Error, terminating
error, Data Collection terminating, with RC=[return_code]
RC=[return_code]
Explanation: Possible internal error. The DFSMS
Explanation: Internal error. The catalog interface catalog interface module IGGCSI00 returned an error.
module detected an invalid control block. This could be due to insufficient storage in the address
space or an error by the calling module.
System action: Dataset group processing for this
collection cycle terminates. System action: Dataset group processing for this
collection cycle terminates.
Operator response: Contact IBM Software Support.
Operator response: Examine TEMS storage trace
messages in RKLVLOG and, if there was insufficient
KS3G064E [module_name] KS3SGCSI LOAD Error,
storage in the address space at the time of the error,
Data Collection terminating,
attempt to increase the storage available to the TEMS.
RC=[return_code]
If this does not appear to be a storage-related error,
Explanation: Possible internal error. The Dataset contact IBM Software Support.
Group catalog interface could not be initialized because
module KS3SGCSI could not be found.
KS3G094E IGGCSI00 Load Error, terminating with
System action: Dataset group processing for this RC=12
collection cycle terminates.
Explanation: Possible internal error. The DFSMS
Operator response: Ensure that module KS3SGCSI catalog interface module IGGCSI00 could not be
was successfully installed into the dataset specified on loaded.
the RKANMODL DD statements in the TEMS started
System action: Dataset group processing for this
task JCL. If so, contact IBM Software Support.
collection cycle terminates.
Operator response: Ensure that module IGGCSI00 is
KS3G066E [module_name] UNABLE TO OBTAIN
in the LPA or Linklist and is loadable. If the module
GSA ADDRESS
appears to be correct, contact IBM Software Support.
Explanation: Internal error. The catalog interface
module detected an invalid control block.
KS3G095E Storage Obtain Error, Terminating
System action: Dataset group processing for this RC=12
collection cycle terminates.
Explanation: Possible internal error. The Dataset
Operator response: Contact IBM Software Support. Group catalog interface module could not obtain
sufficient storage to continue processing.
KS3G090E [module_name] LOAD FAILED FOR System action: Dataset group processing for this
MODULE IGGCSI00, RC=[return_code], collection cycle terminates.
REASON CODE=[reason_code]
Operator response: Examine TEMS storage trace
Explanation: Possible internal error. The DFSMS message in RKLVLOG and, if there was insufficient
catalog interface module IGGCSI00 could not be loaded storage in the address space at the time of the error,
for the specified reason. attempt to increase the storage available to the TEMS.
If this does not appear to be an insufficient storage
System action: Dataset group processing for this error, contact IBM Software Support.
collection cycle terminates.
Operator response: Ensure that module IGGCSI00 is KS3G096E Input Parameter Error, Terminating
in the LPA or Linklist and is loadable. If the module RC=12
appears to be correct, contact IBM Software Support.
Explanation: Internal error. The Dataset Group
catalog interface module was invoked with an invalid
KS3G092E Data Retrieval Error, terminating with parameter list.
RC=[return_code]
System action: Dataset group processing for this
Explanation: Internal error. The catalog interface collection cycle terminates.
module detected an error in the returned catalog data.
Operator response: Contact IBM Software Support.

Chapter 2. KS3 Messages 19

KS3G097E • KS3G127E

Operator response: Contact IBM Software Support.

KS3G097E Environment Error, Terminating RC=12
Explanation: A previously reported error has caused
KS3G123E [module_name] UNABLE TO OBTAIN
dataset group catalog processing to terminate.
GSA ADDRESS
System action: Dataset group processing for this
Explanation: Internal error. The Dataset Group
collection cycle terminates.
performance data collection module could not be
Operator response: Examine previous error initialized.
messages to determine the nature of the original error.
System action: Dataset Group collection is stopped
Contact IBM Software Support.
until the TEMS is restarted.
Operator response: Contact IBM Software Support.
KS3G098E [module_name] LOAD FAILED FOR
MODULE ASASYMBM,
RC=[return_code], REASON KS3G124E [module_name] UNABLE TO LOCATE
CODE=[reason_code] ACTIVE DSN TABLE [pointer_name]
Explanation: Possible internal error. The z/OS Explanation: Internal error. The Dataset Group
symbolic dataset name resolution module AMASYMBM performance data collection module could not be
could not be loaded for the specified reason. initialized.
System action: Dataset group processing for this System action: Dataset Group collection is stopped
collection cycle terminates. until the TEMS is restarted.
Operator response: Ensure that module AMASYMBM Operator response: Contact IBM Software Support.
is in the LPA or Linklist and is loadable. If the module
appears to be correct, contact IBM Software Support.
KS3G125W [module_name] PERFORMANCE
SUBSYSTEM NOT FOUND
KS3G120E [module_name] UNABLE TO OBTAIN
WORKAREA STORAGE Explanation: The Dataset Group performance data
collection module was unable to communicate with the
Explanation: Internal error. The Dataset Group OMEGAMON subsystem that actually collects the
performance data collection module could not be performance data .
initiated due to insufficient storage.
System action: Dataset Group collection continues
System action: Dataset Group collection is stopped without dataset performance data.
until the TEMS is restarted.
Operator response: Start the OMEGAMON
Operator response: Ensure that sufficient storage has subsystem to be able to view dataset-level performance
been specified during product configuration, as per the metrics.
documented guidelines. If changing or increasing
available storage does not correct the problem contact
IBM Software Support. KS3G126E [module_name] KDFXRPRT FAILED
WITH RC/REAS: [return_code/
reason_code]
KS3G121E [module_name] MASTER CB ADDRESS
NOT PASSED Explanation: The Dataset Group performance data
collection module received the indicated return and
Explanation: Internal error. The Dataset Group reason codes from the OMEGAMON subsystem.
performance data collection module was invoked with
an invalid parameter list. System action: Dataset Group collection continues
without dataset performance data.
System action: Dataset Group collection is stopped
until the TEMS is restarted. Operator response: Contact IBM Software Support.

Operator response: Contact IBM Software Support.

KS3G127E [module_name] KDFXRPRT FAILED TO
RETURN A BUFFER
KS3G122E [module_name] DSN GROUP MASTER
CONTROL BLOCK FAILED VALIDATION Explanation: The Dataset Group performance data
collection module did not receive any data from the
Explanation: Internal error. The Dataset Group OMEGAMON subsystem.
performance data collection module detected an invalid
control block. System action: Dataset Group collection continues
without dataset performance data.
System action: Dataset Group collection is stopped
until the TEMS is restarted. Operator response: Contact IBM Software Support.

20 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3G128E • KS3G181E

KS3G128E [module_name] ABENDED KS3G155E [module_name] UNABLE TO LOCATE

ACTIVE DSN TABLE [pointer_name]
Explanation: The Dataset Group performance data
collection module abended. Explanation: Internal error. The Dataset Group space
data collection module could not be initialized.
System action: Dataset Group collection is stopped
until the TEMS is restarted. System action: Dataset Group collection is stopped
until the TEMS is restarted.
Operator response: Examine other messages to
determine the exact nature of the abend and contact Operator response: Contact IBM Software Support.
IBM Software Support.
KS3G156E [module_name] ABENDED
KS3G150E [module_name] UNABLE TO OBTAIN
Explanation: The Dataset Group space data collection
WORKAREA STORAGE
module abended.
Explanation: Internal error. The Dataset Group space
System action: Dataset Group collection is stopped
data collection module could not be initialized due to
until the TEMS is restarted.
insufficient storage.
Operator response: Examine other messages to
System action: Dataset Group collection is stopped
determine the exact nature of the abend and contact
until the TEMS is restarted.
IBM Software Support.
Operator response: Ensure that sufficient storage has
been specified during product configuration, as per the
KS3G157E [module_name] ABENDED
documented guidelines. If changing or increasing
available storage does not correct the problem contact Explanation: The Dataset Group space data collection
IBM Software Support. module abended.
System action: Dataset Group collection is stopped
KS3G151E [module_name] MASTER CB ADDRESS until the TEMS is restarted.
NOT PASSED
Operator response: Examine other messages to
Explanation: Internal error. The Dataset Group space determine the exact nature of the abend and contact
data collection module was invoked with an invalid IBM Software Support.
parameter list.
System action: Dataset Group collection is stopped KS3G180E [module_name] VTOC READ
until the TEMS is restarted. PROCESSING TERMINATED FOR
VOLUME [volser]; RESERVED BY
Operator response: Contact IBM Software Support.
ANOTHER JOB/USER
Explanation: The specified volume is reserved for
KS3G152E [module_name] UNABLE TO LOCATE
exclusive use by a job on either this or another system.
DSN GROUP MASTER CONTROL
BLOCK System action: Space collection for the current
dataset is skipped, and processing continues with the
Explanation: Internal error. The Dataset Group space
next dataset.
data collection module detected an invalid control block.
Operator response: None. However if the specified
System action: Dataset Group collection is stopped
volume was known to be available and not reserved at
until the TEMS is restarted.
the time this message was issued, contact IBM
Operator response: Contact IBM Software Support. Software Support.

KS3G153E [module_name] UNABLE TO OBTAIN KS3G181E [module_name] VTOC

GSA ADDRESS DATASET/VOLUME MISMATCH
Explanation: Internal error. The Dataset Group space Explanation: The VTOC record for a volume did not
data collection module could not be initialized. match the volser.
System action: Dataset Group collection is stopped System action: Space collection for the current
until the TEMS is restarted. dataset is skipped, and processing continues with the
next dataset.
Operator response: Contact IBM Software Support.
Operator response: Check the validity of the VTOC
using another utility (e.g. ISPF 3.4; IEHLIST). If it
appears to be correct, contact IBM Software Support.

Chapter 2. KS3 Messages 21

KS3G183E • KS3G205E

KS3G183E [module_name] CVAFFILT FAILED; KS3G201E [module_name] MASTER CB ADDRESS

RC=[cvaf_return_code] NOT PASSED
Explanation: The specified CVAF error was Explanation: Internal error. The Dataset Group
encountered while attempting to read the VTOC for a summary module was invoked with an invalid parameter
volume. list.
System action: Space collection for the current System action: Dataset Group collection is stopped
dataset is skipped, and processing continues with the until the TEMS is restarted.
next dataset.
Operator response: Contact IBM Software Support.
Operator response: Check the validity of the VTOC
using another utility (e.g. ISPF 3.4; IEHLIST). If it
KS3G202E [module_name] DSN GROUP MASTER
appears to be correct, contact IBM Software Support.
CONTROL BLOCK FAILED VALIDATION
Explanation: Internal error. The Dataset Group
KS3G184E [module_name] UNABLE TO LOCATE
summary module detected an invalid control block.
DSCB FOR [datasetname] ON [volser]
System action: Dataset Group collection is stopped
Explanation: The FORMAT 1 DSCB for the specified
until the TEMS is restarted.
dataset, on the specified volume, could not be obtained.
Operator response: Contact IBM Software Support.
System action: Space collection for the current
dataset is skipped, and processing continues with the
next dataset. KS3G203E [module_name] UNABLE TO OBTAIN
GSA ADDRESS
Operator response: Ensure that the dataset actually
exists on the volume, as indicated by its catalog entry. If Explanation: Internal error. The Dataset Group
so, check the validity of its VTOC entry using another summary module could not be initialized.
utility (e.g. ISPF 3.4; IEHLIST). If it appears to be
correct, contact IBM Software Support. System action: Dataset Group collection is stopped
until the TEMS is restarted.

KSGG184E [module_name] UNABLE TO LOCATE Operator response: Contact IBM Software Support.
UCB FOR [datasetname] ON [volser]
Explanation: The UCB for the specified volume could KS3G204E [module_name] UNABLE TO LOCATE
not be located. [control_block_name]

System action: Space collection for the current Explanation: Internal error. The Dataset Group
dataset is skipped, and processing continues with the summary module could not be initialized.
next dataset. System action: Dataset Group collection is stopped
Operator response: Ensure that the specified volume until the TEMS is restarted.
actually exists and is online, and that the dataset Operator response: Contact IBM Software Support.
actually exists on that volume, as indicated by its
catalog entry. If so, check the validity of its VTOC entry
using another utility (e.g. ISPF 3.4; IEHLIST). If it KS3G205E [module_name] UNABLE TO
appears to be correct, contact IBM Software Support. ALLOCATE SUMMARY TABLE
STORAGE

KS3G200E [module_name] UNABLE TO OBTAIN Explanation: Internal error. The Dataset Group
WORKAREA STORAGE summary module could not be initialized due to
insufficient storage.
Explanation: Internal error. The Dataset Group
summary module could not be initialized due to System action: Dataset Group collection is stopped
insufficient storage. until the TEMS is restarted.

System action: Dataset Group collection is stopped Operator response: Ensure that sufficient storage has
until the TEMS is restarted. been specified during product configuration, as per the
documented guidelines. If changing or increasing
Operator response: Ensure that sufficient storage has available storage does not correct the problem contact
been specified during product configuration, as per the IBM Software Support.
documented guidelines. If changing or increasing
available storage does not correct the problem contact
IBM Software Support.

22 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3G207E • KS3G260E

Operator response: Examine the RKLVLOG to

KS3G207E [module_name] ABENDED
determine the original error that caused collection to
Explanation: The Dataset Group summary module terminate. Contact IBM Software Support.
abended.
System action: Dataset Group collection is stopped KS3G235E STORAGE OBTAIN ERROR,
until the TEMS is restarted. REASON:[reason_code]
Operator response: Examine other messages to Explanation: A request was made to display details
determine the exact nature of the abend and contact about a dataset group dataset, however sufficient
IBM Software Support. storage could not be obtained to complete the request.
System action: Dataset Group detail reporting is
KS3G208E [module_name] ABENDED ended for the current request.
Explanation: The Dataset Group summary module Operator response: Examine TEMS storage trace
abended. message in RKLVLOG and, if there was insufficient
storage in the address space at the time of the error,
System action: Dataset Group collection is stopped
attempt to increase the storage available to the TEMS.
until the TEMS is restarted.
If this does not appear to be an insufficient storage
Operator response: Examine other messages to error, contact IBM Software Support.
determine the exact nature of the abend and contact
IBM Software Support.
KS3G236E [module_name] PARAMETER ERROR,
REASON: [reason_code]
KS3G230E [module_name] PROCESS CONTROLS
Explanation: Internal error. The Dataset Group detail
ERROR, REASON: [reason_code]
module was invoked with an invalid parameter list.
Explanation: Internal error. The Dataset Group detail
System action: Dataset Group detail reporting is
module was invoked with an invalid parameter list.
ended for the current request.
System action: Dataset Group detail reporting is
Operator response: Contact IBM Software Support.
ended for the current request.
Operator response: Contact IBM Software Support.
KSGG236E [module_name] PARAMETER ERROR,
REASON: [reason_code]
KS3G231E [module_name] DSN Group Collector
Explanation: Internal error. The Dataset Group detail
Disabled
module was invoked with an invalid parameter list.
Explanation: A request was made to display detail
System action: Dataset Group detail reporting is
information about a dataset group dataset. Either the
ended for the current request.
first collection cycle has not yet completed (e.g. if RMF
or interval collection was specified and the interval has Operator response: Contact IBM Software Support.
not yet expired), or a previous error has caused the
dataset group collection function to be disabled.
KS3G237E [module_name] SUMMARY TABLE
System action: Dataset Group detail reporting is ERROR, REASON: [reason_code]
ended for the current request.
Explanation: Internal error. The Dataset Group
Operator response: Wait until the specified interval summary module was invoked with an invalid parameter
expires before attempting to obtain dataset group list.
summary information. Examine the RKLVLOG for other
System action: Dataset Group summary reporting is
KS3Gnnnn messages to determine if an error has
ended for the current request.
caused collection to be disabled. If so, contact IBM
Software Support. Operator response: Contact IBM Software Support.

KS3G233E [module_name] DSN Group Collection KS3G260E [module_name] PROCESS CONTROLS

Terminating/Stopped ERROR, REASON: [reason_code]
Explanation: A request was made to display details Explanation: Internal error. The Dataset Group
about a dataset group dataset, however a previous error summary module was invoked with an invalid parameter
has caused the dataset group collection function to list.
terminate.
System action: Dataset Group summary reporting is
System action: Dataset Group detail reporting is ended for the current request.
ended for the current request.

Chapter 2. KS3 Messages 23

KS3G261E • KS3G393E

Operator response: Contact IBM Software Support.

KS3G266E STORAGE OBTAIN ERROR,
REASON:[reason_code]
KS3G261E [module_name] DSN Group Collector
Explanation: A request was made to display summary
Disabled
information about a dataset group, however sufficient
Explanation: A request was made to display summary storage could not be obtained to complete the request.
information about a dataset group. Either the first
System action: Dataset Group summary reporting is
collection cycle has not yet completed (e.g. if RMF or
ended for the current request.
interval collection was specified and the interval has not
yet expired), or a previous error has caused the dataset Operator response: Examine TEMS storage trace
group collection function to be disabled. message in RKLVLOG and, if there was insufficient
storage in the address space at the time of the error,
System action: Dataset Group summary reporting is
attempt to increase the storage available to the TEMS.
ended for the current request.
If this does not appear to be an insufficient storage
Operator response: Wait until the specified interval error, contact IBM Software Support.
expires before attempting to obtain dataset group
summary information. Examine the RKLVLOG for other
KS3G390E [module_name] was unable to add
KS3Gnnnn messages to determine if an error has
group name [group_name]
caused collection to be disabled. If so, contact IBM
Software Support. Explanation: The specified new group_name could
not be added because a group with that name already
exists.
KS3G262E [module_name] DSN Group Collection
Terminating/Stopped System action: The new group is not added.
Explanation: A request was made to display summary Operator response: Specify a different group name
information about a dataset group, however a previous for the dataset group being created.
error has caused the dataset group collection function to
terminate.
KS3G391E [module_name] was unable to acquire
System action: Dataset Group summary reporting is lock for Group Mask table rc=[retcode]
ended for the current request.
Explanation: Internal error. A new group could not be
Operator response: Examine the RKLVLOG to added because an internal table lock could not be
determine the original error that caused collection to obtained.
terminate. Contact IBM Software Support.
System action: The new group is not added.
Operator response: Contact IBM Software Support.
KS3G264E DSN Group On-Demand Collection
Timeout
KS3G392E [module_name] internal lock error for
Explanation: A request was made to display summary
Group Mask table rc=[retcode]
information about a dataset group, however the request
could not complete because collection is currently in Explanation: Internal error. A new group could not be
progress. added because an internal table lock could not be
obtained.
System action: Dataset Group summary reporting is
ended for the current request. System action: The new group is not added.
Operator response: Retry the request when collection Operator response: Contact IBM Software Support.
has completed. If collection seems to be hung or
looping, gather diagnostic data, restart the TEMS and
contact IBM Software Support. KS3G393E [module_name] [table_name] table
create rc=[retcode]

KS3G265E [module_name] PARAMETER ERROR, Explanation: Internal error. The specified group could
REASON: [reason_code] not be added because of an error creating the
persistent table.
Explanation: Internal error. The Dataset Group
summary module was invoked with an invalid parameter System action: The new group is not added.
list. Operator response: Contact IBM Software Support.
System action: Dataset Group summary reporting is
ended for the current request.
Operator response: Contact IBM Software Support.

24 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3G394E • KS3G454E

System action: The collection control table is not

KS3G394E [module_name] [table_name] table
updated.
open rc=[retcode]
Operator response: Contact IBM Software Support.
Explanation: Internal error. The specified group could
not be added because of an error opening the
persistent table. KS3G433E [module_name] [table_name] table
create rc=[retcode]
System action: The new group is not added.
Explanation: Internal error. The collection control table
Operator response: Contact IBM Software Support.
could not be updated because of an error creating the
persistent table.
KS3G395E [module_name] [table_name] Error:
System action: The collection control table is not
Vdefcol for col# [column_number]
updated
rc=[retcode]
Operator response: Contact IBM Software Support.
Explanation: Internal error. The specified group could
not be added because of an error defining a column in
the persistent table. KS3G434E [module_name] [table_name] table
open rc=[retcode]
System action: The new group is not added.
Explanation: Internal error. The collection control table
Operator response: Contact IBM Software Support.
could not be updated because of an error opening the
persistent table.
KS3G413E [module_name] [table_name] table
System action: The collection control table is not
create rc=[retcode]
updated
Explanation: Internal error. The specified group could
Operator response: Contact IBM Software Support.
not be added because of an error creating the
persistent table.
KS3G437E [module_name] Validate: Collection
System action: The new group is not added.
type invalid = [invalid_type]
Operator response: Contact IBM Software Support.
Explanation: Internal error. An invalid collection type
was found in the table.
KS3G414E [module_name] [table_name] table
System action: The collection control table is not
open rc=[retcode]
updated.
Explanation: Internal error. The specified group could
Operator response: Contact IBM Software Support.
not be added because of an error opening the
persistent table.
KS3G453E [module_name] [table_name] table
System action: The new group is not added.
create rc=[retcode]
Operator response: Contact IBM Software Support.
Explanation: Internal error. The collection control table
could not be updated because of an error creating the
KS3G431E [module_name] was unable to acquire persistent table.
lock for Collection Interval table
System action: The collection control table is not
rc=[retcode]
updated
Explanation: Internal error. The collection control table
Operator response: Contact IBM Software Support.
could not be updated because an internal table lock
could not be obtained.
KS3G454E [module_name] [table_name] table
System action: The collection control table is not
open rc=[retcode]
updated.
Explanation: Internal error. The collection control table
Operator response: Contact IBM Software Support.
could not be updatedd because of an error opening the
persistent table.
KS3G432E [module_name] internal lock error for
System action: The collection control table is not
Collection Interval table rc=[retcode]
updated
Explanation: Internal error. The collection control table
Operator response: Contact IBM Software Support.
could not be updated because an internal table lock
could not be obtained.

Chapter 2. KS3 Messages 25

KS3G455E • KS3L007I

KS3G455E [module_name] [table_name] Error: KS3L004I Request must be either -remove or

Vdefcol for col# [column_number] -change
rc=[retcode]
Explanation: The required request must be one of the
Explanation: Internal error. The specified group could following
not be added because of an error defining a column in v -remove to remove or delete launch points
the persistent table.
v -change to insert or change launch points
System action: The new group is not added.
Operator response: Contact IBM Software Support. KS3L005E Request update(insert) requires -loc
and -url parameters
KS3L000I Args = arguments Explanation: To insert new launch points both the
Explanation: These are the arguments that was past v -loc to supply the location
to the Launch Application arguments v -url to supply the http address
Programmer response: This displays the arguments
as they were passed to the Launch Application. KS3L006E modname Unable to acquire view
storage
KS3L001E Invalue parameter invalid-parm Explanation: The probe modname failed to acquire
storage to complete a request for data.
Explanation: An invalid parameter of invalid-parm was
entered to the Launch Application. System action: No information is retrieved for this
request.
This message is part of a multiline message when and
invalid parameter is entered. User response: Increase the value specified in the
v KS3L001E Invalid parameter invalid-parm MINIMUM parameter of the KDSSYSIN RKANPAR
member. This can also require an increase in region
v KS3L002I Ensure that entries with embedded blanks
size if the Tivoli Enterprise Monitoring Server startup
are enclosed with double quotes
proc does not specify REGION=0M.
v KS3L003I Example: -location=″C:\Program
files\Internet Explorer\iexplore.exe″
KS3L006I Request update requires -loc or -url
Programmer response: While validating the parameters
parameters passed to the Launch Application an invalid
parameter was detected. Explanation: To update an existing launch points one
or both can be supplied.
v -loc to supply the location
KS3L002I Ensure that entries with embedded
blanks are enclosed with double v -url to supply the http address
quotes
Explanation: This message is part of a multiline KS3L007E modname Unable to acquire
message when and invalid parameter is entered. address/size of Application Table
v KS3L001E Invalid parameter invalid-parm Explanation: A call to program KS3CGAT returned a
v KS3L002I Ensure that entries with embedded blanks non-zero return code. The call originated from module
are enclosed with double quotes modname.
v KS3L003I Example: -location=″C:\Program System action: All application monitoring fails.
files\Internet Explorer\iexplore.exe″
User response: This is an internal error and should
be reported to IBM Software Support immediately.
KS3L003I Example: -location=″C:\Program
files\Internet Explorer\iexplore.exe″
KS3L007I Issue updates using URL= url explore
Explanation: This message is part of a multiline loc= location
message when and invalid parameter is entered.
Explanation: The launch points are updated using the
v KS3L001E Invalid parameter invalid-parm url and location that was entered by the user.
v KS3L002I Ensure that entries with embedded blanks
are enclosed with double quotes
v KS3L003I Example: -location=″C:\Program
files\Internet Explorer\iexplore.exe″

26 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3L008E • KS3L014E

KS3L008E Unable to allocate storage for new KS3L011E KS3LAPPL Unable to allocate storage
application entry for the Application Name Table
Explanation: An attempt to add an application for Explanation: An attempt to allocate storage from the
monitoring has failed because there is insufficient Tivoli Tivoli Enterprise Monitoring Server Engine pool was
Enterprise Monitoring Server Engine storage available. unsuccessful.
System action: The requested application is not System action: Application monitoring is not available
added to the list of monitored applications. in the Tivoli Enterprise Portal.
User response: Increase the value specified in the User response: Increase the value specified in the
MINIMUM parameter of the KDSSYSIN RKANPAR MINIMUM parameter of the KDSSYSIB RKANPAR
member. This can also require an increase in region member. This can also require an increase in region
size if the Tivoli Enterprise Monitoring Server startup size if the Tivoli Enterprise Monitoring Server startup
proc does not specify REGION=0M. proc does not specify REGION=0M.

KS3L008I Issue updates using explore loc= KS3L011I Processing count of total
location
Explanation: This shows the progress of the Launch
Explanation: The launch points are updated using the Application processing the launch points.
location that was entered by the user.
Programmer response: KS3L012E modname Unable to allocate nnnn
bytes storage for xxx volume|dataset
work table
KS3L009E Unable to acquire ASID work area of
nnnnnnn bytes Explanation: An attempt to allocate storage from the
Tivoli Enterprise Monitoring Server Engine pool was
Explanation: An application monitoring request has
unsuccessful. Possible values for modname include
failed because there is insufficient Tivoli Enterprise
KS3LAPDD and KS3LAPVP.
Monitoring Server Engine storage available. nnnnnnn
indicates the number of bytes requested. System action: Application monitoring data set and
volume details information are unavailable until the
System action: All application monitoring fails.
problem is corrected.
User response: Increase the value specified in the
User response: Increase the value specified in the
MINIMUM parameter of the KDSSYSIN RKANPAR
MINIMUM parameter of the KDSSYSIN RKANPAR
member. This can also require an increase in region
member. This can also require an increase in region
size if the Tivoli Enterprise Monitoring Server startup
size if the Tivoli Enterprise Monitoring Server startup
proc does not specify REGION=0M.
proc does not specify REGION=0M.

KS3L009I Issue updates using URL= url

KS3L012I Launch points completed
Explanation: The launch points are updated using the
Explanation: This indicates the completion of the
url that was entered by the user.
Launch Application processing.

KS3L010E modname Unable to acquire address of

KS3L014E modname Invalid or missing WHERE
Application Name Table
clause
Explanation: A call to program KS3CGPTR has failed.
Explanation: An SQL request was received that
The call originated from module modname. Possible
requires a WHERE clause, but none was found.
values for modname include KS3LAPPL and KS3DAPCL.
Possible values for modname include:
System action: All application monitoring fails. v KS3LAPDD
User response: This is an internal error and should v KS3LAPVP
be reported to IBM Software Support immediately. v KS3LAPVS
System action: This SQL request fails.
KS3L010I Launch points with host= host_address
location= location URL= url User response: If you have modified the supplied
SQL, be sure you still have a valid WHERE clause.
Explanation: This displays the arguments entered by Otherwise, contact IBM Software Support.
the user to the Launch Application.

Chapter 2. KS3 Messages 27

KS3L015E • KS3S004E

KS3L015E modname Unable to allocate storage KS3L019E modname: INVALID pds table RECORD
for node table DETECTED, HEADER = header
Explanation: An attempt to allocate storage from the Explanation: Module modname retrieved a record from
Tivoli Enterprise Monitoring Server Engine pool was historical table pds table and found the heading
unsuccessful. Possible values for modname include information to be invalid. The invalid data, header, is
KS3LXSUM and KS3LXSYS. printed as part of the message.
System action: Cross-system DASD monitoring is System action: Tivoli OMEGAMON XE for Storage on
unavailable in Tivoli Enterprise Portal until the problem z/OS continues without returning historical data.
is corrected.
User response: Contact IBM Software Support.
User response: Increase the value specified in the
MINIMUM parameter of the KDSSYSIN RKANPAR
KS3LHREQ KDFHMWE MAX MWES REACHED
member. This can also require an increase in region
size if the Tivoli Enterprise Monitoring Server startup Explanation: Displays in the RKLVLOG file when the
proc does not specify REGION=0M. management work elements (MWEs) that DFSMShsm™
builds exceeds the maximum amount that Tivoli
OMEGAMON XE for Storage on z/OS is capable of
KS3L016E modname Unable to allocate storage
capturing.
for volume table
System action: The returned HSM request data is
Explanation: An attempt to allocate storage from the
truncated.
Tivoli Enterprise Monitoring Server Engine pool was
unsuccessful. Possible values for modname include User response: None. This message is informational.
KS3LXSUM and KS3LXSYS. The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
System action: Cross-system DASD monitoring is
unavailable in Tivoli Enterprise Portal until the problem
is corrected. KS3S001I Scheduler MCB allocated, $DSCWRK
@: address
User response: Increase the value specified in the
MINIMUM parameter of the KDSSYSIN RKANPAR Explanation: The Scheduler master control block
member. This can also require an increase in region $DSCWRK was allocated at address
size if the Tivoli Enterprise Monitoring Server startup
proc does not specify REGION=0M. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3L017E modname: - REQUEST FOR
HISTORICAL DATA FAILED - reason
KS3S002I V#S3VCTR@: address
Explanation: Module modname has detected a problem
while attempting to retrieve historical data. The retrieval Explanation: The address of the V#S3VCTR control
of historical data is unsuccessful due to the given block is address
reason. Operator response: None. This is an informational
System action: Tivoli OMEGAMON XE for Storage on message. This information is stored in the ITMS:Engine
z/OS continues without returning historical data. log, RKLVLOG.

User response: Contact IBM Software Support.

KS3S003I Stop request req_parm , On-line
Scheduling disabled
KS3L018E modname: FETCH FAILED FOR pds
table TABLE; RC = return code -- DATA Explanation: Request req_parm was sent to terminate
RETRIEVAL FROM PDS TERMINATING on-line scheduling

Explanation: Module modname received return code Operator response: None. This is an informational
return code when attempting to retrieve data from the message. This information is stored in the ITMS:Engine
historical table pds table. log, RKLVLOG.

System action: Tivoli OMEGAMON XE for Storage on

z/OS continues without returning historical data. KS3S004E Unable to find S3 vector, On-line
Scheduling disabled
User response: Contact IBM Software Support.
Explanation: This is an internal error.
Tivoli OMEGAMON XE for Storage continues, but the
scheduling function is disabled.

28 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3S005E • KS3S014I

Operator response: Contact IBM Software Support.

KS3S009E module_name On-line Scheduling
This problem information is stored in the ITMS:Engine
terminated
log, RKLVLOG.
Explanation: Termination of on-line scheduling event
controller
KS3S005E Invalid request code req_code , On-line
Scheduling terminated This is an internal error.
Explanation: Received an invalid request code of Tivoli OMEGAMON XE for Storage continues, but the
req_code scheduling function is disabled.
This is an internal error. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
Tivoli OMEGAMON XE for Storage continues, but the
log, RKLVLOG.
scheduling function is terminated.
Operator response: Contact IBM Software Support.
KS3S010I Scheduler table name table_name
This problem information is stored in the ITMS:Engine
log, RKLVLOG. Explanation: The Online Scheduler is using table
table_name
KS3S006E Service task attach failed rc= Operator response: None. This is an informational
return_code , On-line Scheduling message. This information is stored in the ITMS:Engine
terminated log, RKLVLOG.
Explanation: The attach failed with a return code of
return_code KS3S011I Scheduler ASR allocated, D#ASRTB@:
asr_table_address
This is an internal error.
Explanation: The On-line Scheduler has allocated the
Tivoli OMEGAMON XE for Storage continues, but the
Active Service Registry (ASR) at address
scheduling function is terminated.
asr_table_address
Operator response: Contact IBM Software Support.
Operator response: None. This is an informational
This problem information is stored in the ITMS:Engine
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
log, RKLVLOG.

KS3S007E $DSCWRK GMEM failed, rc=

KS3S012I Scheduler SCH allocated, D#SCHTB@:
return_code , On-line Scheduling
sch_table_address
terminated
Explanation: The On-line Scheduler has allocated the
Explanation: Storage getmain for $DSCWRK failed
Scheduler Table (SCH) at address sch_table_address
with return return_code
Operator response: None. This is an informational
The attach failed with a return code of return_code
message. This information is stored in the ITMS:Engine
This is an internal error. log, RKLVLOG.
Tivoli OMEGAMON XE for Storage continues, but the
scheduling function is terminated. KS3S013I Waiting for Scheduler initialization to
complete
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Explanation: The main task is waiting the scheduler
log, RKLVLOG. task to complete its initialization process.
Operator response: None. This is an informational
KS3S008E module_name OM2SM vector table not message. This information is stored in the ITMS:Engine
found, On-line Scheduling disabled log, RKLVLOG.
Explanation: This is an internal error.
KS3S014I Completed Scheduler initialization
Tivoli OMEGAMON XE for Storage continues, but the
scheduling function is disabled. Explanation: The scheduler has completed its
initialization process.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: None. This is an informational
log, RKLVLOG. message. This information is stored in the ITMS:Engine
log, RKLVLOG.

Chapter 2. KS3 Messages 29

KS3S015I • KS3S037E

KS3S015I No schedule events loaded, Wait for KS3S033E module_name Input Parameter error,
schedule events reason= reason_code ; Forced
termination
Explanation: This message indicates that was were
no previously saved events. Explanation: This is an internal error.
Operator response: None. This is an informational Tivoli OMEGAMON XE for Storage continues, but the
message. This information is stored in the ITMS:Engine scheduling function is disabled.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3S016I Scheduler task started log, RKLVLOG.
Explanation: The scheduler task has started, and is
able to process scheduling request. KS3S034E module_name Storage obtain error rc=
return_code ; Forced termination
Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine Explanation: This is an internal error.
log, RKLVLOG.
Tivoli OMEGAMON XE for Storage continues, but the
scheduling function is terminated.
KS3S017I Waiting for termination request
Operator response: Contact IBM Software Support.
Explanation: This is an information messages. A This problem information is stored in the ITMS:Engine
scheduling task is waiting for termination request. log, RKLVLOG.
Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine KS3S035E module_name Unable to obtain GSA
log, RKLVLOG. address; Terminating
Explanation: This is an internal error.
KS3S020E module_name Abnormal Termination
Tivoli OMEGAMON XE for Storage continues, but the
Recovered
scheduling function is terminated.
Explanation: module_name has experienced an
Operator response: Contact IBM Software Support.
abnormal termination that was recovered.
This problem information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support. log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3S036E module_name Process Controls error,
reason= reason_code ; Forced
KS3S031E module_name ESTAEX macro request termination
rc = return_code
Explanation: This is an internal error.
Explanation: The ESTEAX macro returned with a
Tivoli OMEGAMON XE for Storage continues, but the
return code of return_code
scheduling function is terminated.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
log, RKLVLOG.

KS3S032E module_name Requested schedule time

KS3S037E module_name On-line Scheduler Table
is earlier than the current time
error, reason= reason_code table=
Explanation: The schedule requested a time that is table_name
earlier then the current time on the Tivoli Enterprise
Explanation: This is an internal error.
Monitoring Server.
Tivoli OMEGAMON XE for Storage continues, but the
Operator response: Request a time later than the
scheduling function is terminated.
current time of the Tivoli Enterprise Monitoring Server.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

30 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3S038E • KS3S115I

KS3S038E module_name Build error; missing KS3S102W Requested schedule event time has
missing_module_name module past
Explanation: This is an internal error. Explanation: The time of the event to be scheduled
has pasted.
Tivoli OMEGAMON XE for Storage continues, but the
scheduling function is terminated. Operator response: None. This is an warning
message. This information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support.
log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3S105I There are event_count saved Scheduled
Events
KS3S039E module_name Storage obtain error for
callback parameter list. Invocation Explanation: The initialization of the Scheduler found
ignored. event_count events that were stored
Explanation: This is an internal error. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
Tivoli OMEGAMON XE for Storage continues, but the
log, RKLVLOG.
requested command is ignored.
Operator response: Contact IBM Software Support.
KS3S110I Loaded schedule: Time( schedule_time )
This problem information is stored in the ITMS:Engine
Days( schedule_days ) Callback(
log, RKLVLOG.
callback_name ) Name( event_name )
Info( event_user_info )
KS3S042E ERROR DURING module_name
Explanation: The event has been loaded into the
SDUMPX PROCESSING, RC=
Scheduler
return_code , REASON= reason_code
Operator response: None. This is an informational
Explanation: This is an internal error.
message. This information is stored in the ITMS:Engine
Tivoli OMEGAMON XE for Storage continues, but the log, RKLVLOG.
scheduling function is terminated.
Operator response: Contact IBM Software Support. KS3S111I Requesting schedule: Time(
This problem information is stored in the ITMS:Engine schedule_time ) Days( schedule_days )
log, RKLVLOG. Callback( callback_name ) Name(
event_name ) Info( event_user_info )
KS3S100I Waiting for Schedule Event request Explanation: There has been a request for this event
to the Scheduler
Explanation: The scheduler is waiting for new
scheduling requests. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
Operator response: None. This is an informational log, RKLVLOG.
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3S112I Deleting schedule: Time( schedule_time
) Days( schedule_days ) Callback(
KS3S101E On-line Scheduler unable to define callback_name ) Name( event_name )
Scheduler Event variable; rc= Info( event_user_info )
return_code variable= variable_name
Explanation: There has been a request to delete this
Explanation: This is an internal error. event from the Scheduler
Tivoli OMEGAMON XE for Storage continues, but the Operator response: None. This is an informational
scheduling function is terminated. message. This information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support. log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG. KS3S115I Active schedule: Time( schedule_time )
Days( schedule_days ) Callback(
callback_name ) Name( event_name )
Info( event_user_info )
Explanation: This event is ready for processing

Chapter 2. KS3 Messages 31

KS3S120I • KS3T230E

Operator response: None. This is an informational

KS3S143I Invoked Callback( callback_name )
message. This information is stored in the ITMS:Engine
Name( event_name ) with @
log, RKLVLOG.
event_cb_address
Explanation: The supplied callback for this event was
KS3S120I Missed schedule: Time( schedule_time )
invoked.
Days( schedule_days ) Callback(
callback_name ) Name( event_name ) Operator response: None. This is an informational
Info( event_user_info ) message. This information is stored in the ITMS:Engine
log, RKLVLOG.
Explanation: During initialization this event’s time has
passed.
KS3S144I Callback address invalid Callback(
The expiration time of the event occurred while the
callback_name ) Name( event_name )
Tivoli OMEGAMON XE for Storage product was not
with @ event_cb_address
active
Explanation: The callback address supplied is not
Operator response: None. This is an informational
valid.
message. This information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3S130I Next scheduled interval:
schedule_interval (HH:MM:SS.hh)
KS3T210E SHOWCB FIELDS=(ACBLEN,RPLLEN),
Explanation: This message indicates when the
ERROR: R15(R15) R0(R0)
scheduler processes events. This is based on the
earliest event to process. Explanation: An attempt to determine the length of a
VSAM access control block and a request parameter list
Operator response: None. This is an informational
failed. The SHOWCB is issued to recover from a
message. This information is stored in the ITMS:Engine
previously detected VSAM OPEN failure.
log, RKLVLOG.
System action: Open processing fails, and service
probes initialization completes unsuccessfully.
KS3S131I Waiting for Schedule Timer to expire
User response: Ensure that the VSAM KSDS has
Explanation: The Scheduler is waiting for the time of
been properly created for the OMEGAMON II for SMS
the next event to expire.
services checkpoint data set. The destination is the
Operator response: None. This is an informational Tivoli Enterprise Monitoring Server Engine log,
message. This information is stored in the ITMS:Engine RKLVLOG.
log, RKLVLOG.
KS3T220E GENCB BLK=ACB ERROR: R15(R15)
KS3S141I Unable to locate Callback( R0(R0)
callback_name ) Name( event_name )
Explanation: An attempt to create and initialize a
reason= reason_code
VSAM access control block has failed. The GENCB is
Explanation: The callback name that was supplied issued to recover from a previously detected VSAM
with the event was not found in the Active Service OPEN failure.
Registry.
System action: Open processing fails, and service
Operator response: None. This is an informational probes initialization completes unsuccessfully.
message. This information is stored in the ITMS:Engine
User response: Ensure that the VSAM KSDS has
log, RKLVLOG.
been properly created for the OMEGAMON II for SMS
services checkpoint data set. The destination is the
KS3S142I Invoking Callback( callback_name ) Tivoli Enterprise Monitoring Server Engine log,
Name( event_name ) with @ RKLVLOG.
event_cb_address
Explanation: The event time has expired and the KS3T230E GENCB BLK=RPL ERROR: R15(R15)
supplied callback routine is invoked. R0(R0)
Operator response: None. This is an informational Explanation: An attempt to create and initialize a
message. This information is stored in the ITMS:Engine VSAM request parameter list has failed. The GENCB is
log, RKLVLOG. issued to recover from a previously detected VSAM
OPEN failure.

32 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T240E • KS3T309E

System action: Open processing fails, and service

KS3T304E DFDSS MASTER A.S. DETECTED
probes initialization completes unsuccessfully.
ERROR DURING SLAVE A.S.
User response: Ensure that the VSAM KSDS has EXECUTION
been properly created for the OMEGAMON II for SMS
Explanation: The DFDSS slave address space
services checkpoint data set. The destination is the
returned a non-zero condition code to the master
Tivoli Enterprise Monitoring Server Engine log,
address space.
RKLVLOG.
System action: The DFDSS master task terminates.
KS3T240E UNABLE TO OPEN DDNAME(ddname) User response: Check the DFDSS slave address
R15(R15) ACBERFLG(acberflg) space for messages or a dump. The destination is the
MVS™ system console.
Explanation: An attempt to reopen a VSAM data set
for load processing has failed. The OPEN is issued to
recover from a previously detected VSAM OPEN failure. KS3T306E SLAVE ADDRESS SPACE POSSIBLE
JCL ERROR
System action: Open processing fails, and service
probes initialization completes unsuccessfully. Explanation: The DFDSS slave address space ended
without returning a condition code.
User response: Ensure that the VSAM KSDS has
been properly created for the OMEGAMON II for SMS System action: The DFDSS master task terminates.
services checkpoint data set. The destination is the
User response: A JCL error might have occurred.
Tivoli Enterprise Monitoring Server Engine log,
Check for any messages or for a dump in the DFDSS
RKLVLOG.
slave address space. The destination is the MVS
system console.
KS3T250E UNABLE TO INITIALIZE
DDNAME(ddname) R15(R2)
KS3T307E TIMED OUT WAITING FOR SLAVE A.S.
RPLERRCD(rplerrcd)
INITIALIZATION
Explanation: An attempt to load a new record into a
Explanation: The SLAVESTCTIMEOUT value was
VSAM data set for load processing has failed. A PUT is
exceeded before DFDSS slave address space
issued to initialize the contents of a VSAM data set that
initialization completed.
previously failed to OPEN.
System action: The DFDSS master task terminates.
System action: Open processing fails, and service
probes initialization completes unsuccessfully. User response: Check the DFDSS slave address
space for messages or a dump. You can also check the
User response: Ensure that the VSAM KSDS has
value of SLAVESTCTIMEOUT in member KDFACTIN in
been properly created for the OMEGAMON II for SMS
library rhilev.RKANPAR, and, if appropriate, change the
services checkpoint data set. The destination is the
time-out value (specified in seconds). The destination is
Tivoli Enterprise Monitoring Server Engine log,
the MVS system console.
RKLVLOG.

KS3T308E ERROR OCCURRED IN SLAVE A.S.,

KS3T260E UNABLE TO CLOSE DDNAME(ddname)
CHECK FOR POSSIBLE DUMP
R15(R2) ACBERFLG(acberflg)
Explanation: The DFDSS slave address space
Explanation: An attempt to close a VSAM data set for
returned a non-zero condition code to the master
load processing has failed. The CLOSE is issued to
address space.
initialize the contents of a VSAM data set that
previously failed to OPEN. System action: The DFDSS master task terminates.
System action: Open processing fails, and service User response: Check the DFDSS slave address
probes initialization completes unsuccessfully. space for messages or a dump. The destination is the
MVS system console.
User response: Ensure that the VSAM KSDS has
been properly created for the OMEGAMON II for SMS
services checkpoint data set. The destination is the KS3T309E ERROR DURING enqueue/dequeue,
Tivoli Enterprise Monitoring Server Engine log, CODE= cccc, TERMINATING
RKLVLOG.
Explanation: An error occurred during an enqueue or
dequeue. The condition code from the error is included.
System action: The DFDSS master task terminates.
User response: Call IBM Software Support.

Chapter 2. KS3 Messages 33

KS3T312E • KS3T332E

KS3T312E ERROR INITIATING DFDSS STC, RC= KS3T317E ERROR DURING VSAM OPERATION
rcrc, REASON= reason ON ACTION RESPONSE CHECKPOINT
DATA, ERROR= eeee
Explanation: An error occurred starting the DFDSS
slave address space. The ASCRE macro provides the Explanation: The DFDSS slave address space
rcrc and reason values. attempted to open, read, update, or close the Response
Checkpoint Dataset. VSAM returned a non-zero
System action: The DFDSS master task terminates.
condition code. Additional action messages indicate the
User response: Call IBM Software Support. The exact operation. One of the following messages follows
destination is the MVS system console. this message: KDFAP3035E, KDFAP3036E,
KDFAP3037E, or KDFAP3038E.
KS3T313E ERROR DURING SLAVE A.S. System action: The DFDSS slave and master tasks
INITIALIZATION, RETURN CODE= rcrc terminate.
Explanation: During initialization, the DFDSS slave User response: Check the DFDSS slave address
address space returned a non-zero condition code to space for additional messages. The destination is the
the master address space. MVS system console.
System action: The DFDSS master task terminates.
KS3T330E ERROR OBTAINING SLAVE A.S. ENQ,
User response: Check the DFDSS slave address RETURN CODE= rcrc, TERMINATING
space for messages or a dump. The destination is the
MVS system console. Explanation: A non-zero code was returned while
attempting to obtain an ENQUE.
KS3T314E ERROR ENCOUNTERED IN IKJTSOEV, System action: The DFDSS slave and master tasks
RETURN CODE= rcrc, REASON CODE= terminate.
reason
User response: Call IBM Software Support. The
Explanation: A non-zero code was returned from the destination is the MVS system console.
TSO/E environmental initialization.
System action: The DFDSS slave and master tasks KS3T331E ERROR ALLOCATING ACTION
terminate. RESPONSE DATASET, TERMINATING
User response: Call IBM Software Support. The Explanation: An error was encountered dynamically
destination is the MVS system console. allocating the action response data set. Message
KDFAP3016E should precede this message and provide
the exact error and resolution.
KS3T315E LOAD FAILED FOR MODULE
IKJTSOEV, RETURN CODE= rcrc, System action: The DFDSS slave and master tasks
REASON CODE= reason terminate.
Explanation: A non-zero code was returned from User response: Call IBM Software Support. The
LOAD while attempting to load the module. destination is the MVS system console.
System action: The DFDSS slave and master tasks
terminate. KS3T332E ERROR OBTAINING TIVOLI
ENTERPRISE MONITORING SERVER
User response: Call IBM Software Support. The ENQ, RETURN CODE= rcrc,
destination is the MVS system console. TERMINATING
Explanation: A non-zero code was returned
KS3T316E ERROR DURING DYNAMIC attempting to obtain an ENQUE.
ALLOCATION, ERROR= eeee, INFO= iiii
System action: The DFDSS slave and master tasks
Explanation: A non-zero code was returned while terminate.
attempting to dynamically allocate a resource.
User response: Call IBM Software Support. The
System action: The DFDSS slave and master tasks destination is the MVS system console.
terminate.
User response: Call IBM Software Support. The
destination is the MVS system console.

34 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T333E • KS3T410W

System action: The DFDSS slave and master tasks

KS3T333E ERROR DURING ATTACH OF
terminate.
KS3IRACT, RETURN CODE= rcrc,
TERMINATING User response: Call IBM Software Support. The
destination is the MVS system console.
Explanation: A non-zero code was returned from
ATTACH while attempting to execute the request REXX
exec. KS3T338E ERROR CLOSING ACTION RESPONSE
CHECKPOINT DATASET, TERMINATING
System action: The DFDSS slave and master tasks
terminate. Explanation: An error was encountered closing the
action response checkpoint data set. Message
User response: Call IBM Software Support. The
KDFAP3017E should precede this message and provide
destination is the MVS system console.
the exact error and information codes for resolution.
System action: The DFDSS slave and master tasks
KS3T334E ERROR ALLOCATING ACTION
terminate.
RESPONSE CHECKPOINT DATASET,
TERMINATING User response: Call IBM Software Support. The
destination is the MVS system console.
Explanation: An error was encountered dynamically
allocating the action response checkpoint data set.
Message KDFAP3016E should precede this message KS3T340E ERROR RETRIEVING PARMS, RC= rcrc,
and provide the exact error and information codes for REASON= reason
resolution.
Explanation: A non-zero return code was received
System action: The DFDSS slave and master tasks from ASEXT while attempting to move from the DFDSS
terminate. master address space to the slave address space.
User response: Call IBM Software Support. The System action: The DFDSS slave and master tasks
destination is the MVS system console. terminate.
User response: Call IBM Software Support. The
KS3T335E ERROR OPENING ACTION RESPONSE destination is the MVS system console.
CHECKPOINT DATASET, TERMINATING
System action: An error was encountered opening the KS3T341E DFDSS SLAVE ADDRESS SPACE
action response checkpoint data set. Message STARTED WITH INVALID JOB PARMS=
KDFAP3017E should precede this message and provide (invalid_job_parms)
the exact error and information codes for resolution. The
DFDSS slave and master tasks terminate. Explanation: Invalid parameters were specified on the
EXEC statement in the slave address started task JCL.
User response: Call IBM Software Support. The
destination is the MVS system console. System action: The DFDSS slave and master tasks
terminate.

KS3T336E ERROR READING ACTION RESPONSE User response: Correct the started task JCL and
CHECKPOINT DATASET, TERMINATING resubmit the request. The destination is the MVS
system console.
Explanation: An error was encountered reading the
action response checkpoint data set. Message
KDFAP3017E should precede this message and provide KS3T410W FREE FAILED FOR DDNAME= ddname.
the exact error and information codes for resolution. RC=rc ERROR=error INFO=info

System action: The DFDSS slave and master tasks Explanation: A service response data set containing
terminate. response text could not be freed. The data set is most
likely open by another thread of execution and cannot
User response: Call IBM Software Support. The be freed until the other thread of execution has closed
destination is the MVS system console. the data set. The destination is the Tivoli Enterprise
Monitoring Server Engine log, RKLVLOG.
KS3T337E ERROR UPDATING ACTION Message Variables:
RESPONSE CHECKPOINT DATASET,
TERMINATING ddname
The DDNAME of the response data set
Explanation: An error was encountered updating the allocation.
action response checkpoint data set. Message
KDFAP3017E should precede this message and provide rc The SVC 99 return code for the deallocation
the exact error and information codes for resolution. request.

Chapter 2. KS3 Messages 35

KS3T422E • KS3T431E

error The SVC 99 error code for the deallocation. OMEGAMON II for SMS
The Tivoli Enterprise Monitoring Server
request info
address space log, RKLVLOG.
The SVC 99 information code for the
deallocation request. All other products
The data collection (Tivoli Enterprise
System action: This message is issued to the
Monitoring Server) address space SYSTSPRT
RKLVLOG. No further actions are taken to delete the
output file.
data set. If the error occurred in response to an SQL
DELETE request to remove a completed service
request, a return code of RCABVU (26) is returned to KS3T427E REXX ERROR EXECUTING EXEC ’p0’.
the application issuing the DELETE. REXX RETURN CODE p1.
User response: None. Explanation: An error occurred when invoking the
specified REXX exec.
KS3T422E NULL RESULT FROM REXX EXEC ’ p0’. Message Variables:
Explanation: A null result was returned by the p1 Specifies the REXX return code.
specified REXX exec. The exec should provide a
System action: The attempt to perform the associated
numeric result.
service request is aborted. See TSO/E REXX
System action: None. Programming Services IRXEXEC return codes for a
description of the actions taken by REXX.
User response: This error could have been caused by
an error in the stated REXX exec. Unless you have User response: See the REXX messages issued prior
changed the exec, contact IBM Software Support to this message for more information regarding the
providing this message with the REXX exec name. If error. Review the appropriate destination:
this problem has not been reported previously, you must
OMEGAMON II for SMS
determine why the REXX exec did not return a result.
The Tivoli Enterprise Monitoring Server
You might have to place additional problem
address space log, RKLVLOG.
determination aids in the REXX exec. Review the
appropriate destination: All other products
The data collection (Tivoli Enterprise
OMEGAMON II for SMS
Monitoring Server) address space SYSTSPRT
The Tivoli Enterprise Monitoring Server
output file.
address space log, RKLVLOG.
All other products
KS3T431E INCOMPATIBLE LEVEL OF TSO/E.
The data collection (Tivoli Enterprise
VERSION 2.3.0 OR ABOVE REQUIRED.
Monitoring Server) address space SYSTSPRT
VERSION=p0 RELEASE=p1.
output file.
Explanation: The action services could not be
initialized because an unsupported version of TSO/E
KS3T426E NON-NUMERIC RESULT FROM REXX
was found. Action services requires TSO/E VERSION
EXEC ’ p0’.
2.3.0 or above to satisfy action requests.
Explanation: A non-numeric result was returned by
Message Variables:
the specified REXX exec. The exec should provide a
numeric result. p0 Reports the version of TSO/E found for the
system.
System action: None.
p1 Reports the release of TSO/E found for the
User response: The routine calling REXX failed to
system.
indicate that a only a numeric result was valid. Contact
IBM Software Support providing this message with the System action: The action request processing is
REXX exec name. If this problem has not been reported disabled for the remainder of the data collection (Tivoli
previously, you must determine why the REXX did not Enterprise Monitoring Server) address space execution.
return a numeric result. The routine calling REXX,
KS3IRACT, could have failed to indicate that the REXX User response: Install the required version of TSO/E
exec was being called as a command, or a REXX error before attempting to issue any action requests. The
could have occurred. REXX should detect an error (and destination is the Tivoli Enterprise Monitoring Server
issue message IRX0026) if a non-numeric result is Engine log, RKLVLOG.
being returned by an exec called as a command.
Review the appropriate destination:

36 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T441E • KS3T608E

KS3T441E LOAD FAILED FOR MODULE= p0 KS3T603E KLE_FrrSet ([return_code]) in

ABEND=p1 REASON CODE=p2. [program_name]
Explanation: An attempt to load an executable load Explanation: This is an internal error. An abend
module into virtual storage has failed. Action load occurred during Storage Toolkit processing.
modules are dynamically loaded into virtual storage
System action: Tivoli OMEGAMON XE for Storage
when the first action request is received. Subsequent
continues, but the operation triggering the error does
action requests reuse the dynamically loaded modules.
not complete.
If a load fails, the current action request fails as do
subsequent action requests. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
Message Variables:
log, RKLVLOG.
p0 The load module that failed.
p1 The MVS abend code of the module that failed. KS3T604E Internal error: REQUEST number must
follow comma
p2 The reason code.
Explanation: This is an internal error.
System action: The current request for action fails
and a nonzero return code is returned to the application System action: Tivoli OMEGAMON XE for Storage
program. continues, but the operation triggering the error does
not complete.
User response: Refer to the MVS system codes
documentation for further details on the load failure. Operator response: Contact IBM Software Support.
Ensure that the complete set of load modules are This problem information is stored in the ITMS:Engine
referenced by the STEPLIB concatenation of the started log, RKLVLOG.
task JCL. Also ensure that the entire list of load module
libraries in the STEPLIB concatenation are
KS3T605E Internal error: REQUEST number not
APF-authorized. The destination is the Tivoli Enterprise
valid, source = [program_id]
Monitoring Server Engine log, RKLVLOG.
Explanation: This is an internal error.
KS3T600I STORAGE TOOLKIT INITIALIZATION System action: Tivoli OMEGAMON XE for Storage
HAS COMMENCED continues, but the operation triggering the error does
not complete.
Explanation: The Storage Toolkit is starting.
Operator response: Contact IBM Software Support.
System action: None.
This problem information is stored in the ITMS:Engine
Operator response: None. This is an informational log, RKLVLOG.
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T606E The Storage Toolkit request could not
be started. Check the System log for
KS3T601I STORAGE TOOLKIT ANCHOR BLOCK error messages issued by the started
HAS BEEN CREATED task that is named: ’[stc_name]’
Explanation: The Storage Toolkit is starting. Explanation: The action request cannot be started.
System action: None. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Operator response: None. This is an informational
not complete.
message. This information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: Check the System log for related
error messages and take the corrective action indicated
by those messages. This information is stored in the
KS3T602E Internal error: REQUEST number not
ITMS:Engine log, RKLVLOG.
found
Explanation: This is an internal error.
KS3T608E REQUEST option CANCEL not
System action: The action request is not submitted supported
for execution because it cannot be found.
Explanation: Action requests cannot be cancelled
Operator response: Contact IBM Software Support. after they are submitted.
This problem information is stored in the ITMS:Engine
System action: The action request is not cancelled.
log, RKLVLOG.
Operator response: Contact IBM Software Support.

Chapter 2. KS3 Messages 37

KS3T609E • KS3T618E

This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T609E Internal error analyzing REQUEST KS3T614E Internal error: RESULT number must
option be present
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T610E missing BIGSTRING column in KS3T615E Internal error: period missing between
TK_MODIFY query REQUEST and RESULT
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T611E Internal error: unknown REQUEST KS3T616E Internal error: REQUEST number must
option be present
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T612E Internal error: REQUEST option must KS3T617E Internal error: REQUEST or RESULT
follow REQUEST id number not valid
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T613E Internal error: number must follow KS3T618E Internal error: REQUEST or RESULT
REQUEST command number not valid
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.

38 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T619E • KS3T625E

This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T619E STORAGE TOOLKIT ANCHOR BLOCK
CREATE ERROR STATUS CODE KS3T623E STORAGE TOOLKIT RUNTIME
[status_code] REASON CODE PARAMETER MEMBER KS3ACTIN
[reason_code] READ ERROR RETURN CODE
[return_code]
Explanation: This is an internal error.
Explanation: This is an internal error. The
System action: Tivoli OMEGAMON XE for Storage
[return_code] has these possible values and meanings:
continues, but the operation triggering the error does
4=Invalid handle, 5=Unsuccessful, >256=An abend
not complete.
occurred. The value is (abendcode * 256). Divide the
Operator response: Contact IBM Software Support. value by 256. If the result is less than 4096, this is a
This problem information is stored in the ITMS:Engine system abend. If the result is greater than 4096,
log, RKLVLOG. subtract 4096 to determine the user abend code.
System action: Tivoli OMEGAMON XE for Storage
KS3T620E Internal error analyzing RESULT option continues, but the operation triggering the error does
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support. KS3T624W KS3ACTIN RUNTIME PARAMETER
This problem information is stored in the ITMS:Engine ’[parm_name]’ NOT RECOGNIZED
log, RKLVLOG.
Explanation: An unsupported keyword was supplied
within the KS3ACTIN parameter member in the
KS3T621E STORAGE TOOLKIT RUNTIME RKANPAR data set. The valid keywords are:
PARAMETER MEMBER KS3ACTIN NOT CHECKDSNAME RESDSMGMTCLAS RESDSNPREFIX
FOUND RESDSSTORCLAS RESDSUNIT RESDSVOLUME
Explanation: The RKANPAR data set must contain a SLAVESTCNAME SLAVEMAXSTC SLAVETIMEOUT
member named KS3ACTIN, which contains options that System action: Tivoli OMEGAMON XE for Storage
control the Storage Toolkit. continues, but the operation triggering the error does
System action: The Storage Toolkit is not started. not complete.

Operator response: Rerun the process provided by Operator response: Ensure that you have not
the Configuration Tool to create the KS3ACTIN member. incorrectly typed any of these keywords and that you
This information is stored in the ITMS:Engine log, have not added any text other than keywords or
RKLVLOG. comments (line that begin with *). Also ensure that the
keyword and value supplied are in this format:
″KEYWORD = VALUE″ (but without the quotes). This
KS3T622E STORAGE TOOLKIT RUNTIME information is stored in the ITMS:Engine log, RKLVLOG.
PARAMETER MEMBER KS3ACTIN
OPEN ERROR RETURN CODE
[return_code] KS3T625E STORAGE TOOLKIT RUNTIME
PARAMETER MEMBER KS3ACTIN
Explanation: This is an internal error. The CLOSE ERROR RETURN CODE
[return_code] has these possible values and meanings: [return_code]
4=Invalid handle, 5=Unsuccessful - open failed,
8=Dynamic allocation failed, 9=DSNAME greater than Explanation: This is an internal error. The
44 characters, 10=DDNAME greater than 8 characters, [return_code] has these possible values and meanings:
>256=An abend occurred. The value is (abendcode * 4=Invalid handle, >256=An abend occurred. The value
256). Divide the value by 256. If the result is less than is (abendcode * 256). Divide the value by 256. If the
4096, this is a system abend. If the result is greater result is less than 4096, this is a system abend. If the
than 4096, subtract 4096 to determine the user abend result is greater than 4096, subtract 4096 to determine
code. the user abend code.

System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.

Chapter 2. KS3 Messages 39

KS3T626E • KS3T637E

Operator response: Contact IBM Software Support. Operator response: None. This is an informational
This problem information is stored in the ITMS:Engine message. This information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T626E Internal error: unknown RESULT option KS3T631W PARAMETER ’[keyword]’ WAS
SPECIFIED PREVIOUSLY
Explanation: This is an internal error.
Explanation: A keyword was repeated within the
System action: Tivoli OMEGAMON XE for Storage
KS3ACTIN parameter member.
continues, but the operation triggering the error does
not complete. System action: The additional keyword and value are
ignored.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Remove one of the instances of
log, RKLVLOG. the keyword parameter and its value. This information is
stored in the ITMS:Engine log, RKLVLOG.
KS3T627E Internal error: RESULT option must
follow RESULT id KS3T632E Internal error: unrecognized TOOLKIT
command
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T628I STORAGE TOOLKIT RUNTIME
PARAMETER MEMBER KS3ACTIN WAS KS3T633W PARAMETER ’[keyword]’ VALUE
READ SUCCESSFULLY ’[value]’ IS TOO LONG MAXIMUM
LENGTH IS [max_length]
Explanation: The KS3ACTIN member was read and
processed successfully. Explanation: This is an internal error.
System action: The Storage Toolkit continues its System action: Tivoli OMEGAMON XE for Storage
initialization processing. continues, but the operation triggering the error does
not complete.
Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T629E STORAGE TOOLKIT RUNTIME
PARAMETER MEMBER KS3ACTIN WAS KS3T636W PARAMETER ’[keyword]’ VALUE
NOT READ SUCCESSFULLY ’[value]’ IS NOT NUMERIC
Explanation: This is an internal error. Explanation: A non-numeric parameter value was
supplied where not allowed.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: The keyword and value are ignored.
not complete.
Operator response: Ensure that the SLAVEMAXSTC
Operator response: Contact IBM Software Support. and SLAVETIMEOUT values are numeric. This
This problem information is stored in the ITMS:Engine information is stored in the ITMS:Engine log, RKLVLOG.
log, RKLVLOG.
KS3T637E Internal error: missing TOOLKIT
KS3T630I PARAMETER ’[keyword]’ HAS BEEN command
ASSIGNED THE VALUE ’[value]’
Explanation: This is an internal error.
Explanation: The parameter listed was understood
System action: Tivoli OMEGAMON XE for Storage
and processed.
continues, but the operation triggering the error does
System action: None. not complete.

40 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T638W • KS3T650I

Operator response: Contact IBM Software Support.

KS3T643E STORAGE TOOLKIT ADMINISTRATION
This problem information is stored in the ITMS:Engine
RECORD NOT RECOGNIZED, SOURCE
log, RKLVLOG.
= [program_id]
Explanation: This is an internal error.
KS3T638W Execution thread is active, cannot
delete System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Explanation: An action request that is running has
not complete.
been selected for deletion by a user.
Operator response: Contact IBM Software Support.
System action: The request is running is allowed to
This problem information is stored in the ITMS:Engine
continue and is not deleted.
log, RKLVLOG.
Operator response: The request may be selected for
deletion by a user after it has run. This information is
KS3T644I STORAGE TOOLKIT IS BEING COLD
stored in the ITMS:Engine log, RKLVLOG.
STARTED
Explanation: No action requests have been found
KS3T639E STORAGE TOOLKIT RUNTIME
within the Storage Toolkit during startup, which is
PARAMETER ’[parm_name]’ HAS NOT
normal when the Storage Toolkit is first installed and
BEEN SPECIFIED AND WILL NOT BE
configured.
DEFAULTED
System action: None.
Explanation: The specified parameter was not
specified. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
System action: Tivoli OMEGAMON XE for Storage
log, RKLVLOG.
continues, but the operation triggering the error does
not complete.
KS3T645I STORAGE TOOLKIT ADMINISTRATION
Operator response: Supply the specified keyword and
RECORD FOUND
its value within the KS3ACTIN parameter member in
RKANPAR. This information is stored in the Explanation: Normal startup is under way.
ITMS:Engine log, RKLVLOG.
System action: The Storage Toolkit continues to
initialize.
KS3T640E STORAGE TOOLKIT ADMINISTRATION
Operator response: None. This is an informational
RECORD READ ERROR
message. This information is stored in the ITMS:Engine
Explanation: This is an internal error. log, RKLVLOG.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does KS3T646I STORAGE TOOLKIT IS BEING WARM
not complete. STARTED
Operator response: Contact IBM Software Support. Explanation: Normal startup is under way.
This problem information is stored in the ITMS:Engine
System action: The Storage Toolkit continues to
log, RKLVLOG.
initialize.
Operator response: None. This is an informational
KS3T642W STORAGE TOOLKIT CHECKPOINT
message. This information is stored in the ITMS:Engine
DATASET OPEN FAILURE
log, RKLVLOG.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage KS3T650I [restore_count] SERVICE REQUESTS
continues, but the operation triggering the error does HAVE BEEN RESTORED
not complete.
Explanation: The specified number of action requests
Operator response: Contact IBM Software Support. have been found within the Storage Toolkit during
This problem information is stored in the ITMS:Engine startup.
log, RKLVLOG.
System action: None.
Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
log, RKLVLOG.

Chapter 2. KS3 Messages 41

KS3T654E • KS3T670E

KS3T654E Internal error: Storage Toolkit KS3T666E Quoted string found without XML
Tk_global is 0, source = [program_id] attribute name or equal sign
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T655E Timed-Out waiting for Checkpoint KS3T667E Character < found within XML start or
dataset lock end tag
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T657E Internal error: Storage Toolkit KS3T668E Invalid XML end tag
Tk_modify_session not found
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
System action: Tivoli OMEGAMON XE for Storage continues, but the operation triggering the error does
continues, but the operation triggering the error does not complete.
not complete.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support. This problem information is stored in the ITMS:Engine
This problem information is stored in the ITMS:Engine log, RKLVLOG.
log, RKLVLOG.
KS3T669E Invalid XML start tag
KS3T660E Character < found in string, which is
Explanation: This is an internal error.
not valid
System action: Tivoli OMEGAMON XE for Storage
Explanation: This is an internal error.
continues, but the operation triggering the error does
System action: Tivoli OMEGAMON XE for Storage not complete.
continues, but the operation triggering the error does
Operator response: Contact IBM Software Support.
not complete.
This problem information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support. log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T670E Character = found without earlier XML
attribute name
KS3T665E End of quoted string not found
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
System action: Tivoli OMEGAMON XE for Storage continues, but the operation triggering the error does
continues, but the operation triggering the error does not complete.
not complete.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support. This problem information is stored in the ITMS:Engine
This problem information is stored in the ITMS:Engine log, RKLVLOG.
log, RKLVLOG.

42 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T671E • KS3T685E

KS3T671E End of XML start tag found while XML KS3T676E ---End of parse 2---
attribute incomplete
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
System action: Tivoli OMEGAMON XE for Storage continues, but the operation triggering the error does
continues, but the operation triggering the error does not complete.
not complete.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support. This problem information is stored in the ITMS:Engine
This problem information is stored in the ITMS:Engine log, RKLVLOG.
log, RKLVLOG.
KS3T677E Invalid character (0x[character]) after
KS3T672E Invalid characters within XML start tag number
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T673E XML attribute value must be enclosed KS3T678E Invalid character ([first_character])
in single or double quotes found in string
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T674E Invalid characters within XML end tag KS3T679E Internal error: couldn’t find
Tk_command variable
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T675E End of parse but with incomplete parse
state KS3T685E Unsupported DFSMShsm or
DFSMSdss™ request type
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.

Chapter 2. KS3 Messages 43

KS3T686E • KS3T695E

KS3T686E Internal error: ABEND occurred in KS3T691E STORAGE TOOLKIT INITIALIZATION

Tk_lock constructor HAS FAILED
Explanation: This is an internal error. Explanation: The Storage Toolkit initialization process
has failed.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. Look for additional error messages earlier in the log file.
This information is stored in the ITMS:Engine log,
RKLVLOG.
KS3T687E Internal error: Incorrect access value in
Tk_lock constructor
KS3T692E Existing XMIT session but REQ != END
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T688E Unrecognized attribute found in XMIT
header KS3T693E New XMIT session but REQ != START
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T689E Logic error while parsing XMIT header KS3T694E New XMIT session but no REQ
attribute
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does System action: Tivoli OMEGAMON XE for Storage
not complete. continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: Contact IBM Software Support.
log, RKLVLOG. This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T690I STORAGE TOOLKIT INITIALIZATION
HAS COMPLETED KS3T695E There must be exactly one ID attribute
in the XMIT header
Explanation: The Storage Toolkit initialization process
is complete and successful. Explanation: This is an internal error.
System action: None. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Operator response: None. This is an informational
not complete.
message. This information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

44 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T696E • KS3T705E

KS3T696E Internal error: PERMUTE attribute not KS3T701I STORAGE TOOLKIT TERMINATION
YES or NO HAS COMPLETED
Explanation: This is an internal error. Explanation: The Storage Toolkit has shut down
during normal shutdown of the Tivoli Enterprise
System action: Tivoli OMEGAMON XE for Storage
Monitoring Server.
continues, but the operation triggering the error does
not complete. System action: None.
Operator response: Contact IBM Software Support. Operator response: None. This is an informational
This problem information is stored in the ITMS:Engine message. This information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T697E Internal error: No NAME attribute on KS3T702W DELETE FAILED FOR RESPONSE
SUBSTITUTE DATASET [response_dsname]
Explanation: This is an internal error. Explanation: The data set used to temporarily hold
DFSMShsm or DFSMSdss command output cannot be
System action: Tivoli OMEGAMON XE for Storage
deleted.
continues, but the operation triggering the error does
not complete. System action: None.
Operator response: Contact IBM Software Support. Operator response: The data set might not actually
This problem information is stored in the ITMS:Engine exist if the Storage Toolkit ended abnormally before the
log, RKLVLOG. data set status was recorded. This information is stored
in the ITMS:Engine log, RKLVLOG.
KS3T698E Internal error: no VALUE content
KS3T703E Internal error: matching XML end tag
Explanation: This is an internal error.
not found
System action: Tivoli OMEGAMON XE for Storage
Explanation: This is an internal error.
continues, but the operation triggering the error does
not complete. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Operator response: Contact IBM Software Support.
not complete.
This problem information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T699E Internal error: First XML tag must be
STORAGE-TOOLKIT
KS3T704E Internal error: unrecognized Storage
Explanation: This is an internal error.
Toolkit command
System action: Tivoli OMEGAMON XE for Storage
Explanation: This is an internal error.
continues, but the operation triggering the error does
not complete. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Operator response: Contact IBM Software Support.
not complete.
This problem information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T700I STORAGE TOOLKIT TERMINATION
HAS COMMENCED
KS3T705E Internal error: missing Storage Toolkit
Explanation: The Storage Toolkit is shutting down
command
during normal shutdown of the Tivoli Enterprise
Monitoring Server. Explanation: This is an internal error.
System action: None. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Operator response: None. This is an informational
not complete.
message. This information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

Chapter 2. KS3 Messages 45

KS3T706E • KS3T721W

KS3T706E Unsupported DFSMShsm or DFSMSdss KS3T716E Internal error: problem deleting

request type REQUEST
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T707E Internal error: resource count per KS3T717E Internal error: problem deleting
variable is wrong REQUEST results
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T708E Internal error: No lock value in Tk_lock KS3T718I Content after start tag ignored
destructor
Explanation: Extraneous characters were found within
Explanation: This is an internal error. XML and were ignored.
System action: Tivoli OMEGAMON XE for Storage System action: None.
continues, but the operation triggering the error does
Operator response: None. This is an informational
not complete.
message. This information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support. log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T719E ---End of parse 1---
Explanation: This is an internal error.
KS3T709E Internal error: no Storage Toolkit
command to process System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support.
continues, but the operation triggering the error does
This problem information is stored in the ITMS:Engine
not complete.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3T721W STORAGE TOOLKIT ANCHOR BLOCK
log, RKLVLOG.
DESTROY ERROR STATUS CODE
[status_code] REASON CODE
KS3T714W SERVICE REQUEST [request_number] [reason_code]
COULD NOT BE CANCELED
Explanation: This is an internal error.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
System action: Tivoli OMEGAMON XE for Storage continues, but the operation triggering the error does
continues, but the operation triggering the error does not complete.
not complete.
Operator response: Contact IBM Software Support.
Operator response: Contact IBM Software Support. This problem information is stored in the ITMS:Engine
This problem information is stored in the ITMS:Engine log, RKLVLOG.
log, RKLVLOG.

46 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T722E • KS3T731E

KS3T722E Internal error: typeD record eyecatcher KS3T727E Internal error: typeF record eyecatcher
mismatch mismatch
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T723E Internal error: typeG record eyecatcher KS3T728E Internal error: typeD record but typeG
mismatch == 0
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T724E Internal error: typeF record but typeG KS3T729E Internal error: typeD record eyecatcher
== 0 mismatch
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T725E Internal error: typeF NOT first_in_chain KS3T730I [request_name] STARTED AT

[yy_mm_dd_hh_mm_ss]
Explanation: This is an internal error.
Explanation: An action request started running at the
System action: Tivoli OMEGAMON XE for Storage
specified time.
continues, but the operation triggering the error does
not complete. System action: None.
Operator response: Contact IBM Software Support. Operator response: None. This is an informational
This problem information is stored in the ITMS:Engine message. This information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

KS3T726E Internal error: typeF last_in_chain KS3T731E Internal error: unknown record type
Explanation: This is an internal error. Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does continues, but the operation triggering the error does
not complete. not complete.
Operator response: Contact IBM Software Support. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine This problem information is stored in the ITMS:Engine
log, RKLVLOG. log, RKLVLOG.

Chapter 2. KS3 Messages 47

KS3T732I • KS3T741E

KS3T732I Storage Toolkit command: KS3T737E Unsupported comparison operator

([command]) ([result_operator]) with RESULTID
Explanation: The Storage Toolkit is about to process Explanation: This is an internal error.
a command it has received.
System action: Tivoli OMEGAMON XE for Storage
System action: The Storage Toolkit processes the continues, but the operation triggering the error does
new command. not complete.
Operator response: None. This is an informational Operator response: Contact IBM Software Support.
message. This information is stored in the ITMS:Engine Or, if you have manually created a query in the Tivoli
log, RKLVLOG. Enterprise Portal that accesses the TK_RESDTL table,
ensure that the only comparison operators you use are
LT, LE, GT, GE, EQ, and NE. This information is stored
KS3T733E Could not access the Storage Toolkit
in the ITMS:Engine log, RKLVLOG.
command output data. Verify that the
RKS3DATA VSAM file exists and is
accessible to the Tivoli Enterprise KS3T738E Internal error: bad logic in
Monitoring Server address space. get_next_detail program
Verify that the RKANPAR data set
Explanation: This is an internal error.
contains a KS3ACTIN member that is
correctly coded. RETCODE = System action: Tivoli OMEGAMON XE for Storage
[return_code] continues, but the operation triggering the error does
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does
log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support.
KS3T739E Internal error: </META> end tag not
This problem information is stored in the ITMS:Engine
found where expected
log, RKLVLOG.
Explanation: This is an internal error.
KS3T735E VSAM_begin_browse ReadBegin failed System action: Tivoli OMEGAMON XE for Storage
with code ([return_code]) continues, but the operation triggering the error does
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does
log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support.
KS3T740E Internal error: </SUBSTITUTE> end tag
This problem information is stored in the ITMS:Engine
not found where expected
log, RKLVLOG.
Explanation: This is an internal error.
KS3T736E Unsupported comparison operator System action: Tivoli OMEGAMON XE for Storage
([request_operator]) with REQUESTID continues, but the operation triggering the error does
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does
log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support.
KS3T741E Internal error: </EXPAND> end tag not
Or, if you have manually created a query in the Tivoli
found where expected
Enterprise Portal that accesses the TK_RESDTL table,
ensure that the only comparison operators you use are Explanation: This is an internal error.
LT, LE, GT, GE, EQ, and NE. This information is stored
in the ITMS:Engine log, RKLVLOG. System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.

48 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T742E • KS3T751E

This problem information is stored in the ITMS:Engine continues, but the operation triggering the error does
log, RKLVLOG. not complete.
Operator response: Contact IBM Software Support.
KS3T742E TSO/E ENVIRONMENT INITIALIZATION This problem information is stored in the ITMS:Engine
FAILED: COULD NOT LOCATE KDF log, RKLVLOG.
ANCHOR BLOCK
Explanation: This is an internal error. KS3T747E Equal sign must follow the XML
attribute name
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support. continues, but the operation triggering the error does
This problem information is stored in the ITMS:Engine not complete.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3T743E CONDITION VARIABLE INITIALIZATION log, RKLVLOG.
FAILED. ERROR NUMBER
[error_number]
KS3T748E UNABLE TO ADD NEW CHECKPOINT
Explanation: This is an internal error. RECORD FOR REQUEST
[request_number]
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support. continues, but the operation triggering the error does
This problem information is stored in the ITMS:Engine not complete.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3T744E MUTEX VARIABLE INITIALIZATION log, RKLVLOG.
FAILED. ERROR NUMBER
[error_number]
KS3T749E SERVICE CHECKPOINT DATASET
Explanation: This is an internal error. STORAGE ALLOCATION ERROR
System action: Tivoli OMEGAMON XE for Storage Explanation: This is an internal error.
continues, but the operation triggering the error does
System action: Tivoli OMEGAMON XE for Storage
not complete.
continues, but the operation triggering the error does
Operator response: Contact IBM Software Support. not complete.
This problem information is stored in the ITMS:Engine
Operator response: Contact IBM Software Support.
log, RKLVLOG.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T745E Internal error: </STORAGE-TOOLKIT>
end tag not found where expected
KS3T751E STORAGE TOOLKIT COULD NOT
Explanation: This is an internal error. LOCATE ANCHOR BLOCK.
STATUS=[status_code]
System action: Tivoli OMEGAMON XE for Storage
REASON=[reason_code.]
continues, but the operation triggering the error does
not complete. Explanation: This is an internal error.
Operator response: Contact IBM Software Support. System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine continues, but the operation triggering the error does
log, RKLVLOG. not complete.
Operator response: Contact IBM Software Support.
KS3T746E Quoted string found outside XML start This problem information is stored in the ITMS:Engine
tag log, RKLVLOG.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage

Chapter 2. KS3 Messages 49

KS3T752E • KS3T762E

Operator response: Contact IBM Software Support.

KS3T752E UNABLE TO CREATE RESPONSE
This information is stored in the following log: the
DATASET [response_dsname] FOR
CT/Engine log, RKLVLOG.
REQUEST [request_number]
Explanation: This is an internal error.
KS3T759E Timed-Out waiting for Checkpoint
System action: Tivoli OMEGAMON XE for Storage dataset lock
continues, but the operation triggering the error does
Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support.
continues, but the operation triggering the error does
This problem information is stored in the ITMS:Engine
not complete.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3T753E NEW REQUEST HAS DUPLICATE KEY
log, RKLVLOG.
OF [request_number]
Explanation: This is an internal error.
KS3T760I SERVICE REQUEST [request_number]
System action: Tivoli OMEGAMON XE for Storage STARTED. [request_type]
continues, but the operation triggering the error does
Explanation: An action request submitted by a user
not complete.
has started running.
Operator response: Contact IBM Software Support.
System action: None.
This problem information is stored in the ITMS:Engine
log, RKLVLOG. Operator response: None. This is an informational
message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T755E SERVICE REQUESTS DISABLED DUE
TO CHECKPOINT FAILURE, SOURCE =
[program_id] KS3T761E UNABLE TO READ CHECKPOINT
DATASET FOR UPDATE FOR REQUEST
Explanation: This is an internal error.
[request_number], SOURCE =
System action: Tivoli OMEGAMON XE for Storage [program_id]
continues, but the operation triggering the error does
Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support.
continues, but the operation triggering the error does
Check for an earlier error message, which will contain
not complete.
additional error details. This information is stored in the
ITMS:Engine log, RKLVLOG. Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T756E UNABLE TO CANCEL REQUEST
[request_number].
STATUS=[return_code] KS3T762E UNABLE TO UPDATE CHECKPOINT
DATASET FOR REQUEST
Explanation: This is an internal error.
[request_number], SOURCE =
System action: Tivoli OMEGAMON XE for Storage [program_id]
continues, but the operation triggering the error does
Explanation: This is an internal error.
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support.
continues, but the operation triggering the error does
This problem information is stored in the ITMS:Engine
not complete.
log, RKLVLOG.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
KS3T758E Internal error: Invalid BASE64 source
log, RKLVLOG.
string ([source_string])
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.

50 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T763W • KS3T801E

Operator response: Contact IBM Software Support.

KS3T763W UNABLE TO CONSOLIDATE SERVICE
This problem information is stored in the ITMS:Engine
RESPONSES FOR REQUEST
log, RKLVLOG.
[request_number]
Explanation: This is an internal error.
KS3T768E UNABLE TO ADD NEW ’Type F’
System action: Tivoli OMEGAMON XE for Storage CHECKPOINT RECORD FOR REQUEST
continues, but the operation triggering the error does [request_number]
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does
log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support.
KS3T764E UNABLE TO DELETE CHECKPOINT
This problem information is stored in the ITMS:Engine
RECORD FOR REQUEST
log, RKLVLOG.
[request_number], SOURCE =
[program_id]
KS3T769I SERVICE REQUEST [request_number]
Explanation: This is an internal error.
COMPLETED. RC=[return_code]
System action: Tivoli OMEGAMON XE for Storage
Explanation: An action request submitted by a user
continues, but the operation triggering the error does
has completed.
not complete.
System action: None.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine Operator response: None. This is an informational
log, RKLVLOG. message. This information is stored in the ITMS:Engine
log, RKLVLOG.
KS3T765E UNABLE TO READ ADMINISTRATION
RECORD IN CHECKPOINT DATASET KS3T800E DFSMSdss Storage Toolkit Address
Space has not been configured
Explanation: This is an internal error.
correctly
System action: Tivoli OMEGAMON XE for Storage
Explanation: The SLAVESTCNAME keyword and
continues, but the operation triggering the error does
value were not found in the KS3ACTIN parameter
not complete.
member.
Operator response: Contact IBM Software Support.
System action: The Storage Toolkit is unable to run
This problem information is stored in the ITMS:Engine
DFSMSdss action requests.
log, RKLVLOG.
Operator response: Rerun the process provided by
the Installation and Configuration Assistance Tool to
KS3T766E UNABLE TO UPDATE
create a valid KS3ACTIN member. This information is
ADMINISTRATION RECORD IN
stored in the ITMS:Engine log, RKLVLOG.
CHECKPOINT DATASET
Explanation: This is an internal error.
KS3T801E SERVICE CHECKPOINT DATASET
System action: Tivoli OMEGAMON XE for Storage OWNERSHIP ACQUIRE ERROR.
continues, but the operation triggering the error does DSN=[dsname]
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage
This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does
log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support.
KS3T767E UNABLE TO ADD NEW ’Type G’
This problem information is stored in the ITMS:Engine
CHECKPOINT RECORD FOR REQUEST
log, RKLVLOG.
[request_number]
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.

Chapter 2. KS3 Messages 51

KS3T802W • KS3T891E

continues, but the operation triggering the error does

KS3T802W SERVICE CHECKPOINT DATASET
not complete.
OWNERSHIP RELEASE ERROR.
DSN=[dsname] Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
Explanation: This is an internal error.
log, RKLVLOG.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
KS3T823E SERVICE CHECKPOINT DATASET
not complete.
[request_type] REQUEST ERROR
Operator response: Contact IBM Software Support. BUFFER TOO SMALL
This problem information is stored in the ITMS:Engine
Explanation: This is an internal error.
log, RKLVLOG.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
KS3T811E SERVICE CHECKPOINT DATASET
not complete.
OPEN ERROR RETURN CODE
[status_code] REASON CODE Operator response: Contact IBM Software Support.
[reason_code] This problem information is stored in the ITMS:Engine
log, RKLVLOG.
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
KS3T824E SERVICE CHECKPOINT DATASET
continues, but the operation triggering the error does
[request_type] REQUEST ERROR
not complete.
RETURN CODE [return_code] NOT
Operator response: Contact IBM Software Support. RECOGNIZED
This problem information is stored in the ITMS:Engine
Explanation: This is an internal error.
log, RKLVLOG.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
KS3T812W SERVICE CHECKPOINT DATASET
not complete.
CLOSE ERROR INVALID HANDLE
Operator response: Contact IBM Software Support.
Explanation: This is an internal error.
This problem information is stored in the ITMS:Engine
System action: Tivoli OMEGAMON XE for Storage log, RKLVLOG.
continues, but the operation triggering the error does
not complete.
KS3T830E SERVICE CHECKPOINT DATASET
Operator response: Contact IBM Software Support. STORAGE EXHAUSTED. PUT ERROR
This problem information is stored in the ITMS:Engine VSAM RETURN CODE [rpl_rtncd]
log, RKLVLOG. VSAM REASON CODE [rpl_errcd]
Explanation: This is an internal error.
KS3T821E SERVICE CHECKPOINT DATASET
System action: Tivoli OMEGAMON XE for Storage
[request_type] REQUEST ERROR
continues, but the operation triggering the error does
INVALID HANDLE
not complete.
Explanation: This is an internal error.
Operator response: Contact IBM Software Support.
System action: Tivoli OMEGAMON XE for Storage This problem information is stored in the ITMS:Engine
continues, but the operation triggering the error does log, RKLVLOG.
not complete.
Operator response: Contact IBM Software Support. KS3T891E UNABLE TO ALLOCATE SERVICE
This problem information is stored in the ITMS:Engine RESPONSE DATASET
log, RKLVLOG. [response_dsname] RETURN CODE
[status] REASON CODE [reason_code]
INFO CODE [info_code], SOURCE =
KS3T822E SERVICE CHECKPOINT DATASET
[program_id]
[request_type] REQUEST ERROR
VSAM RETURN CODE [rpl_rtncd] Explanation: This is an internal error.
VSAM REASON CODE [rpl_errcd]
System action: Tivoli OMEGAMON XE for Storage
Explanation: This is an internal error. continues, but the operation triggering the error does
not complete.
System action: Tivoli OMEGAMON XE for Storage
Operator response: Contact IBM Software Support.

52 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KS3T892E • KS3T899E

This problem information is stored in the ITMS:Engine

log, RKLVLOG.

KS3T892E SERVICE RESPONSE DATASET OPEN

ERROR [response_dsname] [status],
SOURCE = [program_id]
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

KS3T893E SERVICE RESPONSE DATASET CLOSE

ERROR [response_dsname] [status],
SOURCE = [program_id]
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

KS3T894E INVALID SPACE VALUES

[space_specification] FOR ACTION
[request_type]
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

KS3T899E COULD NOT LOCATE STORAGE

TOOLKIT ANCHOR BLOCK
Explanation: This is an internal error.
System action: Tivoli OMEGAMON XE for Storage
continues, but the operation triggering the error does
not complete.
Operator response: Contact IBM Software Support.
This problem information is stored in the ITMS:Engine
log, RKLVLOG.

Chapter 2. KS3 Messages 53

54 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 3. KDF and KDFA Messages
This section provides OMEGAMON II for SMS messages with prefixes that range from KDF to KDFA.

User response: None. This message is informational.

KDF0116E ERROR DURING KDFSHSML SDUMPX
PROCESSING, RC= xxx, REASON= xxx
KDFAPP03 DEBUG MESSAGES ARE
Explanation: An SDUMPX macro, issued during
SUPPRESSED
abnormal termination of HSM log analysis, has failed.
The destination is the MVS system console. Explanation: The generation of internal diagnostic
messages was suppressed. The destination is the Tivoli
System action: Abnormal termination continues.
Enterprise Monitoring Server Engine log file, RKLVLOG.
User response: This error should not occur. Contact
System action: None.
IBM Software Support.
User response: None. This message is informational.
KDFAAE00 UNABLE TO OPEN FORM
AUTHORIZATION TABLE KDFAPP04 FORM LOADS WILL BE FORCED
Explanation: An update of the form authorization table Explanation: This message displays during a
failed. The destination is the Tivoli Enterprise Monitoring diagnostic routine. The destination is the Tivoli
Server Engine log file, RKLVLOG. Enterprise Monitoring Server Engine log file, RKLVLOG.
System action: The form authorization record is not System action: Product panels are reinitialized each
stored. time that they are executed by the product.
User response: Ensure that the Tivoli Enterprise User response: None. This message is informational.
Monitoring Server Engine table database cluster was
defined according to product installation instructions.
Contact IBM Software Support. KDFAPP05 AUTHORIZATION FAILURE FOR PANEL
panel_id, USER IS user_id

KDFAAE01 UNABLE TO OPEN FORM Explanation: A user tried to access a panel or product
AUTHORIZATION TABLE function, but lacked authorization. The destination is the
Tivoli Enterprise Monitoring Server Engine log file,
Explanation: An update of the form authorization table RKLVLOG.
failed. The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG. System action: The user is not granted access to the
panel or function.
System action: The form authorization record is not
stored. User response: None. This message is informational.

User response: Make sure that the Tivoli Enterprise

Monitoring Server Engine table database cluster has KDFAP0000I SERVICE PROBES INITIALIZATION
enough space and extents. If the data set has sufficient HAS BEGUN
space, contact IBM Software Support. Explanation: Initialization of the service probes has
begun. The destination is the Tivoli Enterprise
KDFAPP01 USER user_id HAS LOGGED ON Monitoring Server Engine log file, RKLVLOG.

Explanation: Logon processing for the specified user System action: The service probes continue
was completed. The destination is the Tivoli Enterprise initialization.
Monitoring Server Engine log file, RKLVLOG. User response: None.
System action: None.
User response: None. This message is informational. KDFAP0001I SERVICE PROBES ANCHOR BLOCK
HAS BEEN CREATED

KDFAPP02 USER user_id HAS LOGGED OFF Explanation: The service probes anchor block has
been created. The destination is the Tivoli Enterprise
Explanation: The specified user has logged off. The Monitoring Server Engine log file, RKLVLOG.
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG. System action: The service probes initialization
continues.
System action: None.

© Copyright IBM Corp. 2006, 2007 55

KDFAP0019S • KDFAP0023S

User response: None.

KDFAP0021S SERVICE PROBES RUNTIME
PARAMETER MEMBER KDFACTIN NOT
KDFAP0019S SERVICE PROBES ANCHOR BLOCK FOUND
CREATE ERROR STATUS CODE
Explanation: An error occurred when an attempt was
status_code REASON CODE
made to open the service probes runtime parameters
reason_code
member KDFACTIN. Member KDFACTIN cannot be
Explanation: The service probes anchor block cannot found in the RKANPARS data set. The destination is the
be created. The destination is the Tivoli Enterprise Tivoli Enterprise Monitoring Server Engine log file,
Monitoring Server Engine log file, RKLVLOG. RKLVLOG.
System action: The service probes terminate. System action: Message KDFAP0029 is issued and
the service probes terminate.
User response: This is an internal error. Contact IBM
Software Support and provide the message contents. User response: Verify that member KDFACTIN exists
in the RKANPARS data set.
KDFAP0020S SERVICE PROBES NOT INITIALIZED
KDFAP0022S SERVICE PROBES RUNTIME
Explanation: An attempt was made to use the PARAMETER MEMBER KDFACTIN
OMEGAMON II for SMS action services before they OPEN ERROR RETURN CODE
were made available. return_code
System action: OMEGAMON II continues to run, Explanation: An error occurred when an attempt was
however the action service probes cannot be executed. made to open the service probes configuration
The destination is the RKLVLOG from the Tivoli parameter member KDFACTIN. The destination is the
Enterprise Monitoring Server address space. Tivoli Enterprise Monitoring Server Engine log file,
User response: In order to run the action service RKLVLOG.
probes, the Tivoli Enterprise Monitoring Server Message Variables: Return codes are:
component must be fully initialized. If it is not, initialize
Tivoli Enterprise Monitoring Server and retry the probes. 0 Function completed successfully.
If the Tivoli Enterprise Monitoring Server component 4 Invalid handle for the persistent data store.
was initialized and already issued the message
5 Unsuccessful open.
KLVIN408 CANDLE ENGINE VERSION 170 READY,
then check the Tivoli Enterprise Monitoring Server 6 Member not found.
RKLVLOG for these informational messages:
8 Dynamic allocation failed.
KDFAP0000I SERVICE PROBES INITIALIZATION
HAS COMMENCED 9 DSNAME is greater than 44 characters.

KDFAP0001I SERVICE PROBES ANCHOR BLOCK 10 DDNAME is greater than 8 characters.

HAS BEEN CREATED System action: Message KDFAP0029 is issued and
the service probes terminate.
If these messages are found, the service probes should
be initialized. Contact IBM Software Support for further User response: If the problem persists, contact IBM
information. Software Support and provide the return code.

If these messages are not found, then the action KDFAP0023S SERVICE PROBES RUNTIME
services probes have not been initialized. To investigate PARAMETER MEMBER KDFACTIN
further: READ ERROR RETURN CODE
v Search the RKLVLOG of Tivoli Enterprise Monitoring return_code
Server for any related error messages.
Explanation: An error occurred when an attempt was
v Insure that the RKANPAR data sets for Tivoli made to read the service probes runtime parameters
Enterprise Monitoring Server are correct. member KDFACTIN. The destination is the Tivoli
v Insure that the RKANPAR data set members have Enterprise Monitoring Server Engine log file, RKLVLOG.
not been inadvertently modified. Correct any errors
Message Variables: Return codes are:
and restart Tivoli Enterprise Monitoring Server.
0 Function completed successfully.
If further assistance is necessary, contact IBM Software
Support. 2 End of file.
4 Invalid handle for the persistent data store.
5 Get unsuccessful.

56 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP0024W • KDFAP0033W

>256 An abend occurred. The value of the abend

KDFAP0029S SERVICE PROBES RUNTIME
code is determined by dividing the return code
PARAMETER COULD NOT BE READ
value by 256. If the result is less than 4096,
the abend code is issued as a result of a Explanation: The runtime parameters for
system abend. Otherwise the code is issued as OMEGAMON II for SMS services requests cannot be
a result of a user abend. The user abend code read. The destination is the Tivoli Enterprise Monitoring
can be determined by subtracting 4096 from Server Engine log file, RKLVLOG.
the result (after dividing by 256).
System action: The service probes terminate.
System action: Message KDFAP0029S is issued and
User response: Review any error messages that
the service probes terminate.
precede this one. Contact IBM Software Support if
User response: If the problem persists, contact IBM further assistance is required.
Software Support and provide the return code.
KDFAP0030I PARAMETER parameter_name HAS
KDFAP0024W KDFACTIN RUNTIME PARAMETER BEEN ASSIGNED THE VALUE
parameter_name NOT RECOGNIZED parameter_value
Explanation: An unrecognized parameter was Explanation: This message confirms the value
specified in the service probes runtime parameters assigned to the specified parameter by the runtime
member KDFACTIN. The destination is the Tivoli parameters member KDFACTIN. The destination is the
Enterprise Monitoring Server Engine log file, RKLVLOG. Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.
System action: The parameter is ignored. The service
probes continue to read the runtime parameters from System action: The service probes continue to read
the member KDFACTIN. the configuration parameters member KDFACTIN.
User response: Correct the runtime parameters User response: If the value is unsatisfactory, change
member KDFACTIN. the appropriate line in the runtime parameters member
KDFACTIN.
KDFAP0025E SERVICE PROBES RUNTIME
PARAMETER MEMBER KDFACTIN KDFAP0031W PARAMETER parameter_name WAS
CLOSE ERROR RETURN CODE return SPECIFIED PREVIOUSLY
code
Explanation: The value assigned to the specified
Explanation: A error occurred when closing the parameter has already been assigned. The destination
runtime parameters member KDFACTIN. The is the Tivoli Enterprise Monitoring Server Engine log file,
destination is the Tivoli Enterprise Monitoring Server RKLVLOG.
Engine log file, RKLVLOG.
System action: The duplicate value is ignored and the
System action: The service probes terminate. service probes continue initializing.
User response: This is an internal error. Contact IBM User response: Check the runtime parameters
Software Support. member KDFACTIN and remove the duplicate
specification of this parameter value.
KDFAP0028I SERVICE PROBES RUNTIME
PARAMETER MEMBER KDFACTIN KDFAP0033W PARAMETER parameter_name VALUE
WAS READ SUCCESSFULLY parameter_value IS TOO LONG.
MAXIMUM LENGTH IS maximum_length.
Explanation: The runtime parameters for
OMEGAMON II for SMS service requests were read Explanation: The value assigned to the specified
successfully. The destination is the Tivoli Enterprise parameter is too long. The destination is the Tivoli
Monitoring Server Engine log file, RKLVLOG. Enterprise Monitoring Server Engine log file, RKLVLOG.
System action: The service probes initialization Message Variables:
continues.
parameter_name
User response: None. The KDFACTIN keyword parameter name.
parameter_value
The incorrectly specified value of the keyword
parameter.
maximum_length
The maximum acceptable length of the value.

Chapter 3. KDF and KDFA Messages 57

KDFAP0034W • KDFAP0042W

System action: The parameter assignment is ignored. User response: Correct or remove the specified
The service probes continue initializing. runtime parameter.
User response: Correct or remove the specified
runtime parameter. KDFAP0039E RUNTIME PARAMETER
parameter_name HAS NOT BEEN
SPECIFIED AND WILL NOT BE
KDFAP0034W PARAMETER parameter_name VALUE
DEFAULTED
parameter_value IS TOO LARGE.
MAXIMUM VALUE IS maximum_value. Explanation: A valid assignment for the specified
parameter cannot be found in the runtime parameters
Explanation: The value assigned to the specified
member KDFACTIN. The parameter cannot be
parameter is too large. The destination is the Tivoli
defaulted.
Enterprise Monitoring Server Engine log file, RKLVLOG.
System action: The service probes terminate.
Message Variables:
User response: Add an assignment for the specified
parameter_name
parameter to the runtime parameters member
The KDFACTIN keyword parameter name.
KDFACTIN and restart the service probes.
parameter_value
The incorrectly specified value of the keyword
KDFAP0040S SERVICE PROBES ADMINISTRATION
parameter.
RECORD READ ERROR
maximum_length
Explanation: An attempt to read the administration
The maximum acceptable length of the value.
record from the checkpoint data set failed. The
System action: The parameter specification is administration record contains information associated
ignored. The service probes continue initializing. with service requests issued during previous executions
of the data collection (Tivoli Enterprise Monitoring
User response: Correct or remove the specified Server) address space. The destination is the Tivoli
runtime parameter. Enterprise Monitoring Server Engine log file, RKLVLOG.
System action: The service probes initialization
KDFAP0035W PARAMETER parameter_name VALUE terminates and service requests are not accepted for
parameter_value IS TOO SMALL. the remainder of the data collection (Tivoli Enterprise
MINIMUM VALUE IS minimum_value Monitoring Server) address space execution.
Explanation: The value assigned to the specified User response: Determine why the administration
parameter is too small. The destination is the Tivoli record cannot be read. If the service request checkpoint
Enterprise Monitoring Server Engine log file, RKLVLOG. data set has been corrupted, restore the data set from a
Message Variables: backup or delete and recreate the data set.

parameter_name Note: Previously issued service requests status and

The KDFACTIN keyword parameter name. response information can be lost by restoring or
parameter_value recreating the checkpoint data set.
The incorrectly specified value of the keyword
parameter. KDFAP0042W SERVICE PROBES CHECKPOINT
maximum_length DATASET OPEN
The maximum acceptable length of the value. Explanation: An attempt to open the checkpoint data
System action: The parameter specification is set for service requests failed. The service probes
ignored. The service probes continue initializing. assume that this is the first time the checkpoint data set
has been utilized. The destination is the Tivoli
User response: Correct or remove the specified Enterprise Monitoring Server Engine log file, RKLVLOG.
runtime parameter.
System action: The service probes perform a cold
start and write an administration record to the
KDFAP0036W PARAMETER parmname VALUE checkpoint data set.
parmvalue IS NOT NUMERIC
User response: None, unless the checkpoint data set
Explanation: A non-numeric value was specified for has been utilized by the service probes previously. If it
the numeric parameter. The destination is the Tivoli has been utilized previously, attempt to determine why
Enterprise Monitoring Server Engine log file, RKLVLOG. an administration record cannot be found. If necessary,
System action: The incorrectly specified value is contact IBM Software Support.
ignored. Service probes continue initializing.

58 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP0043S • KDFAP0100I

from the checkpoint data set. The destination is the

KDFAP0043S SERVICE PROBES ADMINISTRATION
Tivoli Enterprise Monitoring Server Engine log file,
RECORD NOT RECOGNIZED
RKLVLOG.
Explanation: An invalid administration record was
System action: The invalid request record is deleted.
found in the service checkpoint data set. The
The request restoration processing continues.
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG. User response: Investigate why the record was
invalid. If the problem cannot be determined, contact
System action: The service probes terminate.
IBM Software Support.
User response: Investigate why the administration
record is invalid. To permit the service probes to
KDFAP0050I number_of_requests SERVICE
initialize, restore the service checkpoint data set (to
REQUESTS HAVE BEEN RESTORED
restore any completed requests and responses), or
redefine the service checkpoint data set (to reinitialize Explanation: The specified number of service
the service probes). If necessary, contact IBM Software requests have been restored from the service
Support for assistance. checkpoint data set. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFAP0044I SERVICE PROBES ARE BEING COLD System action: The service probes continue
STARTED initialization.
Explanation: The service probes are being cold User response: None.
started. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG.
KDFAP0090I SERVICE PROBES INITIALIZATION
System action: Service probes initialization continues. HAS COMPLETED
A new administration record is written to the service
checkpoint data set and the initialization continues. Explanation: The initialization of the service probes
has completed. The destination is the Tivoli Enterprise
User response: None. Monitoring Server Engine log file, RKLVLOG.
System action: The service probes await service
KDFAP0045I SERVICE PROBES ADMINISTRATION requests.
RECORD FOUND
User response: None.
Explanation: A valid administration record was found
in the service checkpoint data set. The destination is the
Tivoli Enterprise Monitoring Server Engine log file, KDFAP0091S SERVICE PROBES INITIALIZATION
RKLVLOG. HAS FAILED

System action: The service probes are warm started. Explanation: The initialization of the service probes
failed. The destination is the Tivoli Enterprise Monitoring
User response: None. Server Engine log file, RKLVLOG.
System action: The service probes indicate they are
KDFAP0046I SERVICE PROBES ARE BEING WARM unable to process service requests.
STARTED
User response: See the previous messages for the
Explanation: The checkpoint data set for service cause of the failure.
requests has been successfully opened and checkpoint
information is used to restore service request
information. The destination is the Tivoli Enterprise KDFAP0100I SERVICE PROBES TERMINATION HAS
Monitoring Server Engine log file, RKLVLOG. BEGUN

System action: Service probes initialization continues. Explanation: The termination of the service probes
Any completed requests and responses at the time of began. The destination is the Tivoli Enterprise
the previous termination are restored. Monitoring Server Engine log file, RKLVLOG.

User response: None. System action: The service probes termination

continues.

KDFAP0047W SERVICE REQUEST RECORD FOR User response: None.

REQUEST nnn IS NOT RECOGNIZED
Explanation: An invalid service request record,
request ID nnn, was found in the service checkpoint
data set when attempting to restore service requests

Chapter 3. KDF and KDFA Messages 59

KDFAP0101I • KDFAP0115I

KDFAP0101I SERVICE PROBES TERMINATION HAS KDFAP0112I SHUTDOWN IS DELAYED UNTIL

COMPLETED SERVICES COMPLETE
Explanation: The termination of the service probes Explanation: This message is issued when the user
completed. The destination is the Tivoli Enterprise replies Y or YES to message KDFAP0110A. The
Monitoring Server Engine log file, RKLVLOG. destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG, and the MVS system
System action: The service probes terminate.
console.
User response: None.
System action: The data collection (Tivoli Enterprise
Monitoring Server) address space shutdown is delayed
KDFAP0110A OMEGAMON II for SMS SERVICES IN until all services requests in execution are completed.
PROGRESS. DELAY SHUTDOWN(Y/N)? Normal termination is resumed after service requests
have completed.
Explanation: Service requests on DASD volumes or
data sets are currently in progress. The console User response: None.
operator must reply Y to delay the shutdown of the data
collection (Tivoli Enterprise Monitoring Server) address
KDFAP0113I INVALID REPLY. Y=DELAY SHUTDOWN
space, or N to continue with immediate shutdown.
N=IMMEDIATE SHUTDOWN
System action: The address space shutdown is
Explanation: This message is issued when an invalid
suspended until the console operator replies to the
reply is received for message KDFAP0110A. The
message.
destination is the Tivoli Enterprise Monitoring Server
User response: Engine log file, RKLVLOG, and the MVS system
v Reply Y or YES to delay the shutdown of the data console.
collection (Tivoli Enterprise Monitoring Server) System action: The console operator is reprompted
address space until active service requests are for a decision to delay the data collection (Tivoli
completed. Enterprise Monitoring Server) address space shutdown
v Reply N or NO to proceed with an immediate by reissuing message KDFAP0110A.
shutdown of the data collection (Tivoli Enterprise
User response: Reply Y or N to message
Monitoring Server) address space.
KDFAP0110A.
v Any other reply causes the WTOR message to be
reissued.
KDFAP0114W SERVICE REQUEST reqid COULD
Note: Proceeding with the shutdown can cause NOT BE CANCELED
damage to DASD volumes and data sets Explanation: The service probes attempted to cancel
currently being processed by the address space. an action request when preparing for termination;
If a NO reply is issued, use the data logged in however, the attempt failed. This should not have any
the MSG System Log and the RKLVLOG of the significant impact on the service probes. The destination
data collection (Tivoli Enterprise Monitoring is the Tivoli Enterprise Monitoring Server Engine log file,
Server) address space to review the service RKLVLOG, and the MVS system console.
requests in progress at the time of shutdown.
Refer to messages KDFAP120I and KDFAP130I. Message Variables:
reqid Identifies the ID number of the service request
KDFAP0111I ADDRESS SPACE WILL BE that cannot be cancelled.
SHUTDOWN IMMEDIATELY System action: The service probes continue to
Explanation: This message is issued when the reply terminate.
to message KDFAP0110A was N or NO. The destination User response: None.
is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG, and the MVS system console.
KDFAP0115I OMEGAMON II SMS SERVICES
System action: The data collection address space COMPLETED
terminates immediately, abnormally terminating (ABEND
SA03) the current services in progress. Explanation: This message follows message
KDFAP0112I and indicates that the outstanding service
User response: None. requests causing the data collection (Tivoli Enterprise
Monitoring Server) address space shutdown delay have
completed. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG, and the
MVS system console.

60 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP0120I • KDFAP0900E

System action: The service probes termination address space is suspended. WTOR message
completes and the data collection (Tivoli Enterprise KDFS0110A is issued to prompt the console operator to
Monitoring Server) address space continues with delay the shutdown until service requests on DASD
shutdown processing. volumes and data sets complete.
User response: None. User response: If an immediate shutdown is
requested, or the address space is cancelled while the
service requests were in progress, integrity of the DASD
KDFAP0120I SERVICE IN PROGRESS AT
volume or data sets should be reviewed. If necessary,
SHUTDOWN
manual recovery processing should be taken to restore
Explanation: This message precedes the list of active the DASD volume or data sets. The recovery
services requests at data collection (Tivoli Enterprise processing depends on the service in progress:
Monitoring Server) address space shutdown. Message
Any HSM service requests
KDFS0130S follows this message and lists the service
No recovery processing required.
requests in progress. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG, DFDSS Compress Dataset
and the MVS system console. If the data set is damaged, recover the data
set from the HSM BACKDS taken immediately
System action: See message KDFAP0130I.
before compress processing was initiated.
User response: See message KDFAP0130I.
DFDSS Defragment Volume
DADSM message IEC602 is issued if a data
KDFAP0121W SERVICE PROBES ANCHOR BLOCK set is accessed on a volume where DFDSS
DESTROY ERROR STATUS CODE DEFRAG did not complete. Dataset
status_code REASON CODE SYS.DFDSS.DEFRAG.xxxxxx.volser.DUMMY
reason_code is allocated on the volume by DFDSS and
remains on the volume if the defragmentation
Explanation: The service probes anchor block cannot was interrupted. Resubmit a DFDSS DEFRAG
be destroyed. This message should not have any request on the volume to correct the problem.
significant impact on the service probes. The destination
is the Tivoli Enterprise Monitoring Server Engine log file,
Note: OMEGAMON II also issues an HSM
RKLVLOG.
incremental backup before initiating
System action: Message KDFAP0100 is issued and defragment volume processing. If the
the service probes terminate. IEC602 message is not corrected by
resubmitting the defragmentation
User response: None. request, or if immediate access to data
sets on the volume are required, an
KDFAP0130I service_request ON volser_or_dataset HSM recovery request can be used to
name STARTED AT yy/mm/dd hh:mm:ss restore individual data sets on the
volume, or a HSM dump restore and
Explanation: This message follows message incremental forward recovery can be
KDFAP0120I and is issued for each service request in used to restore the entire volume.
progress at the time of data collection (Tivoli Enterprise
Monitoring Server) address space shutdown. All other DFDSS service requests
No recovery processing required.
Message Variables:
service_request KDFAP0900E DFDSS ACTION REQUEST ADDRESS
The description of the service request in SPACE HAS NOT BEEN CONFIGURED
progress. REFER TO CANDLE DOCUMENT
volser_or_dataset name DF99-4853, DSS VSCR, FOR
The volume serial number of the DASD volume CONFIGURATION INFORMATION
or name of the data set being processed by Explanation: The SLAVESTCNAME parameter was
the service request. not found in the KDFACTIN member of data set
yy/mm/dd rhilev.RKANPAR. This parameter is required to execute
The date at which the service request started DFDSS action requests. The destination is the Tivoli
execution. Enterprise Monitoring Server Engine log file, RKLVLOG.

hh:mm:ss System action: The service probe initialization fails.

The time at which the service request started All data set and volume action probes are suspended
execution. for further execution.

System action: Termination processing for the User response: None.

Chapter 3. KDF and KDFA Messages 61

KDFAP1110E • KDFAP1291E

KDFAP1110E UNABLE TO ALLOCATE SERVICE KDFAP1130E UNABLE TO ALLOCATE INPUT VIO

RESPONSE DATASET. RC= p0 DATASET. RC= p0.
Explanation: The routine called to satisfy a service Explanation: The routine called to satisfy a service
request cannot allocate the service response data set to request cannot allocate a temporary VIO data set for
save service response text. Data set allocation cannot control statements read by utility programs. VIO data
be satisfied for the address space, or installation exits set allocation cannot be satisfied for the address space,
prevent the allocation of the data set. or installation exits prevent the allocation of the VIO
data set.
The most likely cause of the problem is that the
response data set was deleted or is currently allocated Message Variables:
by another address space.
p0 Specifies the return code issued by the TSO/E
Message Variables: ALLOCATE command.
p0 Specifies the return code issued by the TSO/E System action: The service request fails and a -5000
ALLOCATE command. is set for the return code of the request.
System action: The service request fails and a -3000 User response: Ensure that the data collection (Tivoli
is set for the return code of the request. Enterprise Monitoring Server) address space is allowed
to allocate temporary data sets to UNIT (VIO). Also
User response: Determine why the data set cannot
ensure that VIO data set allocation is configured
be allocated. If the problem cannot be determined,
properly for the system. Review the appropriate
contact IBM Software Support for assistance. Review
destination:
the appropriate destination:
OMEGAMON II for SMS
OMEGAMON II for SMS
The Tivoli Enterprise Monitoring Server
The Tivoli Enterprise Monitoring Server
address space log file, RKLVLOG.
address space log file, RKLVLOG.
All other products
All other products
The data collection (Tivoli Enterprise
The data collection (Tivoli Enterprise
Monitoring Server) address space SYSTSPRT
Monitoring Server) address space SYSTSPRT
output file.
output file.

KDFAP1140I NO ADDITIONAL INFORMATION IS

KDFAP1120E UNABLE TO WRITE TO SERVICE
AVAILABLE
RESPONSE DATASET. RC= p0
Explanation: The routine called to satisfy a service
Explanation: An attempt to write response text to a
request did not receive any response text for the
service response data set failed. The most likely cause
request.
of this error is that the data collection (Tivoli Enterprise
Monitoring Server) address space does not write System action: The service request completes
security access to the response data set, or an I/O error normally.
occurred on the volume in which the data set is located.
User response: Review the appropriate destination:
Message Variables:
OMEGAMON II for SMS
p0 Specifies the return code issued by the REXX The Tivoli Enterprise Monitoring Server
EXECIO command. address space log file, RKLVLOG.
System action: The current request for service fails All other products
and -4000 is set for the return code of the request. The data collection (Tivoli Enterprise
Monitoring Server) address space SYSTSPRT
User response: Determine why the write operation
output file.
failed. If the problem cannot be determined, contact IBM
Software Support for assistance. Review the appropriate
destination: KDFAP1291E UNABLE TO ISSUE p0
OMEGAMON II for SMS Explanation: An attempt to issue the specified
The Tivoli Enterprise Monitoring Server message using the TSO/E PUTLINE service failed. The
address space log file, RKLVLOG. destination is the MVS control console (WTO).
All other products System action: An abend U0910 occurs after this
The data collection (Tivoli Enterprise message is issued and a dump is taken.
Monitoring Server) address space SYSTSPRT
User response: See the description of the message
output file.
that cannot be issued. To determine why the TSO/E

62 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP1292E • KDFAP1440E

PUTLINE service failed, contact IBM Software Support reason Specifies the reason code from the TSO/E
providing this message and the message that cannot be services environment initialization routine,
issued. Also, have the abend U0910 dump available. IKJTSOEV.
This message should never be issued. It is issued only
abend Specifies the abend code from the TSO/E
if the TSO/E PUTLINE service responds with a return
services environment initialization routine,
code other than 0, 12, or 16. No other return codes
IKJTSOEV.
should be applicable in the KDFIRACT environment.
System action: Service request processing is disabled
for the remainder of the Tivoli Enterprise Monitoring
KDFAP1292E UNABLE TO ISSUE p0 - INVALID
Server (data collection) address space execution, and
PARAMETERS
OMEGAMON II for SMS service requests are not
Explanation: An attempt to issue the specified accepted.
message using the TSO/E PUTLINE service failed.
User response: Using the return code, reason code,
TSO/E indicated the associated parameters were
and abend code displayed, determine why the TSO/E
invalid. The destination is the MVS control console
environment cannot be initialized. Correct the error and
(WTO).
restart the Tivoli Enterprise Monitoring Server address
System action: An abend U0920 occurs after this space to enable service request processing. If the
message is issued and a dump is taken. cause of the initialization failure cannot be determined,
contact IBM Software Support for assistance. The
User response: See the description of the message
destination is the Tivoli Enterprise Monitoring Server
that cannot be issued. To determine why the TSO/E
Engine log file, RKLVLOG.
PUTLINE service failed, contact IBM Software Support
providing this message and the message that cannot be
issued. Also, have the abend U0920 dump available. KDFAP1430E CONDITION VARIABLE
This message is issued when the TSO/E PUTLINE INITIALIZATION FAILED. ERROR
service provides return code 12. The dump should be NUMBER nnn.
examined to determine why the parameter list was
Explanation: An attempt to initialize a POSIX
invalid.
condition variable used for service requests completion
notification has failed.
KDFAP1293E UNABLE TO ISSUE p0 -
Message Variables:
INSUFFICIENT STORAGE
nnn Specifies the error number set by the POSIX
Explanation: An attempt to issue the specified
pthread_cond_init initialization routine.
message failed. TSO/E indicated that there was
insufficient storage to issue the message. The System action: Service request processing is disabled
destination is the MVS control console (WTO). for the remainder of the Tivoli Enterprise Monitoring
Server (data collection) address space execution, and
System action: The system action depends on the
OMEGAMON II for SMS service requests are not
text of the message that cannot be issued. Refer to the
accepted.
system action of the message.
User response: Contact IBM Software Support for
User response: See the description of the message
assistance. The destination is the Tivoli Enterprise
that cannot be issued. If this message is issued often,
Monitoring Server Engine log file, RKLVLOG.
determine why storage was insufficient to issue the
message.
KDFAP1440E MUTEX VARIABLE INITIALIZATION
FAILED. ERROR NUMBER nnn.
KDFAP1420E TSO/E ENVIRONMENT
INITIALIZATION FAILED. RETURN Explanation: An attempt to initialize a POSIX mutual
CODE rc REASON CODE reason exclusion variable used for service request serialization
ABEND CODE abend. locks has failed.
Explanation: An attempt to initialize the TSO/E Message Variables:
environment for processing of OMEGAMON II for SMS
service requests failed. nnn Specifies the error number set by the POSIX
pthread_cond_init initialization routine.
Message Variables:
System action: Service request processing is disabled
rc Specifies the return code from the TSO/E for the remainder of the Tivoli Enterprise Monitoring
services environment initialization routine, Server (data collection) address space execution, and
IKJTSOEV. OMEGAMON II for SMS service requests are not
accepted.
User response: Contact IBM Software Support for

Chapter 3. KDF and KDFA Messages 63

KDFAP1450E • KDFAP1550S

assistance. The destination is the Tivoli Enterprise data set create, delete, read, and write access to
Monitoring Server Engine log file, RKLVLOG. service response data sets. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFAP1450E UNABLE TO VERIFY PROPER
FORMAT FOR MODULE KDFCRAET KDFAP1530E NEW REQUEST HAS DUPLICATE
KEY OF reqid
Explanation: Module KDFCRAET was loaded but the
data found in the module was not in the format Explanation: The service probes cannot accept a new
expected by the service probes. a service request because a previously issued request
uses the same internal request identifier.
System action: Service request initialization fails, and
OMEGAMON II for SMS service requests are not Message Variables:
accepted for the remainder of the Tivoli Enterprise
reqid Identifies the ID number of the failed service
Monitoring Server (data collection) address space
request.
execution.
System action: The service probes request fails and
User response: This is an internal error. Verify that
returns an error status to the application program
the KDFCRAET module was installed correctly and
making the request.
placed in an APF-authorized library. Contact IBM
Software Support for further assistance. The destination User response: Ensure that the OMEGAMON II
is the Tivoli Enterprise Monitoring Server Engine log file, checkpoint data set has not been overwritten. If the
RKLVLOG. checkpoint data set is damaged, the data set can be
restored to its original state from a data set backup of
the VSAM cluster, or it can be deleted and recreated.
KDFAP1510E SERVICE PROBES COULD LOCATE
Restoration or recreation can cause the loss of service
ANCHOR BLOCK. STATUS=status
requests that have checkpointed. This problem can
REASON=reason.
occur because a large number of service requests were
Explanation: This message indicates that the service issued and never deleted. If a large number of
probes which attempt to locate the anchor block unwanted service requests are retained in the
containing administrative control data have failed. checkpoint data set, issue delete requests to clear the
unwanted requests and allow request identifiers to be
Message Variables:
reused. The destination is the Tivoli Enterprise
status Specifies the return code returned by the Monitoring Server Engine log file, RKLVLOG.
anchor locate service.
reason Specifies the reason code returned by the KDFAP1550S SERVICE REQUESTS DISABLED DUE
anchor locate service routine. TO CHECKPOINT FAILURE

System action: The service probes request fails and Explanation: This message is issued after a fatal
returns an error status to the application program checkpoint failure has been detected. Refer to
making the request. messages issued prior to this message to determine the
exact cause of the failure.
User response: This is an internal error. Contact IBM
Software Support and provide the message. The System action: The service request being processed
destination is the Tivoli Enterprise Monitoring Server fails and an error return code is set for the request.
Engine log file, RKLVLOG. Additionally, service request processing is disabled and
no new service requests are accepted.
KDFAP1520E UNABLE TO CREATE RESPONSE User response: Ensure that the OMEGAMON II
DATASET dsname FOR REQUEST reqid checkpoint data set has not been overwritten and free
space has not been exhausted. If the checkpoint data
Explanation: The service probes cannot create and set is damaged, the data set can be restored to its
catalog the specified service response data set for original state from a data set backup of the VSAM
service request reqid. cluster, or it can be deleted and recreated. Restoration
System action: The service probes request fails and can cause the loss of service requests that were
returns an error status to the application program checkpointed after the backup was taken. This problem
making the request. can occur because a large number of service requests
were issued and never deleted. If a large number of
User response: Ensure that the OMEGAMON II unwanted service requests are retained in the
service request parameters specified in the KDFACTIN checkpoint data set, issue delete requests to allow
member of the runtime parameters data set has been storage in the checkpoint data set to be reused.
configured properly. Also verify that the security access
rights have been granted to the data collection (Tivoli
Enterprise Monitoring Server) address space to allow

64 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP1560E • KDFAP1630W

delete operations on unwanted service requests to allow

KDFAP1560E UNABLE TO CANCEL REQUEST reqid
storage in the checkpoint data set to be reused. The
STATUS= status
destination is the Tivoli Enterprise Monitoring Server
Explanation: This message is issued when an attempt Engine log file, RKLVLOG.
to cancel a service request that is awaiting execution or
is currently executing, fails. This message is normally
KDFAP1610E UNABLE TO READ CHECKPOINT
issued during the shutdown of the data collection (Tivoli
DATASET FOR UPDATE FOR REQUEST
Enterprise Monitoring Server) address space when
reqid
service requests are either awaiting execution or
executing. Service requests awaiting execution are Explanation: This message indicates that the service
restored upon restart of the data collection (Tivoli probes cannot recall the existing service request reqid
Enterprise Monitoring Server) address space, if from the checkpoint data set.
possible. This message can also be issued in response
to a delete operation on service requests that are Message Variables:
awaiting execution. reqid Identifies the ID number of the service request.
Message Variables: System action: The service request fails with a
reqid Identifies the ID number of the service request nonzero return code. The time of the failure is noted,
that cannot be cancelled. and a negative return code value for the request is set.

status Identifies the error status code returned by User response: This is an internal error. If the cause
thread cancellation service routine. of the error cannot be determined, contact IBM Software
Support. The destination is the Tivoli Enterprise
System action: An error code is returned if the Monitoring Server Engine log file, RKLVLOG.
cancellation failure occurred as a result of a delete
operation. Otherwise data collection (Tivoli Enterprise
Monitoring Server) address space termination KDFAP1620E UNABLE TO UPDATE CHECKPOINT
processing continues. DATASET FOR REQUEST reqid

User response: If this message is issued in response Explanation: This message indicates that the service
to a delete action against a service request awaiting probes cannot update the existing service request reqid
execution, contact IBM Software Support for assistance. in the checkpoint data set.
The destination is the Tivoli Enterprise Monitoring Message Variables:
Server Engine log file, RKLVLOG.
reqid Identifies the ID number of the service request.

KDFAP1600I SERVICE REQUEST reqid STARTED. System action: The service request fails with a
action ON objclass object. nonzero return code; the time of the failure is noted,
and a negative return code value for the request is set.
Explanation: This message indicates that a service
request has begun execution. User response: This is an internal error. If the cause
of the error cannot be determined, contact IBM Software
Message Variables: Support. The destination is the Tivoli Enterprise
reqid Identifies the ID number of the service request. Monitoring Server Engine log file, RKLVLOG.

action Describes the action request to be executed.

KDFAP1630W UNABLE TO CONSOLIDATE
objclass RESPONSES FOR REQUEST reqid
Indicates the type of service to be executed.
Possible values are DASD Volume or Dataset. Explanation: This message indicates that the service
probes cannot copy text from a response data set into
object Indicates the VOLSER of the DASD volume if the checkpoint data set. Text temporarily stored in
the objclass value was DASD Volume, or the response data sets is copied to the checkpoint data set
data set name if the objclass value was following completion of each request. Response data
Dataset. sets are only deleted if the text is successfully copied to
the checkpoint data set. The most likely causes of the
System action: The service request completes
failure are:
normally but the cataloged data set containing the
response text is kept until the text can be successfully v Data collection address space shutdown was in
copied to the checkpoint data set. The service probes progress during an attempt to consolidate the
attempt to copy the response text upon the next restart response text.
of the data collection (Tivoli Enterprise Monitoring v Lack of sufficient free storage in the checkpoint data
Server) address space. set to receive the response text.
User response: If the checkpoint data set is full, issue Message Variables:

Chapter 3. KDF and KDFA Messages 65

KDFAP1640E • KDFAP1690I

reqid Identifies the ID number of the service request.

KDFAP1660E UNABLE TO UPDATE
System action: The service request completes ADMINSTRATION RECORD IN
normally but the cataloged data set containing the CHECKPOINT DATASET.
response text is kept until the text can be successfully
Explanation: The service probes cannot update the
copied to the checkpoint data set. The service probes
administration record in the checkpoint data set.
attempt to copy the response text upon the next restart
of the data collection (Tivoli Enterprise Monitoring System action: The service request fails with a
Server) address space. nonzero return code. The time of the failure is noted,
and a negative return code value for the request is set.
User response: If the checkpoint data set is full, issue
delete operations on unwanted service requests to allow User response: This is an internal error. If the cause
storage in the checkpoint data set to be reused. The of the error cannot be determined, contact IBM Software
destination is the Tivoli Enterprise Monitoring Server Support. The destination is the Tivoli Enterprise
Engine log file, RKLVLOG. Monitoring Server Engine log file, RKLVLOG.

KDFAP1640E UNABLE TO DELETE CHECKPOINT KDFAP1670E UNABLE TO ADD NEW CHECKPOINT

RECORD FOR REQUEST reqid RECORD FOR REQUEST reqid
Explanation: The service probes cannot delete the Explanation: The service probes cannot add a record
existing service request reqid in the checkpoint data set. to the checkpoint data set for a new service request.
The most likely cause of the failure is lack of sufficient
Message Variables:
free storage in the checkpoint data set to receive the
reqid Identifies the ID number of the service request. request record.

System action: The deletion of the request fails and a Message Variables:
return code is issued indicating that the delete failure is
reqid Identifies the ID number of the service request.
returned to the application program issuing the delete.
System action: The service request fails with a
User response: This is an internal error. Contact IBM
nonzero return code. The time of the failure is noted,
Software Support. The destination is the Tivoli
and a negative return code value for the request is set.
Enterprise Monitoring Server Engine log file, RKLVLOG.
User response: Determine why the checkpoint data
set cannot be updated. If the checkpoint data set is full,
KDFAP1645E TIMED-OUT WAITING FOR
issue delete operations on unwanted service requests
CHECKPOINT DATASET LOCK
to allow storage in the checkpoint data set to be reused.
(KDFRRAQD)
If the cause of the error cannot be determined, contact
Explanation: The service probes cannot obtain the IBM Software Support for further assistance. The
checkpoint data set lock. destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
System action: The request fails. A return code is
issued to the application making the request.
KDFAP1690I SERVICE REQUEST reqid COMPLETED.
User response: This is an internal error. Contact IBM RC=rc
Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG. Explanation: This message indicates that service
request reqid has completed execution.
KDFAP1650E UNABLE TO READ ADMINISTRATION Message Variables:
RECORD FROM CHECKPOINT
reqid Identifies the ID number of the service request.
DATASET.
rc Identifies the return code value set by the
Explanation: This message indicates that the service
service provider routine. This value is identical
probes cannot recall the administration record from the
to the value displayed on service request
checkpoint data set.
details panels.
System action: The service request fails with a
System action: The next service request in queue (if
nonzero return code time of the failure is noted, and a
any) is executed.
negative return code value for the request is set.
User response: The service request status and detail
User response: This is an internal error. If the cause
panels can be used to review the success or failure of
of the error cannot be determined, contact IBM Software
the completed service request. If the record of the
Support. The destination is the Tivoli Enterprise
service request is no longer needed, a delete operation
Monitoring Server Engine log file, RKLVLOG.
should be issued on the service request to allow
storage in the checkpoint data set to be reused. The

66 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP1701E • KDFAP1702E

destination is the Tivoli Enterprise Monitoring Server return_code

Engine log file, RKLVLOG. Identifies the return code value set by the
service provider routine. This value is identical
to the value displayed on service request
KDFAP1701E UNABLE TO ALLOCATE SERVICE
details panels.
RESPONSE DATASET dataset_name
RETURN CODE return_code REASON reason_code
CODE reason_code INFO CODE The SVC 99 error code for the allocation
info_code request.
Explanation: An attempt to dynamically allocate the info_code
specified service response data set failed. The service The SVC 99 information code for the allocation
probes are unable to copy a service response from a request.
service response data set. The return code, reason
System action: The service probes do not attempt to
code, info code, and message text provide detailed
copy the service response again during this execution of
information regarding the error.
the service probes.
Message Variables:
User response: Determine why the dynamic allocation
datatset_name failed. The return code, reason code, and info code are
The data set name of the response data set. documented in the MVS/ESA Authorized Assembler
Programming Guide. If necessary, contact IBM Software
return_code
Support and provide the message contents. The
Identifies the return code value set by the
destination is the Tivoli Enterprise Monitoring Server
service provider routine. This value is identical
Engine log file, RKLVLOG.
to the value displayed on service request
details panels.
KDFAP1702E SERVICE RESPONSE DATASET
reason_code
OPEN ERROR dataset_name reason
The SVC 99 error code for the allocation
request. Explanation: An attempt to open the specified service
response data set failed.
info_code
The SVC 99 information code for the allocation Message Variables:
request.
datatset_name
System action: The service probes do not attempt to The data set name of the response data set.
copy the service response again during this execution of
reason Reason code describing the open failure:
the service probes.
4 Invalid DD name.
User response: Determine why the dynamic allocation
failed. The return code, reason code, and info code are 8 Invalid record format.
documented in the MVS/ESA™ Authorized Assembler
Programming Guide. If necessary, contact IBM Software 12 Invalid organization.
Support and provide the message contents. The 16 RDJFCB macro call failed.
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG. 20 Open process failed.
24 Resource creation failed.
KDFAP1701I UNABLE TO ALLOCATE SERVICE 52 OBTAIN macro call failed.
RESPONSE DATASET dataset_name
RETURN CODE return_code REASON 256 System abend code abend_code.
CODE reason_code INFO CODE System action: Unpredictable, as the system action is
info_code dependent upon the action that failed.
Explanation: An attempt to dynamically allocate the User response: Investigate the problem. See the
specified service response data set failed. The service following message. If appropriate, contact the IBM
probes are unable to copy a service response from a Software Support and provide the message. The
service response data set. The return code, reason destination is the Tivoli Enterprise Monitoring Server
code, info code, and message text provide detailed Engine log file, RKLVLOG.
information regarding the error.
Message Variables:
datatset_name
The data set name of the response data set.

Chapter 3. KDF and KDFA Messages 67

KDFAP1703E • KDFAP1811S

Monitoring Server address space, perhaps on another

KDFAP1703E SERVICE RESPONSE DATASET GET
system in a shared DASD environment, owns the
ERROR dataset_name reason
service checkpoint data set, thus preventing this
Explanation: An attempt to get a record from the address space from having exclusive control.
specified service response data set failed.
Message Variables:
Message Variables:
dsn Specifies the name of the checkpoint data set.
datatset_name
System action: The service probes terminate.
The data set name of the response data set.
User response: Identify the other Tivoli Enterprise
reason Reason code describing the open failure:
Monitoring Server address space that owns the
4 Invalid DD name. checkpoint data set specified in the KDFACTIN runtime
parameter member. Ensure that no two Tivoli Enterprise
8 Invalid record format.
Monitoring Server address spaces use the same
12 Invalid organization. checkpoint data set. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
16 RDJFCB macro call failed.
20 Open process failed. KDFAP1802W SERVICE CHECKPOINT DATASET
24 Resource creation failed. OWNERSHIP RELEASE ERROR.

52 OBTAIN macro call failed. Explanation: A request to release the service

checkpoint data set ownership failed.
256 System abend code abend_code.
System action: The service probes continue
System action: Unpredictable, as the system action is execution. This error should not have any significant
dependent upon the action that failed. impact on the service probes.
User response: Investigate the problem. See the User response: The destination is the Tivoli
following message. If appropriate, contact IBM Software Enterprise Monitoring Server Engine log file, RKLVLOG.
Support and provide the message. The destination is
the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG. KDFAP1811S SERVICE CHECKPOINT DATASET
OPEN ERROR RETURN CODE
return_code REASON CODE
KDFAP1704E INVALID VALUES FOR SPACE space reason_code.
FOR ACTION action
Explanation: The request to open the service
Explanation: An invalid action effector table entry for checkpoint data set failed.
the SPACEAE column was found.
Message Variables:
Message Variables:
return_code
space The invalid values specified in the SPACEAE Identifies the return code value set by the
column of the action effector table service provider routine. This value is identical
(OMSMS.ACTEFTRTAB). to the value displayed on service request
action The value of the ACTNAMEAE column in the details panels.
row of the action effector table reason_code
(OMSMS.ACTEFTRTAB). The SVC 99 error code for the allocation
System action: The action request is not accepted request.
and an INSERT return code is set for the request. System action: The service probes terminate.
User response: This is an internal processing error. User response: Determine why the open request
Contact IBM Software Support and provide the failed. The return code and reason code are from a
message. The destination is the Tivoli Enterprise VSAM OPEN request and are documented in
Monitoring Server Engine log file, RKLVLOG. MVS/DFP™ Macro Instructions for Data Sets. If
necessary, contact IBM Software Support. The
KDFAP1801S SERVICE CHECKPOINT DATASET destination is the Tivoli Enterprise Monitoring Server
OWNERSHIP ACQUIRE FAILED. Engine log file, RKLVLOG.
DSN=dsn.
Explanation: The service probes claimed ownership of
the service checkpoint data set but the request failed.
This message indicates another Tivoli Enterprise

68 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFAP1812W • KDFAP1823E

v BUFFER FLUSH
KDFAP1812W SERVICE CHECKPOINT DATASET
CLOSE ERROR INVALID HANDLE v ERASE
v GET
Explanation: The request to close the service
checkpoint data set failed. v GET LOCK
v POINT
System action: The service probes continue
execution. The most likely cause of this error is a failure v PUT
to open the checkpoint data set. This error should not v START
have any significant impact on the service probes. v END
User response: Refer to previously issued messages return code
associated with possible open or dynamic data set Identifies the VSAM return code issued by the
allocation errors. The destination is the Tivoli Enterprise checkpoint data set I/O routine.
Monitoring Server Engine log file, RKLVLOG.
reason code
Identifies the VSAM reason code issued by the
KDFAP1821E SERVICE CHECKPOINT DATASET checkpoint data set I/O routine.
reqtype REQUEST ERROR INVALID
HANDLE System action: Unpredictable, as the system action is
dependent upon the action that failed.
Explanation: A service checkpoint data set request
failed because an invalid buffer was used. This is an User response: Investigate the cause of the error.
internal error. The return code and reason code are from the VSAM
request and are documented in MVS/DFP Macro
Message Variables: Instructions for Data Sets. The destination is the Tivoli
reqtype Enterprise Monitoring Server Engine log file, RKLVLOG.
Identifies the type of the I/O request. Values
are: KDFAP1823E SERVICE CHECKPOINT DATASET
v ACQUIRE BUFFER reqtype REQUEST ERROR BUFFER
v BUFFER FLUSH TOO SMALL
v ERASE Explanation: The request to get a service checkpoint
v GET data set record failed because the buffer provided to
receive the record was too small. This is an internal
v GET LOCK
logic error.
v POINT
Message Variables:
v PUT
v START reqtype
Identifies the type of the I/O request. Values
v END
are:
System action: Unpredictable, as the system action is v ACQUIRE BUFFER
dependent upon the action that failed.
v BUFFER FLUSH
User response: This is an internal error. Contact IBM v ERASE
Software Support and provide the message contents.
v GET
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG. v GET LOCK
v POINT
KDFAP1822E SERVICE CHECKPOINT DATASET v PUT
reqtype REQUEST ERROR VSAM v START
RETURN CODE return code VSAM v END
REASON CODE reason code
System action: Unpredictable, as the system action is
Explanation: A service checkpoint data set request dependent upon the type of record being read. The
failed. VSAM provided a return code and a reason service probes continue processing, if possible. Other
code. messages issued with this message can provide further
Message Variables: details.

reqtype User response: This is an internal error. Contact IBM

Identifies the type of the I/O request. Values Software Support and provide the message. The
are: destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
v ACQUIRE BUFFER

Chapter 3. KDF and KDFA Messages 69

KDFAP1824E • KDFAUT01

space has not been exhausted. If the checkpoint data

KDFAP1824E SERVICE CHECKPOINT DATASET
set is damaged, the data set can be restored to its
reqtype REQUEST ERROR RETURN
original state from a data set backup of the VSAM
CODE rc NOT RECOGNIZED
cluster, or it can be deleted and recreated.
Explanation: An I/O request to the service checkpoint
Restoration can cause the loss of service requests that
data set failed. This is an internal logic error.
were checkpointed after the backup was taken. This
Message Variables: problem can also be caused by the unlikely event that a
large number of service requests have been issued and
reqtype
never deleted. If a large number of unwanted service
Identifies the type of the I/O request. Values
requests are retained in the checkpoint data set, issue
are:
delete requests to allow storage in the checkpoint data
v ACQUIRE BUFFER set to be reused.
v BUFFER FLUSH
The TSO LISTC command, the IDCAMS LISTC
v ERASE command, or OMEGAMON II can be used to review the
v GET checkpoint data set disk utilization. If more storage is
v GET LOCK required, the checkpoint data set should be reallocated
using larger primary and secondary allocation
v POINT parameters. Contact IBM Software Support for further
v PUT assistance. The destination is the Tivoli Enterprise
v START Monitoring Server Engine log file, RKLVLOG.
v END
KDFAPT33 OMEGAMON II FOR SMS IS UNABLE
rc Identifies the return code issued by the VSAM
TO CONNECT TO CT/DS®
I/O service.
Explanation: The OMEGAMON II for SMS address
System action: Unpredictable, as the system action is
space is unable to communicate with the Tivoli
dependent upon the type of record being read. The
Enterprise Monitoring Server address space.
service probes continue processing, if possible. Other
messages issued with this message can provide further System action: None.
details.
User response: Contact IBM Software Support.
User response: This is an internal error. Contact IBM
Software Support and provide the message. The
destination is the Tivoli Enterprise Monitoring Server KDFAUT00 - SUPER USER HAS LOGGED ON
Engine log file, RKLVLOG. Explanation: The special user ID CANSUPER was
used to gain access to the product.
KDFAP1830E SERVICE CHECKPOINT DATASET System action: The user logging on with the
STORAGE EXHAUSTED. PUT CANSUPER ID gains access to all product functions.
REQUEST ERROR. VSAM RETURN
CODE return code VSAM REASON User response: None. This message is informational.
CODE reason code. See the OMEGAMON II for SMS User’s Guide for more
information about CANSUPER. The destination is the
Explanation: A PUT I/O request to the service Tivoli Enterprise Monitoring Server Engine log file,
checkpoint data set failed. A secondary allocation RKLVLOG.
cannot be acquired for the checkpoint data set and no
free storage can be found in the VSAM cluster.
KDFAUT01 ATTEMPT TO LOGON AS SUPER USER
Message Variables: FAILED
return code Explanation: An attempt was made to log onto the
The VSAM return code issued by the product using the special administrative logon ID
checkpoint data set I/O routine. CANSUPER. An incorrect password was specified.
reason code System action: Access to the product is not granted.
The VSAM reason code issued by the
checkpoint data set I/O routine. User response: Repeat the logon procedure,
specifying the correct password. If you do not have the
System action: The service probes continue correct password, contact your product administrator.
processing, if possible. Other messages issued with this The destination is the Tivoli Enterprise Monitoring
message can provide further details. Server Engine log file, RKLVLOG.
User response: Ensure that the OMEGAMON II
checkpoint data set has not been overwritten and free

70 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Chapter 4. KDFC Messages
This section provides OMEGAMON II for SMS messages with the prefix of KDFC.

RKLVLOG. The load request fails and returns a nonzero

KDFCH01I SQL LOAD COMPLETE, MEMBER=
return code. The user session continues.
member.
User response: Any panel showing results from this
Explanation: This message is generated for each
query provides incorrect or blank output. Review
SQL source member that is loaded either during
product installation logs for errors, then contact IBM
OMEGAMON II for SMS address space initialization or
Software Support. The destination is the Tivoli
as a result of a user navigating to a product panel.
Enterprise Monitoring Server Engine log file, RKLVLOG.
System action: This message is issued to the
RKLVLOG.
KDFCT003 KDFS APPLICATION vtam-appl
User response: None. This message is informational. STARTED
The destination is the Tivoli Enterprise Monitoring
Explanation: The OMEGAMON II for SMS application
Server Engine log file, RKLVLOG.
has been successfully started where vtam-appl is the
OMEGAMON II for SMS APPLID.
KDFCH02I PANEL LOAD COMPLETE, MEMBER=
System action: None.
member.
User response: None. This is an informational
Explanation: This message is generated for each
message only. The destination is the Tivoli Enterprise
panel initialization source member that is loaded either
Monitoring Server Engine log file, RKLVLOG, and the
during OMEGAMON II for SMS address space
MVS system console.
initialization or as a result of a user navigating to a
product panel.
System action: This message is issued to the
RKLVLOG.
User response: None. This message is informational.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.

KDFCH03E MEMORY ALLOCATION FAILURE,

MEMBER= member.
Explanation: This message is generated if storage is
unable to be allocated during loading of SQL or panel
initialization data.
System action: This message is issued to the
RKLVLOG. The load request fails and returns a nonzero
return code. The user session continues, although blank
or incorrect data can be shown.
User response: Increase virtual storage allocation for
the address space and restart it. The destination is the
Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.

KDFCH04E I/O ERROR ON READ, MEMBER=

member.
Explanation: This message is generated if an I/O
error occurs when trying to read data from either an
SQL source data set or from panel initialization data.
member indicates the member of the persistent data
store that is causing the error.
System action: This message is issued to the

© Copyright IBM Corp. 2006, 2007 71

72 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 5. KDFD Messages
This section provides product-related messages with the prefix of KDFD.

User response: None. This message is informational.

KDFD001I KDFDEVIN INPUT PARMS: parameters
To enable SMF recording within the Tivoli Enterprise
Explanation: This message displays the input
Monitoring Server, specify a valid recording interval for
parameters for data collection that are specified in the
the SMFDINTV parameter and a valid SMF user record
KDFDEVIN member of a data set pointed to by the
number for the SMFRECN parameter. The SMFDINTV
RKANPAR DD statement for the Tivoli Enterprise
parameter accepts the following values:
Monitoring Server address space.
RMFSYNC
System action: None.
Synchronizes with the RMF interval.
User response: None. This message is informational.
SMFSYNC
The destination is the Tivoli Enterprise Monitoring
Synchronizes with the SMF interval.
Server Engine log file, RKLVLOG.
1-1439 Specifies the recording interval in minutes.
KDFD002W KDFDEVIN: SMFDINTV VALUE=OFF;
SMF DEVICE RECORDING DISABLED Specify a user record number from 128255 for the
SMFRECN parameter. Restart the Tivoli Enterprise
Explanation: The KDFDEVIN member of a data set Monitoring Server address space. The destination is the
pointed to by the RKANPAR DD statement for the Tivoli Tivoli Enterprise Monitoring Server Engine log file,
Enterprise Monitoring Server address space contains RKLVLOG.
the parameter SMFDINTV(OFF).
System action: SMF recording is disabled within the KDFD004W KDFDEVIN: INVALID SMF RECORD ID
Tivoli Enterprise Monitoring Server. SMF DEVICE RECORDING DISABLED
User response: None. This message is informational. Explanation: The KDFDEVIN member of a data set
pointed to by the RKANPAR DD statement for the Tivoli
To enable SMF recording within the Tivoli Enterprise
Enterprise Monitoring Server address space contains an
Monitoring Server, specify a valid recording interval for
invalid SMF user record number on the SMFRECN
the SMFDINTV parameter and a valid SMF user record
parameter.
number for the SMFRECN parameter. The SMFDINTV
parameter accepts the following values: System action: SMF recording is disabled within the
Tivoli Enterprise Monitoring Server.
RMFSYNC
Synchronizes with the RMF interval. User response: None. This message is informational.
To enable SMF recording within the Tivoli Enterprise
SMFSYNC
Monitoring Server, make sure that a valid SMF user
Synchronizes with the SMF interval.
record number (128-255) has been specified on the
1-1439 Specifies the recording interval in minutes. SMFRECN parameter. Then, restart the Tivoli Enterprise
Monitoring Server address space. The destination is the
Specify a user record number from 128 to 255 for the Tivoli Enterprise Monitoring Server Engine log file,
SMFRECN parameter. Restart the Tivoli Enterprise RKLVLOG.
Monitoring Server address space. The destination is the
Tivoli Enterprise Monitoring Server Engine log file,
KDFD005E KDFDEVIN: APF AUTHORIZATION
RKLVLOG.
REQUIRED FOR DATA COLLECT
Explanation: All load libraries specified in the
KDFD003W KDFDEVIN: INVALID SMFDINTV
STEPLIB DD statement of the Tivoli Enterprise
VALUE; SMF DEVICE RECORDING
Monitoring Server address space are not APF
DISABLED
authorized.
Explanation: The KDFDEVIN member of a data set
System action: The initialization of the Tivoli
pointed to by the RKANPAR DD statement for the Tivoli
Enterprise Monitoring Server terminates.
Enterprise Monitoring Server address space contains an
invalid value for the SMFDINTV parameter. User response: Make sure that all the Tivoli
Enterprise Monitoring Server load libraries are
System action: SMF recording is disabled within the
APF-authorized prior to restarting the Tivoli Enterprise
Tivoli Enterprise Monitoring Server.
Monitoring Server address space. The destination is the

© Copyright IBM Corp. 2006, 2007 73

KDFD006I • KDFD013E

Tivoli Enterprise Monitoring Server Engine log file,

KDFD010I KDFDSMF: SMF RECORDING
RKLVLOG.
INTERVAL FOR STC SUB-SYSTEM= n
HSECS
KDFD006I KDFDRMFL RETURNING: rmf_level
Explanation: SMF DASD interval recording was being
Explanation: The internal representation (in done at the same interval as the STC subsystem under
hexadecimal characters) of the RMF level currently SMF. The STC subsystem recording interval within SMF
running on the MVS system under which the Tivoli is displayed in hundredths of a second (HSECS).
Enterprise Monitoring Server is running was displayed.
System action: None.
System action: None.
User response: This is an informational message
User response: None. This message is informational. only. The destination is the Tivoli Enterprise Monitoring
The destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Server Engine log file, RKLVLOG.
KDFD011I KDFDSMF: RECORDING INTERVAL
KDFD007I KDFDSMF: SMF DEVICE RECORDING DEFAULTING TO 15 MINUTES
STARTED
Explanation: SMF DASD interval recording is being
Explanation: SMF DASD interval recording was done every 15 minutes within the Tivoli Enterprise
started within the Tivoli Enterprise Monitoring Server Monitoring Server address space.
address space.
System action: None.
System action: None.
User response: This is an informational message
User response: This is an informational message only. The destination is the Tivoli Enterprise Monitoring
only. The destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Server Engine log file, RKLVLOG.
KDFD012E KDFDEVIN: ALLOCATION FAILED FOR
KDFD008I KDFDSMF: SMF DEVICE RECORDING work_area SIZE=bytes
COMPLETED
Explanation: Data collection initialization failed during
Explanation: SMF DASD interval recording was allocation of the required work area name indicated in
completed in the Tivoli Enterprise Monitoring Server the message. The size (in bytes) required for the work
address space. area is also displayed.
System action: None. System action: The initialization of Tivoli Enterprise
Monitoring Server terminates.
User response: This is an informational message
only. The destination is the Tivoli Enterprise Monitoring User response: Change the LIMIT parameter
Server Engine log file, RKLVLOG. depending on the number of devices defined to your
system. The LIMIT value is expressed as a power of 2,
thus LIMIT (22,x) specifies 4 meg, LIMIT (23,x) specifies
KDFD009I KDFDSMF: RMF INTERVAL= n HSECS 8 meg, and so on. Each device table entry is 320 bytes,
ELAPSED= n HSECS REMAINING= n so LIMIT (23,x) allows allocation of a device table large
HSECS enough to accommodate about 26,000 devices. LIMIT
Explanation: SMF DASD interval recording is being (24,x) accommodates twice that many. If the error still
synchronized with RMF interval recording within the occurs, contact IBM Software Support. The destination
Tivoli Enterprise Monitoring Server. The RMF interval is the Tivoli Enterprise Monitoring Server Engine log file,
length, elapsed time within the current RMF interval, RKLVLOG.
and time remaining within the current interval are
displayed in hundredths of a second (HSECS). KDFD013E KDFDEVIN: LOAD FAILED FOR
System action: None. KDFDcccc

User response: This is an informational message Explanation: Data collection initialization failed while
only. The destination is the Tivoli Enterprise Monitoring attempting to load the module indicated.
Server Engine log file, RKLVLOG. System action: The initialization of the Tivoli
Enterprise Monitoring Server terminates.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.

74 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD014E • KDFD020E

message only. The destination is the Tivoli Enterprise

KDFD014E KDFDEVIN: NODATA PARM - DATA
Monitoring Server Engine log file, RKLVLOG.
COLLECTION BYPASSED
Explanation: Member KDFDEVIN of the data set
KDFD018I KDFDSCIN: DEVICES STARTED FOR
pointed to by the RKANPAR DD statement for the Tivoli
COLLECTION; container SUCCESSFUL
Enterprise Monitoring Server address space was empty
COUNT=nnn; FAILURE COUNT=nnn
or not present.
Explanation: The data set collector has started
System action: Data collection for OMEGAMON II is
collecting for devices as specified in the KDFDSCIN
suppressed, but Tivoli Enterprise Monitoring Server
parameter member of the data set pointed to by the
initialization continues.
RKANPAR DD statement. The number of devices for
User response: Verify that the KDFDEVIN member which collection was successfully started is given, as
exists or is not empty. See the IBM OMEGAMON II for well as the number for which it failed.
SMS Program Directory for information about creating a
System action: None.
valid KDFDEVIN member. Then, restart the Tivoli
Enterprise Monitoring Server address space with the User response: If the failure count is not zero (0),
corrected KDFDEVIN member of the data set pointed to make sure that all devices specified on the VOLSERS,
by the RKANPAR DD statement. The destination is the DEVICES, and DEVRANGE parameters in the
Tivoli Enterprise Monitoring Server Engine log file, KDFDSCIN member are valid devices for the system on
RKLVLOG. which the Tivoli Enterprise Monitoring Server is active. If
changes are made, restart the Tivoli Enterprise
Monitoring Server address space. The destination is the
KDFD015I KDFDSCIN INPUT PARMS: parameters
Tivoli Enterprise Monitoring Server Engine log file,
Explanation: The input parameters for data set RKLVLOG.
collection specified in the KDFDSCIN member of the
RKANPAR DD statement for the Tivoli Enterprise
KDFD019W KDFDSCIN: NO DEVICES SPECIFIED
Monitoring Server address space are displayed.
FOR COLLECTION
System action: None.
Explanation: No devices were specified in the
User response: This is an informational message KDFDSCIN parameter member of the data set pointed
only. The destination is the Tivoli Enterprise Monitoring to by the RKANPAR DD statement for data set
Server Engine log file, RKLVLOG. collection.
System action: No devices are specified for data set
KDFD016W KDFDSCIN: PARM ERRORS collection.
DETECTED; DEVICES WILL BE
User response: If data set collection is desired,
SKIPPED
specify devices using the VOLSERS, DEVICES, and
Explanation: At least one hex device number is DEVRANGE parameters in the KDFDSCIN member.
invalid in the input parameters for data set collection Then restart the Tivoli Enterprise Monitoring Server
specified in the KDFDSCIN member of the data set address space. The destination is the Tivoli Enterprise
pointed to by the RKANPAR DD statement for the Tivoli Monitoring Server Engine log file, RKLVLOG.
Enterprise Monitoring Server address space.
System action: The device or device range with the KDFD020E KDFDSCIN: CANDLE SUBSYSTEM
invalid number is ignored and data set collection does INITIALIZATION FAILED; RC=
not occur for the devices. return_code
User response: Correct the device (DEVICES) or Explanation: The Tivoli Enterprise Monitoring Server
device range (DEVRANGE) parameters in the initialization call to the subsystem required for data set
KDFDSCIN member, then restart the Tivoli Enterprise collection failed with the return code displayed.
Monitoring Server address space. The destination is the
System action: Data set collection does not occur.
Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG. User response: Make sure that the subsystem
module KCNDLI is available to the Tivoli Enterprise
Monitoring Server address space, then restart the Tivoli
KDFD017I KDFDSCIN: DATASET COLLECTOR
Enterprise Monitoring Server. Otherwise, record the
INITIALIZED; RC= return_code
return code and contact IBM Software Support. The
Explanation: The data set collector has been destination is the Tivoli Enterprise Monitoring Server
successfully initialized; the initialization return code is Engine log file, RKLVLOG.
displayed. Valid return codes are zero (0) and 4.
User response: None. This is an informational

Chapter 5. KDFD Messages 75

KDFD021E • KDFD027I

attempt during the Tivoli Enterprise Monitoring Server

KDFD021E KDFDSCIN: DATASET COLLECTOR
initialization. However, a prior attempt to initialize data
INITIALIZATION FAILED; SSRQ RC=
set collection encountered a problem which caused data
return_code INIT RC= return_code
set collection to be completely disabled.
Explanation: The Tivoli Enterprise Monitoring Server
System action: Data set collection does not occur.
initialization call to the data set collector failed with the
given return codes. User response: Find previous messages in the
RKLVLOG from the KDFDSCIN module to identify the
System action: Data set collection does not occur.
original reason for data set collection being disabled
User response: Make sure that the subsystem and follow advice for the messages.
address space has been started. Because a retry to
initialize is automatically attempted when data set
KDFD025I KDFDSCIN: DATASET COLLECTION
collector data is requested, a restart of the Tivoli
DISABLED; NO KDFDSCIN PARM
Enterprise Monitoring Server address space should not
MEMBER
be necessary. Otherwise, record the two return codes
and contact IBM Software Support. The destination is Explanation: Data set collection has been disabled
the Tivoli Enterprise Monitoring Server Engine log file, because the KDFDSCIN parameter member of the data
RKLVLOG. set pointed to by the RKANPAR DD statement was not
found. The lack of the KDFDSCIN member is the
normal way to disabling data set collection.
KDFD022E KDFDSCIN: DATASET COLLECTOR
DEVICE FAILED; SSRQ RC= System action: Data set collection does not occur.
return_code RC= return_code
User response: This is an informational message
Explanation: Data set collection was not successfully only. If data set collection is desired, specify devices
started for any devices specified in the KDFDSCIN using the VOLSERS, DEVICES, and DEVRANGE
member of the data set pointed to by the RKANPAR DD parameters in the KDFDSCIN member, then restart the
statement. The return codes are displayed. Tivoli Enterprise Monitoring Server address space. The
destination is the Tivoli Enterprise Monitoring Server
System action: Data set collection does not occur.
Engine log file, RKLVLOG.
User response: Make sure that the devices specified
on the VOLSERS, DEVICES, and DEVRANGE
KDFD026E KDFDSCIN: PARM MEMBER NOT
parameters in the KDFDSCIN member are valid devices
FOUND IN PDS IN SECOND PASS; RC=
for the system on which the Tivoli Enterprise Monitoring
return_code
Server is active, then restart the Tivoli Enterprise
Monitoring Server address space. Otherwise, record the Explanation: Data set collection initialization failed
two return codes and contact IBM Software Support. during the second pass of parsing the KDFDSCIN
The destination is the Tivoli Enterprise Monitoring member of the data set pointed to by the RKANPAR DD
Server Engine log file, RKLVLOG. statement. The member is no longer available, even
though it was available during the first pass of parsing.
KDFD023E KDFDSCIN: ALLOCATION FAILED FOR System action: Data set collection does not occur.
START LISTS; SIZE= bytes
User response: Correct the problem with the
Explanation: Data set collection initialization failed KDFDSCIN member, then restart the Tivoli Enterprise
during allocation of the required area for device lists. Monitoring Server address space. If the error still
The number of bytes required for the area is given in occurs, contact IBM Software Support. The destination
the message. is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.
System action: Data set collection does not occur.
User response: Restart the Tivoli Enterprise
KDFD027I KDFDTERM: DATASET COLLECTION
Monitoring Server address space with a larger region
STOPPED; container SUCCESSFUL
size. If the error still occurs, contact IBM Software
COUNT=nnn; FAILURE COUNT=nnn
Support. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG. Explanation: During termination of the Tivoli
Enterprise Monitoring Server address space, the data
set collector has stopped collecting for devices. The
KDFD024W KDFDSCIN: DATASET COLLECTION
number of devices for which collection was successfully
PREVIOUSLY DISABLED; RETRY NOT
stopped is given, as well as the number for which it
ATTEMPTED
failed. A failure to stop collecting for some devices can
Explanation: Due to an incoming request to the Tivoli be normal because they were not started during the
Enterprise Monitoring Server for data, data set collector Tivoli Enterprise Monitoring Server initialization.
initialization has been retried after an unsuccessful

76 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD028I • KDFD035W

System action: None. code and contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
User response: None. This message is informational.
Engine log file, RKLVLOG.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
KDFD032E KDFDCISS: LOAD ERROR DURING
$CACHENV INITIALIZE
KDFD028I KDFDTERM: DATASET COLLECTOR
TERM NOT DONE; container reason Explanation: The cache collection environment failed
because of an error during an attempt to load the
Explanation: During termination of the Tivoli
module KCCCOLL.
Enterprise Monitoring Server address space, the data
set collector did not require termination for the reason System action: DASD and control unit cache data
specified. collection does not occur.
System action: None. User response: Make sure that the module KCCCOLL
is available to the Tivoli Enterprise Monitoring Server
User response: None. This message is informational.
address space, then restart the Tivoli Enterprise
The destination is the Tivoli Enterprise Monitoring
Monitoring Server. Otherwise, contact IBM Software
Server Engine log file, RKLVLOG.
Support. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG.
KDFD029E KDFDTERM: DATASET COLLECTOR
STOP DEVICE FAILED; container SSRQ
KDFD033W KDFDCISS: ERROR IN $CACHRTR
RC=return_code STOP RC=return_code
INITIAL CUSCAN; RC=return_code
Explanation: During termination of the Tivoli REASON=reason_code
Enterprise Monitoring Server address space, the data
Explanation: An error occurred in initializing cache
set collector failed to stop collecting for devices
control unit information; the return and reason codes are
specified in the KDFDSCIN member of the data set
displayed.
pointed to by the RKANPAR DD statement.
System action: Control unit cache data collection
System action: Data set collection can continue for
does not occur.
devices even though the Tivoli Enterprise Monitoring
Server address space is not active. User response: If no cache controllers are installed
on the system, this message is normal and
User response: If you no longer want data set
informational only. If cache controllers are installed,
collection for devices, and previous messages issued
record the return code and reason code and contact
during the Tivoli Enterprise Monitoring Server
IBM Software Support. The destination is the Tivoli
initialization indicate that it was successfully started,
Enterprise Monitoring Server Engine log file, RKLVLOG.
stop the subsystem address space, when convenient. If
the data set collector is left operating, you can
experience some overhead degradation. The destination KDFD034W KDFDCISS: ALLOCATION FAILED FOR
is the Tivoli Enterprise Monitoring Server Engine log file, W#CCUWRK; SIZE=bytes
RKLVLOG.
Explanation: Cache control unit collection initialization
failed during the allocation of a required work area. The
KDFD030I KDFDCISS: $CACHENV INITIALIZED size required for the area is displayed.
SUCCESSFULLY
System action: Control unit cache data collection
Explanation: The cache collection environment has does not occur.
been successfully initialized.
User response: Restart the Tivoli Enterprise
System action: None. Monitoring Server address space with a larger region
size. If the error still occurs, contact IBM Software
User response: None. This message is informational.
Support. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG.
KDFD031E KDFDCISS: ERROR IN $CACHENV
INITIALIZE; container RC= return_code
KDFD035W KDFDCISS: EXTRA SPACE FOR
REASON= reason_code
CONTROL UNITS USED; DATA LOST
Explanation: The cache collection environment failed FOR: cache_control_unit
to initialize for the return and reason codes displayed.
Explanation: An attempt was made to add the cache
System action: DASD and control unit cache data control unit specified to the control unit work area after
collection does not occur. initialization and all extra space allocated for such
additions was used. The Tivoli Enterprise Monitoring
User response: Record the return code and reason

Chapter 5. KDFD Messages 77

KDFD036W • KDFD042W

Server was not able to keep and report data about the Tivoli Enterprise Monitoring Server Engine log file,
specified control unit. The control unit is specified by the RKLVLOG.
SSID (ssidFF00) or the SDID (FFFFcc00, where cc is
the SDID).
KDFD039W KDFDCISS: ERROR IN $CACHRTR
System action: None. DEVICE ACCUM. SCAN;
RC=return_code REASON=reason_code
User response: Although not immediately required,
restart the Tivoli Enterprise Monitoring Server address Explanation: An error occurred in retrieving DASD
space to remedy the situation. The destination is the cache information, which was to be accumulated at the
Tivoli Enterprise Monitoring Server Engine log file, cache control unit level. The return and reason codes
RKLVLOG. are given in the message. All cache control unit
statistics might not be current.
KDFD036W KDFDCISS: ERROR IN $CACHRTR System action: None.
UPDATE CUSCAN; RC=return_code
User response: One occurrence of this message does
REASON=reason_code
not indicate a problem. If the message persists, record
Explanation: An error occurred in retrieving cache the return and reason codes and contact IBM Software
control unit information for the return and reason codes Support. The destination is the Tivoli Enterprise
displayed. All cache control unit status information might Monitoring Server Engine log file, RKLVLOG.
not be current.
System action: None. KDFD040W KDFDCISS: $CACHTAB
FUNCTION=REFRESH (n) FAILED;
User response: Record the return and reason codes
RC=return_code REASON=reason_code
and contact IBM Software Support. The destination is
the Tivoli Enterprise Monitoring Server Engine log file, Explanation: An error occurred while refreshing
RKLVLOG. current cache information; the return and reason codes
are displayed. Cache information might not be as
current as specified in the CACHINTV parameter in
KDFD037W KDFDCISS: CU NOT FOUND IN
member KDFDEVIN.
W#CCUWRK DURING DEVICE
ACCUMULATION PHASE: System action: None.
cache_control_unit
User response: One occurrence of this message does
Explanation: The specified cache control unit not indicate a problem. If the message persists, record
associated with a DASD device was not represented in the return and reason codes and contact IBM Software
the control unit work area. The control unit is specified Support. The destination is the Tivoli Enterprise
by the SSID (ssidFF00) or the SDID (FFFFcc00, where Monitoring Server Engine log file, RKLVLOG.
cc is the SDID).
System action: Data pertaining to this DASD device is KDFD041W KDFDCISS: $CACHTAB
not included in cache control unit information. FUNCTION=RESET FAILED;
RC=return_code
User response: One occurrence of this message does
REASON=reason_code
not indicate a problem. If the message persists, contact
IBM Software Support. The destination is the Tivoli Explanation: An error occurred while resetting cache
Enterprise Monitoring Server Engine log file, RKLVLOG. base statistics; the return and reason codes are given in
the message. Cache information covers a longer period
than specified in the CACHINTV parameter in the
KDFD038W KDFDCISS: CU UPDATED IN DEVICE
KDFDEVIN member.
ACCUM PHASE BUT NOT DURING
CUSCAN PHASE: cache_contro_unit System action: None.
Explanation: The specified cache control unit User response: Record the return and reason codes
associated with a DASD device has not had its data and contact IBM Software Support. The destination is
updated during the current collection interval. The the Tivoli Enterprise Monitoring Server Engine log file,
control unit is specified by the SSID (ssidFF00) or the RKLVLOG.
SDID (FFFFcc00, where cc is the SDID).
System action: None. All data is still there; however, KDFD042W COLLECTION INTERVAL TABLE
the control unit status information might not be current. INQUIRY FAILED - reason
User response: One occurrence of this messages Explanation: The probe that collects data collection
does not indicate a problem. If the message persists, interval information failed because of the reason
contact IBM Software Support. The destination is the appended to the end of the message.

78 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD043W • KDFD056W

System action: Processing continues. A default persists, contact IBM Software Support. The destination
collection interval is adopted. is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.
User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFD048I DEVICE COLLECTION TABLE UPDATE
SUCCESSFUL
KDFD043W COLLECTION INTERVAL TABLE
UPDATE REJECTED - UPDATE IN Explanation: An attempt to update the device
PROGRESS collection table completed successfully.
Explanation: An attempt to update data collection System action: OMEGAMON II continues monitoring
interval information failed because of contention. using the updated device collection table.
System action: The update is rejected. User response: This is an informational message
only. The destination is the Tivoli Enterprise Monitoring
User response: Retry the request. If the problem
Server Engine log file, RKLVLOG.
persists contact IBM Software Support. The destination
is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG. KDFD049W DEVICE COLLECTION TABLE ADD
FAILED - xxxxxxxxxx
KDFD044W COLLECTION INTERVAL TABLE Explanation: An attempt to add a device to the
UPDATE FAILED - $DEVWRK NOT collection table failed. The reason for the failure is
FOUND stated in the message. Possible reasons are:
Explanation: An attempt to update data collection v KDFX REQUEST FAILED
interval information failed because an internal control v MEMORY NOT AVAILABLE
block cannot be found. v MONITOR RESET FAILED
System action: The update is rejected. v DUPLICATE ENTRY
User response: Contact IBM Software Support. The This message might be preceded by an additional
destination is the Tivoli Enterprise Monitoring Server KDFD049W message containing diagnostic information
Engine log file, RKLVLOG. in the following format:
KDFX cccc REQUEST ERROR - CN RC=9999 KDFX RC=9999
KDFD045I COLLECTION INTERVAL TABLE System action: OMEGAMON II continues monitoring
UPDATE SUCCESSFUL using the existing device collection table.
Explanation: An update of the data collection interval User response: Try the update again. If the problem
information successfully completed. persists, contact IBM Software Support. The destination
System action: Normal processing continues. is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.
User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFD055W parameter KEYWORD SYNTAX INVALID

KDFD047W DEVICE COLLECTION TABLE UPDATE Explanation: An error was detected during the parsing
FAILED - xxxxxxxxxx of the KDFDEVSU member of the RKANPAR data set.

Explanation: An attempt to update the device System action: The DASD exclusion list is
collection table failed. The reason for the failure is incomplete.
stated in the message. Possible reasons are: User response: Correct the keyword syntax. The
v KDFX REQUEST FAILED destination is the Tivoli Enterprise Monitoring Server
v STORAGE UNAVAILABLE Engine log file, RKLVLOG.
v MONITOR RESET FAILED
KDFD056W STORAGE SHORTAGE PROCESSING
This message might be preceded by an additional
parameter KEYWORD
KDFD047W message containing diagnostic information
in the following format: Explanation: A getmain failure occurred while
KDFXcccc REQUEST ERROR - CN RC=9999 KDFX RC=9999 processing the listed parameter of the KDFDEVSU
member of the RKANPAR data set.
System action: OMEGAMON II continues monitoring
using the existing device collection table. System action: The DASD exclusion list is
incomplete.
User response: Try the update again. If the problem

Chapter 5. KDFD Messages 79

KDFD058W • KDFD072W

User response: Review the region size of the Tivoli

KDFD069E KDFDPDEV: SETUP FAILED FOR DASD
Enterprise Monitoring Server Engine address space.
TABLE INSERTS; RC=99
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG. Explanation: The setup request issued prior to
inserting historical application information into the
Persistent Data Store failed with return code ’99’.
KDFD058W parameter KEYWORD INVALID DEVICE
ADDRESS SPECIFIED System action: Historical information collection is
bypassed for the current interval. Collection is retried
Explanation: A syntax error was discovered while
next interval.
processing the KDFDEVSU member of the RKANPAR
data set. The range of addresses in the listed parameter User response: Verify the persistent data store was
was invalid. allocated and initialized without error. If the problem
persists, contact IBM Software Support. The destination
System action: The DASD exclusion list is
is the Tivoli Enterprise Monitoring Server Engine log file,
incomplete.
RKLVLOG.
User response: Correct the erroneous syntax. The
destination is the Tivoli Enterprise Monitoring Server
KDFD070E KDFD070E KDFDPDEV: INSERT
Engine log file, RKLVLOG.
FAILED FOR DASD TABLE INSERT;
RC=99 -- RECORDING TERMINATING
KDFD060W parameter KEYWORD DUPLICATE FOR THIS INTERVAL
ENTRY SPECIFIED
Explanation: A request to add historical DASD
Explanation: A duplicate specification occurred while information to the Persistent Data Store failed with
processing the KDFDEVSU member of the RKANPAR return code ’99’.
data set.
System action: Historical DASD information collection
System action: The DASD exclusion list is is terminated. Collection is retried during the next
incomplete. collection interval.
User response: Correct the erroneous duplicate User response: Verify the persistent data store was
syntax. The destination is the Tivoli Enterprise allocated and initialized without error. Check the Tivoli
Monitoring Server Engine log file, RKLVLOG. Enterprise Monitoring Server address space logs
CTPDSOUT and CTPDSLOG for relevant messages. If
the problem persists, contact IBM Software Support.
KDFD061W KDFDEVIN: RMF API INITIALIZATION The destination is the Tivoli Enterprise Monitoring
FAILURE, RC=nn Server Engine log file, RKLVLOG.
Explanation: An attempt to initialize the RMF API
failed with a return code of nn. KDFD071E KDFDPDEV: DASD PDS RECORDING
System action: The RMF API is not used to retrieve DISABLED - $DEVWRK ADDRESS
performance data. ZERO ON ENTRY

User response: None. The destination is the Tivoli Explanation: The recording of DASD information to
Enterprise Monitoring Server Engine log file, RKLVLOG. the persistent data store is disabled as an internal
control block cannot be found.

KDFD063W parameter KEYWORD VALUE INVALID System action: Normal processing continues, but
historical dasd information is unavailable.
Explanation: A syntax error was discovered while
processing the KDFDEVSU member of the RKANPAR User response: Contact IBM Software Support. The
data set. destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
System action: The DASD exclusion list is
incomplete.
KDFD072W KDFDPDEV: DASD PDS RECORDING
User response: Correct the erroneous syntax. The SKIPPED THIS INTERVAL - NO
destination is the Tivoli Enterprise Monitoring Server ENTRIES FOUND IN DEVICE TABLE
Engine log file, RKLVLOG.
Explanation: No DASD are currently being monitored
and no historical information is recorded for this interval.
System action: Normal processing continues.
User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.

80 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD073W • KDFD082W

member of the rhilev.TKDFPRMD data set was

KDFD073W KDFDPDEV: CACHE STATISTICS NOT
specified as 0.
RECORDED THIS INTERVAL -
V#CISTOK IS ZERO System action: Tape information is not available. The
collection of tape data is disabled.
Explanation: No cache statistics can be recorded.
User response: None, if no tape data is desired. If
System action: Normal processing continues, but no
tape data is desired, define a nonzero collection interval
historical cache information is available for this interval.
using the Configuration Tool panels. The destination is
User response: None. The destination is the Tivoli the Tivoli Enterprise Monitoring Server Engine log file,
Enterprise Monitoring Server Engine log file, RKLVLOG. RKLVLOG.

KDFD074W KDFDPDEV: $CACHRTR ERROR; KDFD080I KDFDPDSN reqid REQUEST ERROR

VOLSER=volser RC=nn REASON=xx RC= rc
Explanation: An error occurred attempting to retrieve Explanation: DF request indicated by reqid cannot be
cache statistics. completed for KDFDPDSN. The error return code rc
indicates the type of problem.
System action: Normal processing continues, but no
historical cache information is available for this interval. System action: A system request cannot be
completed.
User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG. User response: Most causes of this message are
transient in nature, and do not indicate a problem. If the
message persists, contact IBM Software Support.
KDFD075E KDFDTPIN: INPUT DATA NOT
Possible return codes include:
AVAILABLE - TAPE COLLECTION
BYPASSED x’fe’ Indicates the control blocks for the persistent
data store have not yet initialized. Retry, if the
Explanation: Module KDFDTPIN was unable to read
problem persists contact IBM Software
member KDFDTPIN of the rhilev.TKDFPRMD data set.
Support.
System action: Tape information is not available. The
x’ff’ Indicates that the persistent data store did not
collection of tape data is disabled.
initialize successfully and the control blocks do
User response: If the KDFDTPIN member of the not exist. Re-initialize the data sets of the
rhilev.TKDFPRMD data set does not exist, define it persistent data store. The CTPDSOUT and
using the Configuration Tool panels. If the member does CTPDSLOG JES data sets can contain
exist, contact IBM Software Support. The destination is information concerning the problem. If this fails,
the Tivoli Enterprise Monitoring Server Engine log file, contact IBM Software Support.
RKLVLOG.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
KDFD076I KDFDTPIN: INTERVAL OF OFF
SPECIFIED - TAPE COLLECTION
DISABLED KDFD081E KDFDTAPE: INVALID WORK AREA
Explanation: The INTERVAL value in the KDFDTPIN Explanation: The tape collection work area did not
member of the rhilev.TKDFPRMD data set was pass validation.
specified as OFF.
System action: The collection of tape data is
System action: Tape information is not available. The disabled.
collection of tape data is disabled.
User response: Obtain a dump of the data collector
User response: None, if no tape data is desired. If address space and the RKLVLOG for the data collection
tape data is desired, define a collection interval using address space. Then contact IBM Software Support.
the Configuration Tool panels. The destination is the The destination is the Tivoli Enterprise Monitoring
Tivoli Enterprise Monitoring Server Engine log file, Server Engine log file, RKLVLOG.
RKLVLOG.
KDFD082W KDFD082W KDFDTAPE: CATALOG
KDFD077I KDFD076I KDFDTPIN: INTERVAL OF 0 READ ERROR, RC = xx - yy
SPECIFIED - TAPE COLLECTION
System action: An attempt to extract data from the
DISABLED
tape catalog failed with return code xx and reason code
Explanation: The INTERVAL value in the KDFDTPIN yy. The collection of tape data continues. However, data
for installed tape libraries is not available.

Chapter 5. KDFD Messages 81

KDFD083E • KDFD095E

User response: Contact IBM Software Support.

KDFD089I KDFLDEV: HISTORICAL DATA
FETCHED IS PAST RANGE; DATE
KDFD083E KDFDTAPE: SUBSYSTEM FUNCTION REQUESTED = mm/dd/yy, TIME
DIOPUCBA: RC = xx - yy REQUESTED = hhmmss, DATE
RETURNED = mm/dd/yy, TIME
Explanation: An attempt to access the subsystem RETURNED = hhmmss
failed with return code xx and reason code yy.
Explanation: No qualifying data can be found for the
System action: The collection of tape data is historical request.
disabled. Tape data is not available.
System action: Normal processing continues, but no
User response: Verify that the subsystem was data is returned.
installed with the proper level of maintenance, and has
been started. Gather the RKLVLOG for the data User response: None.
collection address space, and contact IBM Software
Support. The destination is the Tivoli Enterprise
KDFD093W KDFDPAPL: RMF SYNCHRONIZATION
Monitoring Server Engine log file, RKLVLOG.
FAILED - RECORDING INTERVAL
DEFAULTING TO 15 MINUTES
KDFD084E KDFDTAPE: STORAGE UNAVAILABLE,
Explanation: Either RMF is inactive or its recording
LENGTH = xxxxxxxx
interval is less than one minute.
Explanation: An attempt to obtain xxxxxxxx bytes of
System action: Application statistics is collected at 15
storage failed.
minute intervals.
System action: The collection of tape data is
User response: None. The destination is the Tivoli
disabled. Tape data is not available.
Enterprise Monitoring Server Engine log file, RKLVLOG.
User response: Keep the RKLVLOG for the data
collection address space and contact IBM Software
KDFD094E KDFDPAPL: SETUP FAILED FOR APPL
Support. The destination is the Tivoli Enterprise
TABLE INSERTS; RC=99
Monitoring Server Engine log file, RKLVLOG.
Explanation: The setup request issued prior to
inserting historical application information into the
KDFD085E KDFDTAPE: LOAD FAILED FOR
Persistent Data Store failed with return code ’99’.
IEFEB4UV
System action: Historical information collection is
Explanation: IBM load module IEFEB4UV was not
bypassed for the current interval. Collection is retried
available to be loaded.
next interval.
System action: The collection of tape data is
User response: Verify the persistent data store was
disabled. Tape data is not available.
allocated and initialized without error. If the problem
User response: Load module IEFEB4UV should be in persists, contact IBM Software Support. The destination
either SYS1.LINKLIB or SYS1.LPALIB. Contact your is the Tivoli Enterprise Monitoring Server Engine log file,
system programmer to determine the location of this RKLVLOG.
IBM module. If it is located in either a linklisted data set
or a data set in the LPALIB concatenation, contact IBM
KDFD095E KDFDPAPL: INSERT FAILED FOR APPL
Software Support. The destination is the Tivoli
TABLE INSERT; RC=rc -- RECORDING
Enterprise Monitoring Server Engine log file, RKLVLOG.
TERMINATING FOR THIS INTERVAL,
R5=r5
KDFD086E KDFLDEV: REQUEST FOR
Explanation: An attempt to insert historical application
HISTORICAL DATA FAILED - ERROR
data into the Persistent Data Store (PDS) failed with
LOCATING DFPDSWKA
return code specified as rc. r5 contains the length of the
Explanation: An attempt to retrieve historical device record being inserted.
data failed because an internal control block cannot be
System action: This historical record is bypassed and
found.
processing continues.
System action: No data is returned.
User response: Verify that the persistent data store is
User response: This error should not occur. Contact large enough, and that it was allocated and initialized
IBM Software Support. The destination is the Tivoli without error. If the problem persists, contact IBM
Enterprise Monitoring Server Engine log file, RKLVLOG. Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.

82 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD096E • KDFD109E

v DEVRANGE
KDFD096E KDFDPAPL: APPL PDS RECORDING
DISABLED - reason v VOLSERS

Explanation: An attempt to initialize historical System action: The volume in error is bypassed for
application data recording in the Persistent Data Store data set level monitoring. Normal processing continues.
failed because of reason. Possible values for reason User response: Correct the error in KDFDSCIN and
include: issue the DFREF command to refresh the KDFDSCIN
v $DEVWRK ADDRESS ZERO ON ENTRY parameters. The destination is the Tivoli Enterprise
v OM2SM VECTOR TABLE NOT FOUND Monitoring Server Engine log file, RKLVLOG.
v $APPLWRK WORK AREA NOT FOUND
v DFPDSWKA WORK AREA NOT FOUND KDFD104W KDFDEVSU PARM KEYWORD
parameter INVALID
v INVALID DFPDSWKA DETECTED
v LOAD FAILED FOR KDFDRMFI Explanation: A syntax error was discovered while
parsing the contents of the KDFDEVSU member of the
System action: Historical collection for application RKANPAR data set.
data is bypassed for the life of this Tivoli Enterprise
Monitoring Server address space. System action: The DASD exclusion list is
incomplete.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server User response: Correct the erroneous syntax. The
Engine log file, RKLVLOG. destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.

KDFD101I parm KEYWORD INVALID - SET TO

DEFAULT KDFD105W KDFDEVSU PARM ERRORS
DETECTED; EXCLUDE LIST
Explanation: The value specified for keyword parm in INCOMPLETE
member KDFDSCIN of the RKANPAR data set is
invalid. Explanation: Errors have been detected while parsing
the contents of the KDFDEVSU member of the
System action: The default value is taken for the RKANPAR data set. A preceding error message details
keyword parameter and processing continues. the exact cause of the error.
User response: Correct the value for the keyword and System action: The DASD exclusion list only consists
issue the DFREF command to refresh the KDFDSCIN of those specifications successfully parsed prior to
parameters. The destination is the Tivoli Enterprise discovery of the error.
Monitoring Server Engine log file, RKLVLOG.
User response: Correct the erroneous syntax. The
destination is the Tivoli Enterprise Monitoring Server
KDFD102W MSR AND SAMPCT KEYWORDS Engine log file, RKLVLOG.
MUTUALLY EXCLUSIVE
Explanation: Keywords MSR and SAMPCT were both KDFD106I KDFDEVSU PARM MEMBER NOT
specified for the same volume in member KDFDSCIN of FOUND; EXCLUDE LIST WAS NOT
the RKANPAR data set. These keywords are mutually BUILT
exclusive.
Explanation: There is no KDFDEVSU member in the
System action: The volume in error is bypassed for RKANPAR data set.
data set level monitoring. Normal processing continues.
System action: Normal processing continues, all
User response: Correct the error in KDFDSCIN and devices are monitored.
issue the DFREF command to refresh the KDFDSCIN
parameters. The destination is the Tivoli Enterprise User response: None. The destination is the Tivoli
Monitoring Server Engine log file, RKLVLOG. Enterprise Monitoring Server Engine log file, RKLVLOG.

KDFD103W parm KEYWORD - MSR KEYWORD KDFD109E KDFDCHPS - RMF API NOT AVAILABLE
REQUIRES MONITOR STATUS ON Explanation: IBM module ERBSMFI was not found in
Explanation: OFF and MSR= were specified together on an available library.
keyword parm in member KDFDSCIN of the RKANPAR System action: Processing continues but all data, that
data set. The specification of an MSR value requires is normally obtained through the RMF API, appears as
monitoring status to be specified as (or allowed to zeros or ″n/a″ on the screen.
default to) ON. Possible values for parm include:
v DEVICES User response: Find the library containing the RMF

Chapter 5. KDFD Messages 83

KDFD110E • KDFD1171

interface module ERBSMFI and make sure it is

KDFD113W CPMF UNAVAILABLE - NO CHPID
available to the Tivoli Enterprise Monitoring Server
DATA
started task. This can involve concatenating it as a
STEPLIB. Be aware that your shop might be running a Explanation: The channel path measurement facility is
third-party RMF substitute such as CMF. In that case, unavailable.
the CMF LOADLIB should be concatenated to the
System action: No further attempt is made to gather
STEPLOIB in your Tivoli Enterprise Monitoring Server
channel path data for this collection interval.
startup proc. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG. User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
KDFD110E KDFDCHPS: RMF API FAILURE, RC=
xxxxxxxx
KDFD114W CPMF INACTIVE - NO CHPID DATA
Explanation: An error code (xxxxxxxx) was returned
by the IBM RMF interface. Explanation: The channel path measurement facility is
unavailable.
System action: The collector terminates using the
RMF API for the duration of this collection interval. System action: No further attempt is made to gather
However, a new attempt to use the interface is made channel path data for this collection interval.
during the next and subsequent collection intervals.
User response: Ensure that CPMF is enabled on your
User response: Contact IBM Software Support. The system. The destination is the Tivoli Enterprise
destination is the Tivoli Enterprise Monitoring Server Monitoring Server Engine log file, RKLVLOG.
Engine log file, RKLVLOG.
KDFD115I CPMF MODE CHANGE - NO CHPID
KDFD111E module: RMF SMF RECORD, INVALID DATA
DCS
Explanation: The channel path measurement facility
Explanation: An SMF record was encountered which mode has changed between inactive, compatibility or
should have contained a data control section, but did extended mode.
not. Possible values for module include:
System action: No further attempt is made to gather
v KDFDCHPS channel path data for this collection interval.
v KDFLCHP
User response: None. The destination is the Tivoli
System action: The collector stops using the RMF Enterprise Monitoring Server Engine log file, RKLVLOG.
API for the duration of this collection interval. However,
a new attempt to use the interface is made during the
next and subsequent collection intervals. KDFD116I KDFDEVIN DFSMSHSM NOT
INSTALLED
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server Explanation: the IBM Hierarchical Storage
Engine log file, RKLVLOG. Management (HSM) system is not installed on the
system.

KDFD112E KDFDCHPS: RMF API RETURN System action: No further attempt is made to gather
ERROR, RC= xxxxxxxx HSM related data.

Explanation: Attempting to execute the RETURN User response: None. The destination is the Tivoli
function of the RMF interface, an error (xxxxxxxx) was Enterprise Monitoring Server Engine log file, RKLVLOG.
returned.
System action: The collector stops using the RMF KDFD1171 KDFDUDGI INPUT PARMS: xxxxxxxx
API for the duration of this collection interval. However, Explanation: The input parameters from the
a new attempt to use the interface is made during the KDFDUDGI member of the rhilev RKANPAR data set
next and subsequent collection intervals. were written as xxxxxxxx.
User response: Contact IBM Software Support. The System action: None. Processing continues.
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG. User response: This message is output as a result of
an error. There should be an error message in the Tivoli
Enterprise Monitoring Server SYSOUT log. Follow the
instructions for the error. The destination is the Tivoli
Enterprise Monitoring Server address space log file,
RKLVLOG.

84 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD118E • KDFD125I

Support. The destination is the Tivoli Enterprise

KDFD118E KDFDUDGI MULTIPLE NAME
Monitoring Server address space log file, RKLVLOG.
PARAMETERS IN GROUP DEFINITION -
GROUP IGNORED
KDFD122E KDFDUDGI - xxxxx: yyyyy
Explanation: The NAME keyword was specified twice
in the definition for a single user DASD group. Explanation: A syntax error has occurred in which:
xxxx is the error and yyyyy is the input data that caused
System action: The definition of the user DASD group
the error.
is ignored.
System action: The user DASD group definition
User response: This message should be
containing the error is ignored. Processing continues
accompanied by message KDFD117I. Remove the
with the next user DASD group definition.
multiple NAME keywords from the definition of the user
DASD group in the KDFDUDGI member of the User response: Correct the error and restart the Tivoli
rhilev.RKANPAR data set. The destination is the Tivoli Enterprise Monitoring Server address space. The error
Enterprise Monitoring Server address space log file, is in the KDFDUDGI member of the rhilev.RKANPAR
RKLVLOG. data set. The destination is the Tivoli Enterprise
Monitoring Server address space log file, RKLVLOG.
KDFD119E KDFDUDGI UNABLE TO ALLOCATE
SUMMARY VECTOR KDFD123E KDFDUDGI - STORAGE ALLOCATION
FAILURE; SIZE= xxxxx
Explanation: The summary vector build failed.
Explanation: Allocation of xxxx bytes of virtual storage
System action: Processing continues; however, the
failed.
product is degraded. There is not any user DASD
groups available, and various components of the System action: The user DASD group definition
product do not function properly. containing the error is ignored. Processing of
KDFDUDGI parameters is terminated.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server User response: Contact IBM Software Support. The
address space log file, RKLVLOG. destination is the Tivoli Enterprise Monitoring Server
address space log file, RKLVLOG.
KDFD120E KDFDUDGI GROUP NAME
PREVIOUSLY DEFINED - DUPLICATE KDFD124E KDFDUDGI - GROUP NAME MUST BE
IGNORED DEFINED PRIOR TO OTHER
ELEMENTS
Explanation: A user DASD group with this name was
previously defined. Explanation: The first parameter of a user DASD
group definition was not the NAME keyword.
System action: This definition for the user DASD
group is ignored. The previously defined user DASD System action: The user DASD group definition
group is not affected. containing the error is ignored. Processing continues
with the next user DASD group definition.
User response: All user DASD group definitions must
have unique names. This message should be User response: A user DASD group definition must
accompanied by message KDFD117I. Rename the user begin with the keyword NAME. This message is
DASD group as defined in the KDFDUDGI member of accompanied by message KDFD117I. Correct the error
the RKANPAR data set. The destination is the Tivoli and restart the Tivoli Enterprise Monitoring Server
Enterprise Monitoring Server address space log file, address space. The error is in the KDFDUDGI member
RKLVLOG. of the rhilev.RKANPAR data set. The destination is the
Tivoli Enterprise Monitoring Server address space log
file, RKLVLOG.
KDFD121W KDFDUDGI INPUT DATA NOT
AVAILABLE - NO USER GROUPS
DEFINED KDFD125I KDFDUDGI - EMPTY INPUT MEMBER
PROCESSED
Explanation: Member KDFDUDGI of the
rhilev.RKANPAR data set was not found. Explanation: The KDFDUDGI member of the
rhilev.RKANPAR data set was empty.
System action: No user DASD groups are defined.
System action: No user DASD groups are defined.
User response: This message can be ignored if there
Processing continues.
was no intention to define user DASD groups and the
KDFDUDGI member of the rhilev.RKANPAR data set User response: If the KDFDUDGI member of the
does not exist. Otherwise, contact IBM Software rhilev.RKANPAR data set was intentionally left empty,

Chapter 5. KDFD Messages 85

KDFD126E • KDFD140E

then no action is necessary. If the intention was to the Tivoli Enterprise Monitoring Server address space
define user DASD groups, use the Configuration Tool to log file, RKLVLOG.
try again. If the problem persists, contact IBM Software
Support. The destination is the Tivoli Enterprise
KDFD130E KDFDUDGI - TOO MANY xxxxx
Monitoring Server address space log file, RKLVLOG.
ENTRIES
Explanation: The allowable number of entries of type
KDFD126E KDFDUDGI - INVALID INTERNAL
xxxxx was exceeded. The xxxxx field specifies one of
CHAIN, RC = xx
the keyword parameters.
Explanation: An internal control block chain was
System action: The processing of the user DASD
invalid. The xx field indicates the chain with the
group definition with the problem halts. Other
problem.
processing continues normally.
System action: The processing of user DASD group
User response: Review the definition for the user
definitions halts.
DASD group with the problem. Reduce the number of
User response: Generate a running dump of the Tivoli entries for which the limit is exceeded. The destination
Enterprise Monitoring Server address space and contact is the Tivoli Enterprise Monitoring Server address space
IBM Software Support. The destination is the Tivoli log file, RKLVLOG.
Enterprise Monitoring Server address space log file,
RKLVLOG.
KDFD131E KDFDUDGI - INVALID DEVICE RANGE
Explanation: A value in the DEVRANGE keyword was
KDFD127E KDFDUDGI - VOLSER INPUT INVALID
invalid.
System action: The input from the VOLSER keyword
System action: The processing of the user DASD
had invalid syntax. The processing of the user DASD
group definition with the problem halts. Other
group definition with the problem halts. Other
processing continues normally.
processing continues normally.
User response: Review the definition for the user
User response: Review the rules for the VOLSER
DASD group with the problem. Correct the DEVRANGE
keyword and correct the mistake. Then restart Tivoli
parameter with the problem. The destination is the Tivoli
Enterprise Monitoring Server. The destination is the
Enterprise Monitoring Server address space log file,
Tivoli Enterprise Monitoring Server address space log
RKLVLOG.
file, RKLVLOG.

KDFD132E KDFDSUMM - STORAGE ALLOCATION

KDFD128E KDFDUDGI - INVALID DEVICE
FAILURE; SIZE= xxxxx
ADDRESS
Explanation: An attempt to allocate xxxx bytes of
Explanation: The input from the DEVICE keyword had
virtual storage failed.
invalid syntax.
System action: The processing of performance and
System action: The processing of the user DASD
space data for SMS and user DASD groups terminates.
group definition with the problem halts. Other
processing continues normally. User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
User response: Review the rules for the DEVICE
address space log file, RKLVLOG.
keyword and correct the mistake. Then restart the Tivoli
Enterprise Monitoring Server. The destination is the
Tivoli Enterprise Monitoring Server address space log KDFD140E KDFDUDSI ALLOCATION FAILURE FOR
file, RKLVLOG. DATASET GROUPS HEADER
User response: A GETMAIN request failed. Dataset
KDFD129E KDFDUDGI - INVALID INTERNAL INDEX groups are not active.
Explanation: An internal control block had an invalid System action: Tivoli Enterprise Monitoring Server
value. start-up continues.
System action: The processing of the user DASD User response: Restart the Tivoli Enterprise
group definition with the problem halts. Other Monitoring Server with a larger region size. If the error
processing continues normally. persists, contact IBM Software Support. The destination
is the Tivoli Enterprise Monitoring Server Engine log file,
User response: Review the definition for the user
RKLVLOG.
DASD group with the problem. If there are no syntax
errors, contact IBM Software Support. The destination is

86 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFD141E • KDFD149E

KDFD141E KDFDUDSI - input parameter values KDFD145E KDFDUDSI - INVALID FEATURE NAME
SPECIFIED
Explanation: An unrecognized keyword was
encountered during the parsing of the KDFDUDSI Explanation: An invalid feature name was specified.
member of the RKANPAR data set.
System action: Normal operation continues. The
System action: Normal operation continues. The invalid definition is discarded.
specified parameter value is ignored.
User response: Specify only valid feature names in
User response: Correct the specified parameter. To the KDFDUDSI member of the RKANPAR data set. To
ensure correct input, use the Configuration Tool to ensure correct input, use the Configuration Tool to
specify parameters again. The destination is the Tivoli specify parameters again. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG. Enterprise Monitoring Server Engine log file, RKLVLOG.

KDFD142E KDFDUDSI ALLOCATION FAILURE FOR KDFD146E KDFDUDSI - FEATURE STATUS NOT
DATASET GROUP CORRECTLY SPECIFIED
Explanation: A GETMAIN request failed. Explanation: A valid feature status was not specified.
System action: Tivoli Enterprise Monitoring Server System action: Normal operation continues. The
start-up continues. User data set groups are not incorrect definition is discarded.
available.
User response: Ensure that feature names have an
User response: Restart the Tivoli Enterprise accompanying valid feature status in the KDFDUDSI
Monitoring Server with a larger region size. If the error member of the RKANPAR data set. To ensure correct
persists, contact IBM Software Support. The destination input, use the Configuration Tool to specify parameters
is the Tivoli Enterprise Monitoring Server Engine log file, again. The destination is the Tivoli Enterprise Monitoring
RKLVLOG. Server Engine log file, RKLVLOG.

KDFD143E KDFDUDSI - GROUP NAME MAY ONLY KDFD147E KDFDUDSI - INVALID FEATURE
BE SPECIFIED ONCE STATUS SPECIFIED
Explanation: The GRPNAME keyword was specified Explanation: An invalid feature status was specified.
more than once in a single data set group definition.
System action: Normal operation continues. The
System action: Normal operation continues. The invalid definition is discarded.
specified group is discarded.
User response: Specify a valid feature status in the
User response: Correct the data set group definition KDFDUDSI member of the RKANPAR data set. To
in the KDFDUDSI member of the RKANPAR data set. ensure correct input, use the Configuration Tool to
To ensure correct input, use the Configuration Tool to specify parameters again. The destination is the Tivoli
specify parameters again. The destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFD148E KDFDUDSI - FEATURE MAY ONLY BE
KDFD144E KDFDUDSI - GROUP NAME MUST BE SPECIFIED ONCE
UNIQUE
Explanation: The FEATURE keyword was specified
Explanation: The same name was defined to two more than once in a single data set group definition.
different data set groups.
System action: Normal operation continues. The
System action: Normal operation continues. The incorrect group is discarded.
duplicate definition is discarded.
User response: Correct the data set group definition
User response: Correct the data set group definition in the KDFDUDSI member of the RKANPAR data set.
in the KDFDUDSI member of the RKANPAR data set. To ensure correct input, use the Configuration Tool to
To ensure correct input, use the Configuration Tool to specify parameters again. The destination is the Tivoli
specify parameters again. The destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFD149E KDFDUDSI - MAXIMUM NUMBER OF
DSNAMES EXCEEDED
Explanation: The limit of 100 data set names per data
set group was exceeded.
System action: Normal operation continues. The

Chapter 5. KDFD Messages 87

KDFD150E • KDFD157E

incorrect group is discarded.

KDFD153E KDFDUDSI - SAVEAREA STACK
User response: Reduce the number of data set EXHAUSTED
names in the data set group definition in the KDFDUDSI
Explanation: An internal error occurred.
member of the RKANPAR data set. To ensure correct
input, use the Configuration Tool to specify parameters System action: Dataset groups are not available.
again. The destination is the Tivoli Enterprise Monitoring
User response: Report this error to IBM Software
Server Engine log file, RKLVLOG.
Support. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG.
KDFD150E KDFDUDSI - INVALID DATASET MASK
SPECIFIED
KDFD154I KDFDUDSI GROUPS READ= mmmm,
Explanation: When specifying a data set mask, the GROUPS ACCEPTED= nnnn
wildcard character must appear after (not within) the
Explanation: As a result of parsing the KDFDUDSI
first-level qualifier. For example, ’SYS1?’ is invalid while
member of the RKANPAR data set, mmmm data set
’SYS1.?’ is valid. When updating
groups were input of which nnnn were accepted.
RKANPAR(KDFDUDSI) directly, the wildcard character
is a question mark (?). When using the Configuration System action: Dataset groups are available.
Tool to specify data set groups, the wildcard character is
an asterisk (*). User response: None. This message is informational.
The destination is the Tivoli Enterprise Monitoring
System action: Normal operation continues. The Server Engine log file, RKLVLOG.
invalid group is discarded.
User response: Correct the data set mask in the data KDFD155I KDFDUDSI USER DATASET GROUPS
set group definition in the KDFDUDSI member of the SUCCESSFULLY INITIALIZED
RKANPAR data set. To ensure correct input, use the
Configuration Tool to specify parameters again. The Explanation: Dataset groups initialization completed
destination is the Tivoli Enterprise Monitoring Server successfully.
Engine log file, RKLVLOG. System action: Dataset groups are available.
User response: None. This message is informational.
KDFD151E KDFDUDSI - DATASET NAME TOO The destination is the Tivoli Enterprise Monitoring
LONG Server Engine log file, RKLVLOG.
Explanation: A data set name greater than 44 bytes
was specified. KDFD156I KDFDUDSI USER DATASET GROUP
System action: Normal operation continues. The WORKAREA LOCATED AT xxxxxxxx
invalid group is discarded. Explanation: This is the hexadecimal address of the
User response: Correct the data set name in the data work area for data set groups.
set group definition in the KDFDUDSI member of the System action: Dataset groups are available.
RKANPAR data set. To ensure correct input, use the
Configuration Tool to specify parameters again. The User response: None. This message is informational.
destination is the Tivoli Enterprise Monitoring Server The destination is the Tivoli Enterprise Monitoring
Engine log file, RKLVLOG. Server Engine log file, RKLVLOG.

KDFD152E KDFDUDSI - NO DATASETS SPECIFIED KDFD157E KDFDUDSI USER DATASET GROUPS

NOT INITIALIZED
Explanation: A data set group was specified without
data set entries. Explanation: Dataset group initialization failed for the
reasons stated in previous messages.
System action: Normal operation continues. The
invalid group is discarded. System action: Dataset groups are not available.

User response: Correct the data set name length in User response: Examine the error messages
the data set group definition in the KDFDUDSI member immediately preceding this message for the cause of
of the RKANPAR data set. To ensure correct input, use the failure. To ensure correct input, use the
the Configuration Tool to specify parameters again. The Configuration Tool to specify parameters again. The
destination is the Tivoli Enterprise Monitoring Server destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG. Engine log file, RKLVLOG.

88 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFDBG01 • KDFDSCTE

User response: This error should not occur. Contact

KDFDBG01 The contents of this message varies
IBM Software Support. The destination is the Tivoli
depending on debugging conditions in
Enterprise Monitoring Server Engine log file, RKLVLOG.
effect
Explanation: This message is generated when the
KDFDHSML LOGY OPEN FAILED, DSN= dsname,
product is executed in debugging mode. It should
RC= xxx REASON= yyy
appear only when diagnosing a problem with IBM
Software Support. Explanation: An attempt to open the HSM log data
set failed with the specified return and reason code.
System action: The message is written to the Tivoli
Enterprise Monitoring Server Engine log data set. System action: The request is attempted up to twice,
as necessary. If the third attempt fails, HSM log analysis
User response: Follow instructions from IBM Software
terminates.
Support. The destination is the Tivoli Enterprise
Monitoring Server Engine log file, RKLVLOG. User response: This error should not occur. Contact
IBM Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFDHSML INVALID REQUEST CODE - LOG
ANALYSIS TERMINATED
KDFDHSML SERVICE TASK ATTACH FAILED nnn -
Explanation: An invalid request was made of the HSM
LOG ANALYSIS TERMINATED
log analysis controller.
Explanation: An MVS ATTACH macro failed with the
System action: HSM Log analysis terminates.
specified return code.
User response: This error should not occur, contact
System action: HSM Log analysis terminates.
IBM Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG. User response: This error should not occur. Contact
IBM Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFDHSML LOGY ALLOCATION FAILED, DSN=
dsname, RC= xxx
KDFDHSML STOP REQUEST nnn - LOG ANALYSIS
Explanation: An attempt at allocating the HSM log
TERMINATED
data set has failed with the specified return and reason
code. Explanation: Termination of HSM log analysis
completed with code ’nnn’.
System action: The request is attempted up to twice,
as necessary. If the third attempt fails, HSM log analysis System action: None.
terminates.
User response: None. The destination is the Tivoli
User response: This error should not occur. Contact Enterprise Monitoring Server Engine log file, RKLVLOG.
IBM Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFDSCTE DATASET COLLECTOR TERM NOT
DONE, NOT PREVIOUSLY INITIALIZED
KDFDHSML LOGY CLOSE FAILED, DSN= dsname,
RC= xxx REASON= yyy Explanation: An error occurred during the initialization
of the data set collector.
Explanation: An attempt to close the HSM log data
set failed with the specified return and reason code. System action: None.

System action: Normal operation continues. User response: Review the RKLVLOG log for
previous error messages. The destination is the Tivoli
User response: This error should not occur. Contact Enterprise Monitoring Server Engine log file, RKLVLOG.
IBM Software Support. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFDSCTE DATASET COLLECTOR STOPPED.
SUCCESSFUL COUNT= count FAILURE
KDFDHSML LOGY GET FAILED, DSN= dsname, RC= COUNT=failures
xxx REASON= yyy
Explanation: The data set collector ran successfully.
Explanation: An attempt to read the HSM log data set
failed with the specified return and reason code. System action: None.

System action: The request is attempted up to twice, User response: None. The destination is the Tivoli
as necessary. If the third attempt fails, HSM log analysis Enterprise Monitoring Server Engine log file, RKLVLOG.
terminates.

Chapter 5. KDFD Messages 89

90 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 6. KDFH and KDFL Messages
This section provides OMEGAMON II for SMS messages with prefixes that range from KDFH to KDFL.

installation exit where it is specified as a number of 4K

KDFHS017 KDFDHSIN LOGY INVALID MEMBER
blocks. This error is written to the ITMS:Engine log file,
NAME/GDG VERSION LENGTH
RKLVLOG.
Explanation: An error was detected in the
System action: The installation default size (as
specification of the HSM LOGY data set. The length of
described above) is used.
the member name of the persistent data store or the
GDG version is either zero bytes or greater than eight User response: Adjust the size of the
bytes. MCDSDSPACESIZE parameter in RKANPAR member
KDFDHSIN to a value from zero to 2097152.
System action: HSM log analysis does not initialize.
User response: Check the specification in member
KDFL097E KDFLAPPL: REQUEST FOR
KDFDHSIN of the RKANPAR data set. The destination
HISTORICAL DATA FAILED - reason
is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG. Explanation: An attempt to retrieve historical
application data from the Persistent Data Store failed
because of reason. Possible values for reason include:
KDFHS018 KDFDHSIN LOGYDSPACESIZE VALUE
SPECIFIED EXCEEDS MAXIMUM v ERROR LOCATING DFPDSWKA
ALLOWABLE SIZE, USING v INVALID DFPDSWKA DETECTED
INSTALLATION DEFAULT. v NO JOBNAME INDEX SPECIFIED
Explanation: An error was detected in the v SETUP ERROR; RC=rc
specification of the LOGYDSPACESIZE parameter
which defines the maximum size of the data space used System action: Volume and data set information for
to contain information collected from the HSM LOGY this application is not returned to the requesting panel.
data set. This parameter is specified in kilobytes. The User response: Contact IBM Software Support. The
minimum allowable value is 0 and the maximum is destination is the Tivoli Enterprise Monitoring Server
2097152. If zero is specified, the installation default is Engine log file, RKLVLOG.
used. At the time of this writing, the IBM-defined default
maximum is 239 4K-blocks or 956K bytes. Be aware
that this value might be overridden in the IEFUSI KDFL098E KDFLAPPL: FETCH FAILED FOR APPL
installation exit where it is specified as a number of 4K TABLE; TC= rc -- DATA RETRIEVAL
blocks. This error is written to the ITMS:Engine log file, FROM PDS TERMINATING
RKLVLOG. Explanation: In retrieving historical application data
System action: The installation default size (as from the Persistent Data Store, the fetch routine of the
described above) is used. persistent data store returned with a non-zero return
code indicated in rc. Possible values for reason include:
User response: Adjust the size of the
LOGYDSPACESIZE parameter in RKANPAR member x’ff’ Invalid DFPDSTBL address passed.
KDFDHSIN to a value from zero to 2097152. x’fe’ DFPDSWKA not found.
x’fd’ Error obtaining the vector table of the
KDFHS019 KDFDHSIN MCDSDSPACESIZE VALUE persistent data store.
SPECIFIED EXCEEDS MAXIMUM
ALLOWABLE SIZE, USING For any of these errors, Contact IBM Software Support.
INSTALLATION DEFAULT.
System action: Volume and data set information for
Explanation: An error was detected in the this application is not returned to the requesting panel.
specification of the MCDSDSPACESIZE parameter
which defines the maximum size of the data space used User response: Contact IBM Software Support.
to contain information collected from the HSM MCDS
data set. This parameter is specified in kilobytes. The
KDFL100I KDFLAPPL: HISTORICAL DATA
minimum allowable value is 0 and the maximum is
FETCHED IS PAST RANGE; DATE
2097152. If zero is specified, the installation default is
REQUESTED = mm/dd/yy, TIME
used. At the time of this writing, the IBM-defined default
REQUESTED = hhmdd, DATE
maximum is 239 4K-blocks or 956K bytes. Be aware
RETURNED = mm/dd/yy, TIME
that this value may be overridden in the IEFUSI

© Copyright IBM Corp. 2006, 2007 91

KDFLAU01 • KDFLAU08

RETURNED = hhmmss
KDFLAU05 INITIALIZATION OF USER TABLE IN
Explanation: No qualifying data can be found for the PROGRESS
historical request.
Explanation: This message is written to the Tivoli
System action: Normal processing continues, but no Enterprise Monitoring Server Engine log data set during
data is returned. product initialization, and indicates that the user
authorization table is being initialized.
User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG. System action: Table initialization continues.
User response: None. This message is informational.
KDFLAU01 INITIALIZATION OF FORM TABLE IN The destination is the Tivoli Enterprise Monitoring
PROGRESS Server Engine log file, RKLVLOG.
Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during KDFLAU06 INITIALIZATION OF USER TABLE IS
product initialization, and indicates that initial loading of COMPLETE
the form authorization table is in progress.
Explanation: This message is written to the Tivoli
System action: Table initialization continues. Enterprise Monitoring Server Engine log data set during
product initialization, and indicates that initialization of
User response: None. This message is informational. the user authorization table has completed successfully.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG. System action: The user authorization table is
initialized.
KDFLAU02 INITIALIZATION OF FORM TABLE IS User response: None. This message is informational.
COMPLETE The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during
product initialization, and indicates that initialization of KDFLAU07 LOADING OF USER TABLE IN
the form authorization table has completed successfully. PROGRESS
System action: The table is initialized. Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during
User response: None. This message is informational. product initialization, and indicates that loading of the
The destination is the Tivoli Enterprise Monitoring user authorization table is in progress.
Server Engine log file, RKLVLOG.
System action: The table loads into virtual storage.
KDFLAU03 LOADING OF FORM TABLE IN User response: None. This message is informational.
PROGRESS The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during
product initialization, and indicates that the form KDFLAU08 LOADING OF USER TABLE IS
authorization table is being loaded into virtual storage. COMPLETE
System action: The table loads into virtual storage. Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during
User response: None. This message is informational. product initialization, and indicates that loading of the
The destination is the Tivoli Enterprise Monitoring user authorization table has completed successfully.
Server Engine log file, RKLVLOG.
System action: The user authorization table is loaded.
KDFLAU04 LOADING OF FORM TABLE IS User response: None. This message is informational.
COMPLETE The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
Explanation: This message is written to the Tivoli
Enterprise Monitoring Server Engine log data set during
product initialization, and indicates that loading of the
form authorization table has completed successfully.
System action: The table is loaded.
User response: None. This message is informational.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.

92 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Chapter 7. KDFS Messages
This section provides product-related messages with the prefix of KDFS.

Explanation: The data set I/O collector has abended

KDFS000I REQUESTED MESSAGE messsage_id
and an SVC dump has been taken.
IS NOT DEFINED
System action: The data set I/O collector will attempt
Explanation: An attempt was made to issue the
an orderly termination when the dump is complete.
message number displayed; however, that message has
not been defined to the message interface. User response: Contact IBM Software Support. Do
not delete the dump. The destination is the MVS system
System action: Processing continues as if the
console.
message had been issued.
User response: Contact IBM Software Support. The
KDFS004I CANDLE DATASET I/O SUBFUNCTION
destination is the MVS system console.
function_id RC = return_code
Explanation: An attempt to start the subfunction
KDFS001I DATASET I/O COLLECTION VERSION
displayed was unsuccessful, and displayed the return
version_number INITIALIZATION
code indicated in the message.
COMPLETE
System action: Initialization continues; however, some
Explanation: The data set I/O collector
functionality is lost.
version_number has successfully initialized and is ready
to monitor devices. User response: Contact IBM Software Support. The
destination is the MVS system console.
System action: Processing continues.
User response: None. This message is informational.
KDFS005W CANDLE DATASET I/O REQUIRES MVS
The destination is the MVS system console.
SUPPORT FOR SCOPE=COMMON
DATA SPACES
KDFS002W DATASET I/O COLLECTION VERSION
Explanation: The data set I/O collector must be run
version_number INITIALIZATION
on a level of MVS/ESA that provides support for
UNSUCCESSFUL.
SCOPE=COMMON data spaces.
Explanation: An attempt to initialize the data set I/O
System action: Initialization is terminated.
collector version_number was not successful.
User response: Do not attempt to run the data set I/O
System action: The data set I/O collector terminates.
collector on a level of MVS that does not meet the
Dataset I/O data is not available.
minimum requirement. The destination is the MVS
User response: There should be a message issued system console.
prior to this. Follow the instructions for the previous
message. The destination is the MVS system console.
KDFS006W ONLY ONE CANDLE DATASET I/O
COLLECTOR MAY RUN ON THE
KDFS0028I CANDLE DATASET I/O COLLECTOR SYSTEM AT A TIME
RESOURCE MANAGER CLEANUP IN
Explanation: The data set I/O collector has detected
PROGRESS
another Candle data set I/O collector to be active on the
Explanation: The collector has terminated abnormally, system.
and the resource manager routine has been called to
System action: Initialization of this collector is
clean up the environment.
terminated.
System action: None.
User response: Do not attempt to start a second
User response: None. This message is informational. collector. Make sure that only one data set I/O collector
There should be other messages issued previously that (subsystem) is installed.
require action. If there are no previous messages,
contact IBM Software Support.
KDFS007W CANDLE DATASET I/O module
UNABLE TO INSTALL I/O CONFIG EXIT,
KDFS003A SVC DUMP TAKEN FOR CANDLE RC=return_code
DATASET I/O COLLECTION
Explanation: The data set I/O collector module

© Copyright IBM Corp. 2006, 2007 93

KDFS008A • KDFS014A

specified attempted to install an I/O configuration exit.

KDFS011A CANDLE DATASET I/O module UNABLE
The attempt failed with the return code displayed.
TO FIX number PAGES OF STORAGE,
System action: Initialization of the collector RC=return_code
terminates.
Explanation: An attempt by the module specified to fix
User response: See the IBM manual, MVS/ESA number of pages of virtual storage failed with a the
Planning: Dynamic I/O Configuration for an explanation return code displayed.
of the displayed return code. If the return code as
System action: The collector terminates.
documented for the CONFCHG service indicates a
product problem, contact IBM Software Support. User response: If this is not a result of an installation
Otherwise, correct the problem with the system. problem, contact IBM Software Support. The destination
is the MVS system console.
KDFS008A CANDLE DATASET I/O UNABLE TO
OBTAIN PRIVATE STORAGE KDFS012A CANDLE DATASET I/O module
INTERNAL VALIDATION ERROR number
Explanation: An attempt to obtain private virtual
storage failed. Explanation: Routine module has determined that the
product has not been installed correctly. The number
System action: The collector terminates.
indicates the source of the problem.
User response: Remove any constraints upon the
System action: The collector does not initialize.
region available. Because almost all storage usage is
above the 16-megabyte line, this problem is likely the User response: Check the linkage editor message for
result of an artificial constraint on storage availability. module from the APPLY of the product or maintenance
The destination is the MVS system console. for error messages. If the return code is zero (0),
contact IBM Software Support. The destination is the
MVS system console.
KDFS009A CANDLE DATASET I/O module UNABLE
TO VALIDATE CONTROL BLOCK
control_block KDFS013I CANDLE DATASET I/O VER
version_number TERMINATING
Explanation: An attempt to validate the MVS control
block specified from within the module failed. Explanation: The collector is terminating.
System action: Depending upon the control block System action: The collector terminates. I/O statistics
involved, either the collector terminates or continues is not collected.
processing, bypassing the use of the control block
User response: If this is a result of a stop command,
specified in the message.
then no action is necessary. Otherwise, gather
User response: Contact IBM Software Support. The documentation, including any previous messages, and
destination is the MVS system console. contact IBM Software Support, if necessary. The
destination is the MVS system console.
KDFS010A CANDLE DATASET I/O module OBTAIN
FOR bytes OF storage_type KDFS014A CANDLE DATASET I/O module
RC=return_code SERVICE REQUEST request FAILURE,
RC= return_code
Explanation: An attempt by the module specified to
obtain the indicated amount of storage_type virtual Explanation: The module specified requested a
storage failed with the return code displayed. service of either MVS or the subsystem, and the
request failed with the return code displayed.
System action: The collector terminates.
System action: The collector terminates if the request
User response: Make sure that the installation has
is critical.
not artificially constrained the availability of the type of
virtual storage in question, either private or common. If User response: If the failure was for an MVS service,
storage is not artificially constrained, contact IBM ensure that it was not the result of an installation
Software Support. The destination is the MVS system problem. If necessary, contact IBM Software Support.
console. The destination is the MVS system console.

94 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFS015A • KDFS026W

KDFS015A CANDLE DATASET I/O module DEVICE KDFS022W CANDLE DATASET I/O module
TABLE FULL SUBTASK task_id FAILED - STOPPING
Explanation: The module specified attempted to add a Explanation: A prior attempt to restart subtask task_id
device type to an internal table, but the table had no by routine module was unsuccessful.
free entries.
System action: The collector terminates.
System action: The collector continues; however, data
User response: Contact IBM Software Support. The
is not collected for all devices.
destination is the MVS system console.
User response: Contact IBM Software Support. The
destination is the MVS system console.
KDFS023A CANDLE DATASET I/O module
ROUTINE routine FAILED return_code
KDFS016I CANDLE DATASET I/O - NO DEVICE reason_code
TYPES TO MONITOR
Explanation: The module specified called routine, and
Explanation: During initialization the collector found the called routine returned with the return and reason
that there were no device types installed that it was able codes displayed.
to monitor. It can monitor 3375, 3380, 3390, and future
System action: The collector attempts to continue
DASD devices.
functioning.
System action: The collector terminates.
User response: Review the appropriate user
User response: If there are device types installed that response:
the collector should monitor, contact IBM Software
OMEGAMON II for SMS
Support. Otherwise, no action is required.
This is an informational message only.
All other products
KDFS019A CANDLE DATASET I/O module ATTACH
Contact IBM Software Support.
OF task_id FAILED, RC=return_code
Explanation: An attempt by module to attach the MVS The destination is the MVS system console.
subtask specified failed with the return code displayed.
System action: The collector terminates. KDFS024A CANDLE DATASET I/O module service
INSTALLATION FAILED
User response: Refer to IBM Application
Development Reference: Services for Authorized Explanation: An attempt by routine module to install
Assembler Language Programs for an explanation of the service specified was not successful.
the return code. If the return code does not indicate an
installation problem, contact IBM Software Support. The System action: The collector terminates.
destination is the MVS system console. User response: Contact IBM Software Support. The
destination is the MVS system console.
KDFS020I CANDLE DATASET I/O module
SUBTASK task_id FAILED KDFS025W CANDLE DATASET I/O module
Explanation: Routine module has determined that RELEASE OF bytes storage RC=return_
subtask task_id has terminated unexpectedly. code

System action: The collector attempts to restart the Explanation: An attempt by routine module to release
subtask. the number of bytes of virtual storage specified failed
with the return code displayed.
User response: Contact IBM Software Support. The
destination is the MVS system console. System action: The collector continues processing
normally.

KDFS021I CANDLE DATASET I/O module User response: Contact IBM Software Support. The
RESTARTING SUBTASK task_id destination is the MVS system console.

Explanation: Routine module attempted to restart

subtask task_id after it unexpectedly terminated. KDFS026W CANDLE DATASET I/O module UNABLE
TO FREE number PAGES OF
System action: If the restart is successful, the STORAGE, RC=return_code
collector continues; otherwise the collector terminates.
Explanation: An attempt by routine module to free the
User response: None. The destination is the MVS specified number of pages of virtual storage was not
system console.

Chapter 7. KDFS Messages 95

KDFS027W • KDFS033I

successful. The return code from the PGSER service

KDFS030A MIGRATION SUBTASK ABEND, CODE=
displayed.
abend_code
System action: The collector continues processing
Explanation: The subtask used to arrange job and
normally.
data set information has abnormally terminated with the
User response: Refer to IBM Application displayed completion code.
Development Reference: Services for Authorized
System action: The collector terminates.
Assembler Language Programs for an explanation of
the return code. Contact IBM Software Support. The User response: Inspect the console log for messages
destination is the MVS system console. that can provide information as to why the ABEND
occurred. If problems persist, contact IBM Software
Support. The destination is the MVS system console.
KDFS027W CANDLE DATASET I/O module
UCBLOOK RC = return_code, DEVICE
NUMBER device KDFS031A CVAFSEQ ERROR READING VTOC:
RC= return_code, CVSTAT=xx
Explanation: An invocation of the UCBLOOK service
by routine module resulted in the return code displayed Explanation: A volume table of contents cannot be
for device number device. read using the CVAFSEQ macro. The volume for which
the VTOC failure occurred is identified in a separate
System action: The collector continues processing;
message displayed on the system console.
however, there is no data available for the specified
device. System action: Some data set names cannot be
resolved for the volume’s I/O activity.
User response: See the IBM MVS/ESA Planning:
Dynamic I/O Configuration manual for an explanation of User response: Consult the IBM MVS/DFP System
the return code. Contact IBM Software Support. The Programming Reference manual for an explanation of
destination is the MVS system console. the return code and CVSTAT fields returned by
CVAFSEQ. If problems persist, contact IBM Software
Support. The destination is the MVS system console.
KDFS028 CANDLE DATASET I/O COLLECTOR
RESOURCE MANAGER CLEANUP IN
PROGRESS KDFS032A UNABLE TO ACQUIRE VTOC
STORAGE: LENGTH= bytes,
Explanation: The collector has terminated abnormally,
RC=return_code
and the resource manager routine has been called to
clean up the environment. Explanation: The migration subtask was unable to
allocate the specified number of bytes of private storage
System action: None.
for its CVAF buffers. The return code displayed is
User response: None. This is an informational provided by the STORAGE macro.
message only. There should be other messages issued
System action: The collector terminates.
previously that require action. If there are no previous
messages, contact IBM Software Support. The User response: Increase the subsystem region size.
destination is the MVS system console. The destination is the MVS system console.

KDFS029A UNABLE TO ATTACH MIGRATION KDFS033I UNABLE TO READ VOLUME TABLE OF

SUBTASK, RC= return_code CONTENTS FOR volser
Explanation: The ATTACH macro used to create the Explanation: The migration subtask was unable to
migration subtask failed. The return code displayed read the VTOC of the displayed volser. An
represents the contents of register 15 passed back by accompanying console message is generated
the ATTACH macro. describing the precise cause of the error.
System action: The collector terminates. System action: Some data set names cannot be
resolved for the volume’s I/O activity.
User response: Refer to the IBM Application
Development Reference: Services for Authorized User response: Locate the diagnostic message that
Assembler Language Programs for an explanation of indicates the cause of the VTOC error and take any
the return code. If problems persist, contact IBM necessary corrective action. If problems persist, contact
Software Support. The destination is the MVS system IBM Software Support. The destination is the MVS
console. system console.

96 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFS034A • KDFS103E

KDFS034A CELL POOL FAILURE FOR SERVICE KDFS040W KDFS040W - KDFSPDEV HANG
service, RC=return_code DETECTED; VOLUME=vvvvvv
Explanation: The cell pool service specified failed with Explanation: While collecting space and fragmentation
the return code displayed. The migrator subtask uses information, OMEGAMON XE for Storage was unable to
callable cell pool services to create its internal table complete an LSPACE call for volume vvvvvv in less
entries. than 15 seconds. This might indicate a problem with the
volume or might be the result of a high rate of
System action: The collector terminates.
contention for the volume’s VTOC.
User response: The IBM Reference: Services for
System action: Processing for the specified volume is
Assembler Language Programs manual contains a
bypassed for this collection interval.
description of the return codes associated with the
failing service. Contact IBM Software Support. User response: Consider the amount of contention for
this volume at the time the message occurred. If this
does not explain the problem then you may wish to
KDFS035I UNABLE TO READ FORMAT 4 DSCB
review your EREP reports and check other sources to
WITH LSPACE, RC=return_code
make sure the volume is not under a hardware reserve
Explanation: The LSPACE macro used by the or otherwise improperly enqueued. The destination is
migrator subtask has failed with the return code the Tivoli Enterprise Monitoring Server Engine log file,
displayed. The volume for which the VTOC failure RKLVLOG.
occurred is identified in a separate message displayed
on the system console.
KDFS100E ATTACH FAILED FOR KDFSHSMM,
System action: Some data set names cannot be RC= rc
resolved for the volume’s I/O activity.
Explanation: An ATTACH macro failed with the
User response: Consult the IBM MVS/DFP System indicated return code.
Programming Reference manual for an explanation of
System action: HSM MCDS analysis is unavailable.
the return code and CVSTAT fields returned by
CVAFSEQ. If problems persist, contact IBM Software User response: Contact IBM Software Support. The
Support. The destination is the Tivoli Enterprise destination is the Tivoli Enterprise Monitoring Server
Monitoring Server Engine log file, RKLVLOG. Engine log file, RKLVLOG.

KDFS036I UNABLE TO OBTAIN DEVICE CELL, KDFS101I MCDS ANALYSIS HAS TERMINATED
DATA LOST
Explanation: The HSM MCDS analysis feature
Explanation: The migrator subtask has run out of cell terminated.
pool storage to record data set I/O information.
System action: None.
System action: Some information about data set I/O
User response: None. The destination is the Tivoli
activity is lost.
Enterprise Monitoring Server Engine log file, RKLVLOG.
User response: Ensure that the archive subtask is
running in the subsystem address space. If problems
KDFS102E ACB ACQUISITION FAILED,
persist, contact IBM Software Support. The destination
COMPLETION CODE compl_code
is the MVS system console.
Explanation: A request for an ACB failed with the
indicated completion code.
KDFS037A INSUFFICIENT STORAGE TO READ
VTOC FOR VOLUME volser System action: The HSM MCDS analysis feature is
unavailable.
Explanation: The migrator subtask was unable to fit
the VTOC for the volume specified in the space it had User response: Contact IBM Software Support. The
allocated. destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
System action: The collector terminates.
User response: Contact IBM Software Support. The
KDFS103E UNABLE TO ALLOCATE MIGRATION
destination is the MVS system console.
CONTROL DATASET, RC= rc
Explanation: A request to allocate the HSM MCDS
failed with the indicated return code.
System action: The HSM MCDS analysis feature is
unavailable.

Chapter 7. KDFS Messages 97

KDFS104E • KDFS14A

User response: Contact IBM Software Support. The

KDFS109E MCDS SUBTASK ABEND,
destination is the Tivoli Enterprise Monitoring Server
COMPLETION CODE compl_code
Engine log file, RKLVLOG.
Explanation: The HSM MCDS analysis subtask
abended with the indicated completion code.
KDFS104E OPEN FAILED FOR MIGRATION
CONTROL DATASET System action: The HSM MCDS analysis feature is
unavailable.
Explanation: A request to open the HSM MCDS
failed. User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
System action: The HSM MCDS analysis feature is
Engine log file, RKLVLOG.1
unavailable.
User response: Contact IBM Software Support. The
KDFS220E MCDS SUBTASK ABEND,
destination is the Tivoli Enterprise Monitoring Server
COMPLETION CODE S01D
Engine log file, RKLVLOG.
Explanation: The HSM MCDS analysis subtask
abended with the indicated completion code.
KDFS105E ERROR IN VSAM START REQUEST
System action: The HSM MCDS analysis feature is
Explanation: A request to browse the HSM MCDS
unavailable.
failed.
User response: Contact IBM Software Support. The
System action: The HSM MCDS analysis feature
destination is the Tivoli Enterprise Monitoring Server
terminates.
Engine log file, RKLVLOG.2
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
KDFS110E INVALID POST CODE RECEIVED,
Engine log file, RKLVLOG.
CODE= post_code
Explanation: The indicated invalid post code was
KDFS106E ERROR IN TERMINATION REQUEST
received from the HSM MCDS analysis subtask.
Explanation: A request to close and deallocate the
System action: The HSM MCDS analysis feature
HSM MCDS failed.
terminates.
System action: HSM MCDS processing continues.
User response: Contact IBM Software Support. The
User response: Contact IBM Software Support. The destination is the Tivoli Enterprise Monitoring Server
destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Engine log file, RKLVLOG.
KDFS111E BLDL for KDFSHSMM FAILED, RC= rc
KDFS107E ERROR IN VSAM ccccc REQUEST, RC=
Explanation: Module KDFSHSMM is not available.
return_code, REASON= reason_code
System action: The MCDS analysis feature is not
Explanation: A VSAM POINT or GET request failed
available.
with the indicated return and reason codes.
User response: Verify the RKANMODL concatenation.
System action: HSM MCDS processing continues.
If in doubt, contact IBM Software Support. The
User response: Contact IBM Software Support. The destination is the Tivoli Enterprise Monitoring Server
destination is the Tivoli Enterprise Monitoring Server Engine log file, RKLVLOG.
Engine log file, RKLVLOG.
KDFS14A CANDLE DATASET I/O module
KDFS108E SAVEAREA STACK EXHAUSTED SERVICE REQUEST request FAILURE,
RC=return_code
Explanation: An internal error occurred.
Explanation: The module specified requested a
System action: The HSM MCDS analysis feature is service of either MVS or the subsystem, and the
unavailable. request failed with the return code displayed.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
1. “Message KDFHS019” on page 91 explains the source of
this message and describes a workaround.
2. “Message KDFHS019” on page 91 explains the source of
this message and describes a workaround.

98 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

 KDFS15A • KDFS206I

System action: The collector terminates if the request

KDFS202E DSPSERV CREATE FAILED, RC= rc
is critical.
Explanation: An MVS DSPSERV TYPE=CREATE
User response: If the failure was for an MVS service,
request failed with the indicated return code.
ensure that it was not the result of an installation
problem. If necessary, contact IBM Software Support. System action: The HSM MCDS analysis feature
terminates.
KDFS15A CANDLE DATASET I/O module DEVICE User response: Contact IBM Software Support. The
TABLE FULL destination is the Tivoli Enterprise Monitoring Server
Engine log file, RKLVLOG.
Explanation: The module specified attempted to add a
device type to an internal table, but the table had no
free entries. KDFS203E ALESERV REQUEST FAILED, RC= rc
System action: The collector continues; however, data Explanation: An MVS ALESERV request failed with
is not collected for all devices. the indicated return code.
User response: Contact IBM Software Support. System action: The HSM MCDS analysis feature
terminates.
KDFS17A CANDLE DATASET I/O DSPSERV User response: Contact IBM Software Support. The
number FAILED, return_code- destination is the Tivoli Enterprise Monitoring Server
reason_code Engine log file, RKLVLOG.
Explanation: An attempt to create the data space
number specified failed. The DSPSERV request KDFS204E STIMERM REQUEST FAILED, RC= rc
returned the return_code and reason_code.
Explanation: An MVS STIMERM request failed with
System action: The collector does not initialize. the indicated return code.
User response: Refer to the IBM Application System action: The HSM MCDS analysis feature
Development Reference: Services for Authorized terminates.
Assembler Language Programs for explanations of the
User response: Contact IBM Software Support. The
return and reason codes. If the return and reason codes
destination is the Tivoli Enterprise Monitoring Server
do not indicate a problem in your installation, contact
Engine log file, RKLVLOG.
IBM Software Support.

KDFS205I MCDS ANALYSIS SUBTASK STARTING

KDFS18A CANDLE DATASET I/O ALESERV
QUIESCE
number FAILED, RC=return_code
Explanation: The HSM MCDS analysis feature is
Explanation: An attempt to add an entry to an access
being shut down.
list for data space number failed. The return code from
ALESERV was displayed. System action: HSM MCDS analysis terminates.
System action: The collector does not initialize. User response: None. This message is informational.
The destination is the Tivoli Enterprise Monitoring
User response: Refer to IBM Application
Server Engine log file, RKLVLOG.
Development Reference: Services for Authorized
Assembler Language Programs for an explanation of
the return code. If the return code does not indicate a KDFS206I MCDS ANALYSIS SUBTASK HAS
problem in your installation, contact IBM Software TERMINATED
Support.
Explanation: The MCDS analysis feature has
terminated.
KDFS201E STORAGE OBTAIN REQUEST FAILED
System action: Normal operation continues.
Explanation: An MVS STORAGE request failed.
User response: None. This message is informational.
System action: The HSM MCDS analysis feature The destination is the Tivoli Enterprise Monitoring
terminates. Server Engine log file, RKLVLOG.
User response: Restart the Tivoli Enterprise
Monitoring Server with a larger region size. If the error
persists, contact IBM Software Support. The destination
is the Tivoli Enterprise Monitoring Server Engine log file,
RKLVLOG.

Chapter 7. KDFS Messages 99

KDFS207I • KDFSHL00

Tivoli Enterprise Monitoring Server Engine log file,

KDFS207I MCDS DATASPACE LOCATED AT
RKLVLOG.
address, LENGTH len
Explanation: The HSM MCDS data space with the
KDFS211E FAILURE IN ACQUISITION OF MCDS
indicated length was created at the indicated address.
DSN, RC= rc
System action: The HSM MCDS analysis feature
Explanation: Locating the data set name of the HSM
proceeds.
MCDS failed with the indicated return code.
User response: None. This message is informational.
System action: The HSM MCDS analysis feature
The destination is the Tivoli Enterprise Monitoring
terminates.
Server Engine log file, RKLVLOG.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
KDFS208I MCDS DATASPACE ID= id, STOKEN=
Engine log file, RKLVLOG.
token
Explanation: These are the generated names of the
KDFS212E INVALID DATA DETECTED FOR dsname
HSM MCDS data space.
Explanation: An invalid HSM MCDS record was
System action: The HSM MCDS analysis feature
detected.
proceeds.
System action: The HSM MCDS analysis feature
User response: None. This message is informational.
continues.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG. User response: None. This message is informational.
The destination is the Tivoli Enterprise Monitoring
Server Engine log file, RKLVLOG.
KDFS209E INTERNAL LOGIC ERROR
Explanation: An internal error occurred.
KDFS213E SVC DUMP WILL BE REQUESTED
System action: The HSM MCDS analysis feature
Explanation: HSM MCDS analysis abended and
terminates.
requested a dump.
User response: Contact IBM Software Support. The
System action: The HSM MCDS analysis feature
destination is the Tivoli Enterprise Monitoring Server
terminates.
Engine log file, RKLVLOG.
User response: Contact IBM Software Support. The
destination is the Tivoli Enterprise Monitoring Server
KDFS210E MCDS DATASPACE IS TOO SMALL
Engine log file, RKLVLOG.
Explanation: The HSM MCDS data space is too small
for general use.
KDFS214E SDUMPX REQUEST FAILED, RC= rc
For example, an error condition occurs when the
Explanation: An MVS SDUMPX request failed with
specification of the MCDSDSPACESIZE parameter is
the indicated return code.
exceeded. This parameter defines the maximum size of
the data space used to contain information collected System action: The HSM MCDS analysis feature
from the HSM MCDS data set. This parameter is continues to terminate.
specified in kilobytes. The minimum allowable value is 0
and the maximum is 2097152. If zero is specified, the User response: Contact IBM Software Support. The
installation default is used. At the time of this writing, the destination is the Tivoli Enterprise Monitoring Server
IBM-defined default maximum is 239 4K-blocks or 956K Engine log file, RKLVLOG.
bytes. Please be aware that this value may be
overridden in the IEFUSI installation exit where it is KDFSHL00 ABEND abend_code AVERTED IN RC++
specified as a number of 4K blocks. This error is written PACKAGE
to the ITMS:Engine log file, RKLVLOG.
Explanation: Error recovery processing detected that
System action: The HSM MCDS analysis feature the specified abend occurred during processing.
terminates.
System action: Error recovery is started.
User response: Increase the MCDSDSPACESIZE
parameter in the KDFDHSIN member of the RKANPAR User response: Contact IBM Software Support. The
data set and recycle the Tivoli Enterprise Monitoring destination is the MVS system console.
Server. Using the Configuration Tool to specify again
ensures correct parameter input. The destination is the

100 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 KDFSHL01 • KDFSHSML

KDFSHL01 ABEND abend_code AVERTED IN KDFSHSML HSMLOG DATASPACE XXXXXXXX

SESSION INITIALIZATION CREATED
Explanation: Error recovery processing detected that Explanation: The HSM log analysis data space has
the specified abend occurred during processing. been successfully created.
System action: Error recovery is started. System action: HSM log analysis initialization
continues.
User response: Contact IBM Software Support. The
destination is the MVS system console. User response: None. The destination is the Tivoli
Enterprise Monitoring Server Engine log file, RKLVLOG.
KDFSHL02 ABEND abend_code AVERTED IN
SESSION DISPATCHER KDFSHSML HSMLOG PROCESSING BYPASSED
DUE TO ERROR
Explanation: Error recovery processing detected that
the specified abend occurred during processing. Explanation: A GET request from the HSM log data
set has failed.
System action: Error recovery is started.
System action: The request is attempted up to twice,
User response: Contact IBM Software Support. The
as necessary. If the third attempt fails, HSM log analysis
destination is the MVS system console.
terminates.
User response: This is an internal error. Contact IBM
KDFSHL03 ABEND abend_code AVERTED IN
Software Support. he destination is the Tivoli Enterprise
SESSION TERMINATION
Monitoring Server Engine log file, RKLVLOG.
Explanation: Error recovery processing detected that
the specified abend occurred during processing.
TKDFSHSML macro REQUEST - RC = 99999999
System action: Error recovery is started. 99999999
User response: Contact IBM Software Support. The Explanation: A DSPSERV or ALESERV request
destination is the MVS system console. failed.
System action: HSM log analysis terminates.
KDFSHL04 ABEND abend_code AVERTED IN
User response: This is an internal error. Contact IBM
CREATING SESSION ENVIRONMENT
Software Support. The destination is the Tivoli
Explanation: Error recovery processing detected that Enterprise Monitoring Server Engine log file, RKLVLOG.
the specified abend occurred during processing.
System action: Error recovery is started. KDFSHSML MESSAGE ARC nnnnn FORMAT
ERROR DETECTED - TEXT:
User response: Contact IBM Software Support. The
destination is the MVS system console. Explanation: An error occurred while parsing the
specified HSM log message.
KDFSHL05 ABEND abend_code AVERTED WHEN System action: The message is bypassed.
DESTROYING ENVIRONMENT
User response: This error should not occur. Contact
Explanation: Error recovery processing detected that IBM Software Support. The destination is the Tivoli
the specified abend occurred during processing. Enterprise Monitoring Server Engine log file, RKLVLOG.

System action: Error recovery is started.

KDFSHSML MESSAGE CONTROL TABLE ERROR
User response: Contact IBM Software Support. The DETECTED - XXXXXXXX
destination is the MVS system console.
Explanation: This is an internal error that should not
occur.
KDFSHSML HSMLOG DATASPACE AT CAPACITY -
nnnnnnnn BLOCKS System action: The HSM log analysis data space is
rebuilt.
Explanation: The HSM log analysis data space is full.
User response: This error should not occur. Contact
System action: The data space is rebuilt. IBM Software Support. The destination is the Tivoli
User response: Consider increasing the site default Enterprise Monitoring Server Engine log file, RKLVLOG.
data space size. The destination is the MVS system
console.

Chapter 7. KDFS Messages 101

KDFSTR01

KDFSTR01 RC++ START - SESSION LIST AT

address
Explanation: Informational message printed on the
Tivoli Enterprise Monitoring Server Engine log data set.
This message lists the address of the product anchor
control block.
System action: None.
User response: None. This message is informational.
The destination is the MVS system console.

102 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 8. KRC Messages
This section provides OMEGAMON II for SMS messages with the prefix of KRC.

failed. This message is preceded by a KRCXSY04

KRCXSY01 PRIMARY SERVER NOT FOUND IN
message when the Create_Path was issued.
PROFILE
System action: None.
Explanation: A server designated as the primary
server cannot be found in the server’s member of the User response: Check the availability of the primary
profile. This message might indicate that the server. The server might not have completed
primary=YES statement in the profile has been removed initialization or it might have abnormally ended. Restart
or is syntactically incorrect. the server if it has abended. You cannot log on to
OMEGAMON II unless you designate a primary server
System action: None.
in the profile or specify a remote server ID.
User response: Verify that the server profile contains
the primary=YES statement or correct any syntax
KRCXSY06 rnode: {LOCALID= locname
problems with the statement. You cannot log on to
REMOTEID= remname MODE= logmode}
OMEGAMON II unless you designate a primary server
snode: {SERVER= srvrname USER=
in the profile or specify a remote server ID.
xsys}
Explanation: This message displays the path string
KRCXSY02 RcPackage not found
used to log on to a specified data server. This
Explanation: A global anchor cannot be found during information is derived from the configuration data in the
product initialization. This indicates an internal problem profile and is useful in determining server connection
with OMEGAMON II for SMS. problems.
System action: None. System action: None.
User response: Contact IBM Software Support. User response: None.

KRCXSY03 SQL1 REQUEST SQL1_CreatePath

SUCCESSFUL FOR sssss SQL1
STATUS ddd(xx)
Explanation: This message informs you that you have
successfully connected to server sssss.
System action: None.
User response: None.

KRCXSY04 SQL1 REQUEST rrrrr FAILED FOR sssss

SQL1 STATUS ddd(xx)
Explanation: The server failed to respond to the
specified request. This message might indicate that
OMEGAMON II is experiencing problems connecting to
the server.
System action: None.
User response: Check the availability of the server to
which you are attempting to connect. Try to reconnect
when the server becomes available using the Specify
Systems for Cross-system Monitoring panel within an
OMEGAMON II session.

KRCXSY05 COULD NOT CONNECT TO PRIMARY

SERVER
Explanation: The Create_Path to the primary server

© Copyright IBM Corp. 2006, 2007 103

104 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Part 2. Problem determination
In problem determination, you start with a symptom, or set of symptoms, and trace them back to their
cause. Problem determination is not the same as problem solving. However, during the process of problem
determination you might obtain sufficient information to enable you to solve a problem. In some cases, you
cannot solve a problem after determining its cause. For example, a performance problem might be caused
by a limitation of your hardware. However, in the following situations, problem determination can lead to
problem solving:
v End-user errors
v Application programming errors
v System programming errors, such as in resource definitions

This section summarizes the types of problem determination information that is available and includes links
to that information:
Troubleshooting overview
This chapter describes the troubleshooting process and provides summary descriptions of the logs
that provide essential troubleshooting information:
v “The troubleshooting process” on page 107
v “Sources of troubleshooting data” on page 109

Note: The Appendix A, “General problem determination for Tivoli OMEGAMON XE monitoring
agents on z/OS,” on page 133 appendix provides information that is valid for all
OMEGAMON XE monitoring agents, including specific locations of log files.
Troubleshooting tips
These chapters describe common problems that can occur with Tivoli OMEGAMON XE for
Storage on z/OS and available workarounds. These problems are grouped into the following
categories:
v Chapter 10, “Troubleshooting installation and configuration,” on page 113
v Chapter 11, “Troubleshooting data collection,” on page 115
– “Tips regarding the collection of diagnostic data” on page 146
– “Collection of monitoring data” on page 115
– “Generation of data reports” on page 118
v Chapter 12, “Troubleshooting performance issues,” on page 123
v Chapter 13, “Troubleshooting error conditions,” on page 125
v Chapter 14, “Troubleshooting specific product features,” on page 129

Note: IBM Tivoli Monitoring Problem Determination Guide, GC32-9458 provides information about
problems and workarounds for the basic components of IBM Tivoli Monitoring.
Other sources of troubleshooting information
Consult the following resources for additional help with troubleshooting:
v Product Support Web page for Tivoli OMEGAMON XE for Storage on z/OS:
http://www-306.ibm.com/software/sysmgmt/products/support/
IBMTivoliOMEGAMONXEforStorage.html. This Web page provides links to Technotes, PSP
Buckets, and Shop zSeries information, among many other topics.
v Appendix C, “Support information,” on page 161 appendix for other sources of support for
problem determination and problem solving.
v IBM Tivoli Open Process Automation Library at the following Web site: http://catalog.lotus.com/
wps/portal/tm. The Web site includes problem-solving topics such as the following items:

© Copyright IBM Corp. 2006, 2007 105

 “IBM Tivoli Monitoring Version 6.1, Administrator Workspace and Views”
In an enterprise environment, administrators are always challenged to make sure all
critical components are functioning according to design specifications. This document
describes how to create 10 workspace views within IBM Tivoli Monitoring, Version 6.1,
to help administrators better manage the enterprise production environment. These
views give a compact view of the enterprise.
“IBM Tivoli Monitoring Version 6.1, Remotely Start/Stop Situations”
In some cases, you might lack direct access to the Tivoli Enterprise Portal, but need to
restart a situation. You can use the command-line interface to achieve this goal. This
document describes how.
“IBM Tivoli Monitoring, Creating a Moveable HUB TEMS on z/OS”
The hub Tivoli Enterprise Monitoring Server as configured by Configuration Tool is by
definition static. It cannot be moved from one LPAR to another without reconfiguring
every component that connects to it. The technique described here allows the hub
monitoring server to be relocated to any suitable LPAR in the environment with no
changes, and with minimal disruption to all components connecting to it.

106 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 9. Troubleshooting overview
This section describes the troubleshooting process and provides summary descriptions of the logs that
provide essential troubleshooting information.

The troubleshooting process

This section describes how to analyze and resolve problems that you might have with the product. Answer
the questions step by step.
1. Does the problem seem to be caused by or related to the monitoring agent?

Note: Avoid a basic problem with Tivoli OMEGAMON XE for Storage on z/OS by understanding the
basic product architecture, as described here. The Tivoli OMEGAMON XE for Storage on z/OS
monitoring agent must report to a local Tivoli Enterprise Monitoring Server that is installed and
configured in the same z/OS address space. The local server for each agent must report to a
hub server. The hub server can be running on any supported system. (If located in a z/OS
system, the hub server can also act as the local server for a specific monitoring agent.)

Your answer: Do this next:

No. Refer to IBM Tivoli Monitoring Problem Determination Guide. This document helps you resolve
problems beyond a specific monitoring agent, such as problems with the Tivoli Enterprise Portal
and problems with historical reporting.
Yes. Go to Step 2.

Do not worry if you cannot answer this question with certainty at this stage. Later in this process, you
generate trace logs that can pinpoint the source of a problem.
2. Has required maintenance been applied?
v To answer this question for the monitoring agent, consult the Program Directory to confirm that all
required PTFs have been installed. Also check the PSP bucket for updated requirements, as follows:
a. Access the “Technical help database page for mainframe Preventive Service Planning (PSP)
buckets” Web page: http://www14.software.ibm.com/webapp/set2/psp/srchBroker
b. Find relevant PSP Buckets. Search for PSP Buckets that have the Tivoli OMEGAMON XE for
Storage on z/OS, V4.1.0 prefix: OMXES4100.
c. Consult each PSP Bucket to learn what PTFs are required.
d. Access the Shop z-Series Web site to obtain the PTFs: https://www14.software.ibm.com/
webapp/ShopzSeries/ShopzSeries.jsp
v For the Tivoli Management Services Components:
– Consult IBM Software Support Technotes, if any.
– Determine whether fix packs are available for any components that run on distributed computers.
For example, a fix pack might be available for a Tivoli Enterprise Portal that is running on a
Windows computer.
– See IBM Support Assistant for updates.

Your answer: Do this next:

No. Apply maintenance and see whether the problem persists.
Yes. Go to Step 3.

3. When does the problem occur, or how does the problem occur?

Note: During this step, you might review the cross-referenced documentation and fail to recognize a
the solution to your problem. The remaining steps of this process help you understand the

© Copyright IBM Corp. 2006, 2007 107

 problem better and find documented solutions that are not obvious at first.

Problem area: Refer to: *

Installation and configuration of the monitoring Chapter 10, “Troubleshooting installation and configuration,” on
agent. page 113 *
Data collection. Chapter 11, “Troubleshooting data collection,” on page 115 *
v “Tips regarding the collection of diagnostic data” on page
146
v “Collection of monitoring data” on page 115
v “Generation of data reports” on page 118
– “Real-time data reports” on page 118
– “Short-term historical data reports” on page 118
– “Long-term historical data reports” on page 119
Performance issues. Chapter 12, “Troubleshooting performance issues,” on page
123 *
Error conditions. Chapter 13, “Troubleshooting error conditions,” on page 125
Specific product features, such as Dataset Attributes Chapter 14, “Troubleshooting specific product features,” on
Database or IBM TotalStorage Productivity Center page 129 *
launch.

* If the cross-references in this step do not provide solutions to your problem, go to Step 4.
4. Can trace logs reveal details about the problem?

Your answer: Do this next:

No. Trace logs frequently reveal the source of a problem. However, if you are certain that trace logs
cannot help you, go to Step 7 on page 109.
Yes. Read about logging in “Sources of troubleshooting data” on page 109. Set up trace logs for the
affected component. Also see Appendix A, “General problem determination for Tivoli
OMEGAMON XE monitoring agents on z/OS,” on page 133 for information on these topics:
v Locations of IBM Tivoli Monitoring trace logs.
v Locations of trace logs for a specific monitoring agent.
v Setting up RAS1 tracing, interpreting those logs, and sending logs to IBM Software Support.
v Setting up OMEGAMON II debugging logs, interpreting those logs, and sending logs to IBM
Software Support, see
Note: The unique utilities in Tivoli OMEGAMON XE for Storage on z/OS, such as the Storage
Toolkit and Dataset Attributes Database, log their messages to the Tivoli Enterprise Portal log.
Consult the Tivoli Enterprise Portal log when you are troubleshooting these utilities.

Note: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade
performance of the monitoring agent. You must restore RAS1 tracing to the minimal
KBB_RAS1=ERROR setting after problem diagnosis is completed.
5. Can more focussed trace logs reveal more details about the problem?

Your answer: Do this next:

No. Go to Step 7 on page 109.
Yes. Define a different type of trace logging, using the methods that are referenced in Step 4.
Note: See the troubleshooting tips in “Tips regarding the collection of diagnostic data” on page
146, as needed, to ensure successful capture of diagnostic data.

108 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 Note: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade
performance of the monitoring agent. You must restore RAS1 tracing to the minimal
KBB_RAS1=ERROR setting after problem diagnosis is completed.
6. Is there documentation for the problem that the logs reveal?
The trace logs might provide helpful key words regarding your problem, including unique message
numbers. Use key words regarding your problem to search in the following sources:
v Problem Determination Guide for the monitoring agent
v IBM Tivoli Monitoring Problem Determination Guide, GC32-9458
v RETAIN database

Your answer: Do this next:

No. Go to Step 7.
Yes. Follow the instructions that are documented for the problem. Then go to Step 7.

7. Is the problem solved?

Your answer: Do this next:

No. Compile information about the problem and contact IBM Software Support. See “Capturing z/OS
logs to send to IBM Software Support” on page 165.
Yes. (No further action is required.)

Sources of troubleshooting data

The primary troubleshooting feature is logging. Logging refers to the text messages and trace data
generated by the software. Messages and trace data are sent to an output destination, such as a console
screen or a file.

Typically, text messages relay information about the state and performance of a system or application.
Messages also alert the system administrator to exceptional conditions when they occur. Consult the
explanation and operator response associated with the displayed messages to determine the cause of the
failure.

Trace data captures information about the current operating environment when a component or application
fails to operate as designed. IBM Software Support personnel use trace information to determine the
source of an error or unexpected condition. Refer to the chapter on diagnostic tools in the IBM Tivoli
Monitoring: Problem Determination Guide for more information about trace tools.

Collecting data
If you have a problem that you are unable to solve using the information in this guide, gather the following
information that relates to the problem and contact IBM Software Support for further assistance.
v Monitored application file.
v Appropriate RAS1 trace output.
v Description of the operation scenario that led to the problem.
v Incorrect output, such as Tivoli Enterprise Portal screen prints or a description of what you observed, if
applicable.
v Log files from failing systems. You can collect all logs or logs of a certain type such as, RAS (reliability,
availability, and serviceability) trace logs or message logs. Refer to “About log files for product
components” on page 110 for information about the locations of logs.
v Application information, such as version number and patch level.
v Operating system version number and patch level.

Chapter 9. Troubleshooting overview 109

v Messages and other information displayed on the screen.
v Version number of the following members of the monitoring environment:
– IBM Tivoli Monitoring. Also provide the patch level, if available.
– Monitoring agent version number.
– Tivoli Enterprise Portal. Select About Tivoli Enterprise Portal ... from the Help menu.

Note: The version number of the Tivoli Enterprise Portal and the Tivoli Enterprise Portal Server must
always be synchronized.
v If the systems stops on Windows, collect the drwtsn32.log and user.dmp files, if available. The files
are located in the following path:
\Documents and Settings\All Users\Documents\DrWatson

See the chapter on diagnostic tools in the IBM Tivoli Monitoring: Problem Determination Guide for more
information about trace tools.
1. Enter the following command at the command prompt to enable the Dr. Watson tool as default
debugger:
drwtsn32 –i 2
2. Enter the following command at the command prompt to open the configuration window of the Dr.
Watson tool:
drwtsn32

About log files for product components

The Tivoli Enterprise Monitoring Agent generates log files that contain messages and trace information.
The log files contain message and trace information about the events and processing being performed.
Log files provide a complete record of system activity, not just of problems. The log files are created when
you start the IBM Tivoli Monitoring components.

When you encounter a problem, check the messages in the log files to determine if the source is a
problem in your environment or with an IBM Tivoli Monitoring product. If you determine that the problem is
caused by a product defect, follow the instructions for contacting IBM Software Support in the Appendix C,
“Support information,” on page 161. See “Collecting logs for reproducible problems that are reported as
Tivoli Enterprise Portal client problems” on page 134 for the locations of log files. The location of the log
depends on the client type and operating system the client is running on. The following sections provide
locations of the fundamental types of logs:
v Logs for components on distributed systems:
– “Collecting logs for the Tivoli Enterprise Portal desktop client” on page 134
– “Collecting logs for the Tivoli Enterprise Portal browser client” on page 135
– “Additional logs to collect: Tivoli Enterprise Portal Server logs, Tivoli Enterprise Monitoring Server
logs, and data warehousing logs” on page 135
v Logs for components on z/OS systems: “Collecting logs on the z/OS system” on page 137
IBM Software Support might request some or all of these files while investigating a problem you have
reported. Also, you might be asked to set a trace in the client and then collect the log. Trace logging is a
fundamental tool for troubleshooting in cases where a problem is reproducible.

Note: Some of the tracing options produce large amounts of trace information. Therefore, monitor the disk
or spool space when activating tracing to prevent your disk or spool from reaching capacity. Return
the trace settings to the default settings after the desired trace information has been collected.

Log files for each of the components are explained in the following sections.

110 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Tivoli Enterprise Monitoring Server on z/OS
The log files for Tivoli Enterprise Monitoring Server on z/OS are created as defined in the started
procedure when you start the Tivoli Enterprise Monitoring Server. View the log files with any text editor.

When you investigate problems with Tivoli Enterprise Monitoring Server, view the sysout data sets or spool
files in the job output and view the z/OS system log for any messages that might pertain to the problem.

Tivoli Enterprise Monitoring Server on Windows or UNIX

The log files are created automatically when you start Tivoli Enterprise Monitoring Server on Windows or
UNIX. View the log files with any text editor. Whenever the Tivoli Enterprise Monitoring Server is started,
the log files are purged and written anew for the current work session. If you want to preserve the log file
from the last work session, you must rename it or copy it to another directory before starting Tivoli
Enterprise Monitoring Server.

When you investigate problems with Tivoli Enterprise Monitoring Server, use the Windows Event Viewer to
check that the Tivoli Enterprise Monitoring Server started correctly and to look for errors.

Tivoli Enterprise Portal

The log files are created automatically when you start Tivoli Enterprise Portal. View the log files with any
text editor. Whenever you start a new work session, the log files are purged and written again for the
current work session. To preserve the log file from the last work session, rename it or copy it to another
directory before starting the Tivoli Enterprise Portal.

In desktop mode, the log files are named kcjras1.log and KCJ.log. KCJ.log contains any errors that
might have been written by the Sun Java™ libraries that are used by the Tivoli Enterprise Portal desktop
client. In browser mode, the log file is named javalog.txt or is viewed in Java Console of Internet Explorer.
You might need to edit your Internet Explorer browser options to enable the error log file on your local
system. Refer to the Tivoli Enterprise Portal online help for information on enabling the log file. You can
change the level of tracing by using the File > Trace Options... window.

In addition, logon prompts and progress messages are displayed in the Logon window status bar. This
area is also used to display error messages.

When you investigate problems with Tivoli Enterprise Portal, use the Windows Event Viewer to check that
the Tivoli Enterprise Portal Server started correctly and to look for errors.

Tivoli Enterprise Portal Server

The log files are created automatically when you start Tivoli Enterprise Portal Server. The log file is named
in “Additional logs to collect: Tivoli Enterprise Portal Server logs, Tivoli Enterprise Monitoring Server logs,
and data warehousing logs” on page 135. View the log files with any text editor. Whenever the Tivoli
Enterprise Portal Server is started, the log files are purged and written again for the current work session.

When the log file reaches a 5 MB size limit, it is closed. A new file is created, with the sequential number
added to make the file name unique. By default, 5 files are saved over the life of the Tivoli Enterprise
Portal Server, up to a total of 32 files maximum. You can change these values through the Manage Tivoli
Monitoring Services application as follows:
1. Right-click the Tivoli Enterprise Portal Server row.
2. Select Advanced in the pop-up menu.
3. Select the Edit Trace Parms menu item to access the dialog box where you can configure logging
behavior.

When you investigate problems with Tivoli Enterprise Portal Server, use the Windows Event Viewer to
check that the Tivoli Enterprise Portal Server started correctly and to look for errors.

Chapter 9. Troubleshooting overview 111

You can change trace settings using the Manage Tivoli Enterprise Monitoring Services Action >
Advanced > Edit Trace Parms... window. You can also use the Service Console, accessible from the
Tivoli Enterprise Portal Server using an Internet Explorer browser, to read logs and turn on traces for
remote product diagnostics and configuration.

For more information about troubleshooting problems on Tivoli Enterprise Portal Server, refer to IBM Tivoli
Monitoring: Problem Determination Guide.

IBM Tivoli Data Warehouse and the warehouse proxy

To view the Application Event Log for IBM Tivoli Data Warehouse, start the Event Viewer by clicking Start
> Programs > Administrative Tools > Event Viewer. Select Application from the Log pull-down menu.

In the warehouse proxy, you can set error tracing on to capture additional error messages that can be
helpful in detecting problems. Refer to IBM Tivoli Monitoring: Installation and Setup Guide for more
information.

112 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 10. Troubleshooting installation and configuration
This chapter describes potential problems and workarounds regarding the installation and configuration of
the product.

Take Action commands show return code 0, but might be

unsuccessful
Take Action commands are a standard feature of the Tivoli Enterprise Portal in IBM Tivoli Monitoring and
are described in the user’s guide. In general, Take Action commands display a zero (0) return code in the
Tivoli Enterprise Portal (which is always located on a distributed system). This code indicates successful
submission of the command. The portal does not display the actual result of the command being executed.
For information on the result of command execution refer to the command output in the z/OS SYSLOG for
the specific system that is the target of the Take Action command.

A monitored system is displayed in the wrong Tivoli Enterprise Portal

In an environment with multiple hub Tivoli Enterprise Monitoring Servers, when the server and monitoring
agents are brought down and then back up, the monitoring agents might forward data to the wrong hub
Tivoli Enterprise Monitoring Server. The data is not displayed where you expect to find it, yet the
RKLVLOG indicates that the monitoring agent is running.

If you see this situation, ensure that you correctly configured the run-time environment (RTE) in which the
monitoring agent is running. Check the sequence of protocols that the monitoring agent uses to connect to
the server and ensure that the correct values are provided for each protocol.

Historical workspaces contain no data

If historical collection is not enabled and the historical workspace does not contain data, operators see
message KFWITM220E Request failed during execution. displayed in the Tivoli Enterprise Portal
message area.

Use the information found in IBM Tivoli Monitoring: Installation and Setup Guide to configure historical data
collection and retry the operation.

Tivoli Enterprise Monitoring Server on z/OS starts normally in a

system without the Integrated Cryptographic Service Facility but does
not connect to the Tivoli Enterprise Portal Server
Although Integrated Cryptographic Service Facility (ICSF) provides robust password encryption, you are
not required to use it because the ICSF can affect compatibility with the z/OS OMEGAMON monitoring
products. The following messages are displayed when the portal server cannot connect to the monitoring
server:
Call to KLE_CryptoGetFP failed with exit code 8. Cannot get CSNBXAE function pointer
Logon validation did not complete - system error. User:username
keyfile:key ip:ip_address

If you see these failed connection messages, perform the following steps so that the Tivoli Enterprise
Portal Server can connect to the Tivoli Enterprise Monitoring Server.
1. From the Configuration Tool Configure the Tivoli Enterprise Monitoring Server steps, select
Specify configuration values > Integrated Cryptographic Service Facility (ICSF) installed?.
2. Specify N in the Integrated Cryptographic Service Facility (ICSF) installed? field.

© Copyright IBM Corp. 2006, 2007 113

3. After the Tivoli Enterprise Monitoring Server configuration is complete and the server is running, you
must modify the portal server configuration to use an older, less robust encoding algorithm by
performing the following steps:
a. Edit the kfwenv file in install_dir\CNPS (where install_dir is C:\IBM\ITM by default) using a text
editor.
b. On a separate line, enter the following text:
USE_EGG1_FLAG=1
c. Save the file and exit.
d. Restart the Tivoli Enterprise Portal Server, if it is running.

U200 Port in use message found in RKLVLOG, indicating an incorrect

default port for TCP/IP profile
After you completely install and configure a monitoring agent (both inside and outside the Configuration
Tool) and then try to start the agent, you might find a U200 Port in use abend (abnormal end of task)
message in RKLVLOG, indicating a connection failure.

This problem can occur when the port that you defined for communication among the Tivoli Management
Services components was already reserved for a different application in the PORT statement of your
TCP/IP profile.

If this is your problem, perform the following steps:

1. Verify that the existing port reservation is no longer needed or choose a different port for
communication among the Tivoli Management Services components.
2. Edit your TCP/IP profile to reserve the port for the Tivoli Enterprise Monitoring Server started
procedure or change your IBM Tivoli Monitoring configuration (Tivoli Enterprise Portal Server, Tivoli
Enterprise Monitoring Server, and monitoring agent) to communicate with the Tivoli Enterprise
Monitoring Server on a different port.
3. Stop and then start the started procedures affected by your configuration change.

114 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 11. Troubleshooting data collection
This chapter describes potential problems and workarounds regarding data collection by the product,
including the following subtopics:
v “Collection of monitoring data”
v “Generation of data reports” on page 118

Collection of monitoring data

This section describes general data collection problems.

DFSMShsm space-size values exceeded

In a system where the size of the DFSMShsm LOGY data set or the MCDS data are large, default values
that Tivoli OMEGAMON XE for Storage on z/OS assigns for these data sets might be too low. Adjust this
value, as described in “Message KDFHS018” on page 91 and “Message KDFHS019” on page 91.

Workspace displays no data or does not show all the data you
expected
You have clicked on a navigation item or you have clicked on a link and the workspace either displays no
data or does not show all the data that you are expecting.

Many of the workspaces that are provided in the Tivoli OMEGAMON XE for Storage on z/OS product are
defined with filters. Each view in the workspace may have filters defined. These filters restrict the data that
is displayed to the rows that may be interesting to the user. To view the filters that are defined to a
workspace, right-click in the view and select Properties. Click the Filters tab to view or change the filters
that are defined for the view. Adjust the filters to meet the needs of your enterprise. The data displayed on
a workspace view is dependant on the Query supplying that data.

In some cases, the Query itself does not return the desired data. To view the Query that is returning data
to the workspace view, right-click in the view and select Properties. Click the Click here to assign a
query button, and examine the columns and any selection criteria.

Note: Do not modify product-provided Queries. (In many cases, modification of these queries is blocked.)
If you need to change a query, make a copy of the query with a new name.

Refer to the IBM Tivoli OMEGAMON XE for Storage on z/OS: User’s Guide for information on the
product-provided workspaces. Refer to the IBM Tivoli Monitoring: User’s Guide for information on defining
customizing workspaces and views.

Tape collection off; no VTS data occurs

User impact: You have configured data collection on Virtual Tape Servers (VTS), but no data is present in
the VTS workspace in the Tivoli Enterprise Portal.

Workaround: This problem can occur when you are not collecting related data; the following items are
prerequisites for enabling the collection of VTS data:
v Tape device collection, which you enable when you configure Tivoli OMEGAMON XE for Storage on
z/OS.
v Collection of SMF record type 94.

© Copyright IBM Corp. 2006, 2007 115

The timing of tape refreshes is in minutes, but data only changes
hourly
User impact: You have specified a tape collection interval, but data for VTS devices changes only every
hour.

Workaround: No workaround is available. This information is extracted from SMF data written by the tape
controllers. VTS controllers only write SMF records hourly. For example, you can specify a tape interval of
900 seconds (15 minutes), and a refresh operation takes place every 15 minutes. However, during a given
one-hour period, only data from the previous interval is available for the refresh operation. New data is
available only after the one-hour interval.

Monitoring agent is running out of storage

If response time is slow on the monitoring agent, check the RKLVLOG for messages about a possible
storage problem. A storage usage event is generated every hour and written to the RKLVLOG.

Typically the STORAGE command is used in conjunction with the EVERY command schedule period issuance
of the STORAGE command. The KDSSTART member of RKANCMD has the following line by default.
EVERY 00:60:00 STORAGE D * LOG STORAGE USE

Where:
EVERY
Is a command that is used to schedule another command for periodic execution.
00:60:00
Shows the hours, minutes, and second. For example, a value of 00:60:00 says run this command
every 60 minutes.
STORAGE
Displays statistics of ITMS:Engine storage usage.
D Stands for Detail. STORAGE provides both primary and extended storage statistics. This
information is helpful in tuning ITMS:Engine memory management.

The default entry causes the STORAGE D command to be issued every 60 minutes. The interval at which
the command is automatically issued is defined during the Tivoli Enterprise Monitoring Server configuration
with the Enable storage detail logging parameter on the Specify Advanced Configuration Options
panel, where the values are Y or N. There are two other settings associated with the Enable storage
detail logging parameter:
v Set the Storage detail logging interval to monitor storage. The interval values are written as part of the
second EVERY command in &rhilev.&midlev.RKANCMDU(KDSSTART). The default is 60 minutes.
v Set the Flush VSAM buffers interval to force all deferred VSAM writes to DASD. The interval values
are written as part of the third EVERY command in &rhilev.&midlev.RKANCMDU(KDSSTART). The default
is 30 minutes.
v To disable storage detail logging, set this parameter to N, which then generates the second EVERY
command as a comment.

To control storage detail logging dynamically, you can issue the following command from the z/OS console
to the monitoring server started task to enable storage detail logging:
MODIFY procname,STORAGE D

Where:
MODIFY
Is the z/OS operator command.

116 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
procname
Is the name of the monitoring server started task. The default name of monitoring server started
task is CANSDSST.
STORAGE
Displays statistics of ITMS:Engine storage usage.
D Stands for Detail. STORAGE provides both primary and extended storage statistics. This
information is helpful in tuning ITMS:Engine memory management.

After you issue this command, look in the RKLVLOG for the output. See the following sample output of this
command, with explanations.
01 KLVSD001 PRIMARY MAIN STORAGE INFORMATION:
02 KLVSD003 ALLOCATION DETAIL:
03 KLVSD004 SIZE(1-16) USE(1629) TOTAL(1652) ACCESSED(2122)
04 KLVSD004 SIZE(17-32) USE(1222) TOTAL(1256) ACCESSED(1804)
05 KLVSD004 SIZE(33-48) USE(43) TOTAL(51) ACCESSED(989)
06 KLVSD004 SIZE(49-64) USE(30) TOTAL(321) ACCESSED(789)
07 KLVSD004 SIZE(65-80) USE(190) TOTAL(299) ACCESSED(474)
08 KLVSD004 SIZE(81-96) USE(277) TOTAL(432) ACCESSED(492)
09 KLVSD004 SIZE(97-112) USE(27) TOTAL(43) ACCESSED(412)
10 KLVSD004 SIZE(113-128) USE(39) TOTAL(43) ACCESSED(311)
11 KLVSD004 SIZE(129-160) USE(79) TOTAL(374) ACCESSED(222)
12 KLVSD004 SIZE(161-192) USE(84) TOTAL(111) ACCESSED(205)
13 KLVSD004 SIZE(193-224) USE(96) TOTAL(127) ACCESSED(177)
14 KLVSD004 SIZE(225-256) USE(148) TOTAL(259) ACCESSED(192)
15 KLVSD004 SIZE(257-320) USE(342) TOTAL(365) ACCESSED(144)
16 KLVSD004 SIZE(321-384) USE(40) TOTAL(54) ACCESSED(98)
17 KLVSD004 SIZE(385-512) USE(5) TOTAL(35) ACCESSED(80)
18 KLVSD004 SIZE(513-768) USE(21) TOTAL(26) ACCESSED(92)
19 KLVSD004 SIZE(769-1024) USE(14) TOTAL(17) ACCESSED(12)
20 KLVSD004 SIZE(1025-2048) USE(28) TOTAL(35) ACCESSED(8)
21 KLVSD004 SIZE(2049-4096) USE(81) TOTAL(97) ACCESSED(2)
22 KLVSD004 SIZE(4097-8192) USE(8) TOTAL(9) ACCESSED(1)
23 KLVSD004 SIZE(8193-16384) USE(1) TOTAL(1) ACCESSED(1)
24 KLVSD005 LIMIT(65536) SLOPE(9) SIZES(23) TOTAL(2916K) FREE(2055K)
25 OVERHEAD(44936)
27 KLVSD031 BUFFER POOL INFORMATION
28 KLVSD032 POOL BUFSIZE(3564) SEGSIZE(65536) MASK(3FFFF) SIDEQ(0)
29 KLVSD033 BUFFERS INUSE(0) MAX(0) GETS(0) FREES(0)
30 KLVSD033 SEGMENTS INUSE(0) MAX(0) GETS(0) FREES(0) Q(0) QMAX(0)
31 KLVSD032 POOL BUFSIZE(3440) SEGSIZE(65536) MASK(7FFFF) SIDEQ(0)
32 KLVSD033 BUFFERS INUSE(3) MAX(9) GETS(245) FREES(242)
33 KLVSD033 SEGMENTS INUSE(1) MAX(1) GETS(1) FREES(0) Q(1) QMAX(1)
34 KLVSD032 POOL BUFSIZE(2560) SEGSIZE(65536) MASK(1FFFFFF) SIDEQ(0)
35 KLVSD033 BUFFERS INUSE(53) MAX(57) GETS(340) FREES(287)
36 KLVSD033 SEGMENTS INUSE(3) MAX(3) GETS(13) FREES(10) Q(1) QMAX(2)
37 KLVSD032 POOL BUFSIZE(1920) SEGSIZE(65536) MASK(FFFFFFFF) SIDEQ(0)
38 KLVSD033 BUFFERS INUSE(1) MAX(2) GETS(60) FREES(59)
39 KLVSD033 SEGMENTS INUSE(1) MAX(1) GETS(36) FREES(35) Q(1) QMAX(1)
40 KLVSD039 END OF BUFFER POOL INFORMATION

Where:
01 Is an ITMS:Engine header message.
02 Is an ITMS:Engine header message.
03 - 23
Is an ITMS:Engine message specifying the following values:
v SIZE: The range (m-n, in bytes) of the sizes of data blocks in the storage area. For example,
SIZE(1-16) indicates that this area contains all of the blocks that are from 1 to 16 bytes long.
v USE: The number of blocks in use.
v TOTAL: The total number of storage blocks allocated.

Chapter 11. Troubleshooting data collection 117

 Note: If the values of both USE and TOTAL are zero, the message is not displayed
v ACCESSED: The total number of times the storage block size was accessed.
24 Is an ITMS:Engine message specifying the following values:
v OVERHEAD: The amount of storage (in bytes) used for storage control.
v LIMIT: The size (in bytes) of the largest block that can be allocated.
v SLOPE: An IBM-internal parameter.
v SIZES: Specifies the number of storage areas.
v TOTAL: Specifies (in kilobytes) the total amount of storage.
v FREE: Specifies (in kilobytes) the amount of storage available.
25 Is a continuation of the previous ITMS:Engine message.
26 Is an ITMS:Engine message specifying the following values:
v TMS : The amount (in bytes) of temporary storage allocated. ITMS:Engine uses this storage, for
example, to resolve a string expression. Normally, this value is zero.
v PREFIX: The length (in bytes) of the storage block prefix.
v CUSHION: The overhead (in bytes) for each storage block. This value is equal to the value of
PREFIX plus the debug overhead, if any.
27 - 40
Is buffer pool usage information.

Generation of data reports

This section provides troubleshooting information regarding the generation of the following three types of
data reports:
v “Real-time data reports”
v “Short-term historical data reports”
v “Long-term historical data reports” on page 119
To troubleshoot problems with long-term data reports, also see IBM Tivoli Monitoring: Problem
Determination Guide, and look for issues such as of data warehousing, warehouse proxy configuration,
and summarization and pruning of data.

Real-time data reports

This section provides troubleshooting information regarding the generation of real-time data reports.

Identifiers for Data Rows are not Exported

Limitation: Locked columns and axis values are not included by default when you export a report or chart.
For example, this behavior causes a problem with the data extracted by an export of a bar chart that
utilizes the SSID number as one of the axis values. The extracted data does not contain the SSID number,
because axis values are not exported by default.

Workaround: When you want row identifiers such as SSID or LCU to be exported, you must select those
columns from the available columns, prior to exporting a report.
v The ″Assigned″ option exports all columns that you see.
v The ″Available″ option exports additional invisible columns, such as Timestamp and SSID.

Short-term historical data reports

This section provides troubleshooting information regarding the generation of short-term historical data
reports. See IBM Tivoli OMEGAMON XE for Storage on z/OS and OMEGAMON II for SMS: Planning,
Installation, and Configuration Guide for information on the persistent data store, which is the repository for
short-term historical data.

118 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Monitoring agent cannot insert all requested data rows into the persistent data
store
Failure to write data to the persistent data store can indicate a number of problems that sometimes
manifest themselves as tuning problems. See the following resources for information that might help
resolve the problem:
v Chapter 12, “Troubleshooting performance issues,” on page 123 in the current document
v IBM Tivoli OMEGAMON XE for Storage on z/OS: Tuning Guide
v OMEGAMON II for SMS Tuning Guide, GC32-9283
v The following workaround:
This workaround resolves the problem of a persistent data store that is full. In this situation, log
messages are displayed showing problems with components prefixed by KPD or KPX in the RKPDLOG
SYSOUT data set. These prefixes correspond to problems with the persistent data store.
Perform the following steps to determine whether the persistent data store files (Short-Term History) are
full:
1. From TSO SDSF log (=S.LOG) enter the following commands against the Tivoli Enterprise
Monitoring Server started task (for example, CANSDSST):
/F CANSDSST, KPDCMD QUERY CONNECT
/F CANSDSST, KPDCMD QUERY DATASTORE
2. View the RKPDLOG, as follows:
From the TSO SDSF Status panel (=S.ST), type a question mark (?) beside the name of the Tivoli
Enterprise Monitoring Server started task (for example, CANSDSST). This action causes the
RKPDLOG to be presented.
3. Enter an S beside the RKPDLOG entry to open it.
4. Scroll to the bottom of the RKPDLOG to see the output of the QUERY command and determine
whether the RKDF or RKS3 files are full.
5. If that log shows that these files are filling up too quickly, allocate more space so that you can keep
a larger amount of short-term historical data available online. See the Administrators Guide for
information on allocating the Persistent Data Store.
Also, monitor CPU usage and memory usage in the Tivoli Enterprise Monitoring Server started task
address space. Excessive CPU or memory consumption could be caused by persistent data store
activity.

Long-term historical data reports

This section provides troubleshooting information regarding the generation of historical (long-term) data
reports. Always consult the IBM Tivoli Monitoring Problem Determination Guide for general information
about data warehousing, the Warehouse Proxy server, and summarization and pruning.

Unable to warehouse all history data

User impact: Some of the historical tables for Tivoli OMEGAMON XE for Storage on z/OS are not
displayed in the Historical Configuration dialog box of the Tivoli Enterprise Portal and therefore cannot be
configured for data warehouse storage.

Workaround: No workaround is available. Not all historical tables for Tivoli OMEGAMON XE for Storage on
z/OS are eligible for data warehousing. For a list of tables whose data can be warehoused, see
Appendix B, “Historical data collection disk space requirements,” on page 155.

SQL queries to IBM Tivoli Data Warehouse fail because of invalid column name
When you are writing a Structured Query Language (SQL) query against IBM Tivoli Data Warehouse
(without using the Tivoli Enterprise Portal) where your database manager is DB2® or Oracle, the query
sometimes fails, indicating that the column name is invalid.

Chapter 11. Troubleshooting data collection 119

The cause of this problem might be that your column name is greater than 30 characters in length, and
DB2 and Oracle do not support column names greater than 30 characters.

The warehouse proxy creates the table with the abbreviated column names. These abbreviations are
shown in the WAREHOUSEID database table.

Additionally, column names that seem to meet the fewer than 30 characters rule might also fail when the
summarization and pruning agent is used because this agent adds a four-character prefix to the column
name (for example, AVG_).

To avoid this problem, revise your SQL queries to match the abbreviated column names in the
WAREHOUSEID table.

Summarization and pruning agent fails to run as scheduled

The Summarization and Pruning agent provides the ability to customize the length of time for which to
save data (pruning) and how often to compress data (summarization). This agent is configured to
determine how much data you summarize and prune and how often you perform this space-saving
operation. For more information about this agent, refer to the IBM Tivoli Monitoring: Administrator’s Guide.

If the summarization and pruning agent fails to run on schedule, determine whether the KSYCAT and
KSYATR members are missing from the RKANDATV data set on the Tivoli Enterprise Monitoring Server. If
the files are missing, you must copy the required files to your z/OS monitoring server installation, as
follows:
1. Obtain the following files from an IBM Tivoli Monitoring installation path on a distributed computer, for
example, a Windows computer. These files exist in an installation of either the monitoring server or the
portal.
a. Obtain a copy of the ksy.atr file from either of the following relative paths:
..\IBM\ITM\cms\attrlib OR
..\IBM\ITM\CNPS\CMSATR
b. Obtain a copy of the ksy.cat file from either of the following relative paths:
..\IBM\ITM\cms\rkdscatl OR
..\IBM\ITM\CNPS\RKDSCATL
2. Use FTP to send the files ksy.atr and ksy.cat files from the Windows installation to be members of
&hilev.RKANDATV
3. Ensure the members are named ksyatr and ksycat.
4. Recycle the Tivoli Enterprise Monitoring Server that is running on z/OS.
5. Recycle the monitoring agent.
6. Recycle the Summarization and Pruning agent.

Summarization and pruning does not function as described

The files that enable summarization and pruning are automatically installed on a hub Tivoli Enterprise
Monitoring Server if that component is located on the same computer as the Tivoli Enterprise Portal
Server. You must enable summarization and pruning manually in the following scenarios:
v The hub Tivoli Enterprise Monitoring Server is located on a computer other than the computer that hosts
the Tivoli Enterprise Portal Server.
OR
v The Tivoli OMEGAMON XE for Storage on z/OS monitoring agent is not configured in the same
consolidated software inventory (CSI) as the hub Tivoli Enterprise Monitoring Server.
To enable the Summarization and Pruning Agent to run against Tivoli OMEGAMON XE for Storage on
z/OS tables in the IBM Tivoli Data Warehouse, you must install the catalog and attribute data files on the
hub Tivoli Enterprise Monitoring Server on z/OS.

120 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
To install the catalog and attribute data files on the hub Tivoli Enterprise Monitoring Server on z/OS,
complete the following process:
1. Copy the following members from a CSI where the Tivoli OMEGAMON XE for Storage on z/OS
monitoring agent has been installed and configured to the CSI where the hub Tivoli Enterprise
Monitoring Server is installed:
v TKANDATAV (KS3ATR)
v TKANDATAV (KS3CAT)
v TKANPAR (KS3PDICT)
2. Restart your hub Tivoli Enterprise Monitoring Server.

Chapter 11. Troubleshooting data collection 121

122 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 12. Troubleshooting performance issues
This chapter describes potential problems and workarounds regarding declines in system performance.
See the IBM Tivoli OMEGAMON XE for Storage on z/OS: Tuning Guide for general tuning guidelines.

Data set I/O collection tuning

User impact: High CPU utilization in the OMEGAMON Subsystem address space, specifically with the
KDFSCOL and KDFSMIG modules.

Workaround: Data set I/O collection refers to the feature of Tivoli OMEGAMON XE for Storage on z/OS
which allows customers to get millisecond response time information at the data set level. Use one or both
of the following methods to manage this feature:
v Turn the feature on or off at the volume level. In general, monitor only volumes for which data set
response time is a critical issue or volumes that are known to have problems.
v Regulate the feature by using parameters that specify when data set level I/O monitoring starts for a
volume. Apply these parameters whenever you need to monitor a large number of volumes.
Use one of the following methods to collect data set level I/O statistics for a device:
v Monitor I/O events based on a fixed interval, called sample count. Sample count specifies how often I/O
events are monitored. If the sample count for a device is set to 1 (the default), every I/O event is
monitored. If the sample count is set to 5, every fifth I/O is monitored. Valid values are 1 through 99.
v Activate device monitoring when there is an extended period of response-time degradation, and
deactivate monitoring during periods of acceptable response time. You specify a millisecond response
(MSR) trigger value for a device and a global trip count that controls the number of times an MSR
exception occurs before monitoring resumes for the device. Valid values are 1 through 999.
Use the Configuration Tool to set these parameters.

Performance of the Tivoli Data Warehouse database is degraded or

there are gaps where historical data is unavailable for a specified
collection period
A number of symptoms indicate that your database or persistent datastore is in need of maintenance. You
might, for example, note that your DB2 transaction logs are filling up. You might see gaps in the data in
the middle or at the end where no historical data is available for a specified collection period. This problem
also manifests itself as degraded performance, such that database inserts require an unusually long period
of time. Inserts must be completed between display intervals. Operations need to completed before the
next collection interval to prevent the persistent data store from wrapping.

Adhere to the following guidelines to prevent these problems:

v Practice good database maintenance. Schedule regular maintenance outages and reorganize your IBM
Tivoli Data Warehouse tables, including the summarization and pruning tables, using a command to
reorganize table storage, such as (in DB2) the REORG command.
v Review the appendix “Relational database design and performance tuning for DB2 database servers”
appendix in the IBM Tivoli Monitoring: Administrator’s Guide to learn about DB2 tuning considerations.
v Change your Send to warehouse setting from daily to hourly.
v Increase the size of your database transaction log.
v To eliminate gaps in displays of historical data less than 24 hours old, increase the size of the persistent
data store on the mainframe.

© Copyright IBM Corp. 2006, 2007 123

Long response times or no results returned when specifying historical
collection time spans for some workspaces
For historical data collection in large data sets, the intervals that you set for refreshing historical
workspaces, for data collection, and for data chunking can affect performance dramatically. For example,
when you select a time span of many hours (for example, 24 hours) for a workspace where a large
number (tens of thousands) of rows of data has been stored in the persistent data store, the resulting
query can take 60 seconds or longer to complete. Also, the monitoring agent might use a high percentage
of available CPU while the query is processed.

Apply one or more of the following solutions to mitigate this problem:

v Set the refresh interval to “on demand” in historical workspaces, as follows.
1. Select Refresh Every in the View menu to access the submenu.
2. Select On Demand in the submenu.
If you set a short interval instead (60 or fewer seconds) the monitoring agent processing required
might not complete within the refresh interval, causing subsequent requests to be queued. The
monitoring agent then works continuously to process the query. High CPU utilization continues until
the user navigates to another workspace or closes the Tivoli Enterprise Portal.
v Specify longer historical collection intervals of 30 minutes or 1 hour, instead of the 15-minute defaults,
for the attribute groups that generate this problem. Longer historical collection intervals reduce the
number of rows per hour stored in the persistent data store.
v Consider not collecting historical data for attribute groups that you are experiencing this problem with.
Collect other data that provides the perspective on system performance or activity that you require.
v Modify the KFW_REPORT_TERM_BREAK_POINT parameter in the KFWENV file of the Tivoli
Enterprise Portal Server, which is located in the $CandleHome$\CNPS path. This parameter controls how
many hours of historical data (counting back from the present time) are to be retrieved from the
persistent data store (short-term history) data sets. The default is 86400 seconds (24 hours). A shorter
time setting creates smaller sets of data to be searched in the persistent data store by the Tivoli
Enterprise Portal. Older data (data excluded by changing this parameter) can be accessed if you are
populating historical data in the IBM Tivoli Data Warehouse. Be aware that modifying the
KFW_REPORT_TERM_BREAK_POINT parameter affects all applications that are using the Tivoli
Enterprise Portal Server.
The Tivoli Enterprise Portal queries the IBM Tivoli Data Warehouse for data older than the value of
KFW_REPORT_TERM_BREAK_POINT. Configure a one-hour warehousing interval to ensure that data
is available in the IBM Tivoli Data Warehouse. A one-hour warehousing interval also improves
performance of situations and real-time queries.

124 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 13. Troubleshooting error conditions
This section describes messages that the system provides to indicate performance problems.

Understanding abend U0001

The U0001 abend (abnormal end of task) is forced any time Tivoli OMEGAMON XE for Storage on z/OS
detects that an attempt to collect space information for a volume has taken more that 15 seconds to
complete. Typically, this operation completes in less that a second. The abend exists so that LSPACE
tasks that run too long are terminated before they affect system performance. Otherwise, the task can
affect system performance because it holds an exclusive enqueue on the volume while collecting space
and fragmentation data.

Limitation
The U0001 abend itself generates an unnecessary memory dump. If the memory dumps occur frequently,
system performance might be affected.

Workaround
Avoid this problem by adding a SLIP command to the SYS1.PARMLIB to bypass memory dumps for
U0001 abends in the address space of the Tivoli Enterprise Monitoring Server. An example of the SLIP
command to add to the IEASLPxx member in your parmlib is as follows:
SLIP SET, C=U0001,JOBNAME=tems_taskname,A=NOSVCD,ID=xxxx,END

Tivoli OMEGAMON XE for Storage on z/OS is the only OMEGAMON product that uses the U0001 abend.

Determining which volume being processed

Note: The following points apply to this procedure:
v This procedure is relevant when you do not add the SLIP command that is described in the
preceding workaround.
v This procedure is necessary because in this situation a Hang Detected message is not
generated for this volser.
When Tivoli OMEGAMON XE for Storage on z/OS abends the space collection subtask with U0001, the
negative effect on response time on a volume is transient. This effect is caused by DASD maintenance
tasks or high contention rates on the control unit. At times, you might want to know which volume
encountered the problem, so that you can take further action, if needed. Perform the following steps to
analyze the memory dump that the U0001 produces to obtain the volume serial number (VOLSER) for the
affected volume:
1. Select option 6 from the IPCS main menu.
2. Type SUMMARY REGS on the command line.
3. Scroll down to the KDFSPDEV program request block entry:
EP....... KDFSPDEV

Notice that the interrupt code for the bottom request block is 0x4E, (WLIC..... 0002004E). This code
represents the LSPACE macro.
4. A service request block (SVRB) exists above that line. This SVRB contains the registers that were
generated when the LSPACE macro was issued.
5. Inspect the contents of the R1 register.
6. Look up the address from the R1 register in the memory dump.

© Copyright IBM Corp. 2006, 2007 125

 v Notice the LSPA eye catcher shown in bold in the following example. This eye catcher marks the
dummy control section (DSECT) for the LSPACE request.
v Notice the offset +C in LSPA, shown in bold in the next line. This value is the UCB (unit control
block) address.
30A33378 D3E2D7C1 0018200A | LSPA.... |
30A33380 00000000 020FF190 30A33390 00000000 | ......1..t...... |
30A33390 00008101 C0002721 000FE5A2 00000030 | ..a.{.....Vs.... |
30A333A0 0000322D 00000000 00000000 00000000 | ................ |
7. Look up the UCB address in the dump. Notice the bolded details in the following example:
020FF190 00A8FF8C 196F0800 00000000 08E4C3C2 | .y...?.......UCB
020FF1A0 3030200F 000FF169 00010100 505249F3 | ......1.....PRI3
020FF1B0 F0F01002 00A00001 020FEF90 02101FA8 | 00.............y
020FF1C0 6F800101 00000000 38688072 1EB55840 | ?..............
020FF1D0 1D4CF8F0 10A7B910 D8002724 274D3232 | .<80.x..Q....(..
8. The VOLSER of the offending device is at offset +1C in the UCB.

Note: Instead of referring to the contents of the R1 register in Step 6, you can inspect the contents of the
R8 register. This register points directly to the device entry in the OMEGAMON device table, as
shown in the bolded parts in this example. The VOLSER is displayed at offset +6.
296D59C0 020FF190 196F5052 49F3F0F0 0F8C0801 | ..1..?PRI300....
296D59D0 00020008 321B0008 FF000200 02D000CC | .............}..
296D59E0 0000009C 00000189 00000000 00000003 | .......i........
296D59F0 00000128 0000005C 00000090 0000012F | .......*........

Monitoring agent receives remote procedure call errors during

warehousing, with some requests timing out and failing
While the monitoring agent is performing a warehousing operation, the agent might receive multiple remote
procedure call (RPC) errors, upload failures, and specific requests that time out, while others succeed. You
might see messages similar to this one in the warehousing log:
[IBM][CLI Driver][DB2/NT] SQL0911N
The current transaction has been rolled back because of a deadlock or timeout.
Reason code "2".
SQLSTATE=40001

These RPC calls may indicate that the warehouse proxy agent locks up temporarily and cannot respond to
new requests. Eventually, the proxy clears and continues processing. These kinds of problems are
symptoms of insufficient database tuning.

If you plan to install your Tivoli Data Warehouse on DB2, you must update the DB2 configuration to reduce
the likelihood of database deadlocks when large amounts of monitor data are transferred to the
warehouse. Use the following examples as a guide to making the configuration changes. It is best to make
these changes before installing the warehouse proxy and Summarization and Pruning agent and creating
the warehouse database. To ensure that tablespaces are created correctly, use the database creation
support provided during installation (or reinstallation) of the Tivoli Data Warehouse agent from the Manage
Tivoli Enterprise Services window.

To relieve database deadlock, perform the following steps:

1. Stop the warehouse proxy and summarization and pruning agents, and drop and recreate the existing
warehouse database.
2. Review the appendix “Relational database design and performance tuning for DB2 database servers”
appendix in the IBM Tivoli Monitoring: Administrator’s Guide to learn about DB2 tuning considerations.
Then issue the following command from the DB2 command window:
db2 update db cfg for WAREHOUS using parameter value

Use the following data configuration parameters:

126 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 DFT_DEGREE
LOGBUFSZ
LOCKLIST
SORTHEAP
NUM_IOCLEANERS
NUM_IOSERVERS
LOGFILSIZ
LOGPRIMARY
3. Restart the warehouse proxy and summarization and pruning agents.
4. Configure historical collection at the Tivoli Enterprise Portal.

Other Errors
The base components of IBM Tivoli Monitoring can generate other errors in the RKLVLOG. See the IBM
Tivoli Monitoring Problem Determination Guide, GC32-9458 for information and messages to assist with
troubleshooting framework problems.

Chapter 13. Troubleshooting error conditions 127

128 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Chapter 14. Troubleshooting specific product features
This chapter describes potential problems and workarounds for the unique features and user interface of
the product. See also to the section on Tivoli Enterprise Portal in the IBM Tivoli Monitoring: Problem
Determination Guide.

Note: The unique utilities in Tivoli OMEGAMON XE for Storage on z/OS, such as the Storage Toolkit and
the Dataset Attributes Database, log their messages to the Tivoli Enterprise Portal log. When you
are troubleshooting these utilities you must consult the Tivoli Enterprise Portal log.

Problem determination for the Dataset Attributes Database

This section provides problem determination information regarding the Dataset Attributes Database.

Performance degrades while this feature runs

Be aware that there is a difference between the data obtained by IDCAMS DCOLLECT and by the Dataset
Attributes Database feature. See IBM Tivoli OMEGAMON XE for Storage on z/OS: User’s Guide for more
information.

User impact: Performance issues occur during the Dataset Attribute data collection cycle.

Workaround: Data collection runs as set of subtasks within the address space of the Tivoli Enterprise
Monitoring Server. Consider the following options when a new collection cycle is started:
v Clear the Collect Catalog data option. This setting greatly reduces the resource consumption and
elapsed time of the collection cycle, but any attributes that might have been obtained from the catalog
are unavailable.
v Exclude any unneeded volumes or storage groups from collection, specifying them explicitly and/or
using masks.
v Schedule the collection to run only as often as necessary to rebuild the memory-resident database, and
at a time when impact on the overall system will be minimal.

Data for the feature is not displayed

User impact: No Dataset Attribute data is displayed.

Workaround: You cannot see Dataset Attribute data until a collection cycle has elapsed. The data is
displayed after the collection cycle is completed. Also, data for this feature is stored in memory, not on the
hard disk. Data might not be displayed for the following reasons:
v A collection cycle has not run. For example, collection is scheduled to begin at 2:00 AM and the Tivoli
Enterprise Monitoring Server was stopped and started at 6:00 AM. No data is displayed until a collection
cycle is completed.
v You restart the monitoring agent. Any data that was displayed is cleared from memory. No new data is
displayed until the collection cycle is completed.
v A task from another application has exclusive control. Because the Dataset Attributes Database feature
accesses every online volume, there is the potential for contention with other applications that use those
resources simultaneously. If another task has exclusive control of a volume and Dataset Attributes
Database is unable to gain access, the volume is bypassed and a message is issued to RKLVLOG.

Data collection for the feature runs too long

User impact: Data collection is not ending within a reasonable time frame.

Workaround: Issue the S3DA STATUS command twice over the course of approximately 1 minute to see if
the number of volumes processed is increasing. (The IBM Tivoli OMEGAMON XE for Storage on z/OS:
© Copyright IBM Corp. 2006, 2007 129
User’s Guide provides information on commands in the “Command-line option” section of “Appendix D.
Dataset Attributes Database”). If the remaining volumes are not being processed, issue the S3DA STOP
command to halt the collection cycle. If data collection still does not stop normally, or you suspect the
process is in a loop (in other words, very high CPU consumption within the TEMS address space), issue
the S3DA TERM command to terminate all Dataset Attribute processing.

Data for the feature is not sent to the Tivoli Data Warehouse
User impact: Dataset Attributes tables are not being sent to the Tivoli Data Warehouse as expected.

Workaround: Ensure that both the History Collection and Warehouse intervals are set to 1 hour in the TEP
Historical Configuration dialog box. Because the Dataset Attribute tables normally only change once per
day when the collection cycle occurs, the Warehouse Proxy does not send tables to the warehouse if it
detects they have not been updated frequently enough to satisfy the historical collection interval.

Data for the feature is displayed incorrectly in the workspace

User impact: Values displayed in Dataset Attribute workspaces seem to be in error.

Workaround: Examine the appropriate attribute from a different source program (for example, ISPF,
IDCAMS) to determine whether the values are being displayed incorrectly. For example, a data set that is
displayed as having negative Free space may, in fact, show a larger amount of space Used than Allocated
in its VTOC entry. This indicates that the VTOC had been incorrectly updated in the past (for example, a
program reaches an ABEND (abnormal end) condition before correctly setting the values).

If the attribute displayed is incorrect, contact IBM Software Support.

Problem determination for cross-product linking

This OMEGAMON XE product dynamically creates links to other OMEGAMON XE products when these
products are installed in the z/OS monitoring environment. This section describes problems that can occur
and guidelines for solving the problems.

Cross-product links missing from link list

Cross-product workspace links are displayed in the link list if the product workspace you are linking to has
been installed and your Tivoli Enterprise Portal user ID is authorized to access the target product.

If a cross-product link is missing from the link list, contact your system administrator to verify the following
information:
v Your user ID is authorized to access the target product.
v The target workspaces of the product are installed. OMEGAMON XE help files, workspaces, and
situations are installed using the IBM Tivoli OMEGAMON Data Files for z/OS CD.

An attempt to link to the workspace of another product fails and Message

KFWITM081E 'The link target cannot be found' is displayed
Many of the OMEGAMON XE products include predefined links to workspaces that are provided by other
products. Message KFWITM081E is displayed whenever you try to link to a workspace that does not exist.
You receive this message when the target workspaces of the product have been installed, but the
monitoring agent responsible for retrieving data for the target workspace is not running.

Product workspaces are installed using the IBM Tivoli OMEGAMON Data Files for z/OS CD. After the
workspaces are installed, all predefined links to the workspaces become enabled, and links to the target
workspaces are included in the link list when an operator right-clicks a link icon.

130 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
If you installed the workspaces for products that you have not installed in your environment, links to these
products are displayed as valid destinations for dynamic cross-product links. To prevent the inclusion of
misleading links, install only the help files, workspaces, and situations for products that you have installed.

Problems with cross-product linking when linking from an

OMEGAMON XE V4.1 workspace to an OMEGAMON XE V3.1
workspace
If you are migrating from OMEGAMON XE V3.1 products to OMEGAMON XE V4.1 products, you might
have a combination of V3.1 and V4.1 monitoring agents installed in your environment. For example, you
might have a Tivoli OMEGAMON XE for Storage on z/OS monitoring agent and an OMEGAMON XE on
z/OS V3.1 monitoring agent running on the same z/OS system during the migration period.

In this migration scenario, using dynamic workspace linking to link from an OMEGAMON XE V4.1
workspace to the workspace of another OMEGAMON XE V3.1 product works correctly, as long as the
target workspace exists in the V3.1 product. If the target workspace does not exist, you receive the
KFWITM081E message.

Chapter 14. Troubleshooting specific product features 131

132 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Appendix A. General problem determination for Tivoli
OMEGAMON XE monitoring agents on z/OS
Service information about the distributed components of Tivoli Management Services and service tasks
common to both distributed and z/OS environment are documented in IBM Tivoli Monitoring: Problem
Determination Guide. That book also explains diagnostic tools and setting up tracing for the various
distributed components of Tivoli Management Services.

This appendix provides an overview of service information that you must collect about a z/OS monitoring
agent and instructions for setting traces and collecting logs for your own use and to forward to IBM
Software Support, if necessary. The following topics are covered:
v “Problem determination flow for an OMEGAMON XE monitoring agent on z/OS”
v “Determining whether the problem was caused by an OMEGAMON XE monitoring agent on z/OS” on
page 134
v “Setting up trace logging for Tivoli OMEGAMON XE for Storage on z/OS” on page 138, including the
following subtopics:
– “Using the KDC_DEBUG environment variable” on page 138
– “Setting up RAS1 tracing” on page 139
– “Redirecting output of RAS1 tracing” on page 144
– “Setting trace levels on a Tivoli Enterprise Monitoring Server on z/OS using the Configuration Tool”
on page 145
v “Tips regarding the collection of diagnostic data” on page 146
v “Understanding RAS1 logs and component prefixes” on page 147
v “Maintaining the persistent datastore” on page 154
For information about submitting problems to IBM Software Support, refer to the support appendix found in
every IBM Tivoli Monitoring book. The support information includes information on this topic: “Capturing
z/OS logs to send to IBM Software Support” on page 165.

Problem determination flow for an OMEGAMON XE monitoring agent

on z/OS
When you encounter a problem with any component, the primary troubleshooting feature is logging.
Logging refers to the writing of text messages and trace data generated by the software to an output
destination, such as a console screen or a file. An OMEGAMON XE monitoring agent on z/OS does not
display messages at the Tivoli Enterprise Portal. Instead, messages are sent to more typical z/OS output
locations, such as sysout data sets or spool files or, more rarely, to the z/OS system console. Logging is
enabled on all monitoring agents by default.

Tracing, on the other hand, creates a record of the processing of a computer program or transaction.
Trace logs capture information about the operating environment when component software fails to operate
as intended to help you diagnose problems. The principal log type is the reliability, availability, and
serviceability (RAS1) trace log. When the Tivoli Management Services z/OS components are initialized,
RAS1 service initialization is one of the first processes started. RAS logs are in the English language only.
The RAS trace log mechanism is available on the Tivoli Enterprise Monitoring Server, the Tivoli Enterprise
Portal Server, and the monitoring agents. Most logs are located in a logs subdirectory on the host
computer.

By default, an OMEGAMON XE monitoring agent on z/OS has minimal tracing enabled. The setting
RAS1=ERROR means that only error messages are captured. When you report a problem, IBM Software
Support might ask you to enable a more in-depth and detailed form of tracing, such as one of those
discussed under “Syntax for RAS1 traces” on page 139.

© Copyright IBM Corp. 2006, 2007 133

IBM Software Support uses the information captured by trace logging to trace a problem to its source or to
determine why an error occurred. The default configuration for trace logging, such as the level of trace
logging, depends on the source of the trace logging. Trace logging is always enabled.

Attention: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade
performance of the monitoring agent. You must restore RAS1 tracing to the minimal KBB_RAS1=ERROR
after problem diagnosis is completed.

Determining whether the problem was caused by an OMEGAMON XE

monitoring agent on z/OS
This section describes how to identify problems caused by a specific OMEGAMON XE monitoring agent.
Sometimes it is difficult to trace the origin of a problem. For example, a problem might first be displayed in
a Tivoli Enterprise Portal client, but the client is reflecting a more basic problem with the Tivoli Enterprise
Monitoring Server.

In any problem scenario, gather all documentation at the time of the error, when all potentially useful
troubleshooting data is available. What seems to be a client problem might be a server problem, especially
in a scenario where data is not showing up at the client. The following sections describe guidelines for
collecting the correct information about any problems reported.

As you collect logs, create an exact description of the problem. For reproducible problems, document the
exact navigation path that produced the error. Screen captures might also help in the problem
determination. For further information, see “Using IBM Support Assistant” on page 161.

In your problem report, try to use the correct terminology when describing the problem (for example,
workspaces, views, navigators, events, and links). Consistent use of the terminology will help IBM
Software Support to understand the problem quickly.

The sections that follow discuss types of problems that you might see and how to capture information
needed to diagnose those problems.

Collecting logs for reproducible problems that are reported as Tivoli

Enterprise Portal client problems
If the problem is reproducible and is reported as a Tivoli Enterprise Portal client problem, send the client
log to IBM Software Support. The location of the log depends on the client type and operating system the
client is running on. The following sections provide locations of the fundamental types of logs:
v Logs for components on distributed systems:
– “Collecting logs for the Tivoli Enterprise Portal desktop client”
– “Collecting logs for the Tivoli Enterprise Portal browser client” on page 135
– “Additional logs to collect: Tivoli Enterprise Portal Server logs, Tivoli Enterprise Monitoring Server
logs, and data warehousing logs” on page 135
v Logs for components on z/OS systems: “Collecting logs on the z/OS system” on page 137
You may be asked to set a trace in the client and then collect the log. Trace logging is a fundamental tool
for troubleshooting in cases where a problem is reproducible.

Collecting logs for the Tivoli Enterprise Portal desktop client

If the Tivoli Enterprise Portal desktop client is being used, collect the logs shown in Table 2 on page 135:

134 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Table 2. Log locations for Tivoli Enterprise Portal desktop client
Component Windows systems UNIX and Linux systems
Tivoli v install_dir\CNP\logs\kcjras1.log where all of install_dir/cnp/logs/host_cj_timestamp.log
Enterprise the RAS1 tracing for the Tivoli Enterprise Portal
Portal desktop client is found.
client v install_dir\CNP\logs\kcj.log and
kcjerror.log any errors generated by the Java
libraries used in the Tivoli Enterprise Portal
client.
where:
install_dir
Specifies the directory where IBM Tivoli Monitoring is installed.
host (On UNIX and Linux systems only)
Specifies the name of the system that hosts the product.
Product code
The cj product code stands for the Tivoli Enterprise Portal. Refer to the product code
appendix of IBM Tivoli Monitoring: Problem Determination Guide for a complete list of
product codes for distributed components of IBM Tivoli Monitoring.
timestamp (On UNIX and Linux systems only)
A decimal representation of the time at which the process was started.

Collecting logs for the Tivoli Enterprise Portal browser client

If the Tivoli Enterprise Portal browser client is being used, then collect the log that is located in the
following path:

C:\Documents and Settings\user_id\Application Data\IBM\Java\Deployment\log\plugin1.4.2.trace

Where user_id is the user's ID on the computer. The plugin1.4.2.trace file contains the RAS1 tracing for
the Tivoli Enterprise Portal browser client and any Java exceptions. The Tivoli Enterprise Portal client logs
contain environmental information, such as the version and build level of the Tivoli Enterprise Portal client.
The log also contains the host and port of the Tivoli Enterprise Monitoring Server that the client is
connecting to.

Additional logs to collect: Tivoli Enterprise Portal Server logs, Tivoli Enterprise
Monitoring Server logs, and data warehousing logs
A problem that is reported as a Tivoli Enterprise Portal client problem might originate in a server failure.
This section provides log locations for the following servers:
v Table 3 on page 136 shows the location of logs for the Tivoli Enterprise Portal Server.
v See the following resources for the location of logs for the Tivoli Enterprise Monitoring Server:
– For the location of logs for a Tivoli Enterprise Monitoring Server on z/OS systems, see “Problems
reported as Tivoli Enterprise Portal Server problems” on page 137.
– For the location of logs for a Tivoli Enterprise Monitoring Server on distributed platforms, see Table 4
on page 136.
v Table 5 on page 137 shows the location of logs for IBM Tivoli Data Warehouse, the warehouse proxy,
and the Summarization and Pruning agent.

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 135
Table 3. Log locations for Tivoli Enterprise Portal Server
Component Windows systems UNIX and Linux systems
Tivoli \install_dir\logs\host_PC_HEXtimestampnn.log install_dir/logs/host_PC_timestamp.log
Enterprise
where:
Portal Server
install_dir
Specifies the directory where IBM Tivoli Monitoring is installed.
host Specifies the name of the system that hosts the product
Product code
The cq product code stands for the Tivoli Enterprise Portal Server. Refer to the product code
appendix of IBM Tivoli Monitoring: Problem Determination Guide for a complete list of
product codes for distributed components of IBM Tivoli Monitoring.
HEXtimestamp (On Windows-based systems only)
A hexadecimal representation of the time at which the process was started.
timestamp (On UNIX and Linux systems only)
A decimal representation of the time at which the process was started.
nn (On Windows-based systems only)
Represents the circular sequence in which logs are rotated. Ranges from 01-05, by default.
However, the first item is always retained, because it includes configuration parameters.

Also, on UNIX and Linux systems look for log information in this file:
kfwservices.exe

Table 4. Log locations for Tivoli Enterprise Monitoring Server on distributed platforms
Component Windows systems UNIX and Linux systems
Tivoli \install_dir\logs\host_PC_HEXtimestampnn.log install_dir/logs/host_PC_timestamp.log
Enterprise
where:
Monitoring
Server install_dir
Specifies the directory where IBM Tivoli Monitoring is installed.
host Specifies the name of the system that hosts the product
Product code
The ms product code stands for the Tivoli Enterprise Monitoring Server. Refer to the product
code appendix of IBM Tivoli Monitoring: Problem Determination Guide for a complete list of
product codes for distributed components of IBM Tivoli Monitoring.
HEXtimestamp (On Windows-based systems only)
A hexadecimal representation of the time at which the process was started.
timestamp (On UNIX and Linux systems only)
A decimal representation of the time at which the process was started.
nn (On Windows-based systems only)
Represents the circular sequence in which logs are rotated. Ranges from 01-05, by default.
However, the first item is always retained, because it includes configuration parameters.

Every successful export of historical data is logged in IBM Tivoli Data Warehouse in the
WAREHOUSELOG table. Errors encountered by the warehouse proxy are recorded in the Windows
Application Event Log.

136 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Table 5. Log locations for IBM Tivoli Data Warehouse, the warehouse proxy, and the Summarization and Pruning
agent on distributed platforms
Component Distributed system
Summarization and install_dir\logs\host_sy_nn.log and
Pruning agent install_dir\logs\host_sy_java_nn.log *
IBM Tivoli Data install_dir\logs\host_hd_nn.log and
Warehouse and the install_dir\TMAITM6\logs\host_Warehouse.lg0 *
warehouse proxy
* where:
host Specifies the name of the system that hosts the product.
install_dir
Specifies the directory where IBM Tivoli Monitoring is installed.
Product code
The sy and hd product code stand for the Summarization and Pruning agent and the IBM Tivoli Data
Warehouse, respectively. Refer to the product code appendix of IBM Tivoli Monitoring: Problem
Determination Guide for a complete list of product codes for distributed components of IBM Tivoli Monitoring.
nn Represents the circular sequence in which logs are rotated. Ranges from 01-05, by default. However, the
first item is always retained, because it includes configuration parameters.

Unreproducible problems reported as Tivoli Enterprise Portal client

problems
If the problem is not reproducible and is reported as a Tivoli Enterprise Portal client problem, collect both
the client and server logs. The logs may be the only indication of the real problem. Always try to get the
logs at the time of the error. The Tivoli Enterprise Portal client has dynamic logging. Restarting the
processes before collecting the logs will rewrite the log and any previous error messages may be lost.

Problems reported as Tivoli Enterprise Portal Server problems

If the problem is reported as a Tivoli Enterprise Portal Server problem, collect the server logs. The Tivoli
Enterprise Portal Server is comprised of two processes, so there is a reliability, availability, and
serviceability (RAS) (referred to in this document as a “RAS1 log”) for each process. If this is a
reproducible problem, you might be asked to set unit traces for the Tivoli Enterprise Portal Server and then
asked to gather the logs. For the location for Tivoli Enterprise Portal Server logs, see “Collecting logs for
reproducible problems that are reported as Tivoli Enterprise Portal client problems” on page 134. Both logs
contain the Tivoli RAS1 trace information. Also, collect the client log at the time of the error, if it is
available.

Collecting logs on the z/OS system

When you rule out problems with Tivoli Management Services components and the problems with the
OMEGAMON XE monitoring agent on z/OS persist, treat the problem as a monitoring agent problem.
Problems that are displayed in the Tivoli Enterprise Portal does not mean that this component is the
source of the failure. For example, a data collection problem with a monitoring agent manifests itself as the
display of no data or incorrect data in the Tivoli Enterprise Portal.

Log files and trace information is collected in the same way for all OMEGAMON XE monitoring agents on
z/OS and the z/OS components of the Tivoli Management Services, as shown in Table 6 on page 138.

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 137
Table 6. Locations of log and trace information for z/OS components
Log location Details
An OMEGAMON XE RKLVLOG for the monitoring agent started task is the single most helpful piece of service
monitoring agent on information for an OMEGAMON XE monitoring agent on z/OS. The RKLVLOG (R = runtime,
z/OS KLV = the prefix associated with IBM Tivoli Monitoring Services:Engine or ITMS:Engine) is
the sysout data set or spool file that contains log and trace messages. Instructions on how to
save the contents of this log to a data set are provided under “Capturing z/OS logs to send
to IBM Software Support” on page 165.

These additional zSeries log files (if available) are also useful:
v The RKLVSNAP sysout data set or spool file contains formatted dump output.
v The RKPDLOG sysout data set or spool file relates to persistent data stores and is
described later in this table.
Refer to your started procedures for the locations of these serviceability log files.
Tivoli Enterprise Because the Tivoli Enterprise Monitoring Server on z/OS runs under ITMS:Engine just as an
Monitoring Server on OMEGAMON XE monitoring agent on z/OS does, all logging under ITMS:Engine is handled
z/OS the same way, that is log and trace data are written to RKLVLOGs and RKPDLOGs.
IBM Tivoli Monitoring ITMS:Engine is a collection of basic operating system and communication service routines
Services:Engine built specifically for z/OS. All address spaces used by OMEGAMON XE monitoring agent on
(ITMS:Engine) z/OS load and use the services of ITMS:Engine.

Successful initialization of ITMS:Engine is noted by this message:

KLVIN408 IBM OMEGAMON PLATFORM ENGINE VERSION 400 READY

For troubleshooting information about ITMS: Engine problems, refer to the z/OS initialization
section of IBM Tivoli Monitoring: Problem Determination Guide.

ITMS:Engine writes messages to the same RKLVLOG as the product it is running. If you
search the RKLVLOG for a OMEGAMON XE monitoring agent on z/OS, product-specific
messages start with the product code (for example, KS3 for Tivoli OMEGAMON XE for
Storage on z/OS) but messages for the ITMS:Engine start with the KLV component prefix.
OMEGAMON The OMEGAMON subsystem does not allocate an RKLVLOG. This component issues
subsystem messages directly to the z/OS system console (or SYSLOG).
Persistent data store The RKPDLOG sysout data set or spool file contains the information and error messages
related to the handling of persistent data stores. To dump this log, follow the procedures
described for RKLVLOG in the sections that follow.

For locations of log files for all the components of Tivoli Management Services and information about
enabling tracing for distributed components, refer to IBM Tivoli Monitoring: Problem Determination Guide.

Setting up trace logging for Tivoli OMEGAMON XE for Storage on z/OS

There are two important debug variables that can be set to debug problems with an OMEGAMON XE
monitoring agent on z/OS:
v The KDC_DEBUG environment variable (see “Using the KDC_DEBUG environment variable”)
v RAS1 tracing
When you are generating logs refer to “Tips regarding the collection of diagnostic data” on page 146.

Using the KDC_DEBUG environment variable

Communications tracing during TCP/IP initialization is controlled by the KDC_DEBUG environment
variable.

138 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
To obtain the level of tracing required to have these TCP/IP initialization messages echoed to the RAS1
log, the string KDC_DEBUG=Y must be added to member KDSENV of RKANPARU (or the appropriate
initialization member named KppENV, where pp is the two-letter prefix associated with the monitoring agent,
such as S3 for Tivoli OMEGAMON XE for Storage on z/OS).

Possible values for KDC_DEBUG are:

Y When this variable is set to Y, then the data flow between the monitoring agent and Tivoli
Management Services components (such as Tivoli Enterprise Monitoring Server and Tivoli
Enterprise Portal Server) during TCP/IP initialization is recorded, including data packages send
and received. When KDC_DEBUG=Y is active in the environment during initialization of TCP/IP
services for this address space and any of the following messages are present:
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.udp

Then TCP/IP initialization was successful. If KDC_DEBUG is set to Y and none of these
messages are displayed in RKLVLOG, then initialization of the TCP/IP service failed.
N The data flow between the monitoring agent and Tivoli Management Services components during
TCP/IP initialization is not recorded. This is the default and the recommended setting for normal
operation.

For OMEGAMON monitoring agents on z/OS, this environment variable can be used during TCP/IP
service initialization to diagnose connectivity problems with application-layers such as telnet and FTP, and
with the IBM Tivoli Monitoring Server, Tivoli Enterprise Portal Server, and the Tivoli Enterprise monitoring
agents.

The KDC_DEBUG environment variable controls all DCS communications tracing. Use the KDC_DEBUG
parameter to track DCS errors or activity between the agent and the Tivoli Enterprise Monitoring Server.

Note: You must place the KDC_DEBUG environment variable statement immediately after the
KDC_FAMILIES environment variable.

Refer to the environment variables appendix in IBM Tivoli Monitoring: Problem Determination Guide for a
list of environment variable associated with other components.

Setting up RAS1 tracing

RAS1 is the OMEGAMON component that provides trace and dump routines. RAS1 tracing provides
runtime filtering of product messages and is the primary diagnostic tool for OMEGAMON. It is provided by
the kbb library service and is set using either the IBM Tivoli Monitoring Service Console interface or some
more direct method of manually modifying the KBB_RAS1 parameter. RAS1 messages are sent to stdout,
so that one of the components in the configurator programs redirects that output to the files shown in
Table 6 on page 138.

Not all OMEGAMON products or functions support RAS1 tracing, and not all OMEGAMON products or
functions use the filters and classes in the same way. For example, two monitoring agents might use the
filters and classes specified in RAS1 tracing differently and with different frequencies.

Again, be aware that RAS1 tracing log files can grow very large with the wrong amount of filtering. There
is no log management function or feature, so be careful with the levels of tracing that you specify. You may
want to run error tracing for all components and then any additional levels depending on diagnostic needs.

Syntax for RAS1 traces

This syntax is used to specify an RAS1 trace in the KppENV file, where pp is the two-letter prefix
associated with the monitoring agent, such as S3 for Tivoli OMEGAMON XE for Storage on z/OS. After
you add this command to the KppENV file, you must stop and restart the address space for it to take

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 139
effect. After that, it remains in effect for the life of the address space. To end this RAS1 trace, you must
edit the KppENV file again and reset the trace level and stop and start the address space.

The basic syntax of the RAS1 trace commands for error tracing is as follows:


KBB_RAS1= global_class

(COMP: component_type) (ENTRY: entry_point)


(UNIT: unit_name, class)

Where:
global_class
Indicates the level of tracing that you want to see. This is a global setting that applies to all RAS1
filters within the process. If you set this global class by itself, it is global in scope and the trace
cannot filter on any of the other keywords. Separate combined classes with a space. The following
are possible values. Valid abbreviations are in parentheses.
v ERROR (ER): returns severe error messages only (this is the default for most applications).
v STATE (ST): records the condition or current setting of flags and variables within the process. If
state tracing is enabled, you can see the current state of particular variables or flags as the
process is running.
v FLOW (FL): causes a message to be generated at an entry or exit point of a function.
v DETAIL (DE): produces a detailed, verbose level of tracing.
v INPUT (IN): records data that is created in the execution of a particular API, function, or
process.
v ALL: causes all available messages to be recorded, a combination of all the other forms of
tracing.
COMP Is the keyword that indicates this trace will include a component type. The COMP keyword is used
to trace groups of routines related by function (or component). Do not use this parameter unless
requested to do so by IBM Software Support.
component_type
Is the identifier for a component type. If an IBM Software Support representative instructs you to
perform a component trace, you will be provided with a code for that component. Do not use this
parameter unless requested to do so by IBM Software Support.
ENTRY
Is the keyword used to narrow a filtering routine to specify a specific ENTRY POINT. Since
multiple entry points for a single routine are not common, this keyword is not commonly used and
should only be used at the explicit request of an IBM Software Support representative.
entry_point
Is a variable representing the name of the entry point. If you are asked to specify a value for the
ENTRY keyword, an IBM Software Support representative will tell you what value to specify for
entry_point .
UNIT Is the keyword that indicates this trace will include collecting information using the compilation unit,
fully qualified or partially qualified. A match is performed between the compilation unit dispatched
and the compilation unit specified on the RAS1 statement. A match results in a trace entry.
unit_name
Is a variable representing the name of the compilation unit. This name can be anything that is
related to the object file name or unit compilation name. In most instances, this name defines the
component that is being traced. This value might be one of the components in one of the
component prefixes, but in practice will most likely be the three-character component identifier for
the monitoring agent (for example, ks3 for Tivoli OMEGAMON XE for Storage on z/OS).

140 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
class One of the same values specified for global_class but, because of its position inside the
parentheses, it is narrowed in scope to apply only to the unit_name specified.
Notes:
1. The default setting for all components is KBB_RAS1=ERROR, meaning that only error tracing is enabled.
2. You can specify any combination of UNIT, COMP, and ENTRY keywords. None of these keywords is
required. However, the RAS1 value you set with the global class applies to all components.
Some examples of RAS1 trace syntax follow.

Example 1 – Tracing requests to and answers from the Tivoli Enterprise Monitoring Server: To
show requests to and answers from the Tivoli Enterprise Monitoring Server, specify this trace:
KBB_RAS1=ERROR (UNIT:KRA ST ERR)

The unit values ST and ERR indicate that you will be collecting state and error information for the agent
framework component (KRA).

This type of agent trace is used only if you are trying to debug a specific problem, because it greatly
increases the number of messages generated by agent. With this type of trace, messages will include a
memory dump of all rows of agent data that have passed filtering, which includes attribute names and
values, request names, table names, and collection interval. Remember to disable this resource-intensive
form of tracing immediately after you have completed your trace.

Example 2 – Tracing proxy controller and distributed agent issues: From the Tivoli Enterprise
Monitoring Server, to trace proxy controller and Tivoli Enterprise Monitoring Server distributed agent
issues, issue this command:
KBB_RAS1=ERROR (COMP:KUX ST ER) (UNIT:KRA ALL) (UNIT:KDS FL)

In this example:
v KUX is a component identifier provided to you by a representative of IBM Software Support so that you
can collect state and error information about this subcomponent.
v KRA is the unit name for the agent framework component. All trace information about this component is
being captured.
v KDS is the Tivoli Enterprise Monitoring Server component and the flow (FL) of entry or exit points
through this component will be documented with records written to RKLVLOG.

Setting RAS1 trace levels for an OMEGAMON XE monitoring agent on z/OS

For most OMEGAMON monitoring agents on z/OS, the trace level KBB_RAS1=ERROR is set by default. You
can change this trace level a number of ways. Three of those ways are explained in the sections that
follow.

Setting trace levels by editing RKANPARU: One of the simplest ways to set trace levels for an
OMEGAMON XE monitoring agent on z/OS is to edit the RKANPARU(KppENV) member.

The text in bold is an example of what an IBM service representative might ask you to add to this member.
File Edit Edit_Settings Menu Utilities Compilers Test Help
sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
EDIT KAN.V4R1.RKANPARU(KS3ENV) - Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change
==MSG> your edit profile using the command RECOVERY ON.
000001 KDE_TRANSPORT=\
000002 SNA.PIPE PORT:135 USE:N\
000003 IP6.PIPE PORT:19184 USE:N\
000004 IP6.UDP PORT:19184 USE:N\
000005 IP.SPIPE PORT:3660 USE:N\
000006 IP6.SPIPE PORT:3660 USE:N\

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 141
 000007 IP.PIPE PORT:1918 EPHEMERAL:Y\
000008 IP.UDP PORT:1918
000009 KBB_RAS1=ERROR (UNIT:KS3TN ALL) (UNIT:KS3IRAFT ALL)
000010 CT_CMSLIST=\
000011 IP.PIPE:x.xx.xxx.xx;\
000012 IP.UDP:x.xx.xxx.xx;
000013 CTIRA_STANDALONE=N
000014 CTIRA_IP_PORT=0
000015 LANG=en_US.ibm-037
****** **************************** Bottom of Data ****************************

Setting trace levels dynamically using IBM Tivoli Monitoring Services console: You can also use
the IBM Tivoli Monitoring Services console to set trace levels for OMEGAMON XE monitoring agents on
z/OS, as well as for a Tivoli Enterprise Monitoring Server on z/OS or a distributed system.

The IBM Tivoli Monitoring Services console enables you to read logs and turn on traces for remote product
diagnostics and configuration. The IBM Tivoli Monitoring Service Console is uniquely identified by its
service point name. All IBM Tivoli Monitoring Services consoles for a host are linked and presented on the
IBM Tivoli Monitoring Services Index for that host. Point a browser to the HTTP port 1920 on a specific
host (for example, http://goby:1920) to launch the IBM Tivoli Monitoring Services Index. You can also
launch the service console by connecting through the HTTPS protocol and port 3661. You can perform
operations on a specific IBM Tivoli Monitoring process by selecting the IBM Tivoli Monitoring Services
console associated with a service point name.

Starting the IBM Tivoli Monitoring Service Console: Use the following procedure to start the IBM Tivoli
Monitoring Services console.
1. Start Internet Explorer V5 or higher.
2. In the Address field, type the URL for the Tivoli Enterprise Portal browser client installed on your Web
server. The URL for the Tivoli Monitoring Services Web server is
http://hostname:1920

Where hostname specifies the computer where the Tivoli Enterprise Portal Server was installed. If the
IBM Tivoli Monitoring Services console is not displayed, a system administrator might have blocked
access to it. Refer to the IBM Tivoli Monitoring: Problem Determination Guide for information about
blocking access to the IBM Tivoli Monitoring Services console. An HTML window displayed with a list
of hyperlinks to all available instances of the IBM Tivoli Monitoring Services console.
3. Click theIBM Tivoli Monitoring Services console link associated with the desired process (service point
name).
4. When the login window opens, click OK.

In secure environments, you need a valid user ID and password to proceed. Upon successful login, the
IBM Tivoli Monitoring Services console opens with three areas:
v Header
v Command Results
v Command Field
You can now issueIBM Tivoli Monitoring Services console commands in the command input area. For a list
of available commands, type a question mark (?) and click Submit.

The IBM Tivoli Monitoring Services console supports the following commands, most of which are useful for
problem determination:
bss1 Manages BSS1 (Basic System Services). This command is paired with one of the following
subcommands:
v dumpcvt: Display KBBSS_cvt_t
v listenv: Display the resident CT® variables

142 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 v getenv: Display environment variables
v setenv: Assign environment variable
v info: Display BSS1_Info() data
v config: Manage configuration variables
config Used to modify the settings of the ITMS: Engine debug environment variables: RES1_DEBUG,
KDH_DEBUG, KDC_DEBUG, and KDE_DEBUG . For example, the following config command
can be used to alter the setting of KDC_DEBUG:
CONFIG KDC_DEBUG=Y

The setting of KDC_DEBUG can be restored to its original value using the following command:
CONFIG KDC_DEBUG=N

For more information about setting KDC_DEBUG for the Tivoli Enterprise Monitoring Server, refer
to “Setting trace levels on a Tivoli Enterprise Monitoring Server on z/OS using the Configuration
Tool” on page 145.
ctbld The ctbld command is used to determine the maintenance level of the product.
http Displays HTTP server management
kdcstat
Displays the status of KDC (RPC Service) component
kdestat
Displays the status of the KDE (Transport Service) component
ras1 Manage RAS1 (Reliability, Availability, and Serviceability). This command is paired with one of the
following subcommands:
v dumpcvt: Display KBBRA_cvt_t
v log: Display RAS1 log capture buffer
v list: List the RAS1 filters
v interpret: Interpret the control string
v ctbld: Display the resident CTBLD data
v units: Display the registered compilation units
The RAS1 (with no operands) command can be used to view the current ITMS:Engine log capture
buffer. When operands are supplied with the RAS1 command, the operands are assumed to be
keywords applicable to the KBB_RAS1 environment variable.
The RAS1 command is especially useful for dynamically enabling and disabling RAS1 traces. The
process of gathering documentation for IBM Software Support might conflict with your company's
need for 24 X 7 product availability. The RAS1 command can be used to alter KBB_RAS1 tracing
parameters dynamically without the need to recycle the product. For example, to enable the
standard IRA traces, you can use the following IBM Tivoli Monitoring Services Console command:
RAS1 ’error (unit:kpx all) (unit:kra all)’

The (single) quoted string is passed to RAS1 as operands of the KBB_RAS1 environment
variable.

After this trace is captured, the IRA trace can be disabled with the following IBM Tivoli Monitoring
Services Console command:
RAS1 ’error (unit:kpx error) (unit:kra error)’

This command restores the RAS1 logging level from ALL to ERROR for units kpx and kra.
res1 Displays the status of RES1 Logical Resource Manager

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 143
Setting trace levels dynamically from the IBM Tivoli Monitoring Service Console command line:
Dynamic RAS1 agent tracing allows the you to send commands to the monitoring agent to alter its RAS1
tracing dynamically while a process is running. This type of tracing tracks particular types of problems as
they occur.

You cannot issue this command if RAS1 agent tracing is not enabled. Enable the RAS1 agent tracing first
before attempting to dynamically alter RAS1 agent tracing with these commands documented here.

You can send these commands using the Tivoli Enterprise Portal Take Action facility.

Dynamic RAS1 agent tracing uses syntax similar to RAS1 agent tracing, but with several differences to
keep in mind. The syntax is:


action FILTER ID= id [UNIT= ras1_unit]

[CLASS= (ras1_class)]

Where:
action Can be one of the following values:
ADD Enables a specific filter,
REMOVE
Disables a specific filter.
ENABLE
Enables a global class.
DISABLE
Disables a global class.
id Is a unique key for each filter specified that commands act upon. The ID is usually a three-letter
component identifier for the component to which the add, remove, enable, or disable action is
being applied.
UNIT Is the keyword that indicates this trace will include collecting information for a certain component.
Units IDs are specific to a product or component. This component ID will be provided to you by an
IBM Software Support representative. Do not use this keyword unless you are doing a component
trace under the direction of IBM Software Support. Only one of these can be specified at a time.
ras1_unit
Is a variable representing the name of the filter. This name can be anything that is related to the
object file name or unit compilation name. In most instances, this variable defines the component
that is being traced. This value can be any one of the components in the Table 7 on page 148.
Typically the value is the three-character component identifier for the monitoring agent (for
example, ks3 for Tivoli OMEGAMON XE for Storage on z/OS).
CLASS
Is the keyword specifying the type of trace.
ras1_class
One of the same values specified for global class. However, because of its position inside the
parentheses, it is narrowed in scope to apply only to the unit_name specified.

Redirecting output of RAS1 tracing

Nearly all diagnostic information for the Tivoli Management Services z/OS components is delivered using
the RAS1 (trace) component. This component is configured in member KBBENV of RKANPARU using the
KBB_RAS1 environment variable.

Often, Tivoli users redirect the initialization member using the ITMS:Engine INITLIST processing. INITLIST
processing is always echoed to the RKLVLOG with the KLVIN411 message.

144 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
The following example shows a typical KBBENV override to a different member, KDSENV:
KLVIN410 INITLIST MEMBER KDSINIT BEING PROCESSED
KLVIN411 KLVINNAM=KDSINNAM
KLVIN411 KLVINTB=KDSINTB
KLVIN411 KLVINVLG=KDSINVLG
KLVIN411 KLVINNAF=KDSINNAF
KLVIN411 KLVINVPO=KDSINVPO
KLVIN411 KLVINSTG=KDSINSTG
KLVIN411 KLVINVAM=KDSINVAM
KLVIN411 KBBENV=KDSENV

In this instance, configuration of KBB_RAS1 is displayed in member KDSENV of RKANPARU.

Setting trace levels on a Tivoli Enterprise Monitoring Server on z/OS

using the Configuration Tool
When you configure a Tivoli Enterprise Monitoring Server on z/OS using the Configuration Tool, a new
Advanced panel shown in Figure 1 lets you specify the level of trace information collected for the Tivoli
Enterprise Monitoring Server on z/OS.

—-------------------- SPECIFY ADVANCED CONFIGURATION VALUES -------------------

COMMAND ===>

Enable Web Services SOAP Server ==> Y (Y, N)

Enable startup console messages ==> Y (Y, N)
Enable communications trace ==> N (Y, N, D, M, A)
Enable storage detail logging ==> Y (Y, N)
Storage detail logging: Hours ==> 0 (0-24) Minutes ==> 60 (0-60)
Flush VSAM buffers: Hours ==> 0 (0-24) Minutes ==> 30 (0-60)
Virtual IP Address (VIPA) type ==> N (S=Static, D=Dynamic, N=None)
Minimum extended storage ==> 150000 K
Maximum storage request size ==> 16 (Primary) ==> 23 (Extended)
Language locale ==> 1 (Press F1=Help for a list of codes)

Persistent datastore parameters:

Maintenance procedure prefix ==> KPDPROC
Datastore file high-level prefix ==> ABENF.HLPLX.NV.RTE1
Volume ==> PRI160 Storclas ==>
Unit ==> 3390 Mgmtclas ==>

Enter=Next F1=Help F3=Back F10=CMS List

Figure 1. Configuration Tool Specify Advanced Configuration Values panel

The advanced configuration values affect logging and tracing on the Tivoli Enterprise Monitoring Server on
z/OS:
Enable startup console messages
Set this parameter to Y if you want a SYSLOG message on the console to indicate when the
TEMS finishes initializing. You can use this message in an automation script. Refer to the
automation package for your site for further instructions on how to capture the KO4SRV032 and
KDSMA001 TEMS automation message IDs. The default is Y.
Enable communications trace
Set this parameter to Y if you want KDC_DEBUG=Y as the override setting in
&hilev.HLPLX.NV.RTE1.RKANPARUU(KDSENV) member. Otherwise, the default setting of
KDC_DEBUG=N is used. This default parameter instructs the data communications layer to report
communications problems using a minimal, summary format. This parameter is intended for stable
applications in production. Note that the default KDC_DEBUG=N generates standard RAS1 trace
data in the TEMS RKLVLOG, in addition to the summary information diagnosing possible timeout
conditions

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 145
 The following settings report on data communications problems:
v KDC_DEBUG=N: minimal tracing (default)
v KDC_DEBUG=Y: full-packet tracing
v KDC_DEBUG=D: KDC_DEBUG=Y plus STATE & FLOW tracing
v KDC_DEBUG=M: KDC_DEBUG=D plus INPUT & OUTPUT HELPs tracing
v KDC_DEBUG=A: KDC_DEBUG=M plus all format tracing
Do not set KDC_DEBUG=A unless directed by an IBM Software Support representative.
Enable storage detail logging
Set this parameter to Y to enable storage allocation detail logging. You can use the storage detail
command output to analyze storage utilization within the TEMS address space. Specifying Y
generates the second EVERY command in &hilev.HLPLX.NV.RTE1.RKANCMDU(KDSSTART).
To disable storage detail logging, set this parameter to N, which generates the second EVERY
command as a comment. To further control storage detail logging, you can also dynamically issue
the following modify command to the CANSDSST started task:
==> /F CANSDSST,STORAGE D

This modify command is useful if the TEMS is already running with storage detail logging initially
disabled. Issuing the modify command activates storage detail logging without having to recycle
the TEMS. The default is Y.

If you set this parameter to Y, you must also define the times for storage detail logging and
flushing the VSAM buffers.
v For Storage detail logging, set the interval to monitor storage. The interval values are written as
part of the second EVERY command in: &hilev.HLPLX.NV.RTE1.RKANCMDU(KDSSTART). The
default is 0 hours (hh) and 60 minutes (mm).
v For Flush VSAM buffers, set the interval to force all deferred VSAM writes to DASD. The
interval values are written as part of the command in:
&hilev.HLPLX.NV.RTE1.RKANCMDU(KDSSTART). The default is 0 hours (hh) and 30 minutes
(mm).

For additional information about the values on this panel, refer to Configuring IBM Tivoli Enterprise
Monitoring Server on z/OS.

Tips regarding the collection of diagnostic data

This section describes problems that might arise when you collect diagnostic data, such as debugging
logs.

KDFDEVIN DEBUG
User impact: You might experience a problem in Tivoli OMEGAMON XE for Storage on z/OS and IBM
Software Support requests that you turn on debugging.

Workaround: Add the DEBUG(ON) parameter to the RKANPAR member KDFDEVIN . The parameter
enables debugging messages in the Tivoli OMEGAMON XE for Storage on z/OS product only. These
messages come from a wide variety of modules and components within the Tivoli OMEGAMON XE for
Storage on z/OS product and substantially increase output to the RKLVLOG. For this reason, enable
debugging only when you are working with IBM Software Support. And run debugging only until you have
collected sufficient data, as defined by your IBM Software Support contact. To turn off debugging, remove
the DEBUG(ON) parameter from the KDFDEVIN member.

146 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
!Trace in VTAMDATA
User impact: You might experience a problem with the OMEGAMON II interface to Tivoli OMEGAMON XE
for Storage on z/OS, and IBM Software Support requests that you turn on tracing in the OMEGAMON II
address space.

Workaround: Tracing in the OMEGAMON II interface is performed on a per-session basis. To enable this
type of tracing, you must be able to pass VTAM USER parameters in your logon command string. Some
types of session manager give you this capability. If you are not using a session manager, the VTAM USS
screen the your support staff provides can give you this capability.

The parameter to pass in your logon command string is !Trace. The generated trace messages
substantially increase output to the RKLVLOG. For this reason, enable tracing only when you are working
with IBM Software Support. And run tracing only until you have collected sufficient data, as defined by your
IBM Software Support contact.

STBDEBUG(X)
User impact: You might notice signs of a storage overlay or storage creep and contact IBM Software
Support. Your IBM contact person might request that you set storage debugging to X, which is the setting
that generates the highest level of detail. (The other possible settings are N, no debugging, and Y, minimal
debugging.)

Workaround: IBM Software Support might instruct you to add this parameter to the RKANPAR member
KDFSYSIN as part of the debugging process. Depending on the state that IBM Software Support asks you
to set, you may also need to modify the MINIMUM parameter in the same member. STGDEBUG(Y) adds
a small amount (32 bytes) to each block of storage allocated from our internal storage manager. Normally,
this does not cause problems because most systems have sufficient extra space in their engine storage
allocation to allow for this. STGDEBUG(X) however, adds a total of 96 bytes to each allocated block of
storage, which can quickly exceed your storage allocation. In most cases, double the value specified in the
MINIMUM parameter whenever you specify STGDEBUG(X). Also, ensure that you run this type of
debugging with the region set to 0M (REGION=0M).

Preferred dump options

User impact: You might experience a problem with Tivoli OMEGAMON XE for Storage on z/OS and IBM
Software Support requests that you set a SLIP to generate a console dump of the OMEGAMON address
space. However, you might be uncertain as to what SDATA options to used.

Workaround: Use the following SDATA parameters to all memory or console dumps taken for the Tivoli
OMEGAMON XE for Storage on z/OS product, unless IBM Software Support instructs you otherwise.
SDATA=(ALLNUC,CSA,LPA,PSA,RGN,SQA,SUM,TRT)

Understanding RAS1 logs and component prefixes

When you open a z/OS log such as RKLVLOG, you find a mix of status lines and numbered product
messages.

Most messages with IDs are documented in the problem determination guides for each monitoring agent.
You can also determine the meaning of a message by entering the message number into an Internet
search engine such a Google. The information that follows help you interpret the messages and status
lines in a z/OS log.

Format of messages in a RAS1 log

A RAS1 log for a monitoring agent on z/OS includes the following information:
v Environmental information

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 147
 – Operating system and CPU data. This information is prefaced with the following string:
PPPxxmmm

Where:
PPP Is the component prefix (See Table 7 for a list of component prefixes).
xx Is the component code (for example, NS Node Status).
mmm Is the module name (for example mdg/mgr for Model/Manager).
– Initial command-line settings
v Component summary, including the following:
– The name of the module
– Information about where the library was loaded from
– The date and time the module was compiled
– The version (if this detail was specified)
v Formatted output, including entry and exit points and text strings. Entry and exit points show flow into
and out of a given function. The exit shows the return code, if applicable. The text depends on the kind
of trace specified. Here is an example:
(00D41 F9C-1{99%}:KV4MAIN.CPP,953,"MainWnd::MainWnd") Entry
(00D41 FD3-1{99%}:KV4MAIN.CPP,959,"MainWnd::MainWnd") Exit
Time,Thread,{%stack avail},pgm_name,Line#,function,text
Not all functions are RAS1 enabled, and trace level may exclude some paths.

Determining which product or component generated a message

All components of Tivoli Management Services writes messages to various log files for the components. All
OMEGAMON XE monitoring agents also generate messages that are captured in message and trace files.

It is not always apparent what component has generated a message. To help you understand the
messages, Table 7 shows the prefixes for the components of all Tivoli Management Services components
and OMEGAMON XE monitoring agents that might be displayed in a log and trace file. The message
begins with one of the three-letter prefixes documented in the following table.
Table 7. Prefixes that might be displayed in message and trace files
Prefix Component
AOP AF/OPERATOR®, OMEGACENTER® Gateway for MVS
ATF OMEGAMON II for IMS™
BG OMEGAMON II for CICS®
BPO IBM Tivoli OMEGAMON XE for DB2 Performance Expert
CI OMEGAMON Base
CNDL OMEGAMON Base
CSAA Classic OMEGAMON
CV OMEGAMON for VM
DGO IBM Tivoli OMEGAMON XE for DB2 Performance Expert
DSM OMEGAMON II for IMS
DX DEXAN®
EA OMEGAMON II for MVS
EB EPILOG®
EC EPILOG
ED EPILOG

148 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
EI EPILOG
EO EPILOG
EP EPILOG
™
ETE End to End
ETX OMEGAMON II for IMS
EU OMEGAMON for VM
EV OMEGAMON for VM
EVS OMEGAMON II for IMS
EX OMEGAMON II for Mainframe Networks
FPE IBM Tivoli OMEGAMON XE for DB2 Performance Expert
H2C OMEGAMON II for DB2
IA Classic OMEGAMON
ICF OMEGAMON II for IMS
IN Classic OMEGAMON
KA2 Tivoli Enterprise Monitoring Server
KA4 Tivoli Enterprise Monitoring Server
KAB OMEGACENTER Gateway for MVS
KAG Configuration Tool, Tivoli Enterprise Monitoring Server
KAM Alert Adapter for OG/MVS, Alert Adapter for OMC Gateway MVS, Configuration Tool
KAO AF/OPERATOR, OMEGACENTER Gateway for MVS
KAT AF/OPERATOR, OMEGACENTER Gateway for MVS, OMEGACENTER Status Manager for MVS
KAU AF/Integrated Resource Manager, OMEGACENTER Gateway for MVS
KBB IBM Tivoli Monitoring Services:Engine or ITMS:Engine, Tivoli Enterprise Monitoring Server
KBF CASP Native Connector
KBL OMEGAMON XE for CASP
KBR OMEGAMON XE for CASP
KBX OMEGAMON XE for CASP, Configuration Tool
KC2 OMEGAMON II for CICS, Configuration Tool
KC3 Configuration Tool, OMEGAMON XE for CICS, IBM Tivoli OMEGAMON XE for CICS on z/OS
KC5 IBM Tivoli OMEGAMON XE for CICS on z/OS
KCA OMNIMON Base
KCC OMNIMON Base
KCF Candle Command Center for MQSeries® Configuration, IBM Tivoli OMEGAMON XE for WebSphere®
MQ, Generic Configuration, Configuration Tool
KCG OMEGAMON XE for IBM Cryptographic Coprocessors, Configuration Tool
KCI IBM Tivoli OMEGAMON XE for CICS on z/OS, Configuration Tool
KCN Configuration Tool, OMNIMON Base
KCO Tivoli Enterprise Monitoring Server
KCP Configuration Tool, IBM Tivoli OMEGAMON XE for CICS on z/OS
KCS OMEGAMON II for MVS

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 149
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
KD2 OMEGAMON II for DB2, Configuration Tool, IBM Tivoli OMEGAMON XE for DB2 Performance Expert
KD3 Configuration Tool, OMEGAMON XE for DB2, OMEGAMON XE for DB2 on z/OS
KD4 ITCAM for SOA
KD5 Configuration Tool, OMEGAMON XE for DB2 on z/OS, IBM Tivoli OMEGAMON XE for DB2
Performance Expert
KDB Configuration Tool, OMEGAMON II for DB2, IBM Tivoli OMEGAMON XE for DB2 Performance Expert
KDC IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KDE IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KDF OMEGAMON II for SMS, Configuration Tool, OMEGAMON II for IMS, Shared Probes
KDH IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KDP Configuration Tool, OMEGAMON XE for DB2, OMEGAMON XE for DB2 on z/OS, IBM Tivoli
OMEGAMON XE for DB2 Performance Expert, OMEGAMON XE for DB2plex
KDS Tivoli Enterprise Monitoring Server, Configuration Tool
KDZ Configuration Tool
KEB OMNIMON Base
KED OMEGAMON II for MVS
KEF Tivoli Enterprise Monitoring Server
KEI OMEGAMON II for IMS
KEP OMEGAMON II for MVS
KET Configuration Tool, End to End, OMEGAMON II for Mainframe Networks
KEX Tivoli Enterprise Monitoring Server
KEZ Tivoli Enterprise Monitoring Server
KFA Tivoli Enterprise Monitoring Server
KFAA Tivoli Enterprise Monitoring Server
KFW Tivoli Enterprise Monitoring Server
KFX Configuration Tool, CASP File Transfer
KGL Tivoli Enterprise Monitoring Server
KHI Tivoli Enterprise Monitoring Server
KHL IBM OMEGAMON z/OS Management Console
KHO Tivoli Enterprise Monitoring Server
KI2 Configuration Tool, OMEGAMON II for IMS
KI3 Configuration Tool, OMEGAMON XE for IMS, IBM Tivoli OMEGAMON XE for IMS on z/OS
KI5 IBM Tivoli OMEGAMON XE for IMS on z/OS
KIA OMNIMON Base
KIB Tivoli Enterprise Monitoring Server
KID Configuration Tool, OMEGAMON II for IMS
KIE IBM Tivoli OMEGAMON XE for WebSphere InterChange Server
KIH Tivoli Enterprise Monitoring Server
KIN Configuration Tool
KIP IBM Tivoli OMEGAMON XE for IMS on z/OS, Configuration Tool, OMEGAMON XE for IMSplex,
OMEGAMON XE for IMS, IBM Tivoli OMEGAMON XE for IMS on z/OS

150 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
KJI OMNIMON Base
KKC Configuration Tool
KKI Configuration Tool
KLB IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLC Tivoli Enterprise Monitoring Server, CL/CONFERENCE®
KLD IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLE IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLF IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLG Tivoli Enterprise Monitoring Server, CL/SUPERSESSION®
KLH CL/SUPERSESSION, IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLI Tivoli Enterprise Monitoring Server, CL/SUPERSESSION
KLS Tivoli Enterprise Monitoring Server, CL/SUPERSESSION
KLT IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLU IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLV IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLX IBM Tivoli Monitoring Services:Engine or ITMS:Engine
KLZ Tivoli Enterprise Monitoring Server
KM2 OMEGAMON II for MVS, Configuration Tool
KM3 IBM Tivoli OMEGAMON XE on z/OS, Configuration Tool, OMEGAMON XE for OS/390®, IBM Tivoli
OMEGAMON XE on z/OS
KM5 IBM Tivoli OMEGAMON XE on z/OS, IBM Tivoli OMEGAMON XE on z/OS
KMA Tivoli Enterprise Monitoring Server
KMC Candle Command Center for MQSeries Configuration, IBM Tivoli OMEGAMON XE for WebSphere
MQ, Configuration Tool, OMEGAMON XE for WebSphere MQ Configuration
KMH OMEGAMON II for MVS
KMQ Candle Command Center for MQSeries, Configuration Tool, OMEGAMON XE for WebSphere MQ
Monitoring
KMR OMEGAMON II for MVS
KMS Tivoli Enterprise Monitoring Server
KMV OMEGAVIEW®, Configuration Tool
KN3 IBM Tivoli OMEGAMON XE for Mainframe Networks, Configuration Tool
KNA IBM Tivoli NetView® for z/OS
KNS Tivoli Enterprise Monitoring Server
KNT Tivoli Enterprise Monitoring Server
KNV Tivoli Enterprise Monitoring Server
KNW Tivoli Enterprise Monitoring Server
KO2 Configuration Tool, OMEGAMON II for DB2, IBM Tivoli OMEGAMON XE for DB2 Performance Expert
KO4 Tivoli Enterprise Monitoring Server
KOB Configuration Tool, OMNIMON Base
KOC Configuration Tool, OMEGAMON II for CICS
KOCJ OMEGAMON II for CICS

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 151
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
KOE IBM Tivoli OMEGAMON XE on z/OS, Configuration Tool, OMEGAMON XE for OS/390 UNIX System
Services
KOG AF/OPERATOR, OMEGACENTER Gateway for MVS
KOI Configuration Tool, OMEGAMON II for IMS
KOM OMEGAMON II for MVS
KON OMEGAMON II for Mainframe Networks, Configuration Tool
KOQ Tivoli Enterprise Monitoring Server
KOR Tivoli Enterprise Monitoring Server
KOS Candle Command Center for Sysplex, IBM Tivoli OMEGAMON XE on z/OS, Configuration Tool,
OMEGAMON II for MVS, IBM Tivoli OMEGAMON XE on z/OS, OMEGAMON XE for Sysplex
KOX Tivoli Enterprise Monitoring Server
KOU Tivoli Enterprise Monitoring Server
KPD Configuration Tool, Tivoli Enterprise Monitoring Server
KPM OMEGAMON II for MVS
KPS Tivoli Enterprise Monitoring Server
KPT Tivoli Enterprise Monitoring Server
KPZ Configuration Tool
KQI CCC for MQSeries Integrator, IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers,
Configuration Tool, Tivoli Enterprise Monitoring Server, OMEGAMON XE for WebSphere Message
Broker Monitoring
KQM Tivoli Enterprise Monitoring Server
KRA IBM Tivoli OMEGAMON XE on z/OS, Configuration Tool, Tivoli Enterprise Monitoring Server,
OMEGAMON XE for OS/390, IBM Tivoli OMEGAMON XE on z/OS
KRC OMEGAMON II for SMS
KRI OMEGAMON II for IMS
KRR CASP Conversion with XML
KRT Configuration Tool
KRU CASP Analyze and Gather, CASP Conversion with XML
KS3 IBM Tivoli OMEGAMON XE for Storage on z/OS, Configuration Tool
KSA Tivoli Enterprise Monitoring Server
KSB Shared Probes
KSD OMEGAVIEW
KSH Tivoli Enterprise Monitoring Server
KSJ OMEGAMON XE for WebSphere Application Server
KSL OMEGACENTER Gateway for MVS
KSM Tivoli Enterprise Monitoring Server
KSS Tivoli Enterprise Monitoring Server
KTN Tivoli Enterprise Monitoring Server
KTR Tivoli Enterprise Monitoring Server
KTV Tivoli Enterprise Monitoring Server
KTX Tivoli Enterprise Monitoring Server

152 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
KUC CASP Universal Connector
KUD Tivoli Enterprise Monitoring Server
KUL Tivoli Enterprise Monitoring Server
KUM Tivoli Enterprise Monitoring Server
KUT Tivoli Enterprise Monitoring Server
KUX Tivoli Enterprise Monitoring Server
KVI Tivoli Enterprise Monitoring Server
KVT Tivoli Enterprise Monitoring Server
KVW IBM Tivoli NetView for z/OS
KWD Configuration Tool, OMEGAMON XE for OS/390
KWE Tivoli Enterprise Monitoring Server
KWO OMEGAVIEW II® for the Enterprise
KWW Configuration Tool, OMEGAMON XE for WebSphere Application Server
KXC Configuration Tool, CASP Analyze and Gather, CASP eBusiness Platform
KXD OMEGAMON II for MVS, IBM Tivoli OMEGAMON XE on z/OS
KXDF OMEGAMON II for MVS
KXM Configuration Tool, CASP Conversion with XML
KXO IBM Tivoli OMEGAMON XE on z/OS, CASP Access for WebSphere
KXS CASP eBusiness Platform, CASP Directory Services
KYN ITCAM for WebSphere, Tivoli Enterprise Monitoring Agent
KZ2 Configuration Tool
LAT OMEGAMON II for IMS
LSCX Classic OMEGAMON
ML OMEGAMON II for IMS
MRG OMEGAMON II for IMS
O2 OMEGAMON II for DB2
OB OMEGAMON Base
OBV OMEGAMON Base
OC OMEGAMON II for CICS
OGN OMEGAMON for VM
OM Classic OMEGAMON
OM2 OMEGAMON II for MVS
OMV OMEGAMON Base
OM0 Classic OMEGAMON
OMG AF/OPERATOR, OMEGACENTER Gateway for MVS
OR OMEGAMON II for IMS
OS OMEGAMON II for IMS
OTR OMEGAMON II for IMS
OV OMEGAMON for VM
PWA OMEGAMON II for IMS

Appendix A. General problem determination for Tivoli OMEGAMON XE monitoring agents on z/OS 153
Table 7. Prefixes that might be displayed in message and trace files (continued)
Prefix Component
REG OMEGAMON II for IMS
TRF OMEGAMON II for IMS
VEB OMEGAMON II for MVS

Using the Log and Trace Analyzer tool

Note: This tool is available in distributed environments and not in mainframe environments.

Tivoli Management Services V6.1 with Fix Pack 3 included a new tool, the Log and Trace Analyzer, that
helps you view, analyze and correlate log files. With the Log and Trace Analyzer, you can evaluate multiple
event and error logs with time synchronization. This tool makes it easier and faster to debug and resolve
problems within multi-tier systems by consuming data in the Common Base Event format and providing
specialized visualization and analysis of the data.

The Log and Trace Analyzer tool is launched from the Tivoli Enterprise Portal Event Tools view, which is
displayed as part of the Event Details workspace. You use the tool to view logs from Tivoli Enterprise
Portal Server or Tivoli Enterprise Monitoring Server

In addition to the Log and Trace Analyzer, specialized OMEGAMON adapters have been provided to aid in
problem determination for some of the more common problems that you might experience when using
Tivoli Management Services (Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Monitoring Server). The OMEGAMON adapters uses the Generic Log Adapter (GLA) to process
application log files and transform their contents into a common format for logging, management, and
problem determination and to facilitate communication between tools in a consistent way.

Additional information related to the Log and Trace Analyzer and the Generic Log Adapter is available at
http://www-128.ibm.com/developerworks/autonomic/probdet.html. OMEGAMON adapters and associated
documentation will be available for download from http://www.ibm.com/software/tivoli/
opal?NavCode=1TW10TM2U as they are developed.

The Web site is updated as additional adapters become available.

Maintaining the persistent datastore

Information about maintaining the persistent datastore on z/OS can be found in IBM Tivoli Monitoring:
Administrator’s Guide.

154 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Appendix B. Historical data collection disk space
requirements
This chapter provides the system administrator with the following information about warehousing historical
data:
v Configuring data export for the Dataset Attribute feature
For Dataset Attribute tables, set the History Collection Interval and the Warehouse Interval to one hour.
Otherwise export of the data to the warehouse might occur at undesirable intervals.
v Basic record sizes for each of the tables from which data is collected.
The following assumptions govern Table 8 on page 156:
– Items in the table that are marked "Yes" in the "Eligible for warehouse?" column are eligible to be
warehoused in IBM Tivoli Data Warehouse. See IBM Tivoli Monitoring: Installation and Setup Guide
for information on setting up the warehouse.
– Space estimates apply to one managed system for a 24-hour period.
– Space estimates assume a 15-minute Resource Monitoring Facility (RMF) interval or 15-minute
collection interval, as appropriate.
– The following formula is used to estimate space requirements: ((60/15) x 24 x Record size x
frequency)

© Copyright IBM Corp. 2006, 2007 155

 Table 8. Disk space requirements for historical data collection

156
File name for Eligible for
Attribute history table historical data warehouse? Record size Frequency Estimated space requirement
Application Dataset APPL_DSDET Yes 142 bytes 1 record per data set per 5325 kilobytes (assumes 20 monitored
Details monitored application per applications with 20 active data sets each)
interval
Application Monitoring APPL Yes 198 bytes 1 record per monitored 371 kilobytes (assumes 20 monitored
application applications)
Cache Control Unit CACHE_CU No 276 - 1364 1 record per cache control 828 kilobytes (assumes 32 control units)
bytes. 276 + unit per RMF interval
(68 per raid
rank on 2105)
Channel Path CHAN_PATH No 148 bytes 1 record per channel path per 888 kilobytes (assumes 64 channel paths
RMF interval online)
DASD Volume DASDPDS No 808 bytes 1 record per logical volume 606000 kilobytes (assumes 8000 devices)
Performance, DASD per RMF interval
Volume Space, Cache
Devices *
Dataset Attribute DA_ALCSUM Yes 148 (1 record * Top N value) per 3 kilobytes (assumes 1 Dataset Attribute
Allocated Space Dataset Attribute collection collection cycle per 24 hours and default Top
Summary * cycle N value of 20)
Dataset Attribute DA_BLKSUM Yes 178 (1 record * Top N value) per 1 kilobytes (assumes 1 Dataset Attribute
Blocksize Distribution Dataset Attribute collection collection cycle per 24 hours)
Summary * cycle

IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Dataset Attribute CA Split DA_CASSUM Yes 132 9 records (in other words, 5 kilobytes (assumes 1 Dataset Attribute
Summary * number of distinct ranges) per collection cycle per 24 hours and default Top
Dataset Attribute collection N value of 20)
cycle
Dataset Attribute Catalog DA_CATSUM Yes 226 (1 record * Top N value) per 3 kilobytes (assumes 1 Dataset Attribute
Summary * Dataset Attribute collection collection cycle per 24 hours and default Top
cycle N value of 20)
Dataset Attribute CI Split DA_CISSUM Yes 160 (1 record * Top N value) per 5 kilobytes (assumes 1 Dataset Attribute
Summary * Dataset Attribute collection collection cycle per 24 hours and default Top
cycle N value of 20)
Dataset Attribute Creation DA_CRTSUM Yes 226 (1 record * Top N value) per 1 kilobytes (assumes 1 Dataset Attribute
Date Distribution Dataset Attribute collection collection cycle per 24 hours)
Summary * cycle
 Table 8. Disk space requirements for historical data collection (continued)
File name for Eligible for
Attribute history table historical data warehouse? Record size Frequency Estimated space requirement
Dataset Attribute DSORG DA_ORGDTL Yes 132 8 records (in other words, 60 kilobytes (assumes 1 Dataset Attribute
Detail * number of distinct ranges) per collection cycle per 24 hours and default Top
Dataset Attribute collection N value of 20)
cycle
Dataset Attribute DSORG DA_ORGSUM Yes 178 (17 records * Top N value) 3 kilobytes (assumes 1 Dataset Attribute
Summary * per Dataset Attribute collection cycle per 24 hours)
collection cycle
Dataset Attribute Extent DA_EXTSUM Yes 160 17 records (in other words, 3 kilobytes (assumes 1 Dataset Attribute
Summary * number of DSORGs) per collection cycle per 24 hours and default Top
Dataset Attribute collection N value of 20)
cycle
Dataset Attribute DA_IBKSUM Yes 178 (1 record * Top N value) per 4 kilobytes (assumes 1 Dataset Attribute
Inefficient Blocksize Dataset Attribute collection collection cycle per 24 hours and default Top
Summary * cycle N value of 20)
Dataset Attribute Mature DA_MATSUM Yes 178 (1 record * Top N value) per 4 kilobytes (assumes 1 Dataset Attribute
Dataset Summary Dataset Attribute collection collection cycle per 24 hours and default Top
cycle N value of 20)
Dataset Attribute DA_NEWSUM Yes 210 (1 record * Top N value) per 3 kilobytes (assumes 1 Dataset Attribute
Newborn Dataset Dataset Attribute collection collection cycle per 24 hours and default Top
Summary * cycle N value of 20)
Dataset Attribute DA_REFSUM Yes 170 (1 record * Top N value) per 1 kilobytes (assumes 1 Dataset Attribute
Reference Date Dataset Attribute collection collection cycle per 24 hours)
Distribution Summary * cycle
Dataset Attribute SMS DA_SMSDTL Yes 132 8 records (in other words, 408 kilobytes (assumes 1 Dataset Attribute
Class Detail * number of distinct ranges) per collection cycle per 24 hours, 100 total SMS
Dataset Attribute collection constructs and default Top N value of 20
cycle
Dataset Attribute SMS DA_SMSSUM Yes 204 (1 record * Top N value) * 16 kilobytes (assumes 1 Dataset Attribute
Class Summary * (number of SMS Data + collection cycle per 24 hours and 100 total
Storage + Management SMS constructs)
Classes + Storage Groups)
per Dataset Attribute
collection cycle

Appendix B. Historical data collection disk space requirements

157
 Table 8. Disk space requirements for historical data collection (continued)

158
File name for Eligible for
Attribute history table historical data warehouse? Record size Frequency Estimated space requirement
Dataset Attribute System DA_SYSSUM Yes 158 1 record * (number of SMS 0.4 kilobytes (assumes 1 Dataset Attribute
Summary * Data + Storage + collection cycle per 24 hours)
Management Classes +
Storage Groups) per Dataset
Attribute collection cycle
Dataset Attribute DA_UNCDTL Yes 394 1 record per Dataset Attribute 870 kilobytes (assumes 1 Dataset Attribute
Uncataloged Dataset collection cycle collection cycle per 24 hours, 250 volumes
Detail * with Uncataloged data sets and default Top N
value of 20)
Dataset Attribute DA_UNCSUM Yes 174 (1 record * Top N value * 30 kilobytes (assumes 1 Dataset Attribute
Uncataloged Dataset number of volumes with collection cycle per 24 hours and 250 volumes
Summary * Uncataloged data sets) per with Uncataloged data sets)
Dataset Attribute collection
cycle
Dataset Attribute DA_NRFSUM Yes 122 (1 record * number of 4 kilobytes (assumes 1 Dataset Attribute
Unreferenced Dataset volumes with Uncataloged collection cycle per 24 hours and default Top
Summary * data sets) per Dataset N value of 20)
Attribute collection cycle
Dataset Attribute Unused DA_UNUSUM Yes 190 (1 record * Top N value) per 3 kilobytes (assumes 1 Dataset Attribute
Space Summary * Dataset Attribute collection collection cycle per 24 hours and default Top
cycle N value of 20)
* See “Configuring data export for the Dataset Attribute feature” on page 155 for configuration tips.

IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Dataset Group Details DSNG_DETL Yes 785 bytes 1 record per Dataset Group 29438 kilobytes (assumes 20 Dataset Groups
per Dataset per interval with 20 data sets each)
Dataset Group Details DSNG_ATTR Yes 191 bytes 1 record per Dataset Group 7163 kilobytes (assumes 20 Dataset Groups
Attributes per Dataset per interval with 20 data sets each)
Dataset Group Details DSNG_DVOL Yes 292 bytes 1 record per Dataset Group 10950 kilobytes (assumes 20 Dataset Groups
Volume per Dataset per Volume per with 20 data sets each with 1 volume each)
interval
Dataset Group Summary DSNG_SUMM Yes 382 bytes 1 record per Dataset Group 717 kilobytes (assumes 20 Dataset Groups)
per interval
Dataset Performance HDSN_IO_ST No 300 bytes 1 record per monitored data 56250 kilobytes (assumes 2000 data set
set per application accessing records)
the data set per RMF interval
 Table 8. Disk space requirements for historical data collection (continued)
File name for Eligible for
Attribute history table historical data warehouse? Record size Frequency Estimated space requirement
HSM CDS HSM_CDS Yes 98 bytes 1 record per control data set 37 kilobytes (assumes single data set cds)
per interval
HSM Function Statistics HSM_FUN_DA Yes 100 bytes 1 record per HSM function 65 kilobytes
per interval
HSM Function Status HSM_FUN_ST No 87 bytes 1 record per interval 8 kilobytes
HSM Function Summary HSM_ACTVTY Yes 87 bytes 1 record per function per 41 kilobytes
interval
HSM Requests HSM_REQS Yes 198 bytes 1 record per request at time 186 kilobytes (assumes 10 queued requests)
of interval per interval
HSM Status HSM_STATUS Yes 145 bytes 1 record per interval 14 kilobytes
Logical Control Unit LCU No 349 bytes 1 record per logical control 1047 kilobytes (assumes 32 logical control
unit per RMF interval units)
SMS Cache Sets CACHE_SET Yes 203 bytes 1 record per cache set per 190 kilobytes (assumes 10 cache sets)
interval
SMS Configuration SMS_CONFIG Yes 191 bytes 1 record per interval 18 kilobytes
SMS Data Class SMS_DAT_CL Yes 317 bytes 1 record per data class per 594 kilobytes (assumes 20 data classes)
interval
SMS Management Class SMS_MAN_CL Yes 300 bytes 1 record per management 562 kilobytes (assumes 20 management
class per interval classes)
SMS Storage Class SMS_ST_CL Yes 273 bytes 1 record per storage class per 512 kilobytes (assumes 20 storage classes)
interval
SMS Storage Group SMS_ST_GRP Yes 459 bytes 1 record per storage group 861 kilobytes (assumes 20 storage groups)
per interval
SMS Storage Group ST_GRP_STA Yes 99 bytes 1 record per storage group 186 kilobytes (assumes 20 storage groups)
Status per interval
SMS Systems SMS_SYSTEM Yes 69 bytes 1 record per system in the 52 kilobytes (assumes 8 systems)
sms plex per interval
Symmetrix Configuration SYM_CONFIG No 344 bytes 1 record per Symmetrix 129 kilobytes (assumes 4 Symmetrix storage
storage facility per RMF facilities)
interval

Appendix B. Historical data collection disk space requirements

159
 Table 8. Disk space requirements for historical data collection (continued)

160
File name for Eligible for
Attribute history table historical data warehouse? Record size Frequency Estimated space requirement
Symmetrix Devices SYM_DSK_DV No 104 - 32744 1 record per Symmetrix 15219 kilobytes (assumes 4 Symmetrix
bytes. 44 + storage facility per RMF storage facilities with 2024 devices each)
(20 per interval
device)
Symmetrix Directors SYM_DSK_DR No 196 - 8512 1 record per Symmetrix 1560 kilobytes (assumes 4 Symmetrix storage
bytes. 64 + storage facility per interval facilities with 64 directors each)
(132 per
director)
Tape Device TAPE_DEV Yes 115 bytes 1 record per tape device per 345 kilobytes (assumes 32 tape drives)
interval
Tape Group TAPE_GRP Yes 258 bytes 1 record per tape group per 193 kilobytes (assumes 8 tape groups)
interval
TotalStorageDS Array TDS_ARRAY No 124 bytes 1 record per TotalStorageDS 372 kilobytes (assumes 128 arrays)
array per RMF interval
TotalStorageDS TDS_CONFIG No 142 bytes 1 record per TotalStorageDS 53 kilobytes (assumes 4 TotalStorage® DS
Configuration storage facility per RMF storage facilities)
interval
TotalStorageDS Extent TDS_EXPOOL No 197 bytes 1 record per TotalStorageDS 591 kilobytes (assumes 32 extent pools)
Pool extent pool per RMF interval
TotalStorageDS Rank TDS_RANK No 210 bytes 1 record per TotalStorageDS 2520 kilobytes (assumes 128 ranks)
rank per RMF interval

IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide

Volume Group Summary DASD_SUMM No 192 bytes (1 record per storage group + 900 kilobytes (assumes a total of 50 storage
1 record per user dasd group and user dasd groups)
+3) per interval
VTS Cache, VTS HVIRTULTAP No 516 bytes 1 record per VTS per hour 193 kilobytes (assumes 4 vts units)
Capacity, VTS Composite
Library, VTS Overview,
VTS Physical Devices,
VTS Virtual Devices
VTS Virtual Devices HVTSDEVICE No 112 - 4144 1 record per VTS per hour 389 kilobytes (assumes 4 vts units with 64
Summary bytes. 48 + virtual drives each)
(64 per virtual
device)
* See “Configuring data export for the Dataset Attribute feature” on page 155 for configuration tips.
Appendix C. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This section describes the
following options for obtaining support for IBM software products:
v “Using IBM Support Assistant”
v “Obtaining fixes” on page 162
v “Obtaining PTFs (Program Temporary Fixes)” on page 162
v “Receiving weekly support updates” on page 162
v “Contacting IBM Software Support” on page 163
v “Capturing z/OS logs to send to IBM Software Support” on page 165

Using IBM Support Assistant

The IBM Support Assistant is a free, standalone application that you can install on any workstation. You
can then enhance the application by installing product-specific plug-in modules for the IBM products you
use.

The IBM Support Assistant saves you time searching product, support, and educational resources. The
IBM Support Assistant helps you gather support information when you need to open a problem
management record (PMR), which you can then use to track the problem.

The product-specific plug-in modules provide the following resources:

v Support links
v Education links
v Ability to submit problem management reports
For more information, see the IBM Support Assistant Web site at http://www.ibm.com/software/support/isa.

Install and set up the IBM Support Assistant as follows:

1. Download the IBM Support Assistant installation software from the following Web site:
http://www.ibm.com/software/support/isa.
2. Unzip or untar the downloaded file.
3. Run the installation file and respond to the prompts from the installer.
4. Launch the IBM Support Assistant. For example, on Windows XP click IBM Support Assistant in the
following menu path: Start > All Programs > IBM Support Assistant. The Welcome page is
displayed.
5. Select the Updater hyperlink to access the Updater page.
6. Access the Upgrades tab and the IBM Support Assistant tab to select the product-specific plug-in
modules that you want to install.

If you cannot find the solution to your problem in the IBM Support Assistant, you can also check the
following Internet resources for information that might help you resolve your problem:
v Forums and news groups
v Google.com

© Copyright IBM Corp. 2006, 2007 161

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes are available for your
IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.
2. Under Find product support, click All IBM software (A-Z). This opens the software product list.
3. In the software product list, click IBM Tivoli OMEGAMON XE for Storage on z/OS. This opens the
product support site.
4. Under Solve a problem, click APARs to go to a list of fixes, fix packs, and other service updates for
IBM Tivoli OMEGAMON XE for Storage on z/OS
5. Click the name of a fix to read the description and optionally download the fix. You can also search
for a specific fix; for tips on refining your search, click Search tips.
6. In the Find downloads and drivers by product section, select one software category from the
Category list.
7. Select one product from the Sub-category list.
8. Type more search terms in the Search within results if you want to refine your search.
9. Click Search.
10. From the list of downloads returned by your search, click the name of a fix to read the description of
the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM Software Support Handbook
at http://techsupport.services.ibm.com/guides/handbook.html.

Obtaining PTFs (Program Temporary Fixes)

The following steps describe how to identify and obtain required maintenance, known as PTFs (Program
Temporary Fixes):
1. Access the “Technical help database page for mainframe Preventive Service Planning (PSP) buckets”
Web page: http://www14.software.ibm.com/webapp/set2/psp/srchBroker
2. Find relevant PSP Buckets. Search for PSP Buckets that have the Tivoli OMEGAMON XE for Storage
on z/OS, V4.1.0 prefix: OMXES4100.
3. Consult each PSP Bucket to learn what PTFs are required.
4. Access the Shop z-Series Web site to obtain the PTFs: https://www14.software.ibm.com/webapp/
ShopzSeries/ShopzSeries.jsp

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.
2. Click My support in the far upper-right corner of the page under Personalized support.
3. If you have already registered for My support, sign in and skip to the next step. If you have not
registered, click register now. Complete the registration form using your e-mail address as your IBM
ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Systems management. A third list is
displayed.
7. In the third list, select a product sub-segment, for example, Application Performance & Availability.
A list of applicable products is displayed.
8. Select the products for which you want to receive updates.

162 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email on the Edit profile
tab.
11. Select Please send these documents by weekly email.
12. Update your e-mail address as needed.
13. In the Documents list, select Software.
14. Select the types of documents that you want to receive information about.
15. Click Update.

If you experience problems with the My support feature, you can obtain help in one of the following ways:
Online
Send an e-mail message to erchelp@ca.ibm.com, describing your problem.
By phone
Call 1-800-IBM-4YOU (1-800-426-4968).

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance
contract, and you must be authorized to submit problems to IBM. The type of software maintenance
contract that you need depends on the type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli, Lotus®, and Rational®
products, as well as DB2 and WebSphere products that run on Windows, or UNIX operating systems),
enroll in Passport Advantage® in one of the following ways:
Online
Go to the Passport Advantage Web site at http://www-306.ibm.com/software/howtobuy/
passportadvantage/pao_customers.htm .
By phone
For the phone number to call in your country, go to the IBM Software Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic
region.
v For customers with Subscription and Support (S & S) contracts, go to the Software Service Request
Web site at https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink™, CATIA, Linux®, OS/390, iSeries™, pSeries®, zSeries, and other support
agreements, go to the IBM Support Line Web site at http://www.ibm.com/services/us/index.wss/so/its/
a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and WebSphere products that
run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance
agreement by working directly with an IBM sales representative or an IBM Business Partner. For more
information about support for eServer software products, go to the IBM Technical Support Advantage
Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV
(1-800-426-7378) in the United States. From other countries, go to the contacts page of the IBM Software
Support Handbook on the Web at http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region for phone numbers of people who provide support for your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact” on page 164
2. “Describing problems and gathering information” on page 164

Appendix C. Support information 163

3. “Submitting problems”

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to
understand and assess the business impact of the problem that you are reporting. Use the following
criteria:
Severity 1
The problem has a critical business impact. You are unable to use the program, resulting in a
critical impact on operations. This condition requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less significant features (not
critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact on operations, or a
reasonable circumvention to the problem was implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant background information
so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know
the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software
Support is likely to ask for this information.
v Can you recreate the problem? If so, what steps were performed to re-create the problem?
v Did you make any changes to the system? For example, did you make changes to the hardware,
operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to explain the workaround
when you report the problem.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site athttp://www.ibm.com/
software/support/probsub.html. Type your information into the appropriate problem submission
form.
By phone
For the phone number to call in your country, go to the contacts page of the IBM Software Support
Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your
geographic region.

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM
Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the
problem in detail. Whenever possible, IBM Software Support provides a workaround that you can
implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same problem can benefit from
the same resolution.

164 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Capturing z/OS logs to send to IBM Software Support
This section describes how to capture z/OS logs to send to IBM Software Support. To save a log to a file
rather than viewing it online, you need to know how to do the following:
v “Saving the contents of a z/OS log such as RKLVLOG”
v “Ending one RKLVLOG and starting another” on page 166

Saving the contents of a z/OS log such as RKLVLOG

To save the information in your z/OS logs (such as RKLVLOG), use the System Display and Search
Facility (SDSF) facility that is part of TSO. Follow these instructions to use SDSF to capture (in this
example) the RKLVLOG associated with any running task in your z/OS monitoring agent.
1. From ISPF, select the SDSF option using the =s.st 2 option (for RKLVLOG; sometimes these options
are different).
2. Enter the following on the command line: st taskname, where taskname is the name of the procedure
for the log that you want to display and capture. For example, entering st cansn3 on the command line
enables you to see the Tivoli OMEGAMON XE for Storage on z/OS agent job.
3. From the SDSF screen, enter ? next to the name of the started task to display a list of the output files
like the following. For example the output files for the sample cansn3 task noted above looks like this:
JESMSGLG JES2
JESJCL JES2
JESYSMSG JES2
SYSTSPRT CANSN3
SYSPRINT CANSN3
RKLVLOG CANSN3
RKLVSNAP CANSN3
RKPDLOG CANSN3
KS3ANMON CANSN3
KS3ACTCS CANSN3
4. To print the RKLVLOG for this job to a data set, type an s next to the RKLVLOG output file.
5. On the command line of SDSF, type: print d
The d parameter causes the file to be printed to a data set.
6. Press Enter. A panel similar to the one in Figure 2 is displayed.

COMMAND INPUT ===> SCROLL ===> CSR

Data set name ===> ’USER1.NMP181.D26033.CANSON.SYSLOG’

Member to use ===>
Disposition ===> NEW (OLD, NEW, SHR, MOD)

If the data set is to be created, specify the following.

Volume serial will be used to locate existing data sets if specified.

Management class ===> (Blank for default management class)

Storage class ===> (Blank for default storage class)
Volume serial ===> (Blank for authorized default volume) *
Device type ===> (Generic unit or device address) *
Data class ===> (Blank for default data class)
Space units ===> TRKS (BLKS, TRKS, CYLS, BY, KB, or MB)
Primary quantity ===> 5 (In above units)
Secondary quantity ===> 5 (In above units)
Directory blocks ===> 0 (Zero for sequential data set)
Record format ===> VBA
Record length ===> 240
Block size ===> 3120
* Only one of these fields may be specified

Figure 2. SDSF print to database panel

Appendix C. Support information 165

7. Type the data set name and characteristics for the file you are printing and press Enter.
8. You are returned to the RKLVLOG output file. On the command line, specify the number of lines you
want to print by entering a range that includes the entire file, such as:
print 1 99999999

Then press Enter. A message in the upper right corner of the panel tells you how many lines have
been printed.
9. Type print close on the SDSF command line to close the file. The log is now saved in the data set
that was specified in Step 6 on page 165.

For more information about SDSF commands, see z/OS SDSF Operation and Customization (SA22-7670).

Ending one RKLVLOG and starting another

When you recreate a problem to send it to IBM Software Support, you can use a z/OS MODIFY command
to close the current RKLVLOG spool data set and open a new one. This command is issued from a z/OS
console. The TLVLOG command manages the recording of information to RKLVLOG. The syntax and
usage of this command are as follows:


MODIFY stcname , TLVLOG SWITCH

, CLASS= class , COPIES= copies , DEST= dest

, FCB= fcb , FORM= form NO , MAXLINES= maxlines
HOLD=
YES


, UCS= ucs , USER= user , WTRNAME= wtrname

Where:
SWITCH
Is the keyword that dynamically allocates a new RKLVLOG file using the current values, begins
recording on the new file, and closes the current RKLVLOG file, releasing it for processing by JES.
class Is the one-character JES SYSOUT class. CLASS=A is the ITMS:Engine startup value.
copies Is the copy count. The valid range is 1-254. COPIES=1 is the startup value.

Note: JES2 allows 255, but JES3 allows only 254.

dest Is the 1-8 character JES SYSOUT destination. DEST=() is the startup value.
fcb Is the 1-4 character FCB name to be used. FCB=() is the startup value.
form Is the 1-4 character form name to be used. FORM=() is the startup value.
hold Determines whether the SYSOUT is placed in a JES operator hold when spun off. Specify YES
(operator hold is requested) or NO. HOLD=NO is the startup value.

Note: If HOLD=YES is specified, you must issue the appropriate JES release command for the
SYSOUT data set to be processed by JES.
maxlines
Is the maximum number of lines to be written to RKLVLOG, in thousands (for example,
MAXLINES=2 means a maximum of 2000 lines). The valid range is 0 through 16000 (16 million
lines). When this number is reached, an automatic TLVLOG SWITCH is performed, closing the
current RKLVLOG and allocating a new one If the specified value is 0, there is no maximum; you
must manually enter TLVLOG SWITCH to switch log files. MAXLINES=0 is the startup value.

166 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
 Note: Unlike the other values, MAXLINES takes effect immediately. If the new MAXLINES value
is less than the number of lines that have already been written to the current RKLVLOG, a
switch is immediately performed.
ucs Specifies the 1-character to 4-character UCS name to be used. UCS=() is the startup value.
user Is the 1-8 character user ID to which the SYSOUT is to be spooled. Ignored if DEST is blank.
USER=() is the startup value.
wtrname
Is the 1-8 character external writer name to be used. WTRNAME=() is the startup value.

Usage Notes:
1. The TLVLOG command performs up to three functions, depending on the keywords that are specified.
Assuming that you selected all three functions, they are performed in the following order:
a. Updates the dynamic allocation values. With the exception of MAXLINES, these values are used
when the next dynamic allocation is performed. Values are updated whenever they are coded on
the command.
b. Lists the current dynamic allocation values. This is always done.
c. Switches RKLVLOGs. This is done only when SWITCH is specified on the command.

Note: You may update values and request a switch with the same command; the values are updated
first, then the switch is performed.
2. RKLVLOGs may be automatically closed after a certain number of records have been written to them,
similar to the MVS SYSLOG processing. Refer to the MAXLINES keyword for more information.
3. To set up an automatic RKLVLOG switch whenever the ITMS:Engine address space is started, add the
following command to your RKANCMD startup CLIST:
TLVLOG MAXLINES=nnn

This command causes RKLVLOG to be automatically closed and released to JES whenever nnn
thousands of lines have been written. If needed, you can add other installation-dependent values (for
example, CLASS) to this command.
4. Many diagnostic messages are recorded in RKLVLOG. If you set RKLVLOG to spin off automatically,
or if you explicitly switch RKLVLOG, you must ensure that the SYSOUT files are kept at least for the
life of the ITMS:Engine run, in case they are required for problem solving.
5. You might want to issue a TLVLOG SWITCH command after a problem occurs. This command spins off
the RKLVLOG data relating to the problem into a separate spool data set, which can be included as
part of the ITMS:Engine standard problem documentation. Be sure to include all previously spun-off
RKLVLOG files
6. Because RKLVLOG is managed with standard IBM data management routines, records are buffered
before being written. If you are viewing the currently active RKLVLOG with a product such as SDSF,
you will not see the latest messages. Issue the command FLUSH TLVLOG to force the current data
management buffer to be written. Do not use the TLVLOG SWITCH to spin off the current RKLVLOG for
this purpose, as it will unnecessarily fragment the messages recorded in RKLVLOG.
7. Unless you explicitly set a non-zero MAXLINES value, RKLVLOG will never automatically switch.
8. If any error occurs when writing to RKLVLOG, ITMS:Engine will issue a message and disable
RKLVLOG recording. However, messages will still be written to VIEWLOG and all active operator
interfaces. Depending on the error, you may be able to restart RKLVLOG by issuing a switch request.

Here are some example of ways to use this command:

1. To list the current RKLVLOG destination and values:
tlvlog
2. To establish class X and destination SYSPROG as default SYSOUT attributes, and the maximum
number of lines as 20,000:

Appendix C. Support information 167

 tlvlog class=x dest=sysprog maxlines=20
3. To switch to a new RKLVLOG:
tlvlog switch

Flushing the log buffers

After a TLVLOG is switched, issuing an echo command can flush the log buffers and ensure that new
messages are written to the new RKLVLOG. The ECHO command echoes any text entered back to the
screen. The syntax of the ECHO command is shown below:


ECHO

string

Where:
string Is a character string to be echoed back to the operator screen where the ECHO command was
entered.

Usage Notes::
1. Use ECHO to verify that the ITMS:Engine operator facility is functioning properly and to force all
buffered messages to the log.
2. Even after an ECHO, log output may not be visible in JES3 systems. This is a result of the way JES3
manages spool buffers.
3. Enclosing string in single quotes is not necessary unless you want to preserve leading blanks.

168 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Appendix D. Notices
This information was developed for products and services offered in the U.S.A. IBM not offer the products,
services, or features discussed in this document in other countries. Consult your local IBM representative
for information on the products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM product, program, or
service be used. Any functionally equivalent product, program, or service that does not infringe any IBM
intellectual property right be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries,
in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply in the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore this statement not apply to you.

This publication might include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication. IBM
make improvements and/or changes in the products and/or the programs described in this publication at
any time without notice.

Licensees of this program who want to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or
any equivalent agreement between us.

© Copyright IBM Corp. 2006, 2007 169

Trademarks
AIX, Candle, CICS, Common User Access, CUA, DB2, DB2 Universal Database, developerWorks,
eServer, IBM, the IBM logo, IBMLink, iSeries, Lotus, MVS, OMEGAMON, OMEGAMON II, OMEGAVIEW,
OMEGAVIEW II, OS/390, Passport Advantage, ProductPac, pSeries, Rational, Redbooks, S/390,
SystemPac, System z, Tivoli, the Tivoli logo, Tivoli Enterprise, VTAM, WebSphere, z/OS, and zSeries are
trademarks or registered trademarks of International Business Machines Corporation in the United States,
other countries, or both.

Intel, Intel Inside (logos), MMX, Celeron, Intel Centrino, Intel Xeon, Itanium, Pentium, and Pentium II Xeon
are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other
countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

170 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Index
Special characters data collection (continued)
troubleshooting 115
!Trace in VTAMDATA, enabling 147
data missing in persistent data store 119
data row identifiers not exported 118
data set I/O collection, tuning 123
A data warehousing
abends logs 136
U200 Port in use message 114 data, collecting diagnostic 146
accessibility x Dataset Attributes Database
attributes checking for looping 129
space required for historical data collection 155 checking VTOC 130
checking warehousing 130
contrasted with DCOLLECT 129
B data collection 129
books problem determination 129
see publications vii, ix DCOLLECT contrasted with Dataset Attributes
browser client logs 135 Database 129
buffers, flushing log 168 DCS communications tracing 138
debugging, collecting data 146
!Trace in VTAMDATA 147
C disabling KDFDEVIN DEBUG 146
Candle and IBM terms xi enabling KDFDEVIN DEBUG 146
capturing log files for IBM Software Support 165 enabling STBDEBUG(X) 147
cmwras1.log 111 preferred dump options for SDATA 147
collecting diagnostic data 146 desktop client logs 134
collecting log files 134, 135 DFSMShsm space-size values exceeded 115
collection of monitoring data 115 diagnostic data, collecting 146
communications trace, enabling 145 directory names, notation xi
component prefixes, understanding 148 disk space requirements
components, messages for 5 historical data collection 155
Configuration Tool documentation
specifying startup console messages 145 IBM Tivoli Monitoring vii
specifying storage detail logging 145 OMEGAMON II for SMS ix
specifying trace logging 145 OMEGAMON XE for Storage on z/OS vii
Configuration Tool used to set up tracing 145 other resources viii
configuring trace logging 138 RedBooks viii
console dumps, setting a SLIP 147 drwtsn32.log 110
conventions dump, console, for debugging 147
terminology ix dumpcvt, ras1 subcommand 143
typeface x dynamic workspace linking 130
cross-product linking
problem determination 130
cross-product links missing 130 E
customer support 161 ECHO command for flushing log buffers 168
See Software Support education 161
see Tivoli technical training x
enabling storage allocation detail logging 116
D enabling summarization and pruning agent 120
data 118 ending RKLVLOG spool data set 166
generation of reports 118 environment variables for trace logging 138
historical 118 environment variables, notation xi
long-term 118 error conditions 125
real-time 118
short-term 118
data collection F
Dataset Attributes Database 129 features, messages for 5
problem determination 115 fixes, obtaining 162

© Copyright IBM Corp. 2006, 2007 171

flow of problem determination, logging 133
flushing log buffers 168
J
javalog.txt 111
format of messages 3
format of RAS1 messages, understanding 147
K
G KBB_RAS1 trace configuration setting 133
KCJ.log 111
general issues for OMEGAMON XE 133
kcjras1.log 111
generating log files 3
KDC_DEBUG environment variable for trace
generation of data reports 118
logging 138
Generic Log Adapter (GLA) 154
KDC_FAMILIES environment variable 138
Google, searching for message IDs 147
KDF and KDFA-prefixed messages 55
KDFC-prefixed messages 71
KDFD-prefixed messages 73
H KDFDEVIN DEBUG parameter 146
hang detection on volsers 125 KDFH to KDFL-prefixed messages 91
historical (long-term) data reports 119 KDFS-prefixed messages 93
historical data KDFSYSIN DEBUG parameter 147
problem determination 119, 120 KDSENV member of RKANPARU for trace logs 138
data unavailable or gaps in data 123 KFW_REPORT_TERM_BREAK_POINT. environmental
remote procedure calls 126 variable 124
requests failing and timing out 126 kfwenf configuration file 113
summarization and pruning 120 KFWITM081E link target not found 130
troubleshooting KFWRAS1.LOG 111
long response times 124 KLE_CryptoGetFP message 113
no results returned 124 KRC-prefixed messages 103
historical data collection KS3ACTCS sysout data set or spool file 137
disk space requirements 155 KS3ENV member of RKANPARU for trace logs 138
typical frequencies 155
historical tables
warehousing 119, 155
historical workspace
L
library
no data 113
IBM Tivoli Monitoring vii
hung volumes 125
OMEGAMON II for SMS ix
OMEGAMON XE for Storage on z/OS vii
other resources viii
I link target not found 130
IBM and Candle terms xi links between workspaces 130
IBM Redbooks 161 locations of message logs 3
IBM Software Support Log Adapter, Generic 154
data to collect 109 Log and Trace Analyzer tool, using 154
IBM support assistant 161 log buffers, flushing 168
IBM Tivoli Data Warehouse log files
log files 112 browser client 135
space requirements 155 capturing 165
IBM Tivoli Monitoring cmwras1.log 111
library vii collecting 134, 135
IBM Tivoli Monitoring general issues 133 component prefixes 148
IBM Tivoli Monitoring Services console data warehousing 136
setting trace levels dynamically 142 desktop client 134
IBM Tivoli Monitoring Services Index for finding drwtsn32.log 110
consoles 142 ECHO command for flushing log buffers 168
identifiers for data rows not exported 118 flushing log buffers 168
identifying hung volumes 125 format of RAS1 messages 147
index for finding IBM Tivoli Monitoring Services historical data collection 136
consoles 142 javalog.txt 111
installation and configuration kcj.log 134
troubleshooting 113 KCJ.log 111
Integrated Cryptographic Service Facility kcjr.log 134
troubleshooting 113 kcjras1.log 111, 134

172 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
log files (continued)
KFWRAS1.LOG 111
N
notation
KS3ACTCS 137
environment variables xi
locations 134
path names xi
RKLVLOG 137
typeface xi
RKLVLOG spool data set 166
RKLVSNAP 137
RKPDLOG 119, 137
Summarization and Pruning agent 136 O
timestamping 136 OMEGAMON II for SMS
Tivoli Data Warehouse 110, 112 library ix
Tivoli Enterprise Monitoring Server 136 OMEGAMON II for SMS messages
Tivoli Enterprise Monitoring Server on UNIX 111 KDF and KDFA prefix 55
Tivoli Enterprise Monitoring Server on Windows 111 KDFC prefix 71
Tivoli Enterprise Monitoring Server on z/OS 111 KDFD prefix 73
Tivoli Enterprise Portal 110, 111 KDFH to KDFL prefix 91
browser client 135 KDFS prefix 93
desktop client 134 KRC prefix 103
Tivoli Enterprise Portal Server 111, 136 OMEGAMON XE for Storage on z/OS
TLVLOG and flushing log buffers 168 library vii
user.dmp 110 OMEGAMON XE general issues 133
warehouse proxy 110, 112, 136 online publications
WAREHOUSELOG 137 accessing ix
z.OS components 110 opening RKLVLOG spool data set 166
logging ordering publications ix
overview 108 overview
storage detail 116 problem determination 105
logging contrasted with tracing 133
logs
RAS1 trace log 133 P
looping, checking for in Dataset Attributes path names, notation xi
Database 129 performance
Dataset Attributes Database 129
historical data collection 124
M problem determination 119, 123
maintenance Tivoli Data Warehouse 123
applying 107 troubleshooting 119, 123
maintenance of the persistent datastore 154 tuning data set I/O collection 123
manuals persistent data store problems 119
see publications vii, ix persistent datastore, maintenance of the 154
message IDs, searching for in Google 147 plugin1.4.2.trace file 135
messages preferred dump options 147
for product components or features 5 prefixes of monitoring components in logs 148
format 3 printing contents of RKLVLOG 165
format of, in logs 147 printing contents of z/OS logs 165
identifiers 3 problem determination 105
introduction 3 agent is running out of storage 116
KDF and KDFA prefix 55 capturing log files for IBM Software Support 165
KDFC prefix 71 collecting diagnostic data 146
KDFD prefix 73 !Trace in VTAMDATA 146
KDFH to KDFL prefix 91 KDFDEVIN DEBUG parameter 146
KDFS prefix 93 Preferred dump options 146
KRC prefix 103 STBDEBUG(X) 146
locations 3 communications trace 145
prefixes 148 component prefixes 148
Tivoli Data Warehouse 136 cross-product linking 130
types 3 cross-product links missing 130
monitoring agent data collection 115
problem determination 113 data reports 118
historical (long-term) data reports 119
monitoring data 115

Index 173
problem determination (continued) problem determination (continued)
data collection (continued) trace logging (continued)
real-time data 118 setting dynamically 142
short-term data 118 setup with Configuration Tool 145
data to collect 109 V4.1 workspace links to V3.1 workspaces 131
data warehousing logs 135 VTS data 115
Dataset Attributes Database 129 warehousing data 119
default port for TCP/IP profile 114 workspace data 115
describing problems 164 workspace links to prior product versions 131
determining business impact 164 z/OS system logs 137
dynamic workspace linking 130 problem determination flow, logging 133
error conditions 125 problem resolution 161
example, trace logging syntax 141 product features 129
format of RAS1 messages 147 PSP bucket
general issues for OMEGAMON XE 133 finding 107
historical data PTFs
summarization and pruning agent 120 obtaining 107
historical workspaces 113 publications vii
hubs, multiple 113 accessing online ix
identifiers for data rows not exported 118 ordering ix
information sources 105, 109
installation and configuration 113
Integrated Cryptographic Service Facility 113 R
KDC_DEBUG environment variable 138 ras1 command 143
KFWITM081E link target not found 130 RAS1 messages, format 147
log files 110 RAS1 trace log 133
monitoring agents RAS1 tracing 139
historical data collection 123 setup 139
remote procedure calls during warehousing 126 syntax 139
overview 105 trace levels 141, 142
performance 123 real-time data 118
persistent data store 119 record size
process 107 historical data collection 155
product features 129 remote procedure call error 126
RAS1 setup 139 reports 118
RAS1 syntax 139 Dataset Attributes Database 129
RAS1 trace levels 141 generation of 118
reproducible problems 134 historical data 118
RKANPARU 141 long-term data 118
setup trace logging with Configuration Tool 145 real-time data 118
sources of problems 134 short-term data 118
space-size values exceeded 91, 115 reproducible problems 134
SQL queries 119 return code 0, Take Action commands 113
startup console messages 145 RKANPAR member KDFDEVIN, debugging
storage detail logging 145 parameter 146
submitting problems 164 RKANPAR member KDFSYSIN, debugging
tape refresh interval 116 parameter 147
tips 105 RKANPARU member and trace logging 141
Tivoli Enterprise Monitoring Server 113 RKLVLOG
connection to wrong hub 113 flushing log buffers 168
Tivoli Enterprise Monitoring Server logs 135 printing contents of 165
Tivoli Enterprise Portal client problems 137 saving contents of 165
Tivoli Enterprise Portal Server logs 135 spool data set, ending one and starting another 166
Tivoli Enterprise Portal Server problems 137 RKLVLOG data storage messages 116
trace logging 138 RKLVLOG log 114
communications trace 145 RKLVLOG sysout data set or spool file 137
KDC_DEBUG environment variable 138 RKLVSNAP sysout data set or spool file 137
RAS1 setup 139 RKPDLOG 119
RAS1 syntax 139 RKPDLOG sysout data set or spool file 137
RAS1 trace levels 141
RKANPARU 141

174 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
S tape refresh interval 116
TCP/IP initialization and trace logging 138
S3DA commands for Dataset Attributes Database 129
TCP/IP profile
saving contents of RKLVLOG 165
problem determination 114
saving contents of z/OS logs 165
technical support 161
scheduling
terminology ix
summarization and pruning agent 120
terms, Candle and IBM xi
SDATA options for SLIP console dump 147
timestamped logs 136
SDSF print to database panel, for log output 165
tips
setting trace levels dynamically
problem determination 105
IBM Tivoli Monitoring Services console 142
Tivoli Data Warehouse
setting up trace logging 138
and Dataset Attributes Database 130
short-term data 118
database degraded 123
SLIP command to bypass memory dumps for U0001
gaps in historical data 123
abends 125
log files 112
SLIP console dumps 147
problem determination 119
software support 161
Tivoli Data Warehouse, messages for 136
Software Support
Tivoli Enterprise Monitoring Server
contacting 163
logs 136
describing problems 164
problem determination 113
determining business impact 164
Tivoli Enterprise Monitoring Server on UNIX
receiving weekly updates 162
log files 111
submitting problems 164
Tivoli Enterprise Monitoring Server on Windows
source of problems, determining 134
log files 111
space requirements
Tivoli Enterprise Monitoring Server on z/OS
historical data collection 155
log files 111
space-size values exceeded 91, 115
Tivoli Enterprise Portal
Specify Advanced Configuration Values panel
browser client logs 135
specifying startup console messages 145
desktop client logs 134
specifying storage detail logging 145
ENV file 124
specifying trace logging 145
log files 111
SQL queries 119
Tivoli Enterprise Portal client problems,
starting RKLVLOG spool data set 166
unreproducible 137
startup console messages, enabling 145
Tivoli Enterprise Portal Server
STBDEBUG(X) parameter 147
log files 111
storage allocation detail logging, enabling 116
logs 136
STORAGE command 116
Tivoli Enterprise Portal Server problems 137
storage debugging parameter STBDEBUG(X) 147
Tivoli Monitoring Services console
storage detail logging 116
setting trace levels dynamically 142
storage detail logging, enabling 146
Tivoli Monitoring Services Index for finding
storage for agent
consoles 142
troubleshooting 116
Tivoli OMEGAMON XE for Storage on z/OS
storage for monitoring agent
messages 5
problem determination 116
Tivoli software information center ix
summarization and pruning agent 120
Tivoli technical training x
enabling 120
TLVLOG and flushing log buffers 168
scheduling 120
Trace Analyzer tool, using 154
Summarization and Pruning agent
trace files
logs 136
component prefixes 148
support 161
trace levels, setting 141
support assistant 161
trace logging 138
support information x
communications trace 145
syntax
configuring RKANPARU 141
RAS1 tracing 139
environment variables 138
syntax of messages 3
example, distributed agent issues 141
example, proxy controller issues 141
example, trace logging syntax 141
T example, tracing Tivoli Enterprise Monitoring Server
Take Action commands requests 141
return code 0 113 KDC_DEBUG environment variable 138
unsuccessful 113 KDC_FAMILIES environment variable 138

Index 175
trace logging (continued) troubleshooting (continued)
RAS1 setup 139 space-size values exceeded 115
RAS1 syntax 139 SQL queries 119
RAS1 trace levels 141 startup console messages 145
setting levels dynamically 142 storage detail logging 145
setting up with Configuration Tool 145 tape refresh interval 116
trace logs tips 105
overview 108 Tivoli Enterprise Monitoring Server 113
tracing contrasted with logging 133 connection to wrong hub 113
training, Tivoli technical x Tivoli Enterprise Monitoring Server logs 135
troubleshooting 105 Tivoli Enterprise Portal client problems 137
agent is running out of storage 116 Tivoli Enterprise Portal Server 135
capturing log files for IBM Software Support 165 Tivoli Enterprise Portal Server problems 137
collecting diagnostic data 146 trace logging 138
!Trace in VTAMDATA 146 communications trace 145
KDFDEVIN DEBUG parameter 146 KDC_DEBUG environment variable 138
Preferred dump options 146 RAS1 setup 139
STBDEBUG(X) 146 RAS1 syntax 139
communications trace 145 RAS1 trace levels 141
component prefixes 148 RKANPARU 141
cross-product linking 130 setting dynamically 142
cross-product links missing 130 setup with Configuration Tool 145
data collection 115 V4.1 workspace links to V3.1 workspaces 131
data reports 118 VTS data 115
historical (long-term) data reports 119 warehousing data 119
monitoring data 115 workspace data 115
real-time data 118 workspace links to prior product versions 131
short-term data 118 z/OS system logs 137
data to collect 109 tuning data set I/O collection 123
data warehousing logs 135 typeface conventions x
Dataset Attributes Database 129
dynamic workspace linking 130
error conditions 125 U
example, trace logging syntax 141 U0001 abend 125
format of RAS1 messages 147 U200 Port in use message 114
general issues for OMEGAMON XE 133 UNIX-based systems, messages on 134, 136
historical data unsuccessful Take Action commands 113
summarization and pruning agent 120 user.dmp 110
historical workspaces 113 using the Log and Trace Analyzer tool 154
hubs, multiple 113
identifiers for data rows not exported 118
information sources 105, 109 V
installation and configuration 113 V4.1 workspace links to V3.1 workspaces 131
Integrated Cryptographic Service Facility 113 variables, notation for xi
KDC_DEBUG environment variable 138 viewing log files 3
KFWITM081E link target not found 130 volume identification for the U0001 abend 125
log files 110 VTAMDATA, enabling !Trace 147
monitoring agents VTOC and Dataset Attributes Database 130
remote procedure calls during warehousing 126 VTS data absent 115
overview 105
performance 123
persistent data store 119
process 107
W
warehouse proxy
product features 129
log files 112
RAS1 setup 139
logs 136
RAS1 syntax 139
WAREHOUSEID table 119
RAS1 trace levels 141
WAREHOUSELOG table 136, 137
reproducible problems 134
warehousing
RKANPARU 141
space requirements 155
setup trace logging with Configuration Tool 145
warehousing data 119
sources of problems 134
warehousing of Dataset Attributes Database 130

176 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide
Windows, messages on 134, 136
workspace linking 130
workspace links to prior product versions 131
workspaces
no data, missing data 115
no historical data 113

Z
z/OS log files
capturing 165
z/OS logs
printing contents of 165
saving contents of 165
z/OS system logs 137
z/OS, messages on 137

Index 177
178 IBM Tivoli OMEGAMON XE for Storage on z/OS: Problem Determination Guide



Printed in USA

SC32-1836-01