Messages and Troubleshooting Guide - IBM

5.4

IBM OMEGAMON for Db2 PerformanceExpert on z/OSMessages and Troubleshooting Guide

IBM

GH12-7067

2021-03-23 edition

This edition applies to Version 5 Release 4 of IBM® OMEGAMON for DB2® Performance Expert on z/OS (product number5655-W37) and to all subsequent releases and modifications until otherwise indicated in new editions.© Copyright International Business Machines Corporation 2005, 2021.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.© Rocket Software Inc. 2016, 2021.

Contents

About this information........................................................................................... v

Chapter 1. Overview.............................................................................................. 1Where to find information............................................................................................................................ 1Service updates and support information...................................................................................................2Accessibility features...................................................................................................................................2How to send your comments....................................................................................................................... 3

Chapter 2. Messages..............................................................................................5Introduction to OMEGAMON XE for DB2 PE messages.............................................................................. 5

The layout of message descriptions...................................................................................................... 6The structure of message numbers....................................................................................................... 6When you contact IBM support..............................................................................................................8

BPOK - Buffer Pool Analyzer messages...................................................................................................... 9DGOK - Workstation client messages....................................................................................................... 13DGOP - Performance Warehouse messages.............................................................................................31FPEA - Accounting report set messages................................................................................................... 42FPEB - User-Tailored Reporting messages............................................................................................... 47FPEC - Background Control messages......................................................................................................53FPEE - Exception Processing messages....................................................................................................91FPEF - Interactive Report Facility messages............................................................................................ 95FPEI - I/O Activity report set messages..................................................................................................116FPEJ - Installation and Configuration messages....................................................................................118FPEL - Locking report set messages....................................................................................................... 122FPEM - Online Monitor messages........................................................................................................... 123FPEN - Record Trace messages.............................................................................................................. 187FPEP - Spreadsheet Input Data Generator.............................................................................................187FPEQ - Buffer Pool Analyzer messages...................................................................................................190FPER - SQL Activity report set messages................................................................................................192FPES - Statistics report set messages.................................................................................................... 193FPET - Utility Activity report set messages.............................................................................................195FPEU - Utility Services messages............................................................................................................196FPEV - Data Server messages................................................................................................................. 202FPEW - System Parameters report set messages.................................................................................. 275FPEX - Audit report set messages...........................................................................................................276FPEY - Explain report set messages....................................................................................................... 276FPEZ - Migrate/Convert function messages........................................................................................... 290KDP - Tivoli Enterprise Monitoring Agent (TEMA) for DB2 messages....................................................292KO2A - Anomaly Detection Messages.....................................................................................................307KO2D - D5API Collection for TEP and Enhanced 3270UI...................................................................... 308KO2E - Object Analysis messages...........................................................................................................311KO2H - Near-Term History Data Collector messages.............................................................................317KO2I - D5API Framework messages...................................................................................................... 328KO2M - ISPF messages........................................................................................................................... 346KO2O - VTAM Display Logic messages....................................................................................................347KO2R - Capture Server messages........................................................................................................... 413KO2S - Storage Manager messages........................................................................................................ 425KO2X - Cross-Memory Module messages.............................................................................................. 430KO2Z - OMEGAMON PE Subsystem messages.......................................................................................431

iii

Chapter 3. Troubleshooting and support............................................................. 481Troubleshooting during installation........................................................................................................ 481

Error in RKLVLOG - connection failed................................................................................................ 481Troubleshooting commands....................................................................................................................481

DUMP command.................................................................................................................................481TAPECOPY command.........................................................................................................................483

Creating a diagnostic report.................................................................................................................... 486Responding to dialog boxes.................................................................................................................... 486Troubleshooting for Performance Expert Client..................................................................................... 486Troubleshooting for Performance Warehouse........................................................................................486

Solving code-page problems when accessing Performance Warehouse.........................................487Restarting the OMEGAMON Collector............................................................................................... 487Running a CONVERT step with an incorrect data set........................................................................487

Troubleshooting empty reports...............................................................................................................487

Product legal notices......................................................................................... 491

Index................................................................................................................ 495

iv

About this information

IBM OMEGAMON for Db2 Performance Expert on z/OS (also referred to asOMEGAMON for Db2Performance Expert) is a performance analysis, monitoring, and tuning tool for Db2 on z/OS®

environments.

The document is part of the OMEGAMON for Db2 Performance Expert documentation library whichprovides instructions for installing, configuring, and using OMEGAMON for Db2 Performance Expert and isdesigned to help database administrators, system programmers, application programmers, and systemoperators perform these tasks:

• Plan for the installation of OMEGAMON for Db2 Performance Expert• Install and operate OMEGAMON for Db2 Performance Expert• Customize your OMEGAMON for Db2 Performance Expert environment• Diagnose and recover from OMEGAMON for Db2 Performance Expert problems• Design and write applications for OMEGAMON for Db2 Performance Expert• Use OMEGAMON for Db2 Performance Expert with other DB2 products

Tip: To find the most current version of this information, always use IBM Knowledge Center, which isupdated more frequently than PDF books.

© Copyright IBM Corp. 2005, 2021 v

https://www.ibm.com/support/knowledgecenter/

vi Messages and Troubleshooting Guide

Chapter 1. OverviewOMEGAMON for Db2 Performance Expert is a performance analysis, monitoring, and tuning tool for Db2on z/OS environments that enables you to perform a variety of tasks such as reporting, trend analysis, andbuffer pool analysis.

Where to find informationThe OMEGAMON for Db2 Performance Expert documentation set includes the following documents.Full documentation library (Knowledge Center)

SC27-9821-00The OMEGAMON for Db2 Performance Expert Knowledge Center library includes all OMEGAMON forDb2 Performance Expert content.https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/kdp54_welcome.html

Program DirectoryGI19-5019http://publibfp.dhe.ibm.com/epubs/pdf/i1950190.pdf

Full documentation library (PDF)SC27-9821-00The IBM OMEGAMON for Db2 Performance Expert User's Guide PDF includes all of the OMEGAMONfor Db2 Performance Expert content. It is the PDF version of the Knowledge Center library.https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/kdpuge4.pdf

The OMEGAMON for Db2 Performance Expert documentation is also divided into smaller individualdocuments for ease-of-use. These documents contain a subset of the topics in the full documentationlibrary.

Planning, Customization, and Migration GuideGH12-7072https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2cc540.pdf

Buffer Pool Analyzer User's GuideSH12-7075https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/bpobp540.pdf

Reporting User's GuideSH12-7071https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ru540.pdf

Classic Interface User's GuideSH12-7068https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ci540.pdf

ISPF Client User's GuideSH12-7070https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2mi540.pdf

Enhanced 3270 User Interface User's GuideSH12-7074https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ui540.pdf

Performance Expert Client User's GuideSH12-7069https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2mp540.pdf

© Copyright IBM Corp. 2005, 2021 1

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/kdp54_welcome.html

http://publibfp.dhe.ibm.com/epubs/pdf/i1950190.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/kdpuge4.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2cc540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/bpobp540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ru540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ci540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2mi540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2ui540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2mp540.pdf

Report ReferenceSH12-7065https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2rr540.pdf

Report Command ReferenceSH12-7066https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2rc540.pdf

Parameter ReferenceSH12-7073https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2pr540.pdf

Messages and Troubleshooting GuideGH12-7067https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2me540.pdf

Other documentsThese OMEGAMON for Db2 Performance Expert documents are available for users who need informationabout special topics.

Quick Start Guide - GI19-5019Quick start information for the SQL Dashboard and the end-to-end SQL monitoring functions.http://publibfp.dhe.ibm.com/epubs/pdf/h1270640.pdf

DB2 Performance Expert for MultiplatformsSG24-6867A guide to installing, configuring, and using OMEGAMON for Db2 Performance Expert.http://www.redbooks.ibm.com/redbooks/pdfs/sg246470.pdf

Service updates and support informationYou can access support information for IBM Tivoli®OMEGAMON® for Db2 Performance Expert on z/OS andIBM OMEGAMON for Db2 Performance Monitor on z/OS on the Support home website, or you can use theIBM Support Assistant.

Support home

On the Support home website, you can find service updates and support information including software fixpacks, PTFs, Frequently Asked Questions (FAQs), technical notes, troubleshooting information, anddownloads.

Accessibility featuresAccessibility features help people with a physical disability, such as restricted mobility or limited vision, orwith other special needs, to use software products successfully. This Knowledge Center is developed tocomply with the accessibility requirements of software products according to Section 508 of theRehabilitation Act of the United States.

The accessibility features in this Knowledge Center enable users to do the following tasks:

• Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear whatis displayed on the screen. In this Knowledge Center, all information is provided in HTML format.Consult the product documentation of the assistive technology for details on using assistivetechnologies with HTML-based information.

• Operate specific or equivalent features using only the keyboard.• Magnify what is displayed on the screen.

2 Messages and Troubleshooting Guide

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2rr540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2rc540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2pr540.pdf

https://www.ibm.com/support/knowledgecenter/SSUSPS_5.4.0/kdp54/ko2me540.pdf

http://publibfp.dhe.ibm.com/epubs/pdf/h1270640.pdf

http://www.redbooks.ibm.com/redbooks/pdfs/sg246470.pdf

http://www.ibm.com/software/support

In addition, all images are provided with alternative text so that users with vision impairments canunderstand the contents of the images.

Navigating the interface by using the keyboardStandard shortcut and accelerator keys are used by the product and are documented by the operatingsystem. Refer to the documentation provided by your operating system for more information.

Magnifying what is displayed on the screenYou can enlarge information in the product windows using facilities provided by the operating systems onwhich the product is run. For example, in a Microsoft Windows environment, you can lower the resolutionof the screen to enlarge the font sizes of the text on the screen. Refer to the documentation provided byyour operating system for more information.

How to send your commentsYour feedback is important in helping to provide the most accurate and high-quality information.

If you have any comments about this information or any other documentation, you can complete andsubmit the Reader Comment Form.

Chapter 1. Overview 3

https://www14.software.ibm.com/webapp/iwm/web/signup.do?lang=en_US&source=swg-rcf

Chapter 2. MessagesThis section provides explanations and possible user actions for each OMEGAMON for Db2 PE and PMmessage.

“Introduction to OMEGAMON XE for DB2 PE messages” on page 5“When you contact IBM support” on page 8“BPOK - Buffer Pool Analyzer messages” on page 9“DGOK - Workstation client messages” on page 13“DGOP - Performance Warehouse messages” on page 31“FPEA - Accounting report set messages” on page 42“FPEB - User-Tailored Reporting messages” on page 47“FPEC - Background Control messages” on page 53“FPEE - Exception Processing messages” on page 91“FPEF - Interactive Report Facility messages” on page 95“FPEI - I/O Activity report set messages” on page 116“FPEJ - Installation and Configuration messages” on page 118“FPEL - Locking report set messages” on page 122“FPEM - Online Monitor messages” on page 123“FPEN - Record Trace messages” on page 187“FPEP - Spreadsheet Input Data Generator” on page 187“FPEQ - Buffer Pool Analyzer messages” on page 190“FPER - SQL Activity report set messages” on page 192“FPES - Statistics report set messages” on page 193“FPET - Utility Activity report set messages” on page 195“FPEU - Utility Services messages” on page 196“FPEV - Data Server messages” on page 202“FPEW - System Parameters report set messages” on page 275“FPEX - Audit report set messages” on page 276“FPEY - Explain report set messages” on page 276“FPEZ - Migrate/Convert function messages” on page 290“KDP - Tivoli Enterprise Monitoring Agent (TEMA) for DB2 messages” on page 292“KO2D - D5API Collection for TEP and Enhanced 3270UI” on page 308“KO2E - Object Analysis messages” on page 311“KO2H - Near-Term History Data Collector messages” on page 317“KO2I - D5API Framework messages” on page 328“KO2M - ISPF messages” on page 346“KO2O - VTAM Display Logic messages” on page 347“KO2R - Capture Server messages” on page 413“KO2S - Storage Manager messages” on page 425“KO2X - Cross-Memory Module messages” on page 430“KO2Z - OMEGAMON PE Subsystem messages” on page 431

Introduction to OMEGAMON XE for DB2 PE messagesThis information lists all messages and provides additional explanations and possible user actions foreach message. The messages are listed in alphanumeric sequence. This section introduces the messagelayout and describes the structure of message numbers.


The layout of message descriptionsMessages are described according to the following layout:

Message number and message text, as provided by the systemThe message number is described in “The structure of message numbers” on page 6.

The message text provides a short description of the event or problem. Many actual messages containone or more variable text parts. These parts are shown as numbered message variables in messagetexts (for example, <V1>). The texts for the variables are given in the explanation of the messages.Variable text for workstation client messages is shown as numbered message variables within curlybraces, for example {1}.

ExplanationA more detailed explanation of the message, or additional information about the message.

System ActionA description of how the system responds to the event that caused this message. This part might beintentionally missing, if obvious.

User ResponseA description of possible user actions to solve the problem. This part might be intentionally missing, ifobvious.

The structure of message numbersMessage numbers have fourfold structure that consists of prefix, subcomponent identifier, number, andseverity code.Prefix

A three-character prefix that identifies the product or major component that issues a message.BPO

The Buffer Pool Analyzer program prefix.DGO

Prefix that identifies workstation client messages.FPE

The OMEGAMON XE for DB2 PE program prefix (components from former IBM DB2 PerformanceExpert product).

KDPThe Tivoli Enterprise Monitoring Agent (TEMA) for DB2 program prefix

KO2The OMEGAMON XE for DB2 PE program prefix (components from the former OMEGAMON IIproduct).

Subcomponent identifierA one-character subcomponent identifier that identifies the subcomponent within a product or majorcomponent. For example, in message FPEA1242I, the A identifies the Accounting subcomponent inOMEGAMON XE for DB2 PE.

BPO messages use a single subcomponent identifier K, which means that all Buffer Pool Analyzermessages start with BPOK.

DGO messages use a single subcomponent identifier K, which means that all workstation clientmessages start with DGOK.

FPE messages use the following subcomponent identifiers:A

AccountingB

User-Tailored Reporting (part of Batch feature)


CBackground control

EException processing

FInteractive Report Facility (part of Batch feature)

II/O activity

JInstallation and customization

LLocking

MOnline Monitor

RSQL activity

SStatistics

TUtility activity

UUtility services

VData Server

WSystem Parameters report set

XAudit

YExplain

ZMigrate/Convert function

KDP messages do not have explicit subcomponent identifiers.

KO2 messages use the following subcomponent identifiers:A

Reserved for Application Trace Facility (ATF)C

Reserved for Interface, Cross-Memory, Display ModuleD

Reserved for Data Analysis ModuleE

Object AnalysisH

Near-Term History Data CollectorI

Reserved for D5API FrameworkM

ISPF

Chapter 2. Messages 7

OVTAM® Display Logic

PReserved for D5API Collectors

RCapture Server

SStorage Manager

TReserved

UReserved for Utility I/O and Data Conversion Routines

XCross-Memory Module

ZOMPE Subsystem

Message numberA unique number within the range of messages from a subcomponent.

SeverityAn appending single-letter code that indicates the severity of the message.I

Informational message that does not require any user action.W

Warning message that should be analyzed to determine whether the condition can effect theresults. Usually, a warning message does not prevent the system from execution.

EError message that can be corrected by an appropriate user action (for example, by correcting acommand syntax error).

SSevere error message that results from an abnormal condition and in the abandonment ofprocessing for a command. Other commands in a job stream may still be executed.

UUnrecoverable error message that results from an abnormal condition and in the abandonment ofprocessing for the entire job. Most internal errors fall into this category.

When you contact IBM supportIf you discover an error or receive a message where the user response is "Contact IBM support", collectthe following data before contacting IBM support to assist in determining the cause of the errors:

• The complete list of PTFs and maintenance PUT tapes installed, for DB2 and OMEGAMON XE for DB2PE.

• The complete dump listing from SYSABEND or SYSUDUMP.• All error messages, some of which might contain DB2 return codes and reason codes. To interpret the

DB2 codes, read DB2 Messages and Codes.• The listing of the SYSLOG data set for the period of time spanning the failure.

If the problem originated in the background (Batch) execution of a report, also collect:

• The complete run listing (including all steps), JCL command stream, SYSPRINT log, job summary log,trace record distribution report, and system parameters report, if available.

• The complete report or trace listing in question.


If the problem originated in the Host Online Monitor, the IRF, or the foreground execution of a report, alsocollect the following data:

• The complete list of PTFs and maintenance PUT tapes installed for ISPF, in addition to OMEGAMON XEfor DB2 PE and DB2.

• The listing of the ISPF log for the session involved in the problem.• The panel ID, the message number and text of any error messages, and a description of the sequence of

events immediately preceding the error.

If the problem originated in OMEGAMON Collector, also collect the following data:

• The SYSPRINT log• The History data set• The Exception Events data set• An SVCDUMP of both the OMEGAMON Collector and the user experiencing the problem when the

problem occurred, or as soon after as possible.

With any reported problem, the input data might be needed to perform further problem determination.Save the following data sets:

• The files that were input to the foreground or background execution of OMEGAMON XE for DB2 PEreporting. Save the SMF, GTF, DPMOUT, or Host Online Monitor data sets that were used as input to thereport.

Note: If a report problem was experienced when executing in foreground, it might be easier todocument the problem by executing the same report with the same input data in background to gatherthe necessary information.

• The Exception Threshold data set. If the problem involves exception processing, save the contents ofthis data set from the time of the problem onwards.

BPOK - Buffer Pool Analyzer messagesBPOK5000 The bpd file does not contain all

required information.

ExplanationThe bpd file was generated with an earlier version ofBuffer Pool Analyzer.

User responseUpdate your host version of Buffer Pool Analyzer andgenerate new bpd files.

BPOK5001 The size for one or more objects isunknown.

ExplanationThese objects are treated as if they had size zero.

User responseUse the RUNSTATS tools on a regular basis to initializeobject sizes.

BPOK5002 One or more objects are not placedcorrectly.

Explanation{0}

User responseEdit column 'User-defined' to map the respectiveobjects to valid buffer pools.

BPOK5003 The value supplied for {0} is not avalid decimal number.

ExplanationA valid decimal number consists of digits andoptionally a dot.

User responseType a valid decimal number in the correspondingfield.

BPOK5004 Negative numbers are not allowedfor total sizes.


ExplanationNegative numbers for storage amounts are notallowed.

User responseSpecify storage amounts by using positive numbers.

BPOK5005 The sum of virtual sizes cannot bezero.

ExplanationA system without storage does not work correctly.

User responseSpecify a virtual pool size and, optionally, a hiperpoolsize.

BPOK5006 The program cannot process thedata.

ExplanationContents of column {0} for chart {1} cannot be loaded.

User responseIf the problem persists, contact IBM support.

BPOK5007 The directory {0} does not exist.

ExplanationThe directory was not created or was deleted.

BPOK5008 No data view selected.

ExplanationThere is no data view that has the focus.

User responseSelect a data view or generate one by double-clickingon a suitable leaf in the tree. Then try again theoperation.

BPOK5009 The file that you opened iscorrupted.

ExplanationRecord type is not valid: {0}. Possible values are: 'D','B', 'O', 'S'. Processing stopped.

User responseThe file was generated in a wrong way, was corruptedduring transfer, or was transferred by FTP in a modeother than binary mode.

BPOK5010 The file that you opened iscorrupted.

ExplanationThe record type is not registered: {0}. Record types areregistered by a previous create/load statement pair.Processing stopped.

User responseThe file was probably generated in a wrong way.

BPOK5011 The value supplied for {0} is not avalid integer.

ExplanationIntegers consist of digits only.

User responseEnter a valid integer and try again.

BPOK5012 The value supplied for {0} is out ofrange.

ExplanationThe range is from {1} to {2}.

User responseEnter a number within the range and try again.

BPOK5013 The relation between theminimum and the maximum valueis incorrect.

ExplanationThe maximum value must be greater than theminimum value.

User responseCorrect the numbers accordingly.

BPOK5014 Do you want to save your changedpattern file?

BPOK5015 One or more values of thecharacteristics data are not valid.


Explanation{0}

User responseCorrect the values accordingly.

BPOK5017 All data values in the requesteddata view are zero.

ExplanationEmpty data views are not created.

BPOK5018 Do you want to permanentlydelete the report?

BPOK5023 The system is out of memory.

ExplanationThe size of the available memory is smaller than thesize of the memory required to open the selected inputfile.

User responseClose all applications that are currently not needed.Then try again the operation.

BPOK5024 Sorting by table headers will bedisabled. A very large number ofobjects are displayed and sortingwould be slow.

ExplanationThe amount of data to sort is so great that the sortwould take too long.

BPOK5033 The buffer pool data file is notcompatible.

ExplanationThe selected buffer pool data file cannot be used forObject Placement because it was generated with aversion of Performance Expert or Buffer Pool Analyzerthat is no longer supported.

User responseUse bpd files that were created on a host with asupported version of Performance Expert or BufferPool Analyzer.

BPOK5034 Parsing of buffer pool data filefailed.

ExplanationThe selected file is not a valid buffer pool data file.

User responseSelect buffer pool data files (*.bpd) as input to ObjectPlacement.

BPOK5035 No entry from list of recommendedpatterns is selected.

ExplanationA pattern file is required to map objects to bufferpools.

User responseSelect an entry from the list of recommended patterns.

BPOK5036 No entry from list of user-definedpatterns is selected.

ExplanationA pattern file is required to map objects to bufferpools.

User responseSelect an entry from the list of user-defined patterns.

BPOK5037 No write access to {0}.

ExplanationTo overwrite an existing file, write access is required.

User responseChoose a new name for a file to be created or select afile with write access to be overwritten.

BPOK5038 The bpd files do not contain anydata about DB2 table spaces orindexes that can be used for theDBID/OBID translation.

ExplanationThis can happen, for example, if you collect trace databy using SMF or GTF.

User responseWhen you collect trace data by using SMF or GTF, alsocollect catalog information by using one of the tracecollection methods of Buffer Pool Analyzer. Thengenerate a bpd file from both input data sets.


BPOK5100 Incorrect file transfer mode ASCIIwas used.

ExplanationThe file has been damaged by downloading it in thewrong mode.

User responseDownload the file again specifying BINARY mode.

BPOK5101 Invalid Collect Report Data recordformat used.

ExplanationThe file was created with STANDARD record formatspecified.

User responseCreate a new trace file specifying SHORT recordformat.

BPOK5102 Invalid file type.

ExplanationThe file is a Buffer Pool Analysis bpd file, which cannotbe used for simulation.

User responseSimulation requires a trace file created with the BufferPool Analysis Collect Report Data function in SHORTformat.

BPOK5103 Invalid file type and incorrect filetransfer mode ASCII was used.

ExplanationThe file is a damaged Buffer Pool Analysis bpd file,which has been damaged by downloading it in thewrong mode.

User responseSimulation requires a trace file created with the BufferPool Analysis Collect Report Data function in SHORTformat. It must be downloaded in BINARY mode.

BPOK5104 Invalid file format.

ExplanationThe file is not a valid Buffer Pool Analysis trace file. Itmay have been created using the Performance MonitorCollect Report Data function.


BPOK5199 Unknown file format.

ExplanationThe file is not a known file format.


BPOK5800 Wrong date format.

ExplanationThe date you have typed has the wrong format.

User responseUse this date format: {0} or press the Reset button.

BPOK5801 The start date is later than thebegin date.

ExplanationChange a date or press the Reset button.

BPOK5802 One Date lies out of the recordedtime frame.

ExplanationChange the dates or press the Reset button.

BPOK5803 One of the selected files is not abpd file.

ExplanationRemove this file.

BPOK5804 Parsing Process failed.

ExplanationFile {0} cannot be parsed. It is corrupted or not a bpdfile.

BPOK5805 File exists. New file name hasbeen generated for the result.


ExplanationThe intended file name {0} could not be used for theoutput. The reason for that is that a file with that namealready exists. To ensure uniqueness the name {1} hasbeen generated for the target.

BPOK5806 Invalid buffer pool name(s) {0}entered.

ExplanationThe name(s) {0} are not valid DB2 buffer pool name(s).

User responseChange the buffer pool name(s) in the rule(s) and retrythe last action.

BPOK5807 BPD file used for object placementdoes not match the selected tracefile.

ExplanationObject placement recommendations cannot be used.

User responseSelect a matching trace file.

BPOK5902 The connection to CIMOM failed.

ExplanationCIM stored procedures returns error code: 2

BPOK5903 The connection to the databasefailed.


BPOK5905 The access to CIMOM wasdisabled.


BPOK5906 The monitored DB2 instance is notactive.


BPOK5907 The monitored DB2 instance is notstarted.


BPOK5908 An SQL error occurred.

ExplanationCIM stored procedures failed with error code 8. Theremote instance is not active or cannot be reached.

BPOK6000 Internal buffer pool analysis error.

ExplanationYou tried to open a buffer pool data (bpd) file with oneof the Buffer Pool Analyzer client-based functions, butthe bpd file cannot be opened or properlypreprocessed. The file might be damaged, does notcontain data in the required format (Short orStandard) or data type (Summary or Detail), or wasnot created by means of the BPACTIVITY FILEcommand.

User responseCreate a new bpd file, or use another bpd file. If theproblem persists, contact IBM support.

If this error occurs when you use the File TransferProtocol (FTP), also check whether your file transferprogram provides the RDW and NORDW commandoptions. If the default is RDW, it might cause a four-byte record descriptor record to be included in thedata set being downloaded from the host to the client(which might then cause message BPOK6000). Specifythe NORDW command option to avoid the creation ofthe descriptor record.

BPOK7000 The selected DB2 Connectgateway is currently not active.Switch to history mode and selecta date and time at which the DB2Connect gateway was active.

DGOK - Workstation client messagesDGOK200 Specify the elapsed time in the

format HH:MM:SS.

DGOK201 Specify an elapsed time valuefrom 00:00:00 through 99:59:59.

DGOK202 Specify the number of records tobe collected as an integer between0 and 2147483647.


DGOK203 No free slot to run the trace. Tryagain later.

DGOK204 No slot is configured. Contact yourdatabase administrator.

DGOK206 The selected thread stoppedbefore the trace started.

DGOK207 The selected thread stopped. Thereport was generated.

DGOK208 A timeout occurred during reportgeneration. Re-create the report.

DGOK210 File dgoksqla.xml is corrupted ornot accessible. Contact IBM.

DGOK211 Do you want to delete the trace,job summary, DPMLOG, and tracedata sets on the host?

DGOK221 Specify a value between 00:00:00and 12:00:00 for the elapsed time.

DGOK222 SQL Activity Tracing was stopped.No report was generated.

DGOK223 Specify the flush interval in theformat HH:MM:SS.

DGOK224 Specify a value between 00:00:00and 12:00:00 for the flush interval.

DGOK225 SQL Activity Tracing is notsupported in history mode.

User responseIn Statistics and Thread, select the snapshot dataclosest to the time when the error occurred.

DGOK226 Performance Expert Server did notcreate any output data set.

ExplanationOMEGAMON Collector configuration might not becorrect.

User responseCheck the SYSPRINT output of the OMEGAMONCollector job or the system log of the host whereOMEGAMON Collector is running.

DGOK227 SQL Activity cannot be launchedbecause no database alias isdefined for PerformanceWarehouse.

ExplanationSQL Activity utilizes Collect Report Data, which is nowintegrated and runs under control of PerformanceWarehouse.

User responseUse the Performance Warehouse page of the ModifyProperties window and define a database alias forPerformance Warehouse.

DGOK228 SQL Activity was stopped byPerformance Expert Server.

ExplanationOMEGAMON Collector was restarted.

User responseRestart SQL Activity.

DGOK230 Specify a value greater than zerofor the data set size.

DGOK231 Specify one or more datacategories.

DGOK232 Specify a value between 7 and16385 for the OP buffer size.

DGOK233 Specify a valid stop condition.

DGOK234 Specify a trace command.

DGOK235 Specify a member name of theDSG.

DGOK600 An authority problem occurredwhen the DB2 command wasexecuted.

ExplanationYou have insufficient authority to perform thecommands.

User responseVerify your authorization scheme. If required, contactyour DB2 administrator to extend your authority.

DGOK601 Syntax error.

ExplanationThe syntax of the command is incorrect.


User responseCorrect the error and try again. See the DB2 CommandReference.

DGOK650 DB2 Performance Expert isalready started.

ExplanationOnly one DB2 Performance Expert session can run at atime.

User responseUse the DB2 Performance Expert session that isrunning.

DGOK651 DB2 Performance Expert isalready started.

ExplanationOnly one DB2 Performance Expert session can run at atime.

User responseUse the DB2 Performance Expert session that isrunning.

DGOK700 Statement is not explainable.

DGOK702 Your request cannot be performedbecause you did not specify thelocal database alias.

ExplanationData Studio needs the local database alias of themonitored DB2 subsystem to perform your request.

User responseSpecify the local database alias on the DB2 Subsystempage of the DB2 System Properties window.

DGOK713 Data Studio is not started.

ExplanationThe Data Studio is installed but not started. You needto start Data Studio in order to being able to explainthe SQL Statement.

User responseStart the Data Studio.

DGOK714 Exception encountered duringData Studio or Optim™ QueryWorkload Client usage.

ExplanationAn internal exception occurred.

User responseContact IBM support.

DGOK720 Tuning request complete: JobName {JOB ID} Tuning Jobs URL:{URL}

ExplanationData Server Manager single query tuning requestprocessed successfully.

User responseOpen the link in browser to inspect tuning output forthe given Job Name.

DGOK721 Failed to connect Data ServerManager (DSM)

ExplanationData Server Manager connection service returned anerror message: additional_error_message_text

User responseCheck the error message and the data entered whenconfiguring the subsystem for DSM integration (DSMinformation tab in Db2 System Properties window).

DGOK722 Exception encountered duringData Server Manager processing

ExplanationAn internal Exception occurred.

User responseContact IBM Technical Support (check diagnosticstrace).

DGOK723 Data Server Manager tuningrequest call failed

ExplanationTuning WebService call could not completesuccessfully.


User responseContact IBM Technical Support.

DGOK724 Creation of DSM connection profilefailed

ExplanationThe Data Server Manager Tuning WebService was notable to implicitly create the subsystem connectionprofile.

User responseMake sure the subsystem URL parameter is specifiedcorrectly.

DGOK725 No EXPLAIN provider is availableto explain the query

ExplanationData Server Manager (DSM) and Data Studio are notconfigured/installed on the system.

User responseInstall/configure DSM or Data Studio. If both DSM andData Studio are available, DSM is used to explain thequery.

DGOK750 Could not launch browser withDb2zAI System Assessment linkStatus: {0} Assessment URL: {1}

ExplanationThe browser path in the db2pm.prop file is not validor is incorrect.

User responseVerify that the browser property is set correctly in thedb2pm.prop file. You can view the current status ofthe Db2zAI System Assessment by manually copyingthe provided link into a browser window.

DGOK751 Db2zAI failed to launch Status: {0}Message: {1}

ExplanationIBM Db2® AI for z/OS® System Assessment tool failedto launch.

There might be missing or incorrect parametersspecified on the configuration tab for this Db2subsystem. You might see the message:

Unable to get Db2zAI Connection Name forDB2_IDENTIFIER/SYSTEM_NAME=<DSG-member>/<LPAR-name>

when launching the Db2zAI System Assessment API.Possible reasons for this message might be:

• A non-existent Db2zAI connection for thissubsystem

• The group and member values in the SubsystemConfiguration dialog (Db2 Subsystem tab) are notpresent.

User responseOn the Db2zAI configuration tab, correct theparameters that are listed in the error message andrelaunch the assessment.

If the group and member values in the SubsystemConfiguration dialog (Db2 Subsystem tab) are notpresent, use the Retrieve button to retrieve group andmember values or enter the values manually.

For configured Data Sharing members and groups,Db2zAI requires that the Data Sharing Group name bepassed to the System Assessment API call.

DGOK752 Unexpected connection errorMessage: {0}

Explanation:An unexpected connection error has occurred duringthe launch of the IBM Db2® AI for z/OS® SystemAssessment tool.

User response:Check the IBM Db2® AI for z/OS® server (host) statusand the server properties that are specified on theDb2zAI configuration tab.

DGOK753 Assessment period specification isincorrect Message: {0}

ExplanationAn incorrect assessment period was specified in theRoot Cause Analysis dialog.

User responseSpecify a time range in the format MM/DD/YY,HH:MM:SS AM/PM.

DGOK754 Unexpected JSON parse errorMessage: {0}

ExplanationThe port that was specified in the SA Port field on theDb2zAI configuration tab is not a valid Db2zAI port.


Verify the Db2zAI port that should be used and specifyit in the SA Port field.

User responseSpecify the correct SA Port value on the Db2zAIparameters configuration tab and relaunch theassessment.

DGOK755 Unexpected I/O error Message: {0}

ExplanationAn unexpected API content access exception occurredduring the launch of the IBM Db2® AI for z/OS® SystemAssessment tool.

User responseCheck the IBM Db2® AI for z/OS® server (host) statusand the server properties that are specified on theDb2zAI configuration tab.

DGOK1000 Time interval specification isincorrect.

ExplanationA valid time interval is between 00:00:06 and09:59:59.

User responseSpecify a time interval between 00:00:06 and09:59:59.

DGOK1001 The time interval must have theformat HH:MM:SS.

ExplanationThe time interval must have the format HH:MM:SS.

User responseSpecify a time interval in the format HH:MM:SS, forexample, 00:00:30, 00:01:00, or 01:00:00.

DGOK1002 History snapshots are notavailable.

ExplanationA history snapshot does not exist on the host.

User responseTry again later.

DGOK1003 DB2 Performance Expert Serversupports single sort only.

ExplanationThe version of OMEGAMON Collector installed on thehost does not support multiple sort.

User responseInstall the latest version of OMEGAMON Collector.

DGOK1004 The request timed out. Try againlater.

DGOK1005 The HTML browser cannot beopened.

ExplanationThe browser path specified in the Configurationwindow is not correct.

User responseSpecify a correct path in the Location field on thePreferences page of the Configuration window.

DGOK1006 Restart the application to makeyour accessibility changeeffective.

DGOK1400 The area for the output data is toosmall. The output data istruncated.

DGOK1401 The request resulted in a DB2abend. Restart the DB2 instance.

DGOK1402 The authorization exit in DB2Performance Expert Server isactive. It did not return data.

DGOK1403 A severe error occurred in theauthorization exit. Standardauthorization checks were used.Verify your authorization exitcode.

DGOK1404 The DB2 command failed.

ExplanationThe issued DB2 command was not processedcorrectly. Possible reasons are authorization failure,processor abend, syntax error, or exceeded outputlimit.

User responseCheck the syntax and ensure that you have thenecessary authority to perform this command.


DGOK1405 A dynamic statement cache erroroccurred.

ExplanationYou have qualified a statement that was not found inthe statement cache.

DGOK1406 No data returned.

ExplanationFor IFCID 316, data was not returned because thestatements did not match the qualification criteria, orbecause the cache was empty.

DGOK1407 Data sharing group only: at leastone DB2 member did not respond.

ExplanationThe specified member is not a member of the group, orthe member is currently not running.

User responseEnsure that all members of the group are running.

DGOK1408 No buffer pool informationavailable.

ExplanationThe request contained IFCID 254, but a group bufferpool is not connected. The member or subsystem didnot return data.

User responseConfigure the group buffer pool and try again.

DGOK1409 The authorization verificationfailed.

ExplanationPossible reasons are:

• Your user ID or password is not correct.• The performance database of the PE Server subtask

does not exist.• Your user ID does not have monitor 1 or monitor 2

authority.• You are not authorized to use the KO2PLAN plan.

User responseVerify and correct the possible reasons. Note that userID and password are case-sensitive.

DGOK1410 DB2 BIND is missing. DB2Performance Expert Server needsa BIND against DB2.

ExplanationOMEGAMON Collector was changed or updatedwithout the necessary bind against DB2.

User responseIssue the BIND command, then restart OMEGAMONCollector.

DGOK1411 DB2 error.

ExplanationThe DB2 request failed, data is not returned.

User responseSee the console log for detailed information.

DGOK1412 The maximum number of 500users is reached or exceeded.


DGOK1413 The returned data is too large. Therequest was canceled.

DGOK1414 The request was rejected.

ExplanationHistory data has not yet been collected.

User responseEnsure that the collection of history data is enabledand configured correctly.

DGOK1415 The request was rejected.

ExplanationThe history data you requested no longer exists.

User responseSelect a more recent history snapshot.

DGOK1416 DB2 Performance Expert Serverauthorization exit error.

ExplanationThe authorization exit did not finish correctly.


User responseCheck your authorization exit code, then try again.

DGOK1417 This function must be licensed.

ExplanationThis feature is only available if you have a full license.

User responsePurchase a full license to use this feature.

DGOK1418 The DB2 subsystem is not startedor cannot communicate.

ExplanationOMEGAMON Collector is running, but the monitoredDB2 system is not responding.

User responseStart the DB2 system and ensure that it is responding.

DGOK1419 Logon failed due to CAF connecterror.

ExplanationYour logon request was not processed because theconnection to Call Attach Facility (CAF) failed.

User responseVerify your DB2 authorization and check the systemlog for more information.

DGOK1420 Logon failed due to CAF openerror.

ExplanationYour logon request was not be processed because theCall Attach Facility (CAF) reported an open error.

User responseVerify your DB2 authorization and check the systemlog for more information.

DGOK1421 The maximum number of TCP/IPsessions is exceeded.

ExplanationThe maximum number of TCP/IP sessions specified inOMEGAMON Collector startup parameter wasexceeded.

User responseClose one or more sessions or increase the startupparameter value.

DGOK1422 DB2 is out of memory.

ExplanationThe memory or subsystem did not return data.

User responseRestart the DB2 system and ensure that enoughmemory is available.

DGOK1423 Monitor trace class 1 is not active.

ExplanationThe member or subsystem did not return data.

User responseEnable the Monitor trace class 1 in the startupparameter, then try again.

DGOK1424 You are not authorized to receivemonitor trace class 2 information.

User responseAsk your administrator for the necessary privileges.

DGOK1425 The CAF connect failed. Therequest was rejected.

ExplanationOMEGAMON Collector cannot verify your authorizationbecause the connection to the Call Attach Facility(CAF) failed.

User responseCheck the z/OS system log for more information.

DGOK1426 The CAF open failed. The requestwas rejected.

ExplanationOMEGAMON Collector cannot verify your authorizationbecause a Call Attach Facility (CAF) session cannot beopened.

User responseCheck the system log for more information.


DGOK1427 CRDSTCM does not contain therequired DEST(OPX) section.

ExplanationThe START TRACE command sent to OMEGAMONCollector did not contain a DEST(OPX) section, which isnecessary to perform this operation.

User responseAdd this section to your command or have itgenerated.

DGOK1428 Incorrect DSORG. See log.

ExplanationThe data set disposition mode is incorrect. Forexample, 'Append' was specified for a data set thatdoes not exist.

User responseUse the correct mode when writing to a data set. Themode depends on whether a data set exists.

DGOK1429 Incorrect RECFM. See log.

DGOK1430 Incorrect LRECL. See log.

DGOK1431 SMS dynamic allocation error. Seelog.

ExplanationAn SMS data set cannot be opened to receive data.

User responseSee the console log for details.

DGOK1432 The data set is not cataloged. Seelog.Catalog the data set, then tryagain.

DGOK1433 The data set already exists. Seelog.Try another disposition modesuch as 'Append' or 'Overwrite'.

DGOK1434 A catalog error occurred. See log.

DGOK1435 A dynamic allocation erroroccurred. See log.

DGOK1436 An open error occurred. See log.

DGOK1437 Buffer shortage.

ExplanationOMEGAMON Collector has reached the maximumnumber of API function calls that can be handledsimultaneously.


DGOK1438 Internal DB2 Performance ExpertServer error.

ExplanationThe storage allocation for buffers failed.

DGOK1439 The history request was denied.

ExplanationThe snapshot did not exist in history or wasoverwritten.

User responseSpecify a different time frame.

DGOK1440 No more information is available.

ExplanationOMEGAMON Collector has been restarted. The data forthis application is lost and cannot be recovered.

User responseLog off from this subsystem, then log on again.

DGOK1441 Not logged on to DB2 PerformanceExpert Server

ExplanationThe client application has called an API functionwithout being logged on to OMEGAMON Collector.

DGOK1442 Snapshot data was not receivedfrom the host.

ExplanationOMEGAMON Collector did not return any data.

User responseCheck that OMEGAMON Collector is started.

DGOK1443 The instance is not connected to aDB2 Performance Expert Server.The connection failed.


ExplanationOMEGAMON Collector did not return any data.

User responseCheck that OMEGAMON Collector is started.

DGOK1444 DB2 is out of memory.

ExplanationDuring a DB2 IFI request, DB2 reported a failureobtaining memory.

User responseIf you are monitoring a DB2 V7, ensure that APARPQ58341, PTF UQ66442 is applied. If you areconnected to a Data Server of DB2 PM V7, ensure thatAPAR PQ60353, PTF UQ65800 is applied. If theproblem persists, contact IBM support.

DGOK1445 The DB2 connection was lost.

ExplanationOMEGAMON Collector lost its connection to DB2.Possible reason: The thread was canceled or hasstopped.

User responseLog off, then log on again. If the problem persists,contact IBM support.

DGOK1446 Server timeout.

ExplanationServer did not respond in the expected time.


DGOK1447 DB2 returned incorrect READSdata, the request was canceled.

User responseContact DB2 support.

DGOK1448 DB2 Performance Expert Server iscurrently not available, or thewrong port number was specified.

ExplanationThis error can occur when you configured a new DB2and entered a wrong port number in the "RetrieveDB2PM Databases" step.

User responseVerify the port number of your OMEGAMON Collector,and correct it if necessary. Otherwise, restartOMEGAMON Collector.

DGOK1450 Internal DB2 Performance ExpertServer error. DB2 PerformanceExpert Server ran out of memory.

ExplanationThe OMEGAMON Collector could not obtain memory.

User responseThis can be a temporary problem. Retry the operation.If the problem persists, ask the MVS™ operator toenlarge the region size of the Data Server and restartthe Data Server. If the problem still persists, contactIBM support.

DGOK1451 DB2 Performance Expert Server isnot correctly configured or is notstarted.

DGOK1452 The system name cannot beresolved.(UnknownHostException)

ExplanationThe current system is not available or is wrong.

User responseCorrect the system name for the current DB2 system,then try again.

DGOK1453 No data retrieved by the server.

ExplanationThe Data Server has stopped or was not started.Snapshot related stored procedure does not work.

User responseRestart the Data Server. If the problem persists, stopthe Data Server and DB2, then restart DB2 and theData Server. Wait about one minute before repeatingthe request from the client.


DGOK1454 To perform this function a JDBCdriver is needed.

ExplanationThe JDBC DB2 driver cannot be found in the Java™

classpath. This problem can occur if DB2 PerformanceExpert was installed before DB2, or if DB2 wasreinstalled into a new directory after PerformanceExpert was installed.

DGOK1455 You are not authorized to accessthe DB2 PM database tables.

User responseAsk your administrator to add your user ID to the DB2group authorized to work with the Data Server. Checkthatthe Data Server is correctly configured or isstarted.

DGOK1456 DB2 or DB2 Performance ExpertServer is not started, themonitored instance is not enabled,or DB2 is not started locally.

Explanation• The DB2 instance (local or on a server) is not started.• The Data Server (on which your DB2PM database is

located) is not started.• A monitored instance was disabled.• The network connection might be lost.

User responseStart the correct service, or enable the instance to bemonitored in the Data Server configuration.

DGOK1457 User ID not valid.

ExplanationLogon failed because the specified user ID is not valid.

User responseCorrect the user ID.

DGOK1458 Wrong password.

ExplanationLogon failed because the specified password is wrong.

User responseCorrect the password.

DGOK1459 Password expired.

ExplanationLogon failed because the specified password expired.

User responseSpecify a new password on the host.

DGOK1460 New password not valid.

ExplanationLogon failed because the new password is not valid.

User responseCorrect your password on the host.

DGOK1461 User ID not in group.

ExplanationLogon failed because the specified user ID is notdefined to the specified group.

User responseSpecify another group ID or ask your administrator toadd you to the specified group ID.

DGOK1462 Password revoked.

ExplanationLogon failed because the specified password has beenrevoked.

User responseAsk your administrator to reset your password. Thenlog on to the host and specify a new password.

DGOK1463 User ID revoked from group.

ExplanationLogon failed because access to the specified group hasbeen revoked.

User responseAsk your administrator to give you access to thespecified group again.

DGOK1464 The DB2 subsystem is notavailable, or the connection wasterminated when you canceled a


thread using the Cancel Threadcommand.

User responseLog off from this DB2 subsystem and then log on again.

DGOK1465 Error when cataloging thedatabase.

ExplanationA user might have attempted to execute a commandwithout having the proper authority, or the specifiedDB2 connection alias is not correct.

DGOK1466 The communication with themonitored remote instance failed.The remote instance might bedown or unreachable.

DGOK1467 The maximum number ofconcurrent databases havealready been started.

User responseTo start more databases, increase the value of the DB2parameter NUMDB (maximum number of concurrentlyactive databases).

DGOK1468 Saving the threshold set failedbecause of SQL error: {0}

DGOK1469 The stored procedures were notregistered correctly or are notaccessible.

User responseReconfigure the server.

DGOK1470 The maximum number of clientconnections that can be startedhas already been reached.

DGOK1471 The monitored instance is notenabled.

ExplanationThe performance database for the monitored instancewas not found at the Data Server.

User responseEnable the monitored instance with PE Config and tryagain.

DGOK2100 Thread Details cannot be opened.

ExplanationThread Details cannot be opened because the tabledata is incorrect.

User responseTry again. If the problem persists, contact IBMsupport.

DGOK2101 Thread stopped.

ExplanationThe selected thread stopped or was terminated.

DGOK2501 There is no help available.

DGOK3300 {0} Details cannot be opened.

Explanation{0} Details cannot be opened because the table data isincorrect.

User responseTry again. If the problem persists, contact IBMsupport.

DGOK3301 {0} cannot be canceled.

ExplanationThe table data is incorrect.

User responseClose the application and try again. If the problempersists, contact IBM support.

DGOK3302 DB2 Performance Expert Serverinformation is not available.

ExplanationThe Data Server information cannot be received.

User responseClose the application, then try again. If the problempersists, contact IBM support.

DGOK3303 The selected {0} stopped or wasterminated.

DGOK3304 DB2 Performance Expert Serversupports single qualifiers only.


ExplanationThe version of the Data Server that is installed on thehost does not support more than one qualifier.

User responseInstall the latest Data Server.

DGOK3305 This filter already exists.

DGOK3306 Check at least one item in ThreadType.

DGOK3308 DB2 Performance Expert Serverdoes not support SQL activitytracing.

User responseInstall the latest Data Server.

DGOK3309 SQL activity tracing cannot bestarted in GLOBAL view.

ExplanationIn GLOBAL view, the list of applications and theirperformance counter values are aggregated for alldatabase partitions. However, an SQL activity trace canonly be created for a single partition.

User responseSelect a single partition or the entire instance (GROUP)from the "Show Data for" list and then start SQLactivity tracing for an application.

DGOK3500 Data Sharing Group information isnot available.

ExplanationThe subsystem is not a member of a data sharinggroup.

DGOK3501 History data for the specified dateand time is not available.

ExplanationData for the date and time specified was probablyoverwritten by more recent data.

User responseWait until the new timestamp list is loaded to see theoldest snapshot.

DGOK3502 History data is not available.

ExplanationThe request was rejected. History data is not available.

User responseTry again later or restart the Data Server by using thehistory option.

DGOK3503 Data is not available.

ExplanationThe request cannot be processed because data is notavailable. Possible reasons:

• Snapshot did not exist or was overwritten.• History data does not exist.• The thread was stopped or terminated.• The filter has no data.

User responseRespecify the filters and qualification criteria, orspecify a different snapshot.

DGOK3504 Function is not supported in demomode.

User responseDisable the demo mode, log on to a subsystem, and tryagain.

DGOK3505 Details window is not visible inGroup View.

ExplanationThe selected data is not visible in Group View mode.

User responseSelect a member and try again, or close the DetailsWindow.

DGOK3506 The group scope request mighttake longer because the server hasmore than 10 members. Shouldyour request be performed?

DGOK3507 Global or group view is not valid inthis context.

DGOK3600 The specified file name is notvalid.

User responseThe file is empty or read-only.


DGOK3601 Logon is not possible, the selectedDB2 Performance Expert Server{0} is not running.

DGOK3602 The specified subsystem is notconfigured.

User responseAdd this subsystem to the System Overview window,then try again.

DGOK3603 The specified configuration file isnot valid.

User responseThe file does not exist, is empty, cannot be read, or isnot a correct configuration file.

DGOK3604 A DB2 system with the same nameis already defined.

User responseIf this is the system that you are currently configuring,no further action is required. Otherwise, edit thesystem or instance name and provide a unique name.

DGOK3605 Type numbers in this field.

DGOK3606 You cannot log on to the selectedDB2 system ({0}) because there iscurrently no information availableabout its status.

User responseWait until the Server Status column in the DB2 systemstatus table shows an up arrow next to the selectedDB2 subsystem. Then try to log on again.

DGOK3607 The multiplier must be greaterthan zero.

ExplanationA multiplier has been set to zero or one of the historytypes does not exist in the DB2PM.HISTORYDATAtable.

User responseSet another multiplier value.

DGOK3608 The DB2 Connection alias ({0}) isnot correct.

ExplanationThe DB2 Connection alias name was not specified, islonger than eight characters, or contains a characterthat is not valid.

User responseSpecify a valid DB2 Connection alias.

DGOK3609 The snapshot trace or historyparameter cannot be set.

ExplanationThe parameter does not exist in theDB2PM.PARAMETER table.

DGOK3610 The selected DB2PM database isnot receiving DB2 Connect/gateway information.

ExplanationA DB2PM database can only receive data about a DB2Connect gateway if Performance Expert Agent for DB2Connect Monitoring (PE Agent) is installed, configured,and activated at DB2 Connect/gateway. For moredetails, see Installation and Configuration.

User responseSelect a DB2PM database receiving DB2 Connect/gateway information or, if you want to use the selectedDB2PM database, install, configure, and activatePerformance Expert Agent for DB2 Connect Monitoring(PE Agent) at the appropriate DB2 Connect/gateway.

DGOK3611 This function is not available onmulti-partition instances.

DGOK3612 The Performance WarehouseServer is currently not available.

User responseStart the Performance Warehouse server using thePerformance Warehouse page of the Modify Propertieswindow.

DGOK3613 Your password or group is toolong. Specify a password up to 100characters or a group of up to eightcharacters.

DGOK3614 The DB2 system you want to addalready exists in this folder.

DGOK3615 A folder with this name alreadyexists. Specify a different name.


DGOK3616 A copy of this DB2 system alreadyexists in this folder.

DGOK3617 To import a DB2 system, you mustbe logged off from all DB2 systemsthat are defined to DB2Performance Expert Client.

User responseLog off from the DB2 systems to which you are loggedon, then try again.

DGOK3618 To perform this function, you mustfirst log on to a DB2 system.

DGOK3620 No DB2PM database is selected orall DB2 instances are defined toDB2 Performance Expert Client.

DGOK3621 One or more database aliasesalready exist in the DB2 Catalog (ie{0}).

DGOK3622 The specified DB2 PerformanceExpert Server does not monitorany DB2 instances.

User responseTo enable the Data Server to monitor a DB2 instance,you must first configure this instance. For informationabout how to configure an instance, see Installationand Configuration.

DGOK3623 The trace is activated but the tracelevel is 0.

ExplanationTrace data can only be collected with a trace levelgreater 0.

User responseSpecify a trace level from 1 to 5 when you activate atrace.

DGOK3629 You cannot specify any historydata storage settings because thisparameter does not exist in theDB2PM.PARAMETER orDB2PM.PWHDATA table.

DGOK3630 You specified one or more wrongvalues for the history data storagesettings.

User responseFor the storage interval, specify a number from 1through 24. For the interval for summarizing thehistory data, specify a number from 1 through 96.

For the start date for history storage, specify a validdate in the form mm.dd.yyyy.

DGOK3631 For the {0} field, specify a valuegreater than zero.

DGOK3632 You specified a wrong value forthe history data storage settings.

User responseFor the interval for summarizing the history data,specify a number from 1 through 96.

The interval must be equal to, or greater than, therecording interval you specified on the History page.

DGOK3634 Specify {0}.

DGOK3635 Verify that the e-mail is received inthe destination In-Box. If not,verify the specified e-mail (SMTP)server address.

DGOK3636 The database alias ({0}) is notsupported by DB2.

ExplanationYou cannot specify the host name of your workstationas database alias. This is a DB2 restriction.

User responseSpecify another database alias.

DGOK3637 The shortcut ({0}) references aDB2 system that is alreadydeleted. Therefore, this shortcutwill be deleted.

DGOK3638 Some monitor switches are not seton "{0}". Therefore, part of theinformation is not available.

ExplanationOne or more of the following monitor switches are notset: {1}

• BUFFERPOOL (DFT_MON_BUFPOOL): Number ofreads and writes, time taken.

• LOCK (DFT_MON_LOCK): Lock wait times,deadlocks.

• SORT (DFT_MON_SORT): Number of heaps used,sort performance.


• STATEMENT (DFT_MON_STMT): Start and stop time,statement identification.

• TABLE (DFT_MON_TABLE): Measure of activity(rows read and written).

• UWO (DFT_MON_UOW): Start and end times,completion status.

• TIMESTAMP (DFT_MON_TIMESTAMP): Timestamps.

User responseSet the monitor switches for which you want to seedata.

DGOK3639 The library for catalogingdatabases could not be loadedsuccessfully. Some multiplatformtasks such as defining a DB2instance are disabled.

User responseThis message also pops up if the client is started in a64-bit instance, but with a 32-bit JRE. Then, youcannot even log on to a monitored system. Install a64-bit enabled JRE and restart the client.

DGOK3640 The server task is not valid; alogoff has been performed.

ExplanationThe client received a return code 8 with reason codeX'64' from the data collector task. The data collectorreturns this error if the user's started task is in aninvalid and unrecoverable state. The most commonreason is that the data collector ran out of memory.The client cannot recover from this situation becauseall subsequent requests against the server lead to thesame error.

Logging off and on usually frees some resources andallows the user to continue for a while. However, overtime, the error recurs.

User responseStop and restart the data collector.

DGOK3641 A recording interval of less than 30seconds can cause performanceproblems at Performance ExpertServer. In addition, it can happenthat Performance Expert Serverdoes not collect each snapshot. Itis recommended that you specify arecording interval of at least 30seconds. Do you want to leave the

recording interval at less than 30and continue?

DGOK3642 User Exit Program/Script missing

User responseSpecify the path to the User Exit Program/Script.

DGOK3643 The PE Server subtask tries to callyour User Exit Program/Script

User responseVerify that your User Exit Program/Script is called.

DGOK3644 DB2 Visual Explain V8 does notsupport DB2 9.

DGOK3663 Cannot use an active PerformanceWarehouse connection to scheduleSQL Activity trace processing.

ExplanationUnder certain circumstances, the Performance ExpertClient can do an implicit connect to the PerformanceWarehouse however this is not always possible.

User responseBefore you start an SQL activity trace, log in to thePerformance Warehouse for the Db2 subsystem.

DGOK4000 Wrong values for WARNING orPROBLEM thresholds.

ExplanationThe values for WARNING and PROBLEM thresholds arenot valid. Possible reasons:

• The WARNING value is greater than or equal to thePROBLEM value.

• The WARNING or PROBLEM values are not specified.• The PROBLEM value is less than or equal to the

WARNING value.

User responseSpecify valid threshold values.

DGOK4001 The name for the current thresholdis missing.

DGOK4002 The author for current threshold ismissing.

DGOK4003 The threshold cannot be copied.


ExplanationA threshold with the same specification already exists.

User responseFor an exception field, only two thresholdconfigurations with identical filter criteria are allowed.The criteria can be active and inactive.

DGOK4004 The status cannot be changed.

ExplanationThe status cannot be changed to the active state of thecurrent threshold.

User responseThe status cannot be changed to active becauseanother active threshold already exists. For anexception field, only one active threshold configurationis allowed.

DGOK4005 The XML file is corrupted.

ExplanationThe menu item cannot be found because the XML fileis corrupted.

User responseFile gui_exceptionmain.xml is corrupted or notaccessible. Reinstall the program or contact your IBMrepresentative.

DGOK4006 The XML file is corrupted.

ExplanationThe toolbar item cannot be found because the XML fileis corrupted.

User responseFile gui_exceptionmain.xml is corrupted or notaccessible. Reinstall the program or contact your IBMrepresentative.

DGOK4007 Exception Event was startedsuccessfully.

DGOK4008 Exception Event was stoppedsuccessfully.

DGOK4009 To start exception processing, youmust first log on to a DB2 system.

DGOK4010 This Thread does not existanymore.

DGOK4011 The connection to this subsystemis missing.

ExplanationYou must be logged on to the subsystem to receive theevent details information.

User responseLog on to the subsystem.

DGOK4012 No Threshold set selected.

ExplanationPeriodic Exception Processing requires a Thresholdset.

User responseSelect a Threshold set with the Threshold set combobox. Create one, if no one exists.

DGOK4013 Exception Event(s) occurred.

DGOK4014 Periodic Exception(s) start(s).

DGOK4015 Periodic Exception(s) stop(s).

DGOK4016 Periodic Exception(s) refreshed.

DGOK4017 Periodic Exceptions refreshed andstopped.

DGOK4018 The selected Threshold set isempty.

ExplanationFor starting Periodic Exception Processing, a Thresholdset with at least one active Threshold is necessary.

User responseAdd an active Threshold to the Threshold set.

DGOK4019 To start periodic exceptionprocessing on db2_system, selecta threshold set that contains atleast one active threshold that issupported by Performance ExpertServer.

DGOK4020 To view more information on thisexception, you must be logged onto the DB2 system that producedthe exception.

DGOK4021 No exception field selected


ExplanationNo exception field selected.

User responseSelect an exception field.

DGOK4022 Interval is missing.

DGOK4023 {0} is missing.

DGOK4024 E-mail address is not valid.

DGOK4025 Contact with name {0} alreadyexists. Overwrite it?

DGOK4026 Do you want to delete the selectedcontact?

DGOK4027 No contact selected.

DGOK4028 The value in the {0} field is notvalid.

ExplanationThe value in the {0} field is not valid, whereby {0} is thelabel of a numeric entry field.

User responseSpecify a number from {1} through {2}, whereby {1} isthe minimal and {2} is the maximum value.

DGOK4029 The name for the sound file ismissing or is not correct.

ExplanationThe name for the sound file is missing or is not correct.

User responseSpecify an existing sound file.

DGOK4030 Your e-mail specifications are notcorrect or are not complete.

ExplanationYour e-mail specifications are not correct or are notcomplete.

User responseTo send exception notifications by e-mail, do thefollowing:

1. Specify your e-mail address.2. Select the destination e-mail address.

3. If the e-mail (SMTP) server requires authentication,select the appropriate check box and specify yourserver user ID and your password.

DGOK4032 For periodic exception processingon db2_system, the thresholds forthe following exception fields aredisregarded: exception_field_list

ExplanationThe thresholds for the listed exception fields aredefined in the selected threshold set but are not activeor are not supported by the PE Server subtask.

DGOK4033 Exception event processing cannotbe started for '{0}'.

ExplanationException event processing is disabled on the DataServer.

User responseEnable exception event processing on the Exceptionpage of the Data Server Properties window for '{0}'.

DGOK4034 Exception event processing cannotbe started for '{0}'.

ExplanationEvent monitoring is disabled for all monitoreddatabases.

User responseEnable event monitoring for at least one monitoreddatabase by configuring the Data Server.

DGOK4035 Periodic exception processingcannot be started for '{0}'.

ExplanationPeriodic exception processing is disabled on the DataServer.

User responseEnable periodic exception processing on the Exceptionpage of the Data Server Properties window for '{0}'.

DGOK4036 The threshold set containsthresholds for operating systemcounters. These thresholdsbecome active only if the CIMserver was enabled during theconfiguration of Performance


Expert Server and the collection ofhistory data is enabled (on theHistory page of the PerformanceExpert Server Properties window).

DGOK4037 Exception event processing hasbeen deactivated for ''{0}''because it was disabled onPerformance Expert Server.

DGOK4038 Periodic exception processing hasbeen deactivated for ''{0}''because it was disabled onPerformance Expert Server.

DGOK4039 Detailed information for thisexception event is no longeravailable.

ExplanationDetailed information about exception events is storedin a log on the Data Server. If the number of exceptionevents in this log exceeds {0}, the oldest exceptionevent entries are removed from the log. The exceptionevent for which you requested detailed information isamong those that are already removed from the log.

DGOK4101 The recording of diagnosticinformation stopped.Do you wantto send the recorded information?

DGOK4102 The recording of diagnosticinformation stopped.Do you wantto save the recorded information?

DGOK4103 The diagnostic information isrecorded.Do you want to stop therecording and send the diagnosticinformation?

DGOK4104 The diagnostic information isrecorded.Do you want to stop therecording and save the diagnosticinformation?

DGOK4105 The diagnostic information wasrecorded.Do you want to send it?

DGOK4106 The diagnostic information wasrecorded.Do you want to save it?

DGOK4107 The diagnostic information wasnot sent.Do you want to delete it?

DGOK4108 The diagnostic information wasnot saved.Do you want to deleteit?

DGOK4109 The selected file already exists.Doyou want to overwrite it?

DGOK4110 The diagnostic information cannotbe sent.Do you want to save it?

DGOK4111 The diagnostic information cannotbe sent.Do you want to save itagain?

DGOK4112 The recording of the diagnosticinformation cannot be started.

DGOK4113 The recording of the diagnosticinformation cannot be stopped.

DGOK5026 Incorrect timestamp value {0}.

ExplanationEntry does not correspond to format mask {1}.

User responseCorrect the value.

DGOK5027 Partition field entry {0} not valid.

ExplanationThe entry for partition filtering is not a valid regularexpression.

User responseEnter an asterisk or a correct regular expression, forexample: {1}

DGOK5028 Start and end times do not match.

ExplanationThe end time {0} must be later than start time {1}.

User responseCorrect the start time or the end time.

DGOK5029 The provided template isunusable.

ExplanationThe template does not belong to the set of validtemplates.

User responseUse a valid template.

DGOK5031 No performance data exist for anydatabase of the monitoredinstance.


ExplanationNo database is configured for monitoring, or themonitored instance has not been set up to storehistory data in the Performance Warehouse, or themonitored instance has been set up to store historydata but the end of the first storage interval has notbeen reached.

User responseEnsure that you have added databases for monitoringto your monitored instance during configuration of theData Server (peconfig). Further, from PerformanceExpert Client, check the properties of the monitoredinstance whether the storage of history data isenabled. Finally, determine whether sufficient timehas elapsed to allow for the completion of at least onestorage interval. If required, allow for some extra timeand try again later.

DGOK5032 File name not correct.

ExplanationThe provided file name {0} is not valid in youroperating system.

User responseRepeat the Save operation and provide a valid filename.

DGOK5033 The buffer pool data file is notcompatible.

ExplanationThe selected buffer pool data file cannot be used forObject Placement because it was generated with aversion of Performance Expert or Buffer Pool Analyzerthat is no longer supported.

User responseUse bpd files that were created on a host with asupported version of Performance Expert or BufferPool Analyzer.

DGOK5034 Parsing of buffer pool data filefailed.

ExplanationThe selected file is not a valid buffer pool data file.

User responseSelect buffer pool data files (*.bpd) as input to ObjectPlacement.

DGOK5902 CIMOM connection failed.


DGOK5903 Database connection failed.


DGOK5905 CIMOM access disabled.


DGOK5906 Monitored DB2 instance not active.


DGOK5907 Monitored DB2 instance notstarted.


DGOK5908 SQL Error occurred.

ExplanationCIM stored procedures failed with error code 8. Theremote instance might be down or unreachable.

DGOP - Performance Warehouse messagesDGOP1 Insufficient information to

establish a database connection toPerformance Warehouse.

ExplanationOne or more of the following data is missing:

• Database user ID• Password• Database alias• JDBC driver name


User responseBefore you can connect to Performance Warehouse,you must specify a database user ID, password,database alias, and JDBC driver.

DGOP2 Delete the selected object fromPerformance Warehouse?

DGOP3 Exit the application?

DGOP7 There is currently no helpavailable.

DGOP8 Specify a database alias for theDB2PM database.

DGOP9 The database schema DB2PM notfound.

ExplanationA database was connected that does not contain thedatabase schema DB2PM.

User responseCheck the database alias configuration onPerformance Expert Client and the Data Server.

DGOP10 The Performance Warehousetables are not found.


1. Database schema DB2PM does not contain thePerformance Warehouse tables.

2. A SCHEMALIST parameter is used to limit dataretrieval.

3. The specified database alias refers to aperformance database of Performance ExpertVersion 3.1 or later.

User response1. Check the database alias on Performance Expert

Client and Performance Expert Server.2. Check the file db2cli.ini for any SCHEMALIST

parameter specifications to limit the list of schemasthat are used for data retrieval.

3. Beginning with Performance Expert Version 3.1,you can no longer add a Performance Warehousesystem manually. Add the Performance ExpertServer on which the Performance Warehouseresides to your Performance Expert Client and openPerformance Warehouse from the System Overviewwindow.

DGOP11 Performance Expert Client andPerformance Expert Server are notcompatible.

ExplanationThe following list of properties helps to determine theClient and Server versions: {0}

User responseInstall the compatible versions of Performance ExpertClient and Performance Expert Server.

DGOP12 Performance Warehouse onlysupports partitioned databasesystems with one partition.

ExplanationPerformance Warehouse tried to connect to apartitioned database system with multiple databasepartitions.

DGOP13 The partition number of the single-partition database must be 0.

ExplanationPerformance Warehouse only supports partitioneddatabase systems with one partition. This partitionmust have partition number 0.

DGOP14 Performance Warehouse cannotcheck whether it is compatiblewith Performance Expert Server.

ExplanationTo check whether Performance Warehouse iscompatible with the Data Server installed, specificversion information is required. N/P is shown for theinformation that is missing:{0}

User responseCheck whether the Data Server is installed correctly.Install the compatible versions of Performance ExpertClient and the Data Server.

DGOP15 Performance Warehouse could notbe connected automatically.

ExplanationNo database alias is defined for PerformanceWarehouse.


User responseUse the Performance Warehouse page of the ModifyProperties window to define a database alias forPerformance Warehouse.

DGOP16 The specified database aliasbelongs to a DB2PM database on{0}.

ExplanationNone.

User responseDelete the created node. Then open the NewPerformance Warehouse window and create aPerformance Warehouse on {0} using the specifieddatabase alias.

DGOP17 Performance Warehouse is notavailable.


• The PE Server subtask installation is still in progressor incomplete.

• The database alias that you specified in the NewPerformance Warehouse window does not referencea Performance Warehouse.

• The specified database alias refers to a performancedatabase of a Performance Expert version 3.1 orlater.

User response1. Check the status of the PE Server subtask

installation.2. If the installation completed successfully, use the

Client Configuration Assistant of DB2 to check thedatabase alias that you specified.

3. Beginning with Performance Expert Version 3.1,you can no longer add a Performance Warehousesystem manually. Add the Performance ExpertServer on which the Performance Warehouseresides to your Performance Expert Client and openPerformance Warehouse from the System Overviewwindow.

DGOP18 Are you sure you want to removethis Performance Warehouse fromthe tree view?

DGOP19 The process has been scheduledand activated. {0}{0} Click ProcessExecutions in the folders pane of

the Performance Warehousewindow to view the progress of theprocess.

DGOP20 The Performance WarehouseClient cannot be initializedbecause of temporaryinconsistencies of {0} templates.

ExplanationMessage parameter {0} is either process, query, orrule-of-thumb.

This error occurs in rare cases when the set oftemplates is edited by another user while thePerformance Warehouse Client initializes. To avoidinconsistencies, the connection is terminated.

User responseRetry to connect.

DGOP1001 Specify a name for the processgroup.

DGOP1002 Specify a unique name for theprocess group.

DGOP1005 The process group cannot bedeleted because one or more of itsprocesses have the status 'active'.

User responseCheck the status of all processes and change it to 'indefinition', if necessary. Then delete the process group.

DGOP1101 Specify a name for the process.

DGOP1102 Process name already exists.

ExplanationYou attempted to create a process with a name thatalready exists in this group.

User responseChoose a different process name.

Note that the currently selected view might not showall processes in this group.

DGOP1105 The process cannot be deletedbecause it has the status 'active'.

User responseChange the process status to 'in definition', then deletethe process.


DGOP1106 The process cannot be renamedbecause it has the status 'active'.

User responseChange the process status to 'in definition', thenrename the process.

DGOP1107 You cannot add more steps to theselected process.

ExplanationYou tried to add a step to this process but this stepdoes not fit the step sequence of the process. Forexample, on the Trace on z/OS page, a process canconsist of only one step of type CRD. Additional stepsare not allowed.

User responseSee Monitoring Performance from the Workstation formore information about processes and allowed stepsand step sequences.

DGOP1108 You cannot add any steps to theselected process because theprocess has the status 'active'.

User responseChange the process status to 'in definition'. Then addthe step.

DGOP1109 The process cannot be activatedbecause it does not contain anysteps.

User responseAdd one or more steps to the process. Then activatethe process.

DGOP1110 This process is a template andcannot be edited.

ExplanationYou can use templates only as a basis for your ownprocesses.

User responseCopy this process to another process group, then editit.

DGOP1111 The process cannot be copiedbecause a private process groupdoes not exist yet.

ExplanationA process cannot be copied to a public process group.It can only be copied to a private process group.

User responseCreate a private process group and then copy theprocess to it.

DGOP1113 The specified process schedulecannot be stored because theschedule string exceeds themaximum length of {0} characters.

ExplanationYour current schedule definition produces a string thatis {1} characters long. This string is made up asfollows: {2}{2}Hours:\t{3} characters{2}Minutes:\t{4}characters{2}Days:\t{5} characters{2}Months:\t{6}characters{2}Years:\t{7} characters

User responseReduce the length of the schedule string by reducingthe complexity of the schedule. For example, specifyfewer intervals or fewer individual values.

DGOP1114 The status of the process cannotbe changed because the process isrunning.

User responseWait until the process has finished or cancel theprocess. Then try to change the process status.

DGOP1202 Specify an input data set for thestep.

DGOP1204 This step belongs to a process thathas the status 'active' andtherefore cannot be edited.

User responseChange the process status to 'in definition'.

DGOP1205 The step cannot be copiedbecause an appropriate privateprocess does not exist yet.

ExplanationA step can only be copied to a private process if it fitsthe step sequence of that process. The position of thecopied step has to be the same in the source andtarget step sequences. You can only copy steps to theend of the target step sequence.


User responseCreate a process or modify a process such that thestep to be copied fits. Then copy the step.

DGOP1206 The step cannot be deletedbecause the process containingthe step has the status 'active'.

User responseChange the process status to 'in definition', then deletethe step.

DGOP1207 This step is a template and cannotbe edited.

ExplanationYou can use templates as a basis for your own steps.

User responseCopy this step to another process. Then edit it.

DGOP1209 The data set name is not valid.

ExplanationA data set name must comply with the followingsyntax: dsname, dsname(member) ordsname(generation). When you specify a member, themember name must have one through eightalphanumeric characters, with the first character beinga letter. When you specify a generation, the generationmust be a one-, two-, or three-digit number that is lessthan, or equal to, 255 and is preceded by a dash (-), forexample -111, -23, or -3. If it is 0, you can omit thedash. Each digit can be a number from 0 through 9.

User responseSpecify a valid data set name.

DGOP1449 Alias not found.

ExplanationThe database alias is wrong or does not exist.

A new alias definition might not be recognized by theclient.

You have multiple DB2 instances installed on yourworkstation, and the DB2 catalog entries are defined ina DB2 instance other than the currently used instance.

User responseCorrect the database alias for the currently used DB2system, then try again.

Close and restart the workstation client, then try again.

If you have multiple DB2 instances installed on yourworkstation, you can force the DB2 instance to beused by specifying the command "setDB2INSTANCE=<your_instance>" in file db2pe.bat,respectively .db2pe under UNIX.

DGOP1514 The process has been scheduled.{0}{0} To run the process: Changethe process status from ''indefinition'' to ''active'' in theProcess Properties window.

ExplanationThe Data Server only checks the schedule of activatedprocesses.

DGOP1601 Specify at least one input data setfor the report.

DGOP1602 To create a report, add at least onecommand with at least onesubcommand to the REPORT pane.

DGOP1603 Add a REPORT or SAVEsubcommand to the STATISTICScommand.

ExplanationWhen you add the REDUCE subcommand, you mustalso add the REPORT or SAVE subcommand.

DGOP1604 When you select the Use thresholddata set check box in a REPORT,TRACE, or FILE command optionspane, you must specify at leastone exception threshold data setin the Current® data setspecification pane.

DGOP1605 Add a REPORT or SAVEsubcommand to the ACCOUNTINGcommand.

ExplanationWhen you add the REDUCE subcommand, you mustalso add the REPORT or SAVE subcommand.

DGOP1606 Specify a correct range value. Thegeneric form (*) can be used onlyas last character in a range value.

DGOP1607 Specify a name for the input dataset.

DGOP1608 Under Temporary DFSORT workfile, type a value in both fields orleave both fields empty.


DGOP1609 Under Temporary trace work file,type a value in both fields or leaveboth fields empty.

DGOP1610 The list of input data sets exceeds175 characters.

User responseRemove one or more input data sets from the list.

DGOP1611 Specify minimum and maximumvalues for the range.

DGOP1612 Specify a value.

DGOP1613 Specify a unique name for theinput data set.

DGOP1614 Specify a value that is unique inthe list of values.

DGOP1615 Delete the selected commandincluding its subcommands.

DGOP1706 The filter criteria shown in theInclude field exceed 250characters.

User responseDisplay the Include/Exclude Filter window and removeone or more filter criteria.

DGOP1707 The filter criteria shown in theExclude field exceed 250characters.










DGOP1857 The filter criteria shown in theOrder field exceed 200 characters.

User responseDisplay the Order Filter window and remove one ormore filter criteria.

DGOP1858 The filter criteria shown in the Topfield exceed 250 characters.

User responseDisplay the Top Filter window and remove one or morefilter criteria.

DGOP1859 If a check box is selected underFilter options, you must select atleast one top field.

DGOP1951 Specify a name for the group orlist.

DGOP1952 The name you specified for thegroup or list is not correct.

ExplanationA group or list name can consist of up to eightcharacters without embedded spaces and must beginwith a character from A to Z. The second to eightcharacters can be one of the following: A-Z, _, #, $,0-9, @

User responseSpecify a correct group or list name.

DGOP1953 Specify a group or list name that isunique within the report.

DGOP1954 Add at least one subcommand tothe GROUP or LIST command.


DGOP1955 Specify at least one value for theselected group or list.

DGOP1956 The values shown in the Groupvalues or List values field exceed50 characters.

User responseSpecify shorter values for the group or list or deleteone or more values.

DGOP3001 Rule-of-thumb group name ismissing.

ExplanationEvery rule-of-thumb group needs a name.

User responseSpecify a rule-of-thumb group name.

DGOP3002 The rule-of-thumb group name isnot unique.

ExplanationA rule-of-thumb group with this name already exists.

User responseSpecify a unique rule-of-thumb group name.

DGOP3101 Rule of thumb cluster name ismissing.

ExplanationEvery rule of thumb cluster needs a name.

User responseSpecify a rule of thumb cluster name.

DGOP3102 The rule of thumb cluster name isnot unique.

ExplanationA rule of thumb cluster with this name exists already inthe specified rule-of-thumb group.

User responseSpecify a unique rule of thumb cluster name.

DGOP3105 This rule-of-thumb cluster is atemplate and cannot be edited.

ExplanationYou can use templates as a basis for your own rule-of-thumb clusters.

User responseCopy this rule-of-thumb cluster to another rule-of-thumb group and edit it.

DGOP3106 The rule-of-thumb cluster cannotbe copied because a private rule-of-thumb group does not exist yet.

ExplanationA rule-of-thumb cluster cannot be copied to a publicrule-of-thumb group. It can only be copied to a privaterule-of-thumb group.

User responseCreate a private rule-of-thumb group and then copythe rule-of-thumb cluster to it.

DGOP3107 The additional column expressionof the rule-of-thumb cluster is toolong.

ExplanationAn additional column expression of the rule-of-thumbcluster can contain a maximum of 400 characters.

User responseSpecify a shorter additional column expression of therule-of-thumb cluster.

DGOP3108 The filter expression of the rule-of-thumb cluster is too long.

ExplanationA filter expression of the rule-of-thumb cluster cancontain a maximum of 3 000 characters.

User responseSpecify a shorter filter expression of the rule-of-thumbcluster.

DGOP3109 The additional column expressionof the rule-of-thumb cluster issyntactically wrong.


ExplanationAn additional column expression of the rule-of-thumbcluster must be a comma-separated list of tablecolumns.

User responseSpecify a correct comma-separated list of tablecolumns.

DGOP3110 The additional column expressionof the rule-of-thumb cluster issyntactically wrong.

ExplanationEach column of the additional column expression mustbelong to a table of a value expression of a containedrule of thumb.


DGOP3111 The additional column expressionof the rule of thumb containsredundant columns.

ExplanationAll columns of the additional column expression mustnot occur in a value expression of a contained rule ofthumb.


DGOP3204 The rule-of-thumb cannot becopied because an appropriateprivate rule-of-thumb cluster doesnot exist yet.

ExplanationA rule-of-thumb cannot be copied to a public rule-of-thumb cluster. It can only be copied to a rule-of-thumbcluster that has the same type as the rule-of-thumb tobe copied. The rule-of-thumb that you want to copymust be the first rule-of-thumb in the target privaterule-of-thumb cluster or be of the same type as therule-of-thumbs that already exist in that cluster.

User responseCreate a private rule-of-thumb cluster and then copythe rule-of-thumb to it.

DGOP3205 The value expression of the rule ofthumb is missing.

ExplanationEvery rule of thumb needs a value expression.

User responseSpecify a value expression for the rule of thumb.

DGOP3206 The warning threshold of the ruleof thumb is missing.

ExplanationEvery rule of thumb needs a warning threshold.

User responseSpecify a warning threshold for the rule of thumb.

DGOP3207 The problem threshold of the ruleof thumb is missing.

ExplanationEvery rule of thumb needs a problem threshold.

User responseSpecify a problem threshold for the rule of thumb.

DGOP3209 The value expression of the rule ofthumb is too long.

ExplanationA rule of thumb value expression can contain amaximum of 800 characters.

User responseSpecify a shorter rule of thumb value expression.

DGOP3210 The warning threshold of the ruleof thumb is too long.

ExplanationA rule of thumb warning threshold can contain amaximum of 18 characters.


User responseSpecify a shorter rule of thumb warning threshold.

DGOP3211 The problem threshold of the ruleof thumb is too long.

ExplanationA rule of thumb problem threshold can contain amaximum of 18 characters.

User responseSpecify a shorter rule of thumb problem threshold.

DGOP3212 The additional column expressionof the rule of thumb is too long.

ExplanationAn additional column expression of the rule of thumbcan contain a maximum of 400 characters.

User responseSpecify a shorter additional column expression of therule of thumb.

DGOP3213 The warning recommendation ofthe rule of thumb is too long.

ExplanationA rule of thumb warning recommendation can containa maximum of 128 characters.

User responseSpecify a shorter rule of thumb warningrecommendation.

DGOP3214 The problem recommendation ofthe rule of thumb is too long.

ExplanationA rule of thumb problem recommendation can containa maximum of 128 characters.

User responseSpecify a shorter rule of thumb problemrecommendation.

DGOP3215 The value expression of the rule ofthumb is syntactically wrong.

ExplanationA rule of thumb value expression must be anarithmetic expression.

User responseSpecify a correct arithmetic expression.

DGOP3216 The additional column expressionof the rule of thumb issyntactically wrong.

ExplanationAn additional column expression of the rule of thumbmust be a comma-separated list of table columns.


DGOP3217 The warning threshold of the ruleof thumb is syntactically wrong.

ExplanationA rule-of-thumb warning threshold must be a number.

User responseSpecify a decimal number or an integer.

DGOP3218 The warning threshold of the ruleof thumb is syntactically wrong.

ExplanationA rule-of-thumb warning threshold must be a number.


DGOP3219 The problem threshold of the ruleof thumb is syntactically wrong.

ExplanationA rule-of-thumb problem threshold must be a number.


DGOP3220 The problem threshold of the ruleof thumb is syntactically wrong.


ExplanationA rule-of-thumb problem threshold must be a number.


DGOP3221 This rule of thumb is a templateand cannot be edited.

ExplanationYou can use templates as a basis for your own rules ofthumb.

User responseCopy this rule of thumb to another rule-of-thumbcluster and edit it.

DGOP3222 The additional column expressionof the rule of thumb issyntactically wrong.

ExplanationEach column of the additional column expression mustbelong to a table used in the value expression.

User responseSpecify a correct comma-separated list of tablecolumns where each column belongs to a table used inthe value expression.

DGOP3223 The additional column expressionof the rule of thumb containsredundant columns.

ExplanationEach column of the additional column expression mustnot occur in the value expression.

User responseSpecify a correct comma-separated list of tablecolumns where each column does not occur in thevalue expression.

DGOP4003 No data returned for this analysisfilter.

DGOP4005 The minimum length of a variablename is 2 characters.

ExplanationA valid name of a variable consists of a colon followedby alphanumeric characters.

DGOP4006 The rules-of-thumb cluster isempty.

ExplanationThe cluster contains no rules of thumb.

User responseCreate at least one rule in the empty cluster.

DGOP4007 You have not specified a value forone or more of these variables: {0}.Are you sure that you want toproceed?

ExplanationNo values or empty string values have been assignedto the variables shown on the message text.

User responseEnter correct values for these variables.

DGOP4101 ROT details not applicable.

ExplanationThe attention value for the selection is null.

User responseMake a selection with attention values OK, problem, orwarning.

DGOP4102 Column details not available forthe current view.

ExplanationThere are no attention values for the selected ROT thatqualify for current view.

User responseExtend the view to Warning or All, respectively.

DGOP4103 Row details not available for thecurrent view.

ExplanationThere are no attention values for the selected ROT thatqualify for current view.


User responseExtend the view to Warning or All, respectively.

DGOP4104 No entries qualify for the selectedview.

DGOP4105 Column details are only availablefor columns referring to atimestamp or to rules of thumb.

ExplanationThe selected column has no column details. Forexample: the column refers to an additional matrixcolumn that is specified in the cluster definition.

User responseSelect the timestamp column to get row details or acolumn with the name of a rule of thumb to get columndetails.

DGOP4200 There is currently no helpavailable.

DGOP5003 Delete the selected output dataset from Performance Warehouse?

DGOP5004 Type of selected log entry does notmatch with rule of thumb or query.

DGOP6001 The query group name is missing.

ExplanationA query group name is not specified, or a name thatcontains only white-space characters is specified.

User responseSpecify a correct query group name.

DGOP6002 The query group name is notunique.

ExplanationA query group with this name already exists.

User responseSpecify a unique query group name.

DGOP6101 The query name is missing.

ExplanationA query name is not specified, or a name that containsonly white-space characters is specified.

User responseSpecify a correct query name.

DGOP6102 The query name is not unique.

ExplanationA query with this name already exists.

User responseSpecify a unique query name.

DGOP6105 This query is a template andcannot be edited.

ExplanationYou can use templates as a basis for your own queries.

User responseCopy this query to another query group and edit it.

DGOP6106 The query cannot be copiedbecause a private query groupdoes not exist yet.

ExplanationA query cannot be copied to a public query group. Itcan only be copied to a private query group.

User responseCreate a private query group and then copy the queryto it.

DGOP6107 The query expression (SELECTstatement) is missing.

ExplanationA query expression (SELECT statement) must bespecified.

User responseSpecify a query expression (SELECT statement).

DGOP6109 The query expression must startwith SELECT.

ExplanationA query expression must start with SELECT.


User responseSpecify a SELECT statement as query expression.

DGOP6502 The file cannot be opened.

ExplanationReasons why the file cannot be opened include:

• The file exists, but in another directory.• The file or directory is write-protected.• The file does not exist and cannot be created.

User responseSelect another file name and try again.

DGOP6503 The file cannot be opened.

ExplanationAn I/O exception occurred while opening the file.

User responseSelect another file name and try again.

DGOP6504 Cannot create temporary file indefault temporary-file directory{0}.

ExplanationA temporary file cannot be created in the defaulttemporary-file directory.

User responseCheck the file write permissions in the directorysecurity properties.

DGOP6505 A file with the name {0} alreadyexists. Do you want to overwriteit?

ExplanationThe file chosen already exists and will be overwritten ifconfirmed.

User responseClick the Yes button if you want the file to beoverwritten, otherwise click the No button.

DGOP6506 Sorting using the column headeronly affects the currentlyscrollable rows.

ExplanationThe result table shows only a part of the whole resultset. Sorting using the column header only affects theresult table, not the whole result set.

User responseTo sort the whole result set, use the ORDER BY clausein the SQL query.

FPEA - Accounting report set messagesFPEA0600S EXCEPTIONAL CONDITION

OCCURRED WHILE PROCESSINGACCOUNTING. MAIN STORAGEALLOCATION FAILED. RETURNCODE <V1>

ExplanationThere was insufficient storage available to continueprocessing.

• <V1> is the GETMAIN return code.

User responseIncrease the region size, and rerun the job.

FPEA0610S EXCEPTIONAL CONDITIONOCCURRED WHILE PROCESSINGACCOUNTING. MAIN STORAGERELEASE FAILED

ExplanationAn attempt to release storage failed.

User responseRerun the job. If the problem recurs, contact IBMsupport.

FPEA0700S VSAM <V1> FUNCTION FAILED ONDDNAME <V2>. VSAM RETURNCODE <V3>. REASON CODE <V4>

ExplanationA VSAM function failed.

• <V1> is the name of the VSAM function that failed.• <V2> is the ddname for which the function failed.• <V3> is the VSAM return code.


• <V4> is the VSAM reason code.

User responseSee the VSAM documentation.

FPEA0750S PUT FUNCTION FAILED ONDDNAME <V1> WHILEEXTERNALIZING REDUCEDRECORDS

ExplanationAn error occurred when writing records to theaccounting REDUCE work data set.

• <V1> is the ddname.

User responseCheck for system messages detailing the problem.

FPEA0800I THE ALLOCATED SPACE FORACWORK WAS SUFFICIENT. <V1>BYTES HAVE BEEN WRITTEN TOTHE ACWORK DATA SET,CONSUMED BY <V2> RECORDSWITH AN AVERAGE LENGTH OF<V3> AND A MAXIMUM RECORDLENGTH OF <V4>.

ExplanationInput trace data is successfully reduced. The space forthe temporary work data set with ddname ACWORKwas sufficient to hold all reduced data records.

• <V1> is number of bytes written to ACWORK.• <V2> is the number of reduced data records (of

variable lengths) written to ACWORK.• <V3> is the average record length of the reduced

data records.• <V4> is the maximum record length of the reduced

data records.

User responseThe values provided by this message might help toadjust the allocated ACWORK space for ACCOUNTINGREDUCE processing. For more information, see thedescription of REDUCE CALCULATE in the ReportingUser’s Guide.

FPEA0801S INSUFFICIENT SPACE WASALLOCATED FOR ACWORK.COMPLETELY REDUCED DATAWOULD REQUIRE AN ACWORK OF<V1> BYTES, CONSUMED BY <V2>RECORDS WITH AN AVERAGE

LENGTH OF <V3> AND AMAXIMUM RECORD LENGTH OF<V4>.

ExplanationFailure to reduce all input trace data because ofinsufficient space for the temporary work data set withddname ACWORK. No output data is written. However,the job continues to determine the necessary ACWORKspace.

• <V1> is the number of bytes ACWORK would requireto hold all reduced records (provided it is ofsufficient size).

• <V2> is the number of reduced data records (ofvariable lengths) that would be written to ACWORK(provided it is of sufficient size).

• <V3> is the average record length of the reduceddata records that has to be expected.

• <V4> is the maximum record length of the reduceddata records that has to be expected.

User responseAllocate more space to ACWORK and rerun the job.Allocate about 20% more space than indicated by<V1>. You might specify sufficient primary andsecondary work space as options in the SPACEparameter of the ACWORK DD statement. If necessary,specify a multi-volume data set for ACWORK. For moreinformation refer to the Reporting User’s Guide.

FPEA0803I THE INPUT TRACE INCLUDESIFCID 233, 380, OR 381 WHICH ISUSED TO IDENTIFY A STOREDPROCEDURE OR USER-DEFINEDFUNCTION MAIN ROUTINE. AREPORT BY ACTNAME TAKESACCOUNT OF NESTED CALLS BYACCUMULATING DATA FOR EACHMAIN ROUTINE INCLUDING ITSSUBROUTINES.

ExplanationIFCID 233, 380, or 381 was found in the input traceand is used for the calculation that is requested by thecommand ORDER(ACTNAME).

Note:

• IFCID 380 or 381 is preferred, if available, because ituses less system resources when collecting tracedata.

• Stored Procedures (SP) and User-Defined Functions(UDF) can be identified.


• Data of subprograms that were called by StoredProcedures or User-Defined Functions are reflectedin the output of the main program.

• The report has a view on data by activity type andname, but not by each package. That is why thefollowing package counters of subprograms are nottaken into account:

1. The occurrence of subprograms2. The number of package allocations (switches)3. The number of rollup threads

This approach also affects some package averages.

FPEA0804I IFCID 233, 380, OR 381 WAS NOTFOUND IN THE INPUT TRACE. THECALCULATION BY ACTIVITY NAMETREATS SUBPROGRAMS OF ASTORED PROCEDURE OR USER-DEFINED FUNCTION ASSEPARATE ACTIVITIES.

ExplanationThe calculation that is requested by the commandORDER(ACTNAME) is limited to the usage of IFCID 3and IFCID 239. These are the standard AccountingIFCIDs for reporting a thread and a package. The mainprogram of a Stored Procedure or User-DefinedFunction treats their subprograms as separateactivities.

FPEA1242I ACCOUNTING SAVE COMPLETE

ExplanationAccounting SAVE processing is completed.

User responseNone.

FPEA1245I ACCOUNTING FILE COMPLETE.<V1> RECORDS WRITTEN TODDNAME <V2>

ExplanationAccounting FILE processing is completed.

• <V1> is the number of records written by the FILEsubcommand.

• <V2> is the ddname used by the FILE subcommand.

User responseNone.

FPEA1246S UNSUCCESSFUL ATTEMPTWRITING TO FILE DATA SET FORACCOUNTING

ExplanationAn error occurred while writing data to the AccountingFile data set.


FPEA1247W ACCOUNTING TRACE NUMBER<V1>. ACCOUNTING TRACE FORTHIS DB2 SUBSYSTEM ISSUPPRESSED. RECORDS FROMMORE THAN ONE DB2 SUBSYSTEMARE PRESENT IN THE INPUT DATASETS AND PRESORTED(ACCEPT)IS SPECIFIED

ExplanationWhen PRESORTED(ACCEPT) is specified, eachAccounting trace shows a single subsystem. Thismessage is issued to identify the trace whose recordswere ignored.

• <V1> identifies the trace to which the messagerefers, by the order of the corresponding TRACEsubcommand.

Note that, depending on the operational situation, anadditional line indicating the location, group,subsystem ID, member, date, and time may bedisplayed immediately following the message number.

User responseTo produce traces for more than one location withPRESORTED(ACCEPT), request a separate trace foreach location, specifying multiple TRACEsubcommands. Use the INCLUDE option to controlwhich location’s data will appear in a trace.Alternatively, specify PRESORTED(NO); this allows anynumber of locations to be included in a single trace.

FPEA1248I ACCOUNTING <V1> NUMBER<V2>. THE REQUESTED TOP LISTFOR THIS DB2 SUBSYSTEM WASNOT PRODUCED BECAUSE THE<V1> DOES NOT CONTAIN ANYNONZERO VALUES IN THESPECIFIED FIELDS

ExplanationThe input data set contained all null or zero values forthe top fields for the location specified.


• <V1> is REPORT or TRACE.• <V2> identifies the report or trace to which the

message refers, by the order of the correspondingREPORT or TRACE subcommand.


User responseNone.

FPEA2252I ACCOUNTING FIELD <V1> WASNOT CALCULATED. A BEGIN TIMEWAS ZERO OR THE RESULTWOULD HAVE BEEN NEGATIVE

ExplanationA DB2 application time cannot be calculated becausethe begin time was either zero or greater than the endtime.

• <V1> is the field name.

This message may also occur for fields that are notpart of the IBM-provided default report layouts, that is,for fields that are provided via the User-TailoredReporting feature (UTR).


User responseNone.

FPEA2253I ACCOUNTING FIELD <V1> WASNOT CALCULATED A TOTAL OF<V2> TIMES. A BEGIN TIME WASZERO OR THE RESULT WOULDHAVE BEEN NEGATIVE

ExplanationA DB2 application time cannot be calculated becausethe begin time was either zero or greater than the endtime.

• <V1> is the field name.• <V2> is the number of times this event occurred.

User responseNone.

FPEA4500S INITIALIZATION FAILED FORACCOUNTING LIST.INSUFFICIENT STORAGEAVAILABLE



FPEA4530I NUMBER OF ORPHANED DBATSFOR LOCATION <V1> IS <V2>

ExplanationThe message is printed either at the end of the job forevery location if there are any orphaned DBATs, orwhen the maximum number of orphaned DBATs for allLUWIDs has been exceeded.

• <V1> is the location.• <V2> is the number of orphaned DBATs.

User responseIf the message is printed at end-of-file, no response isrequired. If the maximum number has been exceeded,do one of the following:

• Provide the missing data.• Exclude DBATs performed on behalf of non-DB2

requesters.• Check the job summary log whether the Accounting

traces started and ended at approximately the sametime. If they did not, run the job again using thebeginning and end times of the shortest Accountingtrace.

FPEA4531I GENERAL ACCOUNTING DATA FORLUWID INSTANCE <V1> ISMISSING. IFCID 3 IS MISSING

ExplanationThe package overflow data from an IFCID 239 recordcannot be matched with the corresponding IFCID 3.Multiple occurrences of this message indicateincomplete input.

• <V1> is the LUWID instance number.

User responseCheck the input and filters.


FPEA4532I ACCOUNTING DATA FOR ANUMBER OF PACKAGES FORLUWID <V1> IS MISSING. ONE ORMORE IFCID 239 IS MISSING

ExplanationSome package overflow data on IFCID 239 record(s)was missing. Multiple occurrences of this messageindicate incomplete input.

• <V1> is the LUWID number.

User responseCheck the input and filters.

FPEA4533S AN ERROR OCCURRED WHILEACCESSING A VIRTUAL STORAGEDATA STORE. THE REFERENCE IS<V1>, THE TEXT RETURNED FROMTHE DATA STORE IS <V2>

ExplanationAn unexpected event occurs while manipulatingrecords in virtual storage. The most likely cause is thatinsufficient virtual storage is available. Either theprogram has requested excessive virtual storage, orthe region requested was too small or was notsatisfied because of the installation limit.

• <V1> is the reference of the virtual storage datastore.

• <V2> is the text returned from the data store.

User responseExcessive use of virtual storage may be caused byincomplete data being passed to the Accountingsubcomponent. One such case arises when relatedIFCID 3 and 239 records cannot be matched, anotherwhen records belonging to the same distributed logicalunit of work cannot be matched in a merged trace orreport. Ensure that both IFCID 3 and 239 are beingincluded and, if MERGE has been specified, that datafor all locations is present. If the data is complete andthe problem cannot be resolved by specifying a largerregion size, contact IBM support.

FPEA4534I COORDINATING PARALLEL TASKFOR LUW INSTANCE <V1> IS NOTREPORTED AS NOT ALLINFORMATION FOR ASSISTINGPARALLEL TASKS FROM MEMBER<V2> IS AVAILABLE

ExplanationThe number of assisting parallel tasks belonging to thecoordinating parallel task does not match the receivednumber of assisting parallel tasks. A thread is onlyreported if the coordinating parallel task and allcorresponding assisting parallel tasks are available inthe job input.

• <V1> is the LUW instance of the incomplete task.• <V2> is the member name of the missing assisting

task.

User responseIf you wish that the thread is reported, ensure that allIFCID 3 records are available for the coordinatingparallel tasks and the assisting parallel tasks.

FPEA4535I DATA SECTION <V1>, SECTIONNUMBER <V2>, <V3>. HASLENGTH <V4> INSTEAD OFEXPECTED LENGTH <V5>. FIELDVALUES MIGHT BE INVALID.

ExplanationAn incompatibility exists between DB2 andOMEGAMON XE for DB2 PE IFC records.

• <V1> is the data section name• <V2> is the data section number within the IFC• <V3> is the IFC number• <V4> is the found length of the data section• <V5> is the expected length of the data section asdefined in the current DB2 macro.

User responseUpgrade DB2 and OMEGAMON XE for DB2 PE to thelatest PTFs. Collect new trace data after upgrading andrerun OMEGAMON XE for DB2 PE.

FPEA4536I INCONSISTENT DATA FOUND FORLUW: NETWORK ID <V1>,LOGICAL UNIT <V2>, INSTANCE<V3> WITH ACCOUNTINGTIMESTAMP <V4>.IFCID 239INCLUDES QXPK, QBUF, ANDQTXA SECTIONS ALTHOUGH THEQWACPARR FLAG OF IFCID 3 ISON. THE FLAG DENOTES ROLLUP,BUT ROLLUP DATA SHOULD NOTCONTAIN THESE SECTIONS.


ExplanationThe job input includes inconsistent data. Generalpackage data is normally accompanied by theadditional package level accounting sections QXPK,QBUF, and QTXA. In case of rollup, only a singlepackage section is expected without the additionalsections, and the QWACPARR flag is being set on. Atleast one record has been found for which theseconditions do not match. Use the following parametersto identify the missing task in an Accounting trace:

• <V1> is the LUW network ID of the missing task.• <V2> is the LUW logical unit of the missing task.• <V3> is the LUW instance of the missing task.• <V4> is the Accounting timestamp of the missing

task.

User responseSave the job input and output and contact IBMsupport.

FPEA4537I INCONSISTENT DATA FOUND FORLUW: NETWORK ID <V1>,LOGICAL UNIT <V2>, INSTANCE<V3> WITH ACCOUNTINGTIMESTAMP <V4>.IFCID 239 DOESNOT INCLUDE ALL QXPK, QBUF,AND QTXA SECTIONS ALTHOUGHQWACPARR FLAG OF IFCID 3 ISOFF. THE FLAG DENOTES NOACTIVE ROLLUP, THEREFORESECTIONS ARE MISSING.

ExplanationThe job input includes inconsistent data. Generalpackage data is normally accompanied by theadditional package level accounting sections QXPK,QBUF, and QTXA. In case of rollup, only a singlepackage section is expected without the additional

sections, and the QWACPARR flag is being set on. Atleast one record has been found for which theseconditions do not match. Use the following parametersto identify the missing task in an Accounting trace:

• <V1> is the LUW network ID of the missing task.• <V2> is the LUW logical unit of the missing task.• <V3> is the LUW instance of the missing task.• <V4> is the Accounting timestamp of the missing

task.

User responseSave the job input and output and contact IBMsupport.

FPEA4538I A RECORD HAS BEEN DROPPEDFROM FURTHER PROCESSINGBECAUSE IT CANNOT BEASSIGNED TO A KNOWN IFCID 3TYPE. NETWORK ID <V1>,LOGICAL UNIT <V2>, INSTANCE<V3> WITH ACCOUNTINGTIMESTAMP <V4>.

ExplanationAn IFCID 3 trace record does not satisfy one of severalwell defined conditions of DB2. The record cannot beidentified. Therefore it is excluded from the requestedprocesses.

• <V1> is the LUW network ID of the failing record.• <V2> is the LUW logical unit of the failing record.• <V3> is the LUW instance of the failing record.• <V4> is the Accounting timestamp of the unknown

record.

User responseNone.

FPEB - User-Tailored Reporting messagesFPEB000 This command is not recognized

ExplanationThe command entered could not be recognized.

User responseEnter a valid command.

FPEB003 <V1> command not valid in thispanel

ExplanationThe specified command is not valid in this panel.

• <V1> is the command that is not valid.

User responseEnter a valid command for this panel.

FPEB010 An error occurred during an ISPF<V1> service in module <V2>


ExplanationAn ISPF error has occurred.

• <V1> is the ISPF service name.• <V2> is the internal module.

User responseExit, then restart the application. If the problemrecurs, contact IBM support.

FPEB020 Select a number between 1 and 4

ExplanationNone.

User responseEnter 1, 2, 3, or 4.

FPEB021 Valid DPMPARMS data set namemust be entered

ExplanationEither the specified DPMPARMS data set does not exist,or the specified name is not valid.

User responseEnter the name of a valid DPMPARMS data set.

FPEB022 No layouts exist to modify

ExplanationThere were no layouts available to be modified.

User responseThis message only occurs if you have not installed theuser-tailored reporting feature correctly.

FPEB023 Select a layout using one of thefollowing characters: <V1>

ExplanationEither no selection was made from the list, more thanone item was selected from the list, or a characterother than / or a country-designated character wasused to select a list item.

• <V1> is ⁄ and the country-designated character.

User responseSelect the layout you require from the list by entering /or a country-designated character.

FPEB024 Select one or more items to bemodified using one of thefollowing characters: <V1>

ExplanationEither no selection was made from the list, or acharacter other than / or a country-designatedcharacter was used to select a list item.

• <V1> is ⁄ and the country-designated character.

User responseSelect the item or items you require from the list byentering / or a country-designated character.

FPEB025 Duplicate order column numbersentered, so no renumbering hasoccurred

ExplanationThe same number was entered in more than one ordercolumn.

User responseChange the numbers in the order column.

FPEB026 Block configuration selection mustbe 1 (yes) or 2 (no)

ExplanationYou have selected an block configuration that is notvalid.

User responseEnter 1 or 2.

FPEB027 FILLER length must be between 1and 132

ExplanationThe specified FILLER length is not valid.

User responseEnter a FILLER length between 1 and 132.

FPEB028 Internal storage error. Not enoughelements of SELECTED_BLK havebeen allowed for

ExplanationToo many blocks have been selected for processing.


User responseSelect fewer blocks.

FPEB029 Internal storage error. Not enoughelements of SELECTED_CAT havebeen allowed for

ExplanationToo many categories have been selected forprocessing.

User responseSelect fewer categories.

FPEB030 The cursor must be positioned on aselected list entry when using theFILLER command

ExplanationThe FILLER was added after the row containing thecursor. This row must be a selected row.

User responsePosition the cursor on a selected row before issuingthe FILLER command.

FPEB031 No blocks can be modified

ExplanationAn internal error occurred.

User responseSelect a different layout. If the problem recurs, contactIBM support.

FPEB032 No fields for the nominated blockand category can be modified

ExplanationYou cannot modify the fields of the nominated blockand category.

User responseSelect a different block or category.

FPEB033 No table rows for the nominatedblock and category can bemodified

ExplanationYou cannot modify the table rows of the nominatedblock and category.


FPEB034 No table columns for thenominated block and category canbe modified

ExplanationYou cannot modify the table columns of the nominatedblock and category.


FPEB035 No field qualifiers for thenominated block can be modified

ExplanationYou cannot modify the field qualifiers of the nominatedblock and category.

User responseSelect a different block.

FPEB036 Changes have been accepted.Press Enter again to continue

ExplanationIf you have made any changes, the panel isredisplayed showing the changes.

User responsePress Enter again to continue.

FPEB037 Changes have been accepted.EXIT again to continue

ExplanationIf you have made any changes, the panel isredisplayed showing the changes.

User responsePress F3 (Exit) again to continue.


FPEB038 Order must be a number from 1 to99998. Blank or 99999 to excludeitem

ExplanationNone.

User responseEnter a number from 1 to 99 998 to select an item.Blank out or enter 99999 to exclude an item.

FPEB039 Changes for items with anonnumeric order number havebeen ignored

ExplanationYou have entered a nonnumeric value in the ORDERcolumn of the IRF⁄UTR panel. The value has beenignored.

User responseChange the value in the ORDER column or press thesame key to continue processing.

FPEB040 Layout name must be entered

ExplanationNone.

User responseEnter a layout name (1 to 6 characters).

FPEB041 Layout description must beentered

ExplanationNone.

User responseEnter a layout description (1 to 32 characters).

FPEB042 Specify if each new record is tostart on a new page

ExplanationNone.

User responseEnter 1 if each record is to start on a new page, or 2 ifnot.

FPEB043 The layout has been saved

ExplanationThe layout has been saved into the DPMPARMS dataset.

User responseNone.

FPEB044 The layout has not been saved

ExplanationYou have canceled layout changes.

User responseNone.

FPEB049 Error stowing the DPMPARMSlayout member

ExplanationAn error occurred during stowing the DPMPARMSdirectory entry.

User responseAdd more directory blocks to the DPMPARMS data set,and try again.

FPEB070 Tailored layout has been migratedto the current version

ExplanationYou have selected a user-tailored layout contained inthe DPMPARMS data set that belongs to an earlierrelease. It was automatically migrated to the installedrelease.

User responseNone.

FPEB071 While migrating a tailored layout,an ISPF <V1> service call failedwith a return code of <V2>

ExplanationAn ISPF error has occurred.

• <V1> is the ISPF service name.• <V2> is the return code from this service.



FPEB080 Browse data set dynamicallocation has reason code x'<V1>'

ExplanationAn attempt to dynamically allocate a temporarybrowse data set failed.

• <V1> is the reason code in hexadecimal notationreturned by the dynamic allocation service.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) forassistance. If the problem recurs, see your systemprogrammer or contact IBM support.

FPEB081 Browse data set could not beopened

ExplanationAn attempt to open the temporary browse data set hasfailed.

User responseCheck for system messages detailing the problem. Tryagain, and if the problem recurs, see your systemprogrammer or contact IBM support.

FPEB082 DPMPARMS data set receivedLMINIT error - <V1>

ExplanationA problem occurred during allocation of the DPMPARMSdata set.

• <V1> is the ISPF long message returned by theLMINIT service.


FPEB083 DPMPARMS data set receivedLMOPEN error - <V1>

ExplanationA problem occurred while opening the DPMPARMS dataset for write access.

• <V1> is the ISPF long message returned by theLMOPEN service.


FPEB084 Error reading the DPMPARMSlayout member

ExplanationAn attempt to read the DPMPARMS layout member hasfailed.


FPEB085 Error writing the DPMPARMSlayout member

ExplanationAn attempt to write the layout member to theDPMPARMS data set has failed.


FPEB086 DPMPARMS data set dynamicallocation has reason code x'<V1>'

ExplanationAn attempt to dynamically allocate the DPMPARMS dataset failed.

• <V1> is the reason code in hexadecimal notationreturned by the dynamic allocation service.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) forassistance. If the problem recurs, see your systemprogrammer or contact IBM support.

FPEB087 Storage for the user layout couldnot be allocated


ExplanationAn attempt to allocate virtual storage for the userlayout to be stored has failed.


FPEB088 Storage for the modified layoutcould not be allocated

ExplanationAn attempt to allocate virtual storage for the modifiedlayout to be stored has failed.


FPEB089 DPMPARMS data set could not beopened

ExplanationAn attempt to open the DPMPARMS data set has failed.


FPEB091 ISPF browse failed

ExplanationAn ISPF error has occurred attempting to BROWSE thegenerated layout.


FPEB092 UTR layout print service failed

ExplanationAn attempt to write to the browse data set has failed.


FPEB093 The requested layout could not beloaded

ExplanationAn attempt to load a default layout into virtual storagehas failed.


FPEB094 Browse data set received LMINITerror - <V1>

ExplanationA problem occurred during allocation of the temporarybrowse data set.

• <V1> is the ISPF long message returned by theLMINIT service.


FPEB095 Browse data set received LMOPENerror - <V1>

ExplanationA problem occurred while opening the temporarybrowse data set.

• <V1> is the ISPF long message returned by theLMOPEN service.


FPEB096 Default layout does not belong tothis version of DB2 PerformanceExpert

ExplanationA default layout from an earlier version was detected.


User responseUse one of the default layouts supplied with thecurrent version.

FPEB097 Layout generation has failed, so nosample report has been produced

ExplanationAn attempt to generate the layout in virtual storagehas failed.


FPEB098 User layout does not belong to thecurrent product version

ExplanationA user layout from an earlier version was detected.

User responseCreate a new user default for the current productversion.

FPEB099 Some delay can be expected whilethe layout is generated

ExplanationThe layout is being generated in virtual storage.

User responseNone.

FPEC - Background Control messagesFPEC0002U SYSPRINT COULD NOT BE OPENED

ExplanationAn error occurred when opening SYSPRINT.

User responseSee your system programmer for assistance.

FPEC0008U UNABLE TO INITIALIZE LOCATIONQUEUE

ExplanationAn error occurred during initialization.


FPEC0020I INTERNAL ERROR: UNABLE TOPRODUCE MESSAGE <V1>.INTERNAL ERROR CODE <V2>

ExplanationAn error occurred when writing an error message.

• <V1> is the number of the message.• <V2> is the internal error code.

User responseRerun the job. If the problem recurs, contact IBMsupport and quote the internal error code.

FPEC0021S THE MESSAGE HANDLER WASUNABLE TO WRITE A MESSAGE TOTHE JOB SUMMARY VSAM FILE.VSAM RETURN CODE <V1>,REASON CODE <V2>

ExplanationAn error occurred when writing an error message.

• <V1> is the VSAM return code.• <V2> is the reason code.


FPEC0022S UNABLE TO WRITE HEADINGS TOFILE <V1>

ExplanationAn internal exception occurred within DB2 PM.

• <V1> is the name of the file.


FPEC0023S UNABLE TO WRITE A MESSAGE TOFILE <V1>


ExplanationAn error occurred when writing a message to an outputdata set.

• <V1> is the name of the file.


FPEC0024S UNABLE TO WRITE A MESSAGE TOA <V1> REPORT

ExplanationAn error occurred when writing a message to a report.

• <V1> is the name of the report.


FPEC0600U MAIN STORAGE ALLOCATIONFAILED DURING INITIAL SETUPOF ENVIRONMENT

ExplanationA storage constraint was experienced duringexecution.

User responseIncrease the region size and rerun the job.

FPEC0610W CORRELATION TRANSLATIONRECORD <V1>: OFFSET FIELDMUST BE NUMERIC IN THE RANGEOF 0 TO 11

Explanation<V1> indicates the row number in the CORRDATAmember of the DPMPARMS data set where the erroroccurred.

The values in the fields Name Offset and NumberOffset indicate the location where the correlationname or the correlation number begins.

To ensure the correct specification of the parameters,you can use the Correlation Translation Data Seteditor.

User responseSpecify a numeric value in the range of 0 to 11 toindicate the location where the correlation name or thecorrelation number begins.

FPEC0611W CORRELATION TRANSLATIONRECORD <V1>: LENGTH FIELDMUST BE NUMERIC IN THE RANGEOF 1 TO 8


The values in the fields Name Length and NumberLength indicate the length of the correlation name orthe correlation number. The length of the correlationname or the correlation number must not exceed 8bytes including the offset.


User responseSpecify a numeric value in the range of 1 to 8 toindicate the length of the correlation name or thecorrelation number including the offset.

FPEC0612W CORRELATION TRANSLATIONRECORD <V1>: LENGTH VALUEREQUIRED


The value for the fields Name Length or NumberLength is missing. The length of the correlation nameor the correlation number must not exceed 8 bytesincluding the offset.


User responseSpecify a numeric value in the range of 1 - 8 to indicatethe length of the correlation name or the correlationnumber including the offset value.

FPEC0613W CORRELATION TRANSLATIONRECORD <V1>: OFFSET VALUEREQUIRED



The value for the fields Name Offset or Number Offsetis missing.


User responseSpecify a numeric value in the range of 1 - 11 toindicate the location where the correlation name or thecorrelation number begins.

FPEC0614W CORRELATION TRANSLATIONRECORD <V1>: SUM OF OFFSETAND LENGTH CANNOT EXCEED 12BYTES


The length of the correlation name or the correlationnumber must not exceed 12 bytes including the offsetvalue.


User responseCorrect the input record. This error would never occurif the correlation translation data set editor had beenused.

FPEC0615W CORRELATION TRANSLATIONRECORD <V1>: CONNECTIONTYPE REQUIRED

ExplanationThe specification of the connection type is missing.

<V1> indicates the row number in the CORRDATAmember of the DPMPARMS data set where the erroroccurred.


User responseIn the Connection Identifier field, specify the 8-byteconnection name that is used by DB2 to identify yourenvironment, for example, CICS, TSO, or IMS.

FPEC0901S SORT HAS ENCOUNTERED ANERROR DURING EXECUTION THAT

DID NOT ALLOW IT TO COMPLETESUCCESSFULLY

ExplanationNone.

User responseCheck the SYSOUT file for SORT error messages. Seethe appropriate Sort documentation for furtherinformation. Correct the input and rerun the job.

FPEC0902I SORT HAS ISSUED AT LEAST ONEINFORMATIONAL MESSAGEDURING PROCESSING. CHECKSYOUT FOR DETAILS

ExplanationSort issued one or more informational or warningmessages during processing because one or moresingle input records were incomplete or not valid. Theaffected records were discarded by the sort andprocessing continued. All other records wereprocessed successfully.

User responseLook at the SYSOUT to see any messages issued bySort.

One or two incomplete records in several thousandshould not make a noticeable difference to any reportproduced. If too many records were discarded, inputdata could be incomplete.

FPEC0903I INPUT DATA SET APPEARS TO BETERSED

ExplanationThe data read from the input data set showscharacteristics of being compressed with TERSE.

User responseIf you are sure that the data set specified in theINPUTDD statement is not compressed, ignore thismessage. Otherwise, uncompress the data set and tryagain.

FPEC0904W STORAGE ALLOCATION FAILED.NO SMF DECOMPRESSIONPOSSIBLE.

ExplanationThe batch reporting utility identified a DB2 SMF tracerecord that is compressed. The allocation of storage to


prepare the decompression fails because ofinsufficient storage.

User responseDB2 allows compression of SMF trace records, whichare decompressed by the batch reporting utility. In thiscase a corrupted SMF record caused a failure in thestorage allocation. If the problem persists, contactyour DB2 administrator.

FPEC0905W COMPRESSED RECORD HAS ANINVALID LENGTH. NO SMFDECOMPRESSION POSSIBLE.

ExplanationAn SMF record has a maximum length of 32 KB. Thebatch reporter identified a record that exceeds thislength. The record is invalid.

User responseContact your DB2 administator.

FPEC0906W CSRCESRV QUERY FAILS WITHRC=<V1>. NO DECOMPRESSIONPOSSIBLE.

ExplanationThe batch reporting utility identified a DB2 SMF tracerecord that is compressed. For the decompression thez/OS compression utility CSRCESRV is used. In thiscase the QUERY service failed.

User responseCheck the IBM documentation that describesCSRCESRV SERVICE=QUERY. The return code gives anexplanation why the QUERY failed.

FPEC0908W CSRCESRV EXPAND FAILS WITHRC=<V1>. NO DECOMPRESSIONPOSSIBLE.

ExplanationThe batch reporting utility identified a DB2 SMF tracerecord that is compressed. For the decompression thez/OS compression utility CSRCESRV is used. In thiscase the EXPAND service failed.

User responseCheck the IBM documentation that describesCSRCESRV SERVICE=EXPAND. The return code givesan explanation why the EXPAND failed.

FPEC0909I NUMBER OF DECOMPRESSED SMFRECORDS: <V1>

ExplanationThe batch reporting utility provides the number ofdecompressed SMF records.

User responseNone.

FPEC0910E NO REPORTS HAVE BEENPRODUCED DUE TO PREVIOUSERRORS

ExplanationNone.

User responseCorrect the input and rerun the job.

FPEC0999I EXECUTION COMPLETE. RETURNCODE <V1>

ExplanationPerformance Expert execution completed.

• <V1> is the return code.

User responseFor return codes other than 0, evaluate the precedingmessages for possible problem reasons.

FPEC1002S OPEN FAILED FOR RESERVEDDDNAME <V1>

ExplanationThe specified ddname is reserved and cannot be usedin its current context.

• <V1> is the ddname in error.

User responseCorrect the JCL and rerun the job.

FPEC1003S OPEN FAILED FOR DDNAME <V1>,DDNAME IN USE

ExplanationA ddname is specified twice (or more) with conflictingpurposes.

• <V1> is the ddname for which the error occurred.



FPEC1004E REQUIRED DDNAME <V1>MISSING

ExplanationA required ddname was not in the JCL for the job.

• <V1> is the missing ddname.


FPEC1005S OPEN FAILED FOR DDNAME <V1>

ExplanationAn error occurred when opening a data set. The dataset exists, but cannot be opened.



FPEC1006E UNABLE TO DYNAMICALLYALLOCATE DDNAME <V1>.RETURN CODE <V2>, REASONCODE <V3>

ExplanationThe listed ddname cannot be allocated dynamically.

• <V1> is the ddname to be allocated.• <V2> is the return code from DYNALLOC.• <V3> is the reason code returned from DYNALLOC.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) for anexplanation of the return code and reason code.

FPEC1007S UNABLE TO READ FROM SYSINDATA SET

ExplanationAn error occurred while attempting to read from theSYSIN data set.

User responseCheck for accompanying messages to correct the error.

FPEC1008S UNABLE TO REALLOCATE SYSINFOR DB2 LOAD

ExplanationAn attempt was made to reallocate SYSIN DD. Whilethe first step (free SYSIN) was successful, the secondstep (dynamically allocate SYSIN) returned an error.


FPEC1009S UNABLE TO ALLOCATE SYSPRINTFOR DB2 LOAD

ExplanationAn error occurred when allocating SYSPRINT.


FPEC1400E ERROR LOADING LOCDATAMEMBER DETAILS

ExplanationAn internal error occurred while loading the timezonedetails from the LOCDATA member of the DPMPARMSdata set.


FPEC1401E ERROR LOADING MAINPACKMEMBER DETAILS

ExplanationAn internal error occurred while loading the mainpackdetails from the MAINPACK member of the DPMPARMSdata set.


FPEC1700S VSAM <V1> FUNCTION FAILED ONDDNAME <V2>. VSAM RETURNCODE <V3>, REASON CODE <V4>

ExplanationA VSAM function failed.


• <V1> is the name of the VSAM function that failed.• <V2> is the ddname for which the function failed.• <V3> is the VSAM return code.• <V4> is the VSAM reason code.

User responseSee the appropriate VSAM documentation.

FPEC1990I APPLICATION CANCELED DUE TOERRORS LISTED ABOVE

ExplanationErrors occurred during processing.

User responseExamine other messages to determine the cause ofthe error.

FPEC1997I SYNTAX CHECK OF COMMANDSTREAM COMPLETE. ASSOCIATEDPROCESSING HAS NOT BEENSCHEDULED AS NO EXECCOMMAND HAD BEEN SPECIFIED

ExplanationThe syntax of the command stream was checked, butno additional processing was performed, becausethere was no EXEC command.

User responseNone.

FPEC1998I SYNTAX CHECK OF COMMANDSTREAM COMPLETE. ASSOCIATEDPROCESSING HAS NOT BEENSCHEDULED DUE TO ERRORSDETAILED ABOVE

ExplanationThe syntax of the command stream was checked, butno additional processing was performed because oferrors in system initialization.

User responseSee the error messages listed.

FPEC1999I SYSTEM INITIALIZATIONCOMPLETE. RETURN CODE <V1>

ExplanationSystem initialization is completed.

• <V1> is the return code from the system initializationcomponent.

User responseIf the return code is zero, no action is required. If thereturn code is not zero, check other messages todetermine the cause of the error.

FPEC2001I COMMAND INPUT FROM DDNAME<V1>

ExplanationThe application is reading command input from thespecified ddname.


User responseNone.

FPEC2004E <V1> VALUE INVALID, VALIDRANGE IS <V2> TO <V3>

ExplanationThe input value is outside the permissible range.

• <V1> is the input value.• <V2> is the lower limit of the valid range.• <V3> is the upper limit of the valid range.


FPEC2005E <V1> IS AN UNRECOGNIZABLEREPORTING IDENTIFIERKEYWORD. INPUT IGNOREDFROM <V1> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationAn identifier keyword cannot be recognized. Input wasignored between the error and the next validcommand, subcommand, or option.

• <V1> is the unrecognizable keyword.


FPEC2006E INSTALLATION IS INCOMPLETE


ExplanationThe licence FMID for OMEGAMON XE for DB2 PE orOMEGAMON XE for DB2 PM is not correctly installed.

User responseIf errors occurred during installation, correct them andtry to use the product again.

If OMEGAMON XE for DB2 PE or OMEGAMON XE forDB2 PM installed without errors, and you followed therecommended installation and customizationprocedures, and the problem persists, contact IBMsupport.

FPEC2009E <V1> PARAMETER MUST BEALPHANUMERIC

ExplanationThe parameter can only contain the characters in therange A to Z, and 0 to 9.

• <V1> is the keyword in error.


FPEC2010E <V1> HAS ALREADY BEENSPECIFIED

ExplanationA command was specified more than once in the samecommand stream.

• <V1> is the command that was specified more thanonce.

User responseRemove the occurrences of <V1> except for one.

FPEC2011E <V1> IS AN UNRECOGNIZABLETOP PARAMETER KEYWORD.INPUT IGNORED FROM <V1> TONEXT COMMAND, SUBCOMMAND,OR OPTION KEYWORD

ExplanationA TOP parameter keyword cannot be recognized. Inputwas ignored between the error and the next validcommand, subcommand, or option.



FPEC2012E <V1> VALUE <V2> INVALID. VALIDRANGE <V3> TO <V4>

ExplanationThe supplied value of the OMEGAMON XE for DB2 PEidentifier is not valid.

• <V1> is the OMEGAMON XE for DB2 PE identifier.• <V2> is the value supplied.• <V3> is the lower limit of the valid range.• <V4> is the upper limit of the valid range.


FPEC2013E <V1> VALUE <V2> IS NOTNUMERIC

ExplanationThe value supplied in the INCLUDE/EXCLUDE orGROUP/LIST specification for the OMEGAMON XE forDB2 PE identifier shown must be numeric.

• <V1> is the identifier.• <V2> is the value supplied.

User responseCorrect the INCLUDE/EXCLUDE or GROUP/LISTspecification and rerun the job.

FPEC2014E <V1> PARAMETER <V2> IS ANINVALID DDNAME

ExplanationThe parameter supplied is not a valid ddname.

• <V1> is the option.• <V2> is the value supplied.


FPEC2101E RIGHT PARENTHESIS INSERTEDTO COMPLETE <V1> COMMAND

ExplanationA closing parenthesis is missing from the end of acommand.


• <V1> is the command with the missing parenthesis.


FPEC2102E GROUP/LIST NAME MUST BEALPHANUMERIC

ExplanationThe GROUP/LIST supplied contains characters otherthan A-Z or 0-9.

User responseCorrect the specification and rerun the job.

FPEC2104E UNEXPECTED END OF FILEENCOUNTERED IN <V1>COMMAND

ExplanationThe end of the command data set was encounteredbefore the end of the command stream. This error ismost commonly caused by a missing closingparenthesis at the end of the command stream.

• <V1> is the command where end of file wasencountered.


FPEC2105E INVALID INPUT ENCOUNTERED IN<V1> COMMAND. INPUT IGNOREDFROM <V2> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationA not valid command was encountered. The inputbetween the error and the next valid command wasignored.

• <V1> is the command where the incorrect input wasencountered.

• <V2> is the incorrect input.


FPEC2106E <V1> IS AN UNRECOGNIZABLECOMMAND KEYWORD. INPUTIGNORED FROM <V1> TO NEXT

COMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationAn unrecognizable command was encountered. Inputwas ignored between the error and the nextrecognizable command.

• <V1> is the text of the unrecognizable command.


FPEC2107E <V1> MUST PRECEDE ALL OTHERCOMMANDS

Explanation• <V1> is the CASE command, which must bespecified before any other command.

User responseSpecify the CASE command first.

FPEC2114W DISTRIBUTE COMMANDKEYWORD IS NO LONGERSUPPORTED. INPUT IGNOREDFROM DISTRIBUTE TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD.

Explanation:The DISTRIBUTE command is no longer used.

User responseNone.

FPEC2115W SPREADSHEETDD OPTIONKEYWORD IS NO LONGERSUPPORTED. INPUT IGNOREDFROM SPREADSHEETDD TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD.

Explanation:The SPREADSHEETDD FILE subcommand optionkeyword is no longer used for STATISTICS.

User response:Use the Spreadsheet input data generator functionalityinstead.

FPEC2151E RIGHT PARENTHESIS EXPECTEDTO CLOSE <V1> SPECIFICATION.<V2> ENCOUNTERED


ExplanationA closing parenthesis is missing from the end of anINCLUDE/EXCLUDE or GROUP/LIST specification.

• <V1> is INCLUDE, EXCLUDE, GROUP, or LIST.• <V2> is the string encountered where the right

parenthesis was expected.

User responseCorrect the specification.

FPEC2152E <V1> INVALID FOR GROUP

ExplanationA GROUP specification cannot be made for theidentifier shown.

• <V1> is the identifier supplied.

User responseRemove the GROUP specification.

FPEC2153E <V1> IS INVALID FOR AN <V2>SPECIFICATION FOR THISCOMMAND/FUNCTIONCOMBINATION

ExplanationThe identifier shown is not valid for an INCLUDE/EXCLUDE specification for the command and functionassociated.

• <V1> is the identifier supplied.• <V2> is INCLUDE or EXCLUDE.

User responseRemove the specification.

FPEC2154E <V1> IS AN INVALID VALUE FORTHREADTYPE

ExplanationThe value supplied for THREADTYPE in an INCLUDE/EXCLUDE or GROUP/LIST specification is incorrect.

• <V1> is the incorrect value that was supplied.

User responseSee the Report Command Reference for a list of validvalues for THREADTYPE. Correct the specification andrerun the job.

FPEC2155E INCLUDE/EXCLUDE ALREADYSPECIFIED FOR <V1>

ExplanationAn INCLUDE or EXCLUDE specification has alreadybeen made for the identifier shown within the samecommand and function.


User responseRemove the duplicate INCLUDE or EXCLUDEspecification.

FPEC2156E <V1> IS AN INVALID VALUE FORREQUESTTYPE

ExplanationThe value supplied for REQUESTTYPE in an INCLUDE/EXCLUDE or GROUP/LIST specification is not valid.


User responseSee the Report Command Reference for a list of validvalues for REQUESTTYPE. Correct the specificationand rerun the job.

FPEC2157E VALUE <V1> SUPPLIED FOR <V2>IS TOO LONG

ExplanationThe value supplied for the identifier shown in anINCLUDE/EXCLUDE or GROUP/LIST specification is toolong.

• <V1> is the value the length of which is too long.• <V2> is the identifier supplied.

User responseSee the Report Command Reference for the maximumpermitted length for a value of this identifier.

FPEC2158E GENERIC VALUES FOR <V1> ARENOT PERMITTED

ExplanationGeneric values are not permitted for the identifiershown, because they have no meaning.



User responseRemove the generic value.

FPEC2159E <V1> IS AN INVALID VALUE FORRESOURCETYPE

ExplanationThe value supplied for RESOURCETYPE in anINCLUDE/EXCLUDE or GROUP/LIST specification is notvalid.


User responseSee the Report Command Reference for a list of validvalues for RESOURCETYPE. Correct the specificationand rerun the job.

FPEC2160E <V1> IS AN INVALID VALUE FORTYPE

ExplanationAn INCLUDE/EXCLUDE or GROUP/LIST specificationwas made with an unknown type.

• <V1> is the unknown type.

User responseSee the Report Command Reference for a list of validtypes. Correct the specification and rerun the job.

FPEC2163E THE USE OF > OR < IN <V1>VALUES IS INVALID

ExplanationThe use of > or < for the indicated identifier is notvalid.

• <V1> is the identifier that was supplied.


FPEC2164E THE * IN A RANGESPECIFICATION MUST BE THELAST CHARACTER SPECIFIED

ExplanationA generic value has been supplied for a range in anINCLUDE/EXCLUDE or GROUP/LIST specification. Thisgeneric value specifies multiple ranges, not a singlerange.

User responseEnsure that any generic value supplied for either arange from or a range to only has an asterisk (*) as thelast character in the ‘range from’ or ‘range to’ value.This ensures that the range specification only defines asingle range.

FPEC2165E VALUE <V1> SUPPLIED FOR A HEXVALUE IS THE WRONG LENGTH ORCONTAINS CHARACTERS OTHERTHAN 0-9 OR A-F

ExplanationAn identifier, the values of which should be supplied inan INCLUDE/EXCLUDE or GROUP/LIST specification ashexadecimal, has been supplied a value that is eithertoo long or has characters other than 0-9 or A-F.

• <V1> is the invalid hexadecimal value supplied.


FPEC2166E RANGE IS NOT PERMITTED FORIDENTIFIER <V1>

ExplanationA range specification for the shown identifier is notpossible. <V1> is the supplied include/excludeidentifier.

User responseChange the range specification to an enumeration ofvalues or use the asterisk to match multiple values.

FPEC2167E RANGE OPERATOR <V1> IS NOTVALID FOR IDENTIFIER <V2>

ExplanationThe numeric range operators 'GT', 'GE', 'LT', and 'LE' arenot valid for the specified OMEGAMON XE for DB2 PEidentifier. <V1> is the specified include/excludeidentifier.

User responseChange the specification. Use operator 'R' instead tospecify a range of values.

FPEC2201E RIGHT PARENTHESIS INSERTEDTO COMPLETE <V1>SUBCOMMAND


ExplanationA closing parenthesis was missing in a subcommand.

• <V1> is the subcommand where the parenthesis wasmissing.

User responseCorrect the input.

FPEC2202E THE <V1> SUBCOMMAND HASALREADY BEEN SPECIFIED <V2>TIMES FOR THIS COMMAND, THESPECIFICATION IS IGNORED

ExplanationThere are more than the maximum number ofoccurrences of a subcommand.

• <V1> is the subcommand in error.• <V2> is the maximum number of occurrences.


FPEC2203E <V1> SUBCOMMAND IS INVALIDFOR <V2>. INPUT IGNORED FROM<V1> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationThe subcommand is not available with the command.For example, the REDUCE subcommand is notavailable with the RECTRACE command. Input wasignored between the error and the next valid commandor subcommand.

• <V1> is the subcommand.• <V2> is the command.


FPEC2204E UNEXPECTED END OF FILEENCOUNTERED IN <V1>SUBCOMMAND

ExplanationThe end of the input file was encountered before theend of the command stream. This error is mostcommonly caused by a missing closing parenthesis atthe end of the command stream.

• <V1> is the subcommand where end of file wasencountered.


FPEC2205E INVALID INPUT ENCOUNTERED IN<V1> SUBCOMMAND. INPUTIGNORED FROM <V2> TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationA subcommand contains invalid input.

• <V1> is the subcommand that contains the error.• <V2> is the invalid input.


FPEC2206E <V1> IS AN UNRECOGNIZABLESUBCOMMAND KEYWORD. INPUTIGNORED FROM <V1> TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationAn unrecognizable keyword was encountered. Inputwas ignored between the error and the next validcommand or subcommand.

• <V1> is the text of the unrecognizable subcommandkeyword.


FPEC2301I RIGHT PARENTHESIS INSERTEDTO COMPLETE <V1> OPTION

ExplanationA closing parenthesis is missing.

• <V1> is the option where the parenthesis is missing.


FPEC2302E <V1> OPTION ALREADYSPECIFIED FOR THISSUBCOMMAND


ExplanationA subcommand option occurred more than once.

• <V1> is the repeated option.


FPEC2303E <V1> OPTION IS INVALID FOR<V2> <V3>. INPUT IGNOREDFROM <V1> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationYou cannot use the subcommand option in its currentcontext. For example, you cannot use ORDERsubcommand option with the STATISTICS commandand its REPORT subcommand.

• <V1> is the subcommand option.• <V2> is the command.• <V3> is the subcommand.


FPEC2304E UNEXPECTED END OF FILEENCOUNTERED IN <V1> OPTION

ExplanationThe end of the input file was encountered before theend of the command stream. This error is mostcommonly caused by a missing closing parenthesis atthe end of the command stream.

• <V1> is the option where end of file wasencountered.


FPEC2305E INVALID INPUT ENCOUNTERED IN<V1> OPTION. INPUT IGNOREDFROM <V2> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationThe syntax of an option is incorrect.

• <V1> is the name of the option.• <V2> is the invalid input.


FPEC2306E <V1> IS AN UNRECOGNIZABLEOPTION KEYWORD. INPUTIGNORED FROM <V1> TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationAn unrecognizable option keyword was encountered.Input was ignored between the unrecognizable inputand the next valid command, subcommand, or option.



FPEC2307E <V1> IS AN INVALID <V2>PARAMETER

ExplanationA keyword cannot be used in its current context. Forexample, DETAIL is not valid withRECTRACE(TRACE(LEVEL)).

• <V1> is the invalid keyword.• <V2> is the option that contains the invalid keyword.


FPEC2308E <V1> MAXIMUM SPECIFICATIONEXCEEDED, EXTRA PARAMETERSIGNORED

ExplanationThere are more values for an option than allowed. Forexample, you can only specify three values forREPORT(ORDER). The first three values are accepted,and any subsequent values are ignored.

• <V1> is the option containing a not valid number ofvalues.


FPEC2309E <V1> IS AN UNRECOGNIZABLELEVEL KEYWORD. INPUTIGNORED FROM <V1> TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD


ExplanationAn unrecognizable keyword was encountered in theLEVEL option of a REPORT or TRACE subcommand.Input between the error and the next valid command,subcommand, or option was ignored.



FPEC2310E DUPLICATE INPUT ENCOUNTEREDIN <V1> OPTION. INPUT IGNOREDFROM <V2> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationA duplicate option was specified, which is not allowed.Input is ignored between the error and the nextcommand, subcommand, or option. Note that AUTHIDand PRIMAUTH are treated as the same option. So arePACKAGE and PROGRAM. If both options are specified,they are duplicate.

• <V1> is the name of the option.• <V2> is the duplicate input.


FPEC2311E INVALID DATE SPECIFIED IN <V1>OPTION

ExplanationThe specified date is not valid. The date can be in theformat mm/dd/yy where mm is an integer in the range1 to 12, dd is an integer in the range 1 to 31 and validfor the month and year, and yy is an integer in therange 01 to 99. However, depending on theDATEFORMAT parameter, the date can also bespecified in a different format.

• <V1> is the option that contains the invalid date.


FPEC2312E INVALID TIME SPECIFIED IN <V1>OPTION

ExplanationThe specified time is not valid. The time must be in theformat hh:mm:ss.th where hh is an integer in the range

0 to 23, mm and ss are integers in the range 0 to 59,and th is an integer in the range 0 to 99. Trailing zeroscan be omitted.

• <V1> is the option that contains the invalid time.


FPEC2313E <V1> IS AN UNRECOGNIZABLETYPE KEYWORD. INPUT IGNOREDFROM <V1> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationThe keyword specified for TYPE cannot be recognized.

• <V1> is the unrecognized keyword.


FPEC2314I REQUESTTYPE IS TRANSLATEDINTO THE APPROPRIATE TYPE

ExplanationThe OMEGAMON XE for DB2 PE identifierREQUESTTYPE is no longer used and is thereforereplaced by its equivalent TYPE.

User responseYou might want to change the keyword REQUESTTYPEto TYPE and the type to its equivalent, for example,CLAIM to CLAIMREQ.

FPEC2315E INCLUDE/EXCLUDE(TYPE) ONTRACE LEVELS OTHER THANDETAIL IS NOT VALID

ExplanationThe INCLUDE⁄EXCLUDE(TYPE) parameter in acommand specification is not valid for a TRACE LEVELother than DETAIL.

User responseChange the TRACE LEVEL to DETAIL or remove theINCLUDE⁄EXCLUDE(TYPE) parameter.

FPEC2316I DUE TO THE EXCLUDESPECIFICATION ON TYPE THEINCLUDE(REQUESTTYPE) CANNOTBE TRANSLATED. THE


EXCLUDE(REQUESTTYPE) ISIGNORED

ExplanationBoth EXCLUDE(TYPE) and INCLUDE(REQUESTTYPE)were specified in a LOCKING TRACE command. TheEXCLUDE(TYPE) is executed andINCLUDE(REQUESTTYPE) is ignored.

User responseCorrect the specification.

FPEC2317I NOT ALL TYPES ARE APPLICABLETO THE <V1> SUBCOMMAND

ExplanationThe LOCKING command with subcommand <V1> andsubcommand option INCLUDE or EXCLUDE is used,however, for the OMEGAMON XE for DB2 PE identifierTYPE (used with INCLUDE or EXCLUDE) an event typeis specified that is not applicable with the <V1>subcommand.

• <V1> is the subcommand used with the LOCKINGcommand.

User responseSee the Report Command Reference for an explanationof OMEGAMON XE for DB2 PE identifiers andidentifiers used with the INCLUDE or EXCLUDEsubcommand option.

FPEC2318E TYPE IS NOT VALID FOR INCLUDEOR EXCLUDE WITHIN A LOCKINGREPORT

ExplanationINCLUDE⁄EXCLUDE(TYPE) was specified within aLOCKING REPORT command. This is not valid.

User responseRemove the INCLUDE⁄EXCLUDE specification for thiscommand.

FPEC2319I REQUESTTYPE IS NO LONGERSUPPORTED FOR INCLUDE OREXCLUDE WITHIN A LOCKINGREPORT. REQUESTTYPE OPTIONFOR INCLUDE/EXCLUDE ISIGNORED

ExplanationINCLUDE⁄EXCLUDE(REQUESTTYPE) was specifiedwithin a LOCKING REPORT command. This is no longersupported. The specification is ignored.

User responseNone. However, you may wish to remove theINCLUDE⁄EXCLUDE specification for this command.

FPEC2322I INCLUDE/EXCLUDE(REQUESTTYPE) ONTRACE LEVELS OTHER THANDETAIL IS IGNORED

ExplanationINCLUDE⁄EXCLUDE(REQUESTTYPE) was specifiedwithin a LOCKING TRACE command. This is no longersupported. The specification is ignored.

User responseNone. However, you may wish to remove theINCLUDE⁄EXCLUDE specification for this command orchange LEVEL to DETAIL.

FPEC2323I <V1> IS AN AMBIGUOUSABBREVIATION IN THISCONTEXT. <V2> IS ASSUMED

ExplanationThe abbreviated option or parameter <V1> is specifiedin SYSIN. However, <V1> is too short to beunambiguous and can match more than one possibleoption or parameter. <V2> is assumed for furtherprocessing.

User responseIf the assumed option or parameter is not correct,specify a longer abbreviation or the full name.

FPEC2341E DDNAME <V1> EXCEEDS 8CHARACTERS

ExplanationThe value specified for a ddname option contains morethan eight characters.




FPEC2342E LAYOUT <V1> EXCEEDS 8CHARACTERS

ExplanationThe value specified for the LAYOUT option containsmore than eight characters.

• <V1> is the LAYOUT.


FPEC2343E GROUP/LIST NAME <V1> EXCEEDS8 CHARACTERS

ExplanationThe value specified for the GROUP/LIST name containsmore than eight characters.

• <V1> is the LAYOUT.


FPEC2361E INVALID LEVEL PARMS FORREQUESTED FUNCTION

ExplanationThe value specified for LEVEL cannot be used in thecurrent context. For example,RECTRACE(LEVEL(DETAIL)) is not valid.


FPEC2371E INVALID TYPE PARMS FORREQUESTED FUNCTION

ExplanationThe value specified for TYPE cannot be used in thecurrent context. For example,TRANSIT(REPORT(TYPE(AUTHFAIL))) is not valid.


FPEC2401E INCLUDE/EXCLUDE FOR <V1>INVALID. INPUT IGNORED FROM<V1> TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationA keyword or value specified in INCLUDE/EXCLUDEcannot be used in the specified context. For example,you cannot use INCLUDE/EXCLUDE(IFCID) with theACCOUNTING command. Input is ignored between theinvalid keyword and the next valid command,subcommand, or option.

• <V1> is the keyword that cannot be used withINCLUDE/EXCLUDE.


FPEC2402E LOCATION IS NOT PERMITTEDFOR GROUP. INPUT IGNOREDFROM LOCATION TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationYou cannot use the LOCATION identifier with theGROUP command.


FPEC2403E GROUP COMMANDS CANNOTCONTAIN REFERENCES TO OTHERGROUP DEFINITIONS. INPUTIGNORED FROM G TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationA group cannot contain a group.


FPEC2404E REQLOC IS NOT PERMITTED FORGROUP. INPUT IGNORED FROMREQLOC TO NEXT COMMAND,SUBCOMMAND, OR OPTIONKEYWORD

ExplanationYou cannot use the REQLOC identifier with the GROUPcommand.



FPEC2405E <V1> SPECIFICATION HAS NOASSOCIATED VALUES.SPECIFICATION REJECTED

ExplanationNo values were supplied for the GROUP or LISTspecification.

• <V1> is GROUP or LIST.


FPEC2501E INVALID TIMEZONE PARAMETER

ExplanationThe value specified for TIMEZONE is not valid. Specifythe time adjustment in the form +hh:mm or -hh:mm,where hh is an integer in the range 0 to 23, and mm isan integer in the range 0 to 59. Trailing zeros can beomitted.


FPEC2502E INVALID PAGESIZE PARAMETER

ExplanationThe value specified for PAGESIZE is not valid. Specifyan integer in the range 50 to 999.


FPEC2503E <V1> OPTION ALREADYSPECIFIED FOR GLOBAL

ExplanationAn option keyword was specified twice in the GLOBALcommand.

• <V1> is the keyword that was specified twice.

Note that GLOBAL(DB2ID(XXXX)) is interpreted asGLOBAL(INCLUDE(DB2ID(XXXX))).


FPEC2504I RECHOLD OPTION IS OBSOLETEAND IS IGNORED

ExplanationNone.

User responseNone.

FPEC2505E <V1> IS AN INVALID DB2ID

ExplanationThe value specified for DB2ID is not valid.

• <V1> is the invalid value.


FPEC2506E <V1> IS AN INVALID LOCATION

ExplanationThe value specified for LOCATION is not valid.



FPEC2508E NO TIMEZONE PARAMETERSAVAILABLE FOR <V1>

ExplanationA location has been specified with the TIMEZONEoption that is not listed in the LOCDATA member ofDPMPARMS.

• <V1> is the invalid location.

User responseSpecify a valid location with TIMEZONE, or add thespecified location to LOCDATA.

FPEC2509E <V1> IS AN UNRECOGNIZEDPRESORTED KEYWORD. INPUTIGNORED FROM <V1> TO NEXTCOMMAND KEYWORD

ExplanationAn invalid parameter was supplied with PRESORTEDoption.

• <V1> is the invalid keyword.


User responseSpecify a valid keyword with PRESORTED option.

FPEC2510I GLOBAL LOCATION/DB2IDOPTION NO LONGER SUPPORTED.MAKE AN APPROPRIATE GLOBALINCLUDE SPECIFICATION.SPECIFICATION IGNORED

ExplanationThe GLOBAL LOCATION and GLOBAL DB2ID optionsare not supported in this version.


FPEC2511E <V1> IS AN UNRECOGNIZEDSPANINC KEYWORD. INPUTIGNORED FROM <V1> TO NEXTCOMMAND KEYWORD

ExplanationAn invalid keyword was supplied with the SPANINCsubcommand. <V1> is the invalid keyword.

User responseSpecify a valid keyword with SPANINC subcommand.

FPEC2513I OPTION DSETSTAT IS NO LONGERSUPPORTED FOR STATISTICS<V1> SUBCOMMAND INCONJUNCTION WITH OPTIONINTERVAL(X), X > 0. OPTIONDSETSTAT IS IGNORED.

ExplanationStatistics interval processing with intervals > 0 canonly be applied to IFCIDs 1, 2, 225 and 369 that areexternalized by DB2 every minute. IFCID 199externalization is controlled by system parameterSTATIME and may range from 1 to 60 minutes. <V1> isthe REPORT or SAVE command.

User responseRemove the DSETSTAT option from the subcommand.

FPEC2555E LEVEL OPTION HAS BEENSPECIFIED WITH LAYOUT,SORTBY, SUMMARIZEBY, ORWORKLOAD. POTENTIALLYAMBIGUOUS SPECIFICATIONREJECTED

ExplanationThe old LEVEL option is internally translated intoLAYOUT, SORTBY, SUMMARIZEBY, or WORKLOADspecifications as appropriate. If LEVEL is supplied withany of these options, the specification is rejected.


FPEC2602E RANGE TO VALUE IS GREATERTHAN RANGE FROM VALUE

ExplanationA range specified in INCLUDE or EXCLUDE is not valid.


FPEC2603E GROUP/LIST BY <V1> INVALID.INPUT IGNORED FROM <V2> TONEXT COMMAND, SUBCOMMAND,OR OPTION KEYWORD

ExplanationThe identifiers shown are not valid with GROUP orLIST.

• <V1> is the identifier.• <V2> is the next identifier.


FPEC2604E <V1> PREVIOUSLY SPECIFIEDFOR INCLUDE/EXCLUDE. INPUTIGNORED FROM <V1> TO NEXTCOMMAND, SUBCOMMAND, OROPTION KEYWORD

ExplanationThe same identifier keyword was used more than oncewith INCLUDE or EXCLUDE. A keyword can be usedonce in either INCLUDE or EXCLUDE.

• <V1> is the identifier.


FPEC2701E <V1> OPTION ALREADYSPECIFIED FOR <V2> COMMAND


ExplanationAn option keyword cannot be used in its currentcontext. It has already been used with this command.

• <V1> is the duplicated option keyword.• <V2> is the command that contains the duplicated

keyword.


FPEC2702E OPTION <V1> MISSING IN <V2>COMMAND

ExplanationA required option has not been specified with thiscommand.

• <V1> is the required option.• <V2> is the command in which the option is missing.


FPEC2703E <V1> OPTION INVALID FOR <V2>COMMAND

ExplanationAn option keyword cannot be used with this command.For example, RECTRACE(TRACE(TYPE)).

• <V1> is the invalid option keyword.• <V2> is the command that contains the invalid

keyword.


FPEC2704I <V1> IS NOT AVAILABLE TO <V2>.INPUTDD IS ASSUMED

ExplanationA not valid ddname was specified on the EXEC optionof the DUMP or TAPECOPY command. INPUTDD is theonly valid ddname for the EXEC option. The commandis processed using INPUTDD.

• <V1> is the invalid ddname.• <V2> is DUMP or TAPECOPY.

User responseSpecify INPUTDD on the EXEC option, or do notspecify the EXEC option.

FPEC2750I ORDER OPTION NO LONGERAVAILABLE FOR SQL ACTIVITY

ExplanationThe SQLTRACE ORDER is no longer supported and hasbeen ignored.


FPEC2851I OBSOLETE TYPE FOUND, TYPEIGNORED

ExplanationCOMMAND, SQL, and UNASSIGNED are obsoletetypes, but one of these was entered.

User responseEnter a valid type.

FPEC2860E <V1> IS AN UNRECOGNIZABLESORTBY PARAMETER. INPUTIGNORED FROM <V1> TO NEXTCOMMAND KEYWORD

ExplanationAn unrecognizable SORTBY parameter has beensupplied.

• <V1> is the unrecognizable SORTBY parameter.


FPEC2861E <V1> IS AN INVALID SORTBYPARAMETER FOR THIS COMMAND.INPUT IGNORED FROM <V1> TONEXT COMMAND, SUBCOMMAND,OR OPTION KEYWORD

ExplanationThe SORTBY parameter supplied is not valid for thiscommand.

• <V1> is the unrecognizable SORTBY parameter.



FPEC2862E <V1> IS AN UNRECOGNIZABLESUMMARIZEBY PARAMETER.INPUT IGNORED FROM <V1> TONEXT COMMAND KEYWORD

ExplanationAn unrecognizable SUMMARIZEBY parameter hasbeen supplied.

• <V1> is the unrecognizable SUMMARIZEBYparameter.


FPEC2864I LAYOUT <V1> SUPPLIED ISLONGER THAN SIX CHARACTERS.OPTION IGNORED

ExplanationThe LAYOUT parameter supplied is too long.

• <V1> is the LAYOUT parameter supplied.


FPEC2865E <V1> IS AN UNRECOGNIZABLEWORKLOAD PARAMETER. INPUTIGNORED FROM <V1> TO NEXTCOMMAND KEYWORD

ExplanationAn unrecognizable WORKLOAD parameter has beensupplied.

• <V1> is the unrecognizable WORKLOAD parameter.


FPEC2866E NONE SPECIFICATION FORWORKLOAD CONFLICTS WITHOTHER WORKLOAD PARAMETERS.WORKLOAD SPECIFICATIONREJECTED

ExplanationWORKLOAD (NONE) has been supplied with anotherWORKLOAD parameter. This ambiguous specificationis rejected.

User responseCorrect the WORKLOAD option and rerun the job.

FPEC2867I LEVEL SPECIFICATION FORACCOUNTING SUPERSEDED INTHIS RELEASE BY THE LAYOUT,EXCEPTION/NOEXCEPTION, ANDMERGE/NOMERGE OPTIONS

ExplanationThe LEVEL option of the ACCOUNTING command hasbeen replaced by the other options shown.

User responseCorrect the input as required.

FPEC2868I LEVEL SPECIFICATION FORSTATISTICS SUPERSEDED IN THISRELEASE BY THE LAYOUT ANDEXCEPTION/NOEXCEPTIONOPTIONS

ExplanationThe LEVEL option of the STATISTICS command hasbeen replaced by the other options shown.


FPEC2869I LEVEL SPECIFICATION FORSQLACTIVITY SUPERSEDED INTHIS RELEASE BY THESUMMARIZEBY AND WORKLOADOPTIONS

ExplanationThe LEVEL option of the SQLACTIVITY command hasbeen replaced by the other options shown.


FPEC2870I SUMMARIZEBY(OCCURRENCE) INREPORT WOULD PROVIDEEXCESSIVE DETAIL.SPECIFICATION IGNORED

ExplanationThe use of SUMMARIZEBY by OCCURRENCE inREPORT is considered excessive.



FPEC2871E SCOPE PARAMETER <V1>SUPPLIED IS INVALID.SPECIFICATION REJECTED

ExplanationAn invalid parameter was passed for the SCOPEoption.

• <V1> is the invalid parameter.

Valid options are MEMBER or GROUP.

User responseCorrect the input and rerun the job. For furtherinformation, see the Report Command Reference.

FPEC2872E SORT FIELD <V1> IS INVALIDBECAUSE A SORT FIELDIDENTIFIER HAS ALREADY BEENSPECIFIED

ExplanationA sort field has already been specified with theSORTBY option of the ORDER parameter. Only one sortfield is allowed. <V1> is the redundant sort field.

User responseRemove redundant sort field specifications from theBPACTIVITY command.

FPEC2873E IDENTIFIER <V1> IS NOTALLOWED. A SORT FIELDIDENTIFIER HAS ALREADY BEENSPECIFIED. THE SORT FIELD HASTO BE THE LAST PARAMETER INTHE SORTBY OPTION.

ExplanationThe specified identifier is not valid because a sort fieldhas already been specified. The sort field is always thelast value specified with the SORTBY option.

User responseCorrect the SORTBY option of the BPACTIVITYcommand so that the order identifiers are listed firstand the sort field is the last value.

FPEC2874E SORTBY IDENTIFIER <V1>EXCEEDS MAXIMUM COUNT OFIDENTIFIERS. COUNT OFIDENTIFIERS IN SORTBY OPTION

MUST BE LESS THAN THE COUNTOF IDENTIFIERS IN ORDEROPTION.

ExplanationYou cannot specify more SORTBY identifiers than thenumber of identifiers specified for the ORDER option.

User responseCorrect the SORTBY option so that it contains feweridentifiers than the ORDER option.

FPEC2875E SORTBY IDENTIFIER <V1> DOESNOT MATCH IDENTIFIER <V2> ATTHE MATCHING POSITION OF THEORDER OPTION.

ExplanationSpecified SORTBY identifiers must match the specifiedidentifiers for the ORDER option. <V1> is the specifiedSORTBY identifier, <V2> is the specified ORDERidentifier at the same position.

User responseCorrect the identifiers for the SORTBY option to matchthe identifiers for the ORDER option.

FPEC2876E SORT FIELD IDENTIFIER <V1> ISNOT ALLOWED FOR LEVEL (<V2>).

ExplanationSort fields cannot be specified for all levels ofreporting. The specified identifier is not valid for thisreport level. <V1> is the sort field specified with theSORTBY option, <V2> is the report level specified withthe LEVEL option.

User responseCorrect the SORTBY option and use a supported sortfield for the selected LEVEL.

FPEC2877E ORDER PARAMETER MUST BEBPID-QPAGESET FORLEVEL(SUMMARY)

ExplanationFor summary reports only ORDER parameter BPID-PAGESET is allowed.

User responseCorrect the ORDER parameter.


FPEC2878E NO SORT FIELD PARAMETERSPECIFIED WITH THE SORTBYOPTION. THE LAST PARAMETERIN THE SORTBY OPTION MUST BEA SORT FIELD.

ExplanationNo sort field was specified with the SORTBY option.

User responseCorrect the SORTBY option.

FPEC2879E The REPORT subcommand mustbe used with theLEVEL(SUMMARY) option if FILELEVEL(SUMMARY) is also specified

ExplanationFILE LEVEL(SUMMARY) results in detailed data beingremoved from the input stream. Detail data is requiredby the REPORT subcommand if LEVEL(DETAIL) isspecified or if the LEVEL option is not specified,because DETAIL is the default value. Therefore thesecombinations are not supported.


FPEC2902E INVALID DELIMITER FOUND INFIELD COMMAND

ExplanationThe delimiter used in the FIELD command is not valid.


FPEC2908E END OF FILE ENCOUNTEREDREADING SQL STATEMENT.ENSURE THAT STATEMENT ISTERMINATED BY ";"

ExplanationAn SQL statement was not terminated with asemicolon (;).


FPEC2909E SQL STATEMENT SUPPLIEDEXCEEDS 32700 BYTES.STATEMENT TRUNCATED

ExplanationSQL statements that exceed 32700 bytes aretruncated. Truncated SQL statements most likelycause processing errors.

User responseUse an SQL statement that does not exceed 32700bytes and rerun the job.

FPEC2910E INVALID INPUT <V1> IN EXPLAIN<V2> COMMAND

ExplanationThe value supplied in the EXPLAIN command is notvalid.

• <V1> is the invalid input.• <V2> is one of the EXPLAIN keywords:

– PLAN– PACKAGE– QMFQUERY– QUERYNO– SQLSTATEMENT.


FPEC2911E UNEXPECTED END OF FILEENCOUNTERED IN EXPLAINCOMMAND

ExplanationThe specified EXPLAIN command is not complete.

User responseComplete the EXPLAIN command specification. Seethe Report Command Reference for EXPLAIN syntaxdiagrams.

FPEC2912E UNEXPECTED KEYWORDFOLLOWS EXPLAIN. PLAN,PACKAGE, QMFQUERY, QUERYNO,OR SQLSTATEMENT EXPECTED

ExplanationThe supplied EXPLAIN keyword is not valid.


User responseCorrect the input. Valid keywords are:

• PLAN• PACKAGE• QMFQUERY• QUERYNO• SQLSTATEMENT.

FPEC2913E PLAN NAME EXPECTED BUT <V1>ENCOUNTERED

ExplanationAn invalid plan name was supplied.

• <V1> is the invalid plan name.

User responseEnter a valid plan name.

FPEC2914E PLANNAME PARAMETER <V1>SUPPLIED IS TOO LONG

Explanation<V1> is the invalid plan name parameter.

The length of this value must not exceed 8 characters.

User responseSpecify a value with a maximum length of 8characters.

FPEC2915E PACKAGE EXPECTED BUT <V1>ENCOUNTERED

ExplanationAn invalid package was supplied.

• <V1> is the invalid package.

User responseEnter a valid package.

FPEC2916E QUERY NUMBER EXPECTED BUT<V1> ENCOUNTERED

ExplanationA not valid query number was supplied.

• <V1> is the invalid query number.

User responseEnter a valid query number.

FPEC2917E SQL STATEMENT EXPECTED BUT<V1> ENCOUNTERED

ExplanationA not valid SQL statement was supplied.

• <V1> is the invalid string supplied.

User responseEnter a valid SQL statement.

FPEC2918E EXPLAIN <V1> OPTION <V2>ALREADY SPECIFIED

Explanation• <V1> is the EXPLAIN keyword.• <V2> is the option.

In the list of options, <V2> is detected two or moretimes, however, this option can be specified only once.

User responseRemove all specifications of option <V2> except forone.

FPEC2919E OPTION <V1> NOT VALID FOREXPLAIN <V2>

ExplanationA not valid option was supplied with the EXPLAINkeyword.

• <V1> is the invalid option.• <V2> is the EXPLAIN keyword.


FPEC2920E BOTH COLLECTION AND PACKAGEID MUST BE SUPPLIED FOR ANEXPLAIN PACKAGE REQUEST

ExplanationNone.

User responseSpecify a collection ID and a package ID for theEXPLAIN PACKAGE specification.


FPEC2921E ONE OR MORE OF THECOMPONENTS OF THE PACKAGESPECIFICATION EXCEED THEPERMITTED MAXIMUM

ExplanationFor the parameters Location, Collection.andPackage_ID, the maximum length is 18 characters. Forthe parameter Package_Version_ID, the maximumlength is 39 characters.

User responseSpecify values within the limit for the maximum length.

FPEC2922E QUERY NUMBER <V1> SUPPLIEDIS TOO BIG

ExplanationThe query number supplied is longer than 10characters. Such a number cannot identify aPLAN_TABLE row.

• <V1> is the query number supplied.


FPEC2940E ACCTYPE PARAMETER <V1>SUPPLIED IS INVALID. VALIDACCTYPE VALUES ARE: ALL,MATCHING, NONMATCH, ORTABSCAN

ExplanationNone.

• <V1> is the invalid ACCTYPE parameter supplied.

User responseEnter a valid ACCTYPE parameter.

FPEC2941E THE SPECIFIED VALUE <V1> FORTHE DBRM PARAMETER IS TOOLONG.

Explanation<V1> is the invalid value for the DBRM parameter. Thisvalue must not exceed 8 characters.


FPEC2942E THE SPECIFIED VALUE <V1> FORTHE DBRM PARAMETER ISINVALID.

Explanation<V1> is the invalid value for the DBRM parameter. Thisvalue must be alphabetic.

User responseSpecify an alphabetic value for the DBRM parameter.

FPEC2943E FORCE PARAMETER <V1>SUPPLIED IS INVALID. VALIDFORCE VALUES ARE: YES OR NO

ExplanationNone.

• <V1> is the invalid FORCE parameter.

User responseEnter YES or NO.

FPEC2944E FIRST PARAMETER <V1>SUPPLIED IS INVALID. FIRSTPARAMETER MUST BE NUMERICIN THE RANGE 0 - 9999999

ExplanationNone.

• <V1> is the invalid FIRST parameter.

User responseEnter a value in the range 0 to 9 999 999.

FPEC2945E FORMAT PARAMETER <V1>SUPPLIED IS INVALID. VALIDFORMAT VALUES ARE: YES OR NO

Explanation<V1> is the invalid FORMAT parameter.


FPEC2946E GEN PARAMETER <V1> SUPPLIEDIS INVALID. GEN MUST BENUMERIC IN THE RANGE 1 - 99

Explanation<V1> is the invalid GEN parameter.


User responseEnter a value in the range 1 to 99.

FPEC2947E HOSTVAR PARAMETER <V1>SUPPLIED IS INVALID. VALIDHOSTVAR VALUES ARE: YES ORNO

Explanation<V1> is the invalid HOSTVAR parameter.


FPEC2948E SSID PARAMETER <V1> SUPPLIEDIS TOO LONG

Explanation<V1> is the invalid value for the SSID parameter. Thisvalue must not exceed 4 characters.


FPEC2949E INDEXES PARAMETER <V1>SUPPLIED IS INVALID. VALIDINDEXES VALUES ARE: ALL, YES,OR NO

ExplanationNone.

• <V1> is the invalid INDEXES parameter.

User responseEnter ALL, YES, or NO.

FPEC2950E LAST PARAMETER <V1> SUPPLIEDIS INVALID. LAST PARAMETERMUST BE NUMERIC IN THE RANGE0 - 9999999

ExplanationNone.

• <V1> is the invalid LAST parameter.

User responseEnter a value in the range 0 to 9 999 999.

FPEC2951E LOCATION PARAMETER <V1>SUPPLIED IS INVALID. LOCATIONVALUE MUST BE ALPHABETIC

ExplanationNone.

• <V1> is the invalid LOCATION parameter.


FPEC2952E LOCATION PARAMETER <V1>SUPPLIED IS TOO LONG

Explanation<V1> is the invalid value for the LOCATION parameter.This value must not exceed 16 characters.


FPEC2953E LEVEL PARAMETER <V1>SUPPLIED IS INVALID. VALIDLEVEL VALUES ARE: DETAIL,BASIC, INDEXES, KEYDIST, SQL,SUMMARY, OR NORAWXPL

ExplanationNone.

• <V1> is the invalid LEVEL parameter.

User responseEnter one of the valid LEVEL parameters listed in themessage.

FPEC2954E PACKAGES PARAMETER <V1>SUPPLIED IS INVALID. VALIDPACKAGES ARE: ALL, YES, OR NO

ExplanationNone.

• <V1> is the invalid PACKAGES parameter.

User responseEnter ALL, YES, or NO.

FPEC2955E SQLID PARAMETER <V1>SUPPLIED IS INVALID. SQLIDVALUE MUST BE ALPHABETIC


ExplanationNone.

• <V1> is the invalid SQLID parameter.


FPEC2956E SQLID PARAMETER <V1>SUPPLIED IS TOO LONG

Explanation<V1> is the invalid value for the SQLID parameter. Thisvalue must not exceed 8 characters.


FPEC2957E PLANNAME PARAMETER <V1>SUPPLIED IS INVALID.PLANNAME VALUE MUST BEALPHABETIC

ExplanationNone.

• <V1> is the invalid PLANNAME parameter.


FPEC2958E PLANNAME PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationNone.

• <V1> is the invalid PLANNAME parameter.


FPEC2959E AUTHID PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationNone.

• <V1> is the invalid AUTHID parameter.


FPEC2960E TABLE PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationNone.

• <V1> is the invalid TABLE parameter.


FPEC2961E OWNER PARAMETER <V1>SUPPLIED IS INVALID. OWNERVALUE MUST BE ALPHABETIC

ExplanationA not valid OWNER parameter was specified.

• <V1> is the OWNER parameter supplied.


FPEC2962E OWNER PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationNone.

• <V1> is the OWNER parameter supplied.


FPEC2963E PACKLIMIT PARAMETER <V1>SUPPLIED IS INVALID.PACKLIMIT VALUE MUST BENUMERIC IN THE RANGE 0 TO99999

ExplanationAn invalid PACKLIMIT parameter was specified.

• <V1> is the PACKLIMIT parameter supplied.

User responseSpecify a value from 0 through 99 999 for thePACKLIMIT parameter.


FPEC2964E DEGREE PARAMETER <V1>SUPPLIED IS INVALID. VALIDDEGREE VALUES ARE: ANY, DSJ,ESJ, OR 1

ExplanationA not valid DEGREE parameter was supplied.

• <V1> is the DEGREE parameter supplied.

User responseCorrect the input by supplying one of the listed valuesand rerun the job.

FPEC2965E INDATABASE PARAMETER <V1>SUPPLIED IS INVALID.INDATABASE VALUE MUST BEALPHABETIC

ExplanationA not valid INDATABASE parameter was supplied.

• <V1> is the invalid INDATABASE parameter supplied.


FPEC2966E INDATABASE PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationThe INDATABASE parameter supplied exceeds themaximum allowable length of 18 characters.

• <V1> is the invalid INDATABASE parameter supplied.


FPEC2967E KEYDICTIONARY PARAMETER<V1> SUPPLIED IS INVALID.VALID KEYDICTIONARY VALUESARE: YES OR NO

ExplanationNone.

• <V1> is the invalid KEYDICTIONARY parametersupplied.

User responseEnter YES or NO, respectively Y or N.

FPEC2968E REPLACE PARAMETER <V1>SUPPLIED IS INVALID. VALIDREPLACE VALUES ARE: YES OR NO

ExplanationNone.

• <V1> is the invalid REPLACE parameter supplied.

User responseEnter YES or NO, respectively Y or N.

FPEC2969E DATABASE PARAMETER <V1>SUPPLIED IS TOO LONG

ExplanationThe DATABASE parameter supplied exceeds themaximum allowable length of 18 characters.

• <V1> is the invalid DATABASE parameter supplied.


FPEC2990I PARM SPECIFICATION OBSOLETEIN THIS RELEASE.SPECIFICATION IGNORED

ExplanationThe PARM command is no longer used.

User responseNone.

FPEC3001E ERROR INITIALIZINGCORRELATION PROCESSING

ExplanationAn error was found in the correlation translation dataset.


FPEC3011E <V1> <V2> FROM DATE/TIME ISEQUAL TO OR LATER THAN TODATE/TIME

ExplanationThe specified FROM date and time is equal to or laterthan the TO date and time.


• <V1> is the command that contains the error.• <V2> is the subcommand that contains the error.


FPEC3012E REQUESTED FUNCTIONALSPECIFICATION FOR <V1> ISIMPROPER

ExplanationThe combination of commands would not give a result.There are probably commands missing from the input,or an improper subcommand combination has beenspecified.

• <V1> is the command containing the combination.


FPEC3014E SAVE REQUESTED FOR <V1> HASBEEN CANCELED BECAUSE NOREDUCE WAS REQUESTED

ExplanationA SAVE subcommand was not processed becausethere was no new data to save. This message is printedif there are only RESTORE, REPORT, and SAVEsubcommands in the command stream.

• <V1> is the command that contains the SAVEsubcommand.


FPEC3017E DATA FROM RESTORE DDNAME<V1> IS FOR <V3>. <V2> DATA ISEXPECTED

ExplanationThe data in the restore data set is not from the reportset being processed. For example, the command beingprocessed is ACCOUNTING(RESTORE), and the restoredata set contains statistics data.

• <V1> is the ddname for the restore data.• <V2> is the name of the report set being processed.• <V3> is the report set to which the data belongs.


FPEC3018E <V1> DATA HAS WRONG PRODUCTVERSION. MIGRATION REQUIREDBEFORE USE

ExplanationThe data in the restore data set is not compatible withthis release. Data from earlier versions must bemigrated before being restored.

• <V1> is the ddname for the restore data.

User responseUse the save-file utility MIGRATE function to changethe data to the correct format.

FPEC3019I <V1> RESTORE DATA BOUNDARYDIFFERENT TO REDUCE. <V2>REDUCE BOUNDARY SET TO <V3>

ExplanationThe boundary used to reduce the data in the restoredata set was different to the REDUCE(BOUNDARY)specification in the job stream. When combiningrestored data and newly reduced data, the boundary ofrestored data must be the same as newly reduceddata. The REDUCE(BOUNDARY) is adjusted to matchthe boundary of the restored data, and processingcontinues.

• <V1> is the ddname for the restore data.• <V2> is the report set containing the incorrect

setting for BOUNDARY.• <V3> is the adjusted value for REDUCE(BOUNDARY).

User responseCorrect the input if required.

FPEC3020I <V1> RESTORE DATA INTERVALDIFFERENT TO REDUCE. <V2>REDUCE INTERVAL SET TO <V3>

ExplanationThe interval used to reduce the data in the restore dataset was different to the REDUCE(INTERVAL)specification in the job stream. When combiningrestored data and newly reduced data, the interval ofrestored data must be the same as newly reduceddata. The REDUCE(INTERVAL) is adjusted to match theboundary of the restored data, and processingcontinues.

• <V1> is the ddname for the restore data.• <V2> is the report set containing the incorrect

setting for INTERVAL.


• <V3> is the adjusted value for REDUCE(INTERVAL).

User responseCorrect the input if required.

FPEC3021E <V1> <V2> TO TIME CANNOT BE00:00:00.00

Explanation00:00:00.00 is a not valid TO time.

• <V1> is the command that contains the invalid time.• <V2> is the subcommand that contains the invalid

time.


FPEC3022E DATA FROM DDNAME <V1> IS NOTRECOGNIZED

ExplanationThe data in the restore data set is unrecognizable.

• <V1> is the ddname for the restore data.

User responseSupply the correct file or an empty file for the specifiedddname, and rerun the job.

FPEC3026I <V1> REPORT COMMANDREQUIRES MERGE DATA. MERGEOPTION SET ON FOR REDUCE

ExplanationREDUCE(MERGE) was automatically set on.

• <V1> is the report set command.

User responseNone.

FPEC3027I <V1> SAVE REQUESTED ANDRESTORE FILE CONTAINS MERGEDATA. MERGE OPTION SET ONFOR REDUCE

ExplanationThe Save data set contains merged data. The MERGEoption was automatically set on for REDUCE tomaintain a complete set of merged data in the Savedata set.


User responseNone.

FPEC3028E <V1> RESTORE FILE DOES NOTCONTAIN MERGE DATA REQUIREDFOR REPORT COMMAND

ExplanationThe report cannot be generated from the restored file.


User responseSpecify MERGE in the REDUCE subcommand andreduce the data again.

FPEC3029I SYSPRMDD REPLACEMENTSPECIFIED IN GLOBAL BUT NO DDSTATEMENT FOR <V1> SUPPLIED

ExplanationThe GLOBAL SYSPRMDD option has been supplied tooverride the System Parameters report ddname, butthe ddname supplied has not been specified in theJCL.

• <V1> is the overriding ddname supplied.

User responseCorrect the JCL as required.

FPEC3030E SYSPRMDD OPTION IN GLOBALCOMMAND IS INVALID WHENSYSPARMS COMMAND IS USED

ExplanationWhen the new SYSPARMS command is used to requesta system parameters trace or execute a file operation,the GLOBAL option SYSPRMDD is no longer allowed toredefine the ddname for the system parameters trace.

User responseRemove the SYSPRMDD option from the GLOBALcommand if you use the SYSPARMS command. Torequest a system parameters trace, use the SYSPARMSTRACE command with the appropriate ddname.

FPEC3031E SYSTEM PARAMETERS DDNAME<V1> IS INVALID WHENSYSPARMS COMMAND IS USED


ExplanationIn the past, the system parameters ddname statement(or its equivalent specified via GLOBALSYSPRMDD(newdd)) was used to request a systemparameters trace in batch reports. Now you canachieve the same by using the new SYSPARMScommand with its TRACE option. If you use this newcommand, you can no longer use the old systemparameters ddname statement in the same JCL step.You must decide for either the SYSPARMS command orthe system parameters ddname statement.

• <V1> is the system parameters ddname you havespecified in your JCL.

User responseRemove the SYSPRMDD line and, if specified, theGLOBAL option SYSPRMDD from your JCL and use theSYSPARMS TRACE command instead.

FPEC3032I <V1> SHOULD NO LONGER BEUSED. USE THE SYSPARMS TRACECOMMAND INSTEAD

ExplanationThis message is displayed when your JCL contains asystem parameters ddname statement (or anequivalent command renamed by the GLOBAL optionSYSPRMDD) to start a system parameters trace. Usethe SYSPARMS with the trace TRACE option.

• <V1> is the system parameters ddname you havespecified in your JCL.

User responseNone, but you should remove the SYSPRMDD line and,if specified, the GLOBAL option SYSPRMDD from yourJCL and use the SYSPARMS TRACE command instead.

FPEC3033W DISTDD OPTION IN GLOBALCOMMAND IS NO LONGERSUPPORTED. OPTION WILL BEIGNORED DURING GLOBALCOMMAND PROCESSING.

Explanation:The option DISTDD is no longer used in the GLOBALcommand.

User response:None.

FPEC3034E USAGE OF SYTRCDD1 NOTALLOWED IN SYSPRMDD GLOBALOPTION

ExplanationSYTRCDD1 is a reserved name for the SYSPARMScommand. It cannot be used in the SYSPRMDDGLOBAL option.

User responseCorrect your input JCL. Either use another ddname inGLOBAL SYSPRMDD or use the SYSPARMS command(preferably).

FPEC3151E <V1> REFERENCE <V2> FOR <V3>CANNOT BE FOUND

ExplanationThe GROUP or LIST reference indicated for theidentifier shown has not been supplied.

• <V1> is GROUP or LIST.• <V2> is the GROUP or LIST name.• <V3> is the identifier.


FPEC3152E NESTING LEVEL OF GROUPS/LISTS WITHIN AN INCLUDE/EXCLUDE HAS EXCEEDED <V1>

ExplanationThere are too many GROUP or LIST specificationswithin an INCLUDE or EXCLUDE specification.


FPEC3153E CIRCULAR REFERENCE ORMULTIPLE REFERENCE TO <V1><V2> <V3> WITHIN INCLUDE/EXCLUDE SPECIFICATION FOR<V4> <V5> NUMBER <V6>

ExplanationA GROUP or a LIST definition contains a reference toitself.

• <V1> is the identifier.• <V2> is GROUP or LIST.• <V3> is the GROUP or LIST name.• <V4> is the report set command where the circular

reference was detected.


• <V5> is the function where the circular referencewas detected.

• <V6> is the number, for example 2, of the 2nd suchfunction in the report set command specified.


FPEC3154E FIELD REFERENCE <V1> CANNOTBE FOUND

ExplanationThe field reference indicated cannot be found.

• <V1> is the field reference.


FPEC3155E CIRCULAR REFERENCE ORMULTIPLE REFERENCE TO <V1><V2> <V3> WITHIN GLOBALINCLUDE/EXCLUDESPECIFICATION

ExplanationA GROUP or LIST reference within a GLOBAL INCLUDE/EXCLUDE specification contains a reference to itself.

• <V1> is the identifier.• <V2> is GROUP or LIST.• <V3> is the GROUP or LIST name.


FPEC4000E RECORD PROCESSING PHASEHAS BEEN UNSUCCESSFUL

ExplanationThe record processing phase did not complete itsfunction successfully.

User responseCheck for messages detailing the problem.

FPEC4001E RECORD PROCESSINGINITIALIZATION FAILED FOR<V1>

ExplanationThe initialization of record processing failed for thespecified report set.

• <V1> is the name of the report set.


FPEC4002E <V1> FAILED DURING THERECORD PROCESSING PHASE

ExplanationThe record processing phase of the specified reportset failed. Processing terminates at the end of therecord processing phase or after the record processingphases of other report set specifications, if present inthe job.


User responseCheck for messages detailing the problem. If theproblem recurs, contact IBM support.

FPEC4004E INVALID RDW FOUND IN RECORD<F1>. PROCESSING TERMINATED

ExplanationThe record processing terminated because invalidinput record with RDW=0 was encountered.

• <F1> is the number of the invalid input record.

User responseTry to copy input data set with invalid RDWencountered to another data set. It should fix theproblem.

FPEC4003I RECORD PROCESSINGTERMINATION FAILED FOR <V1>

ExplanationThe termination of record processing failed for thespecified report set. Processing continues.



FPEC4005I NUMBER OF RECORDSPROCESSED WITHOUT A CPUHEADER WAS <V1>


ExplanationThe DB2 CPU header was not present in some (or all)input records. TCB times cannot be calculated withoutthe CPU header.

• <V1> is the number of records where the CPUheader was expected but not present.


User responseThe CPU header is written by DB2 when it generatesthe instrumentation data. Ensure that the CPU headeris requested in the START TRACE command. See thedescription of the DB2 START TRACE command in theReporting User’s Guide for more information aboutwhen the CPU header is required.

FPEC4010I NUMBER OF RECORDSPROCESSED WITHOUT ACORRELATION HEADER WAS <V1>

ExplanationThe DB2 correlation header was not present in some(or all) input records. DB2 cannot obtain thecorrelation ID and other information when thecorrelation header is not present.

• <V1> is the number of records that did not have acorrelation header.


User responseThe correlation header is written by DB2 when itgenerates the instrumentation data. Ensure that thecorrelation header is requested in the DB2 STARTTRACE command. See the Report Reference for moreinformation about when the correlation header isrequired.

FPEC4015I NUMBER OF RECORDS FROMUNSUPPORTED RELEASES OF DB2WAS <V1>

ExplanationThe input data contained instrumentation data from aDB2 version that is not supported by this product.

• <V1> is the number of instrumentation records thatwere discarded.

User responseNone.

FPEC4020I NUMBER OF RECORDS FROMUNSUPPORTED PRODUCTRELEASES WAS <V1>

ExplanationThe input data contained data from other OMEGAMONXE for DB2 PE or OMEGAMON XE for DB2 PM versionsthat could not be processed.

• <V1> is the number of records discarded.

User responseNone.

FPEC4025I NUMBER OF INCOMPLETE GTFSPANNED RECORDS DISCARDEDWAS <V1>

ExplanationThe record length used by GTF cannot accommodatethe longer DB2 instrumentation records, so GTF splitsthe data over a number of records. The program didnot find all the record segments necessary toreconstruct the DB2 instrumentation record anddiscarded the incomplete data.


User responseNone.

FPEC4030W IFCID <V1>. DATA SECTION <V2>.REPEATING GROUP <V3>. FIELD<V4> HAS A LENGTH OF <V5>.EXCEEDING THE ALLOWEDLENGTH OR EXCEEDING THE DATASECTION LENGTH <V6>. FIELD<V4> IS IGNORED FROM FURTHERPROCESSING.

ExplanationFor some IFCIDs, DB2 provides long names withvariable length.

For a particular data section field, the internal integrityvalidation for a long string failed. Processing continuesassuming that a long name is not provided.

• <V1> is the DB2 IFCID number.


• <V2> is the name of the data section.• <V3> is the repeating group number of the DB2 data

section.• <V4> is the name of the field within the DB2 data

section.• <V5> is the value for the length of the long name

that is found in the DB2 data section.• <V6> is the value of the length of the DB2 data

section.

User responseContact IBM Support to validate the data that issupplied by DB2.

FPEC4035W MORE THAN <V1> LONG STRINGSQUALIFYING FOR UNIQUE NAMEPROCESSING FOUND IN THEINPUT DATA. THIS CAN INDICATEAN INPUT DATA PROBLEM.UNIQUE NAME PROCESSING HASBEEN SUSPENDED TO PREVENTPERFORMANCE DEGRADATION.

ExplanationThis message might be displayed in conjunction withmessage FPEC4030W.

The Batch Reporter program complements long nameswith the unique short names to be presented correctlyin the reports and traces. However, if too many pairs oflong names and short names are accumulated, theBatch Reporter performance might degradeconsiderably.

A reasonable number of internally stored unique longnames is exceeded. Processing continues, however,instead of adding unique short names, the long namesare truncated and added as short names.

<V1> is the number of internally stored unique longnames.

User responseContact IBM Support to validate the data that issupplied by DB2.

FPEC4040W DATABASE/PAGESET <V1> HASTRANSLATION DATA MISSINGBETWEEN <V2> AND <V3>.TRANSLATIONS TO <V4> MAYHAVE BEEN MADE WHERE THEACTUAL NAMES WERE <V5>

ExplanationSome DBID/OBID translation data is missing. TheDBID or OBID changed, but the exact time of thechange is unknown. DBIDs and OBIDs may have beentranslated based on the old data rather than the new.

• <V1> is the name of the database or page set.• <V2> is the timestamp of the last record before the

missing data.• <V3> is the timestamp of the first record after the

missing data.• <V4> is the old name.• <V5> is the new name.


User responseNone.

FPEC4045W DATABASE/PAGESETTRANSLATION ROUTINEDETECTED <V1> MISSINGIFCID=107 OPEN RECORDS

ExplanationDBID/OBID translation data is missing. Sometranslations may not have been made correctly.

This message is printed if open and close records for aDBID or OBID are out of sequence. For example, thismessage is printed if there are two successive closerecords for the same DBID or OBID. There could be agap in the input data, or records may have been lostduring collection.

• <V1> is the number of missing IFCID 107 records.


User responseNone.

FPEC4050W DATABASE/PAGESETTRANSLATION ROUTINEDETECTED <V1> MISSINGIFCID=107 CLOSE RECORDS


ExplanationDBID/OBID translation data is missing. Sometranslations may not have been made correctly.

This message is printed if open and close records for aDBID or OBID are out of sequence. For example, thismessage is printed if there are two successive openrecords for the same DBID or OBID. There could be agap in the input data, or records may have been lost bySMF or GTF.

• <V1> is the number of missing IFCID 107 records.


User responseNone.

FPEC4055W DATABASE/PAGESETTRANSLATION ROUTINE WASUNABLE TO PERFORM <V1>TRANSLATIONS

ExplanationSome (or all) DBIDs and OBIDs could not be translatedto their eight-character name. This is most commonlycaused by missing IFCID 105 or IFCID 107 data. DB2Trace may not have been started correctly, or therecords could have been lost.

• <V1> is the number of translations that could not beperformed.


User responseNone.

FPEC4060I DB2 START TRACE NUMBER <V1>DB2 SUBSYSTEM ID = <V2> TEXT =<V3>

ExplanationA DB2 START TRACE command was detected.

• <V1> is the trace number.• <V2> is the DB2 subsystem ID.• <V3> is the text of the command.

Note that, depending on the operational situation, anadditional line indicating the location, group,

subsystem ID, member, date, and time may bedisplayed immediately following the message number.

User responseNone.

FPEC4065I DB2 STOP TRACE NUMBER <V1>DB2 SUBSYSTEM ID = <V2> TEXT =<V3>

ExplanationA DB2 STOP TRACE command was detected.

• <V1> is the trace number.• <V2> is the DB2 subsystem ID.• <V3> is the text of the command.


User responseNone.

FPEC4070I LOCATION <V1> HAS RECORDSFOR MORE THAN ONE DB2SUBSYSTEM. RECORDS FROMSUBSYSTEM <V2> PROCESSED,OTHER SUBSYSTEMS REJECTED

ExplanationTwo (or more) different DB2IDs were detected withthe same DB2 location name. Records for the second(or subsequent) DB2 subsystem were not processed.

• <V1> is the location name.• <V2> is the first DB2ID for the DB2 location.

User responseNone.

FPEC4075U LOCATION LIST HAS NOT BEENINITIALIZED BY RECORDPROCESSING

ExplanationAn internal processing error occurred.



FPEC4080U INITIALIZATION FAILED FORRECORD PROCESSING LIST 1.INSUFFICIENT STORAGEAVAILABLE

ExplanationThere was not sufficient storage available to continueprocessing.


FPEC4085U EXCEPTIONAL CONDITIONOCCURRED WHILE RECORDING ASUMMARY. INSUFFICIENTSTORAGE AVAILABLE



FPEC4090U EXCEPTIONAL CONDITIONOCCURRED WHILE RECORDINGAN OPEN. INSUFFICIENTSTORAGE AVAILABLE



FPEC4095U EXCEPTIONAL CONDITIONOCCURRED WHILE RECORDING ACLOSE. INSUFFICIENT STORAGEAVAILABLE



FPEC4100U INSUFFICIENT STORAGEAVAILABLE FOR GTF RECORDWORKAREA



FPEC4105U EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGRECORD PROCESSING LIST 2.VLIST RETURN CODE <V1>


• <V1> is the VLIST return code.





FPEC4120U EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGRECORD PROCESSING LIST 3.INSUFFICIENT STORAGEAVAILABLE







FPEC4140U EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGRECORD PROCESSING LIST 4.INSUFFICIENT STORAGEAVAILABLE



FPEC4150E TRACE RECORD COULD NOT BECONVERTED FROM UNICODE TOEBCDIC. CONVERSION SERVICESMAY NOT BE INSTALLEDCORRECTLY.

ExplanationA trace record from DB2 using Unicode strings wasencountered and could not be converted to EBCDIC forfurther processing and presentation.

User responseCheck that the z/OS Support for Unicode is installedcorrectly and provides conversions from CCSID 1208to the destination EBCDIC CCSID.

FPEC4200E OUT-OF-SEQUENCE RECORDFOUND. ACE ADDRESS: <V1>IFCID: <V2>

ExplanationPRESORTED has been specified in the GLOBALcommand, but the input data set has not previouslybeen sorted, and an out-of-sequence record has beendetected.

• <V1> is the ACE address of the out-of-sequencerecord.

• <V2> is the IFCID of the out-of-sequence record.

Note that, depending on the operational situation, anadditional line indicating the location, group,

subsystem ID, member, date, and time may bedisplayed immediately following the message number.

User responseIf this record is required, rerun the job without thePRESORTED option.

FPEC4205E AN OUT-OF-SEQUENCE RECORDHAS BEEN FOUND

ExplanationPRESORTED (ENFORCE) has been specified on theGLOBAL command, but the input data set has notpreviously been sorted, and an out-of-sequencerecord has been detected. The processing isterminated.

User responseDo one of the following:

• Specify PRESORTED (ACCEPT) to ignore out-of-sequence records and rerun the job.

• Omit the keyword PRESORTED from the GLOBALcommand and rerun the job.

• Sort the input data set before invoking DB2 PM anduse the sorted data as input.

FPEC4210W NUMBER OF OUT-OF-SEQUENCERECORDS WAS <V1>

ExplanationGLOBAL PRESORTED (ACCEPT) has been specified,but out-of-sequence records were encountered in theinput data.



User responseCheck the message log for details of the recordsdiscarded. If necessary, rerun the job without thePRESORTED option.

FPEC4215W NUMBER OF OUT-OF-SEQUENCERECORDS FOR IFCID <V1> WAS<V2>

ExplanationThe program was executed specifying the GLOBALPRESORTED(ACCEPT) option and out-of-sequence


records were encountered. This message shows thenumber of out-of-sequence records of each IFCIDwhich were encountered. It is recommended that thePRESORTED(ACCEPT) option is only used with theAccounting report set. Out-of-sequence records ofother report sets are ignored, and the integrity of theoutput may be in doubt.

A record is out of sequence if its key (location,timestamp) is less than that of the record with thehighest key already processed.

• <V1> is the IFCID.• <V2> is the number of out-of-sequence records.


User responseWhen running accounting, no response is necessary. Ifthe ignored out-of-sequence records were required bythe report set you requested, rerun the job specifyingPRESORTED(NO).

FPEC4220W NUMBER OF INVALID RECORDSFOR IFCID <V1> WAS <V2>

ExplanationThe program encountered one or more IFCIDs that donot comply with the Db2 definitions. There can beseveral reasons for this, such as missing data sectionsor unexpected data section length. The <V1> is theIFCID and <V2> is the number of non-compliantIFCIDs encountered. The accompanying FPEC4225Imessage advises adding ERRDMPDD DD card to dumpinvalid IFCIDs.

User responseIf necessary, collect diagnostics information inERRDMPDD DD and provide it to IBM for problemanalysis.

FPEC4225I ADD ERRDMPDD DD CARD TOREPORT TRACE DATA IN ERROR

ExplanationThis message accompanies message FPEC4220W andappears if no ERRDMPDD DD card supplied for theinvalid IFCIDs dumping.

User responseSupply the ERRDMPDD DD card to collect diagnosticsinformation and then contact IBM Technical Support.

FPEC5000E MERGE PROCESSING PHASE HASBEEN UNSUCCESSFUL

ExplanationThe merge processing phase did not completesuccessfully.


FPEC5001E MERGE PROCESSINGINITIALIZATION FAILED FOR<V1>

ExplanationThe initialization of merge processing failed for thespecified report set.



FPEC5002E <V1> FAILED DURING THE MERGEPROCESSING PHASE

ExplanationThe merge processing phase of the specified report setfailed. Processing terminates at the end of the mergeprocessing phase or after the merge processingphases of other report set specifications, if present inthe job.



FPEC5003I MERGE PROCESSINGTERMINATION FAILED FOR <V1>

ExplanationThe termination of merge processing failed for thespecified report set. Processing continues.



FPEC6000E REPORT PROCESSING PHASE HASBEEN UNSUCCESSFUL


ExplanationThe report processing phase did not complete itsfunction successfully.


FPEC6001E REPORT PROCESSINGINITIALIZATION FAILED FOR<V1>

ExplanationThe initialization of report processing failed for thespecified report set.



FPEC6002E <V1> FAILED DURING THEREPORT PROCESSING PHASE

ExplanationThe report processing phase of the specified report setfailed. Processing terminates at the end of the reportprocessing phase or after the report processing phasesof other report set specifications, if present in the job.



FPEC6003I REPORT PROCESSINGTERMINATION FAILED FOR <V1>

ExplanationThe termination of report processing failed for thespecified report set. Processing continues.



FPEC6005S AN ERROR OCCURRED WHILEREADING THE RESTORE FILE<V1>. VSAM RETURN CODE <V2>,REASON CODE <V3>

ExplanationNone.

• <V1> is the name of the RESTORE file.• <V2> is the VSAM return code.• <V3> is the reason code.


FPEC6010S OPEN FAILED FOR SAVE FILE<V1>, DDNAME IN USE

ExplanationA ddname is specified twice (or more) with conflictingpurposes.

• <V1> is the name of the Save File data set.


FPEC6011S OPEN FAILED FOR SAVE FILE <V1>

ExplanationAn error occurred when opening a data set. The dataset exists, but could not be opened.

• <V1> is the name of the Save File data set.

User responseSee the previous messages detailing the problem.

FPEC6012S THE INITIAL WRITE TO THE SAVEFILE <V1> FAILED. VSAM RETURNCODE <V2>, REASON CODE <V3>

ExplanationAn internal processing error occurred duringexecution.

• <V1> is the ddname for the Save data set.• <V2> is the VSAM return code.• <V3> is the VSAM reason code.


FPEC9101S <V1> <V2> USER-TAILOREDLAYOUT <V3> COULD NOT BEFOUND, AND IS NOT ARECOGNIZED DEFAULT LAYOUT


ExplanationThe user-tailored layout specified does not exist inyour DPMPARMS data set.

• <V1> is the name of the report set.• <V2> is the function.• <V3> is the layout name.

User responseEnsure the layout is copied to the DPMPARMS data set.

FPEC9102S <V1> <V2> DEFAULT LAYOUT <V3>COULD NOT BE FOUND WITH THEEXPECTED LOAD MODULE NAMEOF <V4>

ExplanationNone.

• <V1> is the name of the report set.• <V2> is the function.• <V3> is the layout name.• <V4> is the load module name.

User responseSee your system programmer.

FPEC9103S <V1> <V2> LAYOUT <V3>REQUIRES A MINIMUM PAGE SIZEOF <V4>, THE GLOBAL PAGESIZEIS <V5>

ExplanationNone.

• <V1> is the name of the report set.• <V2> is the function.• <V3> is the layout name.• <V4> is the global page size required.• <V5> is the current global page size.

User responseEither tailor the layout to use less space, or increasethe global page size.

FPEC9104S MEMBER <V1> APPEARS INDPMPARMS, BUT IS NOT A VALIDUSER-TAILORED LAYOUT

ExplanationThe member <V1> was not generated using the UTRfeature, and cannot be used.

User responseGenerate the layout using UTR.

FPEC9105S MEMBER <V1> IS A CORRUPTUSER-TAILORED LAYOUT

ExplanationThe member <V1> has been edited outside the UTRfeature.

User responseRe-create the layout using UTR.

FPEC9106S UNABLE TO ALLOCATE STORAGETO PERFORM USER-TAILOREDREPORTING



FPEC9107S UNABLE TO ACCESS THEDPMPARMS PDS DIRECTORYWHEN SEARCHING FOR A USER-TAILORED LAYOUT

ExplanationThis is an I/O problem.


FPEC9108S MEMBER <V1> APPEARS IN THEDPMPARMS DIRECTORY BUTCOULD NOT BE LOCATED IN THEPDS

ExplanationThe PDS is corrupt.

• <V1> is the DPMPARMS member name.


User responseRe-create the PDS.

FPEC9109S MEMBER <V1> COULD NOT BEREAD FROM THE DPMPARMS PDS

ExplanationThis is an I/O problem.

• <V1> is the DPMPARMS member name.


FPEC9110S <V1> <V2> DEFAULT LAYOUT <V3>CANNOT BE LOADED BECAUSELOAD MODULE NAME <V4> DOESNOT BELONG TO THE CURRENTPRODUCT VERSION

ExplanationA default layout from an earlier version was detected.

• <V1> is the name of the report set.• <V2> is the function.• <V3> is the layout name.• <V4> is the load module name.

User responseUse one of the default layouts supplied with thisproduct.

FPEC9200I <V1> REDUCE COMPLETED.SUMMARY OF REDUCED DATAFOLLOWS

ExplanationNone.


User responseNone.

FPEC9201I <V1> REDUCE COMPLETED. NODATA WAS REDUCED

ExplanationNone.


User responseNone.

FPEC9203E DPM0 CONVERSION FAILED.IFCID CONTAINS INVALID DATA.CORRUPTED RECORD ISDISCARDED FROM FURTHERPROCESSING. REASON CODE:<V1>

ExplanationAn input record contains incorrect data. This inputrecord is discarded from further processing. Thecorresponding subsystem ID and the recordtimestamp are included in your JOBSUMDD.

• <V1> is the reason code

User responseCheck whether your input data is damaged. Forexample, transmission errors might be the reason fordamaged input data. If possible, recollect the data.

If the error remains, specify ERRDMPDD in your Job tocollect the corrupted input data in a service dataset.For further details, see Reporting Command Reference.

If the problem persists, contact IBM support.

FPEE - Exception Processing messagesFPEE0001E EXCEPTION PROCESSING

TERMINATED ABNORMALLY.INTERNAL ERROR IN MODULE<V1>, ERROR CODE <V2>

ExplanationAn internal processing condition occurred duringexecution.

• <V1> is the name of the module.

• <V2> is the error code.

User responseRerun the job. If the problem recurs, contact IBMsupport and quote the error code.

FPEE0012E FILE RECORD WAS NOT WRITTEN,DDNAME = <V1>, RETURN CODE =<V2>


ExplanationAn attempt to write an exception file record failed.

• <V1> is the ddname for which the failure occurred.• <V2> is the return code.

User responseCheck that the DD statement for the ddname is valid,and that there is sufficient space available.

FPEE0014I EXCEPTIONS LOG FILECOMPLETE. <V1> RECORDSWRITTEN TO DDNAME <V2>

ExplanationException log file processing is completed.

• <V1> is the number of records written.• <V2> is the ddname to which the records were

written.

User responseNone.

FPEE0600S EXCEPTIONAL CONDITIONOCCURRED WHILE PROCESSINGEXCEPTIONS. LIST STORAGEALLOCATION FAILED

ExplanationNot enough storage was available to continueexception processing.

User responseIncrease the region size.

FPEE0610S EXCEPTIONAL CONDITIONOCCURRED WHILE PROCESSINGEXCEPTIONS. LIST STORAGERELEASE FAILED

ExplanationAn error occurred when attempting to release storage.


FPEE0915W ERROR ATTEMPTING TOALLOCATE OR OPEN THE <V1>DATA SET.

ExplanationThe indicated data set could not be allocated oropened for exception processing. Possible reasonsare:

• The data set does not exist.• The OMEGAMON Collector is not authorized to

access the data set.• The data set has wrong LRECL or RECFM definitions.

User responseVerify the indicated reasons, correct them, and rerunthe job. If the problem recurs, contact IBM support.

FPEE0918W THRESHOLD FIELD <V1> IS INERROR. EVENT <V2> IS INVALID

ExplanationThe field name entered in the exception threshold dataset is not valid.

• <V1> is the threshold field.• <V2> is the event.

User responseCorrect the field in the exception threshold data setand rerun the job.

FPEE0919W THRESHOLD FIELD <V1> IS INERROR. THE FIELD IS NOT VALIDFOR ENVIRONMENT <V2>

ExplanationThe field name entered in the exception threshold dataset is not valid for this environment.

• <V1> is the threshold field.• <V2> is the environment.

User responseEdit the field in the exception threshold data set andrerun the job.

FPEE0920W THRESHOLD FIELD <V1> IS INERROR. THE FIELD NAME ISINVALID

ExplanationThe field name entered in the exception threshold dataset has invalid syntax.

• <V1> is the threshold field.


User responseCorrect the field in the exception threshold data setand rerun the job.

FPEE0921W THRESHOLD FIELD <V1> IS INERROR. FIELD <V2> IS INVALIDFOR THIS RELEASE OF DB2

ExplanationThe field name entered is not valid for any release ofDB2.

• <V1> is the threshold field.• <V2> is the threshold field.

User responseRemove the field from the exception threshold dataset.

FPEE0922W THRESHOLD FIELD <V1> IS INERROR. FIELD IS INVALID FOREVENT <V2>

ExplanationThe field name entered in the exception threshold dataset is not valid for the event specified.

• <V1> is the threshold field.• <V2> is the event.

User responseChange the field name or the event in the exceptionthreshold data set.

FPEE0923W THRESHOLD FIELD <V1> IS INERROR. NUMERIC VALUE <V2>NOT VALID

ExplanationA not valid numeric value has been specified for thisfield in the exception threshold data set.

• <V1> is the threshold field.• <V2> is the numeric value.

User responseChange the value or remove the field from theexception threshold data set.

FPEE0924W THRESHOLD FIELD <V1> IS INERROR. OPERATOR <V2> ISINVALID

ExplanationA not valid operator has been specified for this field inthe exception threshold data set.

• <V1> is the threshold field.• <V2> is the invalid operator.

User responseChange the specified operator or remove the field fromthe exception threshold data set.

FPEE0925W THRESHOLD FIELD <V1> IS INERROR. FIELD CANNOT BEQUALIFIED

ExplanationThe field has been qualified with either a buffer, DDF,or package qualifier, but the field is not a buffer, DDF,or package field.


User responseChange or remove the field in the exception thresholddata set.

FPEE0926W THRESHOLD FIELD <V1> IS INERROR. QUALIFIER <V2> IS NOTVALID

ExplanationThe field can be qualified, but the buffer, DDF, orpackage qualifier has an incorrect format.

• <V1> is the threshold field.• <V2> is the invalid qualifier.

User responseChange the qualifier or remove the field from theexception threshold.

FPEE0927W THRESHOLD FIELD <V1> IS INERROR. TIME VALUE <V2> ISINVALID

ExplanationA not valid time value has been specified for this fieldin the exception threshold data set.

• <V1> is the threshold field.• <V2> is the invalid time value.


User responseChange the value or remove the field from theexception threshold data set.

FPEE0928W THRESHOLD FIELD <V1> IS INERROR. TIME VALUE IS NOT VALIDFOR THIS FIELD

ExplanationA time value was entered, but the field does not have atime format.


User responseCorrect the format or remove the field from theexception threshold data set.

FPEE0931W THRESHOLD FIELD <V1> IS INERROR. COMPARE BASIS <V2> ISINVALID

ExplanationThe compare basis is not one of ‘V’, ‘M’, ‘S’, ‘C’, or ‘O’.

• <V1> is the threshold field.• <V2> is the invalid compare basis.

User responseCorrect the compare basis for the field.

FPEE0932W THRESHOLD FIELD <V1> IS INERROR. BOTH VALUES ARE BLANK

ExplanationA non-blank field must be entered in either theproblem or warning field.


User responseCorrect the field in the exception threshold data set.

FPEE0942W THRESHOLD FIELD <V1> IS INERROR. FIELD IS NOT A VALIDEXCEPTION FIELD

ExplanationThe field entered cannot be used for exceptionprocessing.


User responseRemove the field from the exception threshold dataset.

FPEE4001S ERROR INITIALIZING EXCEPTIONPROCESSING

ExplanationAn error occurred initializing exception processing.


FPEE4002I EXCEPTION PROCESSINGSUSPENDED. NO DATA

ExplanationAll fields in the exception threshold data set areincorrect, or the data set contains no fields.

User responseAdd valid fields to the exception threshold data set.

FPEE5100E BOTH WARNING AND PROBLEMVALUES MUST BE SPECIFIED

ExplanationNone.

User responseSupply both warning and problem values.

FPEE5200W THRESHOLD FIELD <V1> IS INERROR. THE ENVIRONMENTREPORT IS NOT SUPPORTED

ExplanationThe field is valid only for batch report, but the problemor warning value is an asterisk. The field is ignored forexception profiling.

• <V1> is the threshold field in error.

User responseSpecify a valid threshold value instead of the asterisk.

FPEE5300E WARNING VALUE MUST BEGREATER THAN PROBLEM VALUE


ExplanationNone.

User responseEnter a warning value that is greater than the problemvalue.

FPEE5500I NO VALID INPUT RECORDSENCOUNTERED

ExplanationNo records in the exception threshold data set werevalid.

User responseCheck the exception threshold data set for invalid fieldvalues.

FPEE5604I THRESHOLD DATA SET FROMPREVIOUS RELEASE IS USED

ExplanationThe threshold data set has a format that was valid forprior versions. It has been reformatted to the format ofthe current version.

User responseNone. If you want to avoid this message, use thethreshold data set editor to change the format.

FPEE5605I NO EXCEPTION THRESHOLDCALCULATED. REASON CODE <V1>

ExplanationThe job has ended without having calculated anyexception threshold values.

• <V1> is the reason code.

The following reason codes are possible:1

INPUTDD has no valid data.

User responseProvide valid data to INPUTDD and rerun the job.

FPEF - Interactive Report Facility messagesFPEF000 This command is not recognized

ExplanationA not valid command was entered on the commandline or via a function key.


FPEF001 This command does not acceptparameters

ExplanationThe command entered on the command line or via afunction key does not accept parameters, butparameters were supplied.


FPEF002 This command accepts only asingle parameter

ExplanationThe command entered on the command line or via afunction key only accepts one parameter, but morethan one was supplied.


FPEF003 This command requiresparameters

ExplanationThe command entered on the command line or via afunction key required parameters, but none weresupplied.


FPEF004 <V1> command not valid in thispanel


ExplanationThe command entered on the command line is notvalid in this panel.

• <V1> is the command.


FPEF005 Enter a value for Location or Group

ExplanationBoth LOCATION and GROUP fields are blank.

User responseEnter a value in either or both fields.

FPEF009 Command generation already inprogress in this ISPF logicalscreen

ExplanationAn attempt was made to perform IRF selections, butthe function was already active on this ISPF logicalscreen. You can have only one IRF selection functionactive on a logical screen at a time.

User responseClose the application. If the problem recurs, terminatethe ISPF logical screen.

FPEF010 Enter a / or <V1> to select

ExplanationA value other than a / or a country-designatedcharacter was used in the field at the cursor position.

• <V1> is the country-designated character.

User responseEnter a / or the country-designated character toselect.

FPEF011 Enter one of the listed values

ExplanationA not valid value was entered in the field at the cursorposition, and adjacent to the message.

User responseEnter a value from the list displayed in the panel.

FPEF012 Field must be completed

ExplanationThe field at the cursor position must be completed.

User responseEnter a value for the field.

FPEF013 Prompt is not available for thisfield

ExplanationThe PROMPT command is not valid for the field at thecursor position.

User responseValid options can be determined using the HELPcommand.

FPEF014 This is not a valid data set name

ExplanationA data set name qualifier must begin with analphabetic character, @, #, or $. The remainingcharacters must be either alphanumeric or a hyphen(-).

User responseEnter a valid data set name.

FPEF015 This is not a valid value for thisfield

ExplanationThe value entered in the field at the cursor position isnot valid.

User responseEnter a valid value.

FPEF016 This value must be numeric

ExplanationThe value entered in the field at the cursor position isnot numeric.

User responseEnter a numeric value.


FPEF017 This value must be numeric in therange <V1> to <V2>

ExplanationThe field at the cursor position contains a numericvalue outside the valid range.

• <V1> is the lower limit.• <V2> is the upper limit.

User responseEnter a numeric value in the valid range.

FPEF018 This is not a valid name

ExplanationA name must begin with an alphabetic character, @, #,or $. The remaining characters must be alphanumeric.

User responseEnter a valid name.

FPEF019 Enter 1 for yes or 2 for no

ExplanationA value other than 1 or 2 was used in the field at thecursor position.


FPEF020 Enter a / or <V1> to select one ormore items from the list

ExplanationA value other than / or a country-designated characterwas used in the field at the cursor position.


User responseEnter a / or a country-designated character to select.

FPEF021 Enter a / or <V1> to select, orovertype with space to delete




FPEF022 No Type matches this value. Validtypes are IRLMREQ, CLAIMREQ,DRAINREQ, PLOCKREQ,IRLMSUSP, DRAINSUSP,LATCHSUSP, IRLMRES,DRAINRES, LATCHRES, TIMEOUT,DEADLOCK, LOCKSUMMARY, andLOCKAVOID

ExplanationA value other than those listed in the message wasused in the field at the cursor position.

User responseEnter a correct value.

FPEF023 Enter a / or <V1> to browse or editextension information




FPEF024 No Resource Type matches thisvalue. Valid Resource Types areDATAPAGE, DATABASE, DATASET,PAGESET, INDEX, TABLE, SKCT,SKPT, COLLECT, DRAIN, ROW, andOTHER

ExplanationA value other than those listed in the message wasused in the field at the cursor position.


FPEF025 Enter a / or <V1> to add a newentry





FPEF027 Select only one item from the list

ExplanationEither no selection was made from the list, more thanone item was selected from the list, or a characterother than / or a country-designated character wasused to select a list item.

User responseSelect only one item from the list by entering a / or acountry-designated character.

FPEF028 The group or list selection is beingdeleted because it had noassociated Include or Excludevalues

ExplanationNo INCLUDE/EXCLUDE values were specified for theGROUP or LIST name.

User responseNone.

FPEF029 Range is not applicable to thisidentifier

ExplanationRange is not valid for this identifier.

User responseRemove the range specification.

FPEF030 This location starts with a < buthas no > at the end

ExplanationNone.

User responseEnter the ‘greater than’ sign at the end of the location(locations can be enclosed in ‘less than’ (<) and‘greater than’ (>) symbols).

FPEF031 No Thread Type matches this fieldvalue. Valid Thread Types areALLIED, ALLIED_DIST, and DBAT

ExplanationThe thread type entered does not match any validthread type.


FPEF032 Both value 1 and value 2 arespecified - either set type to 3 orremove value 2

ExplanationBecause range values have been entered, type shouldnot be entered.

User responseEither set type to 3 or remove the range value 2.

FPEF033 This value must be hexadecimalrepresentation (0-9, a-f)

ExplanationThe field at the cursor position must contain acharacter representation of a hexadecimal value. Validcharacters are 0 to 9 and A to F.


FPEF034 This value must have a length of<V1> exactly

ExplanationThe field at the cursor position must contain a setnumber of characters.

• <V1> is the required number of characters.


FPEF035 The maximum length for this valueis <V1>

ExplanationThe field at the cursor position contains an entry thatis too long.

• <V1> is the maximum number of characters.



FPEF036 Generic * is not allowed withGroup and List names

ExplanationYou cannot use the generic form (*) in GROUP or LISTnames.


FPEF037 Group and List values must startwith a character (A-Z)

ExplanationNone.


FPEF038 Generic * can only suffix a rangevalue

ExplanationFor ranges, the generic character * can only be the lastcharacter. For example, ABC* is valid; AB*D is not.


FPEF039 The TO range must be greater thanthe FROM range

ExplanationNone.


FPEF040 Year must be numeric in the range0 to 99

ExplanationNone.


FPEF041 Month must be numeric in therange 1 to 12

ExplanationNone.


FPEF042 Day must be numeric in the range1 to 31

ExplanationNone.


FPEF043 Hours must be numeric in therange 0 to 23

ExplanationNone.


FPEF044 Minutes must be numeric in therange 0 to 59

ExplanationNone.


FPEF045 Seconds must be numeric in therange 0 to 59

ExplanationNone.


FPEF046 Fractions must be numeric in therange 0 to 99


ExplanationNone.


FPEF047 Timezone adjustment sign must be+ or -

ExplanationNone.


FPEF048 Minutes must be numeric in therange 00 to 59

ExplanationNone.


FPEF049 Specify the FROM range

ExplanationNone.

User responseEnter the FROM range.

FPEF051 The day value is invalid for thismonth and year combination

ExplanationNone.

User responseEnter a valid day, month, and year combination.

FPEF052 The end date must be later than orequal to the start date

ExplanationNone.

User responseChange the start date or end date to comply.

FPEF053 The end time must be later than orequal to the start time

ExplanationNone.

User responseChange the start time or end time to comply.

FPEF054 The end date and time must belater than or equal to the startdate and time

ExplanationNone.

User responseChange the start date and time or end date and time tocomply.

FPEF055 When NONE is selected, otherselections are not valid. Eitherdelete NONE or delete allremaining selections

ExplanationNone.

User responseDelete NONE or delete all remaining selections.

FPEF056 The maximum length for thelocation id part of package name is16. Package name compriseslocation.collection.package

ExplanationThe maximum length of the location ID exceeds 16characters.

User responseEnter a location ID up to 16 characters in length.

FPEF057 The maximum length for thecollection id part of package nameis 18. Package name compriseslocation.collection.package


ExplanationThe maximum length of the collection ID exceeds 18characters.

User responseEnter a collection ID up to 18 characters in length.

FPEF058 The maximum length for thepackage id part of package nameis 18. Package name compriseslocation.collection.package

ExplanationThe maximum length of the package ID exceeds 18characters.

User responseEnter a package ID up to 18 characters in length.

FPEF059 Package name can only becomprised of 3 parts: location id,collection id, and package id

ExplanationNone.


FPEF060 <V1>

ExplanationThis message is returned by the LMINIT service ofISPF/PDF Library Access Services or the LISTDSIfunction of TSO/E. The message can be accompaniedby other messages.

• <V1> is the text of the message.

User responseCorrect the problem indicated by the message.

FPEF061 Data set organization must bepartitioned

ExplanationA not valid data set was specified when saving orrecalling IRF selections. The data set was notpartitioned.

User responseCorrect the data set specifications.

FPEF062 Data set must contain 80 bytefixed length records

ExplanationA not valid data set was specified when saving orrecalling IRF selections. The specified data set doesnot contain 80-byte fixed length records.

User responseCorrect the data set specification.

FPEF063 Data set is empty

ExplanationThe data set specified when recalling IRF selectionscontains no data.

User responseSpecify another data set.

FPEF064 Member not found

ExplanationThe member specified in the recall request for IRFselections was not found.

User responseCorrect the data set and member specifications.

FPEF065 The specified pattern produced nomatching members

ExplanationA pattern with no matching members was specifiedwhen recalling IRF selections.

User responseSpecify another pattern or member name.

FPEF066 Member does not contain a validIRF selection table

ExplanationWhen recalling IRF selections, the selected memberdid not contain an IRF selection table.


User responseCorrect the data set and member specifications.

FPEF067 Replacement canceled

ExplanationWhen saving IRF selections, a member name wasspecified that already existed, and the user requestedthat the member not be replaced.

User responseNone.

FPEF068 Member name must be blank for asequential data set

ExplanationWhen trying to save a job stream, a member name wasspecified for a sequential data set.

User responseBlank the member name.

FPEF069 Member name must be specifiedfor partitioned data set

ExplanationWhen trying to save a job stream, a member name wasnot specified for a partitioned data set.

User responseEnter the member name.

FPEF070 Job stream replaced in <V1>

ExplanationThe job stream was successfully saved to an existingdata set. The previous contents were replaced.

• <V1> is the name of the data set where the jobstream was replaced.

User responseNone.

FPEF071 Job stream saved into <V1> hasfailed

ExplanationJob stream save or replace function failed. This istypically accompanied by other messages indicatingthe problem.

• <V1> is the name of the data set where the jobstream was being saved.

User responseCorrect the problems indicated by the accompanyingmessages.

FPEF072 Job stream saved into <V1>

ExplanationThe job stream was successfully saved.

• <V1> is the name of the data set where the jobstream was saved.

User responseNone.

FPEF073 IRF selection <V1> recalled from<V2>

ExplanationIRF selections were successfully recalled.

• <V1> is the name of the member that contained theselections.

• <V2> is the name of the data set that contained theselections.

User responseNone.

FPEF074 IRF selection <V1> saved into<V2>

ExplanationIRF selections were successfully saved into a PDSmember.

• <V1> is the name of the member.• <V2> is the name of the partitioned data set.

User responseNone.

FPEF075 IRF selection <V1> replaced in<V2>


ExplanationIRF selection was successfully saved to an existingdata set. The previous member contents werereplaced.

• <V1> is the name of the member where theselections were replaced.

• <V2> is the name of the data set where theselections were replaced.

User responseNone.

FPEF076 Unable to save selections in dataset <V1>. ISPF message is: <V2>

ExplanationAn error was encountered when saving yourselections.

• <V1> is the name of the data set where theselections were being saved.

• <V2> is the error message returned by ISPF.

User responseCorrect the error indicated by the ISPF message.

FPEF077 Unable to open data set

ExplanationAn error occurred in opening the data set.

User responseEnsure that the data set exists.

FPEF078 Edit error, data may not have beensaved correctly

ExplanationA severe error occurred when editing the data set. Thedata may not have been saved correctly.

User responseBrowse the data set using ISPF to check if the data hasbeen successfully saved. If this is not the case, correctthe edit error and try again.

FPEF079 This field needs to be qualifiedwith a group buffer pool ID

ExplanationA group buffer pool ID qualifier is required for this fieldname.


FPEF080 Field identifier invalid - usePROMPT command for a list

ExplanationThe field identifier at the cursor position is not valid.Use the PROMPT command to select from a list of validvalues.


FPEF081 This field needs to be qualifiedwith a buffer pool ID

ExplanationA buffer pool ID qualifier is required for this fieldname.


FPEF082 This field must not have a qualifier

ExplanationA buffer pool qualifier is not valid for this field name.


FPEF083 Field qualifier invalid - usePROMPT command for a list

ExplanationThe qualifier at the cursor position is not valid. Use thePROMPT command to select from a list of valid values.


FPEF084 The qualifier must be a locationname or omitted


ExplanationThe qualifier at the cursor position should be alocation name or not specified.


FPEF085 Location name must begin with acharacter

ExplanationNone.


FPEF086 Location name must only containletters, digits, and nationalcharacters

ExplanationNone.


FPEF087 The qualifier must be a validpackage name or omitted

ExplanationNone.


FPEF088 This field must be qualified with aResource Limit Facility qualifier

ExplanationNone.


FPEF089 Enter field name before usingPROMPT command on qualifier

ExplanationNone.

User responseEnter a field name, then use PROMPT.

FPEF090 Qualifier for this field is optional.No list is available

ExplanationNone.

User responseNone.

FPEF091 <V1>

ExplanationAn error occurred while trying to view the commandstream.

• <V1> is the text of the ISPF message.

User responseCorrect the problem indicated by the ISPF message.

FPEF092 There is nothing to BROWSE forthe selection

ExplanationThere is no data available for the BROWSE commandto process.

User responseEnsure that selections or entries have been madebefore using the BROWSE command.

FPEF093 Job submission has beensuccessful

ExplanationThe job has been successfully submitted inbackground execution mode.

User responseNone.

FPEF094 Job submission has failed

ExplanationThe job submission in background execution mode hasnot been successful. This message is preceded by oneor more TSO/E messages.


User responseSee z/OS TSO/E Messages for an explanation of theTSO/E messages. Correct the problem indicated by theTSO/E messages.

FPEF095 '*' is not permitted for thisfunction

ExplanationNone.


FPEF100 Groups are not allowed for thisidentifier

ExplanationThe identifier supplied cannot be used in a GROUPspecification.

User responseUse a valid identifier in the GROUP specification.

FPEF101 Lists are not allowed for thisidentifier

ExplanationThe identifier supplied cannot be used in a LISTspecification.

User responseUse a valid identifier in the LIST specification.

FPEF102 Groups are not allowed withinGroups

ExplanationNone.


FPEF103 You cannot add and select ordelete entries at the same time

ExplanationNone.


FPEF104 Identifiers have been repeated

ExplanationMore than one specification of the same identifier hasbeen used.


FPEF105 Location must be alphanumericbeginning with an alphabeticcharacter

ExplanationA not valid location was specified.


FPEF106 Select numbers from the code list

ExplanationNone.

User responseSelect a code from the list shown.

FPEF107 Utility allows only one group of upto three order selections. UseOrder 1 only

ExplanationThe Utility Activity report set only allows the first groupof identifiers to be selected.

User responseSpecify up to three identifiers in the Order 1 row only.

FPEF110 This file cannot be directed to theterminal

ExplanationVSAM or partitioned data sets cannot be directed tothe terminal.


User responseCorrect the data set information.

FPEF111 This file cannot be directed toSYOUT

ExplanationInput, VSAM, or partitioned data sets cannot bedirected to SYSOUT.


FPEF112 This file cannot be set to DUMMY

ExplanationDUMMY cannot be specified for VSAM or partitioneddata sets.


FPEF113 DUMMY cannot be part ofconcatenated data sets

ExplanationDUMMY cannot be concatenated with other data sets.

User responseDo not include DUMMY as a specified data set forconcatenation.

FPEF114 This DDNAME cannot haveconcatenated data sets

ExplanationYou cannot concatenate output or VSAM data sets.

User responseSpecify only one data set for this ddname.

FPEF115 This is not in valid JCL format

ExplanationA JCL syntax error has been detected.


FPEF116 Extension information exists. Youcannot remove the first line

ExplanationMultiple data set information lines exist. Data setinformation must be present on the first line.

User responseEither erase all lines or add information on the firstline.

FPEF117 Extension information exists. Notall lines are in the same format

ExplanationMultiple data set information lines exist. The first dataset information line has been changed into a differentformat. However, the subsequent lines are still in theoriginal format.

User responseEither change the first line back into the originalformat, or change the subsequent lines into the sameformat as the first line.

FPEF119 Enter data set information beforerequesting extension data

ExplanationExtension information can only be requested inforeground if the data set information contains a dataset name.

User responseRemove the select action code from the field orchange the data set information to a data set name.

FPEF120 DDNAME could not be allocated

ExplanationThe file could not be allocated. This message ispreceded by TSO/E messages.

User responseSee z/OS TSO/E Messages for an explanation of TSO/Emessages. Correct the error indicated by the TSO/Emessages.

FPEF121 DDNAME SYSIN could not beallocated


ExplanationThe SYSIN file containing the command stream couldnot be allocated. This message is preceded by TSO/Emessages. See z/OS TSO/E Messages for anexplanation of TSO/E messages.

User responseCorrect the error indicated by the TSO/E messages.

FPEF122 DDNAMEs could not be freed

ExplanationFiles could not be freed.

User responseCorrect the error indicated by the TSO/E messages andfree the files.

FPEF123 DB2 PM has been executed.Return code was <V1>

ExplanationA foreground execution has completed its function.


User responseNone.

FPEF124 <V1>

ExplanationAn error was detected when attempting to run theapplication in foreground execution mode. Thismessage is preceded by TSO/E messages.

• <V1> is the text of the message.

User responseSee z/OS TSO/E Messages for an explanation of TSO/Emessages.

FPEF125 Data set <V1> is empty

ExplanationAn attempt has been made to browse an output dataset specified during foreground execution, whichcontains no data.

• <V1> is the name of the output data set.

User responseNone.

FPEF126 Unable to browse data set. ISPFmessage is: <V1>

ExplanationAn error occurred while attempting to browse the dataset.



FPEF127 Performance Expert has beeninvoked - please stand by

ExplanationThe application is started in foreground executionmode.

User responseNone.

FPEF128 This information format cannothave extension information

ExplanationAn attempt has been made to specify extensioninformation for an output data set in foreground mode.Only input data sets can have extension information.


FPEF130 <V1> is not a valid action code.Valid codes are: /, <V2>, I, R, D, C,M, A, and B

ExplanationAn action code other than those listed was used.

• <V1> is the invalid action code.• <V2> is the country-designated character.

User responseUse a valid action code.

FPEF131 <V1> is not a valid action code.Valid codes are: I, R, D, C, M, A,and B


ExplanationAn action code other than those listed was used.

• <V1> is the invalid action code.

User responseUse a valid action code.

FPEF132 Use I action code to insert rows.Use Insert only when no rows exist

ExplanationNone.

User responseUse I to insert rows.

FPEF133 Invalid SORT column specified

ExplanationNone.

User responseSpecify a valid sort column.

FPEF134 Invalid FIND command. Syntax:'Find column argument (operator)'

ExplanationNone.

User responseCorrect the syntax.

FPEF135 Invalid FIND column specified

ExplanationNone.

User responseSpecify a valid find column.

FPEF136 Invalid FIND operator. Validoperators are: EQ, NE, LT, GE, GT,and LE

ExplanationNone.

User responseSpecify a valid operator.

FPEF137 Move/Copy is pending. CompleteMOVE or COPY command, or'RESET' command

ExplanationNone.

User responseComplete the MOVE or COPY command or use RESET.

FPEF138 <V1> is not a valid line command.Either correct it or blank it out

ExplanationNone.

• <V1> is the invalid line command.

User responseCorrect the input or blank it out.

FPEF140 Command conflict. CompleteBLOCK command before enteringother commands

ExplanationNone.

User responseComplete the BLOCK command.

FPEF141 BLOCK command has an invalidamount

ExplanationNone.


FPEF142 BLOCK command incomplete.Enter a matching command tocomplete the BLOCK commandpair

ExplanationNone.



FPEF143 BLOCK command has an invalidnumeric amount

ExplanationNone.


FPEF144 An RR command has an invalidamount

ExplanationNone.


FPEF150 REPLACE should not be specifiedwithout the TABLE command

ExplanationREPLACE is a subcommand of TABLE. Therefore,REPLACE is meaningless unless you have specifiedTABLE as well.

User responseSpecify REPLACE together with the TABLE command.

FPEF151 User ID should be 8 characters orless

ExplanationNone.

User responseSpecify USERID with a length of 8 characters or less.

FPEF152 Table name should be 10characters or less

ExplanationNone.

User responseSpecify TABLE NAME with a length of 10 characters orless.

FPEF153 KEEPDICTIONARY should not bespecified without the TABLEcommand

ExplanationKEEPDICTIONARY is a subcommand of TABLE.Therefore, KEEPDICTIONARY is meaningless unlessyou have specified TABLE as well.

User responseSpecify KEEPDICTIONARY together with the TABLEcommand.

FPEF501 This character is invalid. Validcharacters are A-Z, @, #, $, and *

ExplanationA not valid character has been entered at the cursorposition. Valid characters are identified in the messagetext.


FPEF502 This character is invalid. Validcharacters are A-Z, @, #, and $



FPEF503 This character is invalid. Validcharacters are A-Z, 0-9, @, #, $, _,–, and *




FPEF504 No connection type matches thisfield value. Valid connection typesare TSO, DB2CALL, CICS®, DLI-BTCH, IMS-MPP, IMS-BMP, IMS-TBMP, IMS-CNTL, SYST-DIR, andAPPL-DIR

ExplanationA not valid connection type has been entered. Thevalid connection types are identified in the messagetext.


FPEF505 Location name begins with a < andmust end with a > or *

ExplanationLocation names can be enclosed in ‘less than’ (<) and‘greater than’ (>) symbols. The name at the cursorposition did not end with a > or a *


FPEF506 This character is invalid. Validcharacters are A-Z, @, #, $, <, and*



FPEF507 This character is invalid. Validcharacters are A-Z, 0-9, @, #, $, _,and –



FPEF508 Location name begins with a < andmust end with a >

ExplanationLocation names can be enclosed in ‘less than’ (<) and‘greater than’ (>) symbols. The name at the cursorposition did not end with a >.


FPEF509 An * may not be followed by othercharacters

ExplanationAn * can only appear on its own without any followingcharacters.


FPEF510 This character is invalid. Validcharacters are A-Z, 0-9, @, #, $, _,–, * and .



FPEF511 This character is invalid. Validcharacters are A-Z, 0-9, @, #, $, <,and *



FPEF512 This character is invalid. Validcharacters are A-Z, 0-9, @, #, $,and *




FPEF600 Editing already in progress in thisISPF logical screen

ExplanationAn attempt was made to perform Data SetMaintenance, but the function was already active onthis ISPF logical screen. You can have only one DataSet Maintenance selection function active on a logicalscreen at a time.

User responseClose, then restart the application. If the problemrecurs, terminate the ISPF logical screen.

FPEF601 <V1>

ExplanationAn error was detected when opening a data set usingData Set Maintenance. This message is accompaniedby ISPF or TSO/E messages.

• <V1> is the ISPF or TSO/E message text.

User responseSee the OS/390® ISPF Services Guide or z/OS TSO/EMessages for specific message information. Correctthe errors indicated by the messages.

FPEF602 Member name should not bespecified

ExplanationThe correlation data set that is being used by Data SetMaintenance is sequential and does not require amember name.


FPEF603 Member name required when dataset is partitioned

ExplanationThe correlation data set which is being used by DataSet Maintenance is partitioned and requires a membername to be specified.


FPEF604 Data set must be partitioned

ExplanationThe DPMPARMS data set must be partitioned.


FPEF606 Data set record format must befixed

ExplanationThe correlation and DPMPARMS data sets must havefixed-length records.


FPEF607 Data set record format must bevariable

ExplanationThe exception threshold data set must have variable-length records.


FPEF608 An error occurred while updatingthe data set. ISPF message is:<V1>

ExplanationAn unexpected error occurred when updating the dataset. This can be accompanied by other messages.

• <V1> is the ISPF message text.

User responseCorrect the condition indicated by the other messagesand try again.


FPEF609 Member is being updated by you oranother user

ExplanationNone.

User responseWait until the member is available.

FPEF610 Offset field must be numeric in therange of 0 to 11

ExplanationNone.


FPEF611 Length field must be numeric inthe range of 1 to 8

ExplanationNone.


FPEF612 Length value required when offsetis specified

ExplanationNone.


FPEF613 Offset value required when lengthis specified

ExplanationNone.


FPEF614 Sum of offset and length cannotexceed 12 bytes

ExplanationNone.


FPEF616 Specify all blanks or all zeros fordefault translation

ExplanationNone.


FPEF617 Length field must be numeric inthe range of 0 to 8

ExplanationNone.


FPEF618 Error initializing correlationprocessing. Error detected inmember CORRDATA in data set<V1>

ExplanationAn error was detected in the correlation translationdata set.

• <V1> is the name of the data set.


User responseSee the previously issued messages to solve theproblem.

FPEF622 Generic * only allowed as the lastcharacter

ExplanationNone.



FPEF624 Compare must be '>' or '<'

ExplanationNone.


FPEF625 Value cannot be a negativenumber

ExplanationNone.


FPEF626 Value cannot be zero whencompare is '<'

ExplanationNone.


FPEF627 A value must be specified forwarning, problem, or both

ExplanationNone.


FPEF628 Warning must be less thanproblem when compare is '>'

ExplanationYou cannot specify a higher value for warning than forproblem when the operator is >.


FPEF629 Warning must be greater thanproblem when compare is '<'

ExplanationYou cannot specify a higher value for problem than forwarning when the operator is <.


FPEF630 DB2 names must begin with aletter

ExplanationNone.


FPEF631 Invalid character found in DB2name

ExplanationNone.


FPEF632 There is no entry following the onecurrently displayed

ExplanationYou have reached the last panel of exception fielddetails.

User responseNone.

FPEF633 There is no previous entry, this isthe first entry

ExplanationYou have reached the first panel of exception fielddetails.

User responseNone.

FPEF634 The format of the exceptionthreshold data set will beconverted to the current format


ExplanationNone.

User responseNone. If you wish to prevent the conversion, pressF12.

FPEF640 Location names should begin witha letter

ExplanationNone.


FPEF641 Invalid character found in locationname

ExplanationNone.


FPEF642 Enter either 1 or 2

ExplanationNone.


FPEF643 Package fields are not supportedper commit, minute, or secondbasis

ExplanationNone.


FPEF651 Logical record length should be atleast 184

ExplanationAn exception threshold data set must have a recordlength of 184 or greater.


FPEF652 Data set should be sequential orpartitioned

ExplanationAn exception threshold data set must be sequential orpartitioned.


FPEF653 Logical record length must be 80

ExplanationA data set has been specified for location orcorrelation translation data set maintenance whichdoes not have a logical record length of 80.


FPEF654 Unable to enqueue data set. ISPFmessage is: <V1>

ExplanationAn error occurred while attempting to enqueue thedata set requested for data set maintenance.



FPEF701 This value must be a percentage,for example 10.00 is 10%

ExplanationNone.


FPEF702 This is an incorrect SYOUTspecification for foregroundprocessing

ExplanationNone.



FPEF703 This is an input data set andcannot be directed to SYOUT

ExplanationNone.


FPEF704 This is an incorrect SYOUTspecification for backgroundprocessing

ExplanationNone.


FPEF990 The application identifier <V1> isincorrect

ExplanationYou are invoking an EXEC with a NEWAPPL of FPEF.You should not invoke this EXEC with the NEWAPPLkeyword.

• <V1> is FPEF.

User responseDelete the copy of FPEFPROF in your ISPF profile dataset, then invoke this EXEC again.

FPEF991 This application dialog isexecuting on an unsupportedrelease of ISPF

ExplanationYou are executing OMEGAMON XE for DB2 PE on arelease of ISPF before version 3 release 5.

User responseThe minimum requirement for the current OMEGAMONXE for DB2 PE version is ISPF 3.5.

FPEF992 The ISPF command table is notcurrent

ExplanationThe EXIT and CANCEL commands are not defined inthe ISPF command table ISPCMDS. The most commonreason for the missing commands is that in a priorrelease of ISPF (which did not have the commandsEXIT and CANCEL) the ISPCMDS command table wascustomized. When the updated release of ISPF wasinstalled, rather than customizing the new ISPCMDScommand table, the one for the previous release wascarried over.

User responseInstall the correct version of ISPCMDS and performwhatever customization is necessary.

FPEF993 The RKO2EXEC library is notavailable

ExplanationThe RKO2EXEC library has not been allocated to eitherthe SYSEXEC or SYSPROC files. This problem shouldonly occur in an MVS/XA environment.

User responseIf your environment is MVS/XA, ensure that theRKO2EXEC library (or its contents) is available in eitherthe SYSEXEC or SYSPROC files. If your environment isnot MVS/XA, then the FPEJINIT EXEC has beenincorrectly modified or the installation of OMEGAMONXE for DB2 PE is incomplete. See your systemprogrammer for assistance.

FPEF994 The application profile pool isunusable

ExplanationThe FPEFPROF member in your ISPF profile data setdoes not contain the name of the OMEGAMON XE forDB2 PE profile extension pool. This situation shouldonly occur when the FPEFPROF member was createdby an application other than OMEGAMON XE for DB2PE, or the product version of the FPEFPROF has beencorrupted.

User responseDelete the FPEFPROF member from your ISPF profiledata set and then restart OMEGAMON XE for DB2 PE.If the problem recurs, contact IBM support.

FPEF995 Incompatible application profilepool detected


ExplanationThe currently active OMEGAMON XE for DB2 PE profileextension pool is incompatible with the OMEGAMONXE for DB2 PE application being started. This canhappen when ISPF opens profile extension pools inshared mode, so the first opened pool is used by allsubsequent executions of OMEGAMON XE for DB2 PE.OMEGAMON XE for DB2 PE releases are onlybackward compatible, not forward compatible.

User responseStart the latest release level OMEGAMON XE for DB2PE application first, then start other OMEGAMON XEfor DB2 PE applications.

FPEF996 Incompatible code levelsdetected. The executable code is

release <V1>, whereas the non-executable code is release <V2>

ExplanationThe release level of the Host Online Monitorapplication executable code is not the same as therelease of the panels, messages, and tables.

• <V1> is the release of the executable code.• <V2> is the release of the panels, messages, and

tables.

User responseEnsure that the correct value has been specified forthe system LNKLST concatenation option during thecustomization of interactive defaults. Ensure also thatthe FPEJINIT EXEC procedure has been customizedcorrectly.

FPEI - I/O Activity report set messagesFPEI0001W I/O ACTIVITY IS MISSING THE

END RECORD FOR IFCID <V1>.EVENT IS BUFFER POOL READ

ExplanationThe beginning of the buffer pool read event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.

• <V1> is the begin-event record identificationnumber.

User responseNone.

FPEI0002W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS BUFFER POOL WRITE

ExplanationThe beginning of the buffer pool write event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0003W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS EDM POOL REQUEST

ExplanationThe beginning of the EDM pool request event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0004W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS BSDS/ACTIVE LOG READI/O

ExplanationThe beginning of the BSDS/active log Read I/O eventwas detected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0005W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS ACTIVE/ARCHIVE LOGNON-I/O WAIT


ExplanationThe beginning of the active/archive log non-I/O waitevent was detected during I/O activity reduction, andno matching end event was found. The record isignored.


User responseNone.

FPEI0006W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS ACTIVE LOG WRITE I/O

ExplanationThe beginning of the active log Write I/O event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0007W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS ARCHIVE LOG WRITEI/O

ExplanationThe beginning of the archive log Write I/O event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0008W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS ARCHIVE LOG READ I/O

ExplanationThe beginning of the archive log Read I/O event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0009W I/O ACTIVITY IS MISSING THEEND RECORD FOR IFCID <V1>.EVENT IS BSDS WRITE I/O

ExplanationThe beginning of the BSDS Write I/O event wasdetected during I/O activity reduction, and nomatching end event was found. The record is ignored.


User responseNone.

FPEI0100S THE SPECIFIED ORDERINGSEQUENCE IS NOT SUPPORTED.

ExplanationIf the ordering sequence contains PARTNBR togetherwith other criteria the buffer pool report will only beordered and created if PARTNBR is preceded byPAGESET.

User responseIf PARTNBR is your favourite criteria then specify anorder sequence that contains PAGESET beforePARTNBR. Then rerun the job.

FPEI0600S EXCEPTIONAL CONDITIONOCCURRED WHILE PROCESSINGI/O ACTIVITY. MAIN STORAGEALLOCATION FAILED



FPEI0610S EXCEPTIONAL CONDITIONOCCURRED WHILE PROCESSINGI/O ACTIVITY. MAIN STORAGERELEASE FAILED

ExplanationAn attempt to release main storage failed.



FPEI0750S PUT FUNCTION FAILED ONDDNAME <V1> WHILEEXTERNALIZING REDUCEDRECORDS

ExplanationAn error occurred when writing records to the I/Oactivity REDUCE work data set.



FPEI1241I I/O ACTIVITY REDUCE COMPLETE

ExplanationI/O activity REDUCE processing is completed.

User responseNone.

FPEI4000I NO DATA TO REDUCE FOR I/OACTIVITY

ExplanationThere was no data available for theIOACTIVITY(REDUCE) subcommand.

User responseCheck the INCLUDE/EXCLUDE and FROM/TOspecifications in REDUCE and GLOBAL.

FPEI4500S INITIALIZATION FAILED FOR I/OACTIVITY LIST. INSUFFICIENTSTORAGE AVAILABLE



FPEI4510S EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGI/O ACTIVITY LIST. INSUFFICIENTSTORAGE AVAILABLE



FPEJ - Installation and Configuration messagesFPEJ000 This field must be completed

ExplanationThe field at the cursor position must not be blank.


FPEJ001 Invalid name - type up to 8alphanumeric characters, the firstof which must be alphabetic

ExplanationThe value entered into this field is not valid.

User responseEnter an alphanumeric value with a length of up to 8characters where the first character is alphabetic.

FPEJ002 Invalid name - type up to 4alphanumeric characters, the firstof which must be alphabetic

ExplanationThe subsystem name is not valid.

User responseEnter an alphanumeric value with a length of up to 4characters where the first character is alphabetic.

FPEJ003 Invalid data set name - type one ormore qualifiers separated by


periods. Each qualifier must be upto 8 alphanumeric characters, thefirst of which must be alphabetic

ExplanationThe load library data set name is not valid.

User responseEnter a valid data set name into the field.

FPEJ004 Use '/' to select this option

ExplanationThe option was selected using a character other than aslash (⁄).

User responseEnter a slash (⁄) to select the option or leave theselection field blank.

FPEJ007 User requested CANCEL - nocustomization values have beensaved

ExplanationThe customization dialog was canceled by the user.The customization values remain unchanged.

User responseNone.

FPEJ008 Customization values have beensaved

ExplanationThe previous customization values have beenreplaced.

User responseNone.

FPEJ009 ISPF encountered an errorperforming a <V1> on the profilepool extension table (<V2>) in thedata set <V3>. The return codewas <V4>. The ISPF message was<V5>

ExplanationAn unexpected ISPF error occurred.

• <V1> is the name of the ISPF function.• <V2> is the name of the table.• <V3> is the name of the data set where the table

resides.• <V4> is the return code.• <V5> is the associated ISPF error message.

User responseEnsure that you are authorized to update the data setand try again. If the problem recurs, contact IBMsupport.

FPEJ010 The command that was entered isnot recognized

ExplanationThe customization dialog could not recognize thecommand entered.


FPEJ011 The indicated value has anincorrect number of decimal digits

ExplanationThe value typed into the field is not valid.


FPEJ012 The indicated value is notacceptable because it is higherthan the maximum permitted ornegative



FPEJ013 The indicated value is notacceptable because it is notnumeric



User responseEnter a valid numeric value.

FPEJ014 The Diagnosis Rules of Thumbhave not been saved

ExplanationThe user canceled the diagnosis rules of thumb dialogbut not the whole customization dialog. Allcustomization values except for the diagnosis rules ofthumb have been replaced.

User responseNone.

FPEJ015 ISPF encountered an errorperforming a <V1> on the profilepool extension table (<V2>) in thedata set <V3>. The return codewas <V4>. The ISPF message was<V5>. The parameters have notbeen saved

ExplanationAn unexpected ISPF error has occurred.

• <V1> is the name of the ISPF function.• <V2> is the name of the table.• <V3> is the name of the data set where the table

resides.• <V4> is the return code.• <V5> is the ISPF message.

User responseEnsure that you are authorized to update the data setand try again.

FPEJ016 The Diagnosis Rules of Thumbhave been saved

ExplanationThe previous rules-of-thumb values have beenreplaced.

User responseNone.

FPEJ017 The customization values have notbeen changed

ExplanationYou have not changed the customization values.

User responseNone.

FPEJ019 The <V1> module call was with thewrong key <V2>

ExplanationYou have invoked the OMEGAMON XE for DB2 PEactivation module using a not valid key.

• <V1> is the name of the module invoked.• <V2> is the key passed to the module.

User responseInvoke the OMEGAMON XE for DB2 PE activationmodule using the same key as provided in the execprocedure on the SMPE tape.

FPEJ020 Dynamic allocation of SYSIN workdata set failed. RC <V1>. ThePerformance Expert Try mode isnot activated

ExplanationThe OMEGAMON XE for DB2 PE activation module triesto dynamically allocate a temporary data set toddname SYSIN with disposition NEW. The MVS servicereturns with a bad return code. The activation moduleterminates. No action is performed.


User responseEnsure that standard dynamic allocation within aprogram works and that SYSIN can be used asddname.

FPEJ021 Dynamic allocation of DB2 PE loadlibrary <V1> failed. RC <V2>. ThePerformance Expert Try mode isnot activated

ExplanationThe OMEGAMON XE for DB2 PE activation module triesto dynamically allocate the OMEGAMON XE for DB2 PEload library to ddname SYSLIB with disposition SHR.The MVS service returns with a bad return code. Theactivation module terminates. No action is performed.

• <V1> is the name of the load library.



User responseEnsure that you enter the invocation exec fullyqualified and that the OMEGAMON XE for DB2 PE loadlibrary has the same high-level qualifiers as theinvocation exec.

FPEJ022 The module containing the Tryprogram authorization has beencorrupted. The PerformanceExpert Try mode of is not activated

ExplanationThe data on the activation module controlling the trymode is different from the data on the delivery tape.No action is performed.

User responseReinstall the product.

FPEJ023 The update of DB2 PerformanceExpert load library <V1> failed.The Performance Expert Try modeis not activated

ExplanationA fatal error has occurred. The reason of the failure isreported by one or more preceding MVS systemmessages.

• <V1> is the name of the load library.

User responseEnsure that OMEGAMON XE for DB2 PE is installedproperly as described in the program directory.Resolve the reason of the failure following the adviseof the MVS system messages.

FPEJ024 The Performance Expert Try modehas already been activated

ExplanationThe mask for the try mode has already been set by anearlier execution of this exec. No action is performed.

User responseIf OMEGAMON XE for DB2 PE functions can no longerbe processed because the try time has ended, contactthe person responsible for ordering OMEGAMON XE forDB2 PE.

FPEJ025 Open, Write, or Close to SYSINwork data set failed. RC <V1>. ThePerformance Expert Try mode isnot activated

ExplanationWhen trying to write to the temporary data setallocated to ddname SYSIN, the MVS data accessservices reported an error, which is indicated by thereturn code. No action is performed.


User responseCorrect the error that caused the MVS access servicesfailure.

FPEJ029 The Performance Expert Try modehas been successfully activated

ExplanationYou have set the try mode of OMEGAMON XE for DB2PE. All functions are available until the end of the trytime.

User responseNone.

FPEJ030 The unit group name has beensuccessfully changed to <V1>

ExplanationNone.

• <V1> is the new unit group name.

User responseNone.

FPEJ031 Module FPEUUNIT not found. Theupdate of the unit group namecould not be processed

ExplanationThe unit group name has not been changed.

User responseCheck the OBJ library and your link step for memberFPEUUNIT, which should be included in load moduleFPEUFUDA. Reinstall the TKANMOD library.


FPEJ032 The update of the unit group namehas failed. The unit group name<V1> is not activated

ExplanationThe unit group name could not be changed asrequested.

• <V1> is the requested new unit group name.

Possible reasons for the failure can be:

• No write access to the TKANMOD library.• A permanent I/O error occurred on the device where

the TKANMOD library resides.• The TKANMOD library is corrupted.

User responseCheck the access authority and change it if necessary,or reinstall the TKANMOD library. If the problemrecurs, contact IBM support.

FPEL - Locking report set messagesFPEL0600S EXCEPTIONAL CONDITION

OCCURRED DURING PROCESSINGOF LOCKING. MAIN STORAGEALLOCATION FAILED



FPEL0610S EXCEPTIONAL CONDITIONOCCURRED DURING PROCESSINGOF LOCKING. MAIN STORAGERELEASE FAILED



FPEL0750S PUT FUNCTION FAILED ONDDNAME <V1> WHILEEXTERNALIZING REDUCEDRECORDS

ExplanationAn error occurred when writing records to the lockingREDUCE work data set.



FPEL1241I LOCKING REDUCE COMPLETE

ExplanationLocking REDUCE processing is completed.

User responseNone.

FPEL1245I LOCKING <V1> COMPLETE. <V2>RECORDS WRITTEN TO DDNAME<V3>

ExplanationLocking function is completed.

• <V1> is the function type.• <V2> is the number of records written.• <V3> is the ddname to which the records are written.

User responseNone.

FPEL1246S UNSUCCESSFUL ATTEMPTWRITING TO FILE DATA SET FORLOCKING

ExplanationAn error occurred when writing to the File data set.


FPEL1247S UNSUCCESSFUL ATTEMPTWRITING TO THE SPREADSHEETDATA SET OF LOCKING

ExplanationAn error occurred when writing to the SPREADSHEETdata set.


User responseCheck for system messages in DPMLOG detailing theproblem.

FPEL4000I NO DATA TO PROCESS FORLOCKING

ExplanationThere was no data available for the locking function.

User responseCheck the INCLUDE/EXCLUDE and FROM/TOspecifications in GLOBAL and all specified LOCKINGfunctions (REDUCE, TRACE, and FILE).

FPEL4500S INITIALIZATION FAILED FORLOCKING LIST. INSUFFICIENTSTORAGE AVAILABLE



FPEL4510S EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGLOCKING LIST. INSUFFICIENTSTORAGE AVAILABLE



FPEM - Online Monitor messagesFPEM0005W Data not available. Monitor trace

may not be active

ExplanationThe DB2 monitor trace might not be active for the DB2subsystem to which you are currently connected.Monitor trace class 1 must be active for the OnlineMonitor to operate successfully.

User responseIf the monitor trace is not active, start the monitortrace. Class 1 is required; classes 2 and 3 are optional.

FPEM001 <V1> command not valid in thispanel. Valid commands are DB2,COLLECT, LOOK, REINIT,OPTIONS, and HISTORY

ExplanationThe command you entered is not available in thecurrent panel.

• <V1> is the command you entered.

User responseEnter one of the following commands:DB2

To enter a DB2 commandCOLLECT

To display the Report Data menu

LOOKTo display the Look Selections menu

REINITTo restart the exception processor

OPTIONSTo set default options

HISTORYTo display HISTORY status or invoke HISTORYmode.

FPEM002 Unrecognized command. Validcommands for this panel are DB2,COLLECT, LOOK, REINIT,OPTIONS, and HISTORY

ExplanationThe command you entered could not be recognized.


To enter a DB2 commandCOLLECT

To display the Report Data menuLOOK

To display the Look Selections menuREINIT

To restart the exception processor



HISTORYTo display HISTORY status or invoke HISTORYmode.

FPEM003 Jump selection <V1> is not valid.Enter a valid selection

ExplanationThe menu selection you entered was not valid.

• <V1> is the jump selection you entered.


FPEM004 Enter a valid selection

ExplanationThe menu selection you entered was not valid.


FPEM005 Data not available. Monitor tracemay not be active

ExplanationThe DB2 monitor trace might not be active for the DB2subsystem to which you are currently connected.Monitor trace class 1 must be active for the OnlineMonitor to operate successfully.

User responseIf the monitor trace is not active, start the monitortrace. Class 1 is required; classes 2 and 3 are optional.

FPEM0060W No history data found

ExplanationNo history data was found for the function beingmonitored. In the case of thread details, this messageis issued if the thread has terminated.

User responseNone.

FPEM0061W Partial history data returned

ExplanationNone.

User responseNone.

FPEM0062E Unable to allocate return area

ExplanationAn error occurred in the allocation of storage for thereturn area.

User responseSee your system programmer.

FPEM0063W Near-term history data is nolonger available. Current data nowbeing obtained

ExplanationNone.

User responseNone.

FPEM006 Enter 1 or 2

ExplanationNone.


FPEM0070E The server is not active

ExplanationNone.

User responseStart the server.

FPEM0071E You have been disconnected fromthe server

ExplanationNone.


User responseIf you require the history function, go to OPTIONS andselect a server if available, otherwise, no action isrequired.

FPEM0073E You have not been connected toDB2 yet

ExplanationNone.

User responseNone.

FPEM007 The Online Monitor is not active

ExplanationThe DB2, LOOK, or REINIT command has beenentered, but the Online Monitor is not currently active.

User responseActivate the Online Monitor.

FPEM008 Enter 1 (Mod) or 2 (Old)

ExplanationThe data set disposition must be 1 or 2.


FPEM009 Select only one item from the list

ExplanationMultiple item selections are not allowed.

User responseSelect one item from the list.

FPEM011 An unusual condition has occurredin one of the Collect facilitysubtasks. Check Collect Messagesfor subtask <V1>

ExplanationA problem has been detected in a collect facilitysubtask.

• <V1> is the name of the collect facility subtask.

User responseReview the collect facility message log and take theappropriate action.

FPEM012 An unusual condition has occurredin the Periodic Exception subtask.Check the Periodic ExceptionMessage Log

ExplanationA problem has been detected in the periodic exceptionsubtask.

User responseReview the periodic message log and take theappropriate action.

FPEM013 The Collect facility subtask <V1>has had an OP buffer overrun

ExplanationAn OP buffer overrun has occurred during theexecution of the collect facility subtask.


User responseNone. However, if OP buffer overflows occurfrequently, then the following ISPF profile poolvariables should be modified during installation of theOnline Monitor:MAIFIBUF

This variable defaults to 512 KB and representsthe OP buffer size for DB2 to use.

MAREADATThis variable defaults to 410 KB and representsthe OP buffer threshold value. When the OP bufferreaches this threshold value, DB2 notifies thesubtask which, in turn, will issue a READAcommand to copy the trace records.

FPEM014 An unusual condition has occurredin the exception notificationsubtask of the Collect facility

ExplanationThe exception notification subtask of the Collectfacility that checks for periodic exceptions andexception events has failed. Insufficient region size ofyour TSO/E session may be the primary cause of thisproblem.


User responseIncrease the region size of the TSO/E session orterminate concurrently running ISPF applicationsbefore trying to restart the Collect facility. If theproblem recurs, contact IBM support and quote anymessages that appear in the panel.

FPEM015 An error has occurred initializingthe Collect facility subtask <V1>

ExplanationA problem has been detected during initialization ofthe Collect facility subtask, because there wasinsufficient storage available.


User responseIncrease the region size and try again. If the problemrecurs, contact IBM support.

FPEM016 <V1> command not valid in thispanel. Valid commands areCOLLECT, LOOK, REINIT,OPTIONS, and HISTORY



User responseEnter one of the following commands:COLLECT



To restart the exception processorOPTIONS

To set default optionsHISTORY

To display HISTORY status or invoke HISTORYmode.

FPEM017 Unrecognized command. Validcommands for this panel areCOLLECT, LOOK, REINIT,OPTIONS, AND HISTORY


User responseEnter one of the following commands:COLLECT






FPEM018 DB2 command not allowedbecause it is already active

ExplanationYou must not invoke this DB2 command from a paneldisplayed by the DB2 command.

User responseExit the DB2 output panel, then reissue the DB2command.

FPEM019 Subtask <V1> was not attached(RC <V2>). The application cannotcontinue.

ExplanationOMEGAMON XE for DB2 PE stopped because an erroroccurred during the ATTACH of a subtask.

• <V1> is the number of the subtask that could not beattached:1

Periodic exceptions subtask2

Collect facility subtask A3

Collect facility subtask B4

Collect facility subtask C5

Collect facility subtask D6

Collect facility exceptions notification subtask7

Collect facility subtask for Buffer Pool Analyzer.• <V2> is the return code from the ATTACH macro.


User responseSee the z/OS MVS Programming: Authorized AssemblerServices Reference for an explanation of the returncode from the ATTACH macro.

FPEM020 This command is not availablefrom this function

ExplanationThe function you are in does not recognize thecommand entered.

User responseTry another command or exit the function.

FPEM021 Maximum DB2 command functionsexceeded

ExplanationThe maximum number of nested DB2 functions hasbeen exceeded.

User responseReturn to the Main Menu and resume the DB2function.

FPEM022 Internal error - DB2 commandoutput table not created

ExplanationAn internal error has been detected in the DB2command function.

User responseTry to issue the command again. If the problem recurs,contact IBM support.

FPEM024 Subsystem <V1> not available. RC<V2>, REASON <V3>

ExplanationA DB2 command has been issued, but the OnlineMonitor is not connected to DB2.

• <V1> is the DB2 subsystem ID.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the CAF reason code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for an

explanation of the return and reason codes todetermine why connection to DB2 failed, and respondaccordingly.

FPEM030 <V1> command not valid in thispanel. Valid commands are DB2,REINIT, OPTIONS, HISTORY, andCOLLECT




To enter a DB2 commandREINIT



To display history statusCOLLECT

To display the Report Data menu.

FPEM031 Unrecognized command. Validcommands for this panel are DB2,REINIT, OPTIONS, HISTORY, andCOLLECT

ExplanationAn unrecognized command was entered.


To enter a DB2 commandREINIT



To display history statusCOLLECT

To display the Report Data menu.

FPEM032 LOOK command not allowedbecause it is already active


ExplanationThe LOOK command cannot be invoked within theLOOK function.

User responseReturn to the LOOK selection menu to select the LOOKfunction required.

FPEM033 Invalid selection <V1>. Validselections are 1 through 3

ExplanationA not valid selection code was entered.

• <V1> is the selection you entered.


FPEM035 No periodic exception messageshave been written

ExplanationNone.

User responseNone.

FPEM036 No periodic exceptions haveoccurred

ExplanationNone.

User responseNone.

FPEM037 Selected exception does not matchcurrent SSID <V1>

ExplanationThe exception you wish to select does not occur in thissubsystem.

• <V1> is the DB2 subsystem ID.

User responseChange your subsystem to the SSID where theexception occurred by selecting Options on the OnlineMonitor Main Menu, and then DB2 Subsystem.

FPEM038 No display exceptions haveoccurred

ExplanationNone.

User responseNone.

FPEM039 Invalid selection <V1>. Validselections are 1 through 6

ExplanationThe selection made was not valid.

• <V1> is the invalid selection.

User responseEnter a valid selection.

FPEM040 Autodisplay activated. Refreshevery <V1> <V2>. Press ATTN toterminate

ExplanationAutodisplay has just been activated.

• <V1> is the interval duration.• <V2> is the interval unit in seconds or minutes.

User responseNone.

FPEM041 Autodisplay. Refresh every <V1><V2>. Press ATTN to terminate

ExplanationAutodisplay is active.

• <V1> is the AUTODISPLAY interval duration.• <V2> is the AUTODISPLAY interval unit in seconds or

minutes.

User responseTo cancel autodisplay, press the ATTN key.

FPEM042 Autodisplay terminated

ExplanationNone.


User responseNone.

FPEM043 Autodisplay interval must benumeric in the range 1 to 7200seconds or 1 to 120 minutes

ExplanationA not valid interval has been entered for the AUTOcommand.

User responseSpecify one of the following:

• 1 to 7 200 when seconds is the unit.• 1 to 120 when minutes is the unit.

FPEM044 Autodisplay units must beSECONDS or MINUTES or any validabbreviation

ExplanationAutodisplay units must be expressed in terms ofseconds or minutes.

User responseEnter SECONDS or MINUTES or any valid abbreviation.

FPEM045 Extra parameters following AUTOcommand

ExplanationThe autodisplay command accepts only twoparameters.

User responseSee Monitoring Performance from ISPF for AUTOcommand usage.

FPEM046 Autodisplay interval must benumeric in the range 1 to 7200seconds

ExplanationThe autodisplay interval is not within allowableboundaries.

User responseSpecify an autodisplay interval in the correct range.

FPEM047 Autodisplay interval must benumeric in the range 1 to 120minutes

ExplanationThe autodisplay interval is not within allowableboundaries.

User responseSpecify an autodisplay interval in the correct range.

FPEM048 Autodisplay activated. Refreshevery <V1> <V2>. History intervalis <V3> seconds. Press ATTN toterminate

ExplanationAutodisplay has just been activated.

• <V1> is the interval duration.• <V2> is the interval unit in seconds or minutes.• <V3> is the HISTORY interval in seconds.

User responseNone.

FPEM049 Autodisplay. Refresh every <V1><V2>. History interval is <V3>seconds. Press ATTN to terminate

ExplanationAutodisplay is active.

• <V1> is the AUTODISPLAY interval duration.• <V2> is the AUTODISPLAY interval unit in seconds or

minutes.• <V3> is the HISTORY interval in seconds.

User responseTo cancel autodisplay, press the ATTN key.

FPEM0500E Subsystem <V1> is invalid. CAF RC<V2>, REASON <V3>

ExplanationAn attempt was made to connect to a DB2 subsystemthat does not exist.

• <V1> is the invalid subsystem name.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the DB2 reason code.


User responseSpecify a valid DB2 subsystem ID for the MVS systemthat you are currently working on, using the globalparameters function.

FPEM0501E DB2 release is <V1>, DB2 loadlib(dsnload) release is <V2>

ExplanationThe release level of the DB2 subsystem is notcompatible with the DB2 load library currentlyallocated to your TSO/E session.

• <V1> is the DB2 release.• <V2> is the DSNLOAD release.

User responseBe sure that the DB2 load library allocated to yourTSO/E session is the same release level as the DB2subsystem that you are connected to. The DB2 loadlibrary must not be allocated using LIBDEF.

FPEM0502E DB2 subsystem <V1> is notavailable. CAF RC <V2>, REASON<V3>

ExplanationAn attempt was made to connect to a DB2 subsystemthat is valid, but is not currently running.

• <V1> is the name of the DB2 subsystem.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the CAF reason code.

User responseStart the DB2 subsystem or connect to a subsystemthat is already active.

FPEM0503E You are not authorized to accessDB2 subsystem <V1>

ExplanationYou do not have the access authority needed toconnect to the requested DB2 subsystem. The mostcommon cause is that you are not defined by RACF® ashaving access to the subsystem.

• <V1> is the subsystem ID of the DB2 subsystem inquestion.

User responseNotify your security administrator.

FPEM0505E You are not authorized to executeplan <V1>

ExplanationYou do not have the DB2 authority needed to executethe requested DB2 plan.

• <V1> is the DB2 plan name.


FPEM0506E Currently allocated DB2 versionnot supported by PerformanceExpert

ExplanationAn attempt was made to connect to a DB2 versionallocated to the user session that is not supported byyour OMEGAMON XE for DB2 PE. In general, a higherDB2 version is not supported by a lower version ofOMEGAMON XE for DB2 PE. Lower DB2 versions canbe supported. For further information on which DB2versions are supported by your OMEGAMON XE forDB2 PE, see the manuals of the OMEGAMON XE forDB2 PE version you are using.

User responseLeave the Host Online Monitor and allocate thelibraries of a supported DB2 version.

FPEM0507E Only one task in this ISPF logicalsession can be connected to DB2

ExplanationAn attempt has been made to start a second DSN orCall Attach Facility (CAF) connection to DB2 from oneISPF logical screen. This error may occur if youattempt to start a second Online Monitor session orstart, for example, SPUFI and a second Online Monitorsession in one ISPF logical screen.

User responseExit the second Online Monitor session.

FPEM051 <V1> command not valid in thispanel. Valid commands are DB2,LOOK, COLLECT, OPTIONS, andHISTORY





To enter a DB2 commandLOOK

To display the Look Selections menuCOLLECT

To display the Report Data menuOPTIONS


To display history status.

FPEM0510I No DB2 subsystem ID (SSID) hasyet been specified. Select theOptions function to specify asubsystem

ExplanationYou have not previously specified a DB2 subsystem IDin the Online Monitor global parameters panel.

User responseUse the global parameters function to supply a DB2subsystem ID.

FPEM0511E Nonzero CAF return code. RC<V1>, REASON <V2>

ExplanationA DB2 call attach error has been detected.

• <V1> is the return code.• <V2> is the reason code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the return and reason codes.

FPEM0512W SQL error <V1> received

ExplanationNone.

• <V1> is the SQL error code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed).

FPEM0515W Abends have stopped the monitortrace. Restart the trace

ExplanationAbends in DB2 have caused the DB2 monitor trace tostop.

User responseCheck the cause of the abend in DB2 and restart themonitor trace.

FPEM0516W MONITOR1, MONITOR2, orSYSADM authority is needed touse DB2 IFI

ExplanationYou do not have the authority needed to execute theDB2 IFI functions used by the Online Monitor. Yourequire MONITOR1, MONITOR2, or SYSADM privilege.


FPEM0517E IFCID <V1> is not valid/availableon this DB2 subsystem

ExplanationThe Online Monitor issued a request for an IFCID fromDB2 IFI, but the IFCID was not recognized by DB2.This should not happen on a normal DB2 subsystem.

• <V1> is the IFCID number.

User responseApply necessary DB2 maintenance.

FPEM0518E Nonzero IFI return code. RC <V1>,REASON <V2>

ExplanationA severe DB2 IFI error has been detected.

• <V1> is the DB2 return code.• <V2> is the DB2 reason code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for an


explanation of the return and reason codes. If theproblem recurs, contact IBM support.

FPEM0519E Performance Expert has beendisconnected from DB2 prior toCAF call. RC <V1>, REASON <V2>

ExplanationDuring execution the connection to DB2 has beenterminated. This might indicate some abnormalcondition in DB2.

• <V1> is the Call Attach Facility (CAF) return code.• <V2> is the CAF reason code.

User responseExamine the DB2 activity log to find out why theconnection was lost. For further information, see alsoDB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed).

FPEM0522E Invalid request passed to the DataMovement PC routine

ExplanationNone.


FPEM0525E Server User Manager task hasterminated due to errors.Connection and Exceptionfunctions are not available

ExplanationNone.


FPEM052 Unrecognized command. Validcommands for this panel are DB2,LOOK, COLLECT, OPTIONS, andHISTORY


User responseEnter one of the following commands:

DB2To enter a DB2 command


COLLECTTo display the Report Data menu


HISTORYTo display history status.


ExplanationNone.

• <V1> is the command entered.









To display history status.

FPEM0548W User Authorization exit returns nodata


ExplanationAccording to the authorization specified for your userID in the user authorization exit there is no data to bereturned to you.

User responseNone.

FPEM0549W Severe error occurred in UserAuthorization exit

ExplanationThe user authorization exit failed with a severe error.

User responseContact your system programmer.

FPEM055 Command not valid in this panel.Valid command is DB2.

ExplanationThe command you entered is not available in thecurrent panel. DB2 is the only valid command in thiscontext.

User responseUse DB2 to enter a DB2 command.

FPEM056 Unrecognized command. Validcommand for this panel is DB2.

ExplanationThe text you entered is not a recognized DB2 orOMEGAMON XE for DB2 PE command. The onlycommand you can use here is DB2.

User responseUse DB2 to enter a DB2 command.

FPEM057 The Collect Report Data facility isnot active

ExplanationThe OMEGAMON XE for DB2 PE Collect Report Datafunction is not active.

User responseActivate Collect Report Data.

FPEM060 No history data found

ExplanationNo history data was found for the function beingmonitored. In the case of thread details, this messageis issued if the thread has terminated.

User responseNone.

FPEM061 Partial history data returned

ExplanationNone.

User responseNone.

FPEM0610W Offset field must be numeric in therange of 0 to 11

ExplanationCorrelation name and correlation number offset fieldmust be numeric in the range of 0 to 11.

User responseCorrect the input record.

To avoid this error, use the maintain parameter datasets facility on the ISPF monitor to specify correlationname translation.

FPEM0611W Length field must be numeric inthe range of 1 to 8

ExplanationCorrelation name and correlation number length fieldmust be numeric in the range of 1 to 8.


FPEM0612W Length value required

ExplanationCorrelation name and correlation number length valueis required.



FPEM0613W Offset value required

ExplanationCorrelation name and correlation number offset valueis required.


FPEM0614W Sum of offset and length cannotexceed 12 bytes

ExplanationSum of offset and length cannot exceed 12 bytes forcorrelation name and correlation number.


FPEM0615W Connection type required

ExplanationNone.


FPEM062 Unable to allocate return area

ExplanationAn error occurred in the allocation of storage for thereturn area. The reason is that there is not enoughstorage assigned to the task to acquire storage for theDB2 interface return area for your Online Monitorrequests.

User responseAsk your system programmer to increase the regionsize of the Performance Expert Server task.

FPEM063 Mear-term history data is nolonger available. Current data nowbeing obtained

ExplanationNone.

User responseNone.

FPEM070 The server is not active

ExplanationNone.

User responseStart the server.

FPEM071 You have been disconnected fromthe server

ExplanationNone.

User responseIf you require the history function, go to OPTIONS andselect a server if available, otherwise, no action isrequired.

FPEM072 DYNALLOC returned return code<V1>, reason code x'<V2>', SMSreason code <V3>

ExplanationAn unusual condition occurred during data setallocation in a system that has SMS installed. The mostlikely reason for this error is the attempt to create adata set that already exists or the attempt to use adata set that does not exist.

• <V1> is the return code.• <V2> is the reason code.• <V3> is the SMS reason code.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) for anexplanation of the return code and reason code.Contact IBM support for an explanation of the SMSreason code, which is described in DFSMS⁄MVS Version1 Release 1 Diagnosis Reference for DFSMS DFP.


FPEM073 You have not been connected toDB2 yet

ExplanationNone.

User responseNone.

FPEM074 No data to display

ExplanationNo qualifications have been specified in the DCPARMS(Data Collector Parameter) data set for the Historyfunction.

User responseNone.

FPEM075 Data set not cataloged

ExplanationThe dynamic allocation routine was called to allocate adata set that was expected to already exist in thecatalog.

User responseCorrect the data set name to one that exists, or changethe disposition to 3 to allocate a new data set.

FPEM076 Specified volume or acceptablevolume not mounted

ExplanationThe specified volume or an acceptable volume is notmounted, and the user does not have volumemounting authorization. This message can be issued ifthe allocation exceeds the maximum allocation that isallowed by SMS. OMEGAMON XE for DB2 PE tries toallocate 100 blocks of primary space and 500 blocksof secondary space on SYSDA. The problem can becircumvented by pre-allocating the data set. Thismessage should be accompanied by a systemmessage indicating the volume that was requested.


FPEM077 DYNALLOC returned Return code<V1>, Reason code x'<V2>'

ExplanationAn unusual condition occurred during data setallocation.



FPEM078 Data set already exists

ExplanationYou cannot create a data set with this name.

User responseSpecify the name of a data set that does not exist.

FPEM079 Catalog Error: Data set nameconflicts with existing data setname or user is not authorized toperform the operation

ExplanationA catalog attempt was not successful.

User responseUse another data set name or see your systemprogrammer for assistance.

FPEM080 System abend occurred for <V1>.Abend code <V2>, reason code<V3>

ExplanationWhen performing I/O on the data set, a system abendoccurred. The data set is closed. Its data might be lost.

• <V1> is the data set name.• <V2> is the abend code.• <V3> is the reason code.

User responseSee MVS Messages and Codes for an explanation of theabend code and reason code.

FPEM0800I Task started at <V1> for DB2subsystem <V2>


ExplanationThe asynchronous Collect task has been started and iswaiting for the start trigger condition to be met.

• <V1> is the date and time when the task started.• <V2> is the DB2 subsystem.

User responseNone.

FPEM0801I Task stopped at <V1>

ExplanationThe asynchronous Collect task has stopped and iswaiting for the user to start the task again.

User responseNone.

FPEM0802E SQL return code –<V1> readingcatalog info, trace stopped

FPEM0803E Destination <V1> has becomeinactive

ExplanationThe OPx destination used for the trace facility hasbecome inactive, and data is no longer being written tothe trace data set. One possible cause is that all tracesthat had <V1> as their destination have been stopped.

• <V1> is the OPx destination.

User responseNone.

FPEM0804I FPEM0804I Task stop trigger is:<V1>

Explanation<V1> includes the following stop trigger criteria:

• By timestamp• By user request• By termination• By number of records• By IFCID• By number of IFCIDs• After START TRACE error• After READA error• After WRITE RECORD error

This message is often accompanied by anothermessage that describes the problem in detail and theappropriate course of action.

FPEM0806W FPEM0806W <V1> records are notwritten to <V2>. The maximumrecord length of one of theserecords is <V3>.

ExplanationThis message shows the number of records that is notwritten to the output data set.

• <V1> is the number of records that is not written tothe output data set.

• <V2> is the name of the output data set that is usedto collect the trace data.

• <V3> is the maximum length of the trace data recordthat is not written to the output data set.

This message is often accompanied by anothermessage that describes the problem in detail and theappropriate course of action.

User responseTo write the complete trace data to the output dataset, follow these steps:

1. Allocate a new output data set to collect the tracedata.

2. Increase the record length of the output data set toat least the maximum length of the trace datarecord that could not be written to the output dataset.

3. Restart the trace.

FPEM0807I The OP buffer high water mark is<V1>.

ExplanationDB2 fills the OP buffer that is assigned to the Collecttask. The Collect task issues a READA command toread the OP buffer. <V1> is the maximum number ofbytes used.

User responseNone.

FPEM081 I/O error occurred for <V1>.System information: <V2>


ExplanationWhen performing I/O on the data set, a system erroroccurred. The SYNAD exit was invoked. The data set isclosed and data might be lost.

• <V1> is the data set name.• <V2> is the system message produced by the

SYNADAF data administration macro.

User responseSee the message buffer format produced by theSYNADAF macro for a description of the error.

FPEM0811I Task start trigger is: <V1>

ExplanationThis message is accompanied by messagesFPEM0800I and FPEM0819I.

Depending on one of the following start triggers, DB2data is collected accordingly:Time

When the user-specified time is met.Periodic Exception

When the Periodic Exception task finds a field thatis in exception status, and if this field matches theuser-specified field.

Exception EventWhen the Data Server finds an exception eventthat matches the user-specified exception event.

Immediate StartImmediately.

FPEM0813I DB2 traces to <V1> started at<V2>

ExplanationThe Collect task start trigger criteria have been met,and the DB2 traces have been started. This message isaccompanied by one or both of the DB2 messagesDSNW130I and DSN9022I.

• <V1> is the OPn buffer that was allocated to thisCollect task by DB2, where n = 1 to 8. DB2 canallocate 1 to 8 buffers.

• <V2> is the date and time when the DB2 tracesstarted.

User responseNone.

FPEM0814I DB2 traces to <V1> stopped at<V2>

ExplanationThe DB2 traces have been stopped because one ormore Collect task stop trigger criteria have been met.

• <V1> is the OPn buffer that was allocated to thisCollect task by DB2, where n = 1 to 8. DB2 canallocate 1 to 8 buffers.

• <V2> is the date and time when the DB2 traces werestopped.

User responseNone.

FPEM0815I <V1> records written to '<V2>'

ExplanationThis message indicates the number of records writtenby the Collect subtask between the most recent DB2trace start and stop messages.

• <V1> is the number of records written to the outputdata set.

• <V2> is the name of the data set where the DB2trace data is to be written.

User responseNone.

FPEM0816E Collect data set is full

ExplanationThe Collect subtask cannot write any more records tothe output data set because it is full.

User responseIf you wish to collect more records, allocate a largerdata set and restart the Collect subtask. If required,reconfigure the task, for example, the start criteria.

FPEM0817E No free OP buffers available at<V1>

ExplanationAll OP buffers are in use, so the Collect subtask couldnot start any DB2 traces.

User responseRestart the Collect subtask when an OP bufferbecomes available.

FPEM0818E An error occurred starting the DB2traces above


ExplanationAn error occurred when the Collect subtask attemptedto start one or more DB2 traces.

User responseThis message is accompanied by a DB2 messagewhich explains the problem and determines the userresponse.

FPEM0819I Task description is: <V1>

Explanation<V1> is the name of the Collect subtask.

A default name is initially assigned to this subtask. Youcan change the default name on the main Collectfacility menu.

This message is always accompanied by messageFPEM0800I.

FPEM082 Error occurred during DYNALLOCde-allocation of <V1>. Return code<V2>, reason code <V3>

ExplanationWhen performing a dynamic data set de-allocation, anerror occurred.

• <V1> is the data set name.• <V2> is the return code.• <V3> is the reason code.


FPEM0820I <V1> buffer overflows occurred

ExplanationDB2 has filled up the OP buffer that is assigned to thisCollect subtask. This message is accompanied bymessage FPEM0821I, which indicates how manyrecords were lost because of the OP buffer being full.

• <V1> is the number of times DB2 has filled up theOP buffer since this Collect subtask was mostrecently started.

User responseIf OP buffer overflows occur frequently, then thefollowing ISPF profile pool variables should bemodified during installation of the Online Monitor:

MAIFIBUFThis variable defaults to 512 KB and representsthe OP buffer size for DB2 to use.


FPEM0821I <V1> records lost

ExplanationRecords got lost due to the OP buffer being full. Nomore records can be written until the OP buffer iscleared out by a DB2 READA command. This messageshould be accompanied by message FPEM0820I.

• <V1> is the number of records lost since this Collectsubtask was most recently started.

User responseIf OP buffer overflows occur frequently, then thefollowing ISPF profile pool variables should bemodified during installation of the Online Monitor:MAIFIBUF

This variable defaults to 512 KB and representsthe OP buffer size for DB2 to use.


FPEM0822E Error allocating Collect data set.Reason code <V1>

ExplanationThe output data set used by the Collect facility subtaskcould not be allocated.

• <V1> is the reason code which identifies why theallocation failed.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) todetermine the course of action to be taken.

FPEM0822E Error allocating Collect data set.Reason code <V1>


ExplanationThe output data set used by the Collect facility subtaskcould not be allocated.



FPEM0823E Error opening Collect data set withreturn code <V1>

ExplanationThe output data set used by the Collect facility subtaskcould not be opened.

• <V1> is the return code which identifies why theopen failed:4

The data set was opened successfully, butwarning messages were issued.

8The data set could not be opened.

12The data set was already opened.

User responseThis message is often accompanied by a systemmessage which details the problem and course ofaction. If the data set was already opened, ensure thatthe same data set is not used by another Collectsubtask you have started. If this is the case, then adifferent data set should be allocated to the Collectsubtask that failed.

FPEM0824E Error writing a record to the outputdata set with return code <V1>

ExplanationThe output data set used by the Collect facility subtaskcould not be written to.

• <V1> is the return code which identifies why the PUTfunction failed (8 indicates an error while writing tothe data set).

User responseThis error should be accompanied by a systemmessage detailing the problem and the course ofaction. Check the appropriate log information. If the

log indicates that the data set is full, define a largerdata set, use the OVERWRITE disposition on theTrigger Immediately panel (FPEMAP41), and select theSTART action again on the Collect Report Data panel(FPEMAP00).

FPEM0825E Error allocating Collect data set.Record length <V1> of <V2> isinappropriate. Length should be atleast 4092

ExplanationThe record length of the data set used to collect tracedata is less than 4 092. It is likely that the defaultrecord length of 6 233 was changed to the indicatedrecord length.

• <V1> is the record length of the data set used tocollect trace data.

• <V2> is the name of the data set used to collecttrace data.

User responseIncrease the record length to at least 4 092 and restartthe trace.

FPEM083 <V1> is full. The data set has beenclosed. Some data may be lost.Abend code <V2>, reason code<V3>

ExplanationWhen writing to a data set, a system abend occurreddue to insufficient space.



FPEM0832W GETMAIN FAILURE OF <V1> KBFOR READA BUFFER. RC <V2>

ExplanationAn error occurred in the allocation of storage for thereturn area. The reason is that there is not enoughstorage assigned to the data collector task to acquirestorage for the DB2 interface return area for yourOnline Monitor requests.


User responseAsk your system programmer to increase the regionsize of the Performance Expert Server task.

FPEM0834E NO READA BUFFER FREED FORREUSE. COLLECT REPORT DATA ISSTOPPED

ExplanationA problem has been detected during the initializationof the Collect facility subtask because there wasinsufficient storage available.

User responseIncrease the region size and try again. If the problemrecurs, contact IBM support.

FPEM084 Space abend occurred whileclosing <V1>. Some data may belost. Abend code <V2>, reasoncode <V3>

ExplanationWhile closing a data set, a system abend occurred dueto insufficient space. The data set is left in a closedstate.



FPEM085 A record was not added to <V1>because it was too long. The dataset is still open. Abend code <V2>,reason code <V3>

ExplanationA record with a length that is larger than the data setrecord length cannot be added to the data set.


User responseIf all records are needed, allocate a data set with alarger record length.

FPEM086 Error attempting to open data set

ExplanationAn error occurred while opening a data set.

User responseNone.

FPEM0860I Compressing started at <V1>

Explanation• <V1> is the start date and time.

FPEM0861I Compressing stopped at <V1>

Explanation• <V1> is the stop date and time.

FPEM0862E Error allocating data set forcompressed data. Reason code<V1>

ExplanationThe output data set used by the Collect facility subtaskcould not be allocated. Typical causes are: The dataset already exists, not enough space, or access isdenied.



FPEM0865E Error during data set compression.Reason code <V1>

User responseSee the TERSEMVS messages, which are usuallyfollowing message FPEM0866I, for possible reasons.

FPEM0866I STARTING TERSE <V1> <V2>

ExplanationMultiple messages from the TRSMAIN utility mightfollow, showing the exec parameters used.

If this message does not show a return code of 0,which indicates an error from the TRSMAIN utility,several TERSEMVS messages are followed.



FPEM0867E Compression will be not started.Reason code <V1>

User responseSee message FPEM0866I for possible reasons andactions.

FPEM087 Data set is already open

ExplanationNone.

User responseNone.

FPEM088 Space abend occurred whileclosing the Exception Log data set.Some data may be lost

ExplanationNone.

User responseNone.

FPEM089 Space abend occurred whileclosing the Exception File data set.Some data may be lost

ExplanationNone.

User responseNone.

FPEM090 Error occurred loading I/O module.Abend code <V1>, reason code<V2>

ExplanationWhen loading the I/O module, a system abendoccurred.

• <V1> is the abend code.• <V2> is the reason code.

User responseSee MVS Messages and Codes for a detailedexplanation of the abend code and reason code.

FPEM091 Insufficient storage available forI/O initialization

ExplanationWhen attempting to initialize I/O processing, there wasnot enough virtual storage available.

User responseIncrease the region size of the user’s TSO/E addressspace.

FPEM0914W Error attempting to write to theexception log

ExplanationAn error occurred when writing to the exception log.The log record was not written.

User responseSee the accompanied system message in theasynchronous message log for action.

FPEM0918W Threshold field <V1> is in error.Event <V2> is invalid

ExplanationThe Online Monitor detected a not valid event in theException Threshold data set.

• <V1> is the threshold field.• <V2> is the invalid event name you specified.

User responseSpecify one of the following event types:STAT

For statistics eventsTHRD

For thread activity eventsACCT

For accounting events.

FPEM0919W Threshold field <V1> is in error.The field is not valid forenvironment <V2>


ExplanationA batch-only field cannot be used in an onlineenvironment, and an online-only field cannot be usedin a batch environment.

• <V1> is the threshold field.• <V2> is the environment.

User responseIf the threshold data set is used in either batch oronline environment, delete references to fields thatare not applicable.

FPEM0920W Threshold field <V1> is in error.The field name is invalid

ExplanationThe Online Monitor detected a not valid field name inthe Exception Threshold data set.

• <V1> is the invalid field name.

User responseCorrect the error.

FPEM0921W Threshold field <V1> is in error.Field is invalid for DB2 <V2>

ExplanationThe field name is not valid for the release of the DB2subsystem to which you are connected.

• <V1> is the threshold field name.• <V2> is the release of the DB2 subsystem.

User responseEnter a valid field name.

FPEM0922W Threshold field <V1> is in error.Field is invalid for event <V2>

ExplanationThe field name specified in the Exception Thresholddata set does not correspond with the event (forexample, a statistics field was specified for a THRDevent).

• <V1> is the field name.• <V2> is the event.


FPEM092 DUMMY is not acceptable for thisdata set

ExplanationThe Exception Threshold data set must be specified.

User responseEnter the name of the valid data set.

FPEM093 <V1>

ExplanationAn error was detected allocating a data set. Thismessage is accompanied by a TSO/E message.

• <V1> is the TSO/E message.

User responseSee z/OS TSO/E Messages for specific messageinformation.

FPEM0938W Error attempting to write to theexception file

ExplanationAn error occurred when writing to the Exception Logfile. The log file record was not written.


FPEM0939E The Periodic Exception Processorhas terminated and cannot berestarted. Exit from the OnlineMonitor before retrying

ExplanationAn earlier error caused the periodic exceptionprocessor to terminate.

User responseExit from the Online Monitor before trying to start theperiodic exception processor again. If the problemrecurs, contact IBM support.

FPEM094 Data set organization (<V1>) of<V2> is inappropriate. Validvalues: <V3>


ExplanationThe specified data set has a not valid data setorganization. The required DSORG is physicalsequential (PS).

• <V1> is the specified data set organization (DSORG).• <V2> is the data set name.• <V3> is a list of valid data set organizations (DSORG).

User responseAllocate a data set with a PS organization.

FPEM0944I Periodic Exception Processorstarted at <V1>

ExplanationThe periodic exception processor is started.

• <V1> is the date and time at which the periodicexception processor started.

User responseNone.

FPEM0945I PERIODIC EXCEPTIONPROCESSOR STOPPED AT <V1>

ExplanationThe periodic exception processor is stopped.

• <V1> is the date and time at which the periodicexception processor stopped.

User responseNone.

FPEM095 Record format (<V1>) of <V2> isinappropriate. Record formatshould be variable

ExplanationThe specified data set has a not valid record format.The required format is variable (V) or variable blocked(VB).

• <V1> is the specified record format.• <V2> is the data set name.

User responseAllocate a data set with a V or VB record format.

FPEM096 Record length (<V1>) of <V2> isinappropriate. Length should be atleast <V3>

ExplanationThe specified data set has a record length (LRECL) thatis too small.

• <V1> is the specified LRECL.• <V2> is the data set name.• <V3> is the minimum LRECL for this file.

User responseCorrect the LRECL.

FPEM097 Member name should not bespecified when the data set issequential

ExplanationThe data set has been defined as sequential. Nomember name should be specified.

User responseSpecify the correct data set.

FPEM098 Member name should be specifiedwhen the data set is partitioned

ExplanationThe data set has been defined as partitioned. Amember name should be specified.

User responseSpecify the correct data set.

FPEM099 Internal error occurred - code is<V1>

ExplanationAn unexpected program error has occurred.

• <V1> is the internal error code.

User responseIf the problem recurs, contact IBM support and quotethe internal error code.

FPEM100 Unrecognized command. Validcommands for this panel areAUTO, REINIT, DB2, LOOK,


COLLECT, HISTORY, OPTIONS, andPURGE

ExplanationThe command you entered is not recognized.

User responseEnter one of the following commands:AUTO

To activate the autodisplay functionREINIT

To restart the exception processorDB2



To display the Report Data menuHISTORY

To display HISTORY status or invoke HISTORYmode


PURGETo purge a thread currently processing in the DB2subsystem.

FPEM101 <V1> command not valid in thispanel. Valid commands for thispanel are AUTO, REINIT, DB2,LOOK, COLLECT, HISTORY,OPTIONS, and PURGE







To display the Look Selections menu


HISTORYTo display HISTORY status or invoke HISTORYmode



FPEM102 The selected thread hasterminated. Details are no longeravailable

ExplanationNone.

User responseNone.

FPEM103 Insufficient storage available forthread processing

ExplanationWhen attempting to initialize the Thread Activitydisplay, there was not enough virtual storage available.


As a principle solution you can increase the size of theinternal storage area that the Online Monitor uses tohold data for the selected purpose. For moreinformation see Monitoring Performance from ISPF,Online Monitor options, Online Monitor Memory Usagewindow.

FPEM104 No locks are currently held orsuspended for this resource. If thethread you selected is no longeractive, values for that threadremain available and will not beaffected by refreshing this panel

ExplanationThe resource that the selected thread was holding, orwas in a suspended state against, is no longer held byany thread. It is possible that the selected thread hasterminated. However, because this panel displaysinformation about a resource, you can continue tomonitor the resource without losing the informationgathered when the thread details were last refreshed.


If you exit from this panel, the other panels relating tothe thread will be unchanged.

User responseNone.

FPEM105 The thread you selected no longerholds this resource. If the threadyou selected is no longer active,values for that thread remainavailable and will not be affectedby refreshing this panel

ExplanationThe resource that the selected thread was holding, orwas in a suspended state against, is no longer held bythat thread (another thread holds a lock which keepsyours out). It is possible that the selected thread hasterminated. However, because this panel displaysinformation about a resource, you can continue tomonitor the resource without losing the informationgathered when the thread details were last refreshed.If you exit from this panel, the other panels relating tothe thread will be unchanged.

User responseNone.

FPEM106 No threads were found matchingthe current qualify values

ExplanationThere are no threads available that match yourselection.

User responseChange the qualify values and try again, or keep tryingwith the selected qualify values.

FPEM107 Insufficient storage to returnlocking data. IFI RC <V1>,REASON <V2>

ExplanationThis warning message indicates that DB2 hasinsufficient storage to process more than 32 KB oflocking data. Up to 32 KB of locking data is returned.

• <V1> is the IFI return code.• <V2> is the reason code.

User responseNone. For further information, see DB2 Messages andCodes (or the corresponding manual of the DB2version you have installed).

FPEM108 Unrecognized command. Validcommands for this panel are SORT,QUALIFY, RESET, AUTO, REINIT,DB2, LOOK, COLLECT, HISTORY,OPTIONS, and PURGE

ExplanationThe command you entered is not recognized in thecurrent panel.

User responseEnter one of the following commands:SORT

To specify the order in which threads are displayedin this panel

QUALIFYTo limit the number of threads shown in this panel

RESETTo disable qualify and sort functions

AUTOTo activate the autodisplay function








FPEM109 <V1> command not valid in thispanel. Valid commands are SORT,QUALIFY, RESET, AUTO, REINIT,DB2, LOOK, COLLECT, HISTORY,OPTIONS, and PURGE


ExplanationThe command you entered is not valid in the currentpanel.


User responseEnter one of the following commands:SORT

To specify the order in which threads are displayedin this panel

QUALIFYTo limit the number of threads shown in this panel

RESETTo disable qualify and sort functions

AUTOTo activate the autodisplay function








FPEM110 Field order must be numeric in therange 1 to 15

ExplanationThe value entered is not within the valid range.


FPEM111 The same order has been specifiedfor more than one field

ExplanationAn attempt has been made to specify a sort with twofields at the same level.

User responseCheck the sort panel for the duplicate sort order.

FPEM112 Sort sequence must be specifiedas 1 (Ascending) or 2 (Descending)

ExplanationA not valid sort sequence has been entered.

User responseSpecify the sort sequence as 1 or 2.

FPEM113 Sort sequence must be specifiedas ASCENDING or DESCENDING orany valid abbreviation

ExplanationThe sort sequence has not been specified correctly.

User responseSpecify the sort sequence as ASCENDING orDESCENDING or any valid abbreviation.

FPEM114 Command contains anunrecognized field identifier. Validvalues are PRIMAUTH,PLANNAME, COLLECTION,PROGRAM, CORRELATION,CONNECT, CONNTYPE, REQLOC,STATUS, REQUESTS, C1ELAPSED,C1CPU, C2ELAPSED, C2CPU, andC3ELAPSED. Valid abbreviationscan be used

ExplanationThe command entered cannot be recognized.

User responseEnter one of the stated values or one of the applicableabbreviations.

FPEM115 Command contains an invalid fieldidentifier abbreviation. Theshortest permitted truncations arePRI, PL, COL, PRO, COR, CONNE,CONNT, REQL, S, REQU, C1E, C1C,C2E, C2C, and C3

ExplanationThe command entered cannot be recognized.


User responseEnter one of the stated values.

FPEM116 At least one order field must bespecified. To use the defaultparameters, cancel this panel anddeactivate the sort command if itis active

ExplanationNo order has been entered for the sort.

User responseSpecify a sort order or use the cancel function to exitthe panel.

FPEM117 More than 32 KB of locking dataexists. Only up to 32 KB of lockingdata can be returned. IFI RC <V1>REASON <V2>. See DB2 MSGS/CODES

ExplanationA DB2 limitation has been reached, and a maximum of32 KB of locking information is returned.

• <V1> is the DB2 IFI return code.• <V2> is the DB2 IFI reason code.

User responseNone. For further information, see DB2 Messages andCodes (or the corresponding manual of the DB2version you have installed).

FPEM118 The selected entry does notrepresent a thread

ExplanationYou have requested a thread display for an entry thatdoes not represent a thread.

User responseSelect only entries that represent threads.

FPEM120 The QUALIFY command acceptsone optional parameter, which canbe on or off or any validabbreviation

ExplanationNone.

User responseIf using a parameter with the Qualify command,ensure it is ON or OFF or any valid abbreviation.

FPEM121 Invalid character. Must bealphabetic

ExplanationA not valid character has been entered.

User responseEnter an alphabetic character.

FPEM122 At least one Thread Status mustbe specified

ExplanationNone.

User responseEnter a thread status.

FPEM123 At least one Thread Type must bespecified

ExplanationNone.

User responseEnter a thread type.

FPEM130 An SQL error has occurred. SQLCODE <V1>. As a result, someDBID/OBID translations may nothave been performed

ExplanationWhile trying to perform SQL functions, a failureoccurred.

• <V1> is the SQL code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) forinformation about the SQL code.

FPEM131 Unrecognized command. Validcommands for this panel areAUTO, REINIT, DB2, LOOK,COLLECT, HISTORY, OPTIONS,EXPLAIN, and PURGE


ExplanationThe command you entered is not recognized.






To display the Report Data menuHISTORY



EXPLAINTo explain the current SQL statement


FPEM132 <V1> command not valid in thispanel. Valid commands are AUTO,REINIT, DB2, LOOK, COLLECT,HISTORY, OPTIONS, EXPLAIN,and PURGE

ExplanationThe command you entered is not recognized in thecurrent panel.







To display the Report Data menu



EXPLAINTo explain the current SQL statement


FPEM133 <V1> command not valid for thisrelease of DB2

ExplanationThe specified command is not supported by the DB2subsystem you are connected to. The only validcommand is PURGE.

• <V1> is the unsupported command.

User responseNone.

FPEM134 No return area from DB2 toindicate the outcome of thecommand entered. IFI RC <V1>,REASON <V2>. See DB2 MSGS/CODES

ExplanationThe PURGE command has failed, and DB2 has notsupplied an explanation why, except for the returncode and reason code provided by the DB2 IFI facility.

• <V1> is the DB2 IFI return code.• <V2> is the DB2 IFI reason code.


FPEM135 A thread has to be selected for the<V1> command

ExplanationThe PURGE command must know which thread is to becanceled.

• <V1> is the PURGE command.


User responseSelect a thread from the list displayed when thePURGE command is entered.

FPEM136 No thread has been created forthis agent, so cannot be purged

ExplanationOnly threads performing work in DB2 can be canceledby the PURGE command.

User responseSelect a thread that is not in I⁄S status.

FPEM138 An SQL error has occurred. SQLCODE -805. The packagesFPEVDB2S, DGOVDB2S,DGOVSDBO, and DGOVSDOB mustbe rebound.

ExplanationWhile trying to perform SQL functions, a failureoccurred.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) forinformation about the SQL code.

FPEM140 Reset successful. Sort and qualifyare now off

ExplanationNone.

User responseNone.

FPEM141 Reset successful. Sort and qualifyare now off. Extra parametershave been ignored

ExplanationThe commands typed in after reset have been ignored.

User responseReenter the commands typed in after RESET.

FPEM142 No history data found. Selectedthread has terminated

ExplanationNone.

User responseNone.

FPEM200 Invalid command. Validcommands are AUTO, DB2, DELTA,HISTORY, INTERVAL, LOOK,COLLECT, OPTIONS, REINIT, andRESET



To activate the autodisplay functionDB2

To enter a DB2 commandDELTA

To view system-wide DB2 activity in time slicesHISTORY


INTERVALTo view an accumulation of statistics data from aspecified point in time





RESETTo revert to regular mode.

FPEM2006E The product installation isincomplete

ExplanationThe licence FMID is not correctly installed.



If OMEGAMON XE for DB2 PE, or OMEGAMON XE forDB2 PM, installed without errors, and you followed therecommended installation and customizationprocedures, and the problem persists, contact IBMsupport.

FPEM202 One or more fields have not beenformatted for display due to aninternal error. Fields markedwith ? are the fields not formatted- other fields have been formattedcorrectly

ExplanationAn internal error occurred when formatting data fordisplay. The fields that could not be formatted containa question mark.

User responseIf the problem recurs, contact IBM support.

FPEM203 Statistics interval processingstarted

ExplanationStatistics interval processing has been activated by theINTERVAL command.

User responseNone.

FPEM204 Statistics interval processingstopped by RESET command

ExplanationStatistics interval processing has been stopped by theRESET command. The data displayed on the Statisticspanel are the accumulated values since DB2 startup.

User responseNone.

FPEM205 Statistics delta processing started

ExplanationStatistics delta processing has been activated by theDELTA command.

User responseNone.

FPEM206 Statistics delta processingstopped by RESET command

ExplanationStatistics delta processing has been stopped by theRESET command. The data displayed on the Statisticspanel are the accumulated values since DB2 startup.

User responseNone.

FPEM207 Insufficient storage available forStatistics processing

ExplanationWhen attempting to initialize statistics, there was notenough storage available.


FPEM208 RESET command ignored - intervalor delta not active

ExplanationThe RESET function is valid only after startingStatistics Interval or Delta processing.

User responseNone.

FPEM209 Statistics Internal Error whileformatting buffer pools

ExplanationAn error occurred while formatting the buffer pooldata.

User responseThis is an internal error. If the condition recurs, contactIBM support and quote the internal error number.

FPEM210 Insufficient storage available fordelta processing


ExplanationThere was not enough storage available when Deltaprocessing was initialized.


FPEM211 Insufficient storage available forinterval processing

ExplanationThere was not enough storage available when Intervalprocessing was initialized.

User responseIncrease the virtual storage of the user’s TSO/Eaddress space.

FPEM212 Unrecognized command.Commands valid for statistics areAUTO, DB2, DELTA, HISTORY,INTERVAL, LOOK, COLLECT,OPTIONS, REINIT, and RESET



To activate the autodisplay functionDB2

To enter a DB2 commandDELTA

To view system-wide DB2 activity in time slicesHISTORY


INTERVALTo view an accumulation of statistics data from aspecified point in time





RESETTo revert to regular mode.

FPEM213 Autodisplay activated. Refreshevery <V1> <V2>. Press ATTN toterminate

ExplanationAUTODISPLAY is active.


User responseTo cancel AUTODISPLAY, press the ATTN key.

FPEM214 Autodisplay. Refresh every <V1><V2>. Press ATTN to terminate

ExplanationAUTODISPLAY is active.


User responseTo cancel AUTODISPLAY, press the ATTN key.

FPEM215 Statistics interval processingstarted. Extra parameters ignored

ExplanationParameters typed in the command line following theINTERVAL command have been ignored.

User responseNone.

FPEM216 Statistics interval processingstopped by RESET command.Extra parameters ignored

ExplanationParameters typed in the command line following theRESET command have been ignored.

User responseNone.


FPEM217 Statistics delta processing started.Extra parameters ignored

ExplanationParameters typed in the command line following theDELTA command have been ignored.

User responseNone.

FPEM218 Statistics delta processingstopped by RESET command.Extra parameters ignored

ExplanationParameters typed in the command line following theRESET command have been ignored.

User responseNone.

FPEM219 DB2 restart detected. Autodisplayterminated

ExplanationA DB2 restart has resulted in a new base time forcalculation of statistics by DB2.

User responseRestart Autodisplay if required.

FPEM220 DB2 restart detected. Autodisplayand delta processing terminated

ExplanationStatistics deltas cannot be calculated across a DB2restart.

User responseRestart Delta processing and Autodisplay if required.

FPEM221 DB2 restart detected. Deltaprocessing terminated

ExplanationStatistics deltas cannot be calculated across a DB2restart.

User responseRestart Delta processing if required.

FPEM222 DB2 restart detected. Autodisplayand interval processingterminated

ExplanationStatistics deltas cannot be calculated for an intervalspanning a DB2 restart.

User responseRestart Autodisplay and interval processing if required.

FPEM223 DB2 restart detected. Intervalprocessing terminated

ExplanationStatistics deltas cannot be calculated for an intervalspanning a DB2 restart.

User responseRestart interval processing if required.

FPEM229 Not all data displayed. Limitedsupport for: <V1>.

ExplanationNot all data returned by DB2 within IFCIDs aredisplayed on the Online Monitor panels.

• <V1> is the reason for the limitation

The following list shows the keywords for the reasons:Multiple IFCID 2

For buffer pool information DB2 10 returns one ormore IFCIDs 2. Only information from the firstIFCID 2 is displayed on the panels. Further IFCIDs2 are ignored.

User responseNone.

FPEM250 Invalid date. Required format is:<V1>

ExplanationThe date entered is not valid.

• <V1> is the valid date format.

User responseEnter a valid date.

FPEM251 Invalid time. Required format is:HH:MM:SS


ExplanationThe time entered is not valid.

User responseEnter a valid time.

FPEM252 History Date/Time is in the future

ExplanationHistory date and time must be in the past.

User responseReenter the date and time.

FPEM253 History is not active

ExplanationA history function could not be used because you arenot connected to an active the Data Server. To usehistory, a server must be installed for the DB2subsystem you are using.

User responseSelect the Options panel from the Online Monitor mainmenu. Select the DB2 Subsystem panel and check thatthe Data Server for your DB2 subsystem has beenstarted. If necessary, start the appropriate server andthen reenter the panel. Connect to the server byselecting it from the subsystem list.

FPEM254 History time is invalid. Requiredformat is: HH:MM:SS

ExplanationThe history time entered is not valid.

User responseEnter a valid history time.

FPEM255 History date is invalid. Requiredformat is: <V1>

ExplanationThe history date entered is not valid.

• <V1> is the valid history date format.

User responseEnter a valid history date.

FPEM256 Syntax error in HISTORYcommand. Valid formats are:HISTORY, HISTORY BACK,HISTORY FORWARD, HISTORYOFF, HISTORY <V1> HH:MM:SS,HISTORY <V2>, and HISTORYHH:MM:SS

ExplanationNone.

• <V1> is the date format.• <V2> is the date format.

User responseEnter a valid HISTORY command.

FPEM257 Error in HISTORY command. Date/Time entered is in the future

ExplanationHistory date and time must be in the past.

User responseReenter the date and time.

FPEM301 Group buffer pool <V1> has beendeleted

ExplanationGroup buffer pool information could not be refreshed.

• <V1> is the name of the group buffer pool.

User responseNone.

FPEM302 DPMOUT record has not formattedsuccessfully

ExplanationA severe error has occurred during formatting of theDPMOUT record.

User responseThis is an internal error. If the condition recurs, contactIBM support.

FPEM303 ISPF variables have not formattedsuccessfully


ExplanationA severe error has occurred during formatting of ISPFvariables.

User responseThis is an internal error. If the condition recurs, contactIBM support and quote the internal error number.

FPEM304 Insufficient storage available forDPMOUT record formatting

ExplanationWhen attempting to allocate storage for recordformatting, the TSO/E region size was too small.


FPEM307 System Parameters internal error<V1>

ExplanationNone.


User responseIf the problem recurs, contact IBM support and quotethe internal error code.

FPEM308 Insufficient storage during SystemParameters initialization

ExplanationThere is insufficient storage for system parametersuse.


FPEM309 Buffer pool <V1> has been deleted

ExplanationBuffer pool information could not be refreshed.

• <V1> is the name of the buffer pool.

User responseNone.

FPEM404 Monitor write function disabled

ExplanationThe monitor write function was deactivated by theglobal parameters function.

User responseNone.

FPEM405 Monitor write function enabled

ExplanationThe monitor write function was activated by the globalparameters function.

User responseNone.

FPEM411 Enter valid subsystem ID

ExplanationThe DB2 subsystem ID contains invalid characters.

User responseEnter a valid DB2 subsystem ID.

FPEM412 Enter valid data set name

ExplanationThe field does not contain a valid data set name.


FPEM413 Enter 1 or 2

ExplanationNone.


FPEM414 Enter a valid Plan Name

ExplanationNone.


User responseEnter a valid plan name.

FPEM415 Select only one server from the list

ExplanationNone.

User responseSelect one from the list.

FPEM416 Enter 1, 2, or 3

ExplanationA not valid number was entered into the dispositionfield.

User responseEnter 1, 2, or 3.1

The current data is appended to previous data.2

The current data replaces any previous data.3

The data set is allocated for the user.

FPEM420 Memory size must be numeric inthe range 1 to 4 (in MB)

ExplanationYou specified a value that is not allowed.

User responseSpecify either 1, 2, 3, or 4.

FPEM500 Subsystem <V1> is invalid. CAF RC<V2>, REASON <V3>

ExplanationAn attempt was made to connect to a DB2 subsystemthat does not exist.

• <V1> is the invalid subsystem name.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the DB2 reason code.

User responseSpecify a valid DB2 subsystem ID for the MVS systemthat you are currently working on, using the globalparameters function.

FPEM501 DB2 release is <V1>, DB2 loadlib(dsnload) release is <V2>

ExplanationThe release level of the DB2 subsystem is notcompatible with the DB2 load library currentlyallocated to your TSO/E session.

• <V1> is the DB2 release.• <V2> is the DSNLOAD release.

User responseBe sure that the DB2 load library allocated to yourTSO/E session is the same release level as the DB2subsystem that you are connected to. The DB2 loadlibrary must not be allocated using LIBDEF.

FPEM502 DB2 subsystem <V1> is notavailable. CAF RC <V2>, REASON<V3>

ExplanationAn attempt was made to connect to a DB2 subsystemthat is valid, but is not currently running.

• <V1> is the name of the DB2 subsystem.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the CAF reason code.

User responseStart the DB2 subsystem or connect to a subsystemthat is already active.

FPEM503 You are not authorized to accessDB2 subsystem <V1>

ExplanationYou do not have the access authority needed toconnect to the requested DB2 subsystem. The mostcommon cause is that you are not defined by RACF ashaving access to the subsystem.

• <V1> is the subsystem ID of the DB2 subsystem inquestion.


FPEM504 The server subsystem <V1> is notpresent. Performance Expert maynot be installed correctly


ExplanationThe Performance Expert subsystem has not beeninstalled correctly.

• <V1> is the server subsystem ID.

User responseCheck the subsystem ID or reinstall correctly.

FPEM505 You are not authorized to executeplan <V1>

ExplanationYou do not have the DB2 authority needed to executethe requested DB2 plan.

• <V1> is the DB2 plan name.


FPEM506 Currently allocated DB2 versionnot supported by DB2 PE

ExplanationAn attempt was made to connect to a DB2 versionallocated to the user session that is not supported byyour OMEGAMON XE for DB2 PE. In general, a higherDB2 version is not supported by a lower version ofOMEGAMON XE for DB2 PE. Lower DB2 versions canbe supported. For further information on which whichDB2 versions are supported by your OMEGAMON XEfor DB2 PE, see the manuals of the OMEGAMON XE forDB2 PE version you are using.

User responseLeave the Online Monitor and allocate the libraries of asupported DB2 version.

FPEM507 Only one task in this ISPF logicalsession can be connected to DB2

ExplanationAn attempt has been made to start a second DSN orCall Attach Facility (CAF) connection to DB2 from oneISPF logical screen. This error may occur if youattempt to start a second Online Monitor session orstart, for example, SPUFI and a second Online Monitorsession in one ISPF logical screen.

User responseExit the second Online Monitor session.

FPEM508 DB2 subsystem <V1> is stopping,please end your session

ExplanationThe DB2 subsystem is terminating.

• <V1> is the name of the DB2 subsystem.

User responseEnd your session.

FPEM509 DB2 subsystem <V1> isabnormally terminating, pleaseend your session

ExplanationThe DB2 subsystem is abnormally terminating.

• <V1> is the name of the DB2 subsystem.

User responseEnd your session.

FPEM510 No DB2 subsystem ID (SSID) hasbeen specified. Select the Optionsfunction to specify a subsystem

ExplanationYou have not previously specified a DB2 subsystem IDon the Online Monitor panels.

User responseSelect Options, then DB2 Subsystem to supply a DB2subsystem ID.

FPEM511 Nonzero CAF return code. RC<V1>, REASON <V2>

ExplanationA DB2 call attach error has been detected.



FPEM512 SQL error <V1> received


ExplanationNone.


User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed).

FPEM513 Internal error <V1> while adding amessage to the DB2I queue

ExplanationNone.



FPEM514 You cannot change the DB2subsystem while trace is active

ExplanationNone.

User responseEither wait until the trace has completed, or stop thetrace. Then change to the new DB2 subsystem.

FPEM515 Abends have stopped the monitortrace. Restart the trace

ExplanationAbends in DB2 have caused the DB2 monitor trace tostop.

User responseCheck the cause of the abend in DB2 and restart themonitor trace.

FPEM516 MONITOR1, MONITOR2, orSYSADM authority is needed touse DB2 IFI

ExplanationYou do not have the authority needed to execute theDB2 IFI functions used by the Online Monitor. Yourequire MONITOR1, MONITOR2, or SYSADM privilege.


FPEM517 IFCID <V1> is not valid/availableon this DB2 subsystem

ExplanationThe Online Monitor issued a request for an IFCID fromDB2 IFI, but the IFCID was not recognized by DB2.This should not happen on a normal DB2 subsystem.

• <V1> is the IFCID number.

User responseApply necessary DB2 maintenance.

FPEM518 Nonzero IFI return code. RC <V1>,REASON <V2>

ExplanationA severe DB2 IFI error has been detected.

• <V1> is the DB2 return code.• <V2> is the DB2 reason code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the return and reason codes. If theproblem recurs, contact IBM support.

FPEM519 The connection to DB2 was lostprior to CAF call. RC <V1>,REASON <V2>

ExplanationOMEGAMON XE for DB2 PE lost the connection to DB2.


User responseExamine the DB2 activity to determine the cause ofthe disconnection. For further information, see alsoDB2 Messages and Codes (or the corresponding DB2version you have installed).

FPEM520 UDA allocation failed. Connectionto server failed. Connection will bemade to DB2

ExplanationNone.


User responseCheck the Data Server log for error messages. If theproblem recurs, contact IBM support.

FPEM521 SRB allocation failed. Connectionto server failed. Connection will bemade to DB2

ExplanationNone.


FPEM522 Invalid request passed to the DataMovement PC routine

ExplanationNone.


FPEM524 No connect or disconnect routineavailable

ExplanationNone.


FPEM525 Server User Manager task hasterminated due to errors.Connection and Exceptionfunctions are not available

ExplanationNone.


FPEM526 Server internal error. CODE <V1>,REASON <V2>



• <V2> is the internal reason code.

User responseCheck the Data Server log for preceding messages orabends. If the problem cannot be corrected andrecurs, contact IBM support.

FPEM527 Server DIV internal error. CODE<V1>




FPEM528 Server HISTORY internal error.CODE <V1>




FPEM529 TCB token storage could not beallocated. Connection to serverfailed. Connection will be made toDB2



FPEM530 UDA allocation failed




FPEM531 SRB allocation failed



FPEM532 You are not authorized to connectto the server

ExplanationYou do not have MONITOR1, MONITOR2, or SYSADMauthority.

User responseObtain these authorities.

FPEM533 SQL reason code of <V1> wasreceived

ExplanationA negative SQL code was entered while the server waschecking user authorities.

• <V1> is the SQL reason code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the SQL reason code.

FPEM534 Invalid request passed to the DataMovement PC routine



FPEM535 You are not authorized to connectto the selected maintenanceserver

ExplanationYou are not in the AdminUser list for this server.

User responseAdd your user ID to the AdminUser list.

FPEM536 You are not authorized to connectto the server, possibly because theMonitor Trace is not active

ExplanationYou were not granted authorization to connect to DB2.If you are a SYSADM, the system could not determinethis due to a missing 106 IFCID.

User responseIf you are a SYSADM, start the monitor trace, then youcan connect as normal. Otherwise you do not have therequired authorization to connect.

FPEM538 TCB token storage could not beallocated



FPEM539 Unknown return code set by theserver


User responseCheck the console messages. If the problem cannot becorrected and recurs, contact IBM support.

FPEM540 Subsystem internal error. SSIreturn code <V1>



• <V1> is the subsystem Interface (SSI) return code.

User responseCheck that the subsystem is installed correctly.

FPEM541 Subsystem internal error. SSI wasable to pass the request to thesubsystem but received SSOBreturn code <V1>


• <V1> is the SSOB return code.

User responseEnsure that the subsystem is installed correctly.

FPEM542 Subsystem internal error due toserver not of matching type toswap subsystems



FPEM543 Subsystem internal error due to<V1> not attached to any server




FPEM544 Subsystem internal error.Unknown return code <V1>




FPEM545 Error during Disconnect fromserver PC routine. Return code<V1>




FPEM546 The area for handling all IFCIDrecords is not large enough. <V1>IFCID records are SUPPRESSED

ExplanationSome IFCID records are ignored by the thread displayfunction. In case of thread summary display, not allthreads are shown. In thread detail, the missinginformation adheres to locked resources. Theinformation SUPPRESSED is in ascending importanceof locked resources: single held locks, multiple heldlocks, locks with suspensions.

• <V1> is the number of records ignored.

User responseIn case of thread summary, select the appropriatequalification, which shows the threads of interest butreduces the amount of IFCID data.

As a principle solution you can increase the size of theinternal storage area that the Online Monitor uses tohold data for the selected purpose. For moreinformation see Monitoring Performance from ISPF,Online Monitor options, Online Monitor Memory Usagewindow.

FPEM547 Nonzero IFI return code. RC 4,REASON 00E60802. The IFCIDreturn area is not large enough toaccommodate all records fromREADS

ExplanationSome IFCID records are ignored by the thread displayfunction. In case of thread summary display, not allthreads are shown. In thread detail, the missinginformation adheres to locked resources. RC 4 andREASON 00E60802 are the return code and reasoncode from the DB2 READS call.


User responseIn case of thread summary, select the appropriatequalification, which shows the threads of interest butreduces the amount of IFCID data.

FPEM550 Function <V1> is not supported forsubsystem <V2> DB2 <V3>.

ExplanationThe release level of the DB2 subsystem is notsupported by this version of OMEGAMON for Db2 PE.

<V1> denotes the unsupported function.<V2> denotes the ID of the subsystem.<V3> denotes the DB2 version.

The following list shows the keywords for the affectedfunctions:THREAD

Display Thread ActivitySTATISTIC

Display StatisticsSYSPARM

Display System ParametersEXCEPTION

Control Exception ProcessingEXPLAIN

ExplainLOOK

Command LOOK to list exceptionsDB2

Command DB2 to submit DB2 commands

User response:None.

FPEM600 The collect subtask "<V1>" hasterminated

ExplanationThe collect subtask has terminated.

• <V1> is the collect subtask.

User responseExit from the Online Monitor before trying to start thecollect subtask again. If the problem recurs, contactIBM support.

FPEM601 The exception processor subtaskhas terminated

ExplanationThe exception processor has terminated.

User responseExit from the Online Monitor before trying the functionagain. If the problem recurs, contact IBM support.

FPEM602 The collect exception notificationsubtask has terminated

ExplanationThe collect exception notification subtask hasterminated. Insufficient region size of your TSO/Esession may be the primary cause of this problem.

User responseIncrease the region size of the TSO/E session orterminate concurrently running ISPF applicationsbefore trying to restart the collect exceptionnotification subtask again. If the problem recurs,contact IBM support.

FPEM650 Insufficient storage

ExplanationThere is not sufficient virtual storage available toperform a diagnosis.

User responseIncrease the amount of storage.

FPEM651 Diagnosis requires elapsed timesfor DB2 suspensions. These arenot present or zero. Accounting orMonitor classes 2 and 3 may not beactive or the thread may not haveexperienced suspensions

ExplanationThere are minimum data requirements to perform adiagnosis. This message occurs if accounting ormonitor classes 2 and 3 are not started or if they arestarted but no suspensions exist.

User responseStart the DB2 monitor or Accounting trace for therequired classes.

FPEM652 The thread must have performedsome buffer activity before it canbe diagnosed

ExplanationThere are minimum data requirements to perform adiagnosis. In this case, some areas of the trace data


provided by DB2 are empty due to insufficient bufferactivity by the thread.

User responseThe thread is not diagnosable. This applies, forexample, if data regarding the use of buffer pools doesnot yet exist.

FPEM654 Unrecognized command. Validcommands for this panel areREINIT, DB2, LOOK, EXPLAIN,COLLECT, and OPTIONS



User responseEnter one of the following commands:REINIT



To display the Look Selections menuEXPLAIN

To explain the current SQL statementCOLLECT


To set default options.

FPEM655 No command allowed for thispanel

ExplanationYou have entered a command, that is not allowed forthis panel.

User responseSelect a thread or press a valid function key, but do notenter a command.

FPEM680 Please wait. Invoking Explain ...

ExplanationOnline Monitor Explain is being invoked.

User responseNone.

FPEM681 Valid selection characters are:<V1>

ExplanationAn SQL statement can only be selected by using a ⁄ or acountry-designated character.

User responseUse either ⁄ or S to select the statement to beexplained.

FPEM682 Valid choices are: 1 for yes, 2 forno

ExplanationOnly 1 or 2 can be used in this field. 1 indicates thatthe Options panel is to be displayed every time. 2indicates that the Options panel is only displayed ifyou enter explain options.

User responseNone.

FPEM683 Only valid optional parameter forExplain is 'OPTIONS'

ExplanationThe only valid parameter for the EXPLAIN command isOPTIONS.

User responseEnter either explain or explain options.

FPEM684 Only 1 SQL statement can beselected for Explain

ExplanationMore than one SQL statement has been selected forExplain from the summary panel.

User responseSelect only one SQL statement to be explained.

FPEM685 Range commands incomplete orconflicting


ExplanationThe range commands E, En, or EE have been enteredincorrectly.

User responseSee Monitoring Performance from ISPF for adescription of proper usage of the range commands.

FPEM686 No explainable SQL statementsfound in source code

ExplanationNo SQL statements eligible for Explain were found inthe source module.

User responseSee Monitoring Performance from ISPF for adescription of the SQL statements that are eligible forExplain.

FPEM687 No SQL statements eligible forExplain found in source

ExplanationNo SQL statements eligible for Explain were found inthe range of the specified source lines.

User responseSee Monitoring Performance from ISPF for adescription of the SQL statements that are eligible forExplain, and alter the range of the Explain to includeeligible SQL statements.

FPEM688 SQL statement found that isgreater than the maximum size

ExplanationAn SQL statement greater than the defined maximumhas been detected.

User responseReduce the size of the statement at cursor position.

FPEM691 Only valid command is 'OPTIONS'

ExplanationA command other than 'OPTIONS' has been enteredon the SQL statement summary panel.

User responseUse the OPTIONS command for altering the SourceExplain options.

FPEM692 Error <V1> during ISPF tableinitialization

ExplanationAn error occurred during processing of an ISPF tablecommand.


User responseEnsure that the ISPF table libraries are allocated andthat the allocated libraries are not full.

FPEM693 Error <V1> during ISPF panelprocessing

ExplanationAn error occurred during processing of an ISPF panel.


User responseEnsure that the ISPF panel libraries are allocated.

FPEM694 SQL text not loaded. Problemreading text from ISPF table

ExplanationAn error has occurred while loading an SQL statementfrom an ISPF table in Online Monitor Explain.


User responseEnsure that the ISPF table libraries are correctlyallocated.

FPEM700 Command <V1> is not valid here.Valid commands are DB2, LOOK,COLLECT, REINIT, OPTIONS, andHISTORY







To display the Report Data menuREINIT



To display HISTORY status.

FPEM701 Command <V1> is not recognized.Valid commands are DB2, LOOK,COLLECT, REINIT, OPTIONS, andHISTORY


• <V1> is the unrecognized command.




To display the Report Data menuREINIT




FPEM702 Error connecting to <V1>. SQLCODE <V2>

ExplanationAn attempt to connect to a remote server failed.

• <V1> is the remote server.• <V2> is the SQL code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the stated SQL code and contact yoursystem programmer.

FPEM703 Error resetting connection to<V1>. SQL CODE <V2>

ExplanationAn attempt to reset connection to a remote serverfailed. Online Monitor Explain is still connected to thecurrent server.

• <V1> is the remote server.• <V2> is the SQL code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the stated SQL code.

FPEM704 Error setting current SQLID. SQLCODE <V1>

ExplanationAn attempt to set the current SQLID failed.



FPEM705 Error setting current degree. SQLCODE <V1>

ExplanationAn attempt to set the current degree failed.



FPEM706 Unexpected SQL error. SQL CODE<V1>

ExplanationAn unexpected SQL error occurred.




FPEM707 Error locating current degree valuefor DBRM/package. SQL CODE<V1>. Current degree setting willdefault to 1

ExplanationAn attempt to extract the degree from the systemcatalogs for the DBRM⁄package returned an error. Thecurrent degree setting defaults to 1.



FPEM708 Error setting Current Degree. SQLCODE <V1>. Processing tocontinue

ExplanationAn attempt to set the current degree for Explain of aDBRM package returned an error. Processingcontinues without the current degree being set to thevalue extracted from the system catalogs for theDBRM package.



FPEM710 Enter a selection from 1 to 4

ExplanationNone.

User responseEnter a valid number.

FPEM711 There are no matching rows intable <V1>

ExplanationNo rows were found that match your selection criteria.

• <V1> is the table name.

User responseChange the selection criteria.

FPEM712 The table <V1> could not beaccessed

ExplanationNone.


User responseNone.

FPEM713 Select just one row from the list ofplan table entries

ExplanationNone.

User responseSelect only one row.

FPEM714 The query number must benumeric or blank

ExplanationNone.

User responseEnter a valid query number, or blank to use the defaultquery number.

FPEM715 Select just one package from thelist

ExplanationNone.

User responseSelect only one package from the list.

FPEM716 Select just one statement from thelist


ExplanationNone.

User responseSelect only one statement from the list.

FPEM717 There are no matching packages

ExplanationNo packages were found that match your selectioncriteria.

User responseChange the selection criteria.

FPEM718 No SQL statements were found forthis package

ExplanationThe package has been bound but does not contain anySQL statements.

User responseSelect a different package.

FPEM719 The plan table owner must be avalid name. Wildcard charactersare not accepted

ExplanationNone.

User responseEnter the correct OWNER of the plan table, or leaveblank to use your own plan table.

FPEM720 Select just one DBRM from the list

ExplanationNone.

User responseSelect only one DBRM from the list.

FPEM721 Select just one statement from thelist

ExplanationNone.

User responseSelect only one statement from the list.

FPEM722 There are no matching DBRMs

ExplanationNo DBRMs were found that match your selectioncriteria.

User responseReenter the DBRM and plan name.

FPEM723 No SQL statements were found forthis DBRM

ExplanationThe DBRM was bound but does not contain SQLstatements.

User responseSelect a different DBRM.

FPEM730 The SQL statement text has notchanged. The statement will notbe explained

ExplanationYou canceled from the editor.

User responseTo explain dynamically, use END from the edit session.

FPEM731 The temporary data set <V1> is inuse

ExplanationNone.

• <V1> is the data set name.

User responseTry again, and if the problem recurs, see your systemprogrammer or contact IBM support.

FPEM732 A severe error occurred whileediting data set <V1>

ExplanationAn error occurred while editing the specified data set.

• <V1> is the data set name.


User responseTry again, and if the problem recurs, see your systemprogrammer or contact IBM support.

FPEM733 The SQL statement text is too long.The text has been truncated

ExplanationNone.

User responseShorten the SQL statement.

FPEM740 There are remote packages in thisplan. The count of SQL statementsdoes not include the statementsfrom the remote packages

ExplanationNone.

User responseNone.

FPEM741 Select just one table partition fromthe list

ExplanationNone.

User responseSelect only one table partition from the list.

FPEM742 No partition information wasfound for this table space

ExplanationNone.

User responseNone.

FPEM743 Select just one index from the list

ExplanationNone.

User responseSelect only one index from the list.

FPEM744 No index information was foundfor this table

ExplanationThe table has no indexes.

User responseNone.

FPEM745 Select just one index partitionfrom the list

ExplanationNone.

User responseSelect only one index partition from the list.

FPEM746 No partition information wasfound for this indexspace

ExplanationNone.

User responseNone.

FPEM747 Select just one column from thelist

ExplanationNone.

User responseSelect only one column from the list.

FPEM748 No key column information wasfound for this column

ExplanationA FETCH from the OMEGAMON XE for DB2 PE copy orview of the DB2 system catalog SYSKEYS table(DGO_SYSKEYS) returned no rows.

The DGO_SYSKEYS table can be created using theinstallation member FPEYCV71, or it can be a shadowcatalog table copied from SYSIBM.SYSKEYS. If it is ashadow catalog table, it must be refreshed regularly.


User responseRun a query against the DGO_SYSKEYS table, such as:

SELECT COLNAME,ORDERING,COLSEQFROM hlq.DGO_SYSKEYSWHERE IXCREATOR = 'PEABPV' AND IXNAME = 'XPE2VMAN'ORDER BY COLSEQ;

and compare the result with a similar query against theSYSIBM.SYSKEYS table. If there are differences, usethe sample job FPEYRSQL to refresh theDGO_SYSKEYS table.

FPEM750 There is no key columndistribution information available

ExplanationNone.

User responseNone.

FPEM751 The table <V1> could not beaccessed

ExplanationNone.


User responseSee your DB2 system administrator.

FPEM752 This statement has no hostvariables

ExplanationThe explained statement has no host variables or wasdynamically explained.

User responseNone.

FPEM753 Output truncated

ExplanationThe output work area is restricted to 800 lines (64 KB).The output is therefore truncated after 800 lines.

User responseUse Batch SQL statement Explain to get the fullExplain output for the SQL statement.

FPEM754 There is no column groupdistribution information available

ExplanationEither the column group distribution information is notavailable or the DB2 version is less than 5.

User responseNone.

FPEM760 The SQL statement is notrecognized or cannot be explained.Only SELECT, INSERT, UPDATE,and DELETE statements can beexplained

ExplanationIf the SQL statement contains the correct SELECT,INSERT, UPDATE, and DELETE statements, it ispossible that a comment is embedded within the SQLstatement. In this case, remove the embeddedcomments and rerun the job.

User responseSee DB2 SQL Reference.

FPEM761 An existing PLAN_TABLE entry forthis statement was not found. Thestatement has been dynamicallyexplained

ExplanationNone. However, this message may also appear whenexplaining an SQL statement from thread activity andan existing entry was found in the PLAN_TABLE.

User responseIn the latter case, to find the access path informationdetermined at bind time, use option 2 or option 3 fromthe Explain menu, depending on whether a package orDBRM, respectively, is being used.

FPEM762 This statement was explained atbind time

ExplanationNone.

User responseNone.


FPEM763 This statement was dynamicallyexplained

ExplanationNone.

User responseNone.

FPEM764 Your plan table is no longer valid.Exit and reenter Explain to re-create the PLAN_TABLE

ExplanationNone.

User responseExit and reenter Explain to re-create the plan table. Ifthis is not successful, delete the plan table and reenterExplain.

FPEM770 Your PLAN_TABLE has beensuccessfully altered to DB2 <V1>format

ExplanationNone.

• <V1> is the DB2 release.

User responseNone.

FPEM771 A DB2 <V1> PLAN_TABLE has beencreated

ExplanationNone.

• <V1> is the DB2 release.

User responseNone.

FPEM772 Your PLAN_TABLE is invalid.Dynamic explains will not beperformed

ExplanationNone.

User responseExit Explain and delete your plan table. ReenterExplain to re-create a new plan table.

FPEM773 Enter a valid database and tablespace name. Leave blank to usedefault names

ExplanationNone.

FPEM774 The database or table space doesnot exist

ExplanationNone.

User responseUse a different database and table space name.

FPEM775 <V1> not authorized to access<V2>.plan_table

ExplanationThe listed user does not have the authority to accessthe plan table.

• <V1> is the user.• <V2> is the owner of the plan table.

User responseObtain authority to access the plan table.

FPEM776 <V1> not authorized to createtable in <V2>

ExplanationThe user does not have the authority to create the plantable.

• <V1> is the current SQLID.• <V2> is the database name.

User responseObtain authority to create the plan table.

FPEM777 <V1> not authorized to access<V2>.PLAN_TABLE. Statementdynamically explained


ExplanationYou do not have the authority to access thePLAN_TABLE related to the package or plan fromwhich an SQL statement was selected to be explained.The SQL statement is explained dynamically by usingthe user’s PLAN_TABLE.

• <V1> is the user ID.• <V2> is the PLAN_TABLE owner ID.

User responseSee your database administrator to get access to thePLAN_TABLE related to the selected package or plan.

FPEM780 Subsystem <V1> is invalid. CAF RC<V2>, REASON <V3>

ExplanationNone.



FPEM781 DB2 subsystem <V1> is notavailable. CAF RC <V2>, REASON<V3>

ExplanationNone.



FPEM782 You are not authorized to accessDB2 subsystem <V1>

ExplanationNone.



FPEM783 You are not authorized to executeplan <V1>

ExplanationNone.

• <V1> is the plan name.


FPEM784 Only one task in this ISPF logicalsession can be connected to DB2

ExplanationNone.

User responseExit OMEGAMON XE for DB2 PE and reenter. If theproblem recurs, contact IBM support.

FPEM785 DB2 PE has been disconnectedfrom DB2 prior to CAF call. RC<V1>, REASON <V2>

ExplanationNone.



FPEM786 DB2 release is not compatible withthe DB2 loadlib (dsnload) release

ExplanationNone.

User responseUse the correct DB2 LOADLIB (DSNLOAD) release.

FPEM787 Nonzero CAF return code. RC<V1>, REASON <V2>


ExplanationNone.



FPEM790 An unexpected error has occurredin module <V1>. The error code is<V2>

ExplanationNone.

• <V1> is the module detecting the error.• <V2> is the internal error code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the error code.

FPEM791 An ISPF <V1> service in module<V2> has returned code <V3>

ExplanationNone.

• <V1> is the ISPF service name.• <V2> is the module detecting the error.• <V3> is the ISPF return code.

User responseSee the OS/390 ISPF Services Guide for an explanationof the ISPF return code. If the problem recurs, contactIBM support.

FPEM792 Storage allocation failed for theExplain module

ExplanationAn error occurred while allocating storage for theExplain module.

User responseExit DB2 PE, and try again. If the problem recurs,contact IBM support.

FPEM793 The explain connection to DB2subsystem <V1> failed. CAF returncode <V2>, reason code <V3>

ExplanationNone.

• <V1> is the DB2 subsystem.• <V2> is the Call Attach Facility (CAF) return code.• <V3> is the reason code.


FPEM794 No entry found for <V1>.<V2> inSYSIBM.SYSTABLES catalog

ExplanationThis message is displayed if a table was not found inthe SYSIBM.SYSTABLES catalog.

• <V1> is the table creator.• <V2> is the table name.

User responseNone.

FPEM800 Please wait. Invoking CollectReport Data ...

ExplanationThe Online Monitor Collect Report Data function isbeing invoked.

User responseNone.

FPEM802 The DB2T storage area has not yetbeen allocated by the Collectsubtask "<V1>"

ExplanationThe Collect facility sets up the DB2 START TRACEcommands in this DB2T storage area. However, theCollect subtask was not able to create the storagearea.

• <V1> is the Collect subtask.


User responseRun the Online Monitor in a larger region space.

FPEM803 Destination <V1> has becomeinactive

ExplanationThe OPx destination used for the trace facility hasbecome inactive, and data is no longer being written tothe trace data set. One possible cause is that all tracesthat had <V1> as their destination have been stopped.

• <V1> is the OPx destination.

User responseNone.

FPEM804 Enter 1 (select), 2 (repeat), 3(delete), or 4 (insert)

ExplanationNone.


FPEM806 Collect Facility failed to save theuser selections ISPF profile table.ISPF service <V1> returned code<V2> with message <V3>

ExplanationWhen a user exits from the collect facility, any changesmade to the table of user selections (as a result ofconfiguring collect tasks) are saved in their ISPFprofile. This message is issued when an error occurs intrying to save these details in the user’s ISPF profile.

• <V1> is the name of the ISPF service.• <V2> is the return code from the ISPF service.• <V3> is the message that is issued by ISPF to

explain the problem.

User responseTake note of the message issued by ISPF and respondaccordingly. The following are possible reasons for thismessage:

• The ISPF profile data set is full.• The ISPF profile data set does not have enough

directory entries.

FPEM809 Collect Report Data stoppedbecause of an error and cannot berestarted. Exit the application,then restart.

ExplanationThe trace facility is unavailable due to a previousfailure.

User responseExit, then restart OMEGAMON XE for DB2 PE beforetrying to start the trace facility again. If the problempersists, contact IBM support.

FPEM810 Trace destination <V1> isunavailable to you. RC <V2>,REASON <V3>. Either this OPdestination is owned by anothertask, or you do not have theappropriate Monitor ClassAuthority

ExplanationYou cannot start a trace for the OP destinationspecified.

• <V1> is an OP buffer destination.• <V2> is a READA return code.• <V3> is a READA reason code.


FPEM811 You cannot leave Collect ReportData while trace is active

ExplanationNone.

User responseEither wait until the trace has completed, or stop thetrace.

FPEM812 The DB2T storage area for StopTrace commands has not yet beenallocated by the Collect subtask"<V1>"


ExplanationThe Collect facility sets up the DB2 STOP TRACEcommands in this DB2T storage area. However, theCollect subtask was not able to create the storagearea.

• <V1> is the name of the Collect subtask.

User responseRun the Online Monitor in a larger region space.

FPEM820 Command <V1> is not recognized.Valid commands are DB2, LOOK,REINIT, OPTIONS, and HISTORY

ExplanationA not valid command was entered at the commandline.







FPEM822 Valid selections are 1, 2, 3, and 4

ExplanationA not valid selection was made on the Collect Facilitymain panel.

User responseSelect one of the listed selection codes and pressEnter.

FPEM823 Valid selections are 1, 2, and 3

ExplanationA not valid selection was entered into the data setdisposition field.

User responseEnter 1, 2, or 3.

FPEM824 Enter a Task Description

ExplanationThe task description field on the Collect facility mainpanel is blank.

User responseEnter a meaningful task description.

FPEM825 Select at least one report set

ExplanationNo selections were made on the Report Selectionpanel.

User responseSelect one or more report sets.

FPEM826 Generics are not allowed

ExplanationAn * was typed into one of the identifiers on the TraceQualification panel.

User responseEnter the full qualifier name or names.

FPEM827 The cursor must be on the 'Forifcid ...' field to use the PROMPTcommand

ExplanationThe PROMPT command was issued, and the cursorwas not on a field to which the PROMPT commandapplies.

User responsePlace the cursor on the field marked with + and reissuethe PROMPT command.

FPEM828 Enter a valid data set name

ExplanationThe data set name entered has a not valid format.


User responseEnter a valid data set name following the IBM namingconventions.

FPEM829 Enter the time in 24-hour clocknotation

ExplanationThe trace task start trigger time is not valid.

User responseEnter a time in 24-hour clock notation where hours arein the range of 0-23, minutes 0-59, and seconds 0-59.

FPEM831 The cursor must be on either the'Field...' or 'For ifcid...' field to usethe PROMPT command

ExplanationThe PROMPT command was issued, and the cursorwas not on a field to which the PROMPT commandapplies.

User responsePlace the cursor on the field marked with + and reissuethe PROMPT command.

FPEM832 Enter a field name

ExplanationThe exception field name is required but it is blank.

User responseEnter the name of a valid exception field. Use thePROMPT command to display a list of valid fields. * is avalid value to represent any field.

FPEM833 Select at least one startingexception event

ExplanationNo starting trigger fields have been selected on theTrigger By Exception Event panel.

User responseSelect at least one start trigger value.

FPEM834 Select at least one of the stopconditions 'Elapsed time' or'Number of records collected' toensure the Collect task will stop

ExplanationOne or both of the conditions ‘elapsed time’ and‘record collected’ must be specified to ensure that thetrace task will stop.

User responseSelect one or both of these stop conditions.

FPEM835 A valid IFCID is required when'Number of IFCIDs collected' isselected

ExplanationThe stop condition ‘number of IFCIDs’ was selected,but no IFCID value was entered or the value entered isnot numeric.

User responseEnter a valid IFCID number. Use the PROMPTcommand to display a list of valid IFCIDs.

FPEM836 Command <V1> is not recognized.Valid commands are END andCANCEL

ExplanationThe text you entered is not recognized as a valid DB2or OMEGAMON XE for DB2 PE command.


FPEM837 Valid selections are 1 and 2

ExplanationYou specified an incorrect value.

User responseSelect 1 or 2.

FPEM840 Collect Report Data is alreadyactive on this screen

ExplanationThe Collect facility is already active on this ISPFscreen.

User responseExit the current screen until control is returned to theCollect facility.


FPEM841 Collect task '<V1>' must beconfigured before the status andmessages can be displayed

ExplanationStatus and messages for a trace task are not availableuntil the task is configured.

• <V1> is the Collect task.

User responseConfigure the task.

FPEM842 Collect task '<V1>' hasterminated, so cannot be restarted

ExplanationThe asynchronous trace task has terminated andtherefore cannot be restarted.


User responseTo restart the task, exit and reenter the Online Monitor.

FPEM843 Collect task '<V1>' is in error, socannot be restarted

ExplanationAn unusual error has occurred that prevents theasynchronous task from running.


User responseSee the trace messages. Exit and reenter the OnlineMonitor to restart the task.

FPEM844 Collect task '<V1>' must beconfigured before it can be started

ExplanationThe trace task cannot be started without aconfiguration.


User responseConfigure the task before you start it.

FPEM845 Collect task '<V1>' has alreadybeen started

ExplanationThe trace task has already been started and is eithercollecting data or waiting for a start trigger.


User responseCorrect the selection.

FPEM846 Collect task '<V1>' has not yetbeen configured

ExplanationThe trace task cannot be stopped because it has notyet been configured.



FPEM847 Collect task '<V1>' must be startedbefore it can be stopped

ExplanationThe trace task cannot be stopped because it has notyet been started.



FPEM848 Collect task '<V1>' must bestopped before it can bereconfigured

ExplanationThe trace task cannot be reconfigured while it isrunning.


User responseStop the task before you reconfigure it.

FPEM850 Select at least one Report Class

ExplanationNo selections were made on the Report Selectionpanel.


User responseSelect one or more reports.

FPEM851 Select at least one IFCID

ExplanationNo selections were made on the IFCID Selectionpanel.

User responseSelect one or more IFCIDs.

FPEM852 Enter at least one identifier in thispanel

ExplanationNo identifiers have been entered on the TraceQualification panel.

User responseEnter at least one identifier on the Trace Qualificationpanel.

FPEM853 Only one set of DB2 qualifiers mayhave more than one qualifyingvalue entered

ExplanationTwo or more identifiers have been entered in morethan one group on the Trace Qualification panel.

User responseOnly one group of identifiers may have two or moreentries.

FPEM854 Elapsed time is invalid

ExplanationThe user has chosen to stop the trace task after anelapsed time, but the time entered is zero or blank.

User responseEnter a time in seconds in the range of 1 to 99 999.

FPEM855 Number of records is invalid

ExplanationThe user has chosen to stop the trace task after anumber of records have been collected, but thenumber entered is zero or blank.

User responseEnter a number in the range of 1 to 99 999 999.

FPEM856 Number of IFCIDs collected isinvalid

ExplanationThe user has chosen to stop the trace task after anumber of IFCIDs have been collected, but thenumber entered is zero or blank.

User responseEnter a number in the range of 1 to 9 999.

FPEM857 IFCID number is invalid

ExplanationThe user has chosen to stop the trace task after aparticular IFCID has been collected, but the IFCIDspecified is zero or blank.

User responseEnter a valid IFCID.

FPEM858 <V1> command not valid in thispanel. Valid commands are DB2,LOOK, REINIT, OPTIONS, andHISTORY









FPEM859 You will not receive informationabout asynchronous I/Os


ExplanationQualifying the plan or the authorization ID in the DB2START TRACE command for performance trace class4 restricts the data that DB2 produces to your taskTCB and omits all asynchronous tasks includingSequential Prefetch.

User responseTo ensure that all Sequential Prefetch related I/O istraced by DB2 and subsequently reported by DB2 PE,do not qualify by plan or by authorization ID.

FPEM860 Select one item only

ExplanationWhen using the Prompt facility for IFCIDs from theTrigger panels, more than one item was selected fromthe list displayed.

User responseSelect only one item from the list.

FPEM861 The IFCID value '<V1>' is invalid -use the PROMPT command for alist

ExplanationThe IFCID entered does not exist.

• <V1> is the invalid IFCID value.

User responseEnter a valid IFCID number or use the PROMPTcommand to display a list of valid IFCIDs.

FPEM862 The IFCID value '<V1>' is notavailable. It has been excluded inCollect Configuration

ExplanationThe IFCID entered is not available. The IFCID has beenexcluded by selections made in Trace Configuration.

• <V1> is the invalid IFCID value.

User responseEnter a valid IFCID number or use the PROMPTcommand to display a list of valid IFCIDs. If the IFCIDyou wish to enter does not appear on this list, then theconfiguration must be changed.

FPEM863 Select one report set

ExplanationNo selections were made on the Report Set Selectionpanel.

User responseSelect one report set.

FPEM864 Select one report class

ExplanationNo selections were made on the Report Set Selectionpanel.

User responseSelect one report.

FPEM865 Select one IFCID

ExplanationNo selections were made on the IFCID Selectionpanel.

User responseSelect one IFCID.

FPEM866 This is the only IFCID available.Others were excluded in CollectConfiguration

ExplanationWhen the PROMPT command was issued on the IFCIDfield, the system found only one IFCID that qualifiedfor selection. The selection panels are bypassed, andthis IFCID is displayed.

User responseNone.

FPEM867 The field identifier '<V1>' is invalid- use the PROMPT command for alist

ExplanationThe exception field entered does not exist.

• <V1> is the invalid field identifier.

User responseEnter a valid exception field name or use the PROMPTcommand to display a list of valid exception fields.


FPEM868 No messages have been writtenfor the Collect subtask '<V1>'

ExplanationThere are no trace task messages to view.

• <V1> is the Collect subtask.

User responseNone.

FPEM869 The message list has not beencreated for the Collect subtask'<V1>'

ExplanationThere is no message area into which the trace task canwrite its messages.

User responseExit and reenter ‘Status and Messages’. The trace taskthen allocates the message area as part of its startuproutine.

FPEM870 Interval time must be in range of 1through 1440 minutes

ExplanationThe time interval selected is outside the valid range.

User responseSpecify a time interval between 1 and 1 440 minutes.

FPEM871 Active time must be in range of 1through 3600 seconds

ExplanationThe active time selected is outside the valid range.

User responseSpecify an active time between 1 and 3 660.

FPEM872 File format must be 1, 2 or 3

ExplanationYou specified a value for the file disposition that is notvalid.

User responseSpecify the file disposition as follows:

1To append to the specified data set

2To overwrite the specified data set

3To allocate a new data set

FPEM873 Size of OP buffer must be between8 KB and 1024 KB

ExplanationThe size of the specified output buffer is outside theacceptable range.

User responseSpecify a valid size for the output buffer.

FPEM874 <V1> command not valid in thispanel. Valid commands are ENDand CANCEL

Explanation• <V1> is the command you entered.

You can only stop a trace from this panel.

User responseNone.

FPEM880 Buffer size incorrect

ExplanationThe OP buffer size should be in the range 8 KB - 1024KB.

User responseSpecify a valid size for the output buffer.

FPEM881 The data type is incorrect, use 1,2, or 3


User responseSpecify the report data required, as follows:1

Detail2

Summary data


3Catalog data only

FPEM882 The start type is incorrect, use 1 or2


User responseYou can choose the way data collection is started, asfollows:1

To start collection immediately2

To start collection at a specified time.

FPEM884 Interval time must be between 0and 1440 minutes

ExplanationNone.

User responseEnter a valid interval time value, in the range 0-1 440.

FPEM885 Active time must be between 0and 3600 seconds

ExplanationNone.

User responseEnter a valid active time value, in the range 0-3 600.

FPEM886 Interval time is less than activetime

ExplanationThe interval time must be greater than the active time.

User responseEnter a time between 0 and 1 440 seconds, that isgreater than the active time specified.

FPEM900 Changes have been accepted

ExplanationThe changes you made in the panel have beenvalidated and accepted.

User responseNone.


















FPEM903 Exception log data set names mustbe different


ExplanationThe periodic and display Exception Log data set namesmust be different when connected to a Data Server.

User responseUse unique data set names.

FPEM904 Exception file data set namesmust be different

ExplanationThe periodic and display Exception File data set namesmust be different when connected to a Data Server.

User responseUse unique data set names.

FPEM905 Display exceptions found. <V1>total <V2> problem

ExplanationThe Display Exception Processor has found exceptionconditions on the current panel.

• <V1> is the total number of exceptions.• <V2> is the number of exceptions classified as

problems.

User responseUse the LOOK command to look at a list of displayexceptions.

FPEM907 Periodic interval must be numericin the range 1 to 7200 seconds

ExplanationThe periodic interval is not within allowableboundaries.

User responseSpecify a periodic interval in the correct range.

FPEM908 Periodic interval must be numericin the range 1 to 120 minutes

ExplanationThe periodic interval is not within allowableboundaries.

User responseSpecify a periodic interval in the correct range.

FPEM909 The Exception Processor hasterminated normally

ExplanationThe Online Monitor Exception Processor has beenterminated from the Exception Processor panel(FPEMXP00).

User responseNone.

FPEM910 <V1> periodic warning exceptionsfound

ExplanationThe Periodic Exception Processor has detectedwarning exceptions.

• <V1> is the number of periodic exceptions.

User responseUse the LOOK command to look at the periodicexceptions.

FPEM911 Display exceptions found. <V1>total, <V2> problem

ExplanationThe Display Exception Processor has found exceptionconditions on the current panel.

• <V1> is the total number of exceptions.• <V2> is the number of exceptions classified as

problems.

User responseUse the LOOK command to look at a list of displayexceptions.

FPEM912 Error attempting to close theException log

ExplanationAn error occurred when closing the exception log.

User responseNone.


FPEM913 Error attempting to close theException File

ExplanationAn error occurred when closing the Exception Log file.

User responseNone.

FPEM914 Error attempting to write to theException log

ExplanationAn error occurred when writing to the exception log.The log record was not written.


FPEM915 Invalid data set name

ExplanationThe data set name specified does not conform to MVSstandards.


FPEM917 Unable to open vlist <V1>. RC<V2>

ExplanationThe Online Monitor detected an internal error.

• <V1> is the VLIST name.• <V2> is the return code.


FPEM918 Event name <V1> is invalid

ExplanationThe Online Monitor detected a not valid event in theexception threshold data set.

• <V1> is the invalid event name you specified.

User responseSpecify one of the following event types:STAT

For statistics eventsTHRD

For thread activity eventsACCT

For accounting events.

FPEM919 Field name <V1> is supported onlyby DB2 PE batch

ExplanationThe field name specified in the exception thresholddata set is valid only in the batch component.


User responseNone.

FPEM920 Field name <V1> is invalid for DB2PE or DB2

ExplanationThe Online Monitor detected a not valid field name inthe exception threshold data set.

• <V1> is the invalid field name.


FPEM921 Field name <V1> is invalid for DB2<V2>

ExplanationThe field name is not valid for the release of the DB2subsystem to which you are connected.

• <V1> is the field name.• <V2> is the release of the DB2 subsystem.

User responseEnter a valid field name.

FPEM922 Field name <V1> invalid for thisevent

ExplanationThe field name specified in the exception thresholddata set does not correspond with the event (for


example, a statistics field was specified for a THRDevent).



FPEM923 Field value <V1> is not numeric

ExplanationThe field value specified in the exception thresholddata set must be numeric.

• <V1> is the value specified for the field.


FPEM924 Comparison operator <V1> isinvalid

ExplanationThe comparison operator is not valid.

• <V1> is the specified comparison operator.

User responseSpecify one of the following:

• > (greater than)• < (less than).

FPEM925 Field name <V1> cannot bequalified

ExplanationAn attempt was made to qualify a field, but the field isnot eligible for qualification.

• <V1> is the name of the field.


FPEM926 Field qualifier <V1> is invalid

ExplanationThe field qualification specified in the exceptionthreshold data set is not valid.

• <V1> is the specified field qualifier.

User responseSpecify one of the following field qualification values:BPn

4 KB buffer pool number (0 ≤ n ≤ 49)BP32K

32 KB buffer poolBP32Kn

32 KB buffer pool number (0 ≤ n ≤ 9)ANY

Any buffer poolTOT

The total of all buffer poolsTOT4K

The total of all 4 KB buffer poolsTOT32K

The total of all 32 KB buffer pools.

FPEM927 <V1> is an invalid time value

ExplanationThe time value specified for a field in the exceptionthreshold data set is not valid.

• <V1> is the specified time value.


FPEM928 A time value is not valid for field<V1>

ExplanationA time value was specified for a field in the exceptionthreshold data set that is not a time field.

• <V1> is the name of the field.


FPEM929 Exception Processor initializedwith errors

ExplanationThe Online Monitor exception processor wasinitialized, but errors were detected duringinitialization. These errors were not severe enough tokeep the exception processor from being initialized,but the threshold entries in error were discarded. Theerrors are listed in the panel.


User responseCorrect the errors.

FPEM930 Exception Processor has beeninitialized

ExplanationThe Online Monitor exception processor was initializedsuccessfully.

User responseNone.

FPEM931 Comparison basis <V1> is invalid

ExplanationThe comparison basis specified in the exceptionthreshold data set is not valid.

• <V1> is the specified comparison basis.

User responseSpecify one of the following:V

Check field value against an absolute valueM

Check field value on a per-minute basisS

Check field value on a per-second basisC

Check field value on a per-commit basis.

FPEM932 Both problem value and warningvalue are blank

ExplanationBoth the problem threshold value and the warningthreshold value are blank.

User responseSpecify a problem threshold value or a warningthreshold value or both.

FPEM933 Invalid compare basis for apackage field

ExplanationValid compare bases are OCCUR and VALUE.


FPEM934 Per occur compare basis is validfor batch only

ExplanationNone.


FPEM935 No valid threshold records

ExplanationAll the records in the threshold data set specified onthe Exception Processor panel (FPEMEP00 orFPEMEP02) are in error. The exception processor is notinitialized when this occurs. The records in error andthe reasons for the error are listed.

User responseCorrect the errors.

FPEM936 Exception event notificationstarted

ExplanationNone.

User responseNone.

FPEM937 Exception event notificationstopped

ExplanationNone.

User responseNone.

FPEM938 Error attempting to write to theException file

ExplanationAn error occurred when writing to the Exception Logfile. The log file record was not written.



FPEM939 The Periodic Exception Processorhas terminated and cannot berestarted. Exit from the OnlineMonitor before restarting

ExplanationAn earlier error caused the periodic exceptionprocessor to terminate.

User responseExit from the Online Monitor before trying to start theperiodic exception processor again. If the problemrecurs, contact IBM support.

FPEM940 The Periodic Exception Processorhas terminated

ExplanationNone.

User responseRestart the Online Monitor.

FPEM941 Environment <V1> is invalid

ExplanationThe environment specified in the exception thresholddata set is not valid.

• <V1> is the value specified for the environment.

User responseCorrect the error. Valid values are:O

For online exception processing onlyB

For batch exception processing onlyZ

For batch and online exception processing.

FPEM942 Internal error building exceptiontables

ExplanationAn error occurred during the building of the exceptiontables.


FPEM943 The exception threshold data set isempty

ExplanationThe threshold data set does not contain any records.

User responseAdd records to the threshold data set or specifyanother threshold data set name.

FPEM944 Periodic Exception Processorstarted at <V1>

ExplanationThe periodic exception processor is started.

• <V1> is the date and time at which the periodicexception processor started.

User responseNone.

FPEM945 Periodic Exception Processorstopped at <V1>

ExplanationThe periodic exception processor is stopped.

• <V1> is the date and time at which the periodicexception processor stopped.

User responseNone.

FPEM946 Threshold data set from previousrelease is used

ExplanationThe threshold data set from a previous release is beingused. New identifiers have defaulted to accept allvalues.

User responseConvert the threshold data set using the thresholddata editor to take full advantage of the newidentifiers.

FPEM947 REINIT command not executed,Exception Processor not active


ExplanationThe REINIT command can only be used if theexception processor is active.

User responseUse the Exception processor panel (FPEMXP00) tostart the exception processor.

FPEM948 <V1> display problems. <V2>periodic problems

ExplanationDisplay or periodic exceptions have been found. Thismessage is displayed if the Disable Auto option is setto N and problem exceptions have been found.

• <V1> is the number of display problems.• <V2> is the number of periodic problems.

User responseNone.

FPEM949 The Threshold data set containsrecords only valid for Batch

ExplanationThere are no records in the exception threshold dataset with an environment field that is either O or Z, orthere are such records, but they are commented out.

User responseInitialize the exception processor with an exceptionthreshold data set that contains threshold recordsvalid for the Online Monitor.

FPEM950 <V1> periodic warning exceptionsfound

ExplanationPeriodic warning exceptions have been found.

• <V1> is the total number of periodic warningexceptions.

User responsePress F4 to look at the exceptions.

FPEM951 Exception event details are notsupported

ExplanationNo details about a selected IFCID, respectivelyexception event, can be reported because the ISPFOnline Monitor runs in DB2 10 toleration mode only.

User responseNone.

FPEM952 REINIT command not alloweduntil previous command iscompleted

ExplanationThe REINIT command cannot be entered until theprevious command has completed its function.

User responsePress F3 and then enter the REINIT command.

FPEM953 Exception Event processor startedat <V1>

ExplanationNone.

• <V1> is the start time of the exception eventprocessor.

User responseNone.

FPEM954 Exception Event processorstopped at <V1>

ExplanationNone.

• <V1> is the end time of the exception eventprocessor.

User responseNone.

FPEM955 Log or File error occurred. CheckPeriodic Message List

ExplanationPeriodic exception processing caused an I/O errorwhile trying to write records to log or file data set.


User responseCheck the periodic message list using the Look panelto see what caused the error.

FPEM956 Authorization failure details notfound

ExplanationNone.

User responseNone.

FPEM957 No exception events have occurred

ExplanationNone.

User responseNone.

FPEM958 No authorization failures haveoccurred

ExplanationNone.

User responseNone.

FPEM959 Exception event details not found

ExplanationNone.

User responseNone.

FPEM995 One or more online applicationsubtasks could not be attached

ExplanationAn error occurred during application startup.

User responseRefer to accompanying messages to detail theproblem.

FPEM996 No data returned, so unable toprocess the request

ExplanationAn unexpected error has occurred.


FPEM997 The program is already active forthis logical screen

ExplanationYou are already running OMEGAMON XE for DB2 PE.

You can only have one session of this program open ata time. This can happen also when the applicationstopped due to an error.

User responseClose the session, or close and restart ISPF, thenrestart OMEGAMON XE for DB2 PE.

FPEM998 The application cannot continuebecause DB2 interface module<V1> cannot be loaded

ExplanationThe DB2 load library containing module <V1> is not inthe program search path.

• <V1> is the DB2 interface module.

User responsePut the DB2 load library SDSNLOAD into the searchpath for load libraries, either by link list concatenation,by allocation to ISPLLIB, or by TSOLIB ACTIVATE.

FPEM999 The application cannot continuebecause of insufficient storage

ExplanationNone.

User responseIncrease the region size of the TSO/E session, orterminate concurrently running ISPF applications.


FPEN - Record Trace messagesFPEN1246S UNSUCCESSFUL ATTEMPT WRITING TO THE FILE DATA SET OF

RECORD TRACE

ExplanationAn error occurred while writing data to the Record trace File data set.


FPEP - Spreadsheet Input Data GeneratorFPEP1000E THE INPUT PARAMETERS '<V1>'

SPECIFY AN INVALID REQUEST.REASON <V2>.

ExplanationThe Spreadsheet Input Data Generator is invoked withinvalid input parameters.

• <V1> is the string of input parameters.• <V2> is the reason code.

The following reason codes might occur:20

Invalid length. You can use only one blankbetween parameters.

24Invalid value for TYPE. Use one of the followingvalues:

• AFBU• AFDF• AFGE• AFGP• AFPK• AFXC• ASBU• ASDF• ASGE• ASGP• ASPK• ASRF• ASXC• SBUF• SDDF• SGBP• SGEN

• SSET• SXCL

28Invalid value for PERSEC. You must use Y or N.

32Invalid value for PERSEC. Y is only valid forStatistics TYPE.

36Invalid value for HDRROW. You must use F, Y, or N.

40Invalid value for HDRPDCOL. You must use Y or N.

44Invalid value for DELIM. You must use a comma (,)or a semicolon (;).

48Invalid value for DECSEP. You must use a comma(,) or a period (.).

52Invalid values for DELIM and DECSEP. You mustuse different values for these parameters.

User responseCorrect the invalid input parameters and rerun theSpreadsheet Input Data Generator.

FPEP1001I TYPE <V1> HAS BEENREQUESTED.

ExplanationThe Spreadsheet Input Data Generator is invoked fortype <V1>.

<V1> is the type of data for which a spreadsheet isrequested. The type is related to the PerformanceDatabase tables and parts that are delivered in theRKO2SAMP / TKO2SAMP library.


User responseNone.

FPEP1002I CSV CREATION FOR TYPE <V1>STARTED.

ExplanationThe Spreadsheet Input Data Generator started tocreate spreadsheet data for type <V1>.

<V1> is the type of data. It is related to thePerformance Database tables and parts that aredelivered in the RKO2SAMP / TKO2SAMP library.

User responseNone.

FPEP1003E FILE <V1>: ALLOCATION OFINTERNAL STRUCTURES FAILEDAT START OF PROCESSING.

ExplanationThe Spreadsheet Input Data Generator failed toallocate internal structures for the file at the start ofprocessing.

<V1> is the name of the file.

User responseCheck that the file records have the correct format.

FPEP1004E DEALLOCATION OF INTERNALSTRUCTURES FAILED AT END OFPROCESSING.

ExplanationThe Spreadsheet Input Data Generator failed todeallocate internal structures at the end of processing.

User responseCheck the system output. Contact IBM Support toreport this problem.

FPEP1005E UNABLE TO OPEN FILE <V1>.

ExplanationAn error occurred when opening the file.


User responseCheck that the file exists and that it is in the correctformat.

FPEP1006E UNABLE TO WRITE OUTPUT FILE.

ExplanationAn error occurred when writing to the output file.

User responseCheck the system output and correct the problem.

FPEP1007I FILE <V1>: ALLOCATION OFINTERNAL STRUCTURESFINISHED.

ExplanationThe allocation of internal structures for the filefinished.


User responseNone.

FPEP1008I RECORDS IN: <V1>: RECORDSOUT: <V2> (INCL. HEADER ROW).

Explanation<V1> is the number of input records processes.

<V2> is the number of records that are written to theoutput file.

User responseNone.

FPEP1010I CSV CREATION FOR TYPE <V1>HAS FINISHED.

ExplanationThe Spreadsheet Input Data Generator finished thecreation of spreadsheet data for type <V1>.


User responseNone.

FPEP1011E CSV CREATION FOR TYPE <V1>FAILED.


ExplanationThe Spreadsheet Input Data Generator cannot createspreadsheet data for type <V1>.


User responseCheck the system output and correct the problem.

FPEP1012E INVALID INPUT RECORD IN LINE<V1> FOR TYPE <V2>.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid record. Therefore it cannot create spreadsheetdata for type <V2>.

• <V1> is the line of the invalid record in the INPUTfile.

• <V2> is the type of data. It is related to thePerformance Database tables and parts that aredelivered in the RKO2SAMP / TKO2SAMP library.

User responseCheck that the INPUT file contains valid records, forexample:

• If a statistics type Sxxx is selected: statistics FILErecords or converted statistics SAVE-FILE records

• If an accounting type AFxx is selected: accountingFILE records

• If an accounting type ASxx is selected: convertedaccounting SAVE-FILE records.

FPEP1015E FILE <V1>: INVALID TOKEN <V2>ENDING AT POSITION <V3> INLINE <V4>. TOKEN <V5>EXPECTED.

ExplanationThe Spreadsheet Input Data Generator detected asyntactical error when processing input data.

• <V1> is the input file.• <V2> is the invalid token.• <V3> is the ending position of the invalid token.• <V4> is the line in the input file of the invalid token.• <V5> is the expected token.

User responseCheck the input file and correct the problem.

FPEP1016E FILE <V1>: INVALID COLUMN<V2> USED IN WHEN CLAUSE.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid column in the WHEN clause of a DB2 loadstatement.

• <V1> is the input file.• <V2> is the invalid column.


FPEP1017E FILE <V1>: INVALID COLUMN<V2> USED IN A DEFAULTIFCLAUSE.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid column in a DEFAULTIF clause of a DB2 loadstatement.



FPEP1018E FILE <V1>: INVALID COLUMN<V2> USED IN A NULLIF CLAUSE.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid column in a NULLIF clause of a DB2 loadstatement.



FPEP1020E FILE <V1>: INVALID COLUMN<V2> USED IN FIELD SELECTIONLIST. COLUMN NOT FOUND INBPART.


ExplanationThe Spreadsheet Input Data Generator detected aninvalid column in the field selection list. This column isnot specified in the metadata B-part.


User responseCheck the input file. For example, make sure that thecorrect metadata part is used or that the correctcolumn is specified in the field selection list.

FPEP1021E FILE <V1>: INVALID FIELD <V2>USED IN FIELD SELECTION LIST.FIELD NOT FOUND IN BPART.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid field in the field selection list. This field is notspecified in the metadata B-part.

• <V1> is the input file.• <V2> is the invalid field.

User responseCheck the input file. For example, make sure that thecorrect metadata part is used or that the correct fieldis specified in the field selection list.

FPEP1022E FILE <V1>: INVALID COLUMN<V2> USED IN FIELD SELECTIONLIST. COLUMN NOT FOUND INLPART.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid column in the field selection list. This column isnot specified in the load statement (L-part).

• <V1> is the input file.• <V2> is the invalid field.


FPEP1023E FILE <V1>: INVALID FORMAT <V2>USED IN FIELD SELECTION LIST.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid format function in the field selection list.

• <V1> is the input file.• <V2> is the invalid format.

User responseCheck the input file and use a valid format function.Valid format functions are MB, P2MB, HEX, or S2T.

FPEP1024E FILE <V1>: INVALID FORMAT <V2>USED IN FIELD SELECTION LISTFOR FIELD <V3>. ENTRY MUST BEBLANK FOR TYPE <AGGR>.

ExplanationThe Spreadsheet Input Data Generator detected aninvalid format function in the field selection list. Fieldswith type AGGR must not have a format function.

• <V1> is the name of the input file.• <V2> is the name of the invalid format.• <V3> is the name of the field.

User responseCheck the input file and remove the format function.

FPEQ - Buffer Pool Analyzer messagesFPEQ7035E FILE RECORD WAS NOT WRITTEN.

DDNAME = <V1>. RETURN CODE =<V2>

ExplanationAn error occurred when attempting to write a record tothe buffer pool File data set.

• <V1> is the ddname for the data set.• <V2> is the return code from the write operation.

User responseCheck the data set allocation.

FPEQ7102E INPUT DATA DOES NOT CONTAIN<V1> RECORDS

ExplanationThe input data set does not contain sufficient data toproduce a detail buffer pool analysis report.


• <V1> identifies the missing data record. Possiblevalues are:DETAILOBJECTGBP-0 TYPE

Group buffer pool attributes (IFCID 230) werenot collected.

GBP-1 TYPEPhysical lock data (IFCID 251) was not collected.

GBP-2 TYPEGroup buffer pool activity information was notcollected from DB2 statistics data (IFCID 2).

GBP-4 TYPECoupling facility cache statistics (IFCID 254)were not collected.

User responseStart a new DB2 trace, or use the trace configurationfunction to produce new input data containing thecorrect level of detail.

Depending on the detail, as well as the IFCIDs listedpreviously, you should include IFCIDs 6 and 7, orIFCIDs 8, 9, and 10, or IFCID 198, or all.

FPEQ7120I UNABLE TO CORRECTLY PRINTHEADER FOR BUFFER POOLACTIVITY REPORT

ExplanationAn error occurred while attempting to print the headeron a buffer pool activity report.


FPEQ7270E BUFFER POOL ACTIVITYEXCEPTIONAL CONDITION.INTERNAL ERROR CODE <V1>


• <V1> are the internal error codes.

User responseRerun the job. If the problem recurs, contact IBMsupport and quote the internal error codes.

FPEQ7450S INITIALIZATION FAILED FORBUFFER POOL ACTIVITY LIST.

INSUFFICIENT STORAGEAVAILABLE



FPEQ7500S MAXIMUM NUMBER OFSUPPORTED OBJECTS EXCEEDED

ExplanationFILE data at object level cannot be generated becausethe number of objects in the DB2 catalog is greaterthan the number of objects currently supported byOMEGAMON XE for DB2 PE.

FILE data output at other levels (detail, buffer, orsummary) is generated, when requested.

User responseContact IBM support to request an increase to thislimit.

FPEQ7502S EXCEPTION OCCURRED DURINGWRITING TO WORK FILE. <V1> OF<V2> RECORDS ALREADYWRITTEN.

ExplanationNot enough data set space allocated for the amount ofdata to be written.

User responseAllocate more data set space. Use the actual allocationsize and the values shown in the message todetermine the minimum space required. Retry theoperation.

FPEQ7504S INSUFFICIENT STORAGE WHILEREADING TRACE DATA. ONLY<V1> RECORDS READ.

ExplanationInsufficient region size to store the amount of catalogdata. The amount depends on the amount of tracedata to be read.


User responseSee the DB2 system catalog. From the catalog tablesSYSIBM.SYSTABLESPACE and SYSIBM.SYSINDEXESdetermine the numbers of objects/rows to be read.Compare the sum of these numbers with the numberof records read and increase the region sizeaccordingly. Run the job again.

FPEQ7600S EXCEPTIONAL CONDITIONOCCURRED DURING BUFFERPOOL ACTIVITY PROCESSING.MAIN STORAGE ALLOCATIONFAILED

ExplanationThere was not enough storage available to continuebuffer pool activity processing.


FPEQ7610S EXCEPTIONAL CONDITIONOCCURRED DURING BUFFERPOOL ACTIVITY PROCESSING.MAIN STORAGE RELEASE FAILED

ExplanationAn error occurred attempting to free virtual storage.


FPER - SQL Activity report set messagesFPER0600S EXCEPTIONAL CONDITION

OCCURRED DURING SQLACTIVITY PROCESSING. MAINSTORAGE ALLOCATION FAILED

ExplanationThere was not enough storage available to continueSQL activity processing.


FPER3270S EXCEPTIONAL CONDITIONOCCURRED DURING SQLACTIVITY PROCESSING.INTERNAL ERROR CODE <V1>



User responseIf the internal error code is OVERFLOW, rerun the joband try one or more of the following actions to reducethe amount of data for an SQL Activity trace:

• Use the FROM/TO options for the GLOBAL commandto specify a limited time interval.

• Rather than specifying WORKLOAD(ALL) in theTRACE subcommand, make an appropriateselection, for example, WORKLOAD(IO).

• Rather than collecting a large amount of data in onetrace, specify the TRACE subcommand repeatedly(you can repeat it up to five times) to spread theinformation over several traces.

For all other internal error codes, rerun the job. If theproblem recurs, contact IBM support and quote theinternal error code.

FPER3280I ONE OR MORE SQLDA ENTRIESARE MISSING.

ExplanationAn informational message as result from anSQLACTIVITY TRACE WORKLOAD(VARS) command,which requests that host variables data is to be shownin an SQL Activity trace. However, some entries in theSQL Descriptor Area (SQLDA) that are required for theexecution of some SQL statements were not found.

User responseNone.

FPER3281I THE MAXIMUM OF 200 SQLDAENTRIES IS REACHED.

ExplanationAn informational message as result from anSQLACTIVITY TRACE WORKLOAD(VARS) command,which requests that host variables data is to be shownin an SQL Activity trace. More than 200 entries in theSQL Descriptor Area (SQLDA) were found but only thefirst 200 entries are shown in the SQL Activity trace.


User responseNone.

FPER3282I INTERNAL STORAGE LIMIT HASBEEN REACHED.

ExplanationThe amount of host variables data, identified by IFCID247 records, exceeds the internal storage limit of 5

MB. Only stored data will be shown in the SQL Activitytrace.

User responseUse the GLOBAL command to minimize the amount ofdata for the specific report.

FPES - Statistics report set messagesFPES0005W STATISTICS RECORD WITH IFCID

0002, SEQNO = <V1> MISSING.IFCID 0001, SEQNO = <V2>IGNORED. AFFECTINGFUNCTIONS: <V3>

ExplanationAn IFCID 0001 record was found without a matchingIFCID 0002 record, and was ignored.

• <V1> is the sequence number of the missing record.• <V2> is the sequence number of the unmatched

record.• <V3> is REDUCE or TRACE/FILE.


User responseNone.

FPES0010W STATISTICS RECORD WITH IFCID0001, SEQNO = <V1> MISSING.IFCID 0002, SEQNO = <V2>IGNORED. AFFECTINGFUNCTIONS: <V3>

ExplanationAn IFCID 0002 record was found without a matchingIFCID 0001 record, and was ignored.

• <V1> is the sequence number of the missing record.• <V2> is the sequence number of the unmatched

record.• <V3> is REDUCE or TRACE/FILE.


User responseNone.

FPES0015I A DB2 RESTART HAS BEENDETECTED. STATISTICSCOUNTERS RESET. AFFECTINGFUNCTIONS: <V1>. NEW BEGINRECORD IFCID <V2>, SEQNO =<V3>

ExplanationA DB2 restart has been detected (the sequencenumber of the end record pair was lower than thebegin record pair). Because a statistics deltacalculation would result in negative values, the currentbegin record pair is discarded, and processingcontinues.

• <V1> is REDUCE or TRACE/FILE.• <V2> is the IFCID number of the record where the

restart was detected.• <V3> is the sequence number of the record pair that

is used as the new begin records.


User responseNone.

FPES0020I STATISTICS REDUCE COMPLETE

ExplanationStatistics REDUCE processing is completed.

User responseNone.


FPES0025I STATISTICS FILE COMPLETE. <V1>RECORDS WRITTEN TO DDNAME<V2>

ExplanationA STATISTICS FILE subcommand has completed itsfunction.

• <V1> is the number of records written.• <V2> is the destination ddname.

User responseNone.

FPES0030I STATISTICS SAVE COMPLETE

ExplanationStatistics SAVE processing is completed.

User responseNone.

FPES0035E FILE RECORD WAS NOT WRITTEN.DDNAME = <V1>. RETURN CODE =<V2>

ExplanationAn error occurred when attempting to write a record tothe Statistics File data set.

• <V1> is the ddname for the data set.• <V2> is the return code from the write operation.

User responseCheck the data set allocation.

FPES0040S EXCEPTIONAL CONDITIONOCCURRED DURING STATISTICS<V1> PROCESSING. MAINSTORAGE ALLOCATION FAILED

ExplanationThere was not sufficient storage available for statisticsprocessing to continue.

• <V1> is RECORD or REPORT.


FPES0045S EXCEPTIONAL CONDITIONOCCURRED DURING STATISTICS

<V1> PROCESSING. MAINSTORAGE RELEASE FAILED


• <V1> is RECORD or REPORT.


FPES0050S VSAM <V1> FUNCTION FAILED ONDDNAME <V2>. VSAM RETURNCODE <V3>. REASON CODE <V4>.SAVE RECORD WAS NOT ADDED

ExplanationAn attempt to write a SAVE record failed.

• <V1> is the name of the VSAM function that failed.• <V2> is the ddname for which the function failed.• <V3> is the VSAM return code.• <V4> is the VSAM reason code.


FPES0055S PUT FUNCTION FAILED ONDDNAME <V1> WHILEEXTERNALIZING REDUCEDRECORDS

ExplanationAn error occurred when writing records to thestatistics REDUCE work data set.



FPES0060W A STATISTICS <V1> DELTACALCULATION RESULTED INNEGATIVE VALUES. BEGINRECORD IFC SEQNO = <V2>

ExplanationThe calculation for a statistics delta record resulted innegative values. The results are ignored andprocessing continues.

• <V1> is REDUCE or TRACE/FILE.


• <V2> is the sequence number of the begin records.

User responseNone.

FPES0065U EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGSTATISTICS LIST 1.INSUFFICIENT STORAGEAVAILABLE

ExplanationThere was not enough storage available for statisticsprocessing to continue.


FPES0070U INITIALIZATION FAILED FORSTATISTICS LIST 1.INSUFFICIENT STORAGEAVAILABLE

ExplanationThere was not enough storage available to continuethe initialization for statistics list 1.


FPES0075U EXCEPTIONAL PROCESSINGCONDITION WHILE GENERATINGSTATISTICS LIST 2.INSUFFICIENT STORAGEAVAILABLE

ExplanationThere was not enough storage available for statisticsprocessing to continue.


FPES0080U INITIALIZATION FAILED FORSTATISTICS LIST 2.INSUFFICIENT STORAGEAVAILABLE

ExplanationThere was not enough storage available to continuethe initialization for statistics list 2.


FPET - Utility Activity report set messagesFPET0600S EXCEPTIONAL CONDITION

OCCURRED DURING UTILITYACTIVITY PROCESSING. MAINSTORAGE ALLOCATION FAILED

ExplanationThere was not enough storage available for utilityactivity processing to continue.


FPET0610S EXCEPTIONAL CONDITIONOCCURRED DURING UTILITYACTIVITY PROCESSING. MAINSTORAGE RELEASE FAILED

ExplanationAn attempt to free storage failed.


FPET1020I UNABLE TO CORRECTLY PRINTHEADER FOR UTILITY ACTIVITYREPORT

ExplanationAn error occurred while attempting to print the headeron a Utility Activity report.



FPET1030W THE INTERNAL LIMIT OF PHASESTHAT CAN BE PROCESSED HASBEEN EXCEEDED. PROCESSINGCONTINUES WITH <V1>REGISTERED PHASES WITHOUTADDITIONAL ONES.

ExplanationProcessing is limited to <V1> phases. New phasesfound after reaching this limit cannot be processed.

User responseEnsure that the input trace data does not include morethan the maximum number of phases.

FPET1040W THE INTERNAL LIMIT OFSUBTASKS THAT CAN BEPROCESSED HAS BEENEXCEEDED. PROCESSINGCONTINUES WITH <V1>REGISTERED SUBTASKSWITHOUT ADDITIONAL ONES.

ExplanationProcessing is limited to <V1> subtasks. New subtasksfound after reaching this limit cannot be processed.

User responseEnsure that the input trace data does not include morethan the maximum number of subtasks. For example,

check and adapt the PARALLEL option of the COPY orRECOVER utility when collecting DB2 trace data.

FPET3270E EXCEPTIONAL CONDITIONOCCURRED DURING UTILITYACTIVITY PROCESSING.INTERNAL ERROR CODE <V1>



User responseRerun the job. If the problem recurs, contact IBMsupport and quote the internal error code.

FPET4500E INITIALIZATION FAILED FORUTILITY ACTIVITY LIST.INSUFFICIENT STORAGEAVAILABLE



FPEU - Utility Services messagesFPEU0001U UNABLE TO LOAD BASE SERVICES


User responseRerun the job. If the problem recurs, see your systemprogrammer or contact IBM support.

FPEU0002U UNABLE TO LOAD NLS SUPPORTMODULE

ExplanationAn error occurred during initialization of NLS support.


FPEU0003S <V1> IS AN INVALID VALUE INTHE DATEFORMAT PARAMETER

ExplanationThe value supplied in the DATEFORMAT parameter isnot valid.


User responseThe DATEFORMAT parameter must be eight characterslong and contain one each of DD, MM, and YY for theday, month, and year, respectively. You can specify theday, month, and year in any order. A single character


delimiter is also required in the third and sixthpositions.

FPEU0004S DATEFORMAT PARAMETER VALUE<V1> HAS BEEN SPECIFIED MORETHAN ONCE

ExplanationThe value for day (DD), month (MM), or year (YY) hasbeen specified more than once. For example, aDATEFORMAT of DD-DD-YY was specified.

• <V1> is the duplicated DATEFORMAT parametervalue.


FPEU0005S <V1> IS AN INVALID DELIMITERIN THE DATEFORMAT PARAMETER

ExplanationValid delimiters are the “/”, “—”, or “.” characters.

• <V1> is the invalid delimiter.

User responseUse a valid delimiter.

FPEU0006I DATEFORMAT PARAMETER OF<V1> HAS BEEN ACCEPTED

ExplanationThe supplied DATEFORMAT parameter was accepted.

• <V1> is the accepted DATEFORMAT parameter.

User responseNone.

FPEU0007U UNABLE TO LOAD ISPF SUPPORTMODULE

ExplanationThe ISPF services are required to run OMEGAMON XEfor DB2 PE but the support module could not beloaded. This message should be accompanied byanother message indicating the problem.

User responseSee the accompanying message to correct the error.

FPEU0008U UNABLE TO USE ISPF SERVICES

ExplanationThe ISPF services are required to run OMEGAMON XEfor DB2 PE but could not be used. This messageshould be accompanied by another message indicatingthe problem.


FPEU0009S PROCESSING HAS BEENTERMINATED DUE TO PREVIOUSERRORS

ExplanationNone.

User responseCheck the previous error messages, correct the input,and rerun the job.

FPEU0011U UNABLE TO INIT BASE SERVICES

ExplanationAn error occurred during initialization of the baseservices. This message should be accompanied byanother message indicating the problem.


FPEU0015I SECOND SESSION NOTSUPPORTED

ExplanationA second session of the OMEGAMON for DB2 PE ISPFOnline Monitor is started in a ISPF split screen. Thissecond session is not supported.

User responseNone.

FPEU0020E UNABLE TO ALLOCATE VIRTUALSTORAGE. GETMAIN RETURNCODE: <V1>, STORAGEREQUESTED: <V2>, SUBPOOL:<V3>, LOCATION: <V4>

ExplanationAn error occurred attempting to allocate virtualstorage.


• <V1> is the GETMAIN return code.• <V2> is the STORAGE length.• <V3> is the SUBPOOL.• <V4> is the location.


FPEU0021W UNABLE TO FREE VIRTUALSTORAGE. FREEMAIN RETURNCODE: <V1>, STORAGE ADDRESS:<V2>, STORAGE LENGTH: <V3>,SUBPOOL: <V4>

ExplanationAn error occurred attempting to free virtual storage.

• <V1> is the FREEMAIN return code.• <V2> is the STORAGE address.• <V3> is the STORAGE length.• <V4> is the SUBPOOL.


FPEU0022W UNABLE TO RELEASE VIRTUALSTORAGE FROM SUBPOOL <V2>.FREEMAIN RETURN CODE: <V1>

ExplanationAn error occurred attempting to release virtualstorage.

• <V1> is the FREEMAIN return code.• <V2> is the SUBPOOL.


FPEU0025E AN ERROR OCCURRED DURINGDYNALLOC. DYNALLOC RETURNCODE: <V1>, ERROR REASONCODE: <V2>, INFORMATIONREASON CODE: <V3>

ExplanationAn error occurred during dynamic allocation.

• <V1> is the DYNALLOC return code.

• <V2> is the error reason code.• <V3> is the information reason code.

User responseSee MVS Messages and Codes (or the correspondingmanual of the MVS version you have installed) for anexplanation of the return code and reason codes. If theproblem recurs, contact IBM support.

FPEU0027E UNABLE TO LINK TO MODULE<V1>. ABEND CODE <V2>

ExplanationA link could not be made to the load module requiredfor OMEGAMON XE for DB2 PE.

• <V1> is the name of the module.• <V2> is the abend code returned from the system.

User responseSee MVS Messages and Codes.

FPEU0028E UNABLE TO LOAD MODULE <V1>.ABEND CODE <V2>

ExplanationA load module required to run OMEGAMON XE for DB2PE could not be loaded into virtual storage.

• <V1> is the name of the load module.• <V2> is the abend code returned from the system.

User responseSee MVS Messages and Codes for an explanation of thesystem abend code.

FPEU0029W UNABLE TO DELETE MODULE<V1>. RETURN CODE <V2>

ExplanationA load module previously loaded by OMEGAMON XEfor DB2 PE could not be deleted from virtual storage.

• <V1> is the load module not dropped.• <V2> is the return code from SVC 9.


FPEU0040W VSAM FILE <V1> WAS OPENEDSUCCESSFULLY BUT A WARNINGWAS ISSUED. VSAM RETURN


CODE: <V2>, VSAM REASON CODE<V3>

ExplanationNone.

• <V1> is the name of the VSAM file.• <V2> is the VSAM return code.• <V3> is the VSAM reason code.


FPEU0041E VSAM FILE <V1> COULD NOT BEOPENED. VSAM RETURN CODE:<V2>, VSAM REASON CODE: <V3>

ExplanationNone.

• <V1> is the name of the VSAM file.• <V2> is the VSAM return code.• <V3> is the VSAM reason code.


FPEU0042E FILE <V1> COULD NOT BEOPENED. SYSTEM ABEND CODE:<V2>

ExplanationNone.

• <V1> is the file name• <V2> is the system abend code

User responseSee the operating system documentation for anexplanation of the system abend. If the problemrecurs, contact IBM support.

FPEU0043E FILE <V1> WAS NOT OPENED. ITHAS AN INCORRECT RECORDFORMAT

ExplanationNone.

• <V1> is the file name.

User responseAllocate the file with the correct record format. See theReport Command Reference for more information. Therecord formats are described in "The PerformanceExpert command Stream", section "DD Statements".

FPEU0044E FILE <V1> WAS NOT OPENED. ITHAS AN INCORRECT RECORDLENGTH

ExplanationNone.

• <V1> is the file name.

User responseAllocate the file with the correct record length. See theReport Command Reference for more information.

FPEU0045E UNABLE TO READ FROM FILE<V1>. SYSTEM ABEND CODE: <V2>

ExplanationAn error occurred while reading from a file.

• <V1> is the file name.• <V2> is the system abend code.

User responseSee MVS Messages and Codes for an explanation of thesystem abend code. If the problem recurs, contactIBM support.

FPEU0046E UNABLE TO READ FROM FILE<V1>. SYSTEM MESSAGE BUFFER:<V2>

ExplanationAn error occurred while reading from a file.

• <V1> is the file name.• <V2> is the system message buffer.

User responseSee the SYNADAF macro in DSFSMS/MVS MacroInstruction for Data Set for the system message buffercode.

FPEU0047E UNABLE TO WRITE TO FILE <V1>.SYSTEM ABEND CODE: <V2>

ExplanationAn error occurred while writing to a file.




FPEU0048E UNABLE TO WRITE TO FILE <V1>.SYSTEM MESSAGE BUFFER: <V2>

ExplanationAn error occurred while writing to a file.



FPEU0049E VSAM FILE <V1> COULD NOT BECLOSED. VSAM REASON CODE:<V2>

ExplanationAn error occurred closing the VSAM file.

• <V1> is the VSAM file.• <V2> is the VSAM reason code.


FPEU0050E FILE <V1> COULD NOT BE CLOSED.SYSTEM ABEND CODE: <V2>

ExplanationAn error occurred closing a file.



FPEU0051E FILE <V1> COULD NOT BE CLOSED.SYSTEM MESSAGE BUFFER: <V2>

ExplanationAn error occurred closing a file.



FPEU0052E UNABLE TO EXTRACT DIRECTORYINFORMATION FOR MEMBER <V1>IN FILE <V2>. RETURN CODE<V3>, REASON CODE <V4>

ExplanationNone.

• <V1> is the member name.• <V2> is the file name.• <V3> is the return code.• <V4> is the reason code.

User responseSee the BLDL macro in DSFSMS/MVS Macro Instructionfor Data Set for the system message buffer code.

FPEU0053E UNABLE TO FIND MEMBER <V1>IN FILE <V2>. RETURN CODE<V3>, REASON CODE <V4>

ExplanationNone.

• <V1> is the member name.• <V2> is the file name.• <V3> is the return code.• <V4> is the reason code.

User responseSee the FIND macro in DSFSMS/MVS Macro Instructionfor Data Set for the system message buffer code.

FPEU0060E CODEPAGE TRANSLATION FAILEDWITH RETURN CODE <V1>,REASON CODE <V2>.

ExplanationThe codepage translation failed. The z/OS Support forUnicode has returned the specified values. <V1> is the


return code from z/OS Support for Unicode, <V2> isthe reason code from z/OS Support for Unicode.

DB2 trace records might contain strings in Unicode(UTF-8) format. OMEGAMON XE for DB2 PE uses thez/OS Support for Unicode to convert these strings toother CCSIDs for output to reports. This requires thatthe z/OS Support is set up correctly on the systemwhere OMEGAMON XE for DB2 PE is executed. On asystem where DB2 is installed this will be the caseautomatically because DB2 also requires this support.

User responseCheck that the z/OS Support for Unicode is installedcorrectly and provides conversions from CCSID 1208to the destination EBCDIC CCSID 500. Check thesystem log for additional messages.

FPEU0100S INFORMATION FOR PROBLEMANALYSIS BY SUPPORT:REFERENCE IS MODULE <V1>,CODE=<V2>

ExplanationThis message does not necessarily indicate an errorcondition. It is used to assist internal analysis ofproblems if reported to IBM.

User responseLook at the messages immediately preceding andfollowing this message. Contact IBM support if one ofthese messages indicates an problem that cannot besolved.

FPEU0101S INTERNAL ERROR IN MODULE<V1>, CODE=<V2>, DIAGNOSTICDATA=<V3>

ExplanationAn internal error occurred because a task that isnormally started by the data collector for theOMEGAMON XE for DB2 PE Client was startedmanually. Data collector started tasks are started byOMEGAMON XE for DB2 PE when needed, and mustnot be started manually.

• <V1> is the module name.• <V2> is the error code.• <V3> is the diagnostic data.


FPEU0200S DB2 CAF SUPPORT CANNOT BELOADED. DB2 LOAD LIBRARY MAYNOT BE SPECIFIED IN STEPLIB

ExplanationOMEGAMON XE for DB2 PE could not load the CallAttach Facility (CAF) support modules. One possiblereason is that the DB2 load library is missing in theSTEPLIB DD statement.

User responseDetermine why OMEGAMON XE for DB2 PE cannotload the required modules. Resubmit the job.

FPEU0201S CALL ATTACH FUNCTION <V1>FAILED. RETURN CODE <V2>,REASON CODE <V3>

ExplanationA problem was encountered while establishing aconnection to DB2.

• <V1> is the Call Attach Facility (CAF) function.• <V2> is the return code.• <V3> is the reason code.


FPEU0202S UNICODE CONVERSION SUPPORTCANNOT BE LOADED. Z/OSSUPPORT FOR UNICODE MAY NOTBE INSTALLED CORRECTLY.

ExplanationThe z/OS Support for Unicode could not be loaded toperform a required codepage translation. Programexecution is terminated.

DB2 trace records might contain strings in Unicode(UTF-8) format. OMEGAMON XE for DB2 PE uses thez/OS Support for Unicode to convert these strings toother CCSIDs for output to reports. This requires thatthe z/OS Support is set up correctly on the systemwhere OMEGAMON XE for DB2 PE is executed. On asystem where DB2 is installed this will be the caseautomatically because DB2 also requires this support.

User responseCheck that the z/OS Support for Unicode is installedcorrectly and provides conversions from CCSID 1208


to the destination EBCDIC CCSID. Check the systemlog for additional messages.

FPEU0400W MONITORING OF ACCELERATORVERSION 4 IS NOT FULLYSUPPORTED. REPORTS DO NOTSHOW ALL ACCELERATOR-RELATED COUNTERS.

ExplanationThis version of OMEGAMON for Db2 PE does notsupport DB2 accelerator trace data version 4.

Therefore the accelerator information in batch reports,statistics, and record trace does not inlcude allperformance-related fields.

User responseTo receive complete information about acceleratormonitoring, install the latest version of OMEGAMON forDb2 PE.

FPEV - Data Server messagesFPEV0000I DATA SERVER INITIALIZATION

BEGINS - <V1>

ExplanationNone.

• <V1> is the date and the time the PE Server subtaskstarts.

User responseNone.

FPEV0001S MVS MUST BE ESA 3.1.3 OR LATER

ExplanationNone.

User responseInstall the correct release of MVS.

FPEV0002S <V1> INTERNAL ERROR. NUMBER<V2>, CODE <V3>


• <V1> is the DB2 subsystem ID.• <V2> is the internal error number.• <V3> is the internal error code.

User responseStop and restart the Data Server using the MODIFYcommand. If the problem recurs, contact IBM support.

FPEV0003S <V1> GETMAIN <V2> FAILED. SIZE<V3>, RC <V4>

ExplanationThere is insufficient storage.

• <V1> is the DB2 subsystem ID.• <V2> is an internal code that identifies the

GETMAIN.• <V3> is the size.• <V4> is the return code.

User responseIncrease the OMEGAMON Collector started task regionsize and restart the OMEGAMON Collector.

FPEV0004S <V1> ATTACH FAILED FORMODULE <V2>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the module name.

User responseEnsure that the module is present in the PerformanceExpert load library or in the LPA.

FPEV0005S <V1> ISPF OLM SUBSYSTEMINITIALIZATION FAILED

ExplanationCross-memory initialization failed.



User responseCheck the log for preceding messages or abend codes.If the problem cannot be corrected and recurs, contactIBM support.

FPEV0006I <V1> DATA SERVERINITIALIZATION COMPLETE

ExplanationNone.


User responseNone.

FPEV0007I DATA SERVER ENDED

ExplanationNone.

User responseNone.

FPEV0008S <V1> LOAD FOR MODULE <V2>FAILED

ExplanationLoad for the specified module failed.

• <V1> is the DB2 subsystem ID.• <V2> is the module name.

User responseEnsure that the module is present in the PerformanceExpert load library or can be located in the normalsearch sequence.

FPEV0011I DATA SERVER IS STOPPING

ExplanationNone.

User responseNone.

FPEV0013I <V1> TASK <V2> BEINGREATTACHED

ExplanationTask may have terminated and is being reattached.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the task.

User responseNone.

FPEV0014E <V1> HISTORY TASK COULD NOTBE REINITIALIZED RC <V2>

ExplanationHistory reinitialization failed.

• <V1> is the DB2 subsystem ID.• <V2> is the return code.


FPEV0015W <V1> SERVER INSTANCE ALREADYSTARTED FOR THIS DB2SUBSYSTEM

ExplanationNone.


User responseNone.

FPEV0016E <V1> TOKEN <V2> IS NOTRECOGNIZED

ExplanationThe token or keyword is not valid for the Data Serverparameter.

• <V1> is the DB2 subsystem ID.• <V2> is the token.


FPEV0017E <V1> VALUE <V2> LESS THANMINIMUM OF <V3> FOR KEYWORD<V4>

ExplanationNone.



• <V2> is the value entered.• <V3> is the minimum value.• <V4> is the keyword.


FPEV0018E <V1> VALUE <V2> EXCEEDSMAXIMUM OF <V3> FORKEYWORD <V4>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the value entered.• <V3> is the maximum value.• <V4> is the keyword.


FPEV0019E <V1> <V2> FOUND, BUT <V3>EXPECTED FOR KEYWORD <V4>

ExplanationAn invalid parameter was entered for the specifiedkeyword.

• <V1> is the DB2 subsystem ID.• <V2> is the parameter entered by the user.• <V3> is the expected parameter.• <V4> is the keyword.


FPEV0020E <V1> <V2> IS INVALID FORKEYWORD <V3>


• <V1> is the DB2 subsystem ID.• <V2> is the parameter entered by the user.• <V3> is the keyword.


FPEV0021S <V1> END OF LINE FOUNDBEFORE END OF <V2>PARAMETER

ExplanationThe command in one of the RKD2PAR data setmembers is incomplete.

• <V1> is the DB2 subsystem ID.• <V2> is the parameter or keyword.


FPEV0022E <V1> NUMERIC VALUE EXPECTED.<V2> FOUND FOR KEYWORD <V3>


• <V1> is the DB2 subsystem ID.• <V2> is the parameter that was entered by the user.• <V3> is the keyword.


FPEV0024E <V1> TASK <V2> IS NOT BEINGREATTACHED DUE TO REPEATEDERRORS

ExplanationRepeated abends occurred.

• <V1> is the DB2 subsystem ID.• <V2> is the task.

User responseIt may be necessary to stop and restart the DataServer using the MODIFY command. Check the log forpreceding messages or abend codes. If the problemcannot be corrected and recurs, contact IBM support.

FPEV0025E <V1> <V2> IS TOO LONG FORKEYWORD <V3>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the parameter entered by the user.


• <V3> is the keyword.


FPEV0027E <V1> TASK <V2> TERMINATEDWITH ERROR CODE <V3>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the task.• <V3> is the error code.

User responseThe Data Server reattaches the task unless it haspreviously terminated within the last minute. Checkthe log for preceding messages or abend codes. If theproblem cannot be corrected and recurs, contact IBMsupport.

FPEV0028E <V1> TASK <V2> TERMINATED.CODE <V3>

ExplanationThe task terminated.

• <V1> is the DB2 subsystem ID.• <V2> is the task.• <V3> is the abend code.

User responseThe Data Server reattaches the task unless it haspreviously terminated within the last minute. Checkthe log for preceding messages or abend codes. If theproblem cannot be corrected and recurs, contact IBMsupport.

FPEV0029I <V1> DISPLAY COMMAND OUTPUTBEGINS

ExplanationIssued in response to a DISPLAY command.


User responseNone.

FPEV0030I <V1> CURRENT USERS

ExplanationThis message is issued in response to a DISPLAYcommand.


User responseNone.

FPEV0031I <V1> USERID <V2>, STATUS <V3>


• <V1> is the DB2 subsystem ID.• <V2> is the user ID.• <V3> is the status.

User responseNone.

FPEV0032I <V1> CURRENT DB2INDEPENDENT PARAMETERS



User responseNone.

FPEV0033I <V1> DB2SSID=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the SSID.

User responseNone.

FPEV0034I <V1> PLAN NAME=<V2>



• <V1> is the DB2 subsystem ID.• <V2> is the plan name.

User responseNone.

FPEV0035I <V1> USEDB2AUTHEXIT=<V2>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is:

YESAuthorization checks are done by a user-provided exit based on the DB2 sample authexit.

NOAuthorization checks are done by theauthorization exit provided by PerformanceExpert.

User responseNone.

FPEV0040I DATA SERVER USERID <V1>,GROUP ID <V2>

ExplanationThis message is issued at startup to verify the user IDand group ID.

• <V1> is the user ID from where the Data Server hasbeen started.

• <V2> is the group ID that the Data Server has beenstarted under.

User responseNone.

FPEV0041S <V1> DATA SERVER DOES NOTHAVE THE CORRECT MONITORAUTHORITY

ExplanationThis message is issued during Data Server startup ifthe Data Server does not have the required monitorprivilege.


User responseEnsure that the Data Server user ID is granted therequired privilege.

FPEV0042S <V1> DATA SERVER MUST BE RUNOUT OF AN AUTHORIZED LIBRARY

ExplanationNone.


User responseAuthorize library as specified in the installationprocess and restart the Data Server.

FPEV0043I <V1> HISTORY=<V2>


• <V1> is the Db2 subsystem ID.• <V2> is:

YESHistory data is being collected.

NOHistory data is not being collected. IfHISTORY=NO you can disregard messageFPEV0505W for the same Db2 subsystem if itappears in the job log.

User responseNone.

FPEV0045I <V1> - STATISTICS IS BEINGCOLLECTED, INTERVAL=<V2>SECONDS

ExplanationThis message is issued in response to a DISPLAYcommand or during the Data Server startup.

• <V1> is the DB2 subsystem ID.• <V2> is the interval in which this data is gathered by

the Data Server.

User responseNone.

FPEV0047I <V1> - SYSTEM PARAMETERS AREBEING COLLECTED,INTERVAL=<V2> SECONDS




the Data Server.

User responseNone.

FPEV0049I <V1> - THREAD SQL TEXT ISBEING COLLECTED,INTERVAL=<V2> SECONDS



the Data Server.

User responseNone.

FPEV0051I <V1> - THREAD DETAIL IS BEINGCOLLECTED, INTERVAL=<V2>SECONDS



the Data Server.

User responseNone.

FPEV0052I <V1> - THREAD LOCKING ISBEING COLLECTED,INTERVAL=<V2> SECONDS



the Data Server.

User responseNone.

FPEV0053I <V1> - THERE ARE <V2> HISTORYQUALIFICATIONS ACTIVE.PRIMAUTH PLANNAMECONNECTION ID CORRELATIONNAME


• <V1> is the DB2 subsystem ID.• <V2> is the number of active history qualifications.

User responseNone.

FPEV0054I <V1> <V2> <V3> <V4> <V5>


• <V1> is the DB2 subsystem ID.• <V2> is the plan name.• <V3> is the primary authorization ID.• <V4> is the connection ID.• <V5> is the correlation ID.

User responseNone.

FPEV0056I <V1> - SHDATASETSIZE=<V2>MEGABYTES


• <V1> is the DB2 subsystem ID.• <V2> is the number of pages.

User responseNone.

FPEV0057I <V1> DISPLAY COMMAND OUTPUTENDS




User responseNone.

FPEV0058I <V1> NO CURRENT USERS



User responseNone.

FPEV0059E <V1> DB2 INTERFACE TASK DIDNOT RESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server is stopped, the connectionbetween DB2 and the Data Server does not terminatecorrectly.


User responseNone.

FPEV0060E <V1> USER MANAGER TASK DIDNOT RESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server is stopped, the connectionbetween the user manager and the Data Server doesnot terminate correctly.


User responseNone.

FPEV0062E <V1> HISTORY MANAGER TASKDID NOT RESPOND TOTERMINATION REQUEST

ExplanationWhen the Data Server is stopped, the connectionbetween the history manager and the Data Serverdoes not terminate correctly.


User responseNone.

FPEV0063S <V1> DB2 INTERFACEINITIALIZATION DID NOTCOMPLETE WITHIN <V2>SECONDS OF SERVER INSTANCESTARTUP

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the number of seconds.

User responseThe Data Server thread may be queued at threadcreation. Restart the Data Server. Check the log forpreceding messages or abend codes. If the problemcannot be corrected and recurs, contact IBM support.

FPEV0064I <V1> CAF ERROR WHEN DB2INTERFACE ATTEMPTED TOCONNECT TO DB2 CAF. RC <V2>,REASON <V3>

ExplanationNone.



FPEV0065S <V1> LX RESERVE FAILED. RC<V2>

ExplanationAn error occurred when attempting to reserve a linkingindex. The Data Server terminates.




User responseCheck the log for preceding messages or abend codesand restart the Data Server. If the problem cannot becorrected and recurs, contact IBM support.

FPEV0066I <V1> - <V2> EXCEPTION EVENTS

ExplanationIssued in response to a DISPLAY command.

• <V1> is the DB2 subsystem ID.• <V2> is the exception event type, as follows:

AUTHFAILCollecting events with:

START TRACE(STAT) CLASS(4) DEST(OPx)

CF REBUILDCollecting coupling facility events with:


DDFCollecting events with:

START TRACE(PERM) CLASS(1) DEST(OPx)

DEADLOCKCollecting deadlocks events with:

START TRACE(PERM) CLASS(6) DEST(OPx) IFCID(196)

DSEXTENTCollecting dataset extent events with:


EDMPOOLCollecting events with:

START TRACE(AUDIT) CLASS(1) DEST(OPx)

GLBLTRACECollecting global trace events with:

START TRACE(PERFM) CLASS(30) DEST(OPx) IFCID(90)

LOGSPACECollecting log space shortage events with:


TIMEOUTCollecting events with:

START TRACE(PERM) CLASS(6) DEST(OPx) IFCID(172)

URPROBLEMCollecting unit of recovery problem events with:


User responseNone.

FPEV0067I <V1> DB2COMMAND='<V2>'

ExplanationThe DB2 command issued on a locally connectedsubsystem has failed.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 command.• <V3> is the IFI return code.• <V4> is the IFI reason code.

User responseFor a more detailed description of the problem, seethe DB2 9 Administration Guide.

FPEV0068I <V1> <V2>

ExplanationInformational message.

• <V1> is the DB2 subsystem ID.• <V2> is the resulting output upon issuing a DB2

command.

User responseNone.

FPEV0069I <V1> IFI ERROR WHEN ISSUINGDB2COMMAND '<V2>'. IFI RC<V3>, REASON <V4>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the IFI return code.• <V3> is the IFI reason code.



FPEV0070S <V1> DB2 SUBSYSTEM ID NOTSPECIFIED

ExplanationNone.


User responseSpecify a DB2 subsystem and restart the Data Server.

FPEV0071I <V1> COMMAND: <V2>

ExplanationThis is the command text processed by the DataServer.

• <V1> is the DB2 subsystem ID.• <V2> is the command entered.

User responseNone.

FPEV0072W <V1> THIS PARAMETER CANNOTBE CHANGED FROM THE CONSOLE

ExplanationNone.


User responseNone.

FPEV0076W <V1> DB2 INTERFACE IFI READSDID NOT COMPLETE WITHIN <V2>SECONDS

ExplanationNone. The Data Server will attempt the READSoperation again.

• <V1> is the DB2 subsystem ID.• <V2> is the number of seconds.

User responseNone.

FPEV0080I <V1> DB2 SUBSYSTEM <V2>STOPPED <V3>

ExplanationNone.

• <V1> is the name of the master controller inside theOMEGAMON Collector (MSTR).

• <V2> is the DB2 subsystem ID.• <V3> is the reason for the DB2 subsystem to stop:

QUIESCENormal stop of the DB2 subsystem. Currentthreads can run to completion, and new threadscan be allocated to an application that is running.

FORCENormal stop of the DB2 subsystem. No newthreads are allocated, and work on existingthreads is rolled back.

ABTERMAbnormal stop of the DB2 subsystem.

User responseNone.

FPEV0081I <V1> DB2 SUBSYSTEM <V2>STARTED

ExplanationNone.



User responseNone.

FPEV0093I <V1> DATA SERVER INTERNALTRACE STATUS:

ExplanationThis message is displayed in response to a DISPLAYcommand.


User responseNone.

FPEV0098I <V1> - DATA SERVER TRACE=<V2>



• <V1> is the DB2 subsystem ID.• <V2> is:

ONThe Data Server trace is active.

OFFThe Data Server trace is not active.

User responseNone.

FPEV0099I <V1> DATA MANAGER TASK DIDNOT RESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server was stopped, the Data Servertask did not end correctly.


User responseNone.

FPEV0100I THIS FIELD WAS FOUND INEXCEPTION: <V1>

ExplanationThis message is displayed by the user exit routineFPEMUPXT.

For an exception, the message is:

FPEV0100I <V1> EVENT EXCEPTION REPORTED <V2>

• <V1> is the DB2 subsystem ID.• <V2> can be one of the following:

– DEADLOCK EVENT– TIMEOUT– EDM POOL FULL– AUTHORIZATION FAILURE– THREAD COMMIT INDOUBT– CF START OF A REBUILD– CF END OF A REBUILD– GLOBAL TRACE STARTED– DATA SET EXTENSION– UNIT OF RECOVERY PROBLEM

– LOG SPACE SHORTAGE

For a periodic exception, the message can look likethis:

FPEV0100I <V1> FIELD FOUND IN EXCEPTION BY DB2PERFORMANCE MONITOR<V2>,<V3><V4>,<V5>,<V6>,<V7>,<V1>,<V8><V9>,<V10>,<V11>,<V12>,<V13>,<V14>

• <V1> is the Performance Expert subsystem ID.• <V2> is the field name qualifier used in the

Exception Threshold data set (8 characters).• <V3> is the field description (40 characters).• <V4> is the event: ACCT = Accounting, STAT =

Statistics, THRD = Thread.• <V5> is the primary authorization ID (8 characters).• <V6> is the plan name (8 characters).• <V7> is the connection ID (8 characters).• <V1> is the DB2 subsystem ID (8 characters).• <V8> is the DB2 timestamp: yyyy-mm-dd-hh.mm.ss.mmmmmm (26 characters).

• <V9> is the exception level: P = Problem, W =Warning.

• <V10> is the exception value (12 characters).• <V11> is the operator: > or <.• <V12> is the threshold value (12 characters).

The following two fields are displayed only if theexception is related to a thread:

• <V13> is the LUWID (8 characters network ID-8characters LU name-12 characters Instancenumber).

• <V14> is the DB2 token.

If the IBM-supplied user exit routine FPEMUPXT wasmodified in your installation, this message may bedifferent or missing.

User responseNone.

FPEV0102W <V1> PURGE COMMAND ALLOWSSPECIFICATION OF ONE "USER-ID/GROUP-ID" ONLY. ANYADDITIONAL SPECIFICATION OF"USER-ID/GROUP-ID" ISIGNORED

ExplanationThis message is displayed in response to a PURGEcommand that has failed. The operator has tried to


specify more than one USER-ID/GROUP-ID to bepurged, but only one is allowed.


User responseSpecify only one USER-ID/GROUP-ID.

FPEV0103E <V1> GLOBAL SERVICES MAINTASK DID NOT RESPOND TOTERMINATION REQUEST

ExplanationWhen the Data Server was stopped, the global servicesmain task did not end correctly.


User responseNone.

FPEV0104E <V1> USS0 MAIN TASK DID NOTRESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server was stopped, the USS0 maintask did not end correctly.


User responseNone.

FPEV0105E <V1> UAS0 MAIN TASK DID NOTRESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server was stopped, the UAS0 maintask did not end correctly.


User responseNone.

FPEV0106I <V1> CCP=<V2>



• <V2> is:YES

CCP (collect CPU parallelism) is active.NO

CCP (collect CPU parallelism) is not active.

User responseNone.

FPEV0107I <V1> - CCPDSS=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the CCP (collect CPU parallelism) data space

size in page units.

User responseNone.

FPEV0108E <V1> DB2COMMAND=('<V2>','<V3>') COULD NOT BE EXECUTEDON SPECIFIED DB2 MEMBER

ExplanationThis message is issued during the Data Server startupif <V1> is not a data sharing group member. Therefore,the command cannot be executed on DB2 member<V3>.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 command specified when the Data

Server was started.• <V3> is the DB2 member on which the command

should have been executed.

User responseRemove the command from the Data Server startupfile, or remove the DB2 member <V3> if the commandshould be executed on a local DB2 subsystem.

FPEV0109I <V1> IFI ERROR WHEN ISSUINGDB2COMMAND '<V2>' ON MEMBER<V3>. IFI RC <V4>, REASON <V5>

ExplanationThe DB2 command issued on member <V3> has failed.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 command.


• <V3> is the DB2 member in the data sharing groupfor which the command was executed.

• <V4> is the IFI return code.• <V5> is the IFI reason code.

User responseFor a more detailed description of the problem, seethe DB2 9 Administration Guide.

FPEV0110I <V1> DATASHARINGGROUP=<V2>



YESThe data sharing group is monitored if thesubsystem referenced by <V1> is connected to adata sharing group.

NOOnly the DB2 subsystem <V1> is monitored,even if connected to a data sharing group.

User responseNone.

FPEV0111I <V1>DB2COMMAND=('<V2>','<V3>')


• <V1> is the DB2 subsystem ID.• <V2> is the DB2 command specified when the Data

Server was started.• <V3> is the DB2 member in the data sharing group

for which the command was executed (optional).

User responseNone.

FPEV0112I <V1> USEUSERAUTHEXIT=<V2>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is:

YESA user-provided exit is used to restrict the user’sauthority to specific areas, for example, statisticsdata only or thread data only.

NOThe DB2 security scheme is used to restrict theuser’s authority.

User responseNone.

FPEV0113S <V1> SERVER INSTANCE IS NOTAUTHORIZED TO USE THESPECIFIED PLAN <V2> OR PLANDOES NOT EXIST

ExplanationThis message is issued during the Data Server startupif the data collector cannot access the required DB2plan. It is the result of the following DB2 reason codes:00F30034

DB2 plan authorization failure or plan is notavailable

00F30040Resource is not available or unknown

• <V1> is the DB2 subsystem ID.• <V2> is the plan name as it was specified in the

startup parameter PLANNAME.

User responseEnsure that the Data Server plans are installed andthat access is granted to the Data Server user ID.

FPEV0114I SERVICE LEVEL IS <V1> APAR<V2>

ExplanationThis message is issued during the startup of the PEServer subtask.

• <V1> is the date and the time when the PE Serversubtask is compiled.

• <V2> is the APAR number of the installed PE Serversubtask service level.

User responseNone.

FPEV0115I <V1> - SQLCACHE IS BEINGCOLLECTED, INTERVAL=<V2>SECONDS




the Data Server.

User responseNone.

FPEV0116I <V1> - DATA SET STATISTICS ISBEING COLLECTED,INTERVAL=<V2> SECONDS



the Data Server.

User responseNone.

FPEV0118S <V1> DB2 <V2> IS NOTSUPPORTED BY THIS VERSION OFOMEGAMON XE DB2 PE.

ExplanationYou have tried to monitor a DB2 subsystem versionthat is not supported by this version of OMEGAMON XEDB2 PE. This can happen if your DB2 version is mucholder than your OMEGAMON XE DB2 PE version or ifyour OMEGAMON XE DB2 PE version is older than theDB2 version you want to monitor.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 version and release.

User responseDepending on the reason for this message, install ahigher OMEGAMON XE DB2 PE version or upgrade yourDB2 subsystem.

FPEV0119I <V1> USER NOT ALLOWED TOEXECUTE OMEGAMON XE DB2 PEOPERATOR COMMANDS.COMMAND CANCELED

ExplanationThis is an internal message which is not displayed onthe system.

User responseNone.

FPEV0121I <V1> KEYWORD <V2> ISOBSOLETE AND IGNORED, USE<V3> INSTEAD

ExplanationThe obsolete keyword <V2> was found in the DataServer parmlib RKD2PAR. The keyword <V3> is usedinstead.

• <V1> is the DB2 subsystem ID.• <V2> is the obsolete keyword.• <V3> is the keyword that is used instead of the one

that has become obsolete.

User responseTo avoid this message in future, remove the obsoletekeyword from the Data Server parmlib. Refer to DB2Installation Guide manual for further information aboutkeyword <V3>.

FPEV0122I <V1> - MAXIMUM NUMBER OFPARALLEL SESSIONS=<V2>

ExplanationThis message is shown during the Data Server startupor in response to a DISPLAY command. It is ignored.

• <V1> is the DB2 subsystem ID.• <V2> is the maximum allowed number of

simultaneous sessions (APPC and TCP/IP).

User responseNone.

FPEV0123I <V1> SESSION INFORMATION -BEGIN



User responseNone.


FPEV0124I <V1> SESSION STATUS UIDDETAILS



User responseNone.

FPEV0125I <V1> <V2> <V3> <V4> <V5>

ExplanationThis message is displayed in response to a DISPLAYcommand. The Data Server was started withoutsupport for workstation clients (for example, TCP/IP orAPPC).

• <V1> is the DB2 subsystem ID.• <V2> is the number of the session manager.• <V3> is the status of the session manager. It can be:

INACTThe session manager is not active.

TCPIP-MThe client is connected to the session managervia TCP/IP and is using the multi-user mode.

TCPIP-SThe client is connected to the session managervia TCP/IP and is using the single-user mode.

APPC-SThe client is connected to the session managervia APPC and is using the single-user mode.

PEND-MThe session manager is inactive and waiting foroutstanding DB2 responses. The clientpreviously connected was using the multi-usermode.

PEND-SThe session manager is inactive and waiting foroutstanding DB2 responses. The clientpreviously connected was using the single-usermode.

• <V4> is the user ID of the connected client.• <V5> is detailed information about the client

connection. It can be:IP: xxx.xxx.xxx.xxx:YYYYY

The client session was established via TCP/IP.xxx.xxx.xxx.xxx is the TCP/IP address of theclient and yyyyy the port number of the client.

LU: xxxThe client session was established via APPC. xxxis the LU name of the connected client.

User responseNone.

FPEV0126I <V1> SESSION INFORMATION -END



User responseNone.

FPEV0127I <V1> NO ACTIVE SESSIONSBECAUSE NO COMMUNICATIONINTERFACE IS ACTIVE

FPEV0128S <V1> CONNECT TO DB2 FAILED.MONITOR TRACE IS NOT STARTED

ExplanationThis message is issued during the Data Server startupbecause the Monitor trace is not active.


User responseIssue a DB2 START TRACE command for monitorclass 1.

FPEV0129I <V1>PERFORMANCEWAREHOUSE=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is: YES Performance Warehouse is active. NO

Performance Warehouse is inactive.

User responseNone.

FPEV0130E <V1> DATASERVERHLQ NOTSPECIFIED


ExplanationThis message is shown during the Data Collectorstartup.


User responseSpecify the high-level qualifier for work data sets forthe OMEGAMON Collector and the PerformanceWarehouse function. For further information on how toset up the OMEGAMON Collector, see Installation andConfiguration and the Configuration Tool (formerlyICAT) online help.

FPEV0131E PERFORMANCEWAREHOUSEADDRESSSPACENAME NOTSPECIFIED FOR SERVERINSTANCE <V2>

ExplanationThis message is shown during the Data Server startup,if startup parameter PERFORMANCEWAREHOUSE isset, but required startup parameterPERFORMANCEWAREHOUSEADDRESSSPACENAME ismissing.

User responseSpecify the name for the Performance Warehouse JCL.For further information on how to set up the DataServer for the Performance Warehouse, seeInstallation and Configuration or the Configuration Tool(formerly ICAT) online help.

FPEV0133I <V1> -PERFORMANCEWAREHOUSEADDRESSSPACENAME=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the name of the Performance Warehouse

JCL.

User responseNone.

FPEV0134W <V1> PARAMETER <V2> CANNOTBE SPECIFIED AS STARTUPPARAMETER, IT IS IGNORED

ExplanationThis message is issued during the Data Server startup,if a parameter was specified that is only accepted asMODIFY command via the system console.

• <V1> is the DB2 subsystem ID.• <V2> is the parameter you tried to set

User responseRemove the parameter from the Data Server parmlibRKD2PAR.

FPEV0135W <V1> PERFORMANCEWAREHOUSEIS NOT REQUESTED. THECOMMAND IS IGNORED

ExplanationThis message is issued in response to a MODIFYcommand. You tried to stop the PerformanceWarehouse function, but this function is alreadystopped.


User responseNone.

FPEV0136W <V1> PERFORMANCEWAREHOUSE IS ACTIVE. THECOMMAND IS IGNORED

ExplanationThis message is issued in response to a MODIFYcommand. You tried to start the PerformanceWarehouse function while this function is alreadyactive.


User responseIf you tried to start the Performance Warehousefunction in forced mode, stop it first and then restart itin forced mode.

FPEV0137E LICENSE NOT FOUND

ExplanationThe license FMID for OMEGAMON XE for DB2 PE is notcorrectly installed.

User responseIf errors occurred during installation, correct them andtry to use OMEGAMON XE for DB2 PE again.


If OMEGAMON XE for DB2 PE installed without errors,and you followed the recommended installation andcustomization procedures, and the problem persists,contact IBM support.

FPEV0140E <V1> <V2> IS TOO SHORT FORKEYWORD <V3>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the parameter you tried to set.• <V3> is the keyword.


FPEV0143I <V1> – FILE I/O TRACE=<V2>


• <V1> is the DB2 subsystem ID.• <V2>

– OFF: The file I/O trace is inactive.– ON: The file I/O trace is active.

User responseNone.

FPEV0144I <V1> - DB2C SYSTEM IS BEINGCOLLECTED, INTERVAL=<V2>SECONDS



the Data Server.

User responseNone.

FPEV0145I <V1> - DB2C APPLICATION ISBEING COLLECTED,INTERVAL=<V2> SECONDS



the Data Server.

User responseNone.

FPEV0146I <V1> AUTOMATICAGENTUPDATE=<V2>

ExplanationThis message is issued in response to anAUTOMATICAGENTUPDATE command or during theData Server startup.

• <V1> is the DB2 subsystem ID.• <V2> is the option (Yes or NO) specified with the

command

User responseNone.

FPEV0147I <V1> BIND FOR MODULEFPEVWRPA IS MISSING. NO DB2CONNECT DATA IS COLLECTED

ExplanationThis message is issued when access to a PerformanceExpert DB2 table is intended without proper bind ofthe corresponding DBRM.


User responseIssue the corresponding BIND command or run thecorresponding bind job, then restart the Data Server.

FPEV0148E <V1> VALUE EXCEEDS MAXIMUMOF <V2> FOR KEYWORD <V3>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the maximum value.• <V3> is the keyword.



FPEV0149I <V1> NO AUTHORITY FORREQUESTED OPERATION INDGOVWRPA FOR TABLEDB2PM.PARAMETER NO DB2CONNECT DATA IS COLLECTED

ExplanationThis message is issued when access to a PerformanceExpert DB2 table is intended and the user does nothave sufficient DB2 authority.


User responseGrant the required authority to the user.

FPEV0150I <V1> NO AUTHORITY FORREQUESTED OPERATION INDGOVWRPA FOR TABLEDB2PM.HISTORYDATA. NO DB2CONNECT DATA IS COLLECTED




FPEV0151I <V1> COLLECTING ALSO SYSTEMPARAMETERS DATA FOR HISTORYBECAUSE IT IS REQUIRED FORISPF ONLINE MONITOR

ExplanationNone.


FPEV0152I <V1> BIND FOR MODULEFPEVWR2C MISSING. NO DB2CONNECT DATA IS COLLECTED




FPEV0153I <V1> BIND FOR MODULE <V2>MISSING.


• <V1> is the DB2 subsystem ID.• <V2> is the DBRM name.


FPEV0154I <V1> NO AUTHORITY FORREQUESTED OPERATION IN <V2>FOR TABLE <V3>.


• <V1> is the DB2 subsystem ID.• <V2> is the name of the executing module

performing the DB2 operation.• <V3> is the DB2 table name.


FPEV0155I <V1> REQUESTED OPERATION IN<V2> FOR TABLE <V3> FAILED.SQLCODE <V4>.

ExplanationThis message is issued when access to a PerformanceExpert DB2 table fails and no further specificinformation can be provided.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the executing module

performing the DB2 operation.• <V3> is the DB2 table name.• <V4> is the SQL code.


User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the SQL code.

FPEV0157E <V1> SERVER INSTANCE ISSTOPPING BECAUSE OF ANERROR IN THE DB2 INTERFACE.

ExplanationThe DB2 interface returned errors in response to anessential Data Server request and the Data Servercannot recover automatically. The message ispreceded by message FPEV0064I, which displays thecorresponding return and reason codes provided bythe DB2 interface.

User responseTake corrective action based on the displayed returnand reason codes. Verify that the Data Server isinstalled and customized correctly. Restart the DataServer. Refer to Installation and Configuration and IBMDB2 9 for z/OS - Messages and Codes for moreinformation.

FPEV0158W <V1> <V2> DATA SERVERDETECTED HIGH CYCLE TASKUSAGE (<F3> %) IN TASK <V4>.

ExplanationPerformance Expert detects high cycle task usage forone of its components.

• <V1> is the DB2 subsystem ID.• <V2> is the local time.• <F3> is the detected cycle usage.• <V4> is the name of the task.

The OMEGAMON Collector subtask PESERVERperiodically monitors the CPU cycle consumption of itssubtasks in intervals of one minute. If the CPU cycleconsumption of a subtask exceeds an internalthreshold value, the server issues messageFPEV0158W. The threshold value may vary withsituation and subtask. Cycle usage is not percentageusage of total system CPU, but is the percentage usageof the maximum CPU available to that task - typicallypercentage usage of a single CPU. Additionally, theinternal server traces are started and messageFPEV0162W is issued. If the cycle consumption of thesubtask falls below the threshold within the nextsample interval, the internal traces are switched offand normal processing continues. If the CPUconsumption of the subtask remains above thethreshold within the next sample interval, a dump is

taken and message FPEV0159W is issued. If the cycleconsumption of the subtask continues to exceed thethreshold, the subtask will finally be reattached andmessage FPEV0161W is issued.

User responseThis might occur sporadic because of brief peaks inresource usage and can be ignored. If this occursregularly without obvious cause, then the server tracecan be sent to IBM support for investigation.

FPEV0159W <V1> <V2> DUMP IS WRITTENFOR FURTHER ANALYSIS OF HIGHCPU USAGE

ExplanationPerformance Expert detects high CPU usage for one ofits components and starts to dump data for furtheranalysis. The dump is taken for the second occurrenceof high CPU usage. The message is preceded bymessage FPEV0158W.

• <V1> is the DB2 subsystem ID.• <V2> is the local time.

User responseSave the dump for further analysis by IBM.

FPEV0160I <V1> <V2> GPR <F3>-<F4>:'<V5>'X, '<V6>'X, '<V7>'X, '<V8>'X

ExplanationPerformance Expert detects high CPU usage for one ofits components and starts to write the contents of thegeneral purpose registers to the log for furtheranalysis. The message is issued for the secondoccurrence of high CPU usage. The message ispreceded by message FPEV0159W.

• <V1> is the DB2 subsystem ID.• <V2> is the local time.• <F3> to <F4> is the range of registers.• <V5> to <V8> are the register contents.

User responseSave the Performance Expert log (SYSPRINT) forfurther analysis by IBM.

FPEV0161W <V1> <V2> TASK <V3> WASRESTARTED DUE TO CONTINUOUSHIGH CPU USAGE.


ExplanationPerformance Expert detected high CPU usage for oneof its components and the task was stopped andrestarted because of continuous high CPU usage. Themessage is preceded by message FPEV0158W.

• <V1> is the DB2 subsystem ID.• <V2> is the local time.• <V3> is the name of the task.

User responseNone.

FPEV0162W <V1> <V2> TRACES ARE STARTEDFOR FURTHER ANALYSIS OF HIGHSUBTASK USAGE.

ExplanationPerformance Expert detects high cycle usage for oneof its components and is starting internal traces forfurther analysis. The message is preceded by messageFPEV0158W.

• <V1> is the DB2 subsystem ID.• <V2> is the local time.• <V3> is the name of the task.

User responseIf this situation occurs regularly with no obvious causethen save the Performance Expert log (SYSPRINT) forfurther analysis by IBM.

FPEV0163E DATA SERVER IS STOPPINGBECAUSE AS COULD NOT BE MADENONSWAPPABLE

ExplanationDuring startup of the OMEGAMON Collector, theaddress space could not be changed to nonswappable.

User responseContact the system operator. If z/OS should allow tomake address space nonswappable, contact IBMsupport.

FPEV0164I <V1> INSTANCE FOR DB2SUBSYSTEM <V2> IS STARTING

ExplanationThis message is issued during the start of theOMEGAMON Collector, or if a monitored DB2subsystem is brought online again. The corresponding

OMEGAMON Collector parts, monitoring this DB2subsystem, are being started.



User responseNone.

FPEV0165I <V1> INSTANCE FOR DB2SUBSYSTEM <V2> IS STOPPING

ExplanationThis message is issued during shutdown of theOMEGAMON Collector, or if a monitored DB2subsystem is being stopped. The correspondingOMEGAMON Collector parts, monitoring this DB2subsystem, are being stopped.



User responseNone.

FPEV0166E <V1> SERVER INSTANCE FOR DB2SUBSYSTEM <V2> ABENDED.CODE <V3>

ExplanationThe server instance for the specified DB2 subsystemfailed with the indicated abend code.


• <V2> is the DB2 subsystem ID.• <V3> is the MVS abend code.

User responseContact the system operator and check the abendcode. If it is not a system problem, contact IBMsupport.

FPEV0167I <V1> SERVER INSTANCE FOR DB2SUBSYSTEM <V2> IS RESTARTED

ExplanationThe server instance for the specified DB2 subsystemwas previously stopped because of an error or abendand is now being restarted.




User responseNone.

FPEV0168E <V1> SERVER INSTANCE FOR DB2SUBSYSTEM <V2> IS NOT BEINGREATTACHED DUE TO REPEATEDERRORS

ExplanationThe server instance for the specified DB2 subsystemwas previously stopped because of an error or abendand not being restarted because of repeated errors.



User responseCheck SYSPRINT of the OMEGAMON Collector fordetails. Correct the error, if possible. Restart theOMEGAMON Collector.

FPEV0169E <V1> SERVER INSTANCE FOR DB2SUBSYSTEM <V2> STOPPED WITHERROR CODE <V3>

ExplanationThe server instance for the specified DB2 subsystemhas stopped because of errors.


• <V2> is the DB2 subsystem ID.• <V3> is the reason code.

User responseCheck SYSPRINT of the job for stop reasons inpreceding messages. If possible, correct the error. Ifthe error persists, contact IBM support.

FPEV0170E <V1> SERVER INSTANCE FOR DB2SUBSYSTEM <V2> DID NOT REACTON TERMINATION REQUEST

ExplanationDuring shutdown of the OMEGAMON Collector, asubtask did not respond to a termination request.


User responseThis might be a temporary problem. If the problemrecurs at the next server shutdown, contact IBMsupport.

FPEV0171E <V1> DATA SERVER IS OUT OFMEMORY

ExplanationThe OMEGAMON Collector failed while requestingadditional memory. Depending on severity of failedoperation, the server might stop.

• <V1> is the DB2 subsystem ID of the server instancethat failed when requesting memory, or MSTR for themaster controller of all server instances.

User responseCheck the specified REGION SIZE in the OMEGAMONCollector JCL and verify that enough virtual storage isavailable for the OMEGAMON Collector. Then restartthe OMEGAMON Collector. If the problem persists,contact IBM support.

FPEV0174E SPECIFIED DB2 SUBSYSTEM <V1>IS UNKNOWN

ExplanationThe list of DB2 subsystems to be monitored in theOMEGAMON Collector startup configuration(parameter DB2SSID) contains an unknown DB2subsystem ID.

• <V1> is the unknown DB2 subsystem ID.

User responseUse the Configuration Tool (formerly ICAT) and correctthe list of DB2 subsystems to be monitored, thenrestart the OMEGAMON Collector.

FPEV0175E SYSTEM CONSOLE ATTACH FAILED(QEDIT INSTRUCTION)

ExplanationDuring startup of the OMEGAMON Collector, the servercould not attach to the z/OS system log.

User responseThis might be a temporary problem. Restart the server.If the problem persists, contact IBM support.

FPEV0176E <V1> ISPF OLM RESOURCEMANAGER COULD NOT BE LOADED


ExplanationDuring startup of the OMEGAMON Collector, a modulerequired for controlling access of the ISPF OnlineMonitor to the server could not be loaded.


User responseThis might be a temporary problem. Restart the server.If the problem persists, contact IBM support.

FPEV0177E <V1> ISPF OLM RESOURCEMANAGER COULD NOT BEUNLOADED

ExplanationDuring shutdown of the OMEGAMON Collector, amodule required for controlling access of the ISPFOnline Monitor to the server could not be unloaded.


User responseThis might be a temporary problem. If the problemrecurs at the next server shutdown, contact IBMsupport.

FPEV0178E <V1> AUTHORIZATION EXITDEACTIVATED DUE TO ERROR(CODE <V2>)

ExplanationDuring startup of the OMEGAMON Collector, the DB2user authorization exit (DSN3@ATH) was tested andreturned an error. The usage of the authorization exit inOMEGAMON XE for DB2 PE is deactivated.

• <V1> is the DB2 subsystem ID.• <V2> is the return code from the DB2 authorization

exit.

User responseVerify that the user authorization exit is available tothe OMEGAMON Collector (part of the STEPLIB searchorder of the OMEGAMON Collector JCL) and worksproperly. Then restart the server.

FPEV0179E <V1> DATA SERVER IS NOTALLOWED TO ACCESS DATASET<V2>

ExplanationThe OMEGAMON Collector is not allowed to access theindicated data set. The data set is either the SnapshotHistory archive or the Exception Log data set.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the data set.

User responseGrant RACF ALTER privileges to the started task userID or group ID of the OMEGAMON Collector. Thenrestart the server.

FPEV0180E <V1> DATA SERVER IS NOTALLOWED TO CREATE DATASET,SEE JOB LOG FOR DETAILS

ExplanationThe OMEGAMON Collector is not allowed to create adata set. The data set is either the Snapshot Historyarchive or the exception event log data set.


User responseCheck the SYSPRINT output of the OMEGAMONCollector for details about the data set and theproblem. Grant RACF ALTER privileges to the startedtask user ID or group ID of the OMEGAMON Collectorand restart the server. Note that, for a nonexistent dataset, the privileges must be granted with wildcards.

FPEV0181E <V1> FOUND HISTORY DATA SET<V2> IS NO LINEAR DATA SET(LDS)

ExplanationDuring startup of the OMEGAMON Collector, theexisting Snapshot History data set was found as a non-LDS.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the Snapshot History data set.

User responseDelete or rename the existing data set and restart theOMEGAMON Collector, or, if the data set cannot bedeleted or renamed, choose a different high-levelqualifier in the Configuration Tool (formerly ICAT) fortemporary server data sets.

FPEV0182E <V1> ERROR IN ACCESSINGHISTORY DATA SET <V2> (RC/RS'<V3>'X/'<V4>'X)


ExplanationAccess to the Snapshot History data set failed.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the Snapshot History data set.• <V3> is the hexadecimal return code.• <V4> is the hexadecimal reason code.

User responseContact the system operator and check the return andreason codes. The return and reason codes are eitherreturned by Data-in-Virtual (DIV) operations or bySMS. See the appropriate documentation fordescription of these codes. If the problem is not asystem problem, contact IBM support.

FPEV0183E <V1> FOUND EVENT DATA SET<V2> IS NO LINEAR DATA SET(LDS)

ExplanationDuring startup of the OMEGAMON Collector, theexisting exception event data set was found as a non-LDS.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the exception event data set.

User responseDelete or rename the existing data set and restart theOMEGAMON Collector, or, if the data set cannot bedeleted or renamed, choose a different high-levelqualifier in the Configuration Tool (formerly ICAT) fortemporary server data sets.

FPEV0184E <V1> ERROR IN ACCESSINGEVENT DATA SET <V2> (RC/RS'<V3>'X/'<V4>'X)

ExplanationAccess to the exception event data set failed.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the exception event data sett.• <V3> is the hexadecimal return code.• <V4> is the hexadecimal reason code.

User responseContact the system operator and check the return andreason codes. The return and reason codes are eitherreturned by Data-in-Virtual (DIV) operations or bySMS. See the appropriate documentation for

description of these codes. If the problem is not asystem problem, contact IBM support.

FPEV0185I <V1> LIST OF MONITORED DB2SUBSYSTEMS

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup.

• OMEGAMON Collector• <V1> is the name of the master controller inside the

OMEGAMON Collector (MSTR).

User responseNone.

FPEV0187I <V1> - <Name> <Status> <Detect><Level> <Location> <Type> <Dsg><Lpar>

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup. Itindicates that the indicated DB2 subsystem was auto-detected at the LPAR and is monitored with limitedfunctionality.


• <Name> is the DB2 subsystem ID.• <Status> is the monitoring status of the DB2

subsystem, which can be one of the following:DENIED

The OMEGAMON Collector started task user IDdoes not have the required privileges to connect(IDENTIFY) to this DB2 subsystem.

DOWNThe DB2 subsystem is not running.

EXCLUDEDThe DB2 subsystem is excluded from monitoring.This happens in the following cases:

– The indicated DB2 subsystem was marked inthe Configuration Tool as not to be monitored.

– Monitoring of the indicated DB2 subsystemwas stopped by an operator command.

– The monitoring subtask stopped because of aproblem.

For other possible reasons check the SYSPRINTfor messages that explain why the DB2subsystem is not monitored.


IGNOREDThe version of this DB2 subsystem is notsupported. Therefore, this DB2 subsystemcannot be monitored.

INITIALThe DB2 subsystem is known to the OMEGAMONCollector, but there is neither a connectionestablished nor a monitoring subtask started yet.

MONITOREDThe DB2 subsystem is monitored.

MONDSGThe indicated DB2 subsystem is monitoredimplicitly. The DB2 subsystem is a local memberof a data sharing group that is excluded frommonitoring (configuration) or it is not configuredwhile AUTODETECT is disabled. The DB2subsystem is monitored implicitly by anotherlocal data sharing group member withoutstarting any additional subtasks for monitoringthis DB2 subsystem.

RESTRICTThe DB2 subsystem is known to the OMEGAMONCollector, but the OMEGAMON Collector is notauthorized to connect to the DB2 subsystembecause the DB2 subsystem is started inrestricted access mode (maintenance).

UNKNOWNThe status of the DB2 subsystem cannot bedetermined for one of the following reasons:

– The DB2 subsystem is a remote member of adata sharing group and no local member of thedata sharing group is currently monitored.Therefore, no information about the DB2subsystem can be obtained.

– The DB2 subsystem is a local member of adata sharing group that is excluded frommonitoring (configuration) or it is notconfigured while AUTODETECT is disabled.This DB2 subsystem can be monitoredimplicitly by another local data sharing groupmember without starting additional subtasksfor monitoring this DB2 subsystem. If explicitmonitoring of all local data sharing groupmembers is stopped, no implicit monitoring ispossible, and therefore, no information can beobtained for local and remote members of thedata sharing group.

UPThe DB2 subsystem is running, but the subtaskthat monitors this DB2 subsystem is not yetstarted.

• <Detect> indicates whether the DB2 subsystem wasfound by means of auto-detection.

YThis DB2 subsystem was auto-detected.

NThis DB2 subsystem was configured explicitly oris a remote or implicitly monitored data sharinggroup member.

• <Level> indicates the DB2 version, release, andmodification level as a six-digit character string.

• <Location> indicates where the DB2 subsystem isrunning.LOCAL

The DB2 subsystem runs in the same LPAR asthe OMEGAMON Collector.

REMOTEThe DB2 subsystem is a data sharing groupmember that does not run on the same LPAR asthe OMEGAMON Collector.

• <Type> indicates the type of the DB2 subsystem.SINGLE

The DB2 subsystem does not run in a datasharing group environment.

MEMBERThe DB2 subsystem is a member of a datasharing group.

• <Dsg> The name of the data sharing group to whichthis DB2 subsystem belongs.

• <Lpar> indicates the name of the z/OS system wherethe member is running or was last running beforemonitoring stopped.

User responseIf the status is DENIED, contact your securityadministrator and request authority for theOMEGAMON Collector to access this DB2 subsystem.

FPEV0188I <V1> <DB2_ID> <Status><Detected> <Lvl> <Location><Type> <Dsg> <Lpar>

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup. Itindicates that the specified DB2 subsystem wasspecified in the list of DB2 subsystems (parameterDB2SSID) to be monitored.


• <DB2_ID> is the DB2 subsystem ID.• <Status> is the monitoring status of the DB2

subsystem.


• <Detected> indicates whether the DB2 subsystemwas found by means of auto-detection.

• <Lvl> indicates the DB2 version, release, andmodification level as a three-digit character string.

• <Location> indicates where the DB2 subsystem isrunning.

• <Type> indicates whether the DB2 subsystem is amember of a data sharing group.

• <Dsg> is the name of the data sharing group to whichthis DB2 subsystem belongs.

• <Lpar> is the name of the z/OS system where themember is running.

See message FPEV0187I for details.

User responseNone.

FPEV0189W <V1> PARAMETER <V2> IS NOTALLOWED AS DB2 SUBSYSTEMSPECIFIC PARAMETER

ExplanationDuring startup of the OMEGAMON Collector, theindicated DB2 subsystem independent parameter wasfound in a DB2 specific startup member.

• <V1> is the DB2 subsystem ID.• <V2> is the startup parameter.

User responseThis can happen if the OMEGAMON Collector startupparameter members were changed manually. Use theConfiguration Tool (formerly ICAT) for changing serverconfiguration parameters. If the members have notbeen changed manually, or the problem occurs even ifthe Configuration Tool (formerly ICAT) is used, contactIBM support.

FPEV0190W <V1> PARAMETER <V2> IS NOTALLOWED AS DB2 SUBSYSTEMINDEPENDENT GLOBALPARAMETER

ExplanationDuring startup of the OMEGAMON Collector, theindicated DB2 subsystem dependent parameter wasfound in the DB2 independent startup memberOMPEMSTR.


• <V2> is the startup parameter.

User responseThis can happen if the OMEGAMON Collector startupparameter members were changed manually. Use theConfiguration Tool (formerly ICAT) for changing serverconfiguration parameters. If the members have notbeen changed manually, or the problem occurs even ifthe Configuration Tool (formerly ICAT) is used, contactIBM support.

FPEV0191W <V1> INSTANCE FOR DB2SUBSYSTEM <V2> NOT STARTEDDUE TO ERRORS IN PARAMETERDATA SET

ExplanationDuring startup of the OMEGAMON Collector, theparameter data set member for the indicated DB2subsystem contains errors. The DB2 subsystem is notbeing monitored.



User responseCheck SYSPRINT for wrong startup parameters.Correct them and restart the server.

FPEV0192S <V1> PARAMETER DATA SETMEMBER RKANPAR(OMPEMSTR)NOT FOUND

ExplanationThe startup parameter data set member for DB2subsystem independent configuration settings was notfound. Either the specified data set RKD2PAR does notcontain the member OMPEMSTR, or the OMEGAMONCollector JCL points to the wrong RKD2PAR data set.


User responseEnsure that the OMEGAMON Collector JCL points tothe right RKD2PAR data set. If the right data set isused and the problem persists, run the ConfigurationTool (formerly ICAT) to generate the configurationmember again.

FPEV0193W <V1> PARAMETER DATA SETCOULD NOT BE READ. SEE JOBLOG FOR DETAILS


ExplanationDuring startup of the OMEGAMON Collector, thestartup data set member RKD2PAR(OMPEMSTR) wasfound, but could not be read.


User responseCheck SYSPRINT of the OMEGAMON Collector startedtask and correct the error. Restart the OMEGAMONCollector.

FPEV0194S <V1> PARAMETER DATA SETDDNAME 'RKANPAR' NOTSPECIFIED IN JCL

ExplanationThe required DD statement "RKANPAR" for theconfiguration settings is not specified in theOMEGAMON Collector JCL.


User responseCorrect the OMEGAMON Collector JCL and restart theserver.

FPEV0195I <V1> EVENTOBSERVATION=<V2>

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup andindicates the state of DB2 event observation.

• <V1> is the DB2 subsystem ID.• <V1> is either YES or NO.

User responseNone.

FPEV0196I <V1> -EVENTDSEXTENTQUAL=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the threshold value that indicates when a

DB2 data set extend alert will be sent.

User responseNone.

FPEV0197I <V1> - DEBUG TRACE=<V2>



– OFF: The debug trace is inactive.– ON: The debug trace is active.

User responseNone.

FPEV0198I <V1> AUTODETECT=<V2>

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup. Ifauto-detection of DB2 subsystems by the OMEGAMONCollector PESERVER subtask is switched off, <V2> isNO, otherwise YES.

• <V1> is the DB2 subsystem ID.• <V2> is either YES or NO.

User responseNone.

FPEV0199I <V1> - DB2 SUBSYSTEM <V2>(<V3>) HAS UNSUPPORTEDVERSION

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup, ifthe detected DB2 subsystem has an unsupported DB2version and is therefore not monitored.


• <V2> is the name of the monitored DB2 subsystem.• <V3> is the version of the monitored DB2

subsystem.

User responseNone.


FPEV0200I <V1> - DB2 SUBSYSTEM <V2> ISNOT FOUND

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup. Theindicated DB2 subsystem is not found in the list of DB2subsystems (parameter DB2SSID).


• <V2> is the name of the DB2 subsystem that is notfound.

User responseNone.

FPEV0201I <V1> CURRENT PARAMETERS FORINSTANCE <V2>




User responseNone.

FPEV0202I <V1> - MEMORY TRACE=<V2>



– OFF: The memory trace is inactive.– ON: The memory trace is active.

User responseNone.

FPEV0203W <V1> NO DATA SERVER INSTANCECOULD BE OBTAINED TOMONITOR THE SPECIFIED DB2SUBSYSTEM <V2>. ALL <V3>AVAILABLE DATA SERVERINSTANCES ARE ALREADY IN USE.

ExplanationMore DB2 subsystems are requested to be monitoredthan supported by the Data Server. The indicated DB2subsystem will not be monitored.


• <V2> is the DB2 subsystem ID of the subsystem thatis not being monitored.

• <V3> is the number of maximum available DataServer instances.

User responseReduce the number of DB2 subsystems specified inthe master startup data set memberRKD2PAR(OMPEMSTR). Stop and restart the DataServer using the MODIFY command.

FPEV0204I <V1> AUTOEXCPTHNAME=<V2>

ExplanationThis message is issued in response to a DISPLAYcommand or during OMEGAMON Collector startup, ifauto-exception processing is specified.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the threshold definition data set

that is used for auto-exception processing.

User responseNone.

FPEV0205I <V1> - AUTOEXCPUSER=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the user ID for which auto-exception

processing is started.

User responseNone.

FPEV0206I <V1> - AUTOEXCPPERIOD=<V2>



• <V1> is the DB2 subsystem ID.• <V2> is the interval (in seconds) at which the server

is checking for threshold violations.

User responseNone.

FPEV0207I <V1> - AUTOEXCPEXIT=<V2>



– NO: Exception exit for auto-exception processingis disabled.

– YES: Exception exit for auto-exception processingis enabled.

User responseNone.

FPEV0208I <V1> - AUTOEXCPFILE=<V2>



– NO: Exception are not written to a file data set.– YES: Exceptions are written in raw DB2 format to

the specified file data set.

User responseNone.

FPEV0209I <V1> -AUTOEXCPFILENAME=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the name of the file data set to which

detected exceptions for auto-exception processingare written in raw DB2 format.

User responseNone.

FPEV0210I <V1> - AUTOEXCPFILEDISP=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the disposition of the file data set for auto-

exception processing (MOD or OLD).

User responseNone.

FPEV0211I <V1> - AUTOEXCPLOG=<V2>



– NO: Exception are not written to a LOG data set.– YES: Exceptions are written in log format to the

specified LOG data set.

User responseNone.

FPEV0212I <V1> - AUTOEXCPLOGNAME=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the name of the LOG data set to which

detected exceptions for auto-exception processingare written in log format.

User responseNone.

FPEV0213I <V1> - AUTOEXCPLOGDISP=<V2>



• <V1> is the DB2 subsystem ID.• <V2> is the disposition of the LOG data set for auto-

exception processing (MOD or OLD).

User responseNone.

FPEV0214W <V1> USER AUTHORIZATIONCHECK FOR USER <V2> FAILED(RC <V3>, RS '<V4>'X). LOGONREJECTED.

ExplanationNecessary operations during verification of a userlogon from the PE Client failed.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID of the user that tried to log on.• <V3> is the return code of the failing operation.• <V4> is the reason code of the failing operation.

User responseThis might be a temporary problem. Retry theoperation. If problem persists, please contact IBMsupport.

FPEV0215W <V1> DATA SERVER MASTERALREADY STARTED.

ExplanationA command was issued to start a Data Server that isalready up and running. The command is ignored.



FPEV0217I <V1> BIND FOR MODULEFPEVWRP2 MISSING. NO DB2CONNECT DATA COLLECTING.

FPEV0218I <V1> NO AUTHORITY FOR REQ OPIN DGOVWRP2 FOR TABLEDB2PM.PARAMETER. NO DB2CONNECT DATA COLLECTING.

FPEV0219I <V1> NO AUTHORITY FOR REQ OPIN DGOVWRP2 FOR TABLEDB2PM.HISTORYDATA. NO DB2CONNECT DATA COLLECTING.

FPEV0220W <V1> COMMAND FAILED. THESPECIFIED DB2 SUBSYSTEM <V2>IS NOT RECOGNIZED BY THE DATASERVER.

ExplanationThe subtask command issued to the PerformanceExpert Server subtask (PESERVER) failed because thespecified identifier of the DB2 subsystem is notrecognized by the PE Server subtask.

<V1> is the name of the master controller inside theOMEGAMON Collector (MSTR).

<V2> is the DB2 subsystem identifier.

User responseVerify that the specified DB2 subsystem exists andthat the DB2 subsystem identifier is spelled correctlyin the command string. Correct and reissue thecommand.

FPEV0221W <V1> COMMAND FAILED. THEDATA SERVER INSTANCE FOR THESPECIFIED DB2 SUBSYSTEM <V2>IS NOT RUNNING.

ExplanationThe subtask command issued to the PE Server subtask(PESERVER) failed because the server instance for thespecified DB2 subsystem is not running.

Possible reasons that the server instance failedinclude the following:

• the PE Server subtask was not started because theData Server is not configured to start monitoring forthe specified DB2 subsystem.

• the PE Server subtask terminated because the DB2subsystem terminated.

• the PE Server subtask ended abnormally.

<V1>is the name of the master controller inside theOMEGAMON Collector (MSTR).

<V2> is the DB2 subsystem identifier.

User responseVerify that the PE Server subtask is configured tomonitor the specified DB2 subsystem and that the DB2subsystem is running. Restart the PE Server subtaskand reissue the command.


FPEV0222E <V1> RRSAF LOAD FAILED.RC=<V2> RS=<V3>

ExplanationLoading of the Resource Recovery ServicesAttachment Facility (RRSAF) modules failed.

• <V1> is the DB2 subsystem ID.• <V2> is the return code.• <V3> is the reason code.

User responseEnsure that the RRSAF modules are present andrunning or that they can be located in the normalsearch sequence.

FPEV0223E <V1> RRSAF-IDENTIFY REQUESTFAILED FOR DB2 SUBSYSTEM<V2>. RC= <V3> RS= <V4>

ExplanationThe PE server issued an RRSAF - 'IDENTIFY' request.This request failed because RRS/MVS was not active orthe DB2 subsystem was not attached to RRS/MVS.

• <V1> is the originator of the message.• <V2> is the DB2 subsystem ID.• <V3> is the DB2 return code.• <V4> is the DB2 reason code.

User response• If RRS/MVS is not started, start RRS/MVS and restart

the OMEGAMON Collector started task.• If RRS/MVS is started, restart the OMEGAMON

Collector started task or use the MODIFY commandto manually start the PE Server subtask for the DB2subsystem reported in this error message.

FPEV0224I <V1> INSTANCE FOR DB2SUBSYSTEM <V2> STOPPED

ExplanationThe OMEGAMON Collector components that monitorthe indicated DB2 subsystem have been stopped.

• <V1>is the name of the master controller inside theOMEGAMON Collector (MSTR).


User response:None.

FPEV0240I <V1> CURRENT PARAMETERS FORNON-VSAM WORK DATASETS



User response:None.

FPEV0241I <V1> CURRENT PARAMETERS FORVSAM WORK DATASETS



User response:None.

FPEV0242I <V1> - <V2>=<V3>



• <V2> is a parameter keyword.• <V3> is the parameter value.

User response:None.

FPEV0243I <V1> COMMAND IGNORED. THEPE SERVER SUBTASK FOR DB2SUBSYSTEM <V2> HAS ALREADYBEEN STARTED.

ExplanationA PE Server subtask has already been started and ismonitoring this DB2 subsystem, The subsequentcommand issued to start the PE Server subtask for thisDB2 subsystem again is ignored.



User response:None.

FPEV0250I <V1> EXCEPTION EVENT IFIERROR. IFI RC <V2>, REASON<V3>


ExplanationNone.



FPEV0252I <V1> EXCEPTION EVENT TRACESNOT STARTED

ExplanationNo traces have been requested using theEXCEPTIONEVENT command.


User responseNone.

FPEV0254W <V1> EXCEPTION EVENT DIV <V2>ERROR. RC <V3>-<V4>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the DIV service.• <V3> is the return code.• <V4> is the reason code.

User responseSee z/OS MVS Programming: Authorized AssemblerServices Reference for an explanation of the return andreason codes.

FPEV0255I <V1> EXCEPTION EVENTRECOVERY DATA SET WRAPPED

ExplanationThis message is issued whenever the Exception Eventbegins to write the data set from the beginning of thephysical data set.


User responseNone.

FPEV0256I <V1> EXCEPTION EVENTWAITING FOR DB2INITIALIZATION

ExplanationDB2 has not completed initialization.


User responseStart DB2 if it has not already been started.

FPEV0258I <V1> RRSAF ERROR WHENEXCEPTION EVENT ATTEMPTEDTO CONNECT TO DB2. RC <V2>,REASON <V3>

ExplanationNone.



FPEV0259I <V1> RRSAF ERROR WHENEXCEPTION EVENT ATTEMPTEDTO DISCONNECT FROM DB2. RC<V2>, REASON <V3>

ExplanationNone.



FPEV0261I <V1> AUTOMATIC EXCP STARTED

ExplanationNone.



User responseNone.

FPEV0262W <V1> AUTOMATIC EXCP STARTEDWITH ERRORS

ExplanationNone.


User responseSee the job log or SYSPRINT for accompanyingmessages and respective user actions.

FPEV0263E <V1> AUTOMATIC EXCP NOTSTARTED - NO VALID THRESHOLDRECORDS

ExplanationNone.


User responseSee the job log or SYSPRINT for accompanyingmessages and respective user actions.

FPEV0264E <V1> MISSING FILE DATA SETNAME FOR AUTOMATIC EXCP ONSERVER INSTANCE <V2>

ExplanationNone.


User responseSpecify a data set associated with theAUTOEXCPFILENAME parameter in the subsystemstartup data set member (RKD2PAR).

FPEV0266I <V1> EXCEPTION PROCESSINGDIAGNOSTIC DATA: <V2>

ExplanationOne of the following occurred:

• The monitored DB2 subsystem did not return IFCIDdata within a specified amount of time when periodicexception processing requested the data.

• The timed out DB2 is the PWH that did not insert thefound exceptions within the specified amount oftime.

• <V1> is the DB2 subsystem ID.• <V2> specifies whether the timeout happened on

the monitored DB2, or on the PWH.

User responseIf this message only appears once, then it can beignored. If it appears many times for one DB2subsystem, then contact your DB2 administrator.

FPEV0267I <V1> EXCEPTION PROCESSINGDIAGNOSTIC DATA: RAPRESERVED FOR LATER USE

ExplanationThe return area (RA) will be reused for the next DB2IFI request.


User responseNone.

FPEV0268E <V1> PERIODIC EXCEPTION LOGDATA SET <V2> HAS WRONGSETTINGS. SETTINGS FOUND:RECFM = <V3>, LRECL = <V4>

ExplanationThe Periodic Exception Log data set was allocatedincorrectly.

• <V1> is the DB2 subsystem ID.• <V2> is the data set name.• <V3> is the record format.• <V4> is the record length.

User responseReallocate the Periodic Exception Log data set usingthe correct attributes.RECFM

VBLRECL

≥512

FPEV0269E <V1> PERIODIC EXCEPTION FILEDATA SET <V2> HAS WRONGSETTINGS. SETTINGS FOUND:RECFM = <V3>, LRECL = <V4>


ExplanationThe Periodic Exception File data set was allocatedincorrectly.


User responseReallocate the Periodic Exception File data set usingthe correct attributes.RECFM

VBSLRECL

≥32756

FPEV0270E <V1> PERIODIC EXCEPTIONTHRESHOLD DATA SET <V2> HASWRONG SETTINGS. SETTINGSFOUND: RECFM = <V3>, LRECL =<V4>. PERIODIC EXCEPTIONPROCESSING NOT STARTED.

ExplanationThe Periodic Exception Threshold data set wasallocated incorrectly.


User responseReallocate the Periodic Exception File data set usingthe correct attributes.RECFM

VBLRECL

≥255

FPEV0271W <V1> THE FOLLOWING MODIFYCOMMAND IS NOT ALLOWED:<V2>

ExplanationThe private member configuration is not present forthe indicated DB2 subsystem. No Modify commandsare allowed. Only Display commands are allowed.

• <V1> is the DB2 subsystem ID.• <V2> is the Modify command that is not allowed.

User responseConfigure the DB2 subsystem with the ConfigurationTool (formerly ICAT).

FPEV0273I <V1> PARAMETER DATASETMEMBER <V2> NOT FOUND.MONITORING FOR DB2SUBSYSTEM <V3> IS ENABLEDWITH LIMITED FUNCTIONALITY

ExplanationDuring OMEGAMON Collector startup a DB2subsystem was automatically detected and a PEServer subtask was started to monitor the DB2subsystem. The corresponding parameter datasetmember could not be found. Monitoring for the DB2subsystem is enabled with limited functionality. Onlyrealtime monitoring without DB2 Connect monitoringis supported.


• <V2> is the name of the RKD2PAR parameterdataset member.


User responseNone, if real-time monitoring with limited functionalityis acceptable. Otherwise, configure the indicated DB2subsystem with the Configuration Tool (formerly ICAT),complete the configuration and restart theOMEGAMON Collector.

FPEV0274E <V1> PARAMETER DATASETMEMBER <V2> NOT FOUND.MONITORING FOR DB2SUBSYSTEM <V3> IS DISABLED

ExplanationDuring OMEGAMON Collector startup a PE Serversubtask was started to monitor a configured DB2subsystem, or a Modify command was issued toexplicitly start a PE Server subtask. The correspondingparameter dataset member could not be found for aconfigured DB2 subsystem. The configuration of theOMEGAMON Collector is not complete. Monitoring forthe DB2 subsystem is disabled.


• <V2> is the name of the RKD2PAR parameterdataset member.



User responseConfigure the indicated DB2 subsystem with theConfiguration Tool (formerly ICAT), complete theconfiguration and restart the OMEGAMON Collector.

FPEV0275E <V1> ERROR WHEN PREPARINGPE SERVER SUBTASK.MONITORING FOR DB2SUBSYSTEM <V2> IS DISABLED

ExplanationDuring OMEGAMON Collector startup the preparationfor the attach of a PE Server subtask failed. Monitoringfor the DB2 subsystem is disabled.



User responseCheck the job log for preceding error messages,correct the reported errors and restart theOMEGAMON Collector.

FPEV0303S <V1> DATA MANAGER DIV <V2>ERROR. RC <V3>-<V4>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the DIV service.• <V3> is the return code.• <V4> is the reason code.

User responseSee MVS Messages and Codes for an explanation of thereturn and reason codes. Check the log for precedingmessages or abend codes. If the problem cannot becorrected and recurs, contact IBM support.

FPEV0400I <V1> USER MANAGER TASKSTARTED

ExplanationNone.


User responseNone.

FPEV0401I <V1> USER MANAGER TASKENDED

ExplanationNone.


User responseNone.

FPEV0402E <V1> EXCEPTION EVENT TASKTERMINATED. RC <V2>

ExplanationNone.



FPEV0403E <V1> EXCEPTION EVENT TASKERROR. RC <V2>

ExplanationNone.



FPEV0404E <V1> EXCEPTION EVENT TASKDID NOT RESPOND TOTERMINATION REQUEST

ExplanationNone.


User responseNone.

FPEV0405E <V1> CONNECTION BY USER <V2>FAILED, NO AUTHORITIES FOUND


ExplanationThe user must have MONITOR1 or MONITOR2privileges to use the online monitor.

If external security (RACF) is used to secure DB2resources, the user or assigned group does not haveread access for the corresponding profiles. If DB2internal security is used to secure DB2 resources, nocorresponding entry for the user or assigned groupexists in SYSIBM.SYSUSERAUTH.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID.

System action:The PE Server subtask does not support monitoring forthe unauthorized user ID.

User responseGrant the required authority to the user or a group theuser is assigned to. Refer to Installation andConfiguration.

FPEV0406E <V1> CONNECTION BY USER <V2>FAILED DUE TO SQL ERROR <V3><V4>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID.• <V3> is either - or blank.• <V4> is the SQL error code.

User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the SQL code.

FPEV0408E <V1> PERIODIC EXCEPTION TASKFOR USER <V2> DID NOTRESPOND TO TERMINATIONREQUEST.

ExplanationThe user requested termination of periodic exception,but the task did not respond to the terminationrequest. The periodic exception task can be forced tobe terminated by stopping the Data Server subtask.


User responseStop and restart the Data Server subtask using theMODIFY command.

FPEV0409I <V1> PERIODIC EXCEPTIONPROCESSING TASK STARTED FORUSER <V2>.

ExplanationThe periodic exception task started for the user whorequested periodic exception processing.


User responseNone.

FPEV0410I <V1> PERIODIC EXCEPTIONPROCESSING TASK STOPPINGFOR USER <V2>.

ExplanationThe periodic exception task stopped for the user whorequested the termination of periodic exceptionprocessing.


User responseNone.

FPEV0411W <V1> PERIODIC EXCEPTION TASKDID NOT RESPOND TODEACTIVATION REQUEST.

ExplanationA periodic exception task continues monitoringthreshold exceptions although a user requested tostop periodic exception processing.


User responseRetry to deactivate periodic exception processing. Ifthe problem persists, terminate periodic exceptionprocessing.

FPEV0412I <V1> PERIODIC EXCEPTIONPROCESSING DEACTIVATED FORUSER <V2>.


ExplanationA periodic exception task discontinued to monitorthreshold exceptions for the user who requested tostop periodic exception processing.


User responseNone.

FPEV0413I <V1> PERIODIC EXCEPTIONPROCESSING ACTIVATED FORUSER <V2>

ExplanationA periodic exception task started to monitor thresholdexceptions for the user who requested to start periodicexception processing.


User responseNone.

FPEV0414I <V1> THRESHOLD DATA SET FORUSER <V2> CAUSED PARSEWARNINGS. WARNING: <V3>,COUNTER: '<V4>'X

ExplanationA periodic exception task was requested to monitor agiven set of thresholds and the specified threshold setcontains counters that are not supported by periodicexception processing.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID.• <V3> is the reason for the error.• <V4> is the identifier for the counter.

User responseCorrect the provided threshold set and retry.

FPEV0415I <V1> DUMP FOR THRESHOLD SETIS WRITTEN FOR FURTHERANALYSIS. DIAGNOSTICS: TABLEADDR <F2>, TABLE COUNT <F3>.

ExplanationThe periodic exception task detected an error in theprovided threshold set and starts to dump data for

further analysis. The message is preceded by messageFPEV0414I.

• <V1> is the DB2 subsystem ID.• <F2> is the user ID.• <F3> is the reason for the error.

User responseSave the Performance Expert log (SYSPRINT) anddump for further analysis by IBM. Correct the providedthreshold set and retry.

FPEV0416E <V1> EXCEPTION PROCESSINGUSER EXIT MODULE <V2> NOTFOUND. EXIT DISABLED

ExplanationThe indicated module was not found when theexception processing user exit was called.

• <V1> is the DB2 subsystem ID (DB2SSID).• <V2> is the name of the module.

User responseTry to retrieve and replace the indicated module from abackup version, or contact IBM support.

FPEV0417E <V1> SPECIFIED EXCEPTION LOGDATA SET '<V2>' COULD NOT BEACCESSED. SEE JOB LOG FORDETAILS

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the Exception Log data set.

User responseSpecify a data set that exists and is accessible.

FPEV0418E <V1> SPECIFIED EXCEPTION FILEDATA SET '<V2>' COULD NOT BEACCESSED. SEE JOB LOG FORDETAILS

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the Exception File data set.



FPEV0419E <V1> SPECIFIED EXCEPTIONTHRESHOLD DATA SET '<V2>'COULD NOT BE ACCESSED. SEEJOB LOG FOR DETAILS

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the exception threshold data

set.


FPEV0450I INITIALIZING COMMONSERVICES

ExplanationAn informational message.

FPEV0451I SUBSCRIBING COMMONSERVICES


FPEV0452I TERMINATING COMMONSERVICES


FPEV0453I UNSUBSCRIBING COMMONSERVICES


FPEV0454I COMMON SERVICES PARTIALLYTERMINATED


FPEV0455S COMMON SERVICESINITIALIZATION FAILED

ExplanationA fatal error has occurred.


FPEV0503W <V1> SIZE OF HISTORY DATA SETIS CHANGED TO <V2> BECAUSESPACE ALLOCATION REQUESTCOULD NOT BE FULLYACCOMPLISHED.

ExplanationDADSM EXTEND processing tried to allocate the nextextent for the history data set but this request couldnot be accomplished.

• <V1> is the DB2 subsystem ID.• <V2> is the new maximum number of 4 KB-pages of

the history data set. The new value is less than thevalue that is specified in the SHDATASETSIZE startupparameter for the Data Server.

Check the SYSLOG data set and locate theFPEV0503W message. It should be accompanied bythe system message IEC070I rc-ccc, ..., whererc is the reason code and ccc is the ProblemDetermination Function (PDF) code. These codes willhelp to identify the cause of the problem. Examples forrc-ccc are:

• 204-211 means the maximum number of extentshas been reached because of a lack of space orspace fragmentation problem

• 104-204 means no more volumes are available onwhich to allocate space.

User responseIt is recommended that you reallocate the history dataset to permit allocation of as many pages as arespecified in the SHDATASETSIZE startup parameter.You might have to perform space defragmentation oruse a separate storage class before the reallocation.To reallocate the history data set, perform thefollowing:

1. Stop the OMEGAMON Collector started task.2. Delete the VSAM cluster of the history data set by

using the DELETE command of the IDCAMS utility.3. Define the cluster by using the DEFINE CLUSTER

command of the IDCAMS utility. Use theparameters VOLUMES, STORAGECLASS ifenormous quantity of space is supposed to beallocated.


FPEV0504W <V1> HISTORY DATA SET IS NOTPRESENT

ExplanationNone.


User responseEither create a history data set or remove theSHDATASETSIZE parameter using the ConfigurationTool (formerly ICAT).

FPEV0505W <V1> HISTORY MANAGER NOTCOLLECTING DATA

ExplanationHistory Manager is not collecting data for the Db2subsystem (<V1>) shown in the message.

User responseCheck the log for preceding messages.

Note: If history data is not being collected for the Db2subsystem indicated in the message, you candisregard message FPEV0505W.

FPEV0507I <V1> HISTORY MANAGER TASKSTARTED

ExplanationThe snapshot history for the identified DB2 subsystemis successfully initialized.


User responseNone.

FPEV0508I <V1> HISTORY MANAGER TASKENDED

ExplanationNone.


User responseNone.

FPEV0509I <V1> INITIALIZING HISTORYINDEX FROM HISTORY DATA SET

ExplanationNone.


User responseNone.

FPEV0511I <V1> HISTORY DATA SETWRAPPED, <V2> INTERVALSSTORED

ExplanationThe history data exceeded the size of the history dataset. The history data set was therefore wrapped. Newhistory data will overwrite the earliest history datastored in the data set.

• <V1> is the DB2 subsystem ID.• <V2> is the number of intervals (logical snapshots)

stored when the history data set gets wrapped.

User responseNone.

FPEV0513W <V1> RETURN AREA LARGERTHAN DATA SET, SOME HISTORYDATA LOST

ExplanationThe amount of data returned from DB2 for a particularhistory interval was larger than the allocated size ofthe history data set, and was lost.


User responseIf the problem occurs frequently, use the ConfigurationTool (formerly ICAT) and set the SHDATASETSIZEstartup parameter to a larger value to allocate a largerhistory data set.

FPEV0515W <V1> HISTORY DATA SET SIZECHANGED TO <V2> PAGES

ExplanationThe history data set cannot be made smaller than thespace already used.

• <V1> is the DB2 subsystem ID.• <V2> is the new maximum size of the history data

set.


User responseNone.

FPEV0518S <V1> HISTORY MANAGER TASKTERMINATED

ExplanationNone.


User responseIf history manager restart fails, restart the Data Server.If the problem recurs, contact IBM support.

FPEV0519S <V1> ERROR OCCURRED DURINGHISTORY INDEX INITIALIZATION

ExplanationSome or all of the history data set has been corrupted.


User responseReallocate the history data set using the ConfigurationTool (formerly ICAT)-generated job, changing its size tocorrespond with the value specified in theSHDATASETSIZE startup parameter. If the problemrecurs, contact IBM support.

FPEV0520W <V1> HISTORY MANAGERWAITING FOR DB2 INTERFACEINITIALIZATION

ExplanationEither DB2 has not started or the Monitor trace is notactive.


User responseStart DB2 and the Monitor trace.

FPEV0521I <V1> HISTORY MANAGERCOLLECTING DATA

ExplanationNone.


User responseNone.

FPEV0522I <V1> HISTORY DATA SET SIZE ISTOO SMALL

ExplanationThe OMEGAMON Collector detected that the size ofthe history data set, specified in the SHDATASETSIZEstartup parameter, is too small to store even twological snapshots (intervals). The message continuesto be repeatedly issued, and an entry is written to theOMEGAMON Collector SYSPRINT log, each time afterone current interval is stored. When further storing isnot possible because of the size limitation, the HistoryManager task stops to avoid a corruption of the dataand indexes in the history data set.


User responseUse the Configuration Tool (formerly ICAT) andincrease the SHDATASETSIZE startup parameter valueto a reasonable size, based on the recommendationsgiven in Installation and Configuration and thestatistics provided by message FPEV0511I. Reallocatethe history data set, changing its size so that itcorresponds with the value specified inSHDATASETSIZE.

FPEV0523W <V1> INTERNAL BUFFEROVERFLOW OCCURRED DURINGPROCESSING OF DB2 CONNECTDATA. RC <V2>, REASON <V3>

ExplanationThe History Manager detected that one of its internalbuffers was too small to hold current DB2 Connectdata. As a result, part of the DB2 Connect data was notprocessed.

• <V1> is the DB2 subsystem ID.• <V2> is the return code.• <V3> is the reason code.

User responseIf this error occurs, it is recommended that youcontact IBM support. Proceed as follows:

1. Stop the OMEGAMON Collector.2. Collect the data outlined in “When you contact IBM

support” on page 8. Ensure that you save thehistory data, using the IDCAMS REPRO function. Ifyou need assistance with the IDCAMS REPROfunction, contact IBM support.

3. Restart the OMEGAMON Collector.


FPEV0552S <V1> HISTORY MANAGER DIV<V2> ERROR. RC <V3>-<V4>

ExplanationThere is a problem with the history data set.

• <V1> is the DB2 subsystem ID.• <V2> is the DIV function requested.• <V3> is the return code.• <V4> is the reason code.

User responseSee z/OS MVS Programming: Authorized AssemblerServices Reference for an explanation of the return andreason codes. Check the log for preceding messagesor abend codes. If the problem persists, contact IBMsupport.

FPEV0553W <V1> DB2 REPORTED IFI ERROR(RC <V2>, RS <V3>). CURRENTHISTORY SNAPSHOT DOES NOTCONTAIN ALL DATA FOR THIS DB2

ExplanationThe History Manager requested data from DB2 anddetected an IFI error. If data has been returned byDB2, it is saved to the History data set or History dataspace, but it does not contain all requested data.


User responseCheck the status of DB2 and correct the DB2 problem.See DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for anexplanation of the return and reason codes. If theproblem persists, contact IBM support.

FPEV0555W <V1> DB2 REPORTED INACTIVEMONITOR TRACE. CURRENTHISTORY SNAPSHOT NOT SAVED.ISSUE "START TRACE(MON)"COMMAND

ExplanationThe History Manager requested data from DB2 anddetected that Monitor trace is not active. An activeMonitor trace is necessary to receive performancedata for History. No data was saved to the History dataset or History data space.


User responseIssue the DB2 command START TRACE(MON)manually. If the problem persists, stop the traces onthe member and restart Monitor trace. If the problempersists, contact IBM support.

FPEV0559I <V1> HISTORY MANAGER RETURNAREA TOO SMALL. DATATRUNCATED

ExplanationThe Performance Expert DB2 IFI return area is notlarge enough to store all the returned DB2 data for ahistory manager IFI READS request. Some data gotlost. This can happen if you are requesting a datasharing group wide snapshot of the whole data sharinggroup for history saving.


User responseNone required. However, you can limit the amount ofdata requested from DB2 by using the ConfigurationTool (formerly ICAT) and specifying one or morehistory qualifiers (HQx) as Data Server startupparameters. For example, the specification ofHQ1=(PL=CICS*,PL=MANUFACT,PL=HR*) invokesmultiple IFI READS requests. However, depending onthe number of history qualifiers (HQx) and how youspecify them, a thread can match more than onequalification, multiple thread data can be collected,and problems can occur when past data is viewed.

FPEV0560E <V1> DB2 RETURNED INCORRECTDATA. REQUEST CANCELED

ExplanationIncorrect READS data was found, so the request toretrieve data was canceled.


User responseIf the error recurs, trace the problem using the DataServer trace (tracelevel=36) and contact IBM support.Keep the archived SVC dump titled INCORRECT RA -DB2I and all JES outputs of OMEGAMON CollectorStarted Task for further analysis by IBM support.

FPEV0561E <V1> DB2 MEMBER <V2> ISTEMPORARILY OUT OF MEMORY(RS <V3>). CURRENT HISTORY


SNAPSHOT DOES NOT CONTAINALL DATA FOR THIS MEMBER

ExplanationThe History Manager requested group scope data fromDB2 and detected that member <V2> is temporarilyout of memory (DB2 IFI code <V3>). The data is savedto the History data set or History data space, but itdoes not contain data for all group members.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 member in this group reporting the

problem.• <V3> is the DB2 IFI reason code.

User responseCheck the status of DB2 group member <V2> in thisgroup and correct the DB2 problem. See DB2Messages and Codes (or the corresponding manual ofthe DB2 version you have installed) for an explanationof the return and reason codes. If the problempersists, contact IBM support.

FPEV0562E <V1> DB2 IS TEMPORARILY OUTOF MEMORY (RS <V2>). CURRENTHISTORY SNAPSHOT DOES NOTCONTAIN ALL DATA FOR THIS DB2

ExplanationThe History Manager requested data from DB2 anddetected that this DB2 subsystem is temporarily out ofmemory. If data has been returned by DB2, it is savedto the History data set or History data space, but itdoes not contain all requested data.

• <V1> is the DB2 subsystem ID.• <V2> is the DB2 IFI reason code.

User responseCheck the status of DB2 subsystem and correct theDB2 problem. See DB2 Messages and Codes (or thecorresponding manual of the DB2 version you haveinstalled) for an explanation of the reason code. If theproblem persists, contact IBM support.

FPEV0563E <V1> DB2 MEMBER <V2>REPORTED AN INTERNAL ABEND(RS <V3>). CURRENT HISTORYSNAPSHOT DOES NOT CONTAINALL DATA FOR THIS MEMBER

ExplanationThe History Manager requested group scope data fromDB2 and detected an internal abend in member <V2>.

The data is saved to the History data set or Historydata space, but it does not contain data for all groupmembers.



User responseContact IBM support. See DB2 Messages and Codes (orthe corresponding manual of the DB2 version you haveinstalled) for an explanation of the reason code.

FPEV0564E <V1> DB2 REPORTED ANINTERNAL ABEND (RS <V2>).CURRENT HISTORY SNAPSHOTDOES NOT CONTAIN ALL DATAFOR THIS DB2

ExplanationThe History Manager requested data from DB2 anddetected an internal abend in DB2. If data has beenreturned by DB2, it is saved to the History data set orHistory data space, but it does not contain allrequested data.


User responseContact IBM support. See DB2 Messages and Codes (orthe corresponding manual of the DB2 version you haveinstalled) for an explanation of the reason code.

FPEV0565E <V1> DB2 MEMBER <V2>REPORTED AN UNEXPECTEDCONDITION (RS <V3>). CURRENTHISTORY SNAPSHOT DOES NOTCONTAIN ALL DATA FOR THISMEMBER

ExplanationThe History Manager requested group scope data fromDB2, and DB2 itself detected an unexpected conditionwithin DB2. The data is saved to the History data set orHistory data space, but it does not contain data for allgroup members.




User responseCheck the status of DB2 group member <V2> in thisgroup and correct the DB2 problem. See DB2Messages and Codes (or the corresponding manual ofthe DB2 version you have installed) for an explanationof the reason code. If the problem persists, contactIBM support.

FPEV0566E <V1> DB2 REPORTED ANUNEXPECTED CONDITION (RS<V2>). CURRENT HISTORYSNAPSHOT DOES NOT CONTAINALL DATA FOR THIS DB2

ExplanationThe History Manager requested data from DB2, andDB2 itself detected an unexpected condition withinDB2. If data has been returned by DB2, it is saved tothe History data set or History data space, but it doesnot contain all requested data.


User responseCheck the status of the DB2 subsystem and correct theDB2 problem. Refer to DB2 Messages and Codes (orthe corresponding manual of the DB2 version you haveinstalled) for an explanation of the reason code. If theproblem persists, contact IBM support.

FPEV0567W <V1> DB2 MEMBER <V2>REPORTED IFI ERROR (RC <V3>,RS <V4>). CURRENT HISTORYSNAPSHOT DOES NOT CONTAINALL DATA FOR THIS MEMBER

ExplanationThe History Manager requested group scope data fromDB2 and detected an IFI return code. The data issaved to the History data set or History data space, butit does not contain data for all group members.


problem.• <V3> is the DB2 IFI return code.• <V4> is the DB2 IFI reason code.

User responseCheck the status of the DB2 group member <V2> inthis group and correct the DB2 problem. See DB2Messages and Codes (or the corresponding manual ofthe DB2 version you have installed) for an explanation

of the return and reason codes. If the problempersists, contact IBM support.

FPEV0568W <V1> DB2 MEMBER <V2>REPORTED INACTIVE MONITORTRACE. CURRENT HISTORYSNAPSHOT DOES NOT CONTAINDATA FOR THIS MEMBER. ISSUE"START TRACE(MON)" COMMAND

ExplanationThe History Manager requested group scope data fromDB2 and detected that Monitor trace is not active atgroup member <V2>. An active Monitor trace isnecessary to receive performance data for history. Nodata for this member was saved to the History data setor History data space.


problem.

User responseIssue the DB2 Command START TRACE(MON)manually on member <V2>. If the problem persistsstop the traces on the member and restart the Monitortrace. If the problem persists, contact IBM support.

FPEV0570I <V1> SIZE OF HISTORY DATA SETHAS BEEN CHANGED. OLD DATASET IS ARCHIVED. PLEASE WAIT

ExplanationThe server detected that the specified size for thehistory data set does not match the size of theallocated data set. The size might have been changedin the server parameters, using the Configuration Tool(formerly ICAT). The history data set is archived and anew data set with the new size allocated.


User responseNone.

FPEV0571I <V1> OLD HISTORY DATA SET<V2> SUCCESSFULLY ARCHIVED

ExplanationThe old history data set was successfully archived anda new one was created.

• <V1> is the DB2 subsystem ID.• <V2> is the name of the archived data set.


User responseIf you are asked by IBM support to keep the archiveddata set for further problem analysis, use the REPROcommand of the IDCAMS utility to save the data set.

FPEV0572E <V1> ARCHIVING OF OLDHISTORY DATASET FAILED. SEEJOB LOG FOR DETAILS

ExplanationThe old history data set could not be archived.


User responseRefer to SYSPRINT of the OMEGAMON Collectorstarted task for more details and try to solve theproblem. Restart the OMEGAMON Collector.

FPEV0573I <V1> INCONSISTENCY FOUND INSNAPSHOT HISTORY DATASET.REASON <V2>

ExplanationWhen an existing Snapshot History data set is loadedduring initialization of the snapshot history monitoringfunction, the snapshots are checked for consistencyand integrity. The check failed with reason code <V2>.Possible reason codes are:20

Maximum record length exceeded.24

Invalid product section offset.28

Product section not contained in record.32

Product section exceeds end of record.36

Invalid product section length.40

Invalid type.44

Invalid data.48

Unsupported Db2 release.

• <V1> is the Db2 subsystem ID.• <V2> is the reason code.

User responseIf this message persists, terse the archive data set,open a PMR, and contact IBM Software Support for

further assistance. Message FPEV0571I will providethe name of the archive data set.

FPEV0574I <V1> SNAPSHOT HISTORYDATASET CANNOT BE USED. IT ISARCHIVED. PLEASE WAIT.

ExplanationLoading of an existing Snapshot History data set failedduring initialization of the snapshot history manager.The data set cannot be used as current SnapshotHistory data set. The data set is being archived.


User responseIf the error recurs, trace the problem using the DataServer trace (tracelevel=128) and contact IBMsupport. Keep the archived Snapshot History data setfor further analysis by IBM support.

FPEV0600I <V1> CPU PARALLELISM DATACOLLECTION STARTED

Explanation• <V1> is the DB2 subsystem ID.

User responseNone.

FPEV0601I <V1> CPU PARALLELISM DATACOLLECTION STOPPED


User responseNone.

FPEV0608E <V1> CPU PARALLELISM DATACOLLECTION - NO STORAGEAVAILABLE

ExplanationThe storage size that is allocated to store monitoringdata of the child thread exceeded.

Default value: 20 MBMinimum value: 5 MBMaximum value 50 MB

New incoming monitoring data is discarded. Theprocessing of existing monitoring data continues.



User responseSpecify a value between 5 and 50 for the configurationparameter CPDATASIZE and restart the CPUparallelism data collection.

FPEV0610I <V1> USER AUTHORIZATIONTASK STARTED

ExplanationNone.


User responseNone.

FPEV0611I <V1> USER AUTHORIZATIONTASK ENDED

ExplanationNone.


User responseNone.

FPEV0612E <V1> USER AUTHORIZATIONTASK DID NOT RESPOND TOTERMINATION REQUEST

ExplanationWhen the Data Server was stopped, the userauthorization task did not end correctly.


User responseNone.

FPEV0613I <V1> USER AUTHORIZATION EXITINITIALIZATION PHASETERMINATED WITH RC <V2>

ExplanationThe user authorization exit was terminated during itsinitialization phase because it returned a nonzeroreturn code.


• <V2> is the return code passed by the authorizationexit.

User responseCheck the user authorization exit and restart the DataServer.

FPEV0614I <V1> UNRECOVERABLE ERROR INUSER AUTHORIZATION EXIT.STANDARD OMEGAMON XE DB2PE AUTHORIZATION IS USED.

ExplanationThe user authorization exit was terminated during itsdecide phase because it returned a return code otherthan 0 or 4. Standard Performance Expertauthorization is used for further requests.


User responseCheck the user authorization exit and restart the DataServer.

FPEV0629I <V1> CPU PARALLELISM DATACOLLECTION DID NOT START YET.THE COMMAND IS IGNORED.

ExplanationA MODIFY command is used to stop the CPUparallelism data collection, however, the CPUparallelism data collection already stopped.

<V1> is the DB2 subsystem ID.

System action:None.

User response:None.

FPEV0630I <V1> CPU PARALLELISM DATACOLLECTION IS ACTIVE. THECOMMAND IS IGNORED.

ExplanationA MODIFY command is used to start the CPUparallelism data collection, however, the CPUparallelism data collection is already active.


System action:None.

User response:None.


FPEV0631I <V1> RESTART CPU PARALLELISMDATA COLLECTION FOR NEW DATASPACE SIZE TO TAKE EFFECT.

ExplanationA MODIFY command is used to change the size of thedata space that is used to store monitoring data ofchild threads.


System action:The size of the data space is not changed immediately.The next time the CPU parallelism data collection isstarted or restarted, the new size is used.

User response:Restart the CPU parallelism data collection.

FPEV0632E <V1> CPU PARALELLISM DATACOLLECTION ERROR. RC=<V2>,REASON=<V3>

ExplanationAn error occurred when collecting CPU parallelismdata.

• <V1> is the DB2 subsystem ID.• <V2> is the return code of the component where the

error occurred.• <V3> is the reason code that is associated with the

error situation.

System action:None.

User response:If the error recurs, trace the problem by using the dataserver trace (tracelevel=1) and contact IBM support.

FPEV0633I <V1> CPMON = <V2>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the current setting of the CPMONconfiguration parameter.

System action:None.

User response:None.

FPEV0634I <V1> CPDATASIZE = <V2>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the current setting of the CPDATASIZEconfiguration parameter.

System action:None.

User response:None.

FPEV0701S GETMAIN FAILURE FOR <V1>. RC<V2>

ExplanationThere was insufficient storage available.

• <V1> is the area being obtained.• <V2> is the return code.

User responseIncrease the region size and restart the OMEGAMONCollector.

FPEV0818S <V1> INVALID REQUEST TYPE<V2> IN RQE RECEIVED.COMPONENT <V3>

ExplanationThe Data Server DB2 interface component hasreceived an invalid request.

• <V1> is the DB2 subsystem ID.• <V2> is the request type that was found not valid.• <V3> is an internal identifier that is used by IBM for

maintenance purposes.

User responseRestart the client. If the error recurs, contact IBMsupport.

FPEV0819S <V1> <V2> NO RH PASSED TOCOMPONENT <V3>

ExplanationThe Data Server DB2 interface component hasreceived a invalid request header.

• <V1> is the DB2 subsystem ID.• <V2> is the number of the session manager.• <V3> is an internal identifier that is used by IBM for

maintenance purposes.

User responseRestart the client. If the error recurs, contact IBMsupport.

FPEV0820I (<V1>) <V2> <V3> CONTROL FLOW<V4> <V5> <V6>


ExplanationThis is an internal trace message from the Data ServerAPPC host server.

• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> is the number of the session manager.• <V4> is the trace text.• <V5> is an internal variable of the Data Server.• <V6> is an internal variable of the Data Server.

User responseNone.

FPEV0821I <V1> <V2> BUFFER CONTENT<V3>-<V4>-<V5>-<V6>


• <V1> is the DB2 subsystem ID.• <V2> is the number of the session manager.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.• <V6> is an excerpt of main storage that was traced.

User responseNone.

FPEV0850I <V1> DATA SERVER MAIN TASKSTARTED

ExplanationNone.


User responseNone.

FPEV0851I <V1> DATA SERVER MAIN TASKENDED

ExplanationNone.


User responseNone.

FPEV0852S <V1> DATA SERVER MAIN TASKENDED DUE TO ERROR

ExplanationNone.





• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> shows the last four characters of the module

name.• <V4> is the trace text.• <V5> is an internal variable of the Data Server.• <V6> is an internal variable of the Data Server.

User responseNone.

FPEV0854I <V1> <V2>-<V3>-<V4>-<V5> |<V6>|

ExplanationThis is an internal trace message from the Data Server.

• <V1> is the DB2 subsystem ID.• <V2> is an excerpt of main storage that was traced.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.• <V6> is an excerpt of main storage that was traced.

User responseNone.


FPEV0881E <V1> KEYWORD <V2> WASSPECIFIED MORE THAN ONCE

ExplanationThe Data Server startup parameter <V2> was specifiedmore than once, but is allowed only once.

• <V1> is the DB2 subsystem ID.• <V2> is the startup parameter, that was specified

more than once.

User responseEnsure that keyword <V2> is specified only once in theData Server parmlib RKD2PAR.

FPEV1104S <V1> INTERNAL ERROR INAUTHORIZATION TASK. NUMBER<V2>, CODE <V3>

ExplanationAn internal error has occurred.

• <V1> is the DB2 subsystem ID.• <V2> is an internal error number that identifies the

error.• <V3> is an internal error code that identifies the

error.

User responseStop and restart the Data Server using the MODIFYcommand. If the problem recurs, contact IBM support.


ExplanationThis is an internal trace message from the authorizedaddress space.

• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> is the user ID.• <V4> is a variable trace text.• <V5> is an internal variable of the Data Server.• <V6> is an internal variable of the Data Server.

User responseNone.

FPEV1131I <V1> <V2>-<V3>-<V4>-<V5> |<V6>|

ExplanationThis is an internal trace message from the authorizedaddress space.

• <V1> is the DB2 subsystem ID.• <V2> is an excerpt of main storage that was traced.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.• <V6> is an excerpt of main storage that was traced.

User responseNone.

FPEV1132I <V1> USER AUTHORIZATIONMAIN TASK STARTED

ExplanationNone.


User responseNone.

FPEV1133I <V1> USER AUTHORIZATIONMAIN TASK ENDED

ExplanationNone.


User responseNone.

FPEV1134S <V1> USER AUTHORIZATIONMAIN TASK ENDED DUE TO ERROR

ExplanationNone.



FPEV1135I <V1> - AUTHORIZATION ADDRESSSPACE TRACE=<V2>




OFFThe authorized address space trace is inactive.

ONThe authorized address space trace is active.

User responseNone.

FPEV1139E <V1> AUTHORIZATION MAINTASK DID NOT RESPOND TOTERMINATION REQUEST

ExplanationWhen the Data Server was stopped, the authorizationmain task did not end correctly.


User responseNone.

FPEV1141I <V1> AUTHORIZATION ADDRESSSPACE INFORMATION - BEGIN



User responseNone.

FPEV1142I <V1> AUTHORIZATION ADDRESSSPACE INFORMATION - END



User responseNone.

FPEV1144I <V1> <V2> <V3>


• <V1> is the DB2 subsystem ID.• <V2> is the user ID of an active user.• <V3> is the group ID of an active user.

User responseNone.

FPEV1145I <V1> USER-ID GROUP-ID



User responseNone.


ExplanationThis is an internal trace message from the applicationservices.

• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> is the user ID.• <V4> is a variable trace text.• <V5> is an internal variable of the Data Server.• <V6> is an internal variable of the Data Server.

User responseNone.

FPEV1147I <V1> <V2>-<V3>-<V4>-<V5> |<V6>|

ExplanationThis is an internal trace message from the applicationservices.

• <V1> is the DB2 subsystem ID.• <V2> is an excerpt of main storage that was traced.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.


• <V6> is an excerpt of main storage that was traced.

User responseNone.

FPEV1148I <V1> - APPLICATION SERVICESTRACE=<V2>



OFFThe application services trace is inactive.

ONThe application services trace is active.

User responseNone.

FPEV1152I <V1> STORAGE MAP FOR USER'<V2>', GROUP '<V3>',

ExplanationThis is the first portion of a message, which isdisplayed in response to the DISPLAY=(STORAGEMAP)command. It is always followed by messageFPEV1153I, which represents the second portion.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID.• <V3> is the group ID.

User responseNone.

FPEV1155I <V1> - STORE-ID BUFFER1BUFFER2 TOTAL

ExplanationThis message is displayed in response to theDISPLAY=(STORAGEMAP) command. This message isthe table header for message FPEV1156I.


• The STORE-ID column denotes the snapshot storeID. Snapshot stores can be defined by Data Serverprocesses or by using C-API verbs for snapshotstores.

• The BUFFER1 column denotes the virtual storagesize of snapshot store BUFFER1.

• The BUFFER2 column denotes the virtual storagesize of snapshot store BUFFER2.

• The TOTAL column denotes the total virtual buffersize of snapshot store BUFFER1 and snapshot storeBUFFER2.

User responseNone.

FPEV1156I <V1> <V2> <V3> <V4> <V5>

ExplanationThis message is displayed in response to theDISPLAY=(STORAGEMAP) command. It follows thetable header description of message FPEV1155I.

• <V1> is the DB2 subsystem ID.• <V2> is the snapshot store ID.• <V3> is the virtual storage size of BUFFER1.• <V4> is the virtual storage size of BUFFER2.• <V5> is the total virtual storage size of BUFFER1 and

BUFFER2.

User responseNone.

FPEV1158I <V1> TOTAL FOR AUTHORIZEDADDRESS SPACE = <V2> BYTES

ExplanationThis message is displayed in response to theDISPLAY=(STORAGEMAP) command.

• <V1> is the DB2 subsystem ID.• <V2> is the total virtual storage size of the user data

and the snapshot stores for all users.

User responseNone.

FPEV1162S <V1> ENQUEUEING REQUEST TOINTERNAL THREAD FAILED.

ExplanationThe internal inter-process communication inside theOMEGAMON Collector failed.




FPEV1163I DBS2 USER CROSBBR DOES NOTHAVE REQUIRED MONITOR 1/2PRIVILEGE (RC 8, REASON15075364).

ExplanationAuthorization is missing for the indicated user ID:

User responseNone. For further information about return and reasoncodes, see DB2 Messages and Codes.

FPEV1200I <V1> APPLICATION SERVICESMAIN TASK STARTED

ExplanationNone.


User responseNone.

FPEV1201I <V1> APPLICATION SERVICESMAIN TASK ENDED

ExplanationNone.


User responseNone.

FPEV1202S <V1> APPLICATION SERVICESMAIN TASK ENDED DUE TO ERROR

ExplanationNone.



FPEV1203S <V1> APPLICATION SERVICESMAIN TASK ENDED DUE TO BINDERROR

ExplanationThe Data Server could not start because the bind jobOMBD <V1> did not run successfully.


User responseResubmit the bind job in memberRKD2SAM(OMBD<V1>), then restart the Data Server.For more information, refer to Installation andConfiguration.

FPEV1204S <V1> APPLICATION SERVICESMAIN TASK ENDED DUE TORESOURCE ERROR

ExplanationThe indicated DB2 subsystem is not or is incorrectlydefined in the Configuration Tool (formerly ICAT). AllDB2 subsystems that you want to monitor must bedefined in the Configuration Tool.


User response• Verify whether the indicated DB2 subsystem isdefined in startup data set memberRKD2PAR(OMPEMSTR).

• Check the PE Server subtask log for FPEV1339Imessages. Each DB2 subsystem should report aunique TCP/IP port number in the messages. Ifrequired, use the Configuration Tool to redefine theport numbers.

• Ensure that Grants and Binds in RKD2PAR are run forall DB2 subsystems. Ensure that the DB2PMdatabase has the appropriate authority.

FPEV1205S <V1> APPLICATION SERVICESMAIN TASK ENDED DUE TO DB2RETURN CODE <V2>

FPEV1206W <V1> APPLICATION SERVICES -WAITING FOR DB2INITIALIZATION

ExplanationNone.


User responseNone.

FPEV1210E <V1> APPLICATION SERVICES -RRSAF ERROR WHEN ATTEMPTED


TO CONNECT TO DB2. RC <V2>,REASON <V3>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the Resource Recovery Services Attachment

Facility (RRSAF) return code.• <V3> is the RRSAF reason code.

User responseNone.

FPEV1211I <V1> APPLICATION SERVICES -RRSAF ERROR WHEN ATTEMPTEDTO DISCONNECT FROM DB2. RC<V2>, REASON <V3>

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the Resource Recovery Services Attachment

Facility (RRSAF) return code.• <V3> is the RRSAF reason code.

User responseNone.

FPEV1300I <V1> - TCP/IP TRACE=<V2>



OFFThe TCP/IP trace is inactive.

ONThe TCP/IP trace is active.

User responseNone.

FPEV1301I <V1> TCP/IP=<V2>



YESTCP/IP is active.

NOTCP/IP is inactive.

User responseNone.

FPEV1304I <V1> - IP ADDRESS OF SERVERINSTANCE=<V2>.<V3>.<V4>.<V5>


• <V1> is the DB2 subsystem ID.• <V2> is the IP address of the host TCP/IP server asspecified in the startup parameter data set by theIPADDRESS keyword.

User responseNone.

FPEV1305E <V1> PORT NUMBER FOR TCP/IPSERVER NOT SPECIFIED VIA®'PORT='

ExplanationTCPIP=YES was specified in the startup parameterdata set, but a port number was not specified.


User responseSpecify a port number using the PORT keyword andrestart the Data Server.

FPEV1306E <V1> TCP/IP MAIN TASK DID NOTRESPOND TO TERMINATIONREQUEST

ExplanationWhen the Data Server was stopped, the TCP/IP servermain task did not end correctly.


User responseNone.


FPEV1307I <V1> TCP/IP MAIN SERVER TASKSTARTED

ExplanationNone.


User responseNone.

FPEV1308I <V1> TCP/IP MAIN SERVER TASKENDED

ExplanationNone.


User responseNone.

FPEV1309S <V1> TCP/IP MAIN SERVER TASKENDED DUE TO ERROR

ExplanationNone.



FPEV1311I <V1> - TCPNAME=<V2>


• <V1> is the DB2 subsystem ID.• <V2> is the TCP/IP address space name that wasspecified by means of the Configuration Tool(formerly ICAT).

User responseNone.

FPEV1312E <V1> <V2> TCP/IP FUNCTIONCALL <V3> FAILED. ERRNO=<V4>

ExplanationThe TCP/IP function call failed. See the z/OSCommunications Server IP Application ProgrammingInterface Guide for a detailed description of theERRNO.

• <V1> is the DB2 subsystem ID.• <V2> is the TCP/IP session manager ID.• <V3> is the TCP/IP function call as described in the

z/OS Communications Server IP ApplicationProgramming Interface Guide.

• <V4> is the error number of the TCP/IP function callin error.

User responseAnalyze ERRNO and take appropriate action.

FPEV1313I (<V1>) <V2> <V3> <V4> CONTROLFLOW <V5> <V6> <V7>

ExplanationThis is an internal trace message from the TCP/IPserver.

• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> is the TCP/IP session manager ID.• <V4> is the user ID.• <V5> is a variable trace text.• <V6> is an internal variable of the Data Server.• <V7> is an internal variable of the Data Server.

User responseNone.

FPEV1314I <V1> <V2> <V3>-<V4>-<V5>-<V6>|<V7>|

ExplanationThis is an internal trace message from the TCP/IPserver.

• <V1> is the DB2 subsystem ID.• <V2> is a TCP/IP session manager ID.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.• <V6> is an excerpt of main storage that was traced.• <V7> is an excerpt of main storage that was traced.


User responseNone.

FPEV1315I <V1> NUMBER OF PARALLELSESSIONS EXCEEDS SPECIFIEDMAXIMUM

ExplanationA CONNECT request was rejected because themaximum number of TCP/IP connections wasexceeded.


User responseTry again later, or increase the size of theMAXSESSION parameter using the Configuration Tool(formerly ICAT), and restart the Data Server. See theInstallation and Configuration

FPEV1316I <V1> TCP/IP SESSION MANAGERTASK DID NOT RESPOND TOTERMINATION REQUEST

ExplanationWhen the Data Server was stopped, the sessionmanager task did not end correctly.


User responseNone.

FPEV1317I <V1> TCP/IP SESSION MANAGERTASK <V2> STARTED

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the number of the TCP/IP session manager.

User responseNone.

FPEV1318I <V1> TCP/IP SESSION MANAGERTASK <V2> ENDED

ExplanationNone.


User responseNone.

FPEV1319S <V1> TCP/IP SESSION MANAGERTASK ENDED DUE TO ERROR

ExplanationNone.



FPEV1320S <V1> <V2> TCP/IP SESSIONMANAGER RECEIVED INVALIDREQUEST FROM IP ADDRESS <V3>PORT <V4>

ExplanationAn invalid request was received by the Data ServerTCP/IP session manager. The session is deallocated.

• <V1> is the DB2 subsystem ID.• <V2> is the number of the TCP/IP session manager.• <V3> is the IP address of the originator sending the

invalid request.• <V4> is the port number of the originator sending

the invalid request.

User responseIf the IP address originates from a PE client, restartthe client. If the IP address does not originate from aPE client, identify the application in the network whichis erroneously trying to connect to the Data Server portand correct the configuration of this application. If theerror recurs, trace the problem using the TCP/IP tracefunction and contact IBM support.

FPEV1321S <V1> <V2> TCP/IP PROTOCOLVIOLATION. CHANNEL ALREADYIN USE

ExplanationA duplicate request was received by the Data ServerTCP/IP host server. The request is rejected.



User responseRestart the client. If the error recurs, trace theproblem using the TCP/IP trace and contact IBMsupport.

FPEV1322S <V1> <V2> INVALID CHANNEL<V3> RECEIVED

ExplanationA not valid channel number was passed to the TCP/IPserver. The request is rejected.

• <V1> is the DB2 subsystem ID.• <V2> is the number of the TCP/IP session manager.• <V3> is the invalid channel number.

User responseRestart the client. If the error recurs, trace theproblem using the TCP/IP trace and contact IBMsupport.

FPEV1329I <V1> TCP/IP NOT STARTED.SERVER INSTANCE ATTEMPTS TOESTABLISH A TCP/IPCONNECTION EVERY MINUTE

ExplanationThe Data Server TCP/IP server tries to connect to theTCP/IP interface once every minute until TCP/IP isstarted. This message is displayed each time anattempt to establish a TCP/IP connection has failed.


User responseStart TCP/IP.

FPEV1330I <V1> SERVER TCP/IP SERVER HASSUCCESSFULLY STARTED

ExplanationThis message is displayed when the Data ServerTCP/IP server was able to successfully establish aTCP/IP connection.


User responseNone.

FPEV1331E <V1> <V2> TCP/IP REPORTS THEUNSOLICITED EVENT <V3>.TCP/IP SESSION MANAGER WILLBE TERMINATED

ExplanationThe unsolicited event exit routine of the TCP/IP serverwas invoked by TCP/IP.

• <V1> is the DB2 subsystem ID.• <V2> is the TCP/IP session manager ID.• <V3> is the invocation reason code of the unsolicited

event exit routine.

Examples of reason codes:1

TCP/IP address space has terminated.2

TCP/IP has terminated the connection to the user.

User responseSee the z/OS Communications Server IP ApplicationProgramming Interface Guide for a detailed descriptionof the invocation reason codes, verify the invocationreason code, and take appropriate action.

FPEV1337W <V1>OMEGAMON XE DB2 PETCP/IP TASK FAILED. PORT INUSE

ExplanationYou have specified a port number for a PerformanceExpert TCP/IP server that is already in use by adifferent program. See the startup parameter PORT forthe used TCP/IP port.


User responseSet the TCP/IP port number to a different value or stopthe program using this port. Then restart the DataServer using the MODIFY command.

FPEV1339I <V1> TCPIP PORT <V2>


• <V1> is the DB2 subsystem ID.• <V2> is the port number as specified in the startup

parameter data set by the PORT keyword.

User responseNone.

FPEV1339W PROTOCOL VIOLATION DETECTED.PLEASE INSTALL LATEST LEVELOF PE WORKSTATION CLIENT.


ExplanationCommunication between the Data Server andPerformance Expert Clients via TCP/IP is becomingincreasingly inefficient and is likely to discontinue.

User responseThe Performance Expert Client users must updatetheir Clients to the latest maintenance level.

FPEV1340W TCP/IP PROTOCOL VIOLATIONDETECTED.

ExplanationAn error occurred in the TCP/IP communication eitherbetween the OMEGAMON Collector and theOMEGAMON XE for DB2 PE Client or the OMEGAMONCollector and the Extended Insight feature. This errormight have occurred because another application isusing the TCP/IP port number that is used by theOMEGAMON Collector PE Server subtask.

User responseCheck whether the TCP/IP port is used by anotherapplication. Make sure that your PE Client is at least atlevel 1317. If the problem persists, contact IBMsupport.

FPEV1342I MSTR EXCLUDEDDB2SSID=(<V1>)

ExplanationThis message is displayed during the startup of the PEServer subtask controller (MSTR) and in response to aDISPLAY command.

<V1> is the list of comma separated DB2 subsystemIDs. A listed DB2 subsystem can be excluded frombeing monitored because of the following reasons:

• During the configuration step, it is specified that thesubsystem does not start monitoring.

• The PE Server subtask controller access to the DB2subsystem is denied.

• The configured DB2 subsystem does not exist.• A required parameter data set member for the DB2

subsystem does not exist.• An error occurred during the preparation or the

startup of the monitoring PE Server subtask.

User responseIf the DB2 subsystem is expected to be excluded frombeing monitored: none.

Otherwise, see the PE Server subtask logs SYSPRINTor JESMSGLG for related error messages, correct theerror, and restart the OMEGAMON Collector startedtask.

FPEV1456I (<V1>) <V2> <V3> CONTROL FLOW<V4> <V5> <V6> <V7>

ExplanationThis is an internal trace message from the CollectReport Data address space.

• <V1> is the time when this message was written.• <V2> is the DB2 subsystem ID.• <V3> is the user ID.• <V4> is a variable trace text.• <V5> is an internal variable of the Data Server.• <V6> is an internal variable of the Data Server.• <V7> is an internal variable of the Data Server.

User responseNone.

FPEV1457I <V1> <V2> <V3>-<V4>-<V5>-<V6>|<V7>|

ExplanationThis is an internal trace message from the CollectReport Data address space.

• <V1> is the DB2 subsystem ID.• <V2> is an excerpt of main storage that was traced.• <V3> is an excerpt of main storage that was traced.• <V4> is an excerpt of main storage that was traced.• <V5> is an excerpt of main storage that was traced.• <V6> is an excerpt of main storage that was traced.• <V7> is an excerpt of main storage that was traced.

User responseNone.

FPEV2006E INSTALLATION IS INCOMPLETE

ExplanationThe licence FMID is not correctly installed.



If Performance Expert, or DB2 PM, installed withouterrors, and you followed the recommended installationand customization procedures, and the problempersists, contact IBM support.

FPEV2100I <V1> <V2>ELAPSED PROCESSINGTIME <V3> SEC FOR DB2INTERFACE TASK EXCEEDSTHRESHOLD \varn<V4> SEC

ExplanationThe following list shows the current settings for theprocessing time threshold:

• <V1> is the DB2 subsystem ID.• <V2> is the current time stamp.• <V3> is the actual elapsed processing time.• <V4> is the threshold value for the elapsed

processing time.

User responseThe current time stamp and the actual elapsedprocessing time can be used to further analyze theslowdown.

FPEV2101I <V1> EPTT=<F2> (ELAPSEDPROCESSING TIME THRESHOLD)

ExplanationThis message is preceded by message FPEV2100I orFPEV2103I. An SVC dump is initiated for theOMEGAMON Collector and the DB2 address spaces ofthe DB2 subsystem that is currently handling a call tothe DB2 instrumentation facility interface issued bythe PE Server subtask.

• <V1> is the DB2 subsystem ID.• <V2> is the list of address space IDs.

The address space identifiers are listed in thesequence OMEGAMON Collector, DB2 MSTR, DB2IRLM, DB2 DBM1, and DB2 DIST.

User responseProvide the OMEGAMON Collector started task joboutput and dump to IBM for further analysis.

FPEV2102W DB2 IFI RESPONSE TIMEEXCEEDS MAX WAIT TIME BY nSEC

ExplanationReports timeout conditions when PESERVER subtaskprocessing of data retrieval requests issued by the

Classic Interface exceed internal timeout value nseconds.

User responseTry the request again. PESERVER or Db2Instrumentation Interface is experiencing delays. Ifthis message occurs repeatedly, contact IBM Support.

FPEV2104I <V1> EPTT=<F2> (ELAPSEDPROCESSING TIME THRESHOLD)

ExplanationThe following list shows the current settings for theprocessing time threshold:

• <V1> is the DB2 subsystem ID.• <F2> is the elapsed processing time threshold in

seconds.

FPEV2105I <V1> TONT=<F2> (TIMEOUTNOTIFY THRESHOLD)

ExplanationThe following list shows the current settings for thetimeout notification threshold:

• <V1> is the DB2 subsystem ID.• <F2> is the timeout notification threshold in

seconds.

FPEV2106I <V1> DB2 MONITOR PRIVILEGECHECK PASSED FOR USER <V2>

ExplanationIf a user interface connects to a PE Server subtask, thePE Server subtask checks whether the user has DB2MONITOR privilege. This check passed.


User response:None.

FPEV2107E <V1> DB2 MONITOR PRIVILEGECHECK FAILED FOR USER <V2>

ExplanationIf a user interface connects to a PE Server subtask, thePE Server subtask checks whether the user has DB2MONITOR privilege. This check failed.


User response:


Grant MONITOR1 or MONITOR2 privilege to the userID.

FPEV2108E <V1> DB2 MONITOR PRIVILEGECHECK USING RACF FAILED FORUSER <V2>



System action:The PE Server subtask does not support monitoring forthe unauthorized user ID.

User response:Grant the user ID or assigned group read access toprofile MONITOR1 or MONITOR2.

FPEV2109E <V1> DB2 MONITOR PRIVILEGECHECK USING RACF FAILED FORUSER <V2> (RACROUTE RC=<V3>,RACF RC=<V4> RS=<V5>)


The displayed return and reason codes in decimal areobtained from macro RACROUTE, which is called toprocess the privilege check.

• <V1> is the DB2 subsystem ID.• <V2> is the user ID.• <V3> is the RACROUTE return code.• <V4> is the RACF return code.• <V5> is the RACF reason code.

System action:The PE Server subtask does not support monitoring forthe specified user ID.

User response:For return and reason codes refer to z/OS SecurityServer RACF Macros and Interfaces.

FPEV2702I <V1> DB2 MESSAGES COLLECTORSTARTED.


User responseNone.

FPEV2703I <V1> DB2 MESSAGES COLLECTORSTOPPED.


User responseNone.

FPEV2704S <V1> READA COLLECTORSUPPORT TASK ENDED DUE TOERROR.


User responseCheck the log for preceding messages or abend codes.If the problem persists, contact IBM support.

FPEV2705E <V1> READA COLLECTORSUPPORT TASK DID NOTRESPOND TO TERMINATIONREQUEST

ExplanationWhen the PE Server subtask is stopped, it requests theREADA collector to terminate. However, the READAcollector does not respond to the termination request.


User responseNone.

FPEV2706S <V1> READA COLLECTORSUPPORT TASK RECEIVEDINVALID REQUEST TYPE <V2> INRQE

ExplanationThe request that is sent to the PE Server subtaskinterface component is incorrect.

• <V1> is the DB2 subsystem ID.• <V2> is the incorrect request type.


User responseIf the error recurs, trace the problem by using the DataServer trace (tracelevel=128) and contact IBMsupport.

FPEV2708I <V1> READA COLLECTORSUPPORT TASK - WAITING FORDB2 INITIALIZATION.

ExplanationThe initialization of DB2 is not yet completed.


User responseNone.

FPEV2709I <V1> READA COLLECTORSUPPORT TASK - DB2 COMMANDOUTPUT BEGINS.

ExplanationThe READA collector support task issues DB2commands to start, stop, or restart the necessary DB2traces. If DB2 returns information messages, they aredisplayed between the messages FPEV2709I andFPEV2710I.


User responseNone.

FPEV2710I <V1> READA COLLECTORSUPPORT TASK - DB2 COMMANDOUTPUT ENDS.

ExplanationThe READA collector support task issues DB2commands to start, stop, or restart the necessary DB2traces. If DB2 returns information messages, they aredisplayed between the messages FPEV2709I andFPEV2710I.


User responseNone.

FPEV2712I <V1> READA COLLECTORSUPPORT TASK - READACOMMAND OUTPUT BEGINS.

ExplanationThe READA collector support task issues READAcommands to retrieve performance data from DB2. IfDB2 returns information messages, they are displayedbetween the messages FPEV2712I and FPEV2713I.


User responseNone.

FPEV2713I <V1> READA COLLECTORSUPPORT TASK - READACOMMAND OUTPUT ENDS.

ExplanationThe READA collector support task issues READAcommands to retrieve performance data from DB2. IfDB2 returns information messages, they are displayedbetween the messages FPEV2712I and FPEV2713I.


User responseNone.

FPEV2714E <V1> READA COLLECTORSUPPORT TASK - IFI ERROR ONREADA CALL. RC <V2>, REASON<V3>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the IFI return code.• <V3> is the IFI reason code.

User responseFor an explanation of the return codes and the reasoncodes, see DB2 Messages and Codes or thecorresponding manual of the DB2 version that you areusing.

FPEV2715I <V1>READA COLLECTORSUPPORT TASK - DB2 TRACE LOST

ExplanationThe OP buffer that is assigned to the READA collectoris lost. The trace that is started by the READA collectormight be stopped manually by using an operatorcommand. The READA collector support task stopped.



User responseIf the READA collector support task is not stoppedintentionally, restart it by using MVS operatorcommands.

FPEV2716W <V1> DB2 MESSAGES COLLECTORIS NOT STARTED. THE COMMANDIGNORED

ExplanationA MODIFY command is used to stop the DB2messages collector, however, this collector is alreadystopped.


User responseNone.

FPEV2717W <V1> DB2 MESSAGES COLLECTORIS ACTIVE. THE COMMAND ISIGNORED.

ExplanationA MODIFY command is used to start the DB2messages collector, however, this collector is alreadyactive.


User responseNone.

FPEV2718E <V1> DB2 MESSAGES COLLECTORIS NOT SUPPORTED FOR THIS DB2VERSION.

ExplanationA MODIFY command is used to start or stop the DB2messages collector for a DB2 subsystem version thatis not supported. The DB2 messages collector issupported for DB2 Version 9 or later.


User responseNone.

FPEV2719E <V1> READA COLLECTORSUPPORT TASK - RRSAF ERRORWHEN ATTEMPTED TO CONNECTTO DB2. RC <V2>, REASON <V3>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the IFI return code.• <V3> is the IFI reason code.

User responseFor an explanation of the return codes and the reasoncodes, see DB2 Messages and Codes or thecorresponding manual of the DB2 version that you areusing.

FPEV2720I <V1> STORED PROCEDURECOLLECTOR STARTED.

Explanation<V1> is the DB2 subsystem ID.

User responseNone.

FPEV2721I <V1> STORED PROCEDURECOLLECTOR STOPPED.


User responseNone.

FPEV2722E <V1> STORED PROCEDURECOLLECTOR IS NOT SUPPORTEDFOR THIS DB2 VERSION.


A MODIFY command is used to start or to stop thestored procedure collector for a DB2 subsystemversion that is not supported. The stored procedurecollector is only supported for DB2 10 or later.

User responseNone.

FPEV2723W <V1> STORED PROCEDURECOLLECTOR NOT STARTED. THECOMMAND IS IGNORED.


ExplanationA MODIFY command is used to stop the storedprocedure collector, however, the stored procedurecollector is already stopped.


User responseNone.

FPEV2724W <V1> STORED PROCEDURECOLLECTOR IS ACTIVE. THECOMMAND IS IGNORED.

ExplanationA MODIFY command is used to start the storedprocedure collector, however, the stored procedurecollector is already active.


User responseNone.

FPEV2725E <V1> READA COLLECTORSUPPORT TASK - OP BUFFERRELATED ERROR. RC <V2>,REASON <V3>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the return code of the component where the

error occurs.• <V3> is the reason code that is associated with the

error situation.

User responseFor an explanation of return codes and reason codes,see DB2 Messages and Codes or the correspondingmanual of the DB2 version that you are using.

If the reported reason code is not a DB2 reason codeand if the error recurs, trace the problem by using theData Server trace (tracelevel=1) and contact IBMsupport.

FPEV2726I <V1> READA COLLECTORSUPPORT TASK STARTED.


User responseNone.

FPEV2727I <V1> READA COLLECTORSUPPORT TASK IS STOPPING.


User responseNone.

FPEV2728I <V1> READA COLLECTORSUPPORT TASK ENDED.


User responseNone.

FPEV2729I <V1> DB2 MESSAGES COLLECTORIS STOPPING.


User responseNone.

FPEV2730I <V1> STORED PROCEDURECOLLECTOR IS STOPPING.


User responseNone.

FPEV2731E <V1> DB2 MESSAGES COLLECTORERROR. RC <V2>, REASON <V3>

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the return code of the component where the


error situation.


User responseIf the error recurs, trace the problem by using the DataServer trace (tracelevel=1) and contact IBM support.

FPEV2732E <V1> STORED PROCEDURECOLLECTOR ERROR. RC <V2>,REASON <V3>

ExplanationAn error occurs in the stored procedure collector.

• <V1> is the DB2 subsystem ID.• <V2> is the return code of the component where the


error situation.

User responseIf the error recurs, trace the problem by using the DataServer trace (tracelevel=1) and contact IBM support.

FPEV2733I <V1> READA COLLECTORSUPPORT TASK NOT STARTED. OPBUFFER CHANGES TAKE EFFECTAT NEXT STARTUP.

ExplanationA MODIFY command is used to change thecharacteristics of the OP BUFFER that is used by theREADA collector support task, however, the READAcollector support task is not active.


User responseNone.

FPEV2734I <V1> READA COLLECTORSUPPORT TASK STORAGETHRESHOLD REACHED. STOREDPROCEDURE COLLECTOR DATA ISIGNORED.

ExplanationAn internal data structure that is used by the storedprocedure collector exceeds its maximum size. Themonitoring data of the stored procedure is discarded.The processing continues.


User responseModify the characteristics of the OP buffer that is usedby the READA collector support task to ensure thatREADA data is processed as soon as possible. Forexample, you might want to reduce the OP bufferthreshold by using a MODIFY command. If theproblem persists, contact IBM support.

FPEV2735I <V1> READA COLLECTORSUPPORT TASK STORAGETHRESHOLD REACHED.STATEMENT HIERARCHY ISINVALIDATED.

ExplanationAn internal data structure that is used by the storedprocedure collector exceeds its maximum size. Themonitoring data of the stored procedure is discarded.The processing continues.



FPEV2736I <V1> READA COLLECTORSUPPORT TASK STORAGETHRESHOLD REACHED. STOREDPROCEDURE COLLECTOR CACHEIS RECYCLED.

ExplanationAn internal data structure that is used by the storedprocedure collector has exceeded its expectedmaximum size. The stored procedure monitoring datais discarded and processing continues. This canhappen if stored procedure monitoring data is notrequested by IBM InfoSphere® Optim PerformanceManager for a long time.


User responseEnsure that IBM InfoSphere Optim PerformanceManager setup is correct, i.e. connection toOMEGAMON collector is established and storedprocedure metric data collector is started and returnsmonitoring data. If the problem persists, contact IBMsupport.

FPEV2737I <V1> DB2 MESSAGES COLLECTORTIMEOUT OCCURRED.


ExplanationA request from a user interface cannot be handled bythe Data Server instance because a timeout occurred.The request could not be completed in time.


User response:Resubmit the request. If the problem persists, contactIBM support.

FPEV3001E <V1> THE DATA SERVERINSTANCE RECEIVED AN INVALIDREQUEST.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the request was notprovided or the provided request is not valid.


User responseResubmit the request. If the problem persists, contactIBM support.

FPEV3002E <V1> NO DATA SERVER INSTANCEIS AVAILABLE TO HANDLE THEREQUEST.

ExplanationA request from a user interface cannot be handled bythe Data Server because the Data Server or the DataServer instance dedicated to the specified DB2subsystem has not been started.


User responseVerify that the DB2 subsystem is contained in the listof DB2 subsystems in the master startup data setmember RKD2PAR(OMPEMSTR). If it is not, then addthe DB2 subsystem to the list. Stop and restart theData Server using the MODIFY command. Verify thatthe Data Server is started before requests aresubmitted.

FPEV3003E <V1> THE DB2 SUBSYSTEM ISUNKNOWN TO THE DATA SERVER.

ExplanationA request from a user interface cannot be handled bythe Data Server because the specified DB2 subsystemis unknown to the Data Server.


User responseVerify that the DB2 subsystem is contained in the listof DB2 subsystems in the master startup data setmember RKD2PAR(OMPEMSTR). If it is not, then addthe DB2 subsystem to the list. Stop and restart theData Server using the MODIFY command. Verify thatthe Data Server is started before requests aresubmitted.

FPEV3004E <V1> THE DB2 SUBSYSTEM ORDEDICATED DATA SERVERINSTANCE IS NOT ACTIVE.

ExplanationA request from a user interface cannot be handled bythe Data Server because the specified DB2 subsystemor the dedicated Data Server instance is not active.


User responseVerify that the DB2 subsystem and Data Serverinstance is running.

FPEV3005E <V1> THE DATA SERVERINSTANCE INPUT QUEUE FORREQUESTS IS NOT AVAILABLE.

ExplanationA request from a user interface cannot be handled bythe Data Server because there is no input queueavailable to handle the request.


User responseStop and restart the Data Server using the MODIFYcommand. If the problem persists, contact IBMsupport.

FPEV3006E <V1> THE INTER-SERVERINTERFACE COULD NOT OBTAIN AFREE RESPONSE QUEUE FROMTHE RESPONSE QUEUE POOL OFTHE DATA SERVER INSTANCE.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because there is no freeresponse queue available to handle the request. Thissituation occurs if more parallel requests aresubmitted to a Data Server instance than supported.



User responseResubmit the request.

FPEV3007E <V1> THE INTER-SERVERINTERFACE CANNOT ACCESS THERESPONSE QUEUE.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the response queuecannot be accessed.



FPEV3008E <V1> THE INTER-SERVERINTERFACE CANNOT COPY THESUBMITTED REQUEST TO THEINTERNAL WORK AREA.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the provided requestcannot be copied to the internal work area. Either therequest is not valid or no storage could be obtained.



FPEV3009E <V1> THE INTER-SERVERINTERFACE CANNOT QUEUE THESUBMITTED REQUEST TO THEINPUT QUEUE OF THE DATASERVER INSTANCE.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the provided requestcannot be queued into the input queue of the DataServer instance.



FPEV3010E <V1> THE INTER-SERVERINTERFACE CANNOT RETURN THECOMPLETED REQUEST.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the completedrequest cannot be returned. Either the providedrequest or the internal work area became obsolete.



FPEV3011E <V1> AN INTER-SERVERINTERFACE TIMEOUT OCCURREDWHILE PROCESSING A REQUESTBECAUSE THE DATA SERVERINSTANCE BECAME INACTIVE.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because a timeout occurred.Either the inter server interface is not available or hasterminated unexpectedly.



FPEV3012E <V1> AN INTER-SERVERINTERFACE TIMEOUT OCCURREDWHILE PROCESSING A REQUESTDURING DATA SERVER INSTANCERESTART.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because a timeout occurred.The Data Server instance became unavailable becauseof a restart.



FPEV3013E <V1> A TIMEOUT OCCURREDWHILE PROCESSING A REQUEST.


ExplanationA request from a user interface cannot be handled bythe Data Server instance because a timeout occurred.The request could not be completed in time.



FPEV3014E <V1> THE RESPONSE FROM THEDATA SERVER INSTANCE DOESNOT MATCH THE REQUEST.

ExplanationA request from a user interface cannot be handled bythe Data Server instance because the response doesnot match the request.



FPEV3016W <V1> NO PATH TO THE PE SERVERINSTANCE FOUND BECAUSE NOACTIVE PE SERVER INSTANCE ISAVAILABLE.

ExplanationA user interface requests performance data for aspecified DB2 subsystem. The PE Server receives therequest and tries to route the request to a monitoringPE Server subtask. In a data sharing group a PE Serversubtask must be started for at least one member thatresides on the same LPAR as the OMEGAMONCollector (called local member) to be able to monitormembers of the data sharing group. The data retrievalrequest fails if no PE Server subtask is started for thespecified DB2 subsystem or a local member of thedata sharing group.


User responseConfigure the indicated DB2 subsystem or a localmember of the data sharing group with theConfiguration Tool (formerly ICAT), complete theconfiguration and restart the OMEGAMON Collector.When the indicated DB2 subsystem or local memberof the data sharing group has already been configuredor the DB2 subsystems shall be auto-detected, check

the OMEGAMON started task job log for precedingerror messages during PE Server subtask start up, PEServer subtask termination or the occurrence of anabend. Restart the PE Server subtask. If the problempersists, contact IBM support.

FPEV3200I <V1> PSEUDO IFCID GENERATORSTARTED

ExplanationThe Data Server instance has started a subtask namedPseudo IFCID Generator. The subtask compiles datastructures similar to IFCIDs provided by DB2. Thesedata structures are called pseudo IFCIDs because theydo not originate from DB2. The pseudo IFCIDs areperformance data which are derived from DB2 IFCIDdata or originate from other data sources. The pseudoIFCIDs are used internally to communicateperformance data among the Data Server components.


User responseNone.

FPEV3201I <V1> PSEUDO IFCID GENERATORENDED

ExplanationThe Pseudo IFCID Generator subtask of the DataServer instance has ended during normal terminationof the Data Server.


User responseNone.

FPEV3202S <V1> PSEUDO IFCID GENERATORENDED DUE TO ERROR

ExplanationAn abend occurred within the subtask.


User responseCheck the log for preceding messages or abends. If theproblem cannot be corrected and recurs, contact IBMsupport.

FPEV3203S <V1> PSEUDO IFCID GENERATORTASK DID NOT RESPOND TOTERMINATION REQUEST


ExplanationDuring normal termination of the Data Server the DataServer instance requests the subtask named PseudoIFCID Generator to end. The subtask does not reactwithin the given time and is immediately beingterminated by the Data Server instance.


User responseNone.

FPEV3204S <V1> PSEUDO IFCID GENERATORRECEIVED INVALID REQUESTTYPE <V2>

ExplanationThe subtask received an invalid request.

• <V1> is the DB2 subsystem ID.• <V2> is the invalid request type.

User responseIf the error recurs, trace the problem using the DataServer trace (tracelevel=1) and contact IBM support.

FPEV5001I <V1> PWH SERVER IS STARTING

ExplanationNone.


User responseNone.

FPEV5002I <V1> PWH SERVER IS STOPPING

ExplanationNone.


User responseNone.

FPEV5003I <V1> CHECKING DATABASE FORNECESSARY CHANGES. PLEASEWAIT

ExplanationPerformance Warehouse is checking if the databasemodel for database DB2PM is up to date. The Data

Server may, for example, be forced to update thedatabase if the database model was changed.


User responseNone.

FPEV5004S <V1> DATABASE UPDATE FAILED.SEE JOB LOG FOR DETAILS

ExplanationNone.


User responseCheck the SYSPRINT output of theData Server fordetailed information about the error. Then solve theproblem and restart the Performance Warehousefunction in the Data Server by means of the MODIFYcommand 'PERFORMANCEWAREHOUSE=YES'.

FPEV5005I <V1> DATABASE UPDATECOMPLETE

ExplanationNone.


User responseNone.

FPEV5009I <V1> <V2>

ExplanationThis message is used for trace purposes of thePerformance Warehouse function and only written tothe SYSPRINT output of the Data Server.

• <V1> is the DB2 subsystem ID.• <V2> is the trace information.

User responseNone.

FPEV5010S <V1> DB2 CONNECTION FAILED.SEE JOB LOG FOR DETAILS

ExplanationNone.



User responseCheck the SYSPRINT output of the Data Server fordetailed information about the error. Then solve theproblem and restart the Performance Warehousefunction in the Data Server by means of the MODIFYcommand 'PERFORMANCEWAREHOUSE=YES'.

FPEV5011I <V1> CREATION OF PLAN DB2PMWAS SUCCESSFUL

ExplanationNone.


User responseNone.

FPEV5012S <V1> CREATION OF PLAN DB2PMFAILED. SEE BIND JOB OUTPUT

ExplanationNone.


User responseCheck the SYSPRINT output of the Data Server fordetailed information about the error. Then solve theproblem and restart the Performance Warehousefunction in the Data Server by means of the MODIFYcommand 'PERFORMANCEWAREHOUSE=YES'.

FPEV5013I <V1> REQUIRED PLAN DB2PMNOT FOUND. CREATING IT

ExplanationThe Performance Warehouse function of the DataServer requires a DB2 PLAN DB2PM. This plan was notfound and is now created.


User responseNone.

FPEV5014W <V1> SERVER IS STOPPING. DB2V6 OR LATER IS REQUIRED.

ExplanationThe Performance Warehouse function in the DataServer was requested. DB2 version 6 or later isnecessary for this function.


User responseUse the Configuration Tool (formerly ICAT) and set theData Server startup parameterPERFORMANCEWAREHOUSE to NO.

FPEV5015I <V1> UPDATING DATABASE INFORCED MODE. PLEASE WAIT

ExplanationThe Performance Warehouse function in the DataServer was started in forced mode to check thedatabase model for consistency.


User responseNone.

FPEV5016I <V1> REQUIRED DBRM <V2> NOTBOUND. BINDING IT

ExplanationA DBRM module of the Performance Warehousefunction misses a DB2 BIND and is now being bound.

• <V1> is the DB2 subsystem ID.• <V2> is the database request module (DBRM).

User responseNone.

FPEV5017I <V1> BINDING DBRM <V2>

ExplanationThe Performance Warehouse function of the datacollector is started in forced mode. Therefore theDBRM is being bound.

• <V1> is the DB2 subsystem ID.• <V2> is the database request module (DBRM).

User responseNone.

FPEV5018S <V1> DB2 DISCONNECT FAILED.SEE FOR DETAILS

ExplanationNone.



User responseCheck the SYSPRINT output of the Data Server fordetailed information about the error.

FPEV5019E <V1> DATASET SERVICETERMINATED. LIBRARY SEARCHMAY HAVE FAILED.

ExplanationNone.


User responseCheck the system log for details about the abend. Tryto restart the MVS system catalog and restart the DataServer. If the problem persists, contact IBM support.

FPEV5020I <V1> PERFORMANCE EXPERTREQUIRES A NEW TABLE SPACE<V2>, PLEASE ENTER STORAGEGROUP TO USE, OR BLANK FORDEFAULT STORAGE GROUP.

ExplanationThis message is shown during the Data Server start, ifthe Performance Warehouse function is requested andrequires a new table space.

• <V1> is the DB2 subsystem ID.• <V2> is the new required table space.

User responseEnter the name of the storage group to use for the newtable space through operator reply. To do this, searchfor the corresponding 'write to operator' output andlocate the number of this output. Then enter a 'write tooperator' reply: '/r NO#,REPLY' where NO# is thelocated number and REPLY is the chosen storagegroup (enter a blank as REPLY if you want to use theassigned default storage group). For furtherinformation on how to set up the Data Server for thePerformance Warehouse, see Installation andConfiguration.

FPEV5021I <V1> PLEASE ENTER THE NAMEOF BUFFER POOL TO USE FORTABLE SPACE <V2>. ENTER BLANKFOR DEFAULT BUFFER POOL.

ExplanationThis message is shown during the Data Server start, ifthe Performance Warehouse function is requested andrequires a new table space.

• <V1> is the DB2 subsystem ID.• <V2> is the new required table space.

User responseEnter the name of the buffer pool to use for the newtable space through operator reply. To do this, searchfor the corresponding 'write to operator' output andlocate the number of this output. Then enter a 'write tooperator' reply: '/r NO#,REPLY' where NO# is thelocated number and REPLY is the chosen buffer pool(enter a blank as REPLY if you want to use the assigneddefault buffer pool). For further information on how toset up the Data Server for the PerformanceWarehouse, see Installation and Configuration.

FPEV5022S <V1> ENTERED STORAGEGROUP<V2> IS UNKNOWN

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the storage group requested in message

FPEV5020I.

User responseCreate a new storage group in DB2 or choose adifferent existing one. Then restart the PerformanceWarehouse function in the Data Server by means of theMODIFY command'PERFORMANCEWAREHOUSE=YES' and specify thechosen storage group name.

FPEV5023S <V1> ENTERED BUFFER POOL<V2> IS UNKNOWN

ExplanationNone.

• <V1> is the DB2 subsystem ID.• <V2> is the buffer pool requested in message

FPEV5021I.

User responseRestart the Performance Warehouse function in theData Server by means of the MODIFY command'PERFORMANCEWAREHOUSE=YES' and specify thecorrect buffer pool name.

FPEV5024S <V1> ENTERED STORAGE GROUP<V2> OR BUFFER POOL <V3> ISUNKNOWN


ExplanationNone.


FPEV5020I.• <V3> is the buffer pool requested in message

FPEV5021I.

User responseVerify the specified storage group and buffer poolname. Both names must be known to DB2 and theData Server userID/groupID must have usageprivileges of both DB2 objects. Then restart thePerformance Warehouse function in the Data Serverusing the MODIFY command'PERFORMANCEWAREHOUSE=YES'. You can thenenter the correct names again.

FPEV5025S <V1> SERVER IS NOT ALLOWEDTO USE STORAGEGROUP <V2> ORTO ACCESS DATABASE DB2PM

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the storage group requested in message

FPEV5020I.

User responseEnsure that the Data Server userID/groupID DB2PMhas USE privileges for the specified storage group andhas DBADM privileges on database DB2PM. Thenrestart the Performance Warehouse function in theData Server using the MODIFY command'PERFORMANCEWAREHOUSE=YES'.

FPEV5026S <V1> SERVER IS NOT ALLOWEDTO USE BUFFER POOL <V2> OR TOACCESS DATABASE DB2PM

Explanation• <V1> is the DB2 subsystem ID.• <V2> is the buffer pool requested in message

FPEV5021I.

User responseEnsure that the Data Server userID/groupID DB2PMhas USAGE privilege for the specified buffer pool andhas DBADM privilege on database DB2PM. Thenrestart the Performance Warehouse function in theData Server using the MODIFY command with'PERFORMANCEWAREHOUSE=YES'.

FPEV5027S <V1> SERVER IS NOT ALLOWEDTO USE STORAGE GROUP <V2>,BUFFER POOL <V3> OR TOACCESS DATABASE DB2PM

ExplanationNone.


FPEV5020I.• <V3> is the buffer pool requested in message

FPEV5021I.

User responseEnsure that the Data Server userID/groupID DB2PMhas USAGE privilege for the specified buffer pool andstorage group and has DBADM privilege on databaseDB2PM. Then restart the Performance Warehousefunction in the Data Server using the MODIFYcommand with 'PERFORMANCEWAREHOUSE=YES'.

FPEV5028I <V1> REQUIRED DATABASEDB2PM NOT FOUND. CREATING IT

ExplanationThe Performance Warehouse function of the DataServer requires a DB2 database DB2PM. This databasewas not found and is now created.


User responseNone.

FPEV5029I <V1> CREATION OF DATABASEDB2PM WAS SUCCESSFUL

ExplanationNone.


User responseNone.

FPEV5030S <V1> SERVER IS NOT ALLOWEDTO CREATE DATABASE DB2PM

ExplanationNone.



User responseYou can either grant CREATEDBA privileges to theuserID or group DB2PM, or create the DB2PMdatabase manually and grant DBADM privileges to theDB2PM userid or group. Then restart the PerformanceWarehouse function in the Data Server using theMODIFY 'PERFORMANCEWAREHOUSE=YES'command. For further information on how to set up theData Server for the Performance Warehouse, seeInstallation and Configuration.

FPEV5031S <V1> SERVER IS NOT STARTEDWITH USERID DB2PM OR IS NOTMEMBER OF GROUP DB2PM

ExplanationPerformance Warehouse functions started from theData Server must be started using the MVS task userID DB2PM, or a member of the DB2PM RACF group.


This message is written if a SET CURRENT SQLID ='DB2PM' fails with SQLCODE = -553, which is specifiedas: "auth-id SPECIFIED IS NOT ONE OF THE VALIDAUTHORIZATION IDS" and further explained as: "Theauthorization ID specified as the value of the'authorization-id' or host variable in the SQL SETCURRENT SQLID statement is neither the user'sprimary authorization ID nor one of the associatedsecondary authorization IDs."

User responseChange the MVS task user ID to DB2PM or to theDB2PM RACF group, then restart the Data Server. Forfurther information on how to set up the Data Serverfor the Performance Warehouse, see Installation andConfiguration.

One way to analyze this error is to run an Audit tracewhen authorization changes happen. The trace showsthe IFCIDs 55 (Set Current SQLID), 83 (End Of Identifyrequest), and 87 (End Of Signon request). TheseIFCIDs report the primary and secondary, respectivelythe old and the new SQLID. You can start the Audittrace data collection with AUDIT CLASS(7) or withUSER CLASS(30) IFCID(55,83,87). To collect the tracedata into your private sequential data set, you can usethe ISPF Collect Report Data function (option 3, thenoption 6a). After the Audit trace data was collected,you can run an AUDIT TRACE TYPE(ALL) batch reportor provide IBM with the sequential files containing thecollected Audit trace data. The data should show theresult from the inaction between DB2 and RACF,especially whether the DB2PM group name wasreturned to DB2 as one of the secondary authorizationIDs.

FPEV5032S <V1> SERVER MANAGER TASKTERMINATED

ExplanationNone.


User responseCheck the system log for details about the abend. Tryto restart the MVS system catalog and restart the DataServer. If the problem persists, contact IBM support.

FPEV5033W <V1> SERVER RUNNING OUT OFMEMORY, SEE JOB LOG FORDETAILS

ExplanationThe Data Server could not obtain sufficient memory tocontain data.


User responseThis could be a temporary problem. If the problempersists, increase the region size for the OMEGAMONCollector and restart the Data Server, or contact IBMsupport.

FPEV5034I <V1> PLEASE ENTER NOW THENAME OF THE 32 KB BUFFERPOOL TO USE FOR TABLE SPACE<V2>. ENTER BLANK FOR DEFAULTBUFFER POOL.


Performance Expert needs to associate a 32 KB bufferpool to a table space.

User responseEnter the name of a 32 KB buffer pool (BP32K, or aname in the range BP32K1-BP32K9) as a write tooperator (WTO) reply. To do this, locate the number ofthis WTO message in the system log. Then enter '/rxxx,buffer pool', where xxx is the WTO number and'buffer pool' is the name of the buffer pool. The DataServer requires USAGE privilege for this buffer pool.

FPEV5035E <V1> SPECIFIED BUFFER POOL<V2> IS NOT A VALID 32 KBBUFFER POOL NAME


Explanation• <V1> is the DB2 subsystem ID.• <V2> is the buffer pool name entered in response to

message FPEV5034I.

The entered name is not a valid 32 KB buffer pool.

User responseMessage FPEV5034I is shown again. Enter the correct32 KB buffer pool name. This must be BP32K, or aname in the range BP32K1-BP32K9.

FPEV5036I <V1> PWH SERVER WAITING FORDB2 INITIALIZATION

ExplanationDB2 subsystem is stopped. Performance Warehouse iswaiting for DB2 restart.


User responseNone.

FPEV5037E <V1> BUFFER POOL <V2> FORTABLESPACE <V3> IN RESPONSEFILE IS NO 32K BUFFER POOL

ExplanationDuring the creation of the Performance Warehouse forthe indicated subsystem a response data set wasfound and used. However, the buffer pool specified inthis response data set is not a 32 KB buffer pool.

• <V1> is the DB2 subsystem ID.• <V2> is the specified buffer pool that is not a 32 KB

buffer pool.• <V3> is the table space for which the buffer pool wasspecified.

User responseEdit the response data set and correct the specifiedbuffer pool. The response data set can be found in<HLQ>.<DB2SSID>.SRVRESP, where <HLQ> is thehigh-level qualifier specified in the Configuration Tool(formerly ICAT) for temporary data sets of theOMEGAMON Collector, and <DB2SSID> is the DB2subsystem ID indicated in <V1>.

FPEV5040E <V1> PWH FOUND ANINCOMPATIBLE DATABASE DB2PM

ExplanationDuring Performance Warehouse (PWH) startup anincompatible database DB2PM was detected.


User responseStop the OMEGAMON Collector, drop or migrate theexisting Performance Warehouse database asdescribed in the product documentation and restartthe OMEGAMON Collector.

FPEV504 HISTORY DATA SET OR HISTORYDATA SPACE MUST BE SPECIFIED

ExplanationBoth, history data set size and data space size werereset to 0 in the Data Server Parameters window.

User responseSpecify a size value for either history data set orhistory data space.

FPEV613 USER AUTHORIZATION EXITDENIED YOUR REQUEST

ExplanationYou tried to perform a Performance Expert function.The authorization specified for your user ID in the userauthorization exit rejected your access to this function.

User responseSee your database administrator to clarify if you canget the proper authorization to use this function.

FPEV614 USER AUTHORIZATION EXITRETURNS NO DATA

ExplanationAccording to the authorization specified for your userID in the user authorization exit, no data is to to bereturned to you.

User responseNone.

FPEV615 SEVERE ERROR OCCURRED INUSER AUTHORIZATION EXIT

ExplanationThe user authorization exit failed with a severe error.



FPEV6801E <V1> READING SERVERPARAMETER FAILED, SEE JOB LOGFOR DETAILS

ExplanationDuring the start of the Collect Report Data job theoutput data set could not be created.


User responseCheck SYSPRINT of the job for more details andcorrect the error. Restart the PWH process.

FPEV6802E <V1> INCORRECT SERVER CRDSTART PARAMETER

ExplanationDuring the start of the Collect Report Data job therequired job parameters were not found.


User responseCheck the JCL of the Performance Warehouse job.

FPEV6803E <V1> UPDATING SERVER CRDSTATUS FAILED, SEE JOB LOG FORDETAILS

ExplanationDuring the start of the Collect Report Data job theoutput data set could not be created.


User responseCheck SYSPRINT of the job for more details andcorrect the error. Restart the PWH process using thepreviously used GUI (XE, VTAM, PE Client,Performance Warehouse).

FPEV6804I <V1> <V2> IS STARTING

ExplanationA Collect Report Data job or an internal CRD subtask isstarting.


• <V1> is the name of the Performance Warehousefunction (Collect Report Data).

User responseNone.

FPEV6805I <V1> <V2> IS STOPPING

ExplanationA Collect Report Data job or an internal CRD subtask isstopping.


function (Collect Report Data).

User responseNone.

FPEV6806I <V1> <V2> IS RESTARTING DB2TRACE

ExplanationDuring the collection of DB2 trace data the startedtrace was lost. The trace is restarted. This mighthappen, for example, if the trace was stoppedmanually using a DB2 STOP TRACE command.



User responseIf the message is not caused by STOP TRACEcommands, and if the message shows up several timesduring the collection of DB2 trace data, contact IBMsupport.

FPEV6807I <V1> <V2> TRACES LOST

ExplanationDuring the collection of DB2 trace data the startedtrace was lost. The trace is restarted. This mighthappen, for example, if the trace was stoppedmanually using a DB2 STOP TRACE command.



User responseIf the message is not caused by STOP TRACEcommands, and if the message shows up several times


during the collection of DB2 trace data, contact IBMsupport.

FPEV6808E <V1> <V2> TRACES FAILED, SEEJOB LOG FOR DETAILS

ExplanationDuring the collection of DB2 trace data the necessaryDB2 operation failed.



User responseThis might be a temporary DB2 problem. CheckSYSPRINT of the job for more details. Restart the PWHprocess using the previously used GUI (XE, VTAM, PEClient, Performance Warehouse).

FPEV6809W <V1> <V2> RETRIEVINGASYNCHRONOUS DB2 DATAFAILED, SEE JOB LOG FORDETAILS

ExplanationDuring the collection of DB2 trace data the necessaryDB2 operation failed.



User responseThis might be a temporary DB2 problem. CheckSYSPRINT of the job for more details. Restart the PWHprocess using the previously used GUI (XE, VTAM, PEClient, Performance Warehouse).

FPEV6810W <V1> TASK <V2> DID NOTRESPOND TO TERMINATIONREQUEST

ExplanationDuring the termination of a Collect Report Data job asubtask did not respond to the termination request.

• <V1> is the DB2 subsystem ID.• <V1> is the name of the Collect Report Data subtask.

User responseThis might be a temporary system problem. If theproblem occurs at the end of each Collect Report Datajob, contact IBM support.

FPEV6811W <V1> SYSTEM EXCEPTIONCAUGHT, COLLECT REPORT DATATASK ENDING ABNORMALLY

ExplanationDuring the execution of a Collect Report Data job thejob received an MVS system exception.


User responseCheck the system log for details about the abend.

FPEV6812I <V1> COLLECTION STOPPED DUETO : <V2>

ExplanationThe collection of DB2 trace data was stopped.

• <V1> is the DB2 subsystem ID.• <V1> is the reason why the collection was stopped.

User responseCheck the indicated reason. Usually, the collectionstops according to specified stop conditions. Ifpreceding of following messages indicate an error,check SYSPRINT for additional details.

FPEV6813I <V1> SPECIFIED OP BUFFER SIZETO HIGH FOR THIS DB2, REDUCEDIT TO 1 MB

ExplanationThe configuration of the Collect Report Data step in thePerformance Warehouse contains a OP buffer size thatis not supported with this DB2 version. The OP buffersize is adjusted to 1 MB.


User responseNone.

FPEV6814I <V1> USER <V2> DOES NOT HAVEREQUIRED MONITOR1/2PRIVILEGE TO COLLECT REPORTDATA

ExplanationThe Collect Report Data did not start because the userdoes not have sufficient DB2 authority.



• <V2> is the user ID of the Performance Warehousejob.

User responseThe system administrator should grant the necessaryMONITOR1 or MONITOR2 privileges for the user ID orgroup ID of the Performance Warehouse job.

FPEV6823E COMMAND <V1> NOT FOUND INSYSIN. PARSING STOPPED

ExplanationAn invalid command was found.

• <V1> is the invalid command name.

User responseCorrect the command and retry.

FPEV6831W <V1> UNSUPPORTED COMMAND<V2> AT LINE <F3>, POSITION<F4> IGNORED

ExplanationThe OMEGAMON Collector startup configurationcontains an invalid parameter.

• <V1> is the DB2 subsystem ID.• <V2> is the command name.• <F3> is the line number.• <F4> is the position number.

User responseUse the Configuration Tool (formerly ICAT) and correctthe parameter.

FPEV6834W <V1> DB2 SUBSYSTEM (<V2>) -THIS DB2 VERSION IS NOTSUPPORTED

ExplanationThis message is issued when trying to collect data foran unsupported DB2 version.

• <V1> is the name of the monitored DB2 subsystem.• <V2> is the version of the monitored DB2

subsystem.

User responseNone.

FPEV701 SERVER <V1> NO LONGERAVAILABLE

ExplanationNone.


User responseRestart the Data Server if necessary and reconnect toit.

FPEV702 UNABLE TO CONNECT TO SERVER<V1>

ExplanationUnexpected error.


User responseCheck the log for any Data Server errors. Log on toTSO/E again. If the problem recurs, contact IBMsupport.

FPEV703 ANOTHER USER IS UPDATING THEPARAMETERS FOR SERVER <V1>

ExplanationNone.



FPEV704 <V1> IS NOT AUTHORIZED TOUPDATE THE PARAMETERS FORSERVER <V2>

ExplanationNone.

• <V1> is the user ID.• <V2> is the DB2 subsystem ID.

User responseUse the ADMINUSER command to add this user.

FPEV705 THE PARAMETERS FOR SERVER<V1> ARE CURRENTLYUNAVAILABLE





FPEV706 LOADING THE QUALIFICATIONSFOR SERVER <V1> FAILED




FPEV710 <V1> IS AN INVALID COMMAND

ExplanationYou are not allowed to issue this command here.

• <V1> is the invalid command you issued.

User responseDo not issue this command.

FPEV711 COLLECTION INTERVAL MUST BENUMERIC IN THE RANGE 1 TO86400 SECONDS

ExplanationNone.

User responseCorrect the field.

FPEV712 MAXIMUM SIZE OF HISTORY DATASET MUST BE NUMERIC IN THERANGE 0 TO 9999999 KILOBYTES

ExplanationNone.

User responseUse the Configuration Tool (formerly ICAT) and specifya larger size.

FPEV713 DATASPACE SIZE MUST BENUMERIC IN THE RANGE 0 TO2097148 KILOBYTES

ExplanationNone.

User responseCorrect the field.

FPEV714 NUMBER OF EXTENTS MUST BENUMERIC

ExplanationNone.

User responseEnter a positive integer.

FPEV801 ERROR SAVING PARAMETERS FORSERVER <V1>



User responseReconnect. If the problem recurs, contact IBMsupport.

FPEV911 ERROR PROCESSING GETMAIN.RC <V1>

ExplanationAn error occurred attempting to allocate virtualstorage.


User responseIncrease the region size and retry the OMEGAMONCollector administrator’s dialog.

FPEV921 TBCREATE FAILURE. RC <V1>





FPEV922 TBDISPL FAILURE. RC <V1>




FPEV923 TBADD FAILURE. RC <V1>




FPEV9997I <V1> <V2> <V3> <V4> <V5> <V6><V7> <V8> <V9>

ExplanationFor IBM support personnel only.

User responseNone.

FPEV9999I <V1>

ExplanationA Performance Expert internal error has occurred. Thismessage is meant for IBM support personnel.

• <V1> is a symptom record used by IBM supportpersonnel to diagnose the problem.

User responseSave the information provided in the message andcontact IBM support.

FPEW - System Parameters report set messagesFPEW0110U INSUFFICIENT STORAGE

AVAILABLE TO STORE SYSTEMPARAMETERS DATA

ExplanationThere was not sufficient storage available to continueprocessing the System Parameters report.


FPEW0120I IFCID 106 NOT SUPPORTED

ExplanationNone.

User responseNone.

FPEW0130U INSUFFICIENT STORAGEAVAILABLE TO EXTEND SYSTEMPARAMETERS DATA

ExplanationThere was not sufficient storage available to continueprocessing the System Parameters report.


FPEW1246S UNSUCCESSFUL ATTEMPTWRITING TO THE FILE DATA SETOF SYSTEM PARAMETERS

ExplanationAn error occurred while writing data to the systemparameters file data set.



FPEX - Audit report set messagesFPEX0600S EXCEPTIONAL CONDITION

OCCURRED DURING AUDITPROCESSING. MAIN STORAGEALLOCATION FAILED

ExplanationThere was not enough storage available to continueAudit processing.


FPEX0610S EXCEPTIONAL CONDITIONOCCURRED DURING AUDITPROCESSING. MAIN STORAGERELEASE FAILED



FPEX4252I <V1> <V2> RECORDS WRITTEN TODDNAME <V3>

ExplanationAn AUDIT FILE subcommand has completed itsfunction.

• <V1> is the number of records written.• <V2> is the file type (for example, AUTHFAIL).• <V3> is the ddname for the file.

User responseNone.

FPEY - Explain report set messagesFPEY0001W DB2 RELEASE <V1> IS NOT

SUPPORTED BY THIS PRODUCTVERSION. AN EXPLAIN REQUESTFOR <V2> HAS BEEN IGNORED

ExplanationThe DB2 subsystem is at a release level that is notsupported by this version of OMEGAMON XE for DB2PE.

• <V1> is the DB2 release.• <V2> is the subsystem ID.

FPEY0002W CALL ATTACH FUNCTION <V1>FAILED. RETURN CODE <V2>,REASON CODE <V3>

ExplanationA problem was encountered establishing the requiredconnection between OMEGAMON XE for DB2 PE andDB2.

• <V1> is the Call Attach Facility (CAF) function.• <V2> is the return code.• <V3> is the reason code.

User responseEnsure that the OMEGAMON XE for DB2 PE Explainplan name (DB2PMX32) exists. If the Explain plan wasbound with a name other than the default plan name,this must be specified in the GLOBAL PLANEXPLAINparameter of a OMEGAMON XE for DB2 PE batchExplain request job.

FPEY0003W DB2 CAF SUPPORT CANNOT BELOADED. DB2 LOAD LIBRARY MAYNOT BE SPECIFIED IN STEPLIB

ExplanationOMEGAMON XE for DB2 PE could notload the CallAttach Facility (CAF) support modules. The DB2 loadlibrary may be missing in the STEPLIB DD statement.

User responseDetermine why OMEGAMON XE for DB2 PE cannotload the required modules. Resubmit the job.

FPEY0100I ACCORDING TO THE DB2 CATALOGYOU DO NOT HAVE A PLAN_TABLE.A PLAN_TABLE WILL NOW BECREATED FOR AUTHORIZATION ID<V1>


ExplanationA PLAN_TABLE could not be found for the currentauthorization ID. A PLAN_TABLE is then createdproviding that proper authorization exists. Ifsuccessful, this message is followed by messageFPEY0102I.

• <V1> is the authorization ID.

User responseNone.

FPEY0102I EXPLAIN TABLE NAMED<V1>.PLAN_TABLE CREATED INTHE DEFAULT DATABASE

ExplanationAn Explain table was created for the currentauthorization ID in the default database.


User responseNone.

FPEY0104I COLUMN <V1> HAS BEEN ADDEDTO <V2>.PLAN_TABLE

ExplanationThe PLAN_TABLE for the current authorization ID hasbeen altered with columns compatible to the DB2release being run.

• <V1> is the column name.• <V2> is the authorization ID.

User responseNone.

FPEY0105I LAST COLUMN <V1> HAS BEENADDED TO <V2>.PLAN_TABLE


• <V1> is the column name• <V2> is the authorization ID

User responseNo action required.

FPEY0106I LAST COLUMN <V1> HAS BEENALTERED FOR <V2>.PLAN_TABLE


• <V1> is the column name• <V2> is the authorization ID

User responseNo action required.

FPEY0110I NO STATISTICS AVAILABLE -EXECUTE RUNSTATS

ExplanationNo DB2 catalog statistics are available for the currenttable space.

User responsePerform RUNSTATS against the table space before youuse OMEGAMON XE for DB2 PE Explain.

FPEY0120I INDEX INFORMATIONSUPPRESSED BY USER REQUEST

ExplanationThe user has specified INDEX=N for the EXPLAINPLAN, EXPLAIN QMFQUERY, or EXPLAIN QUERYNOrequest. No column information for the chosen indexwill be shown.

User responseNone.

FPEY0140I NOTE: <V1>.<V2> CONTAINS <V3>ACTIVE PAGES - CONSIDER AUSABLE INDEX

ExplanationThis message is produced if DB2 has chosen a tablespace scan for a table located in a table space largerthan 10 active pages.

• <V1> is the database name.• <V2> is the table space name.• <V3> is the number of active pages.


User responseIf the access path should be index-based, create ausable index, otherwise no action is required.

FPEY0162I PACKAGE REPORTS NOTREQUESTED

ExplanationYou have specified that packages should not beexplained for a specific plan. All DBRMs are explained,but no packages.

User responseNone.

FPEY0164I PLAN <V1> HAS MORE THAN <V2>PACKAGES

ExplanationThe number of packages contained in the plan to beexplained is greater than PACKLIMIT. The packageslisted after the message include all versions ifPACKAGES(ALL) has been specified. Otherwise onlythe latest versions are displayed.

• <V1> is the plan name.• <V2> is the PACKLIMIT.

User responseIncrease the number of packages from a plan that canbe explained by specifying a PACKLIMIT greater thanthe number of packages to be explained. IfPACKAGES(ALL) has been specified, then the numberof packages to be explained can be reduced bychanging the PACKAGES(ALL) specification toPACKAGES(YES).

FPEY0166I PACKAGE <V1> IN COLLECTION<V2> HAS THE FOLLOWINGVERSIONS

ExplanationThe package specified exists in several versions. Allversion identifications are listed. The number ofpackages explained by OMEGAMON XE for DB2 PE iscontrolled by the PACKAGES, GEN, and FORCE options.Processing continues.

• <V1> is the package name.• <V2> is the collection name.

User responseNone.

FPEY0180I CONNECTION TO SERVER <V1>SUCCESSFUL

ExplanationNone.

• <V1> is the server.

User responseNone.

FPEY0182I CONNECTION RESET TO <V1>SUCCESSFUL

ExplanationNone.

• <V1> is the local server.

User responseNone.

FPEY0310I QUERY NO. <V1> DOES NOT EXISTFOR USER <V2> - REQUESTIGNORED

ExplanationThe query number specified in an EXPLAIN QUERYNOrequest could not be located in the accessedPLAN_TABLE. If necessary, specify the correctauthorization ID in the OWNER parameter. Thestatement is ignored, and processing continues withthe next Explain request.

• <V1> is the query number.• <V2> is the user.

User responseVerify that the query number does exist in the table.Also verify that the correct PLAN_TABLE is beingaccessed.

FPEY0314I QNO <V1> IN DBRM <V2> PLAN<V3> IS NOT IN<V4>.PLAN_TABLE

ExplanationThe specified query number could not be located forthe plan and DBRM listed in the PLAN_TABLE of theplan binder. OMEGAMON XE for DB2 PE Explaincontinues looking for the next query number for thesame plan.

• <V1> is the query number.


• <V2> is the DBRM.• <V3> is the plan.• <V4> is the authorization ID.

User responseNone.

FPEY0316I QNO <V1> IN PACKAGE<V2>.<V3> NOT IN<V4>.PLAN_TABLE

ExplanationThe specified query number could not be located forthe collection ID and package name listed in thePLAN_TABLE of the plan binder. OMEGAMON XE forDB2 PE Explain continues looking for the next querynumber for the same collection ID and package name.

• <V1> is the query number.• <V2> is the collection ID.• <V3> is the package name.• <V4> is the authorization ID.

User responseNone.

FPEY0320I PLAN <V1> NOT BOUND WITHEXPLAIN OPTION - REQUESTIGNORED

ExplanationThe plan specified in an EXPLAIN PLAN request wasnot bound with the EXPLAIN(YES) bind option. Thestatement is ignored, and processing continues withthe next Explain request.

• <V1> is the plan.

User responseRebind the plan and rerun the job with the same inputrecord.

FPEY0322I DBRM <V1> HAS NO ROWS IN<V2>.PLAN_TABLE - REQUESTIGNORED

ExplanationThe plan specified in an EXPLAIN PLAN request wasbound with the EXPLAIN(YES) bind option, but therows in the PLAN_TABLE owned by the authorizationID have been deleted for the given DBRM. The

statement is ignored, and processing continues withthe next Explain request.

• <V1> is the DBRM.• <V2> is the authorization ID.

User responseRebind the plan and rerun the job with the same inputrecord.

FPEY0324I PLAN_TABLE FOR USER <V1>DOES NOT EXIST - REQUESTIGNORED

ExplanationThe authorization ID given as the OWNER for anEXPLAIN QUERYNO request has no PLAN_TABLE. Thestatement is ignored, and processing continues withthe next Explain request.

• <V1> is the user.

User responseNone.

FPEY0325I UNABLE TO EXPLAIN <V1> - NOTAUTHORIZED TO ACCESS<V2>.PLAN_TABLE

ExplanationThe authorization ID does not have the privilege toperform the access to the PLAN_TABLE.

• <V1> is the collection ID and package name or theplan name.


User responseSee your system programmer to get authorization.

FPEY0368I LOCATION CANNOT BEDETERMINED UNTIL EXECUTIONTIME - PACKAGE IGNORED

ExplanationThe PACKAGES(YES) specification on the EXPLAINPLAN request has been ignored.

User responseNone.

FPEY0370I PACKAGE <V1>.<V2>.(<V3>) NOTBOUND WITH EXPLAIN OPTION


ExplanationThe package specified in an EXPLAIN PACKAGErequest was not bound with the EXPLAIN(YES) bindoption. The statement is ignored, and processingcontinues with the next Explain request.

• <V1> is the collection ID.• <V2> is the package ID.• <V3> is the version ID.

User responseNone.

FPEY0372I THIS REQUEST WILL RESULT IN<V1> PACKAGES WITH A TOTALOF <V2> SQL STATEMENTS(INCLUDING NON-EXPLAINABLE)

ExplanationThe package statement you have specified will resultin Explain of more than one package with a total ofmore than 300 SQL statements (counting bothexplainable and non-explainable). If this is what yourequire, the request should be reissued with theFORCE(YES) subparameter specified. The statement isignored, and processing continues with the nextExplain request.

• <V1> is the number of packages.• <V2> is the number of SQL statements.

User responseNone.

FPEY0374I NO PACKAGES FOUND FOR: <V1>

ExplanationNo packages were found in SYSIBM.SYSPACKAGE thatwould satisfy the input specification. The statement isignored, and processing continues with the nextExplain request.

• <V1> is the input specification.

User responseNone.

FPEY0376I NO PACKAGES FOUND FOR PLAN<V1>. MATCHING PACKAGE<V3>.<V4>.<V2> SPECIFIED INSYSPACKLIST

ExplanationNo packages were found in SYSIBM.SYSPACKAGE forthe specified plan. The statement is ignored, andprocessing continues with the next Explain request.

• <V1> is the plan.• <V2> is the location ID.• <V3> is the collection ID.• <V4> is the package ID.

User responseNone.

FPEY0378I PACKAGE <V1>.<V2>.(<V3>) HASNO ROWS INSYSIBM.SYSPACKSTMT

ExplanationNo rows were found in SYSIBM.SYSPACKSTMT for thespecified package in the specified collection. Thestatement is ignored, and processing continues withthe next Explain request.

• <V1> is the collection ID.• <V2> is the package ID.• <V3> is the version ID.

User responseNone.

FPEY0380I QMF QUERY <V1>.<V2> DOES NOTEXIST - REQUEST IGNORED

ExplanationA QMF query name specified in an EXPLAINQMFQUERY request does not exist. If the OMEGAMONXE for DB2 PE Explain submitter is not the owner ofthe query, the query name must be prefixed with theauthorization ID, like “AUTHID.QNAME”. Thestatement is ignored, and processing continues withthe next Explain request.

• <V1> is the authorization ID.• <V2> is the query name.

User responseVerify that the query name is spelled correctly.

FPEY0382I QMF OBJECT <V1>.<V2> IS A<V3> AND NOT A QUERY -REQUEST IGNORED


ExplanationThe QMF object specified as the query name is not aquery. The statement is ignored, and processingcontinues with the next Explain request.

• <V1> is the authorization ID.• <V2> is the query name.• <V3> is either a PROC or a FORM.

User responseNone.

FPEY0384I QUERY <V1>.<V2> IS A <V3>QUERY, MUST BE SQL - REQUESTIGNORED

ExplanationThe QMF query specified as the query name is not anSQL query. The statement is ignored, and processingcontinues with the next Explain request.

• <V1> is the authorization ID.• <V2> is the query name.• <V3> is either QBE or PROMPTED.

User responseNone.

FPEY0386I QMF QUERY <V1> IS RESTRICTEDTO OWNER - REQUEST IGNORED

ExplanationThe QMF query specified as the query name can onlybe explained by its owner. The statement is ignored,and processing continues with the next Explainrequest.

• <V1> is the specified QMF query.

User responseTo explain a QMF query created by a differentauthorization ID, the query must be saved with theSHARE=YES parameter.

FPEY0388I END OF QMF QUERY NOT FOUND -REQUEST IGNORED

ExplanationThe QMF statement was found to be larger than 32KB.Either the QMF query is more than 409 lines or theend-of-statement marker was not found. In eithercase, the request is ignored, and processing continueswith the next Explain request.

User responseNone.

FPEY0500W PREPARE OF <V1> FAILED. SQLCODE: <V2>

ExplanationA prepare statement failed during preparing a selectstatement for <V1>. A formatted print of the SQLCAand an error message are provided.

• <V1> is the object of the select statement.• <V2> is the SQL code.

User responseCheck the SQL code and follow the instructions givenin DB2 Messages and Codes (or in the correspondingmanual of the DB2 version you have installed).

FPEY0501I <V1>.PLAN_TABLE DOES NOTEXIST

ExplanationNone.


User responseNone.

FPEY0502I PLAN <V1> BOUND WITH *PACKLIST BIND OPTION.PACKAGES SHOWN MAY NOT BEUSED IN PLAN

ExplanationSince the PACKLIST bind option contained a wildcardspecification when the plan was bound, DB2 will notdetermine the packages to be used until runtime.OMEGAMON XE for DB2 PE Explain may report on alleligible packages, not just those used by the plan.

• <V1> is the plan.

User responseNone.

FPEY0504W DECLARE OF <V1> FAILED. SQLCODE: <V2>


ExplanationA declare statement failed during declaring theprogram cursor. A formatted print of the SQLCA and anerror message are provided.

• <V1> is the program cursor.• <V2> is the SQL code.


FPEY0508W OPEN OF <V1> FAILED. SQL CODE:<V2>

ExplanationAn open statement failed during opening the programcursor. A formatted print of the SQLCA and an errormessage are provided.

• <V1> is the program cursor.• <V2> is the SQL code.


FPEY0509W FUNCTION STEP <V1> FOR TABLE<V2>FAILED. SQL CODE <V3>

ExplanationAn SQL statement failed. A formatted print of theSQLCA and an error message are provided.

• <V1> is the function step keyword:STORAGE

No storage is available for the table rowSELECT

SQL SELECT statement failedSELECT COUNT

SQL SELECT COUNT statement failedINSERT

SQL INSERT statement failedPROGERR

Internal program error.• <V2> is the table name.• <V3> is the SQL code.


FPEY0510W FUNCTION STEP <V1> FORCURSOR <V2> WITH TABLE<V3>FAILED. SQL CODE <V4>


• <V1> is the function step keyword:STORAGE

No storage is available for the table rowOPEN

SQL OPEN CURSOR statement failedFETCH

SQL FETCH CURSOR statement failedCLOSE

SQL CLOSE CURSOR statement failedPROGERR

Internal program error.• <V2> is the cursor name.• <V3> is the table name.• <V4> is the SQL code.


FPEY0514W CURRENT SQLID COULD NOT BEOBTAINED, WILL USEAUTHORIZATION ID: <V1>

ExplanationThe OMEGAMON XE for DB2 PE Explain function couldnot select the current SQLID (secondary authorizationID). The program continues using the primaryauthorization ID. A formatted print of the SQLCA andan error message are provided.

• <V1> is the primary authorization ID.

User responseNone.

FPEY0515E CURRENT DEGREE <V1> COULDNOT BE OBTAINED


ExplanationThe OMEGAMON XE for DB2 PE Explain function couldnot set the current degree specified in the EXPLAINcommand. A formatted printout of the SQLCA isproduced.

• <V1> is the degree specified in the command.

User responseSee DB2 Messages and Codes for a description of theSQL code.

FPEY0520W OPEN OF C_KEYS FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSKEYS joined with SYSIBM.SYSINDEXES.OMEGAMON XE for DB2 PE Explain continues with thecurrent request, after printing the formatted SQLCAand the error message.


User responseSee DB2 Messages and Codes (or the correspondingmanual of the DB2 version you have installed) for adescription of the SQL code.

FPEY0522W FETCH OF C_KEYS FAILED. SQLCODE: <V1>

ExplanationAn error was detected during fetch fromSYSIBM.SYSKEYS joined with SYSIBM.SYSINDEXES.OMEGAMON XE for DB2 PE Explain continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0524W OPEN OF C_IXCOL FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSKEYS joined with SYSIBM.SYSINDEXESand SYSIBM.SYSTABLES. OMEGAMON XE for DB2 PE

Explain continues with the current request, afterprinting the formatted SQLCA and the error message.



FPEY0526W FETCH OF C_IXCOL FAILED. SQLCODE: <V1>

ExplanationAn error was detected during fetch fromSYSIBM.SYSKEYS joined with SYSIBM.SYSINDEXESand SYSIBM.SYSTABLES. OMEGAMON XE for DB2 PEExplain continues with the current request, afterprinting the formatted SQLCA and the error message.



FPEY0528W OPEN OF C_STMT FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSSTMT. A formatted print of the SQLCA andan error message are provided. Processing of thecurrent request is stopped and continues with the nextExplain request.


User responseNone.

FPEY0530W FETCH OF C_STMT FAILED. SQLCODE: <V1>

ExplanationAn error was detected during a fetch fromSYSIBM.SYSSTMT. A formatted print of the SQLCA andan error message are provided.


User responseNone.


FPEY0536W EXPLAIN OF A REMOTE OBJECT ISNOT ALLOWED. SQL CODE: <V1>

ExplanationAn immediate EXPLAIN statement failed, because thestatement being explained contained a table located inanother DB2 system. The EXPLAIN statement mayonly contain local objects. Processing continues withthe next Explain request.



FPEY0538W EXPLAIN OF SUPPLIED SQL-STATEMENT FAILED. SQL CODE:<V1>

ExplanationAn immediate EXPLAIN statement failed. A formattedprint of the SQLCA and an error message are providedtogether with the statement to be explained.Processing continues with the next Explain request.



FPEY0540W TABLE SPACE <V1>.<V2> NOTFOUND INSYSIBM.SYSTABLESPACE. SQLCODE: <V3>

ExplanationThe listed table space could not be found inSYSIBM.SYSTABLESPACE.

• <V1> is the database name.• <V2> is the table space name.• <V3> is the SQL code.


FPEY0542W TABLE <V1>.<V2> NOT FOUND INSYSIBM.SYSTABLES. SQL CODE:<V3>

ExplanationThe listed table could not be found inSYSIBM.SYSTABLES.

• <V1> is the authorization ID.• <V2> is the table name.• <V3> is the SQL code.


FPEY0544W COLUMN <V1> NOT FETCHEDFROM SYSIBM.SYSCOLUMNS. SQLCODE: <V2>

ExplanationThe listed table could not be found inSYSIBM.SYSCOLUMNS. For other SQL codes,OMEGAMON XE for DB2 PE Explain continues with thecurrent request, after printing the formatted SQLCAand the error message.

• <V1> is the column name.• <V2> is the SQL code.


FPEY0546W INDEX <V1>.<V2> NOT FOUNDFROM SYSIBM.SYSINDEXES. SQLCODE: <V3>

ExplanationThe listed index could not be found inSYSIBM.SYSINDEXES. A formatted print of the SQLCAand an error message are provided.

• <V1> is the authorization ID.• <V2> is the index name.• <V3> is the SQL code.



FPEY0548W PLAN <V1> NOT FOUND INSYSIBM.SYSPLAN. SQL CODE:<V2>

ExplanationThe listed plan could not be found inSYSIBM.SYSPLAN.

• <V1> is the plan name.• <V2> is the SQL code.


FPEY0554W DATABASE <V1>.<V2> NOT FOUNDIN SYSIBM.SYSDATABASE. SQLCODE: <V3>

ExplanationThe listed database could not be found inSYSIBM.SYSDATABASE.

• <V1> is the authorization ID.• <V2> is the database name.• <V3> is the SQL code.


FPEY0560W OPEN OF C_TSKEYS FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSKEYS. OMEGAMON XE for DB2 PE Explaincontinues with the current request, after printing theformatted SQLCA and the error message.



FPEY0580W UNAUTHORIZED ACCESS TO THEQ.OBJECT_DIRECTORY TABLE -REQUEST IGNORED

ExplanationThe user has specified an input record with anEXPLAIN QMFQUERY request. The plan does not haveselect authorization to the Q.OBJECT_DIRECTORYtable and returns an SQL code of either -551 or -552.Processing continues with the next Explain request.

User responseNone.

FPEY0582W UNAUTHORIZED ACCESS TO THEQ.OBJECT_DATA TABLE - REQUESTIGNORED

ExplanationThe user has specified an input record with anEXPLAIN QMFQUERY request. The plan does not haveselect authorization to the Q.OBJECT_DATA table andreturns an SQL code of either -551 or -552. Processingcontinues with the next Explain request.

User responseNone.

FPEY0584W ACCESS TO THE TABLEQ.OBJECT_DIRECTORY FAILED.SQL CODE: <V1>

ExplanationThe user has specified an input record with anEXPLAIN QMFQUERY request. The plan does not haveproper authorization to the Q.OBJECT_DIRECTORYtable. A formatted print of the SQLCA and an errormessage is provided.



FPEY0586W ACCESS TO THE TABLEQ.OBJECT_DATA FAILED. SQLCODE: <V1>

ExplanationThe user has specified an input record with anEXPLAIN QMFQUERY request. The plan does not have


proper authorization to the Q.OBJECT_DATA table. Aformatted print of the SQLCA and an error message areprovided. Processing continues with the next Explainrequest.



FPEY0587W QMF QUERY EXCEEDS LIMIT OF 32KB LENGTH, QUERY TRUNCATED

ExplanationYou wanted to explain a QMF query that exceeds the32 KB work area.

User responseIf the query contains many comments, remove themand try again.

FPEY0600W THE EXPLAIN TABLE<V1>.PLAN_TABLE WAS NOTCREATED. SQL CODE: <V2>

ExplanationAn attempt to create a PLAN_TABLE failed. The reasonis that the CREATETAB authorization is missing. Aformatted print of the SQLCA and an error message areprovided. Processing is terminated.

• <V1> is the authorization ID.• <V2> is the SQL code.


FPEY0602W ADDITION OF THREE V2R2COLUMNS TO <V1>.PLAN_TABLEFAILED. SQL CODE: <V2>

ExplanationAn attempt was made to ALTER the three columnsPREFETCH, COLUMN_FN_EVAL, and MIXOPSEQ to theuser’s existing PLAN_TABLE. One or more of the threeALTER statements failed.


User responseNone.

FPEY0605W ADDITION OF FOUR V3 COLUMNSTO <V1>.PLAN_TABLE FAILED.SQL CODE: <V2>

ExplanationAn attempt was made to ALTER the four columnsACCESS_DEGREE, ACCESS_PGROUP_ID,JOIN_DEGREE, and JOIN_PGROUP_ID to the user’sexisting PLAN_TABLE. One or more of the four ALTERstatements failed.


User responseNone.

FPEY0606W PLAN_TABLE IS NOT COMPATIBLEWITH DB2 REL <V1>. SQL CODE:<V2>

ExplanationThe format of the PLAN_TABLE is not compatible withthe current release of DB2.

• <V1> is the DB2 version.• <V2> is the SQL code.

User responseCheck the number of columns in your PLAN_TABLE todetermine what level of PLAN_TABLE exists, andcorrect as necessary before executing OMEGAMON XEfor DB2 PE Explain.

FPEY0607E PLAN_TABLE BELONGING TOPLAN OR PACKAGE OWNER ISNOT SUPPORTED BY DB2 PE

ExplanationThe PLAN_TABLE to be accessed is checked againstthe used DB2 version for validity. If the PLAN_TABLEfits a prior DB2 version, it is adapted to the currentlyused version of DB2. In this case the PLAN_TABLE maynot have the right number of columns for the DB2versions supported by DB2 PE. Thus, OMEGAMON XEfor DB2 PE cannot alter the PLAN_TABLE to supportthe currently active DB2 version.


User responseAsk your system administrator to correct thePLAN_TABLE. If necessary, new columns must beadded.

FPEY0608W ADDITION OF NINE V41 COLUMNSTO <V1>.PLAN_TABLE FAILED.SQL CODE: <V2>

ExplanationAn attempt was made to ALTER the nine columnsSORTC_PGROUP_ID, SORTN_PGROUP_ID,PARALLELISM_MODE, MERGE_JOIN_COLS,CORRELATION_NAME, PAGE_RANGE, JOIN_TYPE,GROUP_MEMBER, IBM_SERVICE_DATA to the user’sexisting PLAN_TABLE. One or more of the nine ALTERstatements failed.



FPEY0609W ADDITION OF ONE V5 COLUMN TO<V1>.PLAN_TABLE FAILED. SQLCODE: <V2>

ExplanationAn attempt was made to ALTER the columnWHEN_OPTIMIZE to the user’s existing PLAN_TABLE.The ALTER statement failed.



FPEY0612W ADDITION OF LAST COLUMN <V1>TO <V2>.PLAN_TABLE IN STEP<V3>FAILED. SQL CODE <V4>


• <V1> is the column name.• <V2> is the authorization ID.

• <V3> is the function step keyword:ALTER TABLE

SQL ALTER TABLE statement failedCOMMENT ON

SQL COMMENT ON statement failedCOMMIT

SQL COMMIT statement failedPROGERR

Internal program error.• <V4> is the SQL code.


FPEY0613W ALTERATION OF LAST COLUMN<V1> FOR <V2>. PLAN_TABLE INSTEP <V3>FAILED. SQL CODE<V4>


• <V1> is the column name.• <V2> is the authorization ID.• <V3> is the function step keyword:

ALTER TABLESQL ALTER TABLE statement failed

COMMENT ONSQL COMMENT ON statement failed

COMMITSQL COMMIT statement failed

PROGERRInternal program error.



FPEY0636W OPEN OF C_EEEPL FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forbinder.DGO_DGOPLAN. Printing of plan historyinformation is stopped. Normal processing continues.




FPEY0638W OPEN OF C_EEED2 FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forbinder.DGO_DGODBRM. Printing of DBRM informationis stopped. Normal processing continues.



FPEY0642W SELECT FROM DGO_DGOPLANFAILED. SQL CODE: <V1>

ExplanationAn error was detected when selecting a row frombinder.DGO_DGOPLAN. Saving plan information isstopped. Normal processing continues.



FPEY0644W OPEN OF C_EEED1 FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forbinder.DGO_DGODBRM. Saving of DBRM information isstopped. Normal processing continues.



FPEY0646W FETCH OF C_EEED1 FAILED. SQLCODE: <V1>

ExplanationAn error was detected during opening a cursor forbinder.DGO_DGODBRM. Saving of DBRM information isstopped. Normal processing continues.



FPEY0704W SELECT FROMSYSIBM.SYSPACKLIST FAILED.SQL CODE: <V1>

ExplanationAn error was detected during a select fromSYSIBM.SYSPACKLIST. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0706W OPEN OF C_PACKAGES_NAVNFAILED. SQL CODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSPACKAGE. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0708W OPEN OF C_PACKAGES FAILED.SQL CODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSPACKAGE. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.




FPEY0709W SELECT AGAINST SYSPACKAGEFAILED FOR PACKAGE <V1> .<V2>.(<V3>). SQLCODE: <V4>

ExplanationOMEGAMON XE for DB2 PE could not accessSYSIBM.SYSPACKAGE.

• <V1> is the collection ID.• <V2> is the package ID.• <V3> is the version ID.• <V4> is the SQL code.


FPEY0710W OPEN OF C_PACK_STMT FAILED.SQL CODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSPACKSTMT. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0712W FETCH FROM C_PACK_STMTFAILED. SQL CODE: <V1>

ExplanationAn error was detected during fetching a row fromSYSIBM.SYSPACKSTMT. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0714W OPEN OF C_SYSPACK_STMTFAILED. SQL CODE: <V1>

ExplanationAn error was detected during opening a cursor forSYSIBM.SYSPACKSTMT. Processing continues with thecurrent request, after printing the formatted SQLCAand the error message.



FPEY0720W CURRENT SERVER NAME COULDNOT BE ACQUIRED. SQL CODE:<V1>

ExplanationAn error was detected during selecting the CURRENTSERVER special register. Processing continues using16 blanks as the current server identification.



FPEY0722W CONNECT RESET FAILED. SQLCODE: <V1>

ExplanationNone.



FPEY0724W CONNECT TO <V1> FAILED (NON-CONNECTABLE STATE). SQL CODE:-752


ExplanationNone.



FPEY0726W CONNECT TO <V1> FAILED(SERVER NAME NOT KNOWN). SQLCODE: -950

ExplanationNone.



FPEY0728W CONNECT TO <V1> FAILED. SQLCODE: <V2>

ExplanationNone.

• <V1> is the server.• <V2> is the SQL code.


FPEY8001W CANNOT ACCESS SYSDBRM FOR<V1> IN <V2>. SQL CODE: <V3>

ExplanationNone.

• <V1> is the DBRM name.• <V2> is the plan name.• <V3> is the SQL code.


FPEZ - Migrate/Convert function messagesFPEZ1000E INPUT PARAMETER IS AN

INVALID REQUEST

ExplanationA parameter other than MIGRATE or CONVERT wasrequested.

User responseUse either MIGRATE or CONVERT.

FPEZ1001I <V1> HAS BEEN REQUESTED

ExplanationMIGRATE or CONVERT has been requested.

• <V1> can be either MIGRATE or CONVERT.

User responseNone.

FPEZ1002E UNABLE TO OPEN INPUT FILE.PROCESSING TERMINATED

ExplanationAn error occurred attempting to open the input file.

User responseCheck that the input file exists or is in the correctformat.

FPEZ1003E UNABLE TO READ INPUT FILE. RC<V1>, REASON <V2>

ExplanationAn error occurred attempting to read the input file.



FPEZ1004E INPUT FILE IS NOT ARECOGNIZED ACCOUNTING ORSTATISTICS SAVE FILE


ExplanationNone.

User responseUse a valid Accounting Save data set or Statistics Savedata set.

FPEZ1005E MIGRATE WAS REQUESTED BUTTHE FORMAT OF THE INPUT SAVEFILE IS NOT SUPPORTED BY THISPRODUCT RELEASE.

ExplanationThe input file is a Save data set that cannot bemigrated with this release.

User responseUse only Save data sets of the last and next-to-lastreleases as input for the save-file utility MIGRATEfunction.

FPEZ1006E CONVERT WAS REQUESTED BUTTHE INPUT FILE IS NOT ACURRENT VERSION SAVE FILE

ExplanationThe input file is a Save data set that is not compatiblewith this release. Save data sets from earlier versionsmust be migrated by the save-file utility MIGRATEfunction before being converted.

User responseUse only Save data sets of the current release or of thelast and next-to-last releases that have been migratedas input for the save-file CONVERT function.

FPEZ1007E UNABLE TO OPEN OUTPUT FILE.PROCESSING TERMINATED

ExplanationAn error occurred attempting to open the output file.

User responseCheck that the output file has been allocated correctly.

FPEZ1008I <V1> <V2> HAS STARTED

ExplanationThe accounting or statistics migrate function orconvert function has started.

• <V1> is accounting or statistics.• <V2> is the migrate or convert function.

User responseNone.

FPEZ1009E UNABLE TO WRITE TO OUTPUTFILE. RC <V1>, REASON <V2>

ExplanationAn error occurred attempting to write to the outputfile.



FPEZ1010I <V1> <V2> HAS FINISHED

ExplanationThe accounting or statistics migrate function orconvert function has finished.

• <V1> is accounting or statistics.• <V2> is the migrate or convert function.

User responseNone.

FPEZ1011I RECORDS IN: <V1>. RECORDSOUT: <V2>

ExplanationThis message shows the number of input recordsprocessed and the number of records written to theoutput file.

• <V1> is the number of input records.• <V2> is the number of output records.

User responseNone.

FPEZ1014E A DUPLICATE KEY WASENCOUNTERED IN THE OUTPUTFILE. THE FILE SHOULD BE EMPTY


ExplanationThis message shows the number of input recordsprocessed and the number of records that are writtento the output file.

• <V1> is the number of input records.• <V2> is the number of output records.

User responseNone.

FPEZ1015E INVALID FORMAT OF SAVE INPUTFILE. PROCESSING TERMINATED

ExplanationThe SAVE file contains an invalid structure and couldnot be migrated.

User responseNone.

FPEZ1016E SAVE INPUT FILE COMES FROMVERSION <V1>

ExplanationThis informational message indicates the underlyingsave file product version (520 or 530).

User responseNone.

KDP - Tivoli Enterprise Monitoring Agent (TEMA) for DB2 messagesIn the following error messages from KDPAnn01E to KDPAnn10I, nn represents one of the plex levelagents in the range of p0 through pd. nn identifies the unique error message number.

KDPAnn01E Node header is not available.

ExplanationThe plex level agent cannot find the storage area of thenodes that are registered at the TEMS. The controlblock address contains a NULL value. Therefore itcannot be used.

System actionThe requested data cannot be retrieved.

User responseContact IBM support to report this problem.

KDPAnn02E Cannot resolve the global areaaddress.

ExplanationThe plex level agent cannot find the storage area of aglobal control block that contains information that isrequired by the table code. The address of the controlblock contains a NULL value. Therefore it cannot beused.



KDPAnn03E Error %d from Init_HUB.

ExplanationThe connection to the HUB stopped. It cannot bereconnected.



KDPAnn04E Cannot obtain SQLInterfacestorage for %s.

ExplanationThe storage area to be used to run SQL requests withthe TEMS HUB cannot be allocated.


User responseThere might be a storage constraint on the startedtask. You can adjust the limit statements in the


KD5SYSIN parameter or in the KDSSYSIN parameter.If the problem persists after a restart, contact IBMSupport.

KDPAnn05E Error %d occurred when creatingan access plan.

ExplanationAn SQL request failed. An internal error occurred whencreating an access plan.



KDPAnn06E Error %d occurred when creating aCreate Request.

ExplanationAn SQL request failed. An internal error occurred whencreating a Create request.



KDPAnn07E Cannot locate Input SQLDA.

ExplanationThe SQL statement for obtaining the SQL structure thatis used to define input parameters failed.



KDPAnn08E Error %d occurred when creatingan Open Request.

ExplanationThe SQL request failed. The return code in this errormessage indicates the failure type.



KDPAnn09E Cannot locate Output SQLDA.

ExplanationIn the SQL interface, the SQLDA output area is missing.The SQLDA output area is required to map the datathat is returned by other agents.



KDPAnn10I Cannot detect DB2 systems online.

ExplanationCurrently, no DB2 systems are monitored.

System actionNo data is returned for this request.

User responseVerify that the DB2 systems are running and that oneach LPAR the KDPAGENTS are monitoring thesystems. If at startup time the plex level agent startedprior to the KDPAGENTS, online nodes cannot bedetected. Wait a minute before restarting the request.If the problem persists, contact IBM Support to reportthe problem.

KDPAP01I Connect failed DB2 <ssid>RC=nnnnnnnn RSN=nnnnnnnn

ExplanationD5API could not establish the connection to therequired DB2 instance in the OMPE server.

System actionConnection request is aborted. Possible causes are:

• The OMPE server is down• The DB2 instance is terminated from the OMPE

server


User responseNone.

KDPAP02I Disconnect failed DB2 <ssid>RC=nnnnnnnn

ExplanationD5API disconnect request failed. Possible causes areOMPE server is down or the DB2 instance isterminated from OMPE server.

System actionDisconnect request is aborted.

User responseNone.

KDPAP03E <ssid> table %%%%%%%% -Collection timed out. RC=20

ExplanationD5API collection request for table %%%%%%%%could not complete because another collectionrequest is still actively holding the resource. Thisusually indicates the active data collection took toolong to complete causing the current collectionrequest to fail.

System actionD5API collect request is aborted.


KDPAP04I DB2 <ssid> table %%%%%%%% -D5API connection lost. RC=16

ExplanationD5API could not complete the table collectionbecause the connection is terminated.

System actionCollect request is aborted.

User responseNone.

KDPAP05E Mutex init failed rc nnnn

ExplanationD5API resource control initialization failed.

System actionD5API request is aborted.


KDPAP06E Mutex trylock failed rc nnnn

ExplanationD5API connection request is unable to get hold of theresource.

System actionD5API connection request is aborted.

User responseNone.

KDPAP07E Mutex unlock failed rc nnnn

ExplanationD5API resource control release request failed.

System actionD5API connection request is aborted.

User responseNone.

KDPAT001 DPDC GLOBAL VECTOR TABLE NOTFOUND

ExplanationThe global vector table has not been allocated,indicating that the KDPBGV routine failed to properlyinitialize the environment.

System actionNone.

User responseLook for previous messages for an indication as towhat failed. Contact IBM support.


KDPAT007 DPDC COLLECTOR WAS NOTATTACHED FOR DB2 dbid.R0(xxxxxxxx) R1(xxxxxxxx)R15(xxxxxxxx)

ExplanationThe attempt failed to attach a new TCB for theKDPCOL00 module. Register 15 contains the errorcode from the attach request.

System actionNone.


KDPAU00I DB2PLEX AUTODISCOVERYSTARTED

ExplanationThis is an informational message.

System actionNone.

User responseNone.

KDPAU01F AUTODISCOVERY INITIALIZATIONFAILED

ExplanationOMEGAMON XE for DB2 could not recognize the DB2subsystems that are currently online.

System actionNone.

User responseContact IBM support. Until a solution is found, you canuse the Configuration Tool (formerly ICAT) to disableauto-discovery and manually identify the DB2systems.

KDPAU02E MULTIPLE IPDC AUTODISCOVERYCOMMANDS ISSUED

ExplanationThe auto-discovery command executed more thanonce.

System actionNone.

User responseCheck the RKANCMD file to ensure that only oneAUTODISCOVER command is specified. Remove theextra commands.

KDPAU03F UNABLE TO CREATE LOGICALRESOURCE


System actionNone.


KDPAU04F UNABLE TO ACQUIRE LOGICALRESOURCE


System actionNone.


KDPAU05F RESOURCE LOCK ERRORERRNO=nnnn

ExplanationA logic error is preventing the acquisition of a lock.


System action


KDPAU10F CONTROL BLOCK ALLOCATIONFAILED

ExplanationInsufficient storage for this function. Either not enoughstorage is available for the started task or some type ofstorage overlay is preventing the allocation.

System actionNone.


KDPAU11F CONDITION INITIALIZATIONFAILED

ExplanationThis is an internal error.

System actionNone.


KDPAU12F CONDITION MUTEXINITIALIZATION FAILED


System actionNone.


KDPAU13F MUTEX INITIALIZATION FAILED


System actionNone.


KDPAU14E COMMAND="command" FAILED.STATUS=nnnn

ExplanationThe indicated command did not complete properly.The command was issued to either start collectingdata for a new DB2 subsystem or to stop collectingdata for a DB2 system that is no longer active.

System actionNone.


KDPAU99I DB2PLEX AUTODISCOVERYSHUTDOWN

ExplanationAuto-discovery is no longer active.

System actionNone.

User responseNone.

KDPBG001 DPDC GVT ALREADY INSTALLEDAT ADDRESS xxxxxxxx


ExplanationThe KDPBGV00 routine has already run and allocatedthe global vector table (GVT).

System actionNone.


KDPBG002 DPDC REQUIRES APFAUTHORIZATION

ExplanationThe load library from where the program is loaded isnot authorized.

System actionNone.

User responseAdd the library to the APF authorization list and restartthe task.

KDPBG003 DPDC REQUIRES MVS/ESA

ExplanationThis product is not supported on the MVS operatingsystem you are currently running.

System actionNone.


KDPBG004 DPDC UNABLE TO ACQUIRESTORAGE FOR GVT

ExplanationThe storage request for the global vector table (GVT)failed. Either not enough virtual memory is available orthat a storage corruption is preventing spaceallocation.

System actionNone.


KDPCM001 DPDC IS NOT INITIALIZED


System actionNone.


KDPCM003 DPDC AVT ALLOCATION FAILURE,SIZE=nnnnnn

ExplanationThe storage request for the application vector table(AVT) failed. The size requested is shown as nnnnnnbytes. Either not enough virtual memory is available orstorage corruption is preventing space allocation.

System actionNone.


KDPCM030 DPDC (dbid) MONITOR ISALREADY STARTED

ExplanationThe request to start the collection for the DB2 systemwas ignored because the collector is already started.

System actionNone.

User responseNone.

KDPCM031 DPDC (dbid) MONITOR ISALREADY STOPPED


ExplanationThe request to stop the collection for the DB2 systemwas ignored because the collector is already stopped.

System actionNone.

User responseNone.

KDPCM035 DPDC (dbid) MONITOR IS BEINGTERMINATED

ExplanationThe collector for the specified DB2 system isscheduled for termination.

System actionNone.

User responseNone.

KDPCM037 DPDC (dbid) MONITOR IS BEINGRESTARTED. AVTADDRESS=xxxxxxxx

ExplanationThe collector for the specified DB2 system is beingrestarted. The address of the application vector table(AVT) is shown.

System actionNone.

User responseNone.

KDPCM039 DPDC COMMAND FORMAT ERROR

ExplanationAn error was detected on the command displayed justbefore this message.

System actionNone.

User responseCorrect the syntax and reissue the command.

KDPCM042 IPDC ERROR LOADING MODULEmodname

ExplanationThe system could not load the auto-discovery moduleor the display module from the load library.

System actionNone.

User responseVerify that the module exists.

KDPCT001 DPDC IS NOT INITIALIZED


System actionNone.


KDPCT002 DPDC GVT CREATED.ADDRESS=xxxxxxxx

ExplanationThe initialization of the global vector table hascompleted and the address is displayed.

System actionNone.

User responseNone.

KDPCT007 DPDC description (modname)ROUTINE NOT FOUND

ExplanationThe program identified by the description and modulename could not be loaded from the load library.


System actionNone.

User responseVerify that the proper load libraries are used and thatthe specified member is present.

KDPDB001 DPDC GLOBAL VECTOR TABLE NOTFOUND


System actionNone.


KDPDB007 DPDC SCOM SCAN (modname)ROUTINE NOT FOUND

ExplanationThe program identified by the module name could notbe loaded from the load library.

System actionNone.

User responseVerify that the proper load libraries are used and thatthe specified member is present.

KDPDB020 DB2 MASTER REGION FOR DB2IDdbid IS NOT FOUND OR DB2 ERLYNOT VALID

ExplanationThe collector code could not locate the DB2 masterstarted task for the indicated DB2 system. This can becaused by the dbidMSTR started task not running orbecause the ERLY control block is invalid.

System actionNone.

User responseIf the master task is not running, restart the DB2system. Otherwise, contact IBM support.

KDPDB025 JES CVT NOT FOUND


System actionNone.


KDPDB026 NO SUBSYSTEMS FOUND


System actionNone.


KDPDC005 DPDC UNABLE TO OPEN RKANPARDATASET R0(xxxxxxxx)R1(xxxxxxxx) R15(xxxxxxxx)

ExplanationAn error occurred when trying to open the PDSRKANPAR.

System actionNone.

User responseVerify that the data set is available and not allocated tosome other task in exclusive mode.

KDPDC006 DPDC UNABLE TO ENQUEUERKANPAR DATASET R0(xxxxxxxx)R1(xxxxxxxx) R15(xxxxxxxx)

ExplanationAn ENQUEUE on the RKANPAR data could not beobtained. The return code from the ENQUEUE requestis in R15.


System actionNone.

User responseNone.

KDPDC007 DPDC UNABLE TO FIND MEMBERmember R0(xxxxxxxx)R1(xxxxxxxx) R15(xxxxxxxx)

ExplanationThe indicated member member is not located in theRKANPAR PDS. The Load Runtime Members job mightnot have been run successfully from the ConfigurationTool (formerly ICAT).

System actionNone.

User responseNone.

KDPDC009 DPDC COMMAND {ENTERED |PROCESSED}: cccccccc

ExplanationIf PROCESSED is shown, the indicated command hasbeen successfully executed.

If ENTERED is shown, the indicated command hasfailed. Message KDPDC039 follows this message.

System actionNone.

User responseNone.

KDPDC01E NO MATCHING KDPCNFG PARMFOR DB2ID (dbid)

ExplanationThe data set member RKANPAR(KDPCFNFG) does nothave collection information entries for this DB2subsystem.

System actionNone.

User responseNone.

KDPDC039 DPDC COMMAND FORMAT ERROR

ExplanationThe previous command has a format error.

System actionNone.

User responseCorrect the format and reissue the command.

KDPDC03F UNABLE TO ALLOCATE MEMORYFOR ANCHOR


System actionNone.


KDPDC04E NO DATA COLLECTORS SPECIFIEDFOR DB2ID (dbid)

ExplanationA DB2 system was identified to be monitored, butthere are no collectors defined for that DB2subsystem.

System actionNone.

User responseVerify that the specifications used in the ConfigurationTool (formerly ICAT) for this DB2 system are correct.

KDPDC07E UNABLE TO ALLOCATE KDPDNFCPARM BLOCK



System actionNone.


KDPDC08E INVALID SUBSYSTEMTYPE=cccccccc

ExplanationThe subsystem type is not DB2ID.

System actionNone.

User responseVerify the statements in KDPCNFG to ensure theformat of the commands is proper. The commandsshould all start with DB2ID(xxxx).

KDPDC09E INVALID SUBSYSTEMID=ccccccccccc

ExplanationThe DB2 system name specified on the DB2IDstatement is either missing or has more than 4characters in the name.

System actionNone.

User responseCorrect this in the KDPCNFG member or rerun theConfiguration Tool (formerly ICAT) using the propername of the DB2 subsystem.

KDPDC10E INVALID COLLECTOR=ccccccccSPECIFIED

ExplanationThe collector name is unknown. The valid collectorsare COUPFAC(), THREAD(), OBJECTA(), OBJECTB(),OBJECTV, GBPSTAT(), CONFLICT() and SRM().

System actionNone.

User responseNone.

KDPDC11E ERROR OPENINGRKANPAR(KDPCNFG)

ExplanationThe system could not open the KDPCNFG member ofthe RKANPAR library. The Configuration Tool (formerlyICAT) creates this member when a LOAD operation isperformed for this product.

System actionNone.

User responseVerify that the member exists and can be accessed,and that the ICAT job succeeded.

KDPDC12E UNEXPECTED EOF INRKANPAR(KDPCNFG)

ExplanationAn EOF condition was raised while processing acommand with a continuation indicator.

System actionNone.

User responseCheck the KDPCNFG member to ensure that nocontinuation character is on the last line. TheKDPCNFG member can be recreated using theConfiguration Tool (formerly ICAT) job for loading theRTE.

KDPDC13E INVALID INTERVAL FOR DB2ID(dbid) cccccccc. IGNORED.

ExplanationThe interval value specified is not numeric and cannotbe processed. The value specified has to represent thenumber of seconds between samples.

System actionNone.


User responseVerify the value in the KDPCNFG member and set it toa number from 30 to 999.

KDPDC14F NO SUBSYSTEMS ENABLED INRKANPAR(KDPCNFG)

ExplanationNo parameters controlling the DB2 systems have beenspecified in the KDPCNFG member.

System actionNone.

User responseVerify that the Configuration Tool (formerly ICAT) jobto load the libraries has been run.

KDPDE007 DPDC COLLECTOR SUCCESSFULLYDETACHED FOR DB2 dbid. TCBADDRESS=xxxxxxxx

ExplanationThe collector has successfully stopped and the TCBused by it was released.

System actionNone.

User responseNone.

KDPDS00I MONITORED SUBSYSTEMS:

ExplanationThis message will appear in the RKLVLOG as a result ofissuing the DPDC DISPLAY command. This is the firstline of output from the DPDC DISPLAY command.

System actionNone.

User responseNone.

KDPDS02I DB2(dbid) STATE=ccccccccCOLLECTORS:

ExplanationThis message is shown in RKLVLOG as a result ofissuing the DPDC DISPLAY command. For eachmonitored DB2 system a line is shown with theidentifier and its state. Valid states are STOPPING,STOPPED, STOPPED (NO AUTODISCOVERY),RESTARTING, RESTARTED, STARTING, STARTED, orUNKNOWN. The valid collectors are COUPFAC(),THREAD(), OBJECTA(), OBJECTB(), OBJECTV,GBPSTAT(), CONFLICT() and SRM().

System actionNone.

User responseNone.

KDPDS03I THREAD(nnn) OBJECTV(nnn)SRM(nnn)

ExplanationThis message is shown in the RKLVLOG as a result ofthe DPDC DISPLAY command. Each monitored DB2system will display a line showing which collectors areactive and the sampling interval.

System actionNone.

User responseNone.

KDPDS99I nnn SUBSYSTEMS DISPLAYED

ExplanationThis message is shown in the RKLVLOG as a result ofthe DPDC DISPLAY command. This last line of theoutput contains the number of DB2 subsystems beingmonitored.

System actionNone.

User responseNone.

KDPGOVM1 OBJECT ANALYSIS state FORDSGROUP group ON DB2SUBSYSTEM dbid


ExplanationThis message is shown in the JESMSGL system outputfile and deals with group object analysis collection.Each DB2 system will display a line. The state value iseither ACTIVE or INACTIVE, group is the data sharinggroup name or the DB2 name (when data sharing isnot in use), and dbid identifies the monitored DB2system.

System actionNone.

User responseNone.

KDPGOVM2 OBJECT ANALYSIS ON MVSIDsmfid USING JOB cccccccc

ExplanationThis message is shown in the JESMSGL system outputfile and deals with group object analysis collection.The smfid identifies the MVS image where the DB2 isrunning and cccccccc is the name of the started taskthat collects data for the volume activity workspaces.

System actionNone.

User responseNone.

KDPGOVM3 OBJECT ANALYSIS ON MVSIDsmfid DISABLED

ExplanationThis message isw shown in the JESMSGL systemoutput file and deals with group object analysiscollection. The OBJECTV data collector for the systemidentified by smfid has been disabled, because itreached its limit of five exceptions (abends) whentrying to gather data. This collector will remaindisabled until the address space is recycled.

System actionNone.

User responseNone.

KDPIN009 DPDC VECTOR TABLE NOT FOUND.DBDC NOT INITIALIZED


System actionNone.


KDPIRA01I AGENT BASE INITIALIZATIONCOMPLETE

ExplanationThe agent has completed basic initialization functionssuch as loading required modules.

System actionThe agent will continue with other functions such asconnecting to the TEMS and establishing serverconnections for DB2 subsystems that it will monitor.

User responseNone.

KDPPIR10E The number of arguments exceedsthe limit of 32.

ExplanationThe number of arguments that is passed to the plexlevel agent at startup exceeds the predefined limit of32 arguments.

System actionThe plex level agent stopped to prevent potentialstorage overlays.

User responseVerify the format of the command in the KD5AGSTmember of the RKANCMDU library. It should look likethis:

AT ADD ID=KDPP DELAY=00:00:15CMD='IRAMAN KDPPLEX START'


If there are text strings that do not match the exampleabove, correct the text strings and restart the plexlevel agent.

KDPPIR11E The length of the argument stringexceeds the limit of 4096 bytes.

ExplanationThe length of the argument string that is passed to theplex level agent at startup exceeds the predefined limitof 4096 bytes.

System actionThe plex level agent stopped to prevent potentialstorage overlays.

User responseVerify the format of the command in the KD5AGSTmember of the RKANCMDU library. It should look likethis:

AT ADD ID=KDPP DELAY=00:00:15CMD='IRAMAN KDPPLEX START'

If there are text strings that do not match the exampleabove, correct the text strings and restart the plexlevel agent.

KDPPIR55E Cannot allocate the DPGLOBALcontrol block.

ExplanationThe storage for a common area that is required by theplex level agent cannot be allocated. There might be astorage constraint on the started task.

System actionThe plex level agent stopped.

User responseVerify that the task that is started to run the plex levelagent is not constrained by any memory restrictions inthe KD5SYSIN member of the RKANPAR library. If theplex level agent runs in the same address space as aTEMS, verify the storage specifications in theKDSSYSIN member of the RKANPAR library.

KDPPIR57E Cannot allocate the PLEX Statuscontrol block.

ExplanationThe storage for a common area that is required by theplex level agent cannot be allocated. There might be astorage constraint on the started task.


User responseVerify that the task that is started to run the plex levelagent is not constrained by any memory restrictions inthe KD5SYSIN member of the RKANPAR library. If theplex level agent runs in the same address space as aTEMS, verify the storage specifications in theKDSSYSIN member of the RKANPAR library.

KDPPIR58E Error %d occurred when trying tofind the PLEX status.

ExplanationThe plex level agent cannot obtain the statusinformation on the node that represents the plex levelDB2 node. The status that is returned for the plex levelDB2 node is unexpected. The following error codes forthe status request are displayed:8

Error returned while preparing the SQL statement.12

Error returned while creating the request for theSQL statement.

16Error returned while opening the request for theSQL statement.

20Error returned while obtaining the SQLDA outputarea.


User responseAn internal error might have occurred or thecommunication with the TEMS HUB failed. Verify thatthe TEMS HUB is running and that it is correctlyspecified by the HUB_NAME parameter:

• If the HUB is down, restart the HUB.• If the HUB is not correctly specified, correct the

value for the HUB_NAME parameter in the KD5ENVmember of the RKANPARU library.


• If the HUB is running and correctly specified, contactIBM Support to report the problem.

KDPPIR59E The KDPPLEX agent stoppedbecause the global area is notallocated.

ExplanationThe storage for a common area that is required by theplex level agent is not allocated.

System actionThe plex level agent stopped because of an internalerror.


KDPPIR65E Cannot allocate the ConnectionObject.

ExplanationThe storage for a common area that is required by theplex level agent be cannot allocated. There might be astorage constraint on the started task.


User responseVerify that the task that is started to run the agent isnot constrained by any memory restrictions in theKD5SYSIN member of the RKANPAR library. If theagent is running in the same address space as a TEMS,verify the storage specifications in the KDSSYSINmember of the RKANPAR library.

KDPPIR66E Error %d occurred whenconnecting to %s on port %s

ExplanationAn error occurred when connecting to the TEMS HUB.The error message contains the error number, thevalue for the HUB name, and the port number.

One of the following errors might have occurred:8

Global area not found.12

HUB_NAME not found.16

Storage for connection not available.

20Storage for nodes not available.


User responseThe error codes indicate communication errors orstorage errors.

• If the HUB NAME is not found, verify that the TEMSHUB is running and that the HUB_NAME variable isset correctly in the KD5ENV member of theRKANPAR library.

• If one of the other storage errors occurred, verifythat the specifications in the KDSSYSIN member ofthe RKANPAR library are correct.

KDPPIR71E Connection failure message: %s

ExplanationThe connection to the TEMS HUB failed as indicated bythe message number KDPPIR66E, which is displayedbefore this message is displayed. This messagescontains more information to resolve the connectionerror.

System actionThe agent stopped because of one of the errorsituations that are described in the message numberKDPPIR66E.


KDPPIR72E Cannot connect to TEMS HUB.Therefore KDPPLEX stopped: rc =%d

ExplanationThe agent cannot connect to TEMS HUB. This messageis usually preceded by the message numberKDPPIR66E and KDPPIR71E.


User responseThe error codes indicate communication errors orstorage errors.


• If the HUB NAME is not found, verify that the TEMSHUB is running and that the HUB_NAME variable isset correctly in the KD5ENV member of theRKANPAR library.

• If one of the other storage errors occurred, verifythat the specifications in the KDSSYSIN member ofthe RKANPAR library are correct.

KDPSC001 DPDC GLOBAL VECTOR TABLE NOTFOUND


System actionNone.


KDPRT01E Wait for OMPE server, <reason>

ExplanationThe agent is unable to connect to the OMPE Server.One of these reasons is displayed:

• OMPECT not inited• OMPECT access error• OMPECT struct error• PE STOKEN loc error• D2_STC not active• D2_STC not found• Routtbl not inited

System actionAgent waits for the connection to OMPE server.

User responseContact IBM support after verifying the following:

1. If HLQ.RKANPARU(KD5ENV) has environmentvariable KDP_D2_STC set, make sure the specifiedOMPE server task is running. If not, start the OMPEserver task.

2. There could be a delay before the agent cancommunicate with OMPE server task. The delay isconfigurable using environment variableKDP_STATUS_REFRESH inHLQ.RKANPARU(KD5ENV). While waiting, you maysee KD5ASSCT messages.

3. If OMPE server task is running, check the server logto see if there are any error associated with D5API.The expected messages from OMPE server log are:

KO2I0100I D5API COLLECTORINITIALIZATION IN PROGRESS

KO2I0149I D5API ASM BUILD IS 04/17/1511.11

KO2I0130I D5API REGISTRY ENTRYSUCCESSFULLY REBUILT

KO2I0148I D5API USING REGISTRYXE_D5APIRTB_V530

KO2I0141I D5API COLLECTOR TRACE SET TONO

KO2I0141I D5API COLLECTOR STIMER SETTO 00003000

KO2I0101I D5API COLLECTORINITIALIZATION COMPLETE

KO2I0154I D5API COLLECTOR CONNECTED TODB2 ssid ON BEHALF OF AGENT agenttask

If you do not see above messages, checkHLQ.RKD2PAR(ompetask), make sure that you havecommon collector started.

* * Starts the Common Collector.* EXEC OMPECCPC

KDP5004I <ssid> table %%%%%%%% -D5API connection lost. RC=16

ExplanationD5API could not complete the table collectionbecause the connection is terminated.

System actionCollect request is aborted.

User responseNone.


KO2A - Anomaly Detection MessagesKO2AD000I xxxx Anomaly Detection <msg>

ExplanationFor subsystem xxxx, shows informational messages atthe start or end of anomaly detection.

System actionNone.

User responseNone.

KO2AD020I xxxx <mgs>

ExplanationFor subsystem xxxx, shows messages from ADDBUG >0.

System actionNone.

User responseThis message is for the use of IBM Software Support.If requested, send diagnostic messages toIBM Software Support.

KO2AD040I xxxx <mgs>

ExplanationFor subsystem xxxx, shows messages from ADDBUG >0.

System actionNone.

User responseThis message is for the use of IBM Software Support.If requested, send diagnostic messages toIBM Software Support.

KO2AD101E xxxx Anomaly Storage Areas arebeing reused

ExplanationAnomaly detection has used all the memory locationsallocated.

System actionMemory areas will be reused.

User responseIncrease the memory allocation as appropriate.

KO2AD102W xxxx Anomaly ProcessingSuspended

ExplanationFor subsystem xxxx Anomalies > 1000 have beendetected. But the agent is not processing them tomake the available for display.

System actionAnomaly Detection Stops until the agent begins toprocess the Anomalies.

User responseMake sure the History Collection for attribute GroupDB2 Anomaly is activated.

KO2AD103W xxxx Anomaly ProcessingResumed

ExplanationFor subsystem xxxx Anomaly Collection had beenpreviously suspended and has now resumed.

System actionNone.

User responseNone.

KO2AD200W xxxx Anomaly Detection Ad headerEyecatcher error.

ExplanationThe main control block for anomaly detection does notcontain a valid eyecatcher.

System actionAnomaly detection stops.


User responseAnomaly detection might need to be stopped andrestarted.

KO2D0200W xxxx STORAGE storage_actionfailed rc=nnnnnnnn

ExplanationIf storage_action is OBTAIN, anomaly detection cannotobtain storage to record an anomaly.

If storage_action is RELEASE, anomaly detectioncannot release storage to record an anomaly.

System actionThe anomaly is not recorded or storage has not beenreleased.

User responseNone.

KO2D0201E xxxx IARV64 REQUEST=requestfailed rc=xxxxxxxx rs=xxxxxxxx(KO2AINTB)

ExplanationAnomaly detection was not able to get or releaseabove the bar storage.

System actionIf request is GETSTOR, anomaly detection is notstarted.

If request is DETACH, anomaly detection storage hasnot been freed correctly.

User responseIf request is GETSTOR, the amount of storage used byanomaly detection might need to be lowered.

If request is DETACH, the storage will probably beautomatically freed by z/OS at TCB termination.

KO2D0202E xxxx TCBTOKEN failed rc=xxxx(KO2AINTB)

ExplanationAnomaly detection was not able to obtain the TCBtoken.

System actionAnomaly detection will not start.

User responseNone.

KO2D0203E xxxx $ZTCAE ANOMALY failedrc=xxxxxxxx,rs=xxxxxxxx

ExplanationThe main anomaly detection control block could not befound.

System actionAnomalies will no longer be processed by the agent.

User responseStop and restart anomaly detection.

KO2H1413E xxxx NEAR-TERM HISTORY DATACOLLECTOR - At least one of theAnomaly Detection Use keys mustbe Y

ExplanationAnomaly detection uses the Thread Identity fields forgrouping metrics. At least one key must be specifiedfor subsystem xxxx.

System actionNear term history and anomaly detection are notstarted.

User responseCorrect the anomaly detection control cards forCOPTxxxx.

KO2D - D5API Collection for TEP and Enhanced 3270UIKO2D0000I To display trace debug output,

contact IBM Support to activatethe traces.

KO2D0001E ssid <repname>CT_getCounterValueRaw

<table><field> not found(KO2ABROW)



User responseContact IBM support to report the error.

KO2D0002E Counter Table Address zero(KO2ABROW)



KO2D0004E ssid FL_addFieldByName<table><field> - ReturnCode=nnnnnnnn - ReasonCode=nnnnnnnn (<module>).


User responseContact IBM support to report the error codes.

KO2D0005E ssid Appl Client - RC: nnnnnnnnRS: nnnnnnnn Server RC:nnnnnnnn RS: nnnnnnnn OMRC:nnnnnnnn (KO2APHLR)

Explanation:An internal exception occurred.


KO2D0006E ssid CT_getCounterValue <field>not found (KO2ABROW)



KO2D0007E ssid CT_reset/CT_construct -Return Code= nnnnnnnn - ReasonCode= nnnnnnnn (<module>).

ExplanationAn internal exception occurred in one of the modulesKO2APHLR, KO2AHLR, or KO2CPUCL.


KO2D0008E ssid <table> CT_ParseStream -Return Code=nnnnnnnn - ReasonCode=nnnnnnnn (<module>).

ExplanationAn internal exception occurred in one of the modulesKO2APHLR, KO2ABROW or KO2CPUCL.


KO2D0009E ssid FR_addCriteria<field> -Return Code=nnnnnnnn - ReasonCode=nnnnnnnn (<module>)

ExplanationAn internal exception occurred in one of the modulesKO2AHLR or KO2CPUCL.


KO2D0010E ssid Incorrect Collection TableName <table> (<module>)

ExplanationAn internal exception occurred in one of the modulesKO2AHLR or KO2AFSAM.


KO2D0011E ssid Moving value to a row wouldexceed table size nnnnnnnn FieldName=<field> Length=nnnnnnnn



KO2D0012E ssid <routine> - ReturnCode=nnnnnnnn - ReasonCode=nnnnnnnn (<module>)


ExplanationAn internal exception about <routine> has occurred inone of the modules KO2ABROW, KO2AFSAM,KO2AHLR, KO2APHLR or KO2CPUCL.

User responseContact IBM support to report the error codes

KO2D0013E ssid %%%%%%%%%%%%%%%%%%%%% (<module>)

ExplanationAn internal exception has occurred in one of themodules KO2AFSAM, KO2AHLR, KO2APHLR,KO2CPUCL or KO2LACRA.


KO2D0014I ssid Cancel thread thread ID

ExplanationThis message provides detail about the cancellationaction performed:

• Message ID (KO20014I)• TSO ID of user who canceled thread• DB2 subsystem ID• Thread ID of canceled thread• DSNV message DSNV426I (thread canceled) or

DSNV427I (invalid thread ID specified)

User responseNone required.

KO2D0200W xxxx STORAGE storage_actionfailed rc=nnnnnnnn

ExplanationIf storage_action is OBTAIN, anomaly detection cannotobtain storage to record an anomaly.

If storage_action is RELEASE, anomaly detectioncannot release storage to record an anomaly.

System actionThe anomaly is not recorded or storage has not beenreleased.

User responseNone.

KO2D0201E xxxx IARV64 REQUEST=requestfailed rc=xxxxxxxx rs=xxxxxxxx(KO2AINTB)

ExplanationAnomaly detection was not able to get or releaseabove the bar storage.

System actionIf request is GETSTOR, anomaly detection is notstarted.

If request is DETACH, anomaly detection storage hasnot been freed correctly.

User responseIf request is GETSTOR, the amount of storage used byanomaly detection might need to be lowered.

If request is DETACH, the storage will probably beautomatically freed by z/OS at TCB termination.

KO2D0202E xxxx TCBTOKEN failed rc=xxxx(KO2AINTB)

ExplanationAnomaly detection was not able to obtain the TCBtoken.

System actionAnomaly detection will not start.

User responseNone.

KO2D0203E xxxx $ZTCAE ANOMALY failedrc=xxxxxxxx,rs=xxxxxxxx

ExplanationThe main anomaly detection control block could not befound.

System actionAnomalies will no longer be processed by the agent.

User responseStop and restart anomaly detection.


KO2E - Object Analysis messagesKO2E3000I EVENTMGR INITIALIZATION IN

PROGRESS

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) is currently starting up.

System actionProcessing continues.

User responseNone.

KO2E3001I EVENTMGR INITIALIZATIONSUCCESSFUL

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) started successfully.

System actionThe Event Collection Manager is now active.

User responseNone.

KO2E3002I EVENTMGR MODIFY PROCESSINGIN PROGRESS

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) is currently carrying out an MVSMODIFY request.


User responseNone.

KO2E3003I EVENTMGR STOP PROCESSING INPROGRESS

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) is currently carrying out an MVSstop request.


User responseNone.

KO2E3004I EVENTMGR TERMINATIONCOMPLETE

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) has now shut down.

System actionNone.

User responseNone.

KO2E3005W EVENTMGR %%%% IS ALREADYACTIVE IN SERVER %%%% -START REQUEST REJECTED

ExplanationThe OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) is already active. You cannotstart another, because only one Event CollectionManager is allowed for each version of OMEGAMON XEfor DB2 PE that is running on any one MVS system.

System actionThe start request is ignored.

User responseNone.

KO2E3006E EVENTMGR MODIFY REQUESTCONTAINS INVALID SYNTAX

ExplanationA syntax error in the MVS MODIFY request is found.The OMEGAMON XE for DB2 PE Event CollectionManager (EVENTMGR) cannot respond.

System actionThe MVS MODIFY request is ignored.


User responseCorrect the MVS MODIFY request, then reissue it.

KO2E3007W START REQUEST IGNORED,MONITORING IS ACTIVE

ExplanationThe start request has failed because collection isalready active.

System actionThe request is ignored.

User responseNone.

KO2E3008E START DB2 FAILED, DB2 NOTDEFINED

ExplanationThe DB2 subsystem ID passed on the start request isnot defined on the MVS system in use.


User responseCorrect the DB2 ID on the start request.

KO2E3009S START DB2 FAILED, DB2 NOTACTIVE

ExplanationThe DB2 subsystem ID passed on the start request isnot currently active on the MVS system in use.


User responseCorrect the DB2 ID on the start request.

KO2E3010S START DB2 FAILED, DB2 VERSIONNOT SUPPORTED

ExplanationThe start request has failed because the DB2 versionis not supported by this release of OMEGAMON XE forDB2 PE.



KO2E3011I NO DB2 SUBSYSTEM CURRENTLYMONITORED

ExplanationNo collections are active for any DB2 subsystems.


User responseNone.

KO2E3012W STOP REQUEST DENIED,MONITORING NOT ACTIVE

ExplanationThe stop request could not be processed becausemonitoring is not active for the specified DB2subsystem.


User responseNone.

KO2E3013E SYNTAX ERROR LOCATED INPARM= AT STARTUP

ExplanationUsually, a parameter is configured using an automaticprocess, however the user has bypassed the usualconfiguration. Three data members might be incorrectin the RKD2PAR parameter data set. There might be adata member in RKDPAR that has the same name asthe started task.

System actionProcessing terminates.


User responseRebuild the runtime environment by using theConfiguration Tool (formerly ICAT) to restore the dataset back to the correct values.

KO2E3014U INSTALL OF SSCVT HAS FAILED

ExplanationThe Event Collection Manager (EVENTMGR) hasencountered an error while starting up in thesubsystem.

System actionProcessing is terminated.


KO2E3040I VOLUME ANALYSISINITIALIZATION COMPLETE

ExplanationVolume analysis collection has successfully completedits initialization processing. Volume analysis is startedautomatically when object analysis collection isstarted for the first DB2 subsystem being monitored.

System actionProcessing continues; volume analysis is active.

User responseNone.

KO2E3041I VOLUME ANALYSIS HASTERMINATED

ExplanationVolume analysis collection has successfully shut down.This message is issued when the Event CollectionManager (EVENTMGR) terminates.

System actionNone.

User responseNone.

KO2E3042I VOLUME ANALYSIS TERMINATEDFOR DB2=subsystem

ExplanationVolume analysis collection for the indicated DB2subsystem has terminated because object analysiscollection has terminated.

System actionProcessing continues; but volume analysis for theindicated DB2 subsystem is terminated.

User responseNone.

KO2E3043S VOLUME ANALYSIS ERRORRECOVERY: ID=V270,MOD=cccccccc, OFFSET=nnnnnn,CODE=nnnn/nnnnnnnnn

ExplanationAn error occurred during a Volume Analysis datagathering pass. Volume Analysis successfullyrecovered from this error. This message describes thetype of error that occurred.

System actionVolume Analysis processing continues.

User responseNo action is required.

KO2E3050I %%%% OBJECT ANALYSISPHASE1 INITIALIZATIONCOMPLETE

ExplanationThe startup of object analysis collection for theindicated DB2 subsystem has successfully completedphase 1 initialization processing.


User responseNone.

KO2E3051I %%%% OBJECT ANALYSISPHASE2 INITIALIZATIONCOMPLETE


ExplanationThe startup of object analysis collection for theindicated DB2 subsystem has successfully completedphase 2 initialization processing.


User responseNone.

KO2E3052E %%%% OBJECT ANALYSISCANNOT ESTABLISH PREFETCHCOLLECTION, RSN=nnnn

ExplanationObject Analysis cannot completely collect informationabout DB2 prefetch data.


User responseNone.

KO2E3053I %%%% COMMON COLLECTORINTEGRATION WITH OMPE NOTAVAILABLE

ExplanationThe OMEGAMON Collector STEPLIB included the Db2Data Access Common Collector (CQC) Library, but notat the correct level to support CQC management ofOMPE functions.


User responseProgrammer or Operator Response: If CQCmanagement of Object Analysis is required, the PTFfor CQC APAR PH01031 must be available to the OMPECollector.

KO2E3054I %%%% OBJECT ANALYSISGETPAGE MANAGEMENT

ExplanationIndicates if Object Analysis will manage the GETPAGEdata collection directly (ECTL) or will use the IBM Db2

Data Access Common Collector (CQC) to manage thecollection.


User responseNone.

KO2E3055E %%%% GETPAGE ENABLE ERRORCDE=xxxxxxxx, RC=xxxxxxxx,RSN=xxxxxxxx

ExplanationAn internal error occurred during GETPAGE processingenablement.

System actionNone.

User responseThis indicates an internal logic error; contact IBMSupport.

KO2E3061I %%%% OBJECT ANALYSISTERMINATION IN PROGRESS

ExplanationObject analysis is terminating collection for theindicated DB2 subsystem. This message is issuedduring object analysis termination.


User responseNone.

KO2E3062I %%%% OBJECT ANALYSISPHASE1 TERMINATIONCOMPLETE

ExplanationObject analysis phase 1 termination was successful forthe indicated DB2 subsystem. This message is issuedduring object analysis termination.



User responseNone.

KO2E3063I %%%% OBJECT ANALYSISPHASE2 TERMINATIONCOMPLETE

ExplanationObject analysis phase 2 termination was successful forthe indicated DB2 subsystem. This message is issuedduring object analysis termination.


User responseNone.

KO2E3064I %%%% OBJECT ANALYSISTERMINATION SUCCESSFUL

ExplanationObject analysis termination was successful for theindicated DB2 subsystem. This message is issuedupon completion of object analysis termination.


User responseNone.

KO2E3065I %%%% OBJECT ANALYSIS HASDETECTED THAT DB2TERMINATED

ExplanationObject analysis collection has detected that themonitored DB2 subsystem has terminated.

System actionObject analysis collection for the indicated DB2subsystem is terminating.

User responseNone.

KO2E3066S %%%% OBJECT ANALYSISINITIALIZATION FAILED REASONCODE=%%%%

ExplanationObject analysis for the indicated DB2 subsystem failedduring initialization. The indicated reason codeconsists of four hexadecimal digits of the form pnnn.

p identifies the phase of Object Analysis initialization:1

Initialization phase 12

Initialization phase 2

nnn identifies the error:000

Internal DB2 control block validation failed.001

Internal DB2 module validation failed.002

OMEGAMON interface module load failed.

System actionObject analysis collection for the indicated DB2subsystem is not started.


KO2E3067S %%%% OBJECT ANALYSISTERMINATION CLEANUP PHASE1FAILED

ExplanationObject analysis for the indicated DB2 subsystem failedduring phase 1 termination processing.



KO2E3068S %%%% OBJECT ANALYSISTERMINATION CLEANUP PHSE2FAILED

ExplanationObject analysis for the indicated DB2 subsystem failedduring phase 2 termination processing.




KO2E3069U %%%% OBJECT ANALYSISABNORMAL TERMINATION INPROGRESS

ExplanationAn abnormal condition was detected in the ObjectAnalysis GETPAGE or I/O intercepts. An MVS SVCdump has occurred and should be retained forproblem determination. The DB2 subsystem beingmonitored is identified in the message text.

System actionThe Object Analysis function for this DB2 subsystem isterminated.


KO2E3070I %%%% OBJECT ANALYSISINITIALIZATION IN PROGRESS

ExplanationThe object analysis collection for the indicated DB2subsystem is starting. This message is written to thesystem log whenever an object analysis start requestis being processed.


User responseNone.

KO2E3071I %%%% OBJECT ANALYSISINITIALIZATION SUCCESSFUL

ExplanationThe startup of object analysis collection for theindicated DB2 subsystem was successful.

System actionObject analysis collection is now active.

User responseNone.

KO2E3078S %%%% OBJECT ANALYSISPHASE2 TERMINATION HASFAILED

ExplanationObject analysis for the indicated DB2 subsystem failedduring termination.

System actionObject analysis collection for the indicated DB2subsystem did not successfully terminate.


KO2E3080I %%%% OBJECT ANALYSISFORCED INTERVAL PROCESSINGSTARTED

ExplanationObject Analysis for the indicated DB2 subsystemdetected a shortage of available virtual memory in theaddress space.

System actionNone.

User responseModify the REGION= parameter on the started procthat runs Object Analysis. Increase the memoryallocation for the address space running ObjectAnalysis and restart Object Analysis.

KO2E3081I %%%% OBJECT ANALYSISFORCED INTERVAL PROCESSINGENDED

ExplanationThis message is issued a short time after theKO2E3080I message and indicates the successfulcompletion of the interval processing.

System actionObject Analysis stops temporarily.



KO2E3082S %%%% OBJECT ANALYSISMEMORY SHORTAGE SHUTDOWN

ExplanationObject Analysis cannot continue with currentprocessing because of virtual storage constraints.

System actionNone.


KO2E3083I %%%% OBJECT ANALYSISRESTART WILL BE DONE ON DB2RESTART

ExplanationObject Analysis detected that the indicated DB2subsystem has stopped.

System actionObject Analysis will remain active and will restart itsmonitoring when the indicated DB2 subsystemrestarts.

User responseNone.

KO2E3084S %%%% OBJECT ANALYSISRESTART FAILED

ExplanationObject Analysis could not restart its monitoring of theindicated DB2 subsystem.

System actionObject Analysis for the indicated DB2 subsystem isterminated.

User responseManually restart Object Analysis for the indicated DB2subsystem. If the attempt fails, contact IBM support.

KO2E3085I %%%% OBJECT ANALYSISRESTART TERMINATED DUE TO B2STOP COMMAND

ExplanationObject Analysis was waiting for the indicated DB2subsystem to be restarted, but was stopped by theuser via a Stop command.

System actionObject Analysis for the indicated DB2 subsystem isterminated.

User responseNone.

KO2E3991E EVENTMGR INVALID START PARMSUPPLIED

ExplanationThis message is issued by the Event Manager toindicate that an invalid START parameter has beenspecified in member EMGR<lpar> of the RKD2PARparameter library.

System actionEvent Manager initialization is terminated.

User responseCorrect the parameter problem and restart the EventManager.

KO2H - Near-Term History Data Collector messagesKO2H0001W ssid NEAR-TERM HISTORY DATA

COLLECTOR - aaaaaaaaaa DB2subsystem NOT ACTIVE. WAIT, ORREPLY ANOTHER DB2 ID, ORREPLY STOP

ExplanationThe indicated DB2 subsystem is not active at this time.aaaaaaaaaa = COLLECTION, if this is the DB2 forwhich near-term history data is to be collected.


System actionWaits for a reply from the operator and then takes therequested action.

User responsePerform one of the following actions:

• Wait for the DB2 subsystem to become active and donot give a reply. This WTOR message is automaticallycanceled when the DB2 becomes active.

• Reply with the ID of another DB2 subsystem to beused in place of the inactive DB2.

• Reply Stop to terminate the attempted datacollection for this DB2 subsystem.

To have near-term history collection wait for DB2 tobecome active without issuing this WTOR, add theNTHDB2I=WAIT option to the OMPEOPTS member ofthe RKD2PAR data set.

KO2H0002W ssid NEAR-TERM HISTORY DATACOLLECTOR - DB2 subsystemALREADY BEING MONITORED BYMORE THAN n TASKS. REPLY 'GO',OR 'STOP'

ExplanationThe Near-Term History Data Collector has detectedthat the requested DB2 subsystem is already beingmonitored.

System actionThe system waits for a reply from the operator, thentakes the requested action.

User responseReview the specified options to ensure that they arecorrect.

KO2H0003W ssid NEAR-TERM HISTORY DATACOLLECTOR - aaaaaaaaaa DB2subsystem IS NOT VALID. REPLYANOTHER DB2 ID, OR REPLY STOP

ExplanationThe indicated DB2 is not valid on this system.aaaaaaaaaa = COLLECTION, if this is the DB2subsystem for which near-term history data is to becollected.

System actionThe system waits for a reply from the operator, andthen takes requested action.

User responsePerform one of the following actions:

• Wait for the DB2 subsystem to become active and donot give a reply. This WTOR message is automaticallycanceled when the DB2 becomes active.

• Reply with the ID of another DB2 subsystem to beused.

• Reply Stop to terminate the attempted datacollection for this DB2 subsystem.

KO2H0013E INVALID PARAMETER: parameter

ExplanationThe indicated parameter is not valid in the currentcontext.

System actionProcessing continues with the next recognizableparameter, if possible. The report request is rejected,and processing continues with the next reportstatement (if any).

User responseCorrect the parameter and rerun the report request. Ifthe parameter seems correct, check the adjacentparameters for correct syntax of the entire statement.

KO2H0450I NEAR-TERM HISTORY DATACOLLECTOR - INITIALIZINGCOMMON SERVICES


KO2H0452I NEAR-TERM HISTORY DATACOLLECTOR - TERMINATINGCOMMON SERVICES


KO2H0561I H2 DATA SET dsname STATUS n%FULL

ExplanationThis message supplies information about the status ofall VSAM data sets specified in the collection options


member. It shows whether the data set is activelystoring data, available to store data, or unavailable. Italso shows what percentage of the data set has beenused.


User responseNone.

KO2H0605I <V1> Waiting for initialization ofoutput writer task <V2> minutes

Explanation<V1> is the name of the DB2 subsystem. <V2> is thenumber of minutes.

This message might be issued every five minutes. TheNear Term History task is waiting for the output writertask to complete the initialization.

System actionThe output writer task might be pre-formatting theVSAM linear data sets or it might be processing theVSAM files.

User responseNone.

KO2H0901U NEAR-TERM HISTORY DATACOLLECTOR - UNABLE TO LOADBASE SERVICES



KO2H0902U NEAR-TERM HISTORY DATACOLLECTOR - CANNOT LOCATELOAD MODULE module.TERMINATING

ExplanationOMEGAMON XE for DB2 PE initialization processingcould not locate the indicated load module. Thismessage is usually caused by a failure to fully unloadthe OMEGAMON XE for DB2 PE product tape, or by afailure to migrate all modules to the runtime library.


User responseVerify that the load module is in the proper library andrestart OMEGAMON XE for DB2 PE.

KO2H0903U NEAR-TERM HISTORY DATACOLLECTOR - LOAD MODULEmodule IS AT THE WRONGRELEASE LEVEL. TERMINATING

ExplanationThe indicated OMEGAMON XE for DB2 PE load moduleis not at the correct release level. This message isusually caused by a failure to fully unload theOMEGAMON XE for DB2 PE product tape, or by afailure to migrate all modules to the runtime library.


User responsePlace a version of the load module that is at thecorrect release level in the proper library and restartOMEGAMON XE for DB2 PE.

KO2H0904U NEAR-TERM HISTORY - THENTHDB2I REAL-TIME OPTIONSPECIFIED IS NOT VALID.NTHDB2I=WTOR DEFAULT USED.(H2INIT)

ExplanationThe value specified with the NTHDB2I parameter inthe OMPEOPTS member of RKD2PAR is not valid. Validvalues are WTOR or WAIT.

System actionProcessing continues with the default value of WTOR.

User responseNone.

KO2H0950 OMEGAMON XE for DB2 PEINCOMPATIBLE WITH THISOPERATING SYSTEM.TERMINATING


ExplanationOMEGAMON XE for DB2 PE operates only in anMVS/XA or MVS/ESA environment.


User responseDo not start OMEGAMON XE for DB2 PE on a non-MVS/XA or non-MVS/ESA operating system. Also,ensure that your operating system and your loadlibrary are compatible (both XA or both ESA).

KO2H1305U NEAR-TERM HISTORY DATACOLLECTOR NOT LICENSED FORTHIS SYSTEM. TERMINATING

ExplanationOMEGAMON XE for DB2 PE operates in an MVS/ESAenvironment, but you have an MVS/XA version of theOMEGAMON XE for DB2 PE near-term historycomponent.


User responseUse an MVS/ESA version of the OMEGAMON XE forDB2 PE near-term history component and restart theNear-Term History Data Collector.

KO2H1306E Near-Term History Data CollectorREQUIRES APF LIBRARY.TERMINATING

ExplanationOMEGAMON XE for DB2 PE must run from an APF-authorized library.


User responseMove the OMEGAMON XE for DB2 PE load modules toan APF-authorized library and restart the Near-TermHistory Data Collector.

KO2H1316I Near-Term History Data CollectorHAS TERMINATED



User responseNone.

KO2H1350E NEAR-TERM HISTORY DATACOLLECTOR - PARM PROCESSORFAILED TO OBTAIN PARM WORKAREA

ExplanationAn internal program error occurred where one task didnot get passed from one area to another.


User responseContact DB2 support.

KO2H1351E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT LOCATERKD2PAR DATA SET

ExplanationData set RKD2PAR could not be located. The data setprobably does not exist.


User responseCheck the data set specified for ddname RKD2PAR andensure that it is allocated.

KO2H1352E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT OPENRKD2PAR DATA SET

ExplanationThe RKD2PAR data set could not be opened. The dataset probably does not exist.



User responseCheck the data set specified for ddname RKD2PAR andensure that it is allocated.

KO2H1353E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT LOCATERKD2PAR MEMBER SPECIFIED

ExplanationThe RKD2PAR member could not be located. Themember probably does not exist.


User responseCheck the data set specified for ddname RKD2PAR andensure that the member is allocated.

KO2H1354E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT ACQUIREENOUGH STORAGE TO READRKD2PAR DATA SET

ExplanationUnable to obtain sufficient storage to read theRKD2PAR data set.



KO2H1355E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT ACQUIREBUFFER STORAGE TO READRKD2PAR DATA SET

ExplanationUnable to acquire buffer storage to read the RKD2PARdata set.



KO2H1356E NEAR-TERM HISTORY DATACOLLECTOR - CANNOT ACQUIRESUFFICIENT STORAGE FOR PARMPROCESSING

ExplanationUnable to acquire sufficient storage for parameterprocessing.



KO2H1357E ssid NEAR-TERM HISTORY DATACOLLECTOR - WORD WITH NON-ALPHANUMERIC CHARACTER INTHE RKD2PAR RECORD: record

ExplanationA not valid word with a non-alphanumeric characterwas found in the RKD2PAR record.


User responseCheck the record following the message and correct itin the RKD2PAR member. For more information aboutrecord, see Configuration and Customization, chapter"Monitoring Profiles", section "Exploiting MonitoringProfiles".

KO2H1358E ssid NEAR-TERM HISTORY DATACOLLECTOR - INSUFFICIENTPARMS IN THIS RKD2PARRECORD: record

ExplanationInsufficient parameters for the keyword were found inthis RKD2PAR record.


User responseCheck the RKD2PAR record following this messageand correct it in the RKD2PAR member.


KO2H1359E ssid NEAR-TERM HISTORY DATACOLLECTOR - UNBALANCEDPARENTHESIS IN THIS RKD2PARRECORD: record

ExplanationUnbalanced parentheses for the keyword were foundin this RKD2PAR record.



KO2H1360E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID KEYWORD/PARAMETER IN THIS RKD2PARRECORD: record

ExplanationA keyword or parameter greater than 27 characters ora wrong keyword was found in this RKD2PAR record.


User responseCheck the RKD2PAR record following this messageand correct it in data set memberRKD2PAR(COPTssid).

KO2H1361E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALIDNONNUMERIC CHARACTER INTHIS RKD2PAR RECORD: record

ExplanationA not valid nonnumeric character for the keyword wasfound in this RKD2PAR record.



KO2H1362E ssid NEAR-TERM HISTORY DATACOLLECTOR - ALPHA CHARSINSTEAD OF NUMBER IN THISRKD2PAR RECORD: record

ExplanationAn alphanumeric character for the keyword was foundin this RKD2PAR record. The keyword requires anumeric value.



KO2H1363E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID NUMERICCHARACTER IN THIS RKD2PARRECORD: record

ExplanationA not valid numeric character for the keyword wasfound in this RKD2PAR record.



KO2H1364E ssid NEAR-TERM HISTORY DATACOLLECTOR - TOO MANY PARMSIN THIS RKD2PAR RECORD: record

ExplanationToo many parameters for the keyword were found inthis RKD2PAR record.



KO2H1365E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID PARM FOR


KEYWORD IN THIS RKD2PARRECORD: record

ExplanationA not valid parameter for the keyword was found inthis RKD2PAR record.



KO2H1366E ssid NEAR-TERM HISTORY DATACOLLECTOR - PARM OUT OFNUMERIC RANGE IN THISRKD2PAR RECORD: record

ExplanationA parameter out of numeric range was found in thisRKD2PAR record.



KO2H1367E ssid NEAR-TERM HISTORY DATACOLLECTOR - DETECTEDINSUFFICIENT PARMS IN THISRKD2PAR RECORD: record

ExplanationInsufficient parameters for the keyword were found inthis RKD2PAR record.



KO2H1369E ssid NEAR-TERM HISTORY DATACOLLECTOR - KEYWORD INVOKEDTWICE IN THIS RKD2PARRECORD: record

ExplanationA keyword was invoked twice in this RKD2PAR record.



KO2H1370E ssid NEAR-TERM HISTORY DATACOLLECTOR - READ ERROR FROMRKD2PAR DATA SET. SYNTAXMESSAGE FOLLOWS:

ExplanationAn error occurred while reading the RKD2PAR data set.


User responseCheck the RKD2PAR data set. If a partitioned data setis used, ensure that the member name is specified.

KO2H1375E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALIDPARAMETER FOR KEYWORDkeyword

ExplanationA not valid parameter for the DSNZPARM keyword wasfound. Valid options are YES and NO.


User responseCheck the RKD2PAR member and ensure that theDSNZPARM option is specified correctly.

KO2H1376I ssid NEAR-TERM HISTORY DATACOLLECTOR - ONLY ONE DATASETNAME ALLOWED WITH@DATE@TIME OR GDG(+1)

ExplanationMore than one specification of a data set was found inparameter SEQDATASET in RKD2PAR(COPTcccc). Ifthe variables @DATE and @TIME are used in the


specification of a data set name, or if a GenerationData Group (GDG) name is specified, only a single dataset name is allowed.


User responseCheck and correct the SEQDATASET parameter value.

KO2H1377I ssid NEAR-TERM HISTORY DATACOLLECTOR - MAX GDG LENGTHIS 35 BYTES

ExplanationA GDG name with invalid length was found.


User responseSpecify a GDG name with a length of up to 35 bytes.

KO2H1378I ssid NEAR-TERM HISTORY DATACOLLECTOR - GDG SPEC IS NOTCOMPATIBLE WITH @DATE@TIMEVARIABLES

ExplanationThe use of variables @DATE and @TIME is not allowedin the specification of a Generation Data Group (GDG)data set name.


User responseCorrect the data set name in the SEQDATASETparameter in RKD2PAR(COPTcccc).

KO2H1379I ssid NEAR-TERM HISTORY DATACOLLECTOR - @DATE REQUIRES@TIME TO ASSURE UNIQUE DATASET NAMES

ExplanationEither variable @DATE or @TIME was found in thespecification of a data set name in parameterSEQDATASET in RKD2PAR(COPTcccc). However, to

ensure a unique data set name, both variables must beused in the specification.


User responseCheck and correct the SEQDATASET parameter value.

KO2H1380E ssid NEAR-TERM HISTORY DATACOLLECTOR - NOT USING ANYNEW PARMS FROM RKD2PARMEMBER

ExplanationAn error was detected. No further parameters from theRKD2PAR member will be processed.


User responseCheck the RKD2PAR member and correct the error.

KO2H1381I ssid NEAR-TERM HISTORY DATACOLLECTOR - DETECTED EMPTYRKD2PAR INPUT MEMBER ORDATA SET

ExplanationThe parameter data set is empty.


User responseRebuild the runtime environment by using theConfiguration Tool (formerly ICAT) to restore the dataset.

KO2H1382I ssid NEAR-TERM HISTORY DATACOLLECTOR - USED DEFAULTINTERVAL(15) TO EVALUATEMAXHOURS PARAMETER

ExplanationThe default collection interval is used to calculate themaximum number of hours that the Near-Term HistoryData Collector can collect data.



User responseNone.

KO2H1383I ssid NEAR-TERM HISTORY DATACOLLECTOR - SPACE UNITS MUSTBE SPECIFIED AS "CYL" OR "TRK"

ExplanationAn invalid keyword for the specification of space unitswas found.


User responseNone.

KO2H1384I ssid NEAR-TERM HISTORY DATACOLLECTOR - ALLOCATION SPACEAMOUNT INVALID

ExplanationThe SPACE parameter in RKD2PAR(COPTcccc)contains a wrong value for the primary or secondaryallocation, or both.


User responseCheck and correct the SPACE parameter value.

KO2H1391E ssid NEAR-TERM HISTORY DATACOLLECTOR - CANNOT LOCATETHE PROCESSING ROUTINE FORKEYWORD n

ExplanationUnable to locate the processing routine for theindicated keyword.



KO2H1392E ssid NEAR-TERM HISTORY DATACOLLECTOR - CANNOT PROCESSFILTERING OPTIONS. WORK AREATOO SMALL

ExplanationThe filtering options cannot be processed because thework area is too small.



KO2H1393E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID TABLENAME/SYNONYM SPECIFIED INTHIS RKD2PAR RECORD:

ExplanationA not valid table name or synonym was specified.



KO2H1394E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID QUALIFIERIN THIS RKD2PAR RECORD:

ExplanationA not valid qualifier was specified.



KO2H1395E ssid NEAR-TERM HISTORY DATACOLLECTOR - INVALID FILTERINGVALUE IN THIS RKD2PARRECORD:


ExplanationA not valid filtering value was specified.



KO2H1399E ssid NEAR-TERM HISTORY DATACOLLECTOR - REQUIREDKEYWORD DB2SYS IS NOTSPECIFIED

ExplanationThe DB2SYS keyword is not specified. This keyword isrequired for the Near-Term History Data Collector, datasummarization, and data extraction if LOAD(NO) isspecified.


User responseSpecify the required keyword DB2SYS. Resubmit therequest.

KO2H1400I ssid NEAR-TERM HISTORY DATACOLLECTOR - THE MESSAGENUMBER message-id IS NOTDEFINED

ExplanationThe system attempted to write a message whileparsing RKD2PAR(COPTcccc), but could not find theindicated message-id.



KO2H1401E ssid NEAR-TERM HISTORY DATACOLLECTOR - SORT OR SCANOPTION IS SPECIFIED, BUT NOTACCOUNTING CLASS

ExplanationSORT or SCAN data was requested, but accountingdata is not being collected.


User responseCheck the specified keywords and make the necessarychanges. Resubmit the request.

KO2H1402E ssid NEAR-TERM HISTORY DATACOLLECTOR - H2DATASET MUSTBE SPECIFIED IF VSAM WRITEOPTION SELECTED

ExplanationVSAM was selected as the output destination, but thekeyword H2DATASET was not specified.



KO2H1403E ssid NEAR-TERM HISTORY DATACOLLECTOR - version-dependenttext

ExplanationVersion 3: version-dependent text is WRITEOPTIONKEYWORD VALUE MUST BE VSAM: A wrong value forthe WRITEOPTION keyword was specified.

Version 4: version-dependent text is WRITEOPTIONKEYWORD VALUE VSAM MISSING: The indicatedkeyword value is missing.


User responseCheck the indicated keyword values and make thenecessary changes. Resubmit the request.

KO2H1404I ssid NEAR-TERM HISTORY DATACOLLECTOR --WRITEOPTION(NONE) SPECIFIED,


BUT NO STATISTICS DATACOLLECTED

ExplanationWRITEOPTION(NONE) was specified, but statisticsdata was not being collected.



KO2H1405W ssid NEAR-TERM HISTORY DATACOLLECTOR - KEYWORDSDYNAMICSQL/LOCKCONT/LOCKSUSP IGNORED. version-dependent text

ExplanationVersion 3: version-dependent text is (WRITEOPTIONNOT VSAM): The keywords DYNAMICSQL, LOCKCONT,and LOCKSUSP are only valid withWRITEOPTION(VSAM).

Version 4: version-dependent text is (WRITEOPTIONWITHOUT VSAM): The keywords DYNAMICSQL,LOCKCONT, and LOCKSUSP are only valid withWRITEOPTION(VSAM) or WRITEOPTION(VSAM,SEQ).

System actionThe Near-Term History Data Collector terminates.

User responseNone.

KO2H1406W ssid NEAR-TERM HISTORY DATACOLLECTOR - KEYWORD n ISOBSOLETE AND WAS IGNORED

ExplanationNone.


User responseNone.

KO2H1407E ssid NEAR-TERM HISTORY DATACOLLECTOR - THRDDATASETMUST BE SPECIFIED IF THVSAMWRITE OPTION SELECTED

ExplanationIn the COPT member for DB2 subsystem ssid,WRITEOPTION(THVSAM) has been specified but noTHRDDATASET name prefix has been specified.

System actionHistory collection is not started for the DB2 subsystemssid.

User responseEither add the THRDDATASET name prefix if you wantto collect Thread History, or remove the THVSAM writeoption if you do not want to collect Thread History.

KO2H1408W ssid NEAR-TERM HISTORY DATACOLLECTOR - Function forkeyword keyword not yetimplemented, option set to NO.

ExplanationIn the COPT member for DB2 subsystem ssid, aThread History collection keyword keyword has beenspecified which is not yet implemented in the ThreadHistory collector.

System actionThe keyword keyword is ignored and processingcontinues.

User responseThe keyword keyword can be removed fromrhilev.RKD2PAR(COPTssid) member to prevent themessage from appearing.

KO2H1409E ssid NEAR-TERM HISTORY DATACOLLECTOR - THRDDATASET musthave * in name.

ExplanationIn the COPT member for DB2 subsystem ssid, theTHRDDATASET does not contain an asterisk (*). TheTHRDDATASET keyword specifies a prefix for thedataset names used by Thread History. TheTHRDLOG(nn) parameter specifies the number ofthread history data sets. The asterisk (*) after theprefix is substituted with a four digit number startingwith 0001 up to the number specified in THRDLOG.


System actionHistory collection is not started for the DB2 subsystemssid.

User responseCorrect the THRDDATASET parameter to include anasterisk (*) at the end of the prefix.

KO2H1413E xxxx NEAR-TERM HISTORY DATACOLLECTOR - At least one of theAnomaly Detection Use keys mustbe Y

ExplanationAnomaly detection uses the Thread Identity fields forgrouping metrics. At least one key must be specifiedfor subsystem xxxx.

System actionNear term history and anomaly detection are notstarted.

User responseCorrect the anomaly detection control cards forCOPTxxxx.

KO2I - D5API Framework messages

KO2I return codesKO2I messages might be accompanied by the following return codes:Return code

00000000

Operation completed successfully00000004

Error in collector routine00000008



Error detected by collector module KO2ACONB00000020

Error detected by agent module KD5ATC0000000024

Agent module KD5ATC00 timed out or abended00000028

Agent module KD5ATC00 detected internal DCST table was not initialized

KO2I reason codesKO2I messages might be accompanied by the following reason codes:Reason code

00000000

Operation completed successfully00000004

Invalid call type in D5API control structure00000008

Invalid eyecatcher in D5APIUSE structure


00000012Invalid D5APIUSE pointer in DAPICOMM structure

00000016Collector address space is not active

00000020Common collector registry entry not found

00000024Common collector registry not found

00000028Common collector registry entry eyecatcher is invalid

00000032D5APIUSE structure pointer in registry entry is zero

00000036Agent attempt to connect to collector address space timed out

00000040Agent attempt to collect data from collector timed out. Will retry

00000048While connecting to the collector address space for a given DB2, the agent detected the DB2subsystem was inactive.

00000052Agent detected the collector address space common collector component (COMMCOLL) is inactive

00000056Agent detected the collector address space common collector component (COMMCOLL) is inactive

00000060Agent could not locate the ASCB address for the collector address space

00000064Agent data collect call was issued for an unsuccessful connection

00000072Agent data collect call occurred while connection was being disconnected

00000076Common collector detected an invalid table name

00000080Agent timed out attempting to disconnect from the collector address space

00000084Agent detected that the common collector registry was not initialized

00000092Agent could not locate the DAPICOMM structure for a given connection

00000104Agent encountered an abend handling a connect, collect, or disconnect request

00000108Agent detected that a connection to the collector address space already existed for a given DB2subsystem

00000124Common collector detected that the subtask to process IFI requests for a given DB2 subsystem wasterminated

00000128Common collector routine KO2AOMBB could not be loaded

00000132Common collector cannot monitor a given DB2 subsystem. The PESERVER instance for it may nothave started successfully, or it was stopped.


00000136Agent timed out or encountered a problem handling a connection to the collector address space

00000140Agent detected there were no free DAPICOMM structures for handling a connection request

00000144Agent detected the internal DCST table was not initialized

00000152Agent routine LOCDAPI routine abended and recovered

00000156Agent routine GETDAPI routine abended and recovered

KO2I0100I D5API COLLECTORINITIALIZATION IN PROGRESS

ExplanationThe D5API Collector is currently being initialized.

System actionNone.

User responseNone.

KO2I0101I D5API COLLECTORINITIALIZATION COMPLETE

ExplanationThe D5API Collector has been successfully initialized.

System actionNone.

User responseNone.

KO2I0102I D5API COLLECTOR MODIFYCOMMAND IN PROGRESS

ExplanationThe D5API Collector is processing the requestedcommand.

System actionBegins command processing.

User responseNone.

KO2I0103I FORCE STOP REQUESTACKNOWLEDGED

ExplanationA MODIFY command has been issued to force-stop theOMEGAMON XE for DB2 PE address space.

System actionThe OMEGAMON XE for DB2 PE address space isforcibly terminated.

User responseVerify that the OMEGAMON XE for DB2 PE addressspace has terminated.

KO2I0104I D5API COLLECTOR STOPPROCESSING IN PROGRESS

ExplanationA Stop command has been issued to terminate theD5API Collector in the OMEGAMON XE for DB2 PEaddress space.

System actionThe D5API Collector is terminated.

User responseVerify that the D5API Collector has terminated.

KO2I0105U D5API ABEND ACCESSINGDAPICOMM

ExplanationThe D5API Collector has abnormally terminated.

System actionAn SVC dump is scheduled.



KO2I0553E OINT Jobstep Program:pppppppp. OMPE Subsystemrequired.

ExplanationProgram name 'pppppppp' is the name specified onthe EXEC statement of the STC JCL. OMEGAMON XEfor DB2 PE releases version 4.2.0 and higher requirethat PGM=KO2ZTOBP is specified on the EXECstatement of the STC JCL statement.

System actionStarted task terminates.

User responseSpecify PGM=KO2ZTOPB on the EXEC statement of theSTC JCL statement.

KO2I0554E HINT Jobstep Program:pppppppp. OMPE Subsystemrequired.

ExplanationProgram name 'pppppppp' is the name specified onthe EXEC statement of the STC JCL. OMEGAMON XEfor DB2 PE releases version 4.2.0 and higher requirethat PGM=KO2ZTOBP is specified on the EXECstatement of the STC JCL statement.

System actionStarted task terminates.

User responseSpecify PGM=KO2ZTOPB on the EXEC statement of theSTC JCL statement.

KO2I0107E D5API FAILED TO ATTACH ACONNECTION TO DB2 %%%% ONBEHALF OF AGENT %%%%%%%%

ExplanationThe D5API common collector failed to attach a DB2connection as requested by the XE agent.

System actionThe XE agent Connect call is rejected.


KO2I0108E D5API COLLECTOR DETACH %%%ACON% FAILED

ExplanationThe D5API Collector could not detach the Connect/Collect subtask that was attached on behalf of anAgent address space.

System actionThe D5API Collector resumes waiting for additionalAgent address space requests.


KO2I0109E D5API COLLECTOR ALREADYACTIVE IN D2 INSTANCE %%%%%%%%. START COMMCOLLREJECTED

ExplanationThe D5API Collector is currently active in the D2instance and cannot be started.

System actionThe D5API Collector is not restarted in the current D2instance.

User responseStop the previously started OMEGAMON Collector,then reissue the START COMMCOLL Server command.

KO2I0109I D5API COLLECTOR DETACH %%%ACON% SUCCESSFUL

ExplanationThe D5API Collector successfully detached theConnect/Collect subtask.

System actionNone.

User responseNone.

KO2I0110I D5API COLLECTOR STATUSDISPLAY


ExplanationThe D5API Collector is currently processing therequested MODIFY command.

System actionThe MODIFY command is processed.

User responseNone.

KO2I0111I D5API COLLECTOR REGISTRYDISPLAY



User responseNone.

KO2I0112I D5API COLLECTOR TRACEALLDISPLAY



User responseNone.

KO2I0113E D5API COLLECTOR TRACE TABLENOT INITIALIZED

ExplanationThe trace table for the D5API Collector is notinitialized.

System actionThe TRACEALL Modify command has failed.


KO2I0114I NO D5API COLLECTOR TRACEDATA TO DISPLAY

ExplanationNo trace data is available for display at the currenttime.

System actionNone.

User responseNone.

KO2I0115I D5API STIMER WAIT VALUESUCCESSFULLY CHANGED

ExplanationThe D5API Collector collect timer wait value has beensuccessfully changed.

System actionNone.

User responseNone.

KO2I0116E D5API INVALID STIMER WAITVALUE SUPPLIED

ExplanationThe D5API Collector collect timer wait value in thecommand is invalid.

System actionThe command is rejected.

User responseSpecify a valid wait value in the form of hhmmssth.

KO2I0117I D5API COLLECTOR RESMGRDISPLAY




User responseNone.

KO2I0118I D5API NO RESMGR ENTRIESDEFINED

ExplanationA D5API Collector command was issued to displayresource manager entries, but no entries were found.


User responseNone.

KO2I0119I D5API COLLECTOR TERMINATIONIN PROGRESS

ExplanationThe D5API Collector is terminating.

System actionNone.

User responseNone.

KO2I0120E D5API CONTROL TABLE VALIDITYCHECK FAILED

ExplanationThe D5API Collector could not validate the acronymname in the D5API control table.

System actionD5API Collector termination continues.


KO2I0121E PC TABLE STORAGE RELEASEFAILED

ExplanationThe D5API Collector could not release the PC tablecommon storage structure.

System actionD5API Collector termination continues.


KO2I0121I D5API COLLECTOR WAITING FORSUBTASKS TO EXIT

ExplanationA MODIFY command has been issued to stop theD5API Collector. Stop processing is waiting for allsubtasks to end before terminating.

System actionThe D5API Collector waits for the subtasks to end.

User responseNone.

KO2I0122I RESMGR DEFERRED RESOURCECLEANUP COMPLETE

ExplanationThe D5API Collector successfully released commonECSA resources.

System actionNone.

User responseNone.

KO2I0122W D5API COLLECTOR FORCIBLYTERMINATING

ExplanationA MODIFY command was previously issued to stop theD5API Collector. The timer interval used to wait for allsubtasks to end has been exceeded, causingtermination.

System actionThe D5API Collector is forcibly terminated.



KO2I0123I D5API REGISTRATION ENTRYSUCCESSFULLY RELEASED

ExplanationThe D5API Collector instance registration entry hasbeen successfully released.

System actionNone.

User responseNone.

KO2I0124I D5API COLLECTOR TERMINATIONCOMPLETE

ExplanationThe D5API Collector has terminated.

System actionNone.

User responseNone.

KO2I0127U D5API ECSA STRUCTURESGETMAIN FAILED

ExplanationError occurred while getting ECSA storage for commoncollector control structures.

System actionThe common collector is terminated. Dump isgenerated.


KO2I0128U D5API ECSA STRUCTURESGETMAIN FAILED

ExplanationThe D5API Collector could not obtain ECSA virtualstorage for the D5APIUSE structure.

System actionThe D5API Collector task terminates with abend code3100.


KO2I0129U D5API REGISTRATION ENTRYCREATE FAILED

ExplanationThe D5API Collector could not create the instanceregistration table entry.

System actionThe D5API Collector task abnormally terminates.


KO2I0130I D5API REGISTRATION ENTRYSUCCESSFULLY REBUILT

ExplanationThe D5API Collector successfully rebuilt theregistration table entry for this instance ofOMEGAMON XE for DB2 PE.

System actionNone.

User responseNone.

KO2I0131U D5API REGISTRATION TOKENDELETE FAILED

ExplanationThe D5API Collector could not delete the system-levelregistration name/token pair.

System actionThe D5API Collector task abnormally terminates.


KO2I0133U INTERNAL TRACE RECORDINGTERMINATED DUE TO ABEND


ExplanationThe D5API internal trace processing has abnormallyterminated.

System actionTrace processing stops collecting internal trace data.

User responseMessage KO2I0143I is issued indicating that recoveryis successful. Contact IBM support if recovery is notsuccessful.

KO2I0133W INTERNAL TRACE RECORDINGPREVIOUSLY TERMINATED DUETO ABEND. NO TRACE DATA TODISPLAY

ExplanationA command was issued to display internal trace data,but no trace data is available to display because traceprocessing was previously terminated because of anabnormal end.


User responseShut down and restart OMEGAMON XE for DB2 PE. Ifthe problem persists, contact IBM support.

KO2I0134I D5API REGISTRATION ENTRYSUCCESSFULLY CREATED

ExplanationThe D5API Collector successfully created theregistration table entry for this instance ofOMEGAMON XE for DB2 PE.

System actionNone.

User responseNone.

KO2I0136I D5API TASK-LEVEL TOKENSUCCESSFULLY CREATED

ExplanationThe D5API Collector successfully re-created the task-level name/token pair for Collect/Connect processfunctions.

System actionNone.

User responseNone.

KO2I0137E D5API RESMGR INITIALIZATIONFAILED

ExplanationThe D5API Collector could not initialize the resourcemanager table.

System actionThe D5API Collector abnormally terminates.


KO2I0138I D5API RESMGR INITIALIZATIONCOMPLETE

ExplanationThe D5API Collector successfully initialized theresource manager table.

System actionNone.

User responseNone.

KO2I0140E INVALID MODIFY COMMANDRECEIVED

ExplanationA not valid D5API Collector command has beenentered.



User responseSpecify a valid command.

KO2I0140I D5API COLLECTOR MODIFYCOMMAND COMPLETED

ExplanationA D5API Collector command has been successfullyexecuted.

System actionThe command is executed.

User responseNone.

KO2I0141I D5API COLLECTOR TRACE SET TO<V1>

ExplanationThe D5API Collector has been started or modified withone of the following trace processing parameters(<V1>):

• TRACE=NO - No trace informational messages will bedisplayed in the OMEGAMON job log and Agentaddress space log.

• TRACE=YES - Trace informational messages will bedisplayed in the OMEGAMON job log and Agentaddress space log.

• TRACE=YES,DATA - Trace informational messageswill be displayed in the OMEGAMON job log andAgent address space log, including collected DB2table data.

System actionThe D5API Collector sets the appropriate traceenvironment.

User responseNone.

KO2I0142I D5API ATTACHED A CONNECTIONTO DB2 DDDD ON BE HALF OFAGENT $$$$$$$$

ExplanationThe D5API common collector successfully attached aDB2 connection as requested by the XE agent.

System actionThe D5API common collector monitors the DB2connection for XE agent data collection requests.

User responseNone.

KO2I0143I D5API COLLECTOR ABENDRECOVERY SUCCESSFUL.PROCESSING CONTINUES

ExplanationA D5API Collector component has been deactivatedbecause of an abnormal termination.

System actionProcessing continues without the failed component.


KO2I0144I D5API DB2 CONNECTIONSDISPLAY

ExplanationA D5API Collector command was issued to displayDB2 Agent connections.


User responseNone.

KO2I0144W D5API NO ACTIVE DB2 AGENTCONNECTIONS FOUND

ExplanationA D5API Collector command was issued to displayDB2 Agent connections, but no active DB2 Agentconnections were found.

System actionNone.

User responseNone.


KO2I0147U MODIFY COMMAND ABNORMALLYTERMINATED

ExplanationThe requested MODIFY command has abnormallyterminated.

System actionThe D5API Collector resumes processing.


KO2I0148I D5API USING REGISTRATIONTABLE %%%%%%%%

ExplanationThe D5API Collector successfully retrieved thepersistent system-level name/token pair that is usedto anchor the registration table address.

System actionNone.

User responseNone.

KO2I0149I D5API PTF BUILD IS <V1> <V2>

ExplanationThis message displays the OMEGAMON XE for DB2 PEassembly date (<V1>) and time (<V2>) values.

System actionNone.

User responseNone.

KO2I0150E D5API UNKNOWN POST CODERECEIVED ON BEHALF OF AGENT<V1> - DAPIPSTC=<V2>CALL=<V3>

ExplanationThe D5API Collector received an unknown post code.

• <V1> is the name of the agent.

• <V2> is the D2 post code in the DAPIPSTC field. Thisfield identifies the unknown post code received.Valid post codes are:

– 00000001 - Discover action– 00000002 - Connect action– 00000003 - Collect action– 00000005 - Disconnect action

.• <V3> is the type of call being processed. This fieldidentifies the invalid processing request. Validprocessing requests are:

– DSV - Discover call– CON - Connect call– COL - Collect call– DIS - Disconnect call

System actionThe Agent Connect/Collect call is not processed.


KO2I0151W D5API COLLECTOR FAILED TOLOCATE DB2 ssid ON BEHALF OFAGENT %%%%%%%%

ExplanationThe OMEGAMON XE D5API common collector couldnot connect to the specified DB2 ssid as requested byAgent %%%%%%%%.

System actionThe Agent Connect call is terminated.

User responseVerify that the DB2 subsystem ssid is started andfunctioning properly.

KO2I0152U D5API COLLECTOR DETECTED DB2ssid IS NOT OPERATIONAL ONTHIS SYSTEM

ExplanationThe OMEGAMON XE D5API common collector couldnot connect to the indicated DB2 subsystem.



User responseThis condition occurs when the target DB2 subsystemnormally or abnormally terminates while the D5APIConnect call is in progress. Verify that the indicatedDB2 subsystem is started and functioning properly.

KO2I0152W D5API UNABLE TO LOCATE AGENTADDRESS SPACE

ExplanationThe D5API Collector Connect/Collect task could notdetermine the status of the Agent address space.

System actionThe D5API Collector Connect/Collect task isterminated.

User responseDetermine why the Agent address space terminated,and take appropriate action.

KO2I0153I D5API COLLECTOR WAITING FORAGENT %%%%%%%%CONNECTION REQUESTS

ExplanationAn OMEGAMON XE for DB2 PE agent caused the DB2collection driver module to be attached.

System actionWaiting for Agent connection requests.

User responseNone.

KO2I0154I D5API COLLECTOR ISCONNECTING TO DB2 %%%% ONBEHALF OF AGENT %%%%%%%%.

ExplanationAn OMEGAMON XE for DB2 PE agent caused the DB2collection driver module to connect to the specifiedDB2 subsystem to collect data.

System actionThe connection request is processed.

User responseNone.

KO2I0155I D5API COLLECTORSUCCESSFULLY COLLECTED DATAFROM DB2 %%%% ON BEHALF OFAGENT %%%%%%%%

ExplanationA DB2 collection request was issued by anOMEGAMON XE for DB2 PE agent, and data wassuccessfully collected from the indicated DB2subsystem.

System actionThe requested data is collected.

User responseNone.

KO2I0156I D5API COLLECTOR FOUND NODATA TO COLLECT FROM DB2 ssidON BEHALF OF AGENT %%%%%%%%

ExplanationThe OMEGAMON XE D5API common collector foundno data to collect from the specified DB2 subsystemssid as requested by Agent %%%%%%%%.

System actionThe Agent is notified that no data has been returned.

User responseVerify that the DB2 subsystem ssid is started andfunctioning properly.

KO2I0157I D5API COLLECTORDISCONNECTED FROM DB2 %%%% ON BEHALF OF AGENT %%%%%%%%

ExplanationAn OMEGAMON XE for DB2 PE shutdown request wasissued and the active DB2 Agent connection wasterminated.

System actionThe active DB2 connection is terminated.

User responseNone.


KO2I0158W D5API COLLECTOR UNABLE TOLOCATE DB2 %%%% ON BEHALFOF AGENT %%%%%%%%

ExplanationThe D5API Collector could not locate the indicatedDB2 subsystem.

System actionThe connection request is rejected.

User responseSpecify a valid DB2 SSID and check that the DB2 bindfor the Agent's plan has been run.

KO2I0159W D5API COLLECTOR UNABLE TOACCESS AGENT %%%%%%%%COMMUNICATION DATA AREA<DAPICOMM>

ExplanationThe D5API Collector tried to cross-memory post theAgent for completion of a Connect, Collect, orDisconnect call, but could not access the AgentDAPICOMM communication structure.

System actionThe D5API Collector unit of work associated with therequest is terminated.

User responseVerify that the Agent address space is still active in thesystem. If the Agent address space is not active in thesystem, restart it.

KO2I0160U COLLECTOR UNABLE TO LOCATEAGENT %%%%%%%% FORD5API CALL POST COMPLETION

ExplanationD5API could not locate the agent to complete theaction.

System actionThe common collector DB2 connection is terminated.

User responseNone.

KO2I0161W D5API COLLECTOR FORCIBLYTERMINATED DB2 DDDDCONNECTION ON BEHALF OFAGENT %%%%%%%%

ExplanationThe common collector DB2 connection is terminatedforcibly when receiving no response from thetermination request.

System actionThe D5API collector DB2 connection is terminated.

User responseNone.

KO2I0162U D5API COLLECTOR FAILED TOLOAD THE OMEGAMON BATCH APION BEHALF OF AGENT %%%%%%%%

ExplanationThe common collector could not load the required APIfor agent.

System actionThe common collector is terminated.


KO2I0163U AGENT %%%%%%%%DAPICOMM STRUCTURE FAILEDINTEGRITY CHECKS. DB2 %%%%CONNECTION TERMINATED

ExplanationD5API control structure internal error occurred for theDB2 connection.

System actionThe D5API collector DB2 connection is terminated.


KO2I0164I COLLECTOR RELEASE COUNTERTBL DB2 %%%% ON BEHALF OFAGENT %%%%%%%%.


ExplanationThe D5API collector released counter table when theD5API DB2 connection is terminated.

System actionStorage is released.

User responseNone.

KO2I0170U <Snnn> ABEND IN MODULE<prognm1> PERCOLATED TOD5API MODULE <prognm1>.

ExplanationAn abend <Snnn> occurred.

System actionAn SVC dump is scheduled.


KO2I0180U LOCAL DAPICOMM STORAGERELEASE ERROR

ExplanationThe XE Agent failed to release a local storagecommunication structure used to communicate withthe D5API common collector.

System actionNormal disconnect processing continues.


KO2I0181W D5API IS NOT ACTIVE IN D2=%%%%%%%% ADDRESS SPACE.CONNECT CALL FAILED FOR DB2%%%%

ExplanationThe D5API Collector is not active in the OMEGAMONXE for DB2 PE address space.

System actionThe Agent Connect call is rejected.

User responseVerify that the OMEGAMON XE for DB2 PE addressspace is active in the system. If not, restart it.

KO2I0182E FAILED TO LOCATE THE D2=%%%%%%%% ADDRESS SPACE

ExplanationThe OMEGAMON XE for DB2 PE address space is notactive in the system.



KO2I0183W D5API IS NOT ACTIVE IN D2 %%%%%%%% ADDRESS SPACE.COLLECT CALL FAILED FOR DB2 %%%%

ExplanationThe OMEGAMON XE D5API Agent collection functioncould not collect data from the specified D2 Serveraddress space.

System actionThe Agent Collect call is terminated.

User responseVerify that the D5API Collector component is active inthe D2 Server address space by issuing the followingSTATUS MODIFY command: FO2CI,COMMCOLL,STATUS. For STATUS=INACTIVE,stop the D5API Collector and restart it. To stop theD5API Collector, issue the following MODIFYcommand: F O2CI,F COMMCOLL,STOP. To restartthe D5API Collector, issue the following MODIFYcommand: F O2CI,F COMMCOLL,START. ReplaceO2CI with your D2 Server started task name.

KO2I0184E LOCASCB FAILED TO LOCATE THED2=%%%%%%%% ADDRESSSPACE





KO2I0185E CONTROL TABLE LOCATE ERRORD2=%%%%%%%%




KO2I0186E D5API PC ENVIRONMENT NOTINITIALIZED D2=%%%%%%%%

ExplanationThe OMEGAMON XE for DB2 PE address space has notyet initialized the cross-memory environment.



KO2I0186U DB2 %%%% CONNECTIONALREADY EXISTS IN OM %%%%%%%% - CONNECT CALLREJECTED

ExplanationThe D5API Connect call failed because a DB2connection already exists.

System actionThe Connect call is rejected.

User responseShut down and restart the Agent address space.

KO2I0187W D5API IS NOT ACTIVE IN D2NNNNNNNN ADDRESS SPACE.DISCOVER CALL FAILED

ExplanationThe OMEGAMON XE D5API Agent Discover functioncould not discover the status of active DB2 subsystemIDs known to the D2 Server address space.

System actionThe Agent Discover call is terminated.

User responseVerify that the D5API Collector component is active inthe D2 Server address space by issuing the followingSTATUS MODIFY command: F O2CI,FCOMMCOLL,STATUS. For STATUS=INACTIVE, stop theD5API Collector and restart it. To stop the D5APICollector, issue the following MODIFY command: FO2CI,F COMMCOLL,STOP. To restart the D5APICollector, issue the following MODIFY command: FO2CI,F COMMCOLL,START. Replace O2CI with yourD2 Server started task name.

KO2I0188E LOCASCB FAILED TO LOCATE THED2=%%%%%%%% ADDRESSSPACE


System actionThe Agent Disconnect call is rejected.


KO2I0189I AGENT %%%%%%%%ATTEMPTING CONNECTION TO %%%%%%%% VERSION Vnnn BY%%%%%%%% - DB2 %%%%.

ExplanationAn OMEGAMON XE for DB2 PE agent is attempting aconnection to the indicated Vnnn OMEGAMONcommon collector for the indicated DB2 system.

System actionThe agent is attempting a connection.


User responseNone.

KO2I0190W CONNECT TIME LIMIT EXCEEDED.CONNECT CALL FAILED

ExplanationThe OMEGAMON XE D5API Collector Agent connectionfunction exceeded the internally specified nineminutes connect time allowance.


User responseCheck the OMEGAMON collector job log orOMEGAMON XE for DB2 PE agent RKLVLOG forpossible causes.

KO2I0191W COLLECT TIME LIMIT EXCEEDED.COLLECT CALL FAILED

ExplanationThe OMEGAMON XE D5API Collector Agent datacollection function exceeded the internally specified30 seconds collect time interval.

System actionThe Agent Collect call is terminated

User responseIssue the F O2CI,F COMMCOLL,STIMER=hhmmssthMODIFY D2 Server command to change the defaultcollect time interval. O2CI is the D2 Server startedtask name and hhmmssth is used to specify a newcollect time interval. Example: F O2CI,FCOMMCOLL,STIMER=00050000 changes the collecttime interval to 50 seconds.

KO2I0192W DISCONNECT TIME LIMITEXCEEDED. DISCONNECT CALLFAILED.

KO2I0193I AGENT %%%%%%%%CONNECTED TO %%%%%%%% -DB2 %%%%

ExplanationThe OMEGAMON XE for DB2 PE agent successfullyconnected to the OMEGAMON common collector forthe indicated DB2 subsystem.

System actionThe agent Connect call succeeded.

User responseNone.

KO2I0194I AGENT %%%%%%%% FAILED TOCONNECT TO %%%%%%%% -DB2 %%%%

ExplanationThe OMEGAMON XE for DB2 PE agent failed to connectto the OMEGAMON common collector for the indicatedDB2 subsystem.

System actionThe agent Connect call failed.

User responseCheck the OMEGAMON collector job log orOMEGAMON XE for DB2 PE agent RKLVLOG forpossible causes.

KO2I0195I AGENT %%%%%%%%DISCONNECTED FROM %%%%%%%% - DB2 %%%%

ExplanationThe OMEGAMON XE for DB2 PE agent disconnectedfrom the OMEGAMON common collector for theindicated DB2 subsystem.

System actionThe agent is disconnected from the common collector.

User responseNone. It might be that the OMEGAMON commoncollector or DB2 system was recycled.

KO2I0200U UNABLE TO LOG COLLECTEDDATA. ZERO UAB ADDRESSSUPPLIED

ExplanationThe D5API Agent could not locate the User AgentBlock (UAB) supplied by the caller.

System actionLog data is not collected.



KO2I0201U UNABLE TO LOG COLLECTEDDATA. UAB FAILED VALIDITYCHECK

ExplanationThe D5API Agent could not validate the User AgentBlock (UAB) supplied by the caller.



KO2I0202U UNABLE TO LOG COLLECTEDDATA. UAB BUFFER OVERFLOW

ExplanationThe D5API Agent could not locate a User Agent Block(UAB) buffer required to log collected data.



KO2I0203U DAPICOMM STRUCTURE CELLELEMENT OBTAIN FAILURE

ExplanationThe D5API call could not obtain a communication datastructure that is required to communicate Connectcalls to the common collector.



KO2I0203W TASK TYPE RESMGRINITIALIZATION FAILED

ExplanationThe D5API Agent could not define a task type resourcemanager.

System actionProcessing continues without the resource manager.

User responseNone.

KO2I0204U LOCAL DAPICOMM STORAGEOBTAIN ERROR

ExplanationThe XE Agent could not obtain local storage for thecommunication structure that is required to perform aConnect call to the D5API common collector.

System actionThe XE agent Connect call is rejected.

User responseIncrease the XE agent address space region size andrestart the agent started task.

KO2I0205I DISCONNECT CALL ISSUED ONBEHALF OF AGENT BY D5API EOTRESOURCE MANAGER

ExplanationThe D5API Collector end-of-task resource managerdetected that the Agent did not release its connectioncontrol structure during termination processing.

System actionThe end-of-task resource manager releases the Agentconnection structure on behalf of the terminatingAgent address space.

User responseNone.

KO2I0205U UNABLE TO LOCATE COMMONCOLLECTOR REGISTRY ENTRY FOROM SERVER %%%%%%%%

ExplanationThe D5API call could not locate the common collectorregistry for the specified OMEGAMON Collector.


System actionThe Connect, Collect, or Disconnect call is terminated.

User responseVerify that the OMEGAMON Collector that the Agent istrying to communicate with is active in the system. If itis not active, start the OMEGAMON Collector.

KO2I0206U UNABLE TO VALIDITY-CHECKDAPICOMM STRUCTURE STATUSDUE TO QUEUE SCAN FAILURE

ExplanationThe D5API call could not locate the communicationdata structure that is required to process the commoncollector Collect or Disconnect call.

System actionThe Collect or Disconnect call is rejected.


KO2I0207U D5API CONTROL STRUCTURE FORD2 %%%%%%%% FAILEDINTEGRITY CHECKS. CONNECTCALL FAILED

ExplanationThe Agent program call (PC) routine could notsuccessfully reference processing information in theD5API Collector control structure.



KO2I0208U AGENT DAPICOMM STRUCTUREFAILED INTEGRITY CHECKS.CONNECT CALL FAILED

ExplanationThe Agent program call (PC) routine could notsuccessfully reference processing information in theDAPICOMM communication structure.



KO2I0209U AGENT COLLECT CALL FAILED.CONNECT CALL NOT PREVIOUSLYISSUED. COLLECT CALL FAILED

ExplanationThe Agent program call (PC) routine could not processthe Collect call because Connect was not previouslyissued.



KO2I0210W AGENT TERMINATING DB2 %%%% CONNECTION IN D2 %%%%%%%%

ExplanationThe Agent program call (PC) routine disconnected thespecified DB2 from the D5API Collector because theAgent issued a Connect call to the same DB2subsystem twice without a Disconnect call beingissued.

System actionThe connection to the specified DB2 is reestablished.

User responseNone.

KO2I0211W DAPICOMM STRUCTURE ACCESSFAILED FOR DB2 <ssid>RECOVERY SUCCESSFUL

ExplanationThe D5API agent disconnect function tried to storagerelease a previously freed ECSA DAPICOMM structure.

System actionThe error is ignored and the Disconnect call request issuccessfully processed.

User responseNone.


KO2I0212I AGENT SUCCESSFULLY RELEASEDDAPICOMM STRUCTURE FOR DB2ssid

ExplanationThe D5API agent disconnect function successfullystorage released the ECSA DAPICOMM structure.

System actionDisconnect call processing continues.

User responseNone.

KO2I0212U UNABLE TO LOCATE ACONNECTION TO DB2=ssid IN OMSERVER server-name - [COLLECT |DISCONNECT] CALL FAILED

ExplanationThe D5API call could not locate a connection for thespecified DB2 subsystem on the target OMEGAMONCollector.

System actionThe specified D5API call is terminated and error andreason codes are returned to the calling agent.


KO2I0213U UNABLE TO LOCATE SPECIFIEDDB2=%%%% SUBSYSTEM - %%%%%%%% CALL FAILED

ExplanationThe D5API Connect or Collect call failed because theDB2 subsystem was not found.

System actionThe Connect or Collect call is rejected.

User responseStart the specified DB2 subsystem.

KO2I0214U INVALID TABLE NAME SUPPLIEDBY AGENT %%%%%%%%TABLE=%%%%%%%% DB2=%%%%

ExplanationThe D5API common collector detected that the tablename supplied by the XE agent is invalid.

System actionThe XE agent collect call is rejected.


KO2I0215U IFI SUBTASK IS INACTIVE FORAGENT <V1>, TABLE=<V2>,DB2=<ssid>

ExplanationNone.

System actionNone.

User responseNone.

KO2I0929E UNSUPPORTED IMS VERSION<V1>

ExplanationAn active thread originated from an IMS version that isnot supported by the product.

• <V1> is the unsupported IMS version.

System actionIMS-specific information, such as transaction ID, isdisplayed as N/A.

User responseRequest a product upgrade for support of IMS version<V1>.

KO2I1000W Connection to OMPE Serverssssssss Failed. Subsystem db2Return=return Reason=reason.Retrying in nn Seconds)

ExplanationThe XE Agent's attempt to connect to the OMEGAMONfor Db2 PE Collector failed.

• Return= indicates the return code. For moreinformation, see “KO2I return codes” on page 328.


• Reason= indicates the reason code. For moreinformation, see “KO2I reason codes” on page 328.

System actionThe Agent will keep retrying to connect to the OMPEServer until it is started.

User responseStart the OMPE Server.

KO2I1001W Connection to OMPE Serverssssssss Lost. Return=returnReason=reasonCollectReturn=return2

ExplanationThe XE Agent has detected that the OMPE Server is nolonger running.



CollectReturn

00000000Collection completed successfully

00000004The number of rows returned exceeded thecapacity of the agent.

00000008An abend occurred in the collection routine.

System actionNone.

User responseRestart the OMPE Server.

KO2I1002E Connection to OMPE Serverssssssss Failed. Subsystem db2Return=return Reason=reason. NotRetrying

ExplanationThe XE Agent has detected that the OMPE Server is notconfigured for this DB2 subsystem and cannot monitorit.



System actionThe Agent does not try to reconnect to the OMPEServer until it is configured and restarted.

User responseIf you want to monitor the indicated DB2 subsystem,reconfigure and restart the OMPE Server and theOMEGAMON XE Agent . Otherwise, remove thissubsystem from Auto Discovery.

KO2I9999I <V1>

ExplanationAn internal error has occurred. <V1> providesinformation necessary for debugging andtroubleshooting.

User responseContact IBM Software Support.

KO2M - ISPF messagesKO2M001 OMEGAMON XE for DB2 PE VTAM

session ended successfully

ExplanationThe task "View online DB2 activity - Classic Interface"was successfully ended by a user action.

System actionNone.

User responseNone.

KO2M002 OMEGAMON XE for DB2 PE VTAMsession ended. Return code rc

KO2M003 RETURN PF key has been modified


ExplanationThe immediate return function was successfullymodified by a user action.

System actionNone.

User responseNone.

KO2M004 Data set name is not available

KO2M005 Module name is not available indsname

ExplanationEXEC FPEJINIT could not locate the indicated modulein the indicated data set.

System actionThe start process terminated.

User responseEnsure that the indicated library is accessible.

KO2O - VTAM Display Logic messagesKO2O0450I INITIALIZING COMMON

SERVICES


KO2O0452I TERMINATING COMMONSERVICES


KO2O0500E Near-Term History Data Collector -OPEN VSAM DATA SET FAILEDWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while an OPEN request was issuedto the VSAM data set. This problem could be caused byan I/O error on the VSAM data set.

System actionProcessing continues, but the data extractor cannotextract any performance data from GTF or SMF.

User responseIf the error code does not indicate an I/O error, contactIBM support.

KO2O0501E Near-Term History Data Collector -CLOSE VSAM DATA SET FAILEDWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while a CLOSE was issued to theVSAM data set. This problem could be caused by anI/O error on the VSAM data set.

System actionProcessing continues, but the VSAM data set was notclosed.


KO2O0502E Near-Term History Data Collector -SHOWCB/GENCB RPL FAILEDWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while SHOWCB/GENCB RPL wasissued against the VSAM data set. This problem couldbe caused by an I/O error on the VSAM data set.



KO2O0503E Near-Term History Data Collector -SHOWCB/GENCB EXLST FAILED


WITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while SHOWCB/GENCB EXLST wasissued against the VSAM data set. This problem couldbe caused by an I/O error on the VSAM data set.



KO2O0504E Near-Term History Data Collector -SHOWCB/GENCB ACB FAILEDWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while SHOWCB/GENCB ACB wasissued against the VSAM data set. This problem couldbe caused by an I/O error on the VSAM data set.

System actionProcessing continues, but data extractor cannotextract any performance data from GTF or SMF.


KO2O0505E Near-Term History Data Collector -VSAM PUT FAILED WITH RETURNCODE=rc, REASON CODE=rs

ExplanationAn error occurred while a PUT was issued to the VSAMdata set. This problem could be caused by an I/O erroron the VSAM data set.



KO2O0507E Near-Term History Data Collector -VSAM LOGICAL I/O ERROR WITHRETURN CODE=rc, REASONCODE=rs

ExplanationA logical I/O error occurred while a PUT was issued tothe VSAM data set. This problem could be caused byan I/O error on the VSAM data set.



KO2O0602W %%%% Trace data lost - too manybuffers in use.

Explanation%%%% is the name of the DB2 subsystem. DB2produces IFCID records faster than the Near-TermHistory Collector can process. Currently, more than 15buffers are used. The collection of IFCID records issuspended until 15 or less buffers are used.

System actionRecords are skipped until the Near-Term HistoryCollector can reduce the backlog of records to beprocessed.

User responseYou can solve the problem by doing one or more of thefollowing actions.

Note:

Use the Configuration Tool (previously called ICAT,panel KD261P8 and KD261PB) to modify theBUFSIZE-, NEGSQL-, SCAN-, SORT-, DYNAMICSQL-and POSTPCT- parameters below.

If you do not use the Configuration Tool to record andupdate the parameter library, changes might bereversed the next time you are using it.

1. Increase the buffer size by setting its value to2048. Try different values and evaluate the results.

By default, the buffer size (BUFSIZE) is 1024. Thisvalue might be too small for high volumeproduction systems. The upper limit for the buffersize is the maximum value for a -START TRACE


command. For more information, see the DB2commands reference.

For the OMEGAMON Near-Term History collector,the recommended value for the buffer size is 2048.

2. Reduce the number of IFCIDs to be written to theOPx by using the following settings:NEGSQL(NO)

Use this setting to not collect return codes onSQL events.

Affected IFCIDs: 58, 59, 60, 61, 62, 64, 65, 66,233.

If Near-Term History data is not collected tosequential files, there is no reason to collectthis data.

Near-Term History data is not externalized bythe real time product. However, it can beexternalized by batch reporting if it is collectedto sequential files.

SCAN(NO)Use this setting to not collect SCAN data.

Affected IFCIDs: 15, 16, 17, 18.

SORT(NO)Use this setting to not collect SORT data.

Affected IFCIDs 95, 96.

DYNAMICSQL(NO)Use this setting to not collect SQL text fromdynamic SQL statements.

Affected IFCIDs 22, 63.

The collection of NEGSQL-, SCAN-, SORT-, andDYNAMICSQL-data results in a high volume of tracedata that is generated by the DB2 subsystem. Thisincreases the CPU utilization. Furthermore, itexposes the application to DSNW133I messages.

3. Reduce the POSTPCT value to read buffers morefrequently. Try different values and evaluate theresults.

By default, the POSTPCT value is set toPOSTPCT(70). This means that the OP buffers areread when they are full up to 70%.

4. Ensure that the OMPE collector task is running atthe same or at a higher service level than themonitored DB2 subsystems.

5. Restart the OMEGAMON for DB2 started task tostart using the modified parameters.

KO2O0508E Near-Term History Data Collector -VSAM PHYSICAL I/O ERROR WITHRETURN CODE=rc, REASONCODE=rs

ExplanationA physical I/O error occurred while a PUT was issuedto the VSAM data set. This problem could be caused byan I/O error on the VSAM data set.



KO2O0509E Near-Term History Data Collector -ERROR IN VSAM PUT SEQUENT.WITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while a PUT sequential was issuedto the VSAM data set. This problem could be caused byan I/O error on the VSAM data set.



KO2O0510E Near-Term History Data Collector -ERROR IN VSAM PUT DIRECTWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while a PUT direct was issued to theVSAM data set. This problem could be caused by anI/O error on the VSAM data set.




KO2O0511E Near-Term History Data Collector -END OF VOLUME DETECTED. NOMORE PERFORMANCE DATA ISCOLLECTED

ExplanationAn end of volume is detected, and performance datawill not be extracted any more.


User responseAllocate another VSAM data set or reallocate the VSAMdata set and try the data extractor again.

KO2O0512E Near-Term History Data Collector -VSAM POINT MACRO FAILEDWITH RETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while a POINT was issued to theVSAM data set.



KO2O0513E Near-Term History Data Collector -KEY LENGTH FOR VSAM FILE ISNOT CORRECT

ExplanationThe key length specified for the VSAM data set wasincorrect.


User responseCorrect the key length to 80 and allocate the VSAMdata set again.

KO2O0514E Near-Term History Data Collector -MAXIMUM RECORD LENGTH FORVSAM FILE IS NOT CORRECT

ExplanationThe maximum record length specified for the VSAMdata set was incorrect.


User responseCorrect the maximum record length to 4096 andallocate the VSAM data set again.

KO2O0515E Near-Term History Data Collector -VSAM GET MACRO FAILED WITHRETURN CODE=rc, REASONCODE=rs

ExplanationAn error occurred while a GET was issued to the VSAMdata set. This problem could be caused by an I/O erroron the VSAM data set.



KO2O0516E Near-Term History Data Collector -VSAM DATA SET IS NOTINITIALIZED. PERFORM. DATA ISNOT COLLECTED

ExplanationThe specified VSAM data set was not initialized.


User responseInitialize the VSAM data set using the H2VSMINTutility. The JCL to initialize the VSAM data set is inrhilev.RKD2SAM(ACRTcccc).


KO2O0517I Near-Term History Data Collector -DATA SET dsname INITIALIZED

ExplanationThe indicated H2 (near-term history) data set wasinitialized successfully.

System actionNone.

User responseNone.

KO2O0518E Near-Term History Data Collector -DATA SET dsname INIT FAILED

ExplanationThe indicated H2 (near-term history) data set couldnot be initialized because of an error.

System actionNone.

User responseCheck for other error messages associated with thismessage and correct the error.

KO2O0519E Near-Term History Data Collector -VSAM DATA SET DDNAME H2VSAMIS NOT SPECIFIED

ExplanationThe ddname H2VSAM is not specified, but is requiredfor data extraction.


User responseAdd the DD card H2VSAM, together with the VSAMdata set name, to the data extractor JCL.

KO2O0520E Near-Term History Data Collector -VSAM ENDREQ FAILED WITHRETURN CODE=rc, REASONCODE=rs

ExplanationInternal error.



KO2O0521E Near-Term History Data Collector -VSAM VERIFY FAILED WITHRETURN CODE=rc, REASONCODE=rs




KO2O0522E Near-Term History Data Collector -RECORD LENGTH EXCEEDEDMAXIMUM RECORD LENGTH.RECORD TRUNCATED

ExplanationThe length of the performance record exceeds themaximum record length defined in the VSAM data set.The record is truncated.



KO2O0523E Near-Term History Data Collector -RETRIEVE RECORD FAILED. ENDOF DATA SET REACHED

ExplanationThe length of the performance record exceeds themaximum record length defined in the VSAM data set.The record is truncated.




KO2O0550E NEAR-TERM HISTORY DATACOLLECTOR - DDNAME name ISNOT SPECIFIED IN THE LOGARCHIVE JCL

ExplanationThe indicated ddname is not specified in the modelarchive JCL specified by the ARCHIVEJCL parameter.

System actionProcessing continues, but no JCL is generated toarchive the full Near-Term History Data Collector dataset.

User responseCorrect the model archive JCL.

KO2O0551E Near-Term History Data Collector -OPEN FAILED FOR DATA SET WITHDDNAME dd

ExplanationThe indicated data set in the model archive JCLspecified by the ARCHIVEJCL parameter could not beopened.

System actionProcessing continues, but no JCL is generated toarchive the full Near-Term History Data Collector dataset.

User responseCorrect the model archive JCL.

KO2O0553E Near-Term History Data Collector -FAILED TO LOAD MODULE c

ExplanationThe indicated module could not be loaded.

System actionProcessing stops.

User responseEnsure that this module is in the OMEGAMON XE forDB2 PE load library.

KO2O0554E Near-Term History Data Collector -UNABLE TO CREATE JCL TOARCHIVE H2 DATA SET

ExplanationOMEGAMON XE for DB2 PE could not create the JCLthat is needed to archive the Near-Term History DataCollector data set.


User responseEnsure that the member specified by the ARCHIVEJCLparameter exists in the data set allocated to theRKD2PAR DD statement.

KO2O0555I Near-Term History Data Collector -A BATCH JOB IS SUBMITTED TOFLUSH THE CONTENTS OF THE H2DATA SET



User responseNone.

KO2O0557W Near-Term History Data Collector -ONLY ONE H2 DATA SET ISAVAILABLE FOR FUTURE LOGSWITCHING



User responseNone.


KO2O0558E Near-Term History Data Collector -NO H2 DATA SET IS AVAILABLE,DB2 DATA IS NOT WRITTEN TO H2DATA SET

ExplanationNo data set is available for storing near-term historydata, so the collected DB2 data cannot be saved.


User responseSpecify at least one H2 (near-term history) data set inthe collection options member you are using.

KO2O0559W Near-Term History Data Collector -NO H2 DATA SET IS AVAILABLEFOR FUTURE LOG SWITCHING

ExplanationNo data set is available to store near-term history dataafter the active data set is full.


User responseBe sure that the maximum of three data sets havebeen specified in the collection options member.

KO2O0560W Near-Term History Data Collector -WRONG DISPOS. FOR dsname

ExplanationThe disposition mode for the named data set is notcorrect. Either MOD or NEW is specified; however, onlySHR and OLD are supported.


User responseChange the disposition to SHR or OLD in the JCL andtry again.

KO2O0561I Near-Term History Data Collector -H2 DATA SET dsname STATUS n %FULL

ExplanationThis message supplies information about the status ofall VSAM data sets specified in the collection optionsmember. It shows whether the data set is activelystoring data, available to store data, or unavailable. Italso shows what percentage of the data set has beenused.


User responseNone.

KO2O0562W Near-Term History Data Collector -n H2 RECORDS WERE LOST WHILENO H2 DATA SET WAS AVAILABLETO STORE DB2 DATA

Explanationnnear-term history data records were lost because nooutput buffer or no H2 (near-term history) data setwas available for some time to store collected data.This might also happen when the DB2 subsystem isterminating.


User responseEnsure that the maximum number of H2 (near-termhistory) data sets (3) is specified in the collectionoptions member, so it will be unlikely to lose data inthe future.

KO2O0563W NO H2 DATA SET INFORMATION ISPROVIDED BECAUSE VSAM WRITEOPTION IS NOT USED

ExplanationYou have attempted to display the status of your VSAMdata sets, but the Near-Term History Data Collector isnot writing to VSAM because the WRITEOPTIONkeyword is not set to VSAM.


User responseNone.


KO2O0564W H2 DATA SET IS NOT SWITCHEDBECAUSE VSAM WRITE OPTION ISNOT USED

ExplanationYou have attempted to manually switch VSAM datasets, but the Near-Term History Data Collector is notwriting to VSAM because the WRITEOPTION keywordis not set to VSAM.


User responseNone.

KO2O0565W NO SUBSTITUTION IS DONE INARCHIVE DATA SET. PLEASECHECK ARCHIVE JCL

ExplanationAn error exists in variable usage for @DB2, @DATE, or@TIME in the model archive JCL.

System actionProcessing continues, but the archive job is notsubmitted.

User responseCheck variable usage in the model archive JCL andcorrect any errors.

KO2O0566E ARCHIVE DATA SET NAME ISLONGER THAN 44 BYTES AFTERSUBSTITUTION. ARCHIVE JOB ISNOT SUBMITTED

ExplanationThe variable @DB2, @DATE, or @TIME in the modelarchive JCL is improperly used.

System actionProcessing continues, but the archive job is notsubmitted.

User responseCheck and correct the use of the variables in the modelarchive JCL.

KO2O0567I THERE ARE NO RECORDS IN H2DATA SET AND SO IT IS NOTBEING ARCHIVED

ExplanationThe Near-Term History Data Collector received aSWITCH command and detected that the current logdoes not have any Accounting, Audit, or Statisticsrecords.

System actionSwitches to the next log, but does not submit thearchive JCL.

Note: This message is displayed when the SWITCHcommand processing determines that no Statistics,Accounting or Audit records are in the current log dataset. As a result, the archive JCL is not submitted.

User responseIf you wish to archive any other records, for example,DKNZPARM records, submit the archive JCL manually.

Note: This message may be displayed if two SWITCHcommands are given in rapid succession. This maycreate a situation in which there are no records toarchive, depending on the level of DB2 activity.

KO2O0568W ARCHIVEJCL OPTION IS NOTSPECIFIED, SO NO ARCHIVE JOBIS SUBMITTED

ExplanationNo archival JCL member name was specified at thetime a SWITCH command was executed.

System actionSwitches Near-Term History Data Collector log datasets and continues processing.

User responseCheck that the archive JCL member of therhilev.RKD2SAM data set was not deleted. Themember supplied by IBM is ASEQcccc, where cccc isthe identifier for the Db2 system being monitored.

Note: You can manually submit the archive JCL tocorrect the situation.

KO2O0590E Near-Term History Data Collector -INVALID COLLECTION OPTIONMEMBER c IS SPECIFIED


ExplanationThe collection options member name specified in theNear-Term History Data Collector startup member orthe vary option of the MODIFY command is not valid.

System actionIf a not valid collection options member is specified inthe Near-Term History Data Collector startup member,the Near-Term History Data Collector terminated. If anot valid collection options member was specified bymeans of the MODIFY command, no collection optionis changed.

User responseCheck the collection options member name andreissue the command with a valid member name.

KO2O0591E Near-Term History Data Collector -VSAM DATA SET IS NOTINITIALIZED. DB2 DATA IS NOTCOLLECTED

ExplanationSee member DFNLOG1 or DFNLOG2 in the RKD2SAMdata set for information on how to initialize a VSAMdata set before it can be used by the Near-TermHistory Data Collector.

System actionProcessing continues with the next VSAM data setspecified in the collection options member, if any.

User responseInitialize the VSAM data set.

KO2O0592E DATA SET name IS ALLOCATED TOANOTHER JOB

ExplanationThis message is related to the Near-Term History DataCollector. The named data set is already allocated toanother job. However, a different data set name isrequired for each DB2 on each LPAR.


User responseCheck the Configuration Tool (formerly ICAT)configuration to ensure that different data set namesare used.

KO2O0593E DYNAMIC ALLOC FAILED - R15=n,S99ERROR=n, S99INFO=n,S99ERSN=n, DSN=dsname

ExplanationUnable to dynamically allocate one of the data setsspecified in the options member.


User responseCheck the return code and reason code provided in themessage and resolve the problem. See the MVSsystem programming library Application DevelopmentGuide, section 19-19, for return codes and reasoncodes.

KO2O0594E DATA SET name CANNOT BEFOUND

KO2O0595W NO AUTHORIZATION TO ACCESSDB2 SYSUTIL DATA SET AND NOSTOPPED UTILITY INFORMATIONCOLLECTED

ExplanationUnable to collect any stopped utility informationbecause of missing authorization to access the DB2SYSUTIL data set.


User responseIf you are using an external security package, such asRACF or CA-ACF2, give O2CI Read access to theSYSUTIL data set, then try again. The SYSUTIL data setname iscccccccc.DSNDBC.DSNDB01.SYSUTIL.I0001.A001,where cccccccc is the DB2 catalog name.

KO2O0600E ARGUMENT FOR TRAC COMMANDNOT VALID. TERMINATING


ExplanationInvalid argument found when trying to process theTRAC command.

System actionThe command is not processed.

User responseCheck and correct the arguments. Resubmit thecommand.

KO2O0601E TRAC COMMAND ID NUMBERMUST BE LESS THAN 256.COMMAND TERMINATING

ExplanationOMEGAMON XE for DB2 PE found an ID numbergreater than 256 when it tried to process the TRACcommand.

System actionThe command is not processed.

User responseSupply an ID number less than 256. Resubmit thecommand.

KO2O0700E EXCEPTION PROCESSING NOTINITIALIZED. COMMANDTERMINATING

ExplanationOMEGAMON XE for DB2 PE exception processing is notinitialized. OMEGAMON XE for DB2 PE cannot performexception monitoring.

System actionProcessing continues, ignoring exception analysis.


KO2O0701E EXCEPTION PROCESSING FAILEDTO INITIALIZE. RC=rc.EXCEPTION PROCESSINGINACTIVE

ExplanationOMEGAMON XE for DB2 PE exception processingended during initialization with the indicated error

code OMEGAMON XE for DB2 PE cannot monitorexceptions.

System actionProcessing continues without monitoring exceptions.


KO2O0702E EXCEPTION PROCESSING FAILEDTO LOCATE FIRST XECB.EXCEPTION PROCESSING NOTACTIVE

ExplanationOMEGAMON XE for DB2 PE could not locate the firstexception control block during initialization.OMEGAMON XE for DB2 PE cannot monitorexceptions.



KO2O0703E EXCEPTION PROCESSING FAILEDTO PROCESS EXCEPTION cccc

ExplanationOMEGAMON XE for DB2 PE cannot process theindicated exception. This error is probably caused by astorage overlay.

System actionProcessing continues, but the indicated exception isignored.


KO2O0704E EXCEPTION PROCESSING FAILEDTO PROCESS EXCEPTION cccc.TABLE NOT EXPANDABLE

ExplanationOMEGAMON XE for DB2 PE cannot process theindicated exception because the exception table is notexpandable.


System actionProcessing continues, but the indicated exception isignored.

User responseCheck the installation region constraints for storageabove the 16M line. If necessary, increase the amountof storage available above the line. If the problempersists, contact IBM support.

KO2O0705E EXCEPTION PROCESSING FAILEDTO INITIALIZE. RC = rc.EXCEPTION PROCESSING NOTACTIVE

ExplanationThe OMEGAMON XE for DB2 PE exception processingroutine could not initialize and ended with theindicated return code.


User responseVerify that OMEGAMON XE for DB2 PE is not beingconstrained by installation parameters that restrict theuse of storage above the 16M line. If the problempersists, contact IBM support.

KO2O0706E EXCEPTION PROCESSING FAILEDTO OBTAIN ID INFORMATION.DATA OMITTED

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot obtain identification information about thespecified exception.

System actionProcessing continues. OMEGAMON XE for DB2 PEomits the data it could not obtain from the display.

User responseIf this message is displayed after message KO2O0717,it is a normal occurrence. If it does not, the problem isprobably caused by a storage overlay. Contact IBMsupport.

KO2O0707E EXCEPTION PROCESSING FAILEDTO OBTAIN ID. ZOOMING ERRATIC

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot obtain identification information about thespecified exception. OMEGAMON XE for DB2 PE mightnot have enough information to go to the expectedpanel when you press F11 (Zoom).


User responsePress F11 (Zoom) again. If the problem persists,contact IBM support.

KO2O0708E EXCEPTION PROCESSING FAILEDTO LOCATE XGRP TABLE.EXCEPTION PROCESSING NOTACTIVE

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot locate the exception group table. OMEGAMON XEfor DB2 PE exception processing is not active.



KO2O0709E EXCEPTION PROCESSING FAILEDTO FORMAT XGRP TABLE.EXCEPTION PROCESSING NOTACTIVE

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot format the exception group table.



KO2O0710E EXCEPTION PROCESSING FAILEDTO OBTAIN cccccc CELL.


ExplanationOMEGAMON XE for DB2 PE exception processing couldnot obtain the cccccc cell.

System actionOMEGAMON XE for DB2 PE exception processingcontinues, but might not produce the expected results.


KO2O0711E EXCEPTION PROCESSING FAILEDTO LOCATE EXCEPTION TABLEENTRY. EXCEPTION cccc

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot locate the table entry for the indicated exception.This error is probably caused by a storage overlay.

System actionProcessing continues, but OMEGAMON XE for DB2 PEdoes not display data for this exception.


KO2O0713E EXCEPTION PROCESSING FAILEDTO FIND MESSAGE FOREXCEPTION cccc

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot locate the message for the indicated exception.This error is probably caused by a storage overlay.

System actionProcessing continues without displaying data for thisexception.


KO2O0714E EXCEPTION PROCESSING FAILEDTO FORMAT EXCEPTION MESSAGEcccc

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot format the message for the specified exception.This error is probably caused by a storage overlay.

System actionProcessing continues without displaying data for thisexception.


KO2O0715E EXCEPTION PROCESSING FAILEDTO OBTAIN OUTPUT CELL. UPDATEOMITTED

ExplanationA request for additional virtual storage was denied.

System actionProcessing continues, but exception information andhighlighting are incomplete.


KO2O0716E EXCEPTION PROCESSING FAILEDTO FIND CICS JOB NAME. IDOMITTED

ExplanationOMEGAMON XE for DB2 PE could not determine theCICS job name associated with an exception. Thiserror is probably caused by a storage overlay.

System actionProcessing continues, but exception information andhighlighting are incomplete.


KO2O0717E EXCEPTION PROCESSINGTHREAD ID NOT AVAILABLE.THREAD TERMINATED


ExplanationA thread related to an exception that exceeded itsthreshold value has terminated.

System actionProcessing continues without displaying theseexceptions.

User responseThis is a normal occurrence if the thread has justterminated. If the problem persists, contact IBMsupport.

KO2O0718E EXCEPTION PROCESSING FAILEDWITH UNEXPECTED PROGRAMCHECK IN routine

ExplanationThe OMEGAMON XE for DB2 PE exception processingroutine unexpectedly encountered a program check inthe indicated routine.

System actionProcessing continues, but OMEGAMON XE for DB2 PEexceptions might not produce the expected results.

User responseTake a note of this message, including the routine, andcontact IBM support.

KO2O0719E EXCEPTION PROCESSING FAILEDWITH UNEXPECTED PROGRAMCHECK IN TRIP PROCESSING

ExplanationThe OMEGAMON XE for DB2 PE exception processingroutine unexpectedly encountered a program check ina routine when an exception exceeded its thresholdvalue.

System actionProcessing continues, but OMEGAMON XE for DB2 PEexceptions might not produce the expected results.


KO2O0720E EXCEPTION PROCESSING FAILEDTO LOCATE cccc EXCEPTIONTABLE ENTRY

ExplanationOMEGAMON XE for DB2 PE exception processing couldnot locate the table entry for the indicated exception.This is probably caused by a storage overlay.

System actionProcessing continues, but OMEGAMON XE for DB2 PEdoes not display data for this exception.

User responseRestart OMEGAMON XE for DB2 PE. Contact IBMsupport.

KO2O0740E EXCEPTION PROCESSING FAILEDTO OBTAIN STORAGE FORMESSAGE EXCEPTION TABLE

ExplanationThe OMEGAMON XE for DB2 PE exception processingroutine could not obtain enough storage for itsexception message table.

System actionProcessing continues, but OMEGAMON XE for DB2 PEcannot monitor any exceptions.


KO2O0741E EXCEPTION PROCESSING FAILEDTO OBTAIN MSGE EXCEPTIONCONTROL BLOCKS

ExplanationThe OMEGAMON XE for DB2 PE exception processingroutine could not obtain the control blocks it needs toprocess the MSGE exception.

System actionProcessing continues, but OMEGAMON XE for DB2 PEcannot monitor the MSGE exception.



KO2O0742E ERROR ENCOUNTERED IN USERPROFILE FACILITY. MSGEEXCEPTION NOT AVAILABLE

ExplanationOMEGAMON XE for DB2 PE encountered an errorduring profile processing that prohibits the MSGEexception from operating properly.

System actionOMEGAMON XE for DB2 PE continues processing, butcannot monitor the MSGE exception.


KO2O0743E ERROR ENCOUNTERED IN USERPROFILE FACILITY. POPT OPTIONWILL NOT BE USED

ExplanationUser profile processing failed.



KO2O0750E ABEND IN NEW CYCLESUBROUTINE cccccccc

ExplanationOMEGAMON XE for DB2 PE terminated in the indicatednew cycle subroutine.

System actionProcessing continues, but the data OMEGAMON XE forDB2 PE displays might not be correct.


KO2O0751E ABEND IN NEW CYCLE DRIVER.REPORTED DATA MIGHT BEERRATIC

ExplanationOMEGAMON XE for DB2 PE terminated in the driverthat controls new cycles.

System actionProcessing continues, but the data OMEGAMON XE forDB2 PE displays might not be correct.


KO2O0752I MONITORED DB2 IS NO LONGERACTIVE. DISPLAYED DATA ISFROM LAST CYCLE

ExplanationThe DB2 that OMEGAMON XE for DB2 PE wasmonitoring is no longer active.

System actionOMEGAMON XE for DB2 PE displays the data itcollected during the previous OMEGAMON XE for DB2PE cycle. Processing continues.

User responseDetermine why the DB2 that OMEGAMON XE for DB2PE was monitoring is no longer active, and then restartDB2.

KO2O0753E ABEND IN THREAD CPUCOLLECTION ROUTINE

ExplanationOMEGAMON XE for DB2 PE terminated in the routinethat collects data about the CPU used by a thread.



KO2O0754W THREAD CPU COLLECTION HASBEEN DISABLED


ExplanationOMEGAMON XE for DB2 PE has disabled the routinethat collects data about the CPU used by a thread.



KO2O0755E ABEND IN CPU COLLECTIONROUTINE

ExplanationOMEGAMON XE for DB2 PE terminated in the routinethat collects data about the CPU usage.



KO2O0756W CPU COLLECTION HAS BEENDISABLED

ExplanationOMEGAMON XE for DB2 PE has disabled the routinethat collects data about the CPU usage.



KO2O0757E TRACE STATUS COLLECTION HASTERMINATED

ExplanationOMEGAMON XE for DB2 PE terminated in the routinethat collects data about the status of the global trace.



KO2O0758W TRACE STATUS COLLECTION HASBEEN DISABLED

ExplanationOMEGAMON XE for DB2 PE has disabled the routinethat collects data about the status of the global trace.



KO2O0800E INVALID SSCVT FOUND WITHSSCTID NOT EQUAL TO SSCT.TERMINATING

ExplanationThe JES SSCVT chain contains a not valid SSCVT, onewithout an SSCTID equal to SSCT.

System actionOMEGAMON XE for DB2 PE stops its search of theSSCVT chain and terminates processing.

User responseIdentify and correct the invalid SSCVT. (Your MVSsystems programmer can help you trace the SSCVTchain to correct the invalid SSCVT.)

KO2O0900E OMEGAMON XE for DB2 PEINCOMPATIBLE WITH THISOPERATING SYSTEM.TERMINATING

ExplanationOMEGAMON XE for DB2 PE operates only in anMVS/XA or MVS/ESA environment.


User responseDo not start OMEGAMON XE for DB2 PE on a non-MVS/XA or non-MVS/ESA operating system. Also,ensure that your operating system and your loadlibrary are compatible (both XA or both ESA).


KO2O0901E OMEGAMON XE for DB2 PE MUSTRUN FROM AN APF-AUTHORIZEDLIBRARY. TERMINATING



User responseMove the OMEGAMON XE for DB2 PE load modules toan APF-authorized library and restart the OMEGAMONXE for DB2 PE Common Interface.

KO2O0902U CANNOT LOCATE LOAD MODULEmodule. TERMINATING

ExplanationOMEGAMON XE for DB2 PE initialization processingcould not locate the indicated load module. Thismessage is usually caused by a failure to fully unloadthe OMEGAMON XE for DB2 PE product tape, or by afailure to migrate all modules to the runtime library.


User responseVerify that the indicated load module is in the properlibrary and restart OMEGAMON XE for DB2 PE.

KO2O0903U LOAD MODULE module IS AT THEWRONG RELEASE LEVEL.TERMINATING

ExplanationThe indicated OMEGAMON XE for DB2 PE load moduleis not at the correct release level. This message isusually caused by a failure to fully unload theOMEGAMON XE for DB2 PE product tape, or by afailure to migrate all modules to the runtime library.


User responsePlace a version of the load module that is at thecorrect release level in the proper library and restartOMEGAMON XE for DB2 PE.

KO2O0904E OMEGAMON XE for DB2 PEREQUIRES A DB2= DB2ID ATLOGON. TERMINATING

ExplanationOMEGAMON XE for DB2 PE did not find a DB2subsystem services address space matching the ID ofthe specified DB2 subsystem to be monitored whenthe session was started.


User responseUse the DB2= parameter when you log on to indicatethe ID of the DB2 subsystem to be monitored.Alternatively, specify DB2= on the START OMVTAMstatement to supply a default DB2 ID.

KO2O0905E SPECIFIED DB2 ID IS GREATERTHAN 8 CHARACTERS. SESSIONTERMINATING

ExplanationThe DB2 ID specified for the DB2= parameter is longerthan 8 characters. The ID for the DB2 subsystem to bemonitored cannot be longer than 8 characters.


User responseSupply a valid DB2 ID.

KO2O0906E COULD NOT LOCATE SPECIFIEDDB2 cccccccc. TERMINATING

ExplanationOMEGAMON XE for DB2 PE could not locate a DB2subsystem with a system services address spacenamed cccccccc.



User responseSupply a valid DB2 ID to monitor.

KO2O0907W OMEGAMON XE FOR DB2 PETERMINATING BECAUSE DB2 NOTYET INITIALIZED ORTERMINATING

ExplanationOMEGAMON XE for DB2 PE tried to check the releaselevel of the DB2 subsystem to be monitored and didnot find the normal set of DB2 control blocks duringinitialization. This problem can occur when DB2 isinitializing or terminating.


User responseCheck to see whether the DB2 to be monitored is stillactive. If so, restart OMEGAMON XE for DB2 PE.

KO2O0908W OMEGAMON XE for DB2 PE DOESNOT SUPPORT DB2 RELEASE vrm.TERMINATING

ExplanationOMEGAMON XE for DB2 PE does not support therelease level of the DB2 to be monitored.


User responseNone.

KO2O0910W DB2 HAS TERMINATED. THEFOLLOWING DISPLAY DATA WASCOLLECTED ON dd/mm/yy AThh:mm:ss

ExplanationThe DB2 subsystem that OMEGAMON XE for DB2 PEwas monitoring has terminated. The data that appearson this display was collected at the specified date andtime.

System actionOMEGAMON XE for DB2 PE continues processing.

User responseNone.

KO2O0911E FAILED TO LOCATE IRLM JOBcccccccc. TERMINATING

ExplanationOMEGAMON XE for DB2 PE could not locate theInternal Resource Lock Manager (IRLM) associatedwith the DB2 to be monitored at initialization time.


User responseStart or restart the IRLM used by DB2.

KO2O0912W DB2 HAS TERMINATED. NODISPLAY DATA HAS BEENCOLLECTED DURING THISSESSION

ExplanationThe DB2 subsystem that OMEGAMON XE for DB2 PEwas monitoring has terminated. OMEGAMON XE forDB2 PE cannot collect data about this DB2.

System actionOMEGAMON XE for DB2 PE continues processing, butcannot display data about this DB2.

User responseRestart the DB2 subsystem or direct OMEGAMON XEfor DB2 PE to monitor a different DB2.

KO2O0913E OMEGAMON XE for DB2 PESUPPORTED BY COMMONINTERFACE VERSION 230 ANDABOVE ONLY. VERSION IS vrm

ExplanationOMEGAMON XE for DB2 PE only operates with aCommon Interface at version 230 or later.

System actionOMEGAMON XE for DB2 PE terminates processing.


User responseVerify that OMEGAMON XE for DB2 PE is using anappropriate version of the common interface. If theproblem persists, contact IBM support.

KO2O0914E FAILED TO LOCATE IRLM JOB.TERMINATING

ExplanationThe Internal Resource Lock Manager (IRLM) addressspace is not active.

System actionOMEGAMON XE for DB2 PE terminates.

User responseVerify that the IRLM address space is active andrestart OMEGAMON XE for DB2 PE.

KO2O0920E FAILED TO LOCATE DB2 CONTROLBLOCK cccc FOR xxxx.TERMINATING

ExplanationOMEGAMON XE for DB2 PE could not locate theindicated main DB2 cccc control block duringinitialization.


User responseVerify that the specified DB2 xxxx is active, and restartOMEGAMON XE for DB2 PE.

KO2O0921E FAILED TO LOCATE IRLM CONTROLBLOCK ccccc FOR xxxx.TERMINATING

ExplanationOMEGAMON XE for DB2 PE could not locate theindicated main Internal Resource Lock Manager (IRLM)cccc control block during initialization.


User responseVerify that the IRLM associated with DB2 xxxx isactive, and restart OMEGAMON XE for DB2 PE.

KO2O0922E DB2 DBAS ADDRESS SPACE NOTYET ACTIVE FOR xxxx.TERMINATING

ExplanationOMEGAMON XE for DB2 PE could not locate thedatabase address space (DBAS) for DB2 xxxx duringOMEGAMON XE for DB2 PE initialization.


User responseVerify that the DBAS address space initializedsuccessfully. If not, restart DB2 and then restartOMEGAMON XE for DB2 PE.

KO2O0923E SUBSYSTEM CODE HAS STOPPED.CONTACT IBM SOFTWARESUPPORT

ExplanationA portion of OMEGAMON XE for DB2 PE code stopped.

System actionOMEGAMON XE for DB2 PE processing terminates.


KO2O0924E OMEGAMON XE FOR DB2 PEINITIALIZATION FAILED BECAUSEDB2 xxxx IS TERMINATING

ExplanationDB2 xxxx terminated during OMEGAMON XE for DB2PE initialization.


User responseDetermine why DB2 terminated. Restart DB2 and thenrestart OMEGAMON XE for DB2 PE.

KO2O0925E OMEGAMON XE FOR DB2 PEINITIALIZATION TERMINATEDBECAUSE DB2 xxxx IS NOT USABE


ExplanationDB2 xxxx not usable during OMEGAMON XE for DB2 PEinitialization.


User responseDetermine why DB2 not usable and then restartOMEGAMON XE for DB2 PE.

KO2O0926E OMEGAMON XE for DB2 PE B37SNAP FAILURE OCCURRED. SNAPDEBUGGING FACILITY DISABLED(ABENDXIT)

ExplanationThe data set in use by the O2CI O2SNAP ddname isfull. The O2SNAP data set is used for diagnosticpurposes.

System actionOMEGAMON XE for DB2 PE stops producingdiagnostics.

User responseTerminate the O2CI, then delete and reallocate theO2SNAP data set.

KO2O0927U UNRECOVERABLEOMEGAMON XEfor DB2 PE SNAP FAILURE.TERMINATING

ExplanationA SNAP dump is taken, but failed to complete.



KO2O0928E UNSUPPORTED COMBINATION OFDB2 AND IRLM RELEASES. USINGDEFAULT IRLM Rvrm

ExplanationA compatibility problem between DB2 and the InternalResource Lock Manager (IRLM) was detected.


User responseCall IBM support.

KO2O0930E INVALID VALUE FOR OPTION=PARAMETER. TERMINATING %%%%%

ExplanationA not valid parameter was found, usually beingconfigured by the Configuration Tool (formerly ICAT).


User responseRebuild the runtime environment by using theConfiguration Tool (formerly ICAT).

KO2O0930W - ** WARNING ** - EP ADDR TORTN routine IS UNRESOLVED!

ExplanationAn entry point address to the indicated routine couldnot be resolved. This happens if a program componentin OMEGAMON XE for DB2 PE tries to call anotherentry point that does not exist.



KO2O0951U OMEGAMON XE for DB2 PE MUSTRUN FROM AN APF-AUTHORIZEDLIBRARY. TERMINATING




User responseMove the OMEGAMON XE for DB2 PE load modules toan APF-authorized library and restart the OMEGAMONXE for DB2 PE Common Interface.

KO2O0952E GETMEM > LIMIT: X1 T1 R1 W1 C1R14=X2

ExplanationAn internal memory request was denied. If allowed,the address space will run short on storage.

• X1 is the requested amount.• T1 is the request type.• R1 is the requesting routine name.• W1 is the requested work area.• C1 is the calling routine.• X2 is the requesting return address.

System actionThe memory request is denied.


KO2O1000W DB2 ACCOUNTING CLASS ONETRACE STATUS IS INACTIVE, ALLFIELDS CONTAINING N/A AREUNAVAILABLE

ExplanationOMEGAMON XE for DB2 PE cannot provide data forsome fields when Accounting trace class 1 is notactive. OMEGAMON XE for DB2 PE indicates thesefields by displaying the characters N/A as their output.

System actionOMEGAMON XE for DB2 PE processing continues.

User responseTo display accurate data in these fields, startAccounting trace class 1.

KO2O1001E TABLE OVERFLOW. NOT ALLTHREADS CAN BE DISPLAYED.INCREASE LROWS LOGONPARAMETER

ExplanationThe number of threads that can be displayed is limitedby the LROWS parameter.


User responseUse the Configuration Tool (formerly ICAT) to increasethe LROWS parameter.

KO2O1100E AN APPLICATION TRACEREQUEST IS ALREADY ACTIVE.TRACE REQUEST CANNOT BEPROCESSED

ExplanationThe Application Trace Facility (ATF) received a requestto start a trace, but is already tracing an application.The ATF can only trace one application for eachOMEGAMON XE for DB2 PE session.

System actionThe ATF ignores the request.

User responseWait for the current trace to end, or stop it manually,then resubmit the request.

KO2O1101I APPLICATION TRACE REQUESTHAS BEEN STARTED. TRACEINITIALIZATION IS IN PROGRESS

ExplanationThe Application Trace Facility (ATF) received a requestto trace an application and is preparing to start thetrace.

System actionThe ATF initializes its trace data collector.

User responseNone.

KO2O1103E APPLICATION TRACE STARTREQUEST HAS FAILED.COLLECTOR ATTACH HAS FAILED


ExplanationOMEGAMON XE for DB2 PE could not start theapplication trace request because it could not attachits collector to capture the trace data.

System actionThe Application Trace Facility (ATF) terminates thetrace request.


KO2O1104E APPLICATION TRACE STARTREQUEST HAS FAILED. MODULENAME DSNALI WAS NOT FOUND

ExplanationOMEGAMON XE for DB2 PE could not start theapplication trace request because it could not locatethe DSNALI module.


User responseVerify that the DSNALI module is available to thecommon interface. If the DB2 load modules do notreside in MVS LPALIB or a LINKLIST data set, ensurethat the installation data set is concatenated to theSTEPLIB ddname in the O2CI JCL and that theinstallation data set is APF-authorized.

KO2O1105E APPLICATION TRACE STARTREQUEST HAS FAILED. MODULENAME DSNWLI2 WAS NOT FOUND

ExplanationOMEGAMON XE for DB2 PE could not start theapplication trace request because it could not locatethe DSNWLI2 module.


User responseVerify that the DSNWLI2 module is available to thecommon interface. If the DB2 load modules do notreside in MVS LPALIB or a LINKLIST data set, ensure

that the installation data set is concatenated to theSTEPLIB ddname in the O2CI JCL and that theinstallation data set is APF-authorized.

KO2O1106E APPLICATION TRACE STARTREQUEST HAS FAILED. MODULENAME O2ATccc WAS NOT FOUND

ExplanationOMEGAMON XE for DB2 PE could not start theapplication trace request because it could not locatethe O2ATccc module (where ccc is the DB2 versionbeing monitored).


User responseVerify that the O2ATccc module is in the proper library;then restart OMEGAMON XE for DB2 PE and resubmitthe request.

KO2O1107E APPLICATION TRACE REQUESTKEYWORD=value CONTAINS ANINVALID VALUE. CORRECT ANDPRESS ENTER

ExplanationThe indicated value of the specified keyword isincorrect.

System actionOMEGAMON XE for DB2 PE does not start theapplication trace request.

User responseCorrect the value of the specified keyword. Resubmitthe request.

KO2O1108E ATF START date or time GREATERTHAN END. CORRECT AND PRESSENTER

ExplanationThe indicated start date or start time is greater thanthe end date or end time.



User responseCorrect the date or time value. Resubmit the request.

KO2O1109E APPLICATION TRACE REQUESTKEYWORD=value IS MISSING ORINVALID. CORRECT AND PRESSENTER

ExplanationThe indicated keyword is missing or contains a notvalid value.


User responseCorrect or supply the value for the keyword. Resubmitthe request.

KO2O1110W APPLICATION TRACE REQUESTATTACH KEYWORDS MAY ONLY BESPECIFIED FOR A SINGLE DB2CONNECTION TYPE

ExplanationThe Application Trace Facility (ATF) received a tracerequest that contained qualifiers for more than oneconnection type. A value was provided for more thanone of these options:

TSOUSER= TSO UserID | JOBNAME= ________ Job NameCICSTRAN= ____ CICS Trans ID | CICSCONN= ________ CICS Conn. IDPSBNAME= ________ IMS PSB Name | IMSID= ________ IMS Region ID

System actionOMEGAMON for Db2 Performance Expert does notstart the trace.

User responseReview the application trace request. Clarify therequest to contain qualifiers only for the connectiontype of the plan you want to trace.

KO2O1111I ATF DATA IS FROM ANUNSUPPORTED DB2 VERSION<V1>.

ExplanationThe Application Trace Facility (ATF) received a tracerequest to display trace data that is captured in aVSAM data set, however, the data was collected from aDB2 version that is no longer supported byOMEGAMON for Db2 PE version 5.2.0.

System actionThe Application Trace Facility (ATF) ignores therequest.

User responseYou can do one of the following actions:

• Use a version of OMEGAMON for Db2 PE thatsupports the DB2 version that was used to collectthe trace data.

• Reinitialize the VSAM data set and collect new ATFtrace data by using OMEGAMON for Db2 PE version5.2.0.

KO2O1112I APPLICATION TRACEINFORMATION UNAVAILABLE. ANAPPLICATION TRACE HAS NOTBEEN REQUESTED

ExplanationThe Application Trace Facility (ATF) received a requestto display trace data, but no application trace wasstarted.

System actionThe Application Trace Facility (ATF) ignores therequest.

User responseStart an application trace, then navigate to the DisplayTrace Data panels.

KO2O1113I APPLICATION TRACEINFORMATION UNAVAILABLE. NODATA MATCHING TRACE CRITERIAHAS BEEN COLLECTED

ExplanationThe Application Trace Facility (ATF) received a requestto display trace data, but it could not find any data thatmatched the trace request criteria.


System actionOMEGAMON XE for DB2 PE displays this message.There is no data to display.

User responseVerify whether the trace request criteria werespecified accurately.

KO2O1114E APPLICATION TRACE PROGRAMSUMMARY DISPLAY IS NOTPOSSIBLE. ZOOM FROM UNIT OFWORK SUMMARY

ExplanationThe Application Trace Facility (ATF) was not able toproduce the Program Summary panel.


User responseNavigate to the Program Summary panel from the Unitof Work panel.

KO2O1115E APPLICATION TRACE PROGRAMDETAIL DISPLAY IS NOTPOSSIBLE. ZOOM FROM TRACEPROGRAM SUMMARY

ExplanationThe Application Trace Facility (ATF) was not able toproduce the Program Detail panel.


User responseNavigate to the Program Detail panel from the ThreadUnit of Work panel.

KO2O1116I APPLICATION TRACE PROGRAMDETAIL HAS NOT LOCATEDSUFFICIENT TRACE DATA TOPRODUCE A DISPLAY

ExplanationThe Application Trace Facility (ATF) received a requestto display trace data, but it could not find enoughinformation to produce the requested display.


User responseWait for OMEGAMON XE for DB2 PE to collect moretrace data.

KO2O1117E APPLICATION TRACE SCROLLCONTROL ARGUMENT ISNONNUMERIC

ExplanationA nonnumeric argument was specified with either the+nnnnn, -nnnnn, or Snnnnn ATF control keyword.+nnnnn scrolls forward nnnnn records, -nnnnn scrollsbackward nnnnn records, and Snnnnn selects thespecified record.


User responseSpecify a numeric value for nnnnn and press Enter tocontinue.

KO2O1118E APPLICATION TRACE CONTROLKEYWORD ARGUMENT ISINVALID. LENGTH EXCEEDS SIXCHARACTERS

ExplanationA scroll request (+nnnnn scroll forward, −nnnnn scrollbackward, Snnnnn select the specified record) wasmade on the Detail panel, but the argument is too long.


User responseCorrect the length of the argument and press Enter tocontinue.

KO2O1119E APPLICATION TRACE CONTROLKEYWORD ARGUMENT IS NOTVALID

ExplanationThe Application Trace Facility (ATF) received a notvalid argument for the control keyword.



User responseSupply a valid argument for the keyword and pressEnter to continue.

KO2O1120E APPLICATION TRACE CONTROLKEYWORD NOT LOCATED

ExplanationThe Detail panel does not contain a control keyword.

System actionOMEGAMON XE for DB2 PE displays this message andchooses the current SQL statement as the controlkeyword on the Detail panel.

User responsePress Enter to continue.

KO2O1121I APPLICATION TRACEINFORMATION UNAVAILABLE. NOSQL CALLS LOCATED

ExplanationThe Application Trace Facility (ATF) received a requestto display SQL Detail data, but it could not find anydata that matched the trace request criteria.


User responseWait for OMEGAMON XE for DB2 PE to collect moretrace data, or evaluate the trace criteria specified forthe current trace.

KO2O1122I APPLICATION TRACEINFORMATION UNAVAILABLE.SQL CALL REQUESTED NOTLOCATED

ExplanationThe Application Trace Facility (ATF) Detail panelreceived a plus, minus, or select request to displaytrace data for a selected SQL statement, but the SQLstatement was out of range.

System actionOMEGAMON XE for DB2 PE displays this message.

User responseCorrect the control keyword argument and press Enterto continue.

KO2O1123I APPLICATION TRACE SQL DETAILREQUEST MUST BE SELECTEDFROM PROGRAM SUMMARYDISPLAY

ExplanationThe Application Trace Facility (ATF) could not producethe requested panel.

System actionOMEGAMON XE for DB2 PE ignores the request.

User responseNavigate to the SQL Detail panel by selecting it fromthe Program Summary panel.

KO2O1124I APPLICATION TRACE HASTERMINATED. TRACE HAS BEENTERMINATED DUE TO -STOPTRACE BEING ISSUED

ExplanationThe Application Trace Facility (ATF) trace collector hasterminated because DB2 received a DB2 STOP TRACEcommand that terminated the DB2 trace that the ATFuses to collect data.

System actionThe Application Trace Facility (ATF) does not collectdata.

User responseDetermine why the STOP TRACE command was issued.Restart the trace and then issue an ATF trace request.

KO2O1125E APPLICATION TRACE STARTREQUEST HAS FAILED. PLANNAME plan NOT FOUND OR NOTAUTHORIZED


ExplanationThe plan name required by the Application TraceFacility (ATF) was not found or is not authorized for useby the Common Interface.

System actionDB2 stops attempting to create a thread andterminates the Application Trace Facility (ATF) tracecollection.

User responseDetermine if the customization tasks have beencompleted for the DB2 subsystem being monitored.Bind the indicated plan name and authorize it for usethrough the OMEGAMON XE for DB2 PE CommonInterface.

KO2O1126E APPLICATION TRACE STARTREQUEST HAS FAILED. STARTTRACE IS NOT AUTHORIZED

ExplanationThe Application Trace Facility (ATF) trace collector wasnot able to execute a START TRACE request to theDB2 subsystem being monitored; therefore, it couldnot start.

System actionDB2 START TRACE attempt fails and the ATFterminates.

User responseAuthorize the Common Interface to issue DB2 tracerequests.

KO2O1127E APPLICATION TRACE STARTREQUEST HAS FAILED. PLANNAME plan IS NOT AUTHORIZEDFOR USE

ExplanationThe indicated OMEGAMON XE for DB2 PE plan name isnot authorized for use by the Common Interface. (Thiswas determined during the request to start anApplication Trace Facility (ATF) trace.)

System actionThe DB2 connection fails and the ATF terminates.

User responseAuthorize the Common Interface to use the specifiedplan name.

KO2O1128E APPLICATION TRACE STARTREQUEST HAS FAILED. DB2CONNECT IS NOT AUTHORIZED

ExplanationThe Application Trace Facility (ATF) attempted toconnect to DB2 as a result of a START TRACE request.The connection was rejected by DB2 because theCommon Interface was not authorized to connect.

System actionThe START TRACE request is rejected by DB2, and theATF trace collection is terminated.

User responseIf external security is being used to control the abilityto connect to DB2, then authorize the CommonInterface to allow it to connect to the DB2 subsystembeing monitored. If external security is not being used,contact IBM support.

KO2O1129E APPLICATION TRACE HAS BEENTERMINATED. TRACE DATACOLLECTION WORK AREA IS FULL

ExplanationThe Application Trace Facility (ATF) stopped its currenttrace because the trace data collection work area isfull.

System actionThe ATF trace collector stops.

User responseAttempt to reduce the amount of trace data that iscollected by qualifying the trace criteria supplied in theSTART TRACE request. If the amount of trace datacollected is insufficient, contact IBM support.

KO2O1130E APPLICATION TRACE STARTREQUEST HAS FAILED. DB2CONNECT REJECTED. MAXCONNECTIONS REACHED

ExplanationThe Application Trace Facility (ATF) could not start therequested trace because it could not connect to DB2.


DB2 has reached the maximum number of connectionsallowed at this time.

System actionThe START TRACE request is rejected.

User responseIncrease the value of the CTHREAD parameter in theDSNZPARM module, if necessary. Wait for thebackground collection to stop and reissue the tracerequest.

KO2O1131E APPLICATION TRACE STARTREQUEST HAS FAILED. TRACEMONITOR2 NOT AUTHORIZED

ExplanationThe DB2 subsystem being monitored has notauthorized the Common Interface to issue DB2 tracerequests. (This was determined during the request tostart an Application Trace Facility (ATF) trace.)

System actionDB2 rejects any stop trace requests, and the ATF tracecollection terminates.

User responseGrant trace authority to the Common Interface.

KO2O1132E APPLICATION TRACE STARTREQUEST HAS FAILED. ALL TRACEOPX DESTINATIONS ARE IN USE

ExplanationThe Application Trace Facility (ATF) start trace requestdetermined that all OPX destinations are in use.

System actionThe start trace request is rejected by DB2, and the ATFtrace collection is terminated.


KO2O1133E APPLICATION TRACE DATA HASBEEN LOST. COLLECTOR UNABLETO PROCESS VOLUME OF DATACOLLECTED

ExplanationThe Application Trace Facility (ATF) determined that itcannot process the volume of trace data beinggenerated by DB2. As a result, some data has beenlost.

System actionThe trace collector remains active.

User responseAttempt to further qualify the trace criteria to limit theamount of trace data collected. Specify a plan nameand authid in the trace request. If the problempersists, contact IBM support.

KO2O1134E APPLICATION TRACE UNIT OFWORK DISPLAY IS NOT POSSIBLE.ZOOM FROM TRACE THREADSUMMARY

ExplanationThe Application Trace Facility (ATF) could not producethe Unit of Work panel.


User responseNavigate to the Unit of Work panel from the ThreadSummary panel.

KO2O1135E APPLICATION TRACE UOWSUMMARY HAS NOT LOCATEDSUFFICIENT TRACE DATA TOPRODUCE A DISPLAY




KO2O1136E APPLICATION TRACE PROGSUMMARY HAS NOT LOCATED


SUFFICIENT TRACE DATA TOPRODUCE A DISPLAY




KO2O1137E APPLICATION TRACE SQL INDEXHAS LOCATED MORE ENTRIESTHAN CAN BE DISPLAYED

ExplanationThe Application Trace Facility (ATF) could not producethe SQL Index panel.


User responseTry again when more data is collected.

KO2O1138E ATF AUTHORIZATION IDENTIFIERIN USE = authid

ExplanationThis message follows other ATF authorization failuremessages and shows the AUTHID for which accesswas denied.

System actionNone.

User responseGrant authorization to the indicated AUTHID, then tryagain.

KO2O1139E OVERLAPPING OR DUPLICATEDATA HAS RESULTED ININSUFFICIENT TRACE DATA

ExplanationThe Application Trace Facility (ATF) could not returnthe required trace information because of overlappingor duplicate data.

Overlapping data can occur if the DB2 time stamp forperformance trace records has overlapped for thesame thread.


User responseIf you are able to determine that duplicate data is thesource of the problem, then invoke the ApplicationTrace Facility (ATF) again. If you cannot determine thesource of the problem, contact IBM support.

KO2O1140E APPLICATION TRACE CAPTUREREQUEST FAILED. UNABLE TOLOAD O2ATCccc, O2ATCAP1,O2ATCAP2

ExplanationThe Application Trace Facility (ATF) could not load allof the mentioned modules.

System actionApplication trace capture to VSAM data set is denied.

User responseEnsure that the load library used to start upOMEGAMON XE for DB2 PE contains the mentionedmodules. Correct the problem and invoke theApplication Trace Facility (ATF) again.

KO2O1141E APPLICATION TRACE DSNAMEINCOMPLETE. SINGLE QUALIFIERNOT ALLOWED. REENTER THETRACE REQUEST

ExplanationThe Application Trace Facility (ATF) trace data setname must have two or more qualifiers.

System actionThe ATF terminates the trace request.

User responseRespecify the trace request.


KO2O1142E APPLICATION TRACE value LIMITREQUESTED IS NOT VALID.REENTER THE TRACE REQUEST

ExplanationThe indicated keyword value is not valid.


User responseRe-specify the trace request with a valid value for thekeyword.

KO2O1143E APPLICATION TRACE REQUESTFAILED FOR AN UNDETERMINEDREASON

ExplanationThe attempt to start the Application Trace Facility(ATF) trace has failed for a reason not checked by theATF. The DB2 return code and reason code from theSTART TRACE command are displayed below thismessage.

System actionThe ATF terminates the trace request.

User responseLocate the reason code in DB2 Messages and Codes todetermine why the ATF trace request was notsuccessful. Correct the problem and reenter the tracerequest.

KO2O1144E APPLICATION TRACE STARTREQUEST HAS FAILED. UNABLE TOALLOCATE SPECIFIED DATA SET

ExplanationThe Application Trace Facility (ATF) could not allocatethe specified VSAM data set for use.

System actionThe ATF is terminated.

User responseSpecify the name of a VSAM linear data set and invokethe ATF again.

KO2O1145E APPLICATION TRACE STARTREQUEST HAS FAILED. THE VSAMDATA SET CANNOT BE OPENED.CHECK LOG

ExplanationThe Application Trace Facility (ATF) detected an errorwhen opening the VSAM data set for use.

System actionThe ATF is terminated.

User responseCheck the system log for the specific reason. Correctthe problem, and invoke the ATF again.

KO2O1146E ALLOCATION FAILED, DSN:dsname REASON CODE: rs

ExplanationThe dynamic allocation of the named data set failed.The supervisor call instruction (SVC) 99 returned withthe named reason code.


User responseSee MVS Messages and Codes for more information.

KO2O1147E ATF CAPTURE ERROR: request ONtype RETURN= rc REASON= rsINFO=info

ExplanationThe Application Trace Facility (ATF) detected an errorwith the VSAM data set while using the capture serverAPI. The API request and type information arereturned along with the failing return code, reasoncode, and information code.

System actionApplication trace capture to VSAM data set isdiscontinued.

User responseExamine the associated MVS messages and othercapture server messages prefixed by KO2R. Correctthe problem, and invoke the ATF again.


KO2O1148E ATF DATA SET SPECIFIED COULDNOT BE FOUND OR IS NOT A VSAMDATA SET

ExplanationThe specified Application Trace Facility (ATF) data setdoes not exist or is not a VSAM data set.

System actionOMEGAMON XE for DB2 PE does not start the ATFtrace request.

User responseCorrect the data set name. Resubmit the request.

KO2O1149I ATF DATA SET SPECIFIED HASBEEN MIGRATED. PRESS ENTERTO PROCEED

ExplanationThe specified Application Trace Facility (ATF) data sethas been migrated.

System actionNone.

User responsePress Enter to use the data set, specify a different dataset name, or press PF3 to cancel the request.

KO2O1150W APPLICATION TRACE REQUESTPLANNAME=ALL DISABLED VIAINSTALLATION EXIT

ExplanationThis warning was programmed on purpose. WhenOMEGAMON XE for DB2 PE was installed, it wasconfigured that PLANNAME = ALL is not allowed forthe Application Trace Facility (ATF).


User responseIf required, ask your administrator to allow thisparameter.

KO2O1151E ATF SMF=Y and GTF=Y AREMUTUALLY EXCLUSIVE. CORRECTAND PRESS ENTER TO PROCEED

ExplanationOnly SMF=Y or GTF=Y can be specified.

System actionOMEGAMON XE for DB2 PE does not start theApplication Trace Facility (ATF) trace request.

User responseChange one or both of these parameters to N.Resubmit the request.

KO2O1152 NUMBER OF TRACE RECORDSLOST DUE TO VSAM TASK: n

ExplanationThe Application Trace Facility (ATF) lost n tracerecords produced by DB2 because of high volume.

System actionNone.

User responseUse selection criteria that restrict the volume ofrecords to be captured by the ATF.

KO2O1152E THE APPLICATION TRACE STARTFAILED. THE VSAM DATASET ISFULL.

ExplanationThe application trace cannot be started because theVSAM dataset is full and the option MODE=APPEND isused.

System actionNone.

User responseUse a different VSAM dataset or use the optionMODE=REUSE to overwrite existing data in thedataset.

KO2O1153 NUMBER OF UOW RECORDS LOSTDUE TO VSAM TASK: n

ExplanationThe Application Trace Facility (ATF) lost nUnit of Work(UOW) records because of high volume UOWs in DB2.


System actionNone.


KO2O1160E APPLICATION TRACE REPORTREQUEST FAILED. UNABLE TOLOAD O2AR210, O2AR220,O2ATRPT

ExplanationThe Application Trace Facility (ATF) could not load allof the mentioned modules.

System actionApplication trace reporting is denied.

User responseEnsure that the load library used to start upOMEGAMON XE for DB2 PE contains the mentionedmodules. Correct the problem and invoke the ATFagain.

KO2O1161E MULTIPLE ENTRIES NOTALLOWED FOR field1 AND field2.

ExplanationYou can enter multiple values for the TraceSpecification Fields PLANNAME, PACKNAME, COLLID,PKGLOC and AUTHID. However, DB2 TRACE onlysupports the specification of multiple values for one ofthe fields.

System actionApplication Trace Facility will not continue tracespecification until the field(s) have been corrected.

User responseEither enter a value in the filter field, or change theexclude field to N.

KO2O1161I xxxx STARTING APPLICATIONTRACE

ExplanationAn application trace is being started for DB2subsystem xxxx.

System actionThe application trace is being initialized.

User responseNone.

KO2O1162I xxxx START TRACE yyyy

ExplanationA START TRACE command yyyy is issued to DB2subsystem xxxx.

System actionThe application trace is being initialized.

User responseNone.

KO2O1163E NO VALUE SPECIFIED FOR FIELDfield1, field2 =YES IS INVALID

ExplanationThe exclude option field can only be requested if thecorresponding value field has one or more valuesentered.

System actionATF will not continue trace specification until thefield(s) have been corrected.

User responseEither enter a value in the filter field, or change theexclude option field to N.

KO2O1163I xxxx STOPPING APPLICATIONTRACE

ExplanationAn application trace on DB2 subsystem xxxx has runfor the specified duration or has been stoppedmanually.

System actionThe application trace is being stopped.

User responseNone.


KO2O1164E XPLN=Y NOT ALLOWED WHENPLAN=ALL SPECIFIED

ExplanationTo exclude plans, you must enter a specific plan name.ALL plans cannot be excluded.


User responseEither enter specific plan names instead of ALL or setXPLN to N.

KO2O1164I xxxx STOP TRACE yyyy

ExplanationA STOP TRACE command yyyy is issued to DB2subsystem xxxx.

System actionThe application trace is being stopped.

User responseNone.

KO2O1165E ROUTINE FILTERING NOTALLOWED WHEN XXXXXXXXSPECIFIED

ExplanationWhen ROUTINE1 or ROUTINE2 is specified, some ATFfilter options are not supported. In the message,where XXXXXXXX is given in the example above, theactual text may be PACKNAME, COLLID, or PKGLOC.


User responseEither remove ROUTINE from trace specification orremove other filter value.

KO2O1165W APPLICATION TRACE DBID/OBIDBUFFER FULL

ExplanationThe Application Trace Facility (ATF) buffer, used tohold DBID/OBID information, is full. Some DBID/OBIDwill not be translated.



KO2O1167E THE VTAM TRACE CANNOT BEPROCESSED. REASON: <V1> OR<V2>

ExplanationTIME OVERLAP OCCURRED

If a deferred trace in ATF is scheduled to write to aparticular dataset at a particular time, and youspecify another deferred trace to write to thisparticular dataset at this particular time, this tracecannot be executed because the VSAM dataset isnot available.

<V2> MODE=APPEND REQUIREDIf there are one or more deferred traces that writeto a particular dataset, and you specify anotherdeferred trace to write to this particular dataset byusing the option MODE=REUSE, this trace cannotbe started because it would overwrite data fromthe other traces.

System actionNone.

User response• If <V1> is issued, specify a different dataset or

modify the start time or the duration of the trace sothat the scheduled time does not overlap with otherrequests to this dataset.

• If <V2> is issued, specify a different dataset or usethe option MODE=APPEND.

None.

KO2O1169I THE START DATE IS NOTSPECIFIED. THE CURRENT DATEIS USED.

ExplanationIf the start time is specified without specifying thestart date, the current date is used as the start date ofthe deferred ATF trace.


System actionNone.

User responseNone.

KO2O1170E ROUTINEx REQUIRES BOTHSCHEMA AND NAME TO BESPECIFIED

ExplanationWhen ROUTINE1 or ROUTINE2 is specified, both theschema and name fields must be filled in.

System actionTrace specification cannot be completed.

User responseIf routine filtering is requested, provide values for bothfields.

KO2O1171E TRACING ROUTINES REQUIRESSQLDATA=Y TO BE SPECIFIED

ExplanationRoutine filtering requires SQLDATA=Y to be specified.


User responseIf routine filtering is requested, specify SQLDATA=Y.

KO2O1174E ROUTINE FILTERING REQUIRESDSN SPECIFICATION

ExplanationRoutine filtering requires VSAM data set output.


User responseIf routine filtering is requested, specify an OUTPUTdata set name.

KO2O1200E UNABLE TO ISSUE DB2COMMAND. DB2 NOT ACTIVE

ExplanationOMEGAMON XE for DB2 PE could not issue thecommand requested because the DB2 to which thecommand was issued is not active.


User responseIssue the command to an active DB2 subsystem, orwait for this DB2 to become active.

KO2O1201E UNABLE TO ISSUE DB2COMMAND. GETMAIN FAILED

ExplanationOMEGAMON XE for DB2 PE could not issue thecommand requested because its getmain requestfailed.



KO2O1221I OMEGAMON XE FOR DB2 PEMESSAGE SUBSYSTEM ISSUCCESSFULLY INITIALIZED

ExplanationOMEGAMON XE for DB2 PE successfully initialized itsmessage subsystem.


User responseNone.

KO2O1222E OMEGAMON XE for DB2 PEMESSAGE SUBSYSTEMINITIALIZATION FAILED

ExplanationOMEGAMON XE for DB2 PE could not initialize itsmessage subsystem successfully.


System actionOMEGAMON XE for DB2 PE processing terminates.


KO2O1223E AN ERROR WAS FOUNDOBTAINING DB2/IRLM MESSAGES

ExplanationOMEGAMON XE for DB2 PE encountered an error whilecollecting DB2/IRLM messages.

System actionOMEGAMON XE for DB2 PE processing continues, butOMEGAMON XE for DB2 PE cannot display any DB2/IRLM messages. OMEGAMON XE for DB2 PE writes aSNAP dump to the O2SNAP data set and terminatesthe command.


KO2O1224E O2 MESSAGE SUBSYSTEM IS NOTACTIVE. PLEASE TRY RECYCLINGTHE O2CI STARTED TASK

ExplanationThe OMEGAMON XE for DB2 PE message subsystem isnot active. OMEGAMON XE for DB2 PE cannot displayDB2/IRLM messages.

System actionOMEGAMON XE for DB2 PE processing continues, butOMEGAMON XE for DB2 PE cannot display any DB2/IRLM messages. OMEGAMON XE for DB2 PE writes aSNAP dump to the O2SNAP data set and terminatesthe command.

User responseVerify that OMEGAMON XE for DB2 PE is not beingconstrained by installation parameters that restrict theuse of storage above the 16M line. Contact IBMsupport.

KO2O1230E CONTROL BLOCK VALIDATIONERROR

ExplanationOMEGAMON XE for DB2 PE could not validate a controlblock.

System actionCommand execution terminates. OMEGAMON XE forDB2 PE writes a SNAP dump to the O2SNAP data set.

User responseObtain the SNAP dump and contact IBM support.

KO2O1250E THE KEYWORD SPECIFIED IS NOTRECOGNIZED

ExplanationOMEGAMON XE for DB2 PE did not recognize thekeyword you supplied.

System actionOMEGAMON XE for DB2 PE ignores the command.

User responseCorrect the keyword and press Enter.

KO2O1251W NON-UNIQUE THREAD FOUNDBASED ON SPECIFIEDINFORMATION

ExplanationOMEGAMON XE for DB2 PE could not find a uniquethread based on the plan name, connection ID,correlation ID, and authorization ID supplied. Thecharacters in the parentheses at the end of themessage are an internal code.

System actionOMEGAMON XE for DB2 PE processing continues, butOMEGAMON XE for DB2 PE does not display threadinformation.

User responseSelect the All Threads Connected to DB2 panel (bytyping A. on the top line of the panel). From this panel,move the cursor to a thread for which detailedinformation is needed.

KO2O1252W THREAD NOT FOUND


ExplanationOMEGAMON XE for DB2 PE could not find therequested thread. The requested thread has probablyterminated.

System actionOMEGAMON XE for DB2 PE continues processing.

User responseSpecify another thread.

KO2O1253E UNABLE TO LOCATE IRLMCONTROL BLOCK block

ExplanationOMEGAMON XE for DB2 PE could not locate theindicated Internal Resource Lock Manager (IRLM)control block.

System actionOMEGAMON XE for DB2 PE continues processing, butcannot display all locking information for the specifiedthread.

User responseSpecify a different thread. If the problem persists,contact IBM support.

KO2O1254W THREAD INDOUBT. THREAD DOESNOT OWN LOCKS OR CLAIMS

ExplanationThe Locks/Claims Owned By a Thread panel could notfind any locks or claims owned by the thread that isindoubt. Indoubt threads do not own locks or claims.

System actionThe display is terminated.

User responseNone.

KO2O1255W THREAD INDOUBT. THREAD DOESNOT WAIT FOR LOCKS OR DRAINS

ExplanationThe Locks/Claims Causing a Thread to Wait panelcould not find any locks or drain waits for the threadthat is indoubt. Indoubt threads do not acquire locksand do not drain claims.


User responseNone.

KO2O1256W THREAD INDOUBT (PLANNAME=%%%%)

ExplanationOMEGAMON XE for DB2 PE could not find therequested thread. The requested thread is indoubt.


User responseNone.

KO2O1260E INVALID KEYWORD ON COMMANDLINE (%%%%%)

ExplanationRelated to exception processing.

KO2O1261E KEYWORD OPERATOR IS INVALID(%%%%%)


KO2O1262E INVALID DELIMITERENCOUNTERED (%)


KO2O1263E INVALID DATE OR TIME ENTERED(%%%%%)


KO2O1264E INVALID RELATIVE TIMEENTERED (%%%%%)



KO2O1265E TIME RANGE EXCEEDS THEMAXIMUM VALUE OF %%%%HOURS


KO2O1266E RELATIVE TIME INVALID WHENABSOLUTE DATE/TIME IS ALSOSPECIFIED


KO2O1267E REPORT INTERVAL MUST BE AMULTIPLE OF %%% MINUTESTHAT IS EVENLY DIVISIBLE INTO60


KO2O1269E DUPLICATE VALUE (%%%%%)REMOVED


KO2O1270E EXCEPTION NAME MUST BEENTERED ON COMMAND LINE


KO2O1271E EXCEPTION (%%%%) NOTCURRENTLY DEFINED TOEXCEPTION ANALYSIS


KO2O1272E INVALID EXCEPTION HEADER($XECBH) FOUND


KO2O1273E INVALID FUNCTION SPECIFIED(%%%%%)


KO2O1274E KEYWORD SPECIFIED IS INVALID(%%%%%)


KO2O1275E KEYWORD VALUE LENGTH ISINVALID (%%%%%)


KO2O1276E KEYWORD VALUE IS INVALID (%%%%%)


KO2O1277I NO EXCEPTION FILTERS EXISTFOR %%%%. USING DEFAULTFUNCTION=ADD


KO2O1278E RULE(%%%%%. IS INVALID.INPUT HAS BEEN IGNORED


KO2O1279E INVALID RULE NUMBER FOR ADD.INPUT HAS BEEN IGNORED


KO2O1280E ERROR IN THE OMEGAMON XE forDB2 PE USER PROFILE FACILITY$PSVC (ADD). RETURN CODE=rc

KO2O1281E ERROR IN THE OMEGAMON XE forDB2 PE USER PROFILE FACILITY$STTE. RETURN CODE=rc

KO2O1282E ERROR DURING DELETION OFEXCEPTION RULE

KO2O1283E ERROR IN THE OMEGAMON XE forDB2 PE USER PROFILE FACILITY$PSVC (DELETE). RETURNCODE=rc

KO2O1284I ALL EXCEPTION RULES DELETED.DEFAULTING TO ADD


KO2O1285E THE EXCEPTION ENTERED (%%%%) IS NOT A THREAD EXCEPTION

KO2O1286E ERROR IN THE OMEGAMON XE forDB2 PE USER PROFILE FACILITY$PSVC (FETCH). RETURN CODE=rc

KO2O1287E THRESHOLD VALUE INVALID FOREXCEPTION %%%%

KO2O1288E RULE(%%%%%. INVALID.CONNTYPE NOT = CICS

KO2O1289E RULE(%%%%%. INVALID.CONNTYPE NOT = IMS

KO2O1290E RULE(%%%%%. INVALID.THRESHOLD OR EXCLUDE MUSTBE SPECIFIED, NOT BOTH

KO2O1291E INVALID RULE NUMBERSPECIFIED. DEFAULTING TORULE=01

KO2O1292E INVALID RULE NUMBERSPECIFIED. ADDING TO END OFCURRENTLY DEFINED RULES

KO2O1293E INVALID RULE NUMBERSPECIFIED. DEFAULTING TODISPLAY ALL

KO2O1294E UNABLE TO USE THREADEXCEPTION PROFILE %%%%%%%%. PROFILE IS OUTDATED,PLEASE DELETE AND REDEFINE.

ExplanationException processing routine found outdated userprofile %%%%%%%%.

System actionException rules are skipped and processing continues.

User responseDelete and redefine %%%%%%%% user profile..

KO2O1300E INVALID MODIFY REQUEST TONear-Term History Data CollectorRECEIVED. REQUEST IGNORED

ExplanationThe VARY OPTION command specified is not valid.

System actionProcessing continues with the previous collectionoptions.

User responseCheck the VARY OPTION command, correct themistake and reissue the VARY command.

KO2O1301E Near-Term History Data CollectorCOULD NOT LOCATE MODULEmodule. TERMINATING

ExplanationThe indicated module is required, but missing in theload library.


User responseAdd the module to the load library and restart theNear-Term History Data Collector.

KO2O1302E Near-Term History Data CollectorLOAD MODULE module IS AT THEWRONG RELEASE LEVEL.TERMINATING

ExplanationThe indicated module is at the wrong release level.


User responseMove the module with the correct release level to theload library and restart the Near-Term History DataCollector.

KO2O1303E NEAR-TERM HISTORY DATACOLLECTOR SUPPORTED BYVERSION 250 AND ABOVE ONLY.ACTUAL VERSION IS n

ExplanationThe OMNIMON version is not compatible with theNear-Term History Data Collector.



User responseUse the OMNIMON version delivered with OMEGAMONXE for DB2 PE and restart the Near-Term History DataCollector.

KO2O1304I Near-Term History Data CollectorOPTION PARAMETERSPROCESSED SUCCESSFULLYFROM MEMBER member



User responseNone.

KO2O1305E NEAR-TERM HISTORY DATACOLLECTOR NOT LICENSED FORTHIS SYSTEM. TERMINATING

ExplanationOMEGAMON XE for DB2 PE operates in an MVS/ESAenvironment, but you have an MVS/XA version of theOMEGAMON XE for DB2 PEnear-term historycomponent.


User responseUse an MVS/ESA version of the OMEGAMON XE forDB2 PEnear-term history component and restart theNear-Term History Data Collector.

KO2O1306E Near-Term History Data CollectorREQUIRES APF LIBRARY.TERMINATING



User responseMove the OMEGAMON XE for DB2 PE load modules toan APF-authorized library and restart the Near-TermHistory Data Collector.

KO2O1307I Near-Term History Data CollectorIS TERMINATING



User responseNone.

KO2O1308I Near-Term History Data CollectorACTIVELY MONITORING DB2cccc



User responseNone.

KO2O1309I Near-Term History Data CollectorSERVER cccccccc IS ACTIVE



User responseNone.

KO2O1310I Near-Term History Data CollectorSERVER cccccccc HASTERMINATED



System actionProcessing terminates if a STOP H2 command wasissued, unless an error is recoverable.

User responseIf the Near-Term History Data Collector is terminatingas a result of a STOP H2 command, no action isnecessary. Otherwise, look for previous messages todetermine the reason for termination, and action thatis required.

KO2O1311I Near-Term History Data CollectorSERVER cccccccc REATTACHEDAFTER TERMINATION



User responseNone.

KO2O1312E ANOTHER Near-Term History DataCollector ALREADY ACTIVE FORDB2 subsystem

ExplanationAnother Near-Term History Data Collector is alreadymonitoring this DB2 subsystem. There is only oneactive Near-Term History Data Collector for each DB2.

System actionProcessing terminates during Near-Term History DataCollector startup. Processing continues if a newcollection options member is used.

User responseNone.

KO2O1313W Near-Term History Data CollectorTEMPORARILY SUSPENDED DATACOLLECTION BECAUSE OF NOAVAIL. STORAGE



User responseNone.

KO2O1314I Near-Term History Data CollectorRESUMED DATA COLLECTION.STORAGE AVAILABLE



User responseNone.

KO2O1315W NEAR-TERM HISTORY DATACOLLECTOR - INVALID OUTPUTRECEIVED xxx

ExplanationInvalid output was received.

• xxx is a short text string describing the reason for theinvalid input.



KO2O1316I Near-Term History Data CollectorHAS TERMINATED



User responseNone.

KO2O1317E Near-Term History Data CollectorSERVER cccccccc HAS EXCEEDED


THE MAX. NBR OF ABENDS ANDTERMINATED

ExplanationThe OMEGAMON Collector failed more than 10 timesand has terminated.



KO2O1318I Near-Term History Data Collector -NEW OPTIONS IN EFFECT FORCURRENT INTERVAL



User responseNone.

KO2O1319E Near-Term History Data Collector -NEW INTERVAL OPTIONSREJECTED

ExplanationThe specified check for DB2 failed.



KO2O1320E Near-Term History Data Collector -IDENTITY TO DB2 FAILED.RETURN CODE rc

ExplanationThe Near-Term History Data Collector identified to DB2failed.


User responseCheck the IFI return code in DB2 Messages and Codes.Correct the problem and restart the Near-Term HistoryData Collector.

KO2O1321E Near-Term History Data Collector -IDENTITY TO DB2 FAILED.REASON CODE rs

ExplanationThe Near-Term History Data Collector identified to DB2failed.



KO2O1322E Near-Term History Data Collector -CREATE THREAD FAILED. RETURNCODE rc

ExplanationThe Near-Term History Data Collector could not createa thread to DB2.



KO2O1323E Near-Term History Data Collector -CREATE THREAD FAILED. REASONCODE rs

ExplanationThe Near-Term History Data Collector could not createa thread to DB2.




KO2O1324E Near-Term History Data Collector -DISCONNECT FROM DB2 FAILED.RETURN CODE rc

ExplanationThe Near-Term History Data Collector could notdisconnect from DB2.



KO2O1325E Near-Term History Data Collector -DISCONNECT FROM DB2 FAILED.REASON CODE rs

ExplanationThe Near-Term History Data Collector could notdisconnect from DB2.



KO2O1326E Near-Term History Data Collector -TRACE COMMAND FAILED.RETURN CODE rc

ExplanationThe Near-Term History Data Collector could not start/stop/modify a trace.



KO2O1327E Near-Term History Data Collector -TRACE COMMAND FAILED.REASON CODE rs

ExplanationThe Near-Term History Data Collector could not start/stop/modify a trace.



KO2O1328W Near-Term History Data Collector -DB2 subsystem SPECIFIED INOPTIONS NOT ACTIVE

ExplanationThe specified DB2 subsystem was not active. TheNear-Term History Data Collector has waited for it tocome up for 30 minutes.


User responseBring up the specified DB2 subsystem and restart theNear-Term History Data Collector.

KO2O1329E Near-Term History Data CollectorIS TERMINATING BECAUSE OF ACRITICAL SERVER FAILURE

ExplanationThe Near-Term History Data Collector terminatedbecause it detected a critical server failure.




KO2O1330W Near-Term History Data CollectorTRACE STOPPED. NO STATISTICSDATA IS COLLECTED

ExplanationThe trace started by the Near-Term History DataCollector was stopped. No statistics data wascollected.


User responseRestart the Near-Term History Data Collector andensure that traces started by the collector do not stop.

KO2O1331W Near-Term History Data CollectorTRACE STOPPED. NOACCOUNTING, AUDITING ORPERF. DATA COLLECTED

ExplanationThe trace started by the Near-Term History DataCollector was stopped. As result, no accounting, audit,or performance data can be collected.


User responseRestart the Near-Term History Data Collector andensure that traces started by the collector are notstopped.

KO2O1342E Near-Term History Data Collector -TRACE COMMAND FAILED.cccccccc HAS NO TRACEAUTHORIZATION

ExplanationThe trace command did not go through becauseOMEGAMON XE for DB2 PE does not have DB2 traceauthority.


User responseGrant trace authority to O2CI DB2, then try again.

KO2O1343E Near-Term History Data Collector -TRACE COMMAND FAILED WITHDB2 MESSAGE ID n

ExplanationOMEGAMON XE for DB2 PE could not issue a DB2trace command. The indicated message ID revealswhy.


User responseContact IBM support for an explanation of themessage and help in resolving the problem.

KO2O1345I Near-Term History Data Collector -NEW OPTIONS WILL TAKE EFFECTWHEN THE CURRENT INTERVALEXPIRES

ExplanationNewly specified options for the Near-Term HistoryData Collector will go into effect after the currentinterval ends.

System actionNone.

User responseNone.

KO2O1346E Near-Term History Data Collector -NO MORE STORAGE FOR UOW.PERFORMANCE DATA IS NOTCOLLECTED

ExplanationLack of storage was detected for Unit of Work (UOW).


User responseIncrease the region size.

KO2O1347E Near-Term History Data Collector -READA/READS FAILED. RETURNCODE rc


ExplanationREADA/READS failed during online data collection.


User responseSee DB2 Messages and Codes for an explanation of thereturn code.

KO2O1348E Near-Term History Data Collector -READA/READS FAILED. REASONCODE rs

ExplanationREADA/READS failed during online data collection.


User responseSee DB2 Messages and Codes for an explanation of thereason code.

KO2O1349W Near-Term History Data Collector -DYNAMIC BUFFER POOL CELLPOOL IS FULL

ExplanationThe buffer pool storage used to hold buffer poolinformation is full.



KO2O1350W Near-Term History Data Collector -READS RETRY LIMIT EXCEEDED

ExplanationDB2 has detected a temporary lack of storage on aREADS command.

System actionThe system re-executes the READS command 10times. If lack of storage persists, the commandterminates and returns to the caller with no data.

User responseSee messages KO2O1347E and KO2O1348E for moreinformation.

KO2O1351I variable message text

ExplanationNot applicable.

System actionNot applicable.

User responseNot applicable.

KO2O1352I variable message text

ExplanationNot applicable.

System actionNot applicable.

User responseNot applicable.

KO2O1353E %%%%> STOP TRACE NOTISSUED. TRACE NUMBER IS NOTAVAILABLE




KO2O1355W Near-Term History Data Collector -APPROACHING STORAGE LIMIT.LOG ARCHIVE MIGHT BEREQUIRED

ExplanationDB2 has detected a temporary lack of storage on aREADS command.


System actionThe system re-executes the READS command 10times. If lack of storage persists, the commandterminates and returns to the caller with no data.

User responseSee messages KO2O1347E and KO2O1348E for moreinformation.

KO2O1360E NEAR-TERM HISTORY DATACOLLECTOR - DATA CAPTUREFAILED WITH RC=nn, RSC=nnnn,ARSC=nn, DB2=ssid

ExplanationThe data capture request failed. The return codeRC=nn, reason code RSC=nnnn, additional reasoncode ARSC=nnnn, and DB2 subsystem identifierDB2=ssid are provided for diagnostics. RC

Meaning00

REQUEST COMPLETED

The request is complete.

04REQUEST COMPLETED/WARNING

The request was completed but warningsconditions are returned.

RSCMeaning

0004QUERY DATA IS INCOMPLETE

0008SWITCHED- NO OUTPUT DS

08REQUEST COMPLETE/NO ACTION

The request was completed but no action wastaken.

RSCMeaning

0104RETR-NO DATA AVAIL

0108RETR-INCOMPLETE DATA

010CSTORE-NO OUTPUT DATASETS

OCDRIVER REQUEST FAILED

The driver request failed.

RSCMeaning

0204INVALID DTOKEN ADDRESS

0208LOAD FAILED FOR PAPC

020CDELETE OF PAPC FAILED

0210INIT FAILEDARSC

Meaning04

NO STORAGE UNAVAILABLE08

ATTACH FAILED0C

INVALID STOP ECB10

INVALID PARM LIST14

NOT APF AUTHORIZED0214

ASSOCIATION FAILEDARSC

Meaning04

CS+CID ENQUE EXIST08

INVALID CONNID LENGTH0C

NON-UNQIUE CONNID10

INVALID SETECB14

STORAGE NOT AVAILABLE18

INPUT PARM ERROR0218

DRIVER INACTIVE021C

TERMINATION FAILEDARSC

Meaning04

DRIVER ALREADY TERM0220

DRIVER REQUEST ABENDED


0224DEFINE FAILEDARSC

Meaning04

CS ALREADY DEFINED08

STORAGE NOT AVAIL0C

CT ALREADY DEFINED10

CT NOT FOUND14

DS ALREADY DEFINED18

OBJ ALREADY DEFINED1C

INVALID PARM0228

START FAILEDARSC

Meaning04

ATTACH OF PCSV FAILED08

SET NAME NOT FOUND0C

SET ALREADY ACTIVE10

NO CONTAINER DATA14

CONTAINER ERRORS022C

STOP FAILEDARSC

Meaning04

DETACH OF PCSV FAILED08

SET NAME NOT FOUND0C

DEQUE FAILED10

SET ALREADY INACTIVE0230

SYNC REQUEST FAILEDARSC

Meaning

04SET NAME NOT FOUND

08CONTAINER NOT FOUND

0CCONTAINER SET INACTIVE

10OUTPUT NOT INITIALIZED

0234SWITCH REQUEST FAILEDARSC

Meaning04

SET NAME NOT FOUND08

CONTAINER NOT FOUND0C

CONTAINER SET INACTIVE10

OUTPUT NOT INITIALIZED14

NO CURRENT OUTPUT DS18

CURRENT DS IS EMPTY0238

CAP DQUERY CALL FAILEDARSC

Meaning04

QUERY STORAGE NOT AVAILABLE08

QUERY INPUT SPECIFIED IS INVALID10

USER REQUEST FAILEDRSC

Meaning0304

LOAD FAILED OF PAPC0308

DELETE OF PAPC FAILED030C

SERVER IS INACTIVE0310

INVALID CTOKEN ADDRESS0314

CONNECT FAILED FOR IDARSC

Meaning


04INVALID CONNECT ID

08GETMEM FAILED

0CATTACH TO PRDR FAILED

10DID NOT FIND CID

0318INVALID PTOKEN ADDRESS

031COPEN FAILEDARSC

Meaning04

OBJECT NOT FOUND08

NOT USED0C

INVALID VERSION10

GETMEM FAILED IN OPPATH

The following additional reason codes apply to"OPEN FOR OUTPUT":14

DESCRIBE > MAXIMUM1C

INVALID DESCRIPTION18

DOESNT MATCH EXISTING20

SERVER IS TERMINATING24

NOT DEFINED TO CONTAINER28

GETMEM FAILED IN CREATE2C

OUTPUT NOT INITIALIZED

The following additional reason codes apply to"OPEN FOR INPUT":40

DATASET NOT FOUND44

DATASET NOT INITIALIZED

The following reason codes apply to "RETRIEVE/STORE/QUERY/QUALIFY FUNCTIONS":0320

INVALID AREA PARM

0324INVALID AREA LEN PARM

0328NO USER BUFFERS

032CINVALID ACCESS MODE

0330INVALID START/END TIME

0334IO ERRORS ENCOUNTERED

0338INVALID ARGUMENT (RUNTIME)ARSC

Meaning04

MISSING ARGUMENT END08

COLUMN NOT FOUND0C

INV LOGICAL OPER10

INV ARGUMENT SET14

LENGTH > THAN COLUMN18

LIST MISSING COLUMN033C

RETRIEVE BUFFER UNAVAIL0340

INVALID SEQUENCE AREA0344

INVALID RPT DATE AREA0348

QUALIFY QUALIFY SUBTYPEARSC

Meaning04

INVALID QUALIFY SUBTYPE08

INVALID VALUE (NO COLUMN)0C

NO STORAGE AVAILABLE034C

UNUSED0350

INVALID PATH TYPE FOR REQ0354

USER REQUEST ABEND


0358DISCONNECT FAILEDARSC

Meaning04

ALREADY DISCONNECTED08

PC# WAS NOT FOUND OR ALREADYDISCONNECTED

035CCLOSE PATH FAILEDARSC

Meaning04

PATH ALREADY INACTIVE08

PP# WAS NOT FOUND OR ALREADYCLOSED

0360NO ARGUMENT AREA STORAGE

0364INVALID MAX RECORD PARM

0368INVALID RET OBJECT AREA

036CINVALID RET VERSION AREA

0370CAP QUERY CALL FAILEDARSC

Meaning04

QUERY STORAGE NOT AVAILABLE08

QUERY INPUT SPECIFIED IS INVALID

14INITIALIZATION ERROR

The request cannot be initiated.

RSCMeaning

0404NO STACK AREA

0408CANT OBTAIN TASK WORK

18INVALID REQUEST

The request is invalid.

RSCMeaning

0504INVALID REQUEST

System actionThe Near-Term History Data Collector subtaskprocessing terminates.

User responsePerform a near-term history log archive; repeat asneeded for all defined log data sets. If the archive doesnot resolve the problem, delete and redefine the logdata sets.

Ensure that your ARCVssid JCL members containingthe Archive JCL have been copied torhilev.RKD2PAR. Near-term history is trying toexecute the archive job from this dataset.

If the problem persists, contact IBM support.

KO2O1361E ARCHIVE Near-Term History DataCollector FILES FAILED. REDEFINEAND RETRY (CHKRETCD)

ExplanationThe data capture request failed when attempting toopen or access the log files.

System actionThe Near-Term History Data Collector processingterminates or fails to start.

User responsePerform an near-term history log archive; repeat asneeded for all defined log data sets. If the archive doesnot resolve the problem, delete and redefine the logdata sets. If the problem persists, contact IBMsupport.

KO2O1362W Near-Term History Data CollectorTEMPORARILY SUSPENDED DATACOLLECTION. NO VSAM FILES.DB2=db2

ExplanationUsually, a job is automatically submitted that deletesthe oldest file. You get this message when all files arefilled and the oldest one is not yet deleted.

System actionProcessing is halted.


User responseDelete the oldest file.

KO2O1363I Near-Term History Data CollectorRESUMED DATA COLLECTION.VSAM FILE AVAILABLE. DB2=db2



User responseNone.

KO2O1364E NEAR-TERM HISTORY DATACOLLECTOR - SEQUENTIALCOLLECTION SUSPENDED.REASON reason code

ExplanationThe Near-Term History Data Collector stoppedcollecting data to the sequential output file.


User responseEnsure there is enough space to allocate sequentialdata sets (for example, GDG).

KO2O1365I NEAR-TERM HISTORY DATACOLLECTOR - SEQUENTIALOUTPUT TO dsn

ExplanationThe Near-Term History Data Collector collectsinformation in data set indicated by dsn.


User responseNone.

KO2O1366E SEQ OUTPUT NEEDSDISP=OLD,DSN=xxx

ExplanationAn attempt to allocate a new sequential file xxx or GDGgeneration xxx(+1) failed. Another process has anexisting allocation against the file or GDG base xxx.

System actionThis message is issued once. The Near-Term HistoryData Collector retries the allocation once a second.When the other process releases its allocation, thesequential file is allocated, output is resumed, andconfirmation message Message KO2O1367I is issued.

User responseNone. If required, the holding owner of the sequentialfile or GDG base can be determined by issuing theoperator command D GRS,RES=(SYSDSN,xxx),where xxxis the DSN= value from the message.

KO2O1367I SEQ OUTPUT NOW RESUMEDDSN=xxx

ExplanationA previously locked data set has successfully beenallocated.

System actionThe Near-Term History Data Collector continueswriting IFCID trace output to the new sequential file.

User responseNone.

KO2O1369I NEAR-TERM HISTORY DATACOLLECTOR - RECORD IS TOOLONG FOR SEQUENTIALCOLLECTION IFCID = <V1> DB2subsystem = <V2>

ExplanationAn IFI record length is longer than expected.

<V1> is the name of the IFCID.<V2> is the name of the DB2 subsystem.

System actionThe record is skipped. Processing continues with thenext record.

User responseNone.


KO2O1371I <V1> RECORD IS TOO LONG FORATF DATASET COLLECTION. IFCID= <V2>

ExplanationAn IFI record length is longer than expected.

<V1> is the name of the IFCID.<V2> is the name of the DB2 subsystem.

System actionThe record is skipped. Processing continues with thenext record.

User responseNone.

KO2O1372E <V1> ACCTG CLASS(11) only validfor DB2 11 and above (IFITRACE).

ExplanationAccounting Class 11 is only valid for DB2 11 and later.

System actionNear Term History is not started for subsystem <v1>.

User responseChange Near Term History parameters to not use class11 for this DB2 subsystem.

KO2O1373E <ssid> EXCESSIVE ENQCONTENTION, SEQ ProcessingTemporarily Suspended

ExplanationWhile Near Term History (NTH) was writing to asequential data set, the processing was delayed forover 10 seconds waiting for a system resource. As aresult, Sequential Processing has been suspended.

System actionSequential processing will be suspended to allow allother NTH functions to continue uninterrupted. Oncethe system resource is available, SequentialProcessing will resume.

User responseWait for resource to be released. Using the D GRS,Ccommand can allow you to see what resource the

OMEGAMON collector is waiting for, and action mayneed to be taken based on the holder of the resource.

KO2O1374I <ssid> ENQ CONTENTIONRelieved, SEQ ProcessingResuming

ExplanationENQ Contention detected when earlier KO2O1373EMSG was issued has been relieved, SEQ processingwill resume. Any records processed by Near TermHistory since the KO2O1373E message was issued willnot be written to the sequential data set(s).

System actionSequential file processing has been resumed, and willpick up with the next record processed.

User responseNone

KO2O1385I SSN=ssn REQUEST=reqFROM=mod RC=ret RS=rsnTCB=addr

ExplanationThis message describes the Near-Term History DataCollector initialization process. It contains thefollowing variable information:

• ssn is the DB2 subsystem name.• req is the request string.• mod is the module name (DSNRLI or DSNCLI).• ret is the return code.• rsn is the reason code.• addr is the storage address of the requesting TCB.


User responseNone.

KO2O1400W Near-Term History Data CollectorDETECTED THAT RMF IS NOTACTIVE. 15 MINUTE INTERVAL ISUSED


ExplanationOMEGAMON XE for DB2 PE detects that RMF was notactive when INTERVAL(RMF) was specified in thecollection options member.

System actionProcessing continues and a 15 minute interval is used.

User responseActivate RMF. Near-Term History Data Collector usesRMF interval if RMF is active when the current intervalexpires.

KO2O1401W Near-Term History Data CollectorDETECTED THAT RMF IS ACTIVE.RMF INTERVAL IS USED

ExplanationOMEGAMON XE for DB2 PE detects that RMF wasactive so RMF interval was used. This messagedisplays only if RMF was not active andINTERVAL(RMF) is specified in the collection optionsmember.


User responseNone.

KO2O1402W Near-Term History Data Collector -SUBSYSTEM name IS INMAINTENANCE MODE. WAITINGFOR NORMAL RESTART

ExplanationThe Near-Term History Data Collector has beenstarted, but the DB2 subsystem to be monitored iscurrently running in maintenance mode.

System actionThe Near-Term History Data Collector sends amessage to the console and waits for the operator toreply.

User responseRead messages KO2H0001 and KO2H0003 for furtherfor instructions.

KO2O1405E Near-Term History Data Collector -DB2 CONNECT FAILED. THEMAXIMUM NUMBER OFCONNECTIONS IS REACHED

ExplanationThe maximum number of connections is reached. TheDB2 connect failed.


User responseIncrease the maximum number of connections, orrestart the Near-Term History Data Collector later.

KO2O1406E Near-Term History Data Collector -DB2 CONNECT FAILED. THESPECIFIED DB2 SUBSYSTEM ID ISNOT VALID

ExplanationThe DB2 subsystem ID specified is not valid and DB2connection failed.


User responseEnsure that the subsystem specified in the Near-TermHistory Data Collector options is active and restart thecollector.

KO2O1407E Near-Term History Data Collector -DB2 SUBSYSTEM IS NOT ACTIVEOR IS TERMINATING

ExplanationThe DB2 subsystem to be monitored is not active or isterminating.


User responseEnsure that the DB2 subsystem specified in the Near-Term History Data Collector options is active, andrestart the collector.


KO2O1408E Near-Term History Data Collector -DB2 CONNECT FAILED. USER NOTAUTHORIZED

ExplanationThe DB2 connection failed because the CommonInterface does not have authorization to connect toDB2.


User responseGrant authorization to the Common Interface, thenrestart the Near-Term History Data Collector.

KO2O1409E Near-Term History Data Collector -DB2 CREATE THREAD FAILED.PLAN NOT FOUND OR NOTAUTHORIZED

ExplanationThe plan was not found or not authorized, so the DB2Create Thread failed.


User responseEnsure that KO2vrmHP has been bound and that thenecessary authorizations have been given.

KO2O1410E Near-Term History Data Collector -DB2 CREATE THREAD FAILED. planNOT AUTHORIZED

ExplanationThe plan is not authorized for use by the CommonInterface; therefore, the Create Thread failed.


User responseEnsure that KO2vrmHP has been bound and that thenecessary authorizations have been given.

KO2O1420W Near-Term History Data CollectorDETECTED TERMINATION OF DB2SUBSYSTEM subsystem

ExplanationThe Near-Term History Data Collector detectedtermination of the indicated DB2 subsystem.


User responseNone.

KO2O1421E Near-Term History Data Collector -WORKLOAD cccccccc HAD LOOPEDMORE THAEN TEN TIMES.TERMINATING

ExplanationThe Near-Term History Data Collector detected thatone of its workloads had looped more than ten times.



KO2O1422E NEAR-TERM HISTORY DATA COLL.- WORKLOAD %%%% HADPROGRAM CHECK MORE THAN 10TIMES. TERMINATING

ExplanationThe Near-Term History Data Collector detected thatone of its workloads had a program check more thanten times.



KO2O1423W DB2 SUBSYSTEM subsystem ISNOT ACTIVE, AND NEAR-TERMHISTORY DATA COLLECTOR ISWAITING FOR IT

ExplanationThe indicated DB2 subsystem is to be monitored, butis not active at this time.


System actionThe Near-Term History Data Collector issues WTORmessage KO2H0001 and waits for a reply from theoperator.

User responseRead message KO2H0001 and take appropriateaction.

KO2O1425E Near-Term History Data Collector--DETECTED 50 VSAM LOGICALERRORS. DATA COLLECTIONSTOPPED

ExplanationProcessing of near-term history data terminates.


KO2O1426I DB2 subsystem TERMINATED.Near-Term History Data CollectorSUSPENDED DATA COLLECTION

ExplanationThe DB2 subsystem being monitored by the Near-TermHistory Data Collector was terminated. Data collectionwas stopped and will resume when this DB2subsystem is active again.

System actionThe Near-Term History Data Collector waits for theDB2 subsystem to become active again.

User responseNone.

KO2O1427I DB2 subsystem IS ACTIVE. Near-Term History Data Collector HASRESUMED DATA COLLECTION

ExplanationThe DB2 subsystem is active again, and the Near-TermHistory Data Collector has resumed data collection.

System actionData collection continues.

User responseNone.

KO2O1430E Near-Term History Data CollectorIS TERMINATING. DB2 VERSIONHAS BEEN CHANGED

ExplanationThis conflict occurs if a version change of either DB2 orOMEGAMON XE for DB2 PE is detected.


User responseDelete the near-term history files and redefine them.

KO2O1431E DB2 SUBSYSTEM id IS NOT VALID.RESPOND TO THE FOLLOWINGMESSAGES TO PROCEED

ExplanationThe DB2 subsystem to be monitored, identified by id,is not valid on this system.



KO2O1432E DB2 SUBSYSTEM id FORINSERTION IS NOT VALID.RESPOND TO THE FOLLOWINGMESSAGES TO PROCEED

ExplanationThe DB2 subsystem to which near-term history data isto be written, identified by id, is not valid on thissystem.




KO2O1433W Near-term history does notsupport ACCUMACC greater than25 (NEWINOPT)

ExplanationThe QWAR accounting rolled-up information can onlycontain ACE values for up to 25 rolled-up records.

QWAR is used by Near-term history to determine therecords to be included in a rolled up accountingrecord. If more than 25 records are rolled up, therecords that are created by the threads can neither befound nor matched with the rolled up record.

System actionNone.

User responseSpecify a maximum number of 25 for the installationparameter ACCUMACC.

KO2O1434W Near-term history does notsupport ACCUMACC with DB2 9(NEWINOPT)

ExplanationQWAR is used by Near-term history to determine therecords to be rolled up by using the installationparameter ACCUMACC. With DB2 9, a QWAR cannot becreated. Therefore roll-up processing is not possible.

System actionNone.

User responseSpecify the value NO for the installation parameterACCUMACC.

KO2O1500E CANNOT OBTAIN STORAGE FORNEAR-TERM HISTORY STATISTICSRECORD

ExplanationAdditional storage was needed to keep statistics datafor 96 intervals.

System actionProcessing continues by reusing storage for the oldestinterval.

User responseIncrease region size and restart the CI.

KO2O1501E CANNOT OBTAIN STORAGE FORNEAR-TERM HISTORY DDFSTATISTICS RECORD

ExplanationAdditional storage was needed to keep DDF statisticsdata for 96 intervals.

System actionProcessing continues by reusing storage for the oldestinterval.

User responseIncrease region size.

KO2O1520W NEAR-TERM HISTORY DATA NOTAVAILABLE: reason

ExplanationNear-term history data is not available for one of thefollowing reasons:H2 IS NOT RUNNING

The Near-Term History Data Collector is notrunning.

NO STATISTIC DATAStatistics data is not being collected.

NO DATA AVAILABLEFirst interval has not occurred yet.

NTHWORK NOT FOUNDInternal logic error.


User responsePerform the action that corresponds to the indicatedreason:H2 IS NOT RUNNING

Start the Near-Term History Data Collector.NO STATISTIC DATA

Specify STATISTICS=YES in the Near-Term HistoryData Collector options.

NO DATA AVAILABLEWait for the first interval.

NTHWORK NOT FOUNDContact IBM support.


KO2O1531W REPORT COMBINE LEVELIGNORED. COLLECTION INTERVALDOES NOT DIVIDE EVENLY INTO60 MINUTES

ExplanationThe report combine level is set to HOURLY, but theselected collection interval does not divide evenly into60 minutes.

System actionProcessing continues; OMEGAMON XE for DB2 PEignores the report combine level option.

User responseChange the report combine level to NONE on the Near-Term History Report Option panel. Or change thecollection interval (use 1, 2, 3, 4, 5, 6, 10, 12, 15, 20,or 30 minutes) and restart the Near-Term History DataCollector.

KO2O1600I OBJECT ANALYSIS COLLECTIONIS NOT ACTIVE

ExplanationObject analysis displays require object analysiscollection to be active.


User responseStart the collection by using the Start Object AnalysisCollection panel.

KO2O1601I NO OBJECT ACTIVITY LOCATEDFOR THIS COLLECTION INTERVAL

ExplanationObject analysis collection occurs on an interval basis.This message informs that no object activity hasoccurred for the current interval.


User responseNone.

KO2O1602I NO VOLUMES CONTAININGALLOCATED DB2 OBJECTSLOCATED DURING THISCOLLECTION INTERVAL

ExplanationNo volumes containing allocated DB2 objects could belocated.


User responseNone.

KO2O1603I NO OBJECTS ARE CURRENTLYALLOCATED

ExplanationNo DB2 objects allocated to DB2 were located.


User responseNone.

KO2O1604I NO DB2 I/O ACTIVITY LOCATEDFOR THIS VOLUME DURING THISCOLLECTION INTERVAL

ExplanationThe volume being viewed has not incurred any DB2 I/Oactivity during the collection interval.


User responseNone.

KO2O1605I VOLUME CONTAINS NO DB2ALLOCATED OBJECTS

ExplanationThe volume viewed no longer contains any allocatedDB2 objects.



User responseNone.

KO2O1606I NO DB2 I/O ACTIVITY LOCATEDFOR THIS OBJECT DURING THISCOLLECTION INTERVAL

ExplanationNo DB2 I/O activity could be located for the object inthe current collection interval.


User responseNone.

KO2O1607E COLLECTION NOT SUCCESSFUL.VALIDATION FAILED

ExplanationAn internal error was encountered during collection forthe display.



KO2O1608I NO OBJECTS ARE CURRENTLYALLOCATED FOR THIS DATABASE

ExplanationThe database being viewed is no longer allocated toDB2.


User responseNone.

KO2O1609I OBJECT IS NOT CURRENTLYALLOCATED TO DB2

ExplanationThe space name being viewed no longer contains anydata sets allocated to DB2.


User responseNone.

KO2O1610E EVENTMGR O2ECNTL IS NOTACTIVE. START REQUEST ISIGNORED

ExplanationOMEGAMON XE for DB2 PE could not start the object-and volume analysis collection because the EventCollection Manager O2ECNTL is not active.


User responseStart the OMEGAMON XE for DB2 PE Event CollectionManager under the O2CI. For instructions see IBMTivoli OMEGAMON XE for DB2 Performance Expert onz/OS: Configuration and Customization.

KO2O1611I START REQUEST SUCCESSFULLYPROCESSED

ExplanationThe start request for the object analysis collection wassuccessfully issued.


User responseIf message KO2O1600 recurs, check the SYSLOG dataset for O2CI messages. If necessary, contact IBMsupport.

KO2O1612I STOP REQUEST SUCCESSFULLYPROCESSED

ExplanationThe stop request for the object analysis collection wassuccessfully issued.



User responseIf object analysis remains active, check the SYSLOGdata set for O2CI messages and contact IBM support ifnecessary.

KO2O1613I MODIFY REQUEST SUCCESSFULLYPROCESSED

ExplanationThe modify request for the object analysis collectionwas successfully issued.


User responseNone.

KO2O1614E START REQUEST DENIED.COLLECTION IS ALREADY ACTIVE

ExplanationThe start request is denied because the object analysiscollection is already active.


User responseNone.

KO2O1615E STOP REQUEST DENIED.COLLECTION IS NOT ACTIVE

ExplanationThe stop request is denied because the object analysiscollection is not active.


User responseNone.

KO2O1616E STOP REQUEST DENIED.COLLECTION IS NOT ACTIVE

ExplanationThe stop request is denied because the object analysiscollection is not active.


User responseNone.

KO2O1617E VALID INTERVAL= keyword NOTLOCATED. REQUEST DENIED

ExplanationThe start request for the object analysis collectioncould not be processed because the INTERVAL=keyword was missing or not valid.


User responseCorrect the start request, by specifying a validINTERVAL= operand. Valid interval range is 1 to 9999.

KO2O1618E REQUEST COULD NOT BEPROCESSED. TRY AGAIN

ExplanationOMEGAMON XE for DB2 PE could not start the object-and volume analysis collection because the EventCollection Manager (EVENTMGR) was busy.


User responseTry issuing the request again. If the problem persists,contact IBM support.

KO2O1619I NO NEW DATA SET EXTENTACTIVITY DETECTED

ExplanationObject analysis did not acquire any new extents by anydata sets in the DB2 subsystem being monitoredduring the current interval. No new information todisplay.



User responseNone.

KO2O1620I OBJECT ANALYSIS THREADSUPPORT IS NOT ACTIVE

KO2O1621I NO THREAD ACTIVITY LOCATEDFOR THIS COLLECTION INTERVAL

ExplanationNo data has been found.


User responseNone.

KO2O1700W CAPTURE SERVER INACTIVE

ExplanationThe data capture facility is not available.



KO2O1701E CAPTURE SERVER CONNECTIONFAILED = reason

ExplanationThe near-term thread history feature could notconnect to the server for one of the following reasons:H2 NOT ACTIVE

The Near-Term History Data Collector must bestarted to access near-term thread historyinformation.

H2 NOT COLLECTING TO VSAMThe Near-Term History Data Collector must becollecting to VSAM data sets to access near-termthread history information.

INVALID CONNECT IDInternal error.

CONNECT ID NOT FOUNDInternal error.

RC=nnnn, RSC=nnnn, ARSC=nnnnInternal error. The reason code RC=nnnn, returncode RSC=nnnn, and additional reason codeARSC=nnnn are provided for diagnostics.


User responsePerform the action that corresponds to the indicatedreason:H2 NOT ACTIVE

Start the Near-Term History Data Collector.H2 NOT COLLECTING TO VSAM

Customize the Near-Term History Data Collector tocollect to VSAM data sets if use of the near-termthread history information is required.

All other reasonsCall IBM support.

KO2O1702E CAPTURE SERVER OPEN FAILED =reason

ExplanationThe near-term thread history feature could not accessthe data for one of the following reasons:OBJECT NOT DEFINED WITHIN CONTAINER

The current Near-Term History Data CollectorVSAM data sets do not contain records required forthe near-term thread history feature to functionproperly.

INVALID QUALIFY TO CAPTURE SERVICESInternal error.

UNDETERMINABLE ERRORInternal error.

CONNECT ID NOT FOUNDInternal error.


User responsePerform the action that corresponds to the indicatedreason:OBJECT NOT DEFINED WITHIN CONTAINER

Ensure that the proper VSAM data sets have beendefined to the Near-Term History Data Collector. Ifproper VSAM data sets have been defined, contactIBM support.


All other reasonsCall IBM support.

KO2O1750E INVALID ORG - DSN: dsn - MUSTBE PO

ExplanationThe characteristic of the named data set is not correct.The sequential data set must be partitioned organized(PO).


User responseChange the data set organization.

KO2O1751E DYNAMIC ALLOCATION FAILED -dsn

ExplanationThe dynamic allocation of the named data set failed.



KO2O1761E INVALID DSN: %%%%% - PLEASERE-ENTER

ExplanationThe name of the data set was entered incorrectly.


User responseCorrect the syntax of the data set name.

KO2O1762E INVALID SIZE: %%%% - PLEASERE-ENTER

KO2O1763E INVALID VOLUME ID: %%%%%.PLEASE RE-ENTER

ExplanationThe identifier of the volume was entered incorrectly, orthe volume with the specified volume identifier doesnot exist.


User responseCorrect the syntax or specify a valid volume identifier.

KO2O1764E INVALID DSN: dsname DATA SETALREADY EXISTS

ExplanationNone.


User responseSpecify a different data set name that does not alreadyexist.

KO2O1765E UNABLE TO LOAD MODULE ATRE.POSSIBLE REGION SIZE PROBLEM

ExplanationThe application trace could not be started becausethere is not enough space in the storage region.


User responseIncrease the size of the storage region.

KO2O1768E IFCID TRACE DATA SET NAMEINCOMPLETE. REENTER THETRACE REQUEST

ExplanationA complete, valid data set name is required for theoutput of an IFCID trace.

System actionThe IFCID trace request is rejected.


User responseReenter the trace request using a complete data setname.

KO2O1769I IFCID TRACE IS NOT CURRENTLYRUNNING

ExplanationThe user requested that the results of an IFCID tracebe displayed, but the trace is not active.

System actionThe IFCD command is rejected.

User responseNone.

KO2O1801E TRACE CONNECT TO DB2 FAILEDWITH RETURN CODE rc

ExplanationOMEGAMON XE for DB2 PE attempted to connect toDB2 to start an IFCID trace. The attempt to connect toDB2 failed with the return code indicated

System actionThe IFCID trace was not started.

User responseCorrect the condition that caused the failure and startthe trace again.

KO2O1802E TRACE CONNECT TO DB2 FAILEDWITH REASON CODE rs

ExplanationOMEGAMON XE for DB2 PE attempted to connect toDB2 to start an IFCID trace. The attempt to connect toDB2 failed with the reason code indicated.


User responseCorrect the condition that caused the failure and startthe trace again.

KO2O1803E TRACE OPEN PLAN FAILED WITHRETURN CODE rc

ExplanationOMEGAMON XE for DB2 PE attempted to open theplan to start an IFCID trace. The attempt to open theplan failed with the return code indicated.


User responseCorrect the condition that caused the failure and startthe IFCID trace again.

KO2O1804E TRACE OPEN PLAN FAILED WITHREASON CODE rs

ExplanationOMEGAMON XE for DB2 PE attempted to open theplan to start an IFCID trace. The attempt to open theplan failed with reason code indicated.



KO2O1805E START TRACE COMMAND FAILEDWITH RETURN CODE rc

ExplanationThe START TRACE command was issued to start anIFCID trace. The attempt failed with the return codeindicated.



KO2O1806E START TRACE COMMAND FAILEDWITH REASON CODE rs

ExplanationThe START TRACE command was issued to start anIFCID trace. The attempt failed with the reason codeindicated.




KO2O1808W TOO MANY IFCIDS SPECIFIED.LIST TRUNCATED

ExplanationThe number of IFCIDs requested to be included in theIFCID trace exceeds the maximum allowed.

System actionIFCID trace is started without some of the requestedIFCIDs.

User responseNone.

KO2O1809E TRACE DATA SET SPECIFIEDCOULD NOT BE FOUND. CORRECTAND PRESS ENTER TO PROCEED

ExplanationThe data set name specified for the IFCID trace outputdoes not exist.

System actionOMEGAMON XE for DB2 PE waits for the userresponse.

User responseEnter a valid existing data set name.

KO2O1810W TRACE DATA SET SPECIFIED HASBEEN MIGRATED. PRESS ENTERTO PROCEED

ExplanationThe data set specified for the IFCID trace output hasbeen migrated.


User responseWhen the data set recall has completed, press Enter toproceed with the IFCID trace.

KO2O1811W TRACE DATA SET SPECIFIED ISNOT QSAM. PRESS ENTER TOPROCEED

ExplanationThe data set specified for the IFCID trace output is nota QSAM data set.


User responsePress Enter to allow the correct data set name to beentered.

KO2O1901W IFI COLLECTOR MONITOR TRACEIS NO LONGER ACTIVE

ExplanationOMEGAMON XE for DB2 PE requires the monitor traceto be active to collected data.

KO2O1902E MONITOR1 AUTHORIZATIONREQUIRED. NO DATA CAN BECOLLECTED

ExplanationOMEGAMON XE for DB2 PE requires MONITOR1authorization to start the data collection process.


User responseThe system administrator should grant the necessaryauthorization.

KO2O1903E STATISTICS COLLECTOR READSFAILED. MULTIPLE RETRYATTEMPTS. READS ABANDONED

KO2O1904E IFI COLLECTOR READS FAILEDWITH RETURN CODE rc


ExplanationA READS to the IFI failed with the indicated returncode.


User responseSee message KO2O1906E. Analyze the return code,correct the problem, and retry.

KO2O1905E IFI COLLECTOR READS FAILEDWITH REASON CODE rs

ExplanationA READS to the IFI failed with the indicated reasoncode.


User responseSee message KO2O1904E. Analyze the reason code,correct the problem, and retry.

KO2O1906E IFI COLLECTOR LOAD OF moduleFAILED

Explanationmodule is either DSNALI or DSNRLI.


User responseCheck and correct the STEPLIB DD statement for themissing DB2 load library.

KO2O1907E IFI COLLECTOR LOAD OFDSNWLI2 FAILED

ExplanationOMEGAMON XE for DB2 PE could not load the requiredmodule.


User responseCheck and correct the STEPLIB DD statement for themissing DB2 load library.

KO2O1908E IFI COLLECTOR CONNECT FAILED- RETURN CODE rc


KO2O1909E IFI COLLECTOR CONNECT FAILED- REASON CODE rs


User responseIf the reason code is 00F30013, check RACF CLASSDSNR, then look for profiles xxxx.RRSAF (where xxxxis the DB2 subsystem name).

KO2O1910E IFI COLLECTOR OPEN FAILED -RETURN CODE rc


KO2O1911E IFI COLLECTOR OPEN FAILED -REASON CODE rs PLANNAME=name DB2=subsystem


KO2O1912E IFI COLLECTOR DISPLAY TRACEFAILEDIFI DISPLAY TRACE -FAILED RETURN CODE rcIFIDISPLAY TRACE - FAILED REASONCODE rs

KO2O1913E IFI START TRACE - FAILEDRETURN CODE rcIFI START TRACE- FAILED REASON CODE rs

KO2O1914W IFI COLLECTOR NO MORESTORAGE FOR BUFFER USING %%%%%

KO2O1915W IFI COLLECTOR REACHEDMAXIMUM STORAGE AMOUNT<V1> <V2> <V3> <V4> <V5> <V6><V7>


ExplanationIFI Collector did not read all of the data because themaximum buffer size was exceeded.

<V1> is the buffer size.

<V2> is the number of bytes moved to the buffer.

<V3> is the number of bytes not moved to the buffer.

<V4> is the global reason code.

<V5> is the return code.

<V6> is the reason code.

<V7> are the IFCIDS (two bytes per IFCID).

System action:Processing continues.

User response:Contact IBM support.

KO2O1916W IFI COLLECTOR TIMED OUT

ExplanationDB2 did not respond in time.

System actionThe systems retries automatically.

User responseNone.

KO2O1917E IFI COLLECTOR CRE THRD FAILED- RETURN CODE rcIFI COLLECTORCRE THRD FAILED - REASON CODErsPLAN NAME=plannameDB2=subsystem

KO2O1918I subsystem + IFI COLLECTOR (CAF)CONNECTION ESTABLISHED

ExplanationThe IFI Collector uses a different type of connectionthrough the Call Attach Facility (CAF).


User responseNone.

KO2O1920I subsystem + IFI COLLECTOR (CAF)CONNECTION TERMINATED

ExplanationThe session ended. The user is no longer connectedthrough the Call Attach Facility (CAF).

System actionProcessing ends normally.

User responseNone.

KO2O1922I subsystem + IFI COLLECTOR (CAF)FORCIBLY DETACHED

ExplanationThe call to DB2 through the Call Attach Facility (CAF)has been terminated because the program hasterminated or the subsystem server has been shutdown.


User responseNone.

KO2O1924I EPS1 <KO2PLAN> NOT USING IFIINTERFACE

ExplanationThe DB2 plan needed by OMPE has not been bound tothis DB2. OMEGAMON cannot use the IFI interface andcannot obtain complete monitoring information.


User responseNone.

KO2O1925W THE AUTHORIZATION EXIT ISACTIVE. ALL DATA ISSUPPRESSED.

ExplanationThe parameter USEUSERAUTHEXIT=Y is configured.The authorization user exit is active.

This parameter is specified in the <HILEV>.RKD2PARmember OMPEMSTR.


System actionNone.

User responseContact your administrator.

KO2O1940E WLM SERVICE XX RC: 99 - YYREASON: ZZ

ExplanationOMEGAMON XE for DB2 PE on z/OS has requestedinformation from one of the standard workloadmanager interfaces. The interface has issued anonzero return code as a result of that request.

• XX is the name of the WLM interface:

– IWMRCOLL– IWMCQRY– IWMRQRY– IWMPQRY– IWMDEXTR

• 99 is the nonzero return code:

– 04– 08– 12– 16

• YY is a short text describing the general type of error:

– WARNING– INVOCATION ERROR– ENVIRONMENTAL ERROR– COMPONENT ERROR

• ZZ is a short text describing the specific error andmay be one of the values listed in the table below.This table contains the short text string followed bythe specific return code. This specific return codemay be found in the WLM documentation in yourMVS Bookshelf Programming: Workload ManagerServices, SA22-7619.

INSUF ACCESS X'00000C0E'NOWLM X'00000401'NO MON ENV X'00000402'MON ENV NOT ALLOC X'00000403'COMPAT NO SYSEVENT RQD X'00000404'GOAL NO MON ENV X'00000405'NO PAR ENV X'00000406'RETURN CONT X'00000407'WORK NOT FOUND X'00000408'NO CONN X'00000409'OUTPUT AREA TOO SMALL X'0000040A'NO SERVERS REGISTERED X'0000040B'MON ENV LACKS INFO X'0000040C'ICS DEFAULT X'0000040D'ICS AREA TOO SMALL X'0000040E'

STATE INV DATA RET X'0000040F'TKN NO MATCH X'00000410'ENCL ACTIVE X'00000411'COMPAT MODE X'00000412'IDS DONT MATCH X'00000413'NULL CDS X'00000414'POLICY ACT IN PROGRESS X'00000415'POLICY UNDEFINED X'00000416'BAD SERV DE X'00000417'SERVER NOT REGISTERED X'00000418'SERVER ALREADY REG X'00000419'NO POL MGT X'0000041A'NOT ENCLAVE X'0000041C'BAD RES TKN X'0000041D'NO IWM SVAEA SUBRECORD X'0000041E'

EXEC ENV CHANGED X'0000041F'SYS INFO INCOMPLETE X'00000420'UNKNOWN QUEUE X'00000421'NO IWM SVSEA SUBRECORD X'00000422'DEFAULT POLICY X'00000423'SYSTEM IGNORED X'00000424'NO SCH ENV X'00000425'SCH ENV NOT FOUND X'00000426'SCH ENV NOT AVAILABLE X'00000427'NO SCH ENV DEFINED X'00000428'RESOURCE NOT FOUND X'00000429'SCH ENV NO SYSTEM X'0000042A'NO DATA X'0000042B'ETOKEN NOMATCH X'0000042C'CONTINUE RIP X'0000042D'

SERVER NOT FOUND X'0000042E'SECONDARY WORK DELETED X'0000042F'CNTL REG NOT REG X'00000430'ACTIVE SERVERS X'00000431'UNKNOWN EXPORT TOKEN X'00000432'ENC ALREADY EXPORTED X'00000433'BAD ENTRY VERSION X'00000434'NO CACHE ENTRY X'00000435'BAD BUF SIZE X'00000436'INVALID SWITCH TOKEN X'00000437'NO AFFINITY FOUND X'00000439'REGION NOT FOUND X'0000043A'SRB MODE X'00000801'XMEM USER KEY TKN X'00000802'DISABLED X'00000803'

LOCKED X'00000804'MON ENV SWITCH CONT X'00000805'MON ENV PARENT X'00000806'BAD STOKEN X'00000807'MON ENV DEP CONT X'00000808'SRB USER KEY TKN X'00000809'TCB NOT OWNER USER KEY TKN X'0000080A'BAD PL X'0000080B'MON ENV LACKS DATA X'0000080C'BAD SERV CLS X'0000080D'ARR TIME GT END TIME X'0000080E'NO USER KEY NTFY X'0000080F'EUT FRR X'00000810'NO USER KEY RPT X'00000811'BAD ASCB X'00000812'

USER KEY NO MON TKN X'00000813'USER KEY WRONG PRIM X'00000814'USER KEY WRONG SERVER X'00000815'DEP CONT EXISTS X'00000816'PAR ENV WORK RQST ABSENT X'00000817'BOTH ENV SAME TCB X'00000818'TCB ALREADY ASSOC X'00000819'CALLER NOT AUTH DEP ENV X'0000081A'CALLER NOT AUTH PAR ENV X'0000081B'CONT EXISTS X'0000081C'BAD ELT X'0000081D'BAD LU62 TKN LEN X'0000081E'NO RELATE X'0000081F'


BAD MON ENV X'00000820'BAD CONN X'00000821'

BAD PAR ENV X'00000822'DAT OFF X'00000823'AMODE 24 X'00000824'ASC MODE NOT PRIMARY X'00000825'TASK TERM X'00000826'RSVD NOT0 X'00000827'BAD VERSION X'00000828'BAD OPTIONS X'00000829'MON ENV RELATED X'0000082A'BAD # INSTANCES X'0000082B'BAD NUMBER ASCB X'0000082C'EX ST TIME GT END TIME X'0000082D'CONNECT EXISTS X'0000082E'WRONG HOME X'0000082F'BAD ALET X'00000830'

COLL SUSPENDED X'00000831'STATE INV NODATA RET X'00000832'NOT IN COMPAT MODE X'00000833'BAD ICS ALET X'00000835'MAX ENCLAVE X'00000836'USER KEY CONN TKN X'00000837'CLSFY AREA TOO BIG X'00000838'CLSFY PL TOO SMALL X'00000839'BAD ENCLAVE X'0000083A'HOME NOT OWN CONN X'0000083B'MISSING ACRO X'0000083C'BAD SERV DI X'0000083D'LEVEL MISMATCH X'0000083E'PRIMARY NOT OWN CONN X'0000083F'SERVICE NOT ENABLED X'00000840'

XMEM MODE X'00000841'NO WLM CONNECT X'00000842'SELECT IN PROGRESS X'00000843'BADMONTKN_LISTLEN X'00000844'WRONG ENCLAVE X'00000845'NO USER KEY REG X'00000846'OTHER SPACE CONNECTED X'00000847'BAD WORK UNIT TOKEN X'00000848'WLM SERV BAD APPL X'00000849'WLM SERV BAD SSN X'0000084A'WLM SERV BAD SST X'0000084B'NOT AUTH CONNECT X'0000084D'WLM SERV BAD TYPE X'0000084E'WRONG EXEC TOKEN X'0000084F'BEGIN ENV OUTSTANDING X'00000850'

SEC ENV OUTSTANDING X'00000851'EXEC TOKEN NOT CORRECT X'00000852'WLM QM BAD TYPE X'00000853'TOO MANY SELECT X'00000854'BAD NUM EU MAX X'00000855'BAD NUM EU MIN X'00000856'ALREADY IN ENCLAVE X'00000857'NO TE JOINED TCB X'00000858'ENCLAVE SUBTASK EXISTS X'00000859'SELECTED WORK ACTIVE X'0000085A'NO SERV DAREA X'0000085B'WRONG NUM EU X'0000085C'MON ENV NOT HOME X'0000085D'BAD NUM SYS X'0000085E'BAD SYSTEM L X'0000085F'

NO SYSTEM L X'00000860'QUEUE NOT DEFINED X'00000861'NO PRIOR SELECT X'00000862'NO EXEC ENV X'00000863'SECONDARY WORK EXISTS X'00000864'ROUTING TABLE EXISTS X'00000865'DUPLICATE CNTL REG X'00000866'CNTL REG ALREADY REG X'00000867'MAX CNTL REGEXCEED X'00000868'SYS TYPE NOTREG X'00000869'

GROUP NOT REG X'0000086A'NO CNTL REG X'0000086B'NO CR ROUTE TABLE X'0000086C'NO CR GROUPS X'0000086D'NOT CNTL REG X'0000086E'

INVALID SHUTDOWN X'0000086F'BAD EXPORT TOKEN X'00000870'DID NOT EXPORT OR IMPORT X'00000871'FOREIGN ENCLAVE X'00000872'WRONG SRV LMT X'00000873'WRONG MNG TSK X'00000874'TKN IN DMS MCH X'00000875'NO CPU ONLINE X'00000876'DCM NOT INITIALIZED X'00000877'BAD NUM LIMIT MAX X'00000878'BAD NUM LIMIT MIN X'00000879'NO Q SERVER X'0000087A'UNEXPECTED CALL X'0000087B'WRONG AE LIMITS X'0000087C'BAD NUM AESRVMAX X'0000087D'

BAD REG TOKEN X'00000880'ENCLAVE PREVIOUSLY DELETED X'00000881'TOO MANY REGISTRATIONS X'00000882'NO STG X'00000C01'REPORTING SUSP X'00000C02'SYSEVENT NO WORK ELT X'00000C03'NTFY NO WORK ELT X'00000C04'RPT NO WORK ELT X'00000C05'NO END TIME X'00000C06'NO ARR TIME X'00000C07'NO EX TIME X'00000C08'NO RES MGR X'00000C09'SUSPENDED X'00000C0A'STATE CHANGED X'00000C0B'CLASSIFY FAIL X'00000C0C'

BAD CLSFY X'00000C0D'CDS NOT AVAIL X'00000C0F'CDS TOO SMALL X'00000C10'ONE SYSTEM UNABLE X'00000C11'NO GOAL MODE SYSTEMS X'00000C12'POLICY NOT AVAIL X'00000C13'NO WORK SHUTDOWN X'00000C14'SERVER UNAVAIL X'00000C16'SEC ENV CREATE FAILED X'00000C17'SEC ENV DELETE FAILED X'00000C18'NOT SEC AUTH CONNECT X'00000C19'APPL NOT DEFINED X'00000C1A'APPL NOT SST X'00000C1B'SERVER NOT STARTED X'00000C1C'QMGR NOT ACTIVE X'00000C1D'

HIGHER VERSION LEVEL X'00000C1E'SERVER EXISTS X'00000C1F'DEP CLASSIFY FAIL X'00000C20'NO MON ENV ERR X'00000C21'APPL ENV QUIESCED X'00000C22'IND LOCAL SYSTEM X'00000C23'PROCNAME BLANK X'00000C24'APPL ENV STOPPED X'00000C25'ROUTER NOT ACTIVE X'00000C26'FSV REQ INCOMPAT X'00000C27'BAD SERVICE CLASS X'00000C28'SV DEF ID WRONG X'00000C29'DUPLICAT QUEUE X'00000C2A'TOKEN NOT CURRENT X'00000C2B'CANNOT ACCESS POLICY X'00000C2C'

BAD PERFORMANCE GROUP X'00000C2D'WRONG MODE X'00000C2E'SYSTEM SPACE X'00000C2F'DUPLICATE JOBS X'00000C30'WRONG ASID X'00000C31'NOT ELIGIBLE FOR SRV CLASS X'00000C32'OTHER SUBSYS REG QUEUE X'00000C33'


NO SELECTION X'00000C34'NOT SEC AUTH SERV REG X'00000C35'STRUCTURE UNAVAILABLE X'00000C36'STRUCTURE FULL X'00000C37'UP LEVEL OBJECT X'00000C38'TOO MANY SYSTEMS X'00000C39'INVALID SUBSYSTEM X'00000C3A'STOP TASK X'00000C3B'

CONFIG FAILED X'00000C3C'ENTRY NOT PROCESSED X'00000C3D'TOO MANY SWITCHES X'00000C3E'LDE INVALID X'00000F01'CDE INVALID X'00000F02'XDE INVALID X'00000F03'SDE INVALID X'00000F04'SXDE INVALID X'00000F05'CDE TABLE INVALID X'00000F06'CDEX INVALID X'00000F07'

System actionSee Workload Manager Services, SA22-7619.

User responseSee Workload Manager Services, SA22-7619.

KO2O1941E EXCHANGE LAYER CALL FAILED -RETURN CODE rc

ExplanationAn internal inter-program communication erroroccurred.


User responseSee KO2O1942E. Contact IBM support.

KO2O1942E EXCHANGE LAYER CALL FAILED -REASON CODE rc

ExplanationAn internal inter-program communication erroroccurred.


User responseSee KO2O1941E. Contact IBM support.

KO2O1943E FUDA SERVICES LICENSE CHECKFAILED, EXITING (O2INITE)

ExplanationThe OM PE FUDA service failed to verify the licenseduring server initialization.

System actionProcessing ends. If this message is preceded bymessage FPEV0137E, the license is not valid. If not,the security setup might have been done incorrectly.

User responseEnsure that the license FMID is installed properly andthe security setup is correct.

KO2O1944I SQL PA ANALYSIS INITIATED(OSQPSQPI). REPORT=nnnnnnPLAN=ppppppppPACKAGE=kkkkkkkk

ExplanationAn SQL PA report has been generated for the currentSQL statement.

User responseNone.

KO2O1945I NO ACTIVE SQL STATEMENT TEXTFOUND. REPORT NOT INITIATED.(OSQPSQPI)

ExplanationAn attempt was made to initiate an SQL PA analysisfrom Active Thread display (panel ZSQL), EDMSnapshot (panel EDDM3), or Near Term history (panelZHTCALL.), but there was no active SQL statementbeing displayed.

Reports can only be initiated when a current SQLstatement is displayed.

User responseNone.

KO2O1946I PERFORMANCE WAREHOUSEBUSY OR NOT STARTED. PRESSENTER TO RETRY REQUEST(SQPSQPI)

ExplanationAn attempt was made to initiate an SQL PA analysisfrom Active Thread display (panel ZSQL), EDMSnapshot (panel EDDM3), or Near Term history (panel


ZHTCALL.), but the interface could not initiate therequest with PWH.

User responseEnsure that PWH is properly configured for SQL PAusing the Configuration Tool (formerly ICAT). If PWHhas been properly configured, hit Enter to retry therequest.

KO2O1947W NO REPORTS FOUND FORCURRENT USER (O2OSQP)

ExplanationOption V was selected to display a list of SQL PAreports, but no reports were found that either had acreator ID equal to the current user ID or had a scopeof Public.

User responseNone.

KO2O1948I NO REPORT OUTPUT GENERATEDFOR xxxxxxxx (O2OSQP)

ExplanationNo output was generated for the file selected.xxxxxxxx is one of the following: ANLREP, ANLQLM,ANLQTRC, ANLELOG. ANLLSQL, or JOBERR.

User responseExcept for JOBERR, refer to the appropriate SQL PAdocumentation for information on how each file isgenerated. JOBERR is only available when an SQL PAreport has a status of FAILED.

KO2O1949E PERFORMANCE WAREHOUSEREQUEST FAILED (O2OSQP).variable message text

ExplanationACTION IGNORED. REPORT NOT RUNNING

An attempt was made to cancel a report, but thereport was no longer in RUNNING status.

ACTION IGNORED. REPORT HAS NOT COMPLETEDAn attempt was made to view, delete or modify thescope of a report that has not yet completed.

SQL PA NOT CONFIGURED ON THIS SYSTEMAn attempt was made to initiate an SQL PAanalysis from Active Thread display (panel ZSQL),EDM Snapshot (panel EDDM3), or Near Termhistory (panel ZHTCALL.), but the interface couldnot initiate the request with PWH.

REPORT NOT WITHIN SCOPEAn attempt was made to alter a report by someoneother than the creator of the report. Only thecreator of a report may modify or delete it.

REQUEST=rrrrrrrr RETURN CODE=xxxxxxxx REASONCODE=xxxxxxxx

An internal error occurred during processing.

User responseACTION IGNORED. REPORT NOT RUNNING

None.ACTION IGNORED. REPORT HAS NOT COMPLETED

Wait for the report to complete before performingthe action.

SQL PA NOT CONFIGURED ON THIS SYSTEMEnsure that PWH is properly configured for SQL PAusing the Configuration Tool (formerly ICAT).

REPORT NOT WITHIN SCOPENone.

REQUEST=rrrrrrrr RETURN CODE=xxxxxxxx REASONCODE=xxxxxxxx

Contact IBM support.

KO2O1950E PWH/CAF SUBTASK FAILURE

ExplanationAn internal error occurred during processing and anSVC dump has been generated.


KO2O1957E NO ENTRY FOUND FOR IFCID nnnn

ExplanationNo entry found for IFCID nnnn, where nnnn could be0197.


KO2O1958E NO DATA ADDRESS FOUND FORIFCID nnnn

ExplanationNo data address found for IFCID nnnn where nnnncould be 0197.



KO2O1959E NO DB2 MESSAGE nnnn

ExplanationNo DB2 Message nnnn, where nnnn could be anaddress or a counter value.


KO2O1961W Not a Data Sharing Group - Goption not valid

ExplanationIn the information line after the DB2 subsystem nameG for group mode may only be entered for subsystemsthat are members of a data sharing group.

System actionThe field is set to value S for a single DB2.

User responseEnter group code G only for data sharing groupmembers.

KO2O1962I Group mode must be S or G

ExplanationIn the information line after the DB2 subsystem nameonly G for group mode or S for a single DB2 might beentered.

System actionThe field is set to value S for a single DB2.

User responseEnter group code S or G.

KO2O1963E OMEGAMON Server subtaskPESERVER not active.

ExplanationThe PESERVER subtask is not active. It might havebeen stopped during initialization with the followingcommand:

/F <STC_Name>, P PESERVER

Or the START PESERVER command was not executed,or it failed.

System actionMonitoring is not available.

User responseStart the PESERVER subtask by using the followingcommand:

/F <STC_Name>, S PESERVER

Ensure that the message FPEV0000I appears duringinitialization.

KO2O1368E NEAR-TERM HISTORY DATACOLLECTOR - INVALID RECORDRECEIVED

ExplanationAn IFI record with a length longer than expected orzero has been received.

System actionThe record is skipped and processing continues withthe next record.

User responseNone.

KO2O1964I Backlevel Near-Term History dataset(s) detected. Resetting.

ExplanationNear-term history VSAM data sets from a previousversion of Near-Term History Data Collector werefound. These data sets are not compatible with thecurrent Near-Term History Data Collector.

System actionThe near-term history VSAM data sets are cleared andthe Near-Term History Data Collector will start.

User responseNone.

KO2O1965I Number of threads displayedtruncated, LROWS limit value ofnnnn exceeded (source)

ExplanationThe number of threads running in DB2 is larger thanthe LROWs value (nnnn) used. source is the sourcemodule returning this message.


System actionThe number of DB2 threads is truncated by thecollector to adhere to the requested LROWs limit andto avoid long response times. The threads beingdisplayed are in random order as received by the DB2IFI READS call that is issued by the OMEGAMONCollector PE Server subtask.

User responseUse appropriate filtering to limit the data in the threadsummary displays. For example, by specifying a

specific plan name (PLAN) or authorization ID(AUTHID) in panel ZFILT, the thread data is filtered inDB2 and only the qualifying threads are shown.

You can retain filter specifications in a user profile, oruse an existing profile at logon time by using the"data(user=xx)" logon option, where xx is the profilename. For example, the command logonapplid(ipomd2c) data(user=MT,LROWS=500)opens a session that shows up to 500 threads(LROWS=500) and use the user profile "MT"(user=MT). For more information, see the ZFILT panelhelp.

KO2R - Capture Server messagesKO2R0010E SERVER PARAMETERS NOT VALID

ExplanationThe capture server component could not initialize aserver component because of invalid linkageparameters.

System actionThe capture server component terminates.


KO2R0011E CANNOT SET RECOVERYENVIRONMENT

ExplanationThe capture server component could not initialize aserver component because of recovery environmenterrors.



KO2R0012E CANNOT SET UP ENVIRONMENT

ExplanationThe capture server component could not initialize aserver component because of program environmenterrors.



KO2R0013E STORAGE UNAVAILABLE FORSTACK

ExplanationThe capture server component could not initialize aserver component because of a shortage of virtualstorage.



KO2R0021U ENVIRONMENT NOT SUPPORTEDmodule FOR ROUTINE routine

ExplanationThe capture server component could not load theindicated module when calling the indicated routinebecause the operating system environment is notsupported.




KO2R0022U CANNOT LOAD MODULE moduleFOR ROUTINE routine

ExplanationThe capture server component could not load theindicated module when calling the indicated routinebecause the load module was not found.



KO2R0023U CANNOT INITIALIZE LOADMODULE module FOR ROUTINEroutine

ExplanationThe capture server component detected aninitialization error in the indicated module when callingthe indicated routine.



KO2R0024U VECTORS NOT SET BYINITIALIZATION PROGRAMmodule FOR ROUTINE routine

ExplanationThe capture server component detected aninitialization error for the indicated module whencalling the indicated routine. The program vectorswere not correctly set by the initialization routine.



KO2R0100I DRIVER INITIALIZED

ExplanationThe capture server component is initialized.


User responseNone.

KO2R0101E DRIVER INIT FAILED - RS reason1RI reason2 LR return

ExplanationThe capture server initialization request failed.RS reason1

Reason code.RI reason2

Additional reason information.LR return

Lower routine return code.



KO2R0102I DRIVER TERMINATED

ExplanationThe capture server component has terminated.


User responseNone.

KO2R0103E DRIVER TERM FAILED - RSreason1 RI reason2 LR return

ExplanationThe capture server termination request could notterminate normally.RS reason1

Reason code.RI reason2

Additional reason information.LR return

Lower routine return code.




KO2R0104W SET NOT STARTED (reason) - setname

ExplanationThe capture server start request failed for theindicated set name for one of the following reasons:SET NOT FOUND

The indicated capture container set name was notfound.

SET ALREADY STARTEDThe indicated capture container set name wasalready started.



KO2R0105I SET STARTED - set name connect id

ExplanationThe capture server start request is completed for theindicated SET name and connect ID.


User responseNone.

KO2R0107I SET STOPPED - set name connectid

ExplanationThe capture server resources for the indicated SETname and connect ID have been released/stopped.


User responseNone.

KO2R0108W SET NOT STARTED (NOCONTAINERS STARTED) - set nameconnect id

ExplanationThe capture server resources for the indicated SETname and connect ID were not allocated/started.


User responseNone.

KO2R0109W SET STARTED (ONE OR MORECONTAINERS NOT STARTED) - setname connect id

ExplanationThe capture server resources for the indicated SETname and connect ID were not completely allocated/started.


User responseNone.

KO2R0110E SET TERMINATION FAILED - setname connect id

ExplanationThe capture server resources for the indicated SETname and connect ID could not be successfullyterminated.


User responseNone.

KO2R0111W SET NOT STARTED (NO DATAAVAILABLE - set name connect id


ExplanationThe capture server resources for the indicated SETname and connect ID were started for Read access,but there was no capture data available.


User responseNone.

KO2R0112I FORMAT STARTED FOR DATA SET -Data Set Name

ExplanationA new linear data set is formatted so it can be used bythe Near Term History collector.

KO2R0120E NO OUTPUT DATA SETSAVAILABLE FOR CONTAINER name

ExplanationThe capture server has detected that no captureoutput data sets are available for the indicatedcontainer.


User responseIssue the following modify command ompestc,FH2Db2ssid,LISTH2DS where ompestc is the collectortask name and Db2ssid is the Db2 subsystem name.Then delete and define any files that are markedUNAVAIL.

KO2R0121W CONTAINER NOT STARTED FORname - reason

ExplanationThe capture server could not start the indicatedcontainer for one of the following reasons:NO DATA AVAILABLE

The container was started for Read access, but nodata was available.

NO DATA SETS STARTEDNo data sets started because of errorsencountered with capture data sets.

PWTR ATTACH FAILEDUnable to attach the PWTR subtask.

UNABLE TO INIT OUTPUTUnable to initialize output.


User responsePerform the action that corresponds to the indicatedreason.

KO2R0123E START FAILED FOR DATA SETdsname - reason

ExplanationThe capture server could not start the indicatedcapture data set for one of the following reasons:ALLOCATION FAILED return code

The indicated data set could not be dynamicallyallocated.

NOT AUTHORIZED FOR UPDATEThe user does not have Update access to the dataset.

NOT AUTHORIZED FOR READThe user does not have Read access to the dataset.

OPEN FAILED - CHECK DS TYPEThe data set may not be a linear data set; checkthe data set organization type.

DATA SET IS NOT LINEARThe capture data set is not a linear data set.

PRIMARY EXTEND IS TOO SMALLThe capture data set is a linear data set; howeverthe indexes and data portions could not be built.

DIV ERROR return code reason codeData-in-virtual request failed with the indicatedreturn and reason codes.

DATA SET IS ALREADY IN USEAn attempt to start the data set for Update accessfailed because the data set is already being usedfor Update access.

System actionThe start request is terminated.

User responsePerform the action that corresponds to the indicatedreason:ALLOCATION FAILED return code

Correct the data set name, and restart the captureserver.


NOT AUTHORIZED FOR UPDATEVerify that the proper authority is given to the dataset.

NOT AUTHORIZED FOR READVerify that the proper authority is given to the dataset.

OPEN FAILED - CHECK DS TYPECheck the data set organization; the data set mustbe defined as a linear VSAM data set.

DATA SET IS NOT LINEARSpecify the name of a linear data set, and restartthe capture server.

PRIMARY EXTEND IS TOO SMALLUse a larger data set.

DIV ERROR return code reason codeVerify that the data set is a linear VSAM data set. Ifit is, contact IBM support. Otherwise, redefine thedata set as a linear data set.

DATA SET IS ALREADY IN USEVerify that the data set is correctly being used bythe capture server.

KO2R0124W WARNING FOR DATA SET dsname -3390 TRK SIZE USED device type

ExplanationThe capture server started the data set, but the dataset is on an unknown device type. This may cause aperformance degradation.



KO2R0125W STOP FAILED FOR DATA SETdsname - reason

ExplanationThe capture server could not successfully stop theindicated data set for one of the following reasons:DEALLOC FAILED return code

The dynamic deallocation failed.DIV ERROR return code reason code

Data-in-virtual request failed with the indicatedreturn and reason codes.

System actionProcessing continues, but all resources for the data setmay not be released.


KO2R0126W VALIDATE FAILED FOR DATA SETdsname - reason

ExplanationThe capture server could not successfully validate theindicated capture data set for one of the followingreasons:DUPLICATE VALIDATION TIME

A duplicate validation time exists. This may be theresult of a duplicate data set. The data set can bearchived; the data set is not available forinteractive retrieval.

XID# IS OUT OF SYNCThe internal index directory XID# is notsynchronized with the control block XCI#. Thismay be the result of a system outage. The data setcan be archived; the data set is not available forinteractive retrieval.

XIB# IS OUT OF SYNCThe current index block XIB# is not synchronizedwith the control block XCI#. This may be the resultof a system outage. The data set can be archived;the data set is not available for interactiveretrieval.

XCI# IS CORRUPTEDThe control block XCI# is corrupted. The data setis not usable.

XID# IS CORRUPTEDThe current index directory block XID# iscorrupted. The data set is not usable.

XIB# IS CORRUPTEDThe current index block XIB# is corrupted. Thedata set is not usable.

DECOMPRESS IS UNAVAILABLEThe data set contains compressed data and thedata set is being accessed from an MVS/XAsystem. The IBM data expansion service loadmodule CSRCEXA cannot be loaded. Theprocedure for making the load module available isdocumented in the MVS/ESA ApplicationDevelopment Guide. The data set is not usable.

DATA SET VERSION UNSUPPORTEDThe capture data set is at an unsupported version.See message KO2R0131E. Verify that the mostrecent maintenance is applied to all productcomponents. The data set is not usable.




KO2R0127E FORMAT FAILED FOR DATA SETdsname - PRIMARY EXTENT ISTOO SMALL

ExplanationThe capture server could not format the capture dataset dsname because the primary extent is below theminimum size.

System actionProcessing terminates; the data set is not used.

User responseRedefine the capture data set with a primary size of aleast 3 cylinders, 45 tracks, or 370K, and restart thecapture server.

KO2R0128I CAPTURING OUTPUT ON DATASET dsname

ExplanationThe capture server has selected the indicated capturedata set for output.


User responseNone.

KO2R0129I CAPTURE DATA SET HAS BEENRESET FOR REUSE - dsname

ExplanationThe capture server has reset the indicated capturedata set for reuse.


User responseNone.

KO2R0130E DUPLICATE OBJECT ON DATA SETdsname - object version

ExplanationThe capture server has detected that the capture dataset has a duplicate object and version that exists inother data sets, but the data description does notmatch all other capture data sets.



KO2R0131E VERSION OF CAPTURE DATA SETNOT SUPPORTED - DATA SETversion1 CAPTURE version2

ExplanationThe capture server has detected that the capture dataset was created, but it is at an unsupported version.The format version of the capture data set is version1;the latest version supported by the current capturemodule is version2.



KO2R0132W CAPTURING OUTPUT ON LASTAVAILABLE DATA SET FORCONTAINER name

ExplanationThe capture server is capturing output on the lastavailable data set.


User responseVerify that all full capture data sets are archived.

KO2R0133I CAPTURE DATA SET IS REUSABLE- dsname

ExplanationThe capture server has detected that the indicatedcapture data set is now reusable.



User responseNone.

KO2R0134E VSAM OBJECT DEFINITIONCHANGED. PLEASE R-ECREATEVSAM DATASET(S). RC=12

ExplanationThe VSAM object definition has changed afterinstallation of PTF UK26200.


User responseRe-create H2 VSAM data sets by using the sample JCLdescribed in the README file accompanying the PTF.

KO2R0135E CAPTURE OPEN OBJECT FAILURE- RC=retcode, msgText


System actionAn SVC dump was generated.

User responseSend the SVC dump with retcode and msgText to IBMsupport center.

KO2R0140W SWITCHING FROM DATA SETdsname - reason

ExplanationThe capture server is switching from the indicatedcapture data set for one of the following reasons:DATA SET IS FULL

The capture data set cannot be extended.OBJECT DIRECTORY IS FULL

No more objects can be contained in the data set.INDEX DIRECTORY IS FULL

All usable space in the index directory blocks areused.

USER REQUESTA dynamic request for switch has been requested.


User responsePerform the action that corresponds to the indicatedreason:DATA SET IS FULL

None.OBJECT DIRECTORY IS FULL

Contact IBM support.INDEX DIRECTORY IS FULL

None.USER REQUEST

None.

KO2R0141W SWITCH IS REJECTED. CAPTURESERVER IS TERMINATING

ExplanationThe capture server switch request was rejectedbecause the capture server is terminating.


User responseNone.

KO2R0142W USER SWITCH REQUESTREJECTED. NOT CURRENTLYCAPTURING OUTPUT TOCONTAINER name

ExplanationThe capture server user switch request was rejectedbecause the capture server is not currently capturingoutput for the indicated container.


User responseNone.

KO2R0143W USER SWITCH REQUESTREJECTED. CURRENT OUTPUTDATA SET IS EMPTY FORCONTAINER name


ExplanationThe capture server user switch request was rejectedbecause the current capture data set is empty.


User responseStop the capture server if the data set must bedeallocated.

KO2R0200E DIV I/O ERROR. DATA SETdsname. DIV ERROR return codereason code

ExplanationData-in-virtual request failed with the indicated returnand reason codes.



KO2R0201E CAPTURE DATA SET TRUNCATED.S0C1 ABEND IN PROGRESS. SAVETHE DUMP AND CALL IBMSUPPORT




KO2R0900E ERROR DETECTED BY moduleSxxxx Uuuuu RC=yyyyyyyyPSW=pppppppp pppppppp ATroutine +offset level

ExplanationAn abend has been detected by a capture servercomponent.module

Module affected.

SxxxxSystem abend code.

UuuuuUser abend code.

RC=yyyyyyyyReason code.

AT routine +offsetModule in error and its offset.

levelMaintenance level of the module in error.



KO2R1142E VSAM ERROR: n ON m RETURNCODE=rc REASON CODE=rsFDBK=x

ExplanationThe capture server could not write on the VSAM dataset.


User responseNone.

KO2R1146E ALLOCATION FAILED, DSN:dsname REASON CODE: rs

ExplanationThe dynamic allocation of the named data set failed.The supervisor call instruction (SVC) 99 returned withthe named reason code.



KO2R1147E ATF CAPTURE ERROR: n ON mRETURN=rc REASON=rs INFO=info


ExplanationThe capture server could not write on the VSAM dataset.


User responseNone.

KO2R1150I NUMBER OF TRACE RECORDSWRITTEN: n

ExplanationThe Application Trace Facility (ATF) successfully wroten trace records.

System actionNone.

User responseNone.

KO2R1151I NUMBER OF UOW RECORDSWRITTEN: n

ExplanationThe Application Trace Facility (ATF) successfully wrotenUnit of Work (UOW) records.

System actionNone.

User responseNone.

KO2R1152I NUMBER OF TRACE RECS LOSTDUE TO VSAM TASK: n

ExplanationThe Application Trace Facility (ATF) lost n tracerecords produced by DB2 because of high volume.

System actionNone.


KO2R1153I NUMBER OF UOW RECS LOST DUETO VSAM TASK: n

ExplanationThe Application Trace Facility (ATF) lost nUnit of Work(UOW) records because of high volume UOWs in DB2.

System actionNone.


KO2R1154I NUMBER OF TRACE RECS LOSTDUE TO IFCARLC: n

ExplanationData loss occurs when the buffer fills before themonitor program can obtain the data. DB2 does notwait for the buffer to be emptied, but, instead, informsthe monitor program on the next READA request (inthe IFCARLC field of the IFCA) that the data has beenlost.

System actionNone.

User responseHave a high enough dispatching priority that theapplication can be posted and then issue the READArequest before significant data is lost.

KO2R1155I DSN USED FOR CAPTURE : dsname

ExplanationA user has captured an application trace to data setdsname.

System actionThe trace is completed.

User responseNone.


KO2R0247W Capture Server Failure - Invalidstart or end times

ExplanationA near-term history record that was being written didnot pass the date validity checks. The thread start orend date was zero, or the end data was greater thanthe start date.

System actionThe record is skipped and not written to the near-termhistory data set and processing continues with thenext record.

User responseNone.

KO2R136E Capture object open failure -Description mismatch. Redefinefile

ExplanationNear-term history files were created by a previousmaintenance level of OMEGAMON. The VSAM filesmust be deleted and redefined.


User responseRedefine the VSAM files.

KO2R137E Capture object open failure -Server terminating

ExplanationThe Near-Term History Data Collector has terminated.



KO2R138E Capture server failure - Unable tocreate object - Object not definedto container




KO2R139E Capture server failure - Unable tocreate object - Storage unavailable




KO2R240E Capture server failure - Containeris not initialized for output




KO2R241E Capture object open failure - Dataset not found



User responseCheck the configuration.

KO2R242E Capture server failure - Data set isnot initialized for read





KO2R243E Capture server failure - Invalidarea parameter

ExplanationThe Near-Term History Data Collector has detected aninvalid parameter.

System actionThe Near-Term History Data Collector skips processingthis request. A dump is produced.


KO2R244E Capture server failure - Invalidarea length parameter

ExplanationThe Near-Term History Data Collector has detected aninvalid length.

System actionThe Near-Term History Data Collector skips processingthis request. A dump is produced.


KO2R245E Capture server failure - No userbuffers




KO2R246E Capture server failure - Invalidaccess path not open for input




KO2R247E Capture server failure - Invalidstart or end times

ExplanationThe Near-Term History Data Collector has detected arecord with an invalid time.

System actionThe Near-Term History Data Collector skips processingthis record. A dump is produced.


KO2R248E Capture server failure - I/O errorsencountered on data




KO2R249E Capture server failure - Invalidargument list detected





KO2R250E Capture server failure - Cannotobtain retrieve buffer




KO2R251E Capture server failure - Invalidsequence return area




KO2R252E Capture server failure - Invaliddata return area




KO2R253E Capture server failure - Invalidqualify subtype




KO2R254E Capture server failure - Invalidpath type for request not open foroutput




KO2R255E Capture server failure - Userrequest abended




KO2R256E Capture server failure - Disconnectfailed. Already disconnected




KO2R257E Capture server failure - Primarypath failed to close





KO2R258E Capture server failure - Unable toobtain argument list area




KO2R259E Capture server failure - Invalidmaximum record parameter




KO2R260E Capture server failure - Invalidobject return area




KO2R261E Capture server failure - Invalidversion return area




KO2R262E Capture server failure - Invalidrequest type




KO2S - Storage Manager messagesKO2S0500E OSNP SDUMPX Failure. RC:

XXXXXXXX

ExplanationThe SDUMPx service request failed. The SDUMPxmacro return codes and reason codes are documentedin the z/OS MVS Programming: Authorized ServiceManuals.

For example:

RC: 00000B08Return code: X'08'Reason code: X'0B''

The SDUMPx macro FAILRC parameter is specified.

System actionThe SVCDUMP is not generated.

User responseInvestigate the reason for the abend. Contact IBMSupport to report the problem.

KO2S0501E GCAM Primary-Level Name/Tokenpair CREATE failure. RC:XXXXXXXX

ExplanationA Create Name/Token Pair failure occurred during aprimary-level name/token request.


System actionThe OMPE subtask terminates with abend code S0C3.


KO2S0503I GCAM primary-level Name/Tokenpair created.

ExplanationA Create Name/Token Pair request for a primary-levelname/token pair was successful.

User responseNone.

KO2S0504E GCAM primary-level Name/TokenRETRIEVE failure. RC: XXXXXXXX

ExplanationA Retrieve Name/Token Pair failure occurred for aprimary-level name/token pair request.



KO2S0505E GCAM primary-level Name/TokenDELETE failure. RC: XXXXXXXX

ExplanationA Delete Name/Token Pair failure occurred for aprimary-level name/token pair request.



KO2S0506E GCAM Primary-Level Name/Tokenrequest failure

ExplanationThe Name/Token request is invalid.



KO2S0507I GCAM Primary-Level Name/Tokenpair deleted.

ExplanationThe Delete Name/Token Pair request was successful.

User responseNone.

KO2S0508E OSNP LMOD: xxxxxxxx, CSECT:xxxxxxxx, OFFSET: xxxxxx

ExplanationThe SDUMPx service request failed for the specifiedsymptom record. Review message KO2S0500E.



KO2S0509E SDMP LMOD: xxxxxxxx, CSECT:xxxxxxxx, OFFSET: xxxxxx

ExplanationThe SDUMPx service request failed for the specifiedsymptom record. Review message KO2S0550E.



KO2S0510I DSPM Dataspace XXXXXXXXcreated

ExplanationThe indicated data space was successfully created.


User responseNone.

KO2S0511E DSPM DSPSERV Request Failure.(SCOPE = COMMON ) RC:XXXXXXXX

ExplanationA DSPSERV CREATE failure occurred for aSCOPE=Common data space request.



KO2S0512E DSPM DSPSERV Request Failure.(SCOPE = ALL) RC: XXXXXXXX

ExplanationA DSPSERV CREATE failure occurred for a SCOPE=ALLdata space request.



KO2S0513E DSPM DSPSERV Request Failure.(SCOPE = SINGLE) RC: XXXXXXXX

ExplanationA DSPSERV CREATE failure occurred for aSCOPE=SINGLE data space request.



KO2S0514E DSPM ALESERV PASN-AL ADDFailure. RC: XXXXXXXX

ExplanationAn ALESERV ADD failure occurred for a PASN-ALrequest.



KO2S0515E DSPM ALESERV DU-AL ADDFailure. RC: XXXXXXXX

ExplanationAn ALESERV ADD failure occurred for a DU-AL request.



KO2S0516I DSPM Dataspace XXXXXXXXdeleted

ExplanationThe indicated data space was successfully deleted.

User responseNone.

KO2S0517E DSPM DSPSERV XXXXXXXXDELETE Failure. RC: XXXXXXXX

ExplanationA DSPSERV DELETE failure occurred for the indicateddata space.



KO2S0518I DSPM Dataspace XXXXXXXXadded to PASN-AL

ExplanationThe indicated data space was successfully added tothe PASN-AL.


User responseNone.

KO2S0519I DSPM Dataspace XXXXXXXXadded to DU-AL

ExplanationThe indicated data space was successfully added tothe DU-AL.

User responseNone.

KO2S0520E DSPM Dataspace XXXXXXXXaccess list DELETE Failure. RC:XXXXXXXX

ExplanationA ALESERV DELETE failure occurred for the indicateddata space.



KO2S0522E DSPM TCBTOKEN Service failures.RC: XXXXXXXX

ExplanationA TCBTOKEN failure occurred for the TYPE=JOBSTEPrequest.



KO2S0523I LTCH Latch Set created.

ExplanationThe request to create a set of latches was successful.

User responseNone.

KO2S0524I LTCH Latch Set previously defined.

ExplanationA Latch Create request was previously defined.

System actionNone.

User responseNone.

KO2S0525E LTCH Latch Set CREATE Failure.RC: XXXXXXXX

ExplanationThe request to create a set of latches failed.



KO2S0526E LTCH Latch Set OBTAIN Failure.RC: XXXXXXXX

ExplanationThe request to obtain a set of latches failed.



KO2S0527E LTCH Latch Set RELEASE Failure.RC: XXXXXXXX

ExplanationThe request to release a set of latches failed.



KO2S0528E LTCH Latch Set PURGE Failure. RC:XXXXXXXX


ExplanationThe request to purge a set of latches failed.



KO2S0529I LTCH Latch Set purged.

ExplanationThe request to purge a set of latches was successful.

User responseNone.

KO2S0550I SDMP SDUMPX Failure. RC:XXXXXXXX

ExplanationThe SDUMPx service request failed.



KO2S0551E SDMP Latch Services OBTAINFailure. RC - XXXXXXXX

ExplanationThe request to obtain a set of latches failed.



KO2S0552E SDMP Latch Services RELEASEFailure. RC - XXXXXXXX

ExplanationThe request to release a set of latches failed.



KO2S0553E IFI INITIALIZATION FAILURE.TCB: <V1> DB2: <V2> RC: <V3>

ExplanationAn error occurred during the IFI initialization process.

System actionProcessing continues, but IFI processing for theindicated DB2 subsystem is terminated.


KO2S0554E IFI EXCHANGE LAYER REQUESTFAILURE. TCB: <V1> DB2: <V2>RC: <V3>

ExplanationAn error occurred during the IFI Exchange Layerprocess.

System actionProcessing continues, but IFICID data will not beavailable, and the symptoms might persist for theindicated DB2 subsystem.


KO2S0555E IFI FUDA REQUEST FAILURE. TCB:<V1> DB2: <V2> RC: <V3>

ExplanationAn error occurred during the IFI FUDA Service process.

System actionProcessing continues, but IFI processing for theindicated DB2 subsystem is terminated.



KO2S0556I CIFIMODE=IRB REQUESTBYPASSED. TCB: <V1> DB2: <V2>

ExplanationThe DB2 subsystem ID is not recognized.

System actionProcessing continues, but IFI processing for theindicated DB2 subsystem is bypassed.

User responseNone.

KO2S0557I CIFIMODE=IRB TARGET TCB:<V1> DB2: <V2>

ExplanationFor information only.

System actionNone.

User responseNone.

KO2S0558E OSNP SDUMPx Failure.

ExplanationA SDUMP(x) request failed. Message KO2S0500Econtains the corresponding return code and reasoncode.

There is a large number of reasons why the SDUMP(x)request failed. The following list contains some of themost common reasons and explanations:X'02' – Dump in Progress

On this system, another SVC dump is currently inthe capture phase.

X'03' – CHNGDUMP SuppressIn a CHNGDUMP operator command, DUMP=NO isspecified to suppress the taking of dumps.

X'04' – SLIP NODUMPFor this ABEND CODE, a SLIP trap indicates thatthe dump is to be suppressed.

X'0B' – DAE SuppressThe dump is suppressed by MVS DAE.

X'3E' – MAXSPACE ExceededThe maximum amount of storage for dumpcaptures exceeded. You might want to increase thevalue for the CHNGDUMP option MAXDUMP.

X'46' – AUX Storage ExceededThe MVS threshold of available auxiliary storageexceeded. All dumps are supressed until morethan 35% of system wide AUX storage is available.

System action:The SDUMP(x) dump request failed.

User responseCheck the messages for the reason why the requestmight have failed and consider the appropriateactions.

KO2X - Cross-Memory Module messagesKO2X0450I INITIALIZING COMMON

SERVICES


KO2X0451I SUBSCRIBING COMMONSERVICES


KO2X0452I TERMINATING COMMONSERVICES


KO2X0453I UNSUBSCRIBING COMMONSERVICES


KO2X0454I COMMON SERVICES PARTIALLYTERMINATED



KO2X0455S COMMON SERVICESINITIALIZATION FAILED

ExplanationA fatal error has occurred.


KO2Z - OMEGAMON PE Subsystem messages

KO2Z abend codesKO2Z messages might be accompanied by the following abend codes:Abend codeU2008

The current OMPE subsystem function terminated abnormally. Locate message KO2Z999E in theSYSLOG or OMPE Server job log to identify the reason code associated with this failure.

KO2Z return codesKO2Z messages might be accompanied by the following return codes:Return code0000

Request successful.0004

OMEGAMON XE for DB2 PE return code.0008

Subsystem function failed.0012

Request terminated abnormally.0016

Unexpected ABEND occurred0020

Internal failure occurred0028

OMPE Collector request failed.0256

OMPE/XCF failure occurred

KO2Z reason codesKO2Z messages might be accompanied by the following reason codes:Reason code0000

Successfully completed.0004

Invalid subsystem name specified.0008

OMPECT structure not found in system-level name/token pair.0011

OMPECT validity check error.


0016OMPE subsystem failed.

0020OMPE subsystem is inactive.

0024Mutually exclusive INITPARM parameters specified.

0028One or more INITPARM parameters are not valid.

0032Module OMPELIB cannot open the TKANMOD library.

0036ECSA storage obtain error.

0040Dynamic allocation error trying to allocate data set specified in INITPARM parameter DSN=name.

0044Incorrect input parameter string specified with the VARY OMPE,REFRESH command request.

0048OMPEMGS/LINKAGE=PC must be called within the OMPE Collector address space.

0052JCL parameter data not specified with the utility PARM= JCL keyword.

0056Invalid F/MODIFY command input specified.

0060GXL/GXE global structure update failed.

0064OMPECT control structure ECSA virtual storage obtain error.

0068Refresh processing architecture error detected.

0072Utility command not allowed from TSO/E session.

0076The XCF main task abnormally terminated. Check the OMPE Server job log for error messages insupport of this failure.

0080RKD2PAR parameter data set RDJFCB error detected.

0084RKD2PAR parameter data set Open error detected.

0088The I/O read routine could not find the specified member.

0092The I/O routine could not obtain virtual storage for a READ request.

0096Could not find enough virtual storage to read member data.

0100Member data record insert overflow error detected.

0104Ddname/DSName function error detected by initialization routine.

0108No input records found in the specified set member.


0112Could not identify the XCF component main XCFCT control structure. Structure has been overlaid.

0116XCF main task could not create, delete, or retrieve the home-level name/token pair.

0120XCF resource manager abnormally terminated.

0124XCF member query function abnormally terminated.

0128XCF member Receive request abnormally terminated.

0132Parse routine found no record data to process.

0136Parse routine detected an unrecognized record.

0140Parse routine detected an unrecognized subrecord.

0144The specified input member was not found in the specified data set.

0148Read routine SYNAD error was detected.

0152Unsupported member was specified as input member name.

0156DDN or DSN INITPARM parameter not specified.

0160Parse entry structure error has been detected.

0164SVC call caused an abend because ALLOW(NO) was specified.

0168INITPARM LIB=DSName DYNALLOC allocation error.

0172INITPARM LIB=DSName data set Open error.

0176INITPARM LIB=DSName load module LOAD error.

0180INITPARM LIB=DSName E/CSA storage obtain error.

0184OMPE/XCF status routine abnormally terminated.

0188OMPE/XCF failed to successfully create a required data space.

0192OMPE/XCF XSRE failed validity checks.

0196UCM function detected an invalid input request.

0200The subsystem initialization routine could not obtain ECSA storage for the diagnostic work areabuffers.

0204The global virtual storage list (GSL) is not currently initialized.


0208Incorrect global virtual store list element was specified with a storage release request.

0212Incorrect SSCT control block was processed by the global virtual storage list (GSL) component.

0216Invalid common subpool number was received by the global virtual storage (GSL) component.

0220Loop detected while executing a subsystem interface (SSI) subsystem routine.

0224An operator command interface storage obtain error was detected.

0228Loop detected while executing an EOT broadcast function request.

0232Loop detected while executing an EOM broadcast function request.

0236Loop detected while executing a WTO broadcast function request.

0240OMPECT control structure ESQA storage obtain error.

0244Loop detected by the subsystem initialization routine running in the MSAS address space.

0248Invalid parameter list supplied to the common message WTO processing routine.

0252Undefined message ID was passed as input to the WTO macro.

0256Internal error while processing the subsystem WTO message table repository.

0260Undefined segment error processing a subsystem WTO message request.

0264Invalid global virtual storage structure (GSL) detected.

0268Invalid ASCB(FREE=EOM) global virtual storage request was specified.

0272Invalid TCB (FREE=EOT) global virtual storage request was specified.

0276The global virtual storage list component detected that the GSL structure is not initialized.

0280A utility request was made against a subsystem that is not currently initialized.

0284No data was found to display for the specified command.

0288A subsystem request was issued against a subsystem release that does not match the currentenvironment.

0292The OMPE subsystem could not initialize the ESVT control structure.

0296The OMPE subsystem module loader routine abnormally terminated.

0300The OMPE cross-memory initialization routine abnormally terminated.


0304The OMPE subsystem loader routine could not obtain ECSA virtual storage required for commonlyloaded load modules.

0308The OMPE subsystem could not locate the OMVT vector table.

0312The OMPE subsystem loader routine could not obtain ESQA virtual storage for the CDE/XTLST controlblocks.

0316IRB timer service error. The common IRB routine abnormally terminated.

0320IRB ABTERM post error. The common IRB routine was abnormally terminated while waiting for arequest to complete.

0324Subsystem module OMPECIU abnormally terminated.

0328Subsystem module OMPERFC abnormally terminated.

0332Subsystem module OMPERFR abnormally terminated.

0336Subsystem module OMPERFS abnormally terminated.

0340Invalid PARM= JCL initialization values specified.

0344Subsystem module OMPESVS abnormally terminated.

0348Subsystem module OMPESVS abnormally terminated.

0352Subsystem module OMPEIVT abnormally terminated.

0356Message processing routine loop detected error.

0360A subsystem Refresh request did not complete.

0364An invalid OMPE subsystem name was specified by a utility function.

0368The requested task to be attached by the Attach service request failed while processing in IRB mode.

0372Lock manager routine abnormally terminated.

0376IXCQUERY failed to obtain a buffer large enough to hold group member data.

0380IXCQUERY group NO_MEMBER service request call failed.

0384IXCQUERY group NO_MEMBER service request found no member records in QUAH#REC field.

0388Group user SRB exit routine abnormally terminated.

0392Member XMEM entry dequeue routine abnormally terminated.


0396Module OMPEXDQ XMEM loop detected. The service request abnormally terminated.

0400Module OMPEXDB XMEM loop detected. Service request abnormally terminated.

0408Module OMPEXRB Receive request failed to validate the input parameters supplied by the OMPEXRErequest SRB routine.

0412Module OMPEXRB could not load the module specified in the CALL= operand of the Send servicerequest

0416The routine specified on the CALL= operand of the Send service request returned a non-zero returncode.

0420The routine specified on the CALL= operand of the Send service request abnormally terminated.

0424Routine OMPEXRE failed to add the XCF data space to the DU-AL access list.

0428Routine OMPEXRE failed to receive the XCF response data via the IXCMSGI XCF service request.

0432The main XCF OMPEXCF Receive routine abnormally terminated. XCF Receive services are no longeravailable.

0436The main OMPEXCF task failed to load the driver function load modules.

0440The OMPEXRM resource termination manager terminated abnormally.

0444OMPETOP job step task abended referencing the OMPECT control table.

0448OMPE/XCB function failed while validity checking control structures.

0452OMPE/XCF IRB routine abnormally teminated.

0456OMPE/XCF dispatcher abnormally terminated.

0460OMPE/XCF dispatcher was entered without the LOCAL lock held.

0464OMPE/XCF dispatcher failed to locate a dispatchable TCB.

0468The Attach driver routine detected an invalid task ATTACH count.

0472The Attach driver failed to obtain the required virtual storage buffers.

0476OMPE/XCF dispatcher failed to locate a valid XRRD dispatcher entry.

0480OMPETOP job step task failed to locate the subsystem control table.

0484OMPE/XCF receive routine could not locate sending XMEM status entry.

0488OMPE/XCF receive routine detected a XMEM queue loop condition.


0492OMPE/XCF receive routine could not identify the correct Receive request.

0496OMPE/XCF receive routine failed validity checking XSRE and XRDE structures.

0500OMPE/XCF dispatcher could not retrieve a dispatcher token.

0504OMPE/XCF dispatcher failed control structures validity checks.

0508OMPETOP initialization failed server verification checks.

0512OMPETOP APF-authorization check error detected.

0516OMPE/XCF resource manager failed due to unknown function code.

0520OMPETOP failed to create/retrieve home type name token pair.

0524OMPEOPT detected an invalid user option address.

0528OMPEOPT detected an invalid user options table.

0532OMPEOPT failed while validity checking user options table.

0536OMPEOPT found zero user option table entries defined.

0540OMPEOPT specified user option not found in user options table.

0544OMPETOP could not match a subsystem name to server name.

0548Virtual storage test protection service abnormally terminated.

0552IRB service schedule failed to respond with completion indicator.

0556Event notification cell pool build request failed.

0560General I/O manager detected that the output buffer is too small to handle the request.

0564General I/O manager falied to validity check the supplied buffer address.

0568General I/O manager failed the reuest due to PSW storage key mismatch.

0572General I/O manager could not return any records to requestor.

0576Initialization failed to locate the system-level subsystem name/token pair

0588Common PC routine received invalid input parameters

0700Linkage stack storage key authorization error.

0704Linkage stack storage subpool authorization error.


0708Linkage stack request specified a zero stack size.

0712Linkage stack request size requested exceeds maximum allowed.

0716Linkage stack requested segment size exceeds stack size.

0720OMPE/XCF invalid XSRE structure ID detected in input request data buffer.

0724OMPE/XCF receive routine could not locate the target receive load module.

0728OMPE/XCF receive routine could not locate the specified receive TCB.

0732OMPE/XCF receive routine detected an invalid input request data buffer address.

0736OMPE/XCF receive routine detected an invalid input request data buffer length.

0740OMPE/XCF receive routine detected that the input request data buffer length is too small to handlethe data request.

0744OMPE/XCF receive routine detected that the target data space STOKEN is not initialized.

0748Linkage stack build service routine terminated abnormally.

0752Collector Initialization routine failed to dynamically allocate the load module library.

0756Collector initialization routine failed while closing the STEPLIB load module library.

0760Initialization routine failed to build the cell pool callable services cell pool.

0764Initialization resource manager failed to build the OMPE/XCF receive cell pool.

0768Initialization resource manager failed to build the OMPE/XCF request cell pool.

0772Collector Initialization routine failed to build the required recovery cell pool.

0776Initialization resource manager failed to build the control block access cell pool.

0780OMPE/XCF detected that an invalid SEND request load module was specified.

0784Initialization resource manager failed validity checking a subsystem control structure.

0792The IRB scheduler failed to schedule the requested service routine.

0796OMPE/XCF failed while validty checking the ZXCF collector structure.

0800Linkage stack manager failed validity checking STKE stack element.

0804Linkage stack manager failed validity checking TSTK top element structure.


0808Linkage stack manager failed validity checking BSTK bottom element structure.

0812Linkage stack manager received an invalid service request length.

0816Linkage stack manager detected a linkage stack overflow exception.

0820Linkage stack manager received an invalid stack service request.

0824Linkage stack manager failed validity checking the LSCT control table.

0828Linkage stack manager detected LSCT control table overflow.

0832Initialization resource manager failed to build the control block access key=7 cell pool.

0836Initialization resource manager failed to build the control block access key=8 cell pool.

0840The resource manager driver routine detected that an invalid request was specified.

0844Entry convention processing detected a save area stack overflow exception.

0848Subentry convention processing detected a save area stack overflow exception.

0852Entry stack processing detected a save area stack overflow exception.

0856Initialization resource manager failed to initialize the required cell pool environment.

0876OMPE/XCF receive routine detected that the receive buffer size is too small to process the incomingXCF data request.

0880OMPE/XCF receive routine detected that the receive data space is too small to process the incomingXCF data request.

0884OMPE/XCF response routine received an invalid data space ALET.

0888OMPE/XCF IRB function failed during ALESERV add request processing.

0892OMPE/XCF receive routine failed during ALESERV add request processing.

0896Initialization resource manager failed to build the required SRB cell pool.

0900Common PC routine driver failed validity checking the OMVT vector table.

0904Common PC routine driver failed validity checking the PCPL parameter list.

0908Common PC routine driver failed validity checking the SSCT control table.

0912OMPE/XCF failed to load the required control block access load module.

0916Common PC routine driver failed while processing the save area stack.


0920OMPE/XCF failed due to no OMPEXMT table entries specified.

0924Common PC routine driver received an invalid PC function entry code.

0928OMPE/XCF response routine failed validity checking the XRDE structure.

0932OMPE/XCF response routine failed validity checking the XSRE structure.

0936OMPE/XCF response routine failed validity checking the response data buffer.

0940OMPE/XCF response routine failed validity checking the response buffer size.

0944OMPE/XCF response routine failed validity checking the input buffer size.

0948OMPE/XCF response routine failed validity checking the XMEM structure.

0960OMPE/XCF receive routine failed validity checking the XMEM structure.

0964OMPE/XCF receive routine failed validity checking the XCF status entry.

0968OMPE/XCF detected an output buffer overflow condition.

0972OMPE/XCF detected that the output buffer size specified is zero.

0984Collector initialization driver failed to retrieve the OMPE/XCF connect token.

0988OMPE/XCF component failed validity checking XMEM structure.

0992Common PC routine driver failed validity checking SSCTSUSE pointer.

0996Common PC routine driver failed validity checking OMPECT structure.

1000Common SRB scheduler failed to locate target requested address space.

1004Common SRB scheduler failed to locate the address space STOKEN.

1008Common SRB scheduler failed to locate the subsystem control table.

1012Common SRB scheduler failed to validity check subsystem structures.

1016Common SRB scheduler received an invalid SRB input routine.

1020Common SRB scheduler failed to schedule the specified SRB routine.

1024Common SRB scheduler abnormally terminated.

1028Subsystem initialization routine failed validity checking the SSVT control block.

1032Subsystem initializatrion routine failed validity checking the SSCT control block.


1036Subsystem initialization routine failed validity checking SSI entry point.

1040OMPE/XCF query module detected a locked loop condition.

1044OMPE/XCF group service routine detected a locked loop condition.

1048Subsystem initialization routine failed validity checking SSI function codes.

1052Subsystem initialization routine failed validity checking SSVT address pointer.

1056Subsystem initialization routine failed to swap SSVT control blocks.

1060Subsystem initialization routine failed during SSVT compare and swap processing.

1064Subsystem initialization routine detected invalid SSVT function matrix.

1068Subsystem initialization routine failed during swap SSVT processing.

1072VTAM resource manager failed validity checking XRDE structure.

1076VTAM resource manager failed validity checking XRDE environment.

1080VTAM resource manager detected an invalid processing environment.

1084OMPE/XCF control block access response routine not specified error.

1088OMPE/XCF notifiy routine received the requested input buffers.

1092OMPE/XCF notify routine abnormally terminated.

1096VTAM resource manager failed validity checking OMPE/XCF structures.

1100VTAM resource manager detected an invalid OMPE/XCF initialization request.

1104VTAM routse manager could not locate the DB2 routing table.

1120Memory object manager received an invalid service request.

1124Memory object manager failed validity checking the SGT segment table.

1128Memory object manager failed releasing the SGT segment table.

1132Memory object manager failed validity checking requested segment length.

1136Memory object manager request exceeds maximum size allowed.

1140Memory object manager received a zero or negative segment request length.

1144Memory object manager computed a segment length that exceeds maximum allowed.


1148Memory object manager could not locate key-related segment table.

1152Memory object manager failed validity checking segment table index.

1156Memory object manager failed validity checking segment table entry.

1160Memory object manager could not locate a segment table entry.

1164Memory object manager failed validity checking the SGTE free queue.

1168Memory object manager detected an invalid SGT slot pointer.

1172Memory object manager maximum SGT/SGTE slots exceeded.

1176Memory object manager received an invalid free segment request.

1180Memory object manager failed validity checking SGTE element.

1184Memory object manager failed validity checking SGTE segment length.

1188Memory object manager failed due to incorrect storage release size.

1192Memory object manager could not locate specified storage address.

1196Memory object manager detected that the current TCB exceeded the allowed memory limit.

1200Memory object manager detected that the current address space exceeded the allowed memory limit.

1204Memory object manager abnormally terminated.

1300OMPE/XCF Send service routine failed validity checking XRDE structure.

1304OMPE/XCF Send service routine failed XRDE fetch/store access.

1308OMPE/XCF Send service routine failed validity checking TOKEN parameter.

1312OMPE/XCF Send service routine failed TOKEN fetch/store access.

1316OMPE/XCF Send service routine detected the output data buffer address is not initialized.

1320OMPE/XCF Send service routine detected the output data buffer size is not initialized.

1324OMPE/XCF Send service routine detected the output data buffer exceeds 128 MB.

1328OMPE/XCF Send service routine failed output data buffer fetch/store access.

1332OMPE/XCF Send service routine detected the input data buffer address is not initialized.

1336OMPE/XCF Send service routine detected the input data buffer length is not initialized.


1340OMPE/XCF Send service routine detected the input data buffer exceeds 60K.

1344OMPE/XCF Send service routine failed input data buffer fetch/store access.

1348OMPE/XCF Send service routine abnormally terminated due to fetch/store failure.

1352OMPE/XCF Send service routine failed to retrieve connection token.

1356OMPE/XCF Send service routine failed validity checking XMEM structure.

1360OMPE/XCF Send service routine detected that the OMPE/XCF environment is inactive.

1364OMPE/XCF Send service routine could not locate the OMPEXMT control table.

1368OMPE/XCF Send service routine failed during timer supervision processing.

1372OMPE/XCF Send service routine detected that the input buffer length exceeds data space size.

1376OMPE/XCF Send service routine did not receive a response in the specified time limit.

1380OMPE/XCF Send service routine failed establishing a timer environment.

1384OMPE/XCF Send service routine detected a locked XMEM structure loop.

1388OMPE/XCF Send service routine found an empty XMEM queue.

1392OMPE/XCF Send service routine failed to validity check XMEM structure.

1396OMPE/XCF Send service routine could not locate the target XMEM structure.

1400OMPE/XCF Send service routine timed out waiting for response data.

1404OMPE/XCF Send service routine failed validity checking token TCB address.

1408OMPE/XCF Send service routine failed validity checking token ASCB address.

1412OMPE/XCF Send service routine failed validity checking input buffer ALET.

1416OMPE/XCF Send service routine failed validity checking output buffer ALET.

1420OMPE/XCF Send service routine detected that the target XCF member is not active.

1424OMPE/XCF Send service routine abnormally terminated.

2000OMPEZ64 For the $ZSTOR64 service request, an invalid function code is specified.

2004OMPEZ64 An error occurred. The 64-bit memory object manager stopped abnormally.

2008OMPEZ64 For the $ZSTOR64 service request, an invalid CELLS= macro operand is specified.


2012OMPEZ64 For the $ZSTOR64 service request, an invalid CSIZE= macro operand is specified.

2016OMPEZ64 The CSIZE= value that is specified for the $ZSTOR64 service request exceeds themaximum value.

2020OMPEZ64 For the $ZSTOR64 service request, the FPROT= macro operand is specified. This operand isnot supported.

2024OMPEZ64 For the $ZSTOR64 service request, an invalid TCB= macro operand is specified.

2028OMPEZ64 For the $ZSTOR64 service request, an invalid MODE= macro operand is specified.

2032OMPEZ64 For the $ZSTOR64 service request, an invalid cell pool HDR= macro operand is specified.

2036OMPEZ64 For the $ZSTOR64 service request, an invalid object segment OWNER= macro operand isspecified.

2040OMPEZ64 The 64-bit memory object storage manager request stopped abnormally.

2048OMPEZ64 A shortage of memory object segments is detected.

2052OMPEZ64 The memory object segment request failed.

2056OMPEZ64 An error occurred while checking the validity of the requestor parameter list.

2060OMPEZ64 An error occurred while checking the validity of the FREE ID control field.

2064OMPEZ64 An error occurred while checking the validity of the FREE segment request.

2068OMPEZ64 An error occurred while checking the validity of the CP64 task control segment.

2072OMPEZ64 The memory segment to be freed cannot be found.

2076OMPEZ64 An internal loop is detected while scanning the CP64 control structure.

2084OMPEZ64 The 64-bit memory object storage manager CPCT control table cannot be obtained.

2088OMPEZ64 An overflow condition is detected while processing the CPCT control table.

2092OMPEZ64 An internal error occurred while processing a free extent.

2096OMPEZ64 The requested memory object cannot be built.

2100OMPEZSL The virtual storage cell pool manager received an invalid function code request.

2104OMPEZSL The virtual storage cell pool manager stopped abnormally.

2108OMPEZSL For the $ZPOOL service request, an invalid CELLS= macro operand is specified.


2112OMPEZSL For the $ZPOOL service request, an invalid CSIZE= macro operand is specified.

2116OMPEZSL For the $ZPOOL service request, an invalid CSIZE= macro operand is specified.

2120OMPEZSL For the $ZPOOL service request, an unauthorized virtual storage subpool is specified.

2124OMPEZSL For the $ZPOOL service request, an invalid BUILD macro operand is specified.

2128OMPEZSL For the $ZPOOL service request, an invalid MODE= macro operand is specified.

2132OMPEZSL For the $ZPOOL service request, an invalid HDR= macro operand is specified.

2140OMPEZSL The $ZPOOL service request is stopped abnormally.

2144OMPEZSL For the $ZPOOL service request, an invalid GET= was specified while a cell pool deletionwas in progress.

2148OMPEZSL A shortage of cell pool elements is detected.

2152OMPEZSL The cell pool cannot be extended because the limit for maximum extents is exceeded.

2156OMPEZSL An invalid cell pool GET service request is detected.

2160OMPEZSL An error occurred while checking the structure of the FREE ID data field.

2164OMPEZSL An error occurred while checking a FREE service request cell.

2168OMPEZSL The CP31 structure validity check failed.

2172OMPEZSL A previously freed cell element cannot be freed again.

2176OMPEZSL A CP31 infinite structure loop is detected.

2180OMPEZSL A CP31 infinite extent structure loop is detected.

2184OMPEZSL The validity check of the CPXT control table failed.

2188OMPEZSL A CPXT table overflow error occurred.

2192OMPEZSL A CP31 extent free internal error occurred.

2196OMPEZSL The DELETE cell pool request is not valid.

88000Classic session OMPE/XCF driver detected an invalid input buffer address.

88004Classic session OMPE/XCF driver detected an invalid collection routine name.

88008Classic session OMPE/XCF driver detected that the XCF gateway is not active.


88012Classic session OMPE/XCF driver detected that the specified collection routine is undefined.

88016Classic session OMPE/XCF driver failed to locate the DB2 routing table.

88020Classic session OMPE/XCF driver detected an invalid DB2 routing table.

88024Classic session OMPE/XCF driver failed to locate the specified DB2 subsystem.

88028Classic session OMPE/XCF driver detected an invalid routing table pointer.

88032Classic session OMPE/XCF driver detected an invalid routing table header.

88036Classic session OMPE/XCF driver detected an invalid routing table DB2 ID.

88040Classic session OMPE/XCF driver could not locate the XCF token.

88044OMPE/XCF Send service routine failed validity checking XRDE structure.

88048OMPE/XCF Send service routine failed to locate the XCF connection token.

88052OMPE/XCF Send service routine failed validity checking token TCB pointer.

88056OMPE/XCF Send service routine failed validity checking token ASCB pointer.

88060OMPE/XCF Send service routine failed to locate target XMEM structure.

88064OMPE/XCF Send service routine failed to validity check XMEM structure.

88068OMPE/XCF Send service routine failed to validity check ALLTHOUT thread entry.

88072OMPE/XCF Send service routine detected that the buffer size exceeds data space size.

88076Classic session OMPE/XCF driver failed validity checking $ZDB2 control block.

88080Classic sesson OMPE/XCF driver failed validity checking VPI9800 block.

88084OMPE/XCF remote DB2 thread CPU driver failed sorting ALLTHOUT thread entries.

88088OMPE/XCF remote DB2 thread CPU driver stopped abnormally.

88092OMPE/XCF remote DB2 thread CPU driver found zero threads to process.

88096OMPE/XCF remote DB2 thread CPU driver failed validity checking ZCPU structure.

88100OMPE/XCF remote DB2 thread CPU response routine failed to validity check XSRE structure.

88104OMPE/XCF remote DB2 thread CPU response routine failed to validity check XRDE structure.

88108OMPE/XCF remote DB2 thread CPU response routine failed to validity check IRDA block.


88112OMPE/XCF remote DB2 thread CPU response routine failed to validity check IRDL length.

88116OMPE/XCF remote DB2 thread CPU response routine failed to validity check ZCPU block.

88120OMPE/XCF remote DB2 thread CPU response routine found zero ZCPE entries to process.

88124OMPE/XCF remote DB2 thread CPU response routine failed during ALESERV ADD request.

88128OMPE/XCF remote DB2 thread CPU response routine failed to validity check ZCPE block count.

88132OMPE/XCF remote DB2 thread CPU response routine found an unsupported DB2 subsystem version.

88136OMPE/XCF environment initialization failed to validity check the DB2 ERLY block.

88140OMPE/XCF environment initialization failed to validity check the DB2 subsystem ID.

88144OMPE/XCF environment initialization found an invalid DB2 subsystem ID as input.

88148OMPE/XCF environment initialization failed to validity check the DB2 SCOM block.

88152OMPE/XCF environment initialization failed to validity check the DB2 SSCT control block.

88156OMPE/XCF environment initialization failed to validity check the DB2 ACOM control block.

88160OMPE/XCF environment initialization failed to validity check the DB2 RMVT control block.

88164OMPE/XCF environment initialization failed to validity check the DB2 RMFT control block.

88168OMPE/XCF environment initialization failed to validity check the DB2 AMGS control block.

88172OMPE/XCF environment initialization failed to locate the DB2 routing table.

88176OMPE/XCF remote DB2 thread CPU collection routine failed to validity check Agent ASCB pointer.

88180OMPE/XCF remote DB2 thread CPU collection routine failed to validity check Agent ASSB pointer.

88184OMPE/XCF remote DB2 thread CPU collection routine failed to validity check Agent ASCB address.

88188OMPE/XCF remote DB2 thread CPU collection routine failed during ALESERV ADD request processing.

88192OMPE/XCF remote DB2 thread CPU collection routine failed during ALESERV DELETE processing.

88196OMPE/XCF remote DB2 thread CPU collection routine could not locate the DB2 AGNT control block.

88200OMPE/XCF control block access PC routine driver received an invalid input parameter list.

88204OMPE/XCF control block access PC routine driver specified an invalid processing environment.

88208OMPE/XCF control block access PC routine driver detected an invalid OMPE Collector environment.


88212OMPE/XCF control block access PC routine driver does not support the COMMCOLL collectorenvironment.

88216OMPE/XCF control block access PC routine driver failed validity checking the specified DB2 version.

88220OMPE/XCF control block access PC routine driver detected an unsupported DB2 subsystem version.

88224OMPE/XCF control block access PC routine driver eas unable to locate the XRDE structure.

88228OMPE/XCF control block access PC routine driver failed to validity check XRDE structure.

88232OMPE/XCF control block access PC routine driver could not locate the DB2 vector table.

88236OMPE/XCF control block access PC routine driver received a zero DBPL block address.

88240OMPE/XCF control block access PC routine driver failed to validity check DBPL block.

88244OMPE/XCF control block access PC routine driver found an invalid collection routine entry address.

88248OMPE/XCF control block access PC routine driver failed to locate the specified DB2 subsystem.

88252OMPE/XCF control block access PC routine driver failed to locate the DB2 subsystem SSCT controltable.

88256OMPE/XCF control block access PC routine driver received a null DBPL block address.

88260OMPE/XCF control block access PC routine driver failed to validity check DBPL block.

88264OMPE/XCF control block access PC routine driver detected a zero work area address.

88268OMPE/XCF control block access PC routine driver detected a zero input buffer address.

88272OMPE/XCF control block access PC routine driver detected a zero output buffer address.

88276OMPE/XCF control block access PC routine driver detected a zero work area length.

88280OMPE/XCF remote DB2 thread CPU collection routine failed to validity check the DB2 AGNT controlblock pointer.

88284OMPE/XCF remote DB2 thread CPU collection routine failed to validity check the DB2 AGNT controlblock address.

88288OMPE/XCF remote DB2 thread CPU collection routine failed to validity check the Agent ASCB address.

88292OMPE/XCF remote DB2 thread CPU collection routine failed to validity check the Agent TCB address.

88296OMPE/XCF remote DB2 thread CPU collection routine abnormally stopped.

88300OMPE/XCF DB2 environment initialization routine detected an invalid environment request.


90004OMPE/XCF ACE to AGNT collection routine failed to validity check the AMGS DB2 control block.

90008OMPE/XCF ACE to AGNT collection routine failed to validity check the DB2 ACE control block.

99000OMPE Collector subsystem token service routine retrieve request failed.

99004OMPE Collector subsystem token service routine failed token type validity checks.

90008OMPE Collector subsystem token service routine token name failed validity checks.

90012OMPE Collector subsystem token service routine token address failed validity checks.

90016OMPE Collector subsystem token service routine token retrieve failed validity checks.

90020OMPE Collector subsystem token service routine token delete failed validity checks.

90024OMPE Collector subsystem token service routine token create failed validity checks.

90028OMPE Collector subsystem token service routine token type retrieve failed validity checks.

90032OMPE Collector subsystem token service routine token delete function failed.

91000OMPEZIP The validity check of the OMPECT control structure failed.

91004OMPEZIP A duplicate $ZIIP ENABLE service request call is detected.

91008OMPEZIP The PC service request function code is not valid.

91012OMPEZIP A duplicate $ZIIP ENABLE instance service request is detected.

91016OMPEZIP $ZIIP ENABLE cannot be issued in SRB-mode.

91020OMPEZIP ZIIP support is not available (CVTZIIP).

91024OMPEZIP $ZIIP DISABLE cannot be issued in TCB-mode.

91028OMPEZIP The SVZ control storage block cannot be obtained.

91032OMPEZIP The $ZOMCT control structure is not initialized.

91036OMPEZIP The validity checks of the &ZOMCT control structure failed.

91040OMPEZIP The $ZMSTATE state entry block address is not initialized.

91044OMPEZIP The validity check of the $ZMSTATE entry block failed.

91048OMPEZIP The $ZIIP service request cannot be issued in XM-mode.

91052OMPEZIP The scheduling of the target enclave SRB routine failed.


91056OMPEZIP The DISABLE service request cannot locate the $ZMSTATE state entry block.

91060OMPEZPP The $ZMSTATE state entry block is not valid.

9106491064 There are no zIIPs processors defined for the z/OS image.

91076OMPEZIP The Disable post-processor EPA is not initialized.

91096OMPEZIP The zIIP jobstep TCB environment is not valid.

92000OMPEHVS The return code of the $ZTOKEN CREATE service request is nonzero.

92004OMPEHVS The issued service request is incorrect.

92008OMPEHVS The service request stopped abnormally.

92012OMPEHVS The DELETE service request is not supported in SRB-mode.

92016OMPEHVS The virtual storage is insufficient.

92020OMPEHVS The specified storage heap structure cannot be found.

92024OMPEHVS In the pool, no extents are available.

92028OMPEHVS The heap virtual storage segment to be freed cannot be found.

92032OMPEHVS The BUILD service request cannot to be issued in SRB-mode.

92036OMPEHVS The MODE= service request macro operand is not valid.

92040OMPEHVS The specified heap virtual storage subpool is not valid.

92044OMPEHVS The LOC= service request macro operand is not valid.

92048OMPEHVS The USAGE= service request macro operand is not valid.

92052OMPEHVS The TOKEN= macro operand contains a value of zero.

92056OMPEHVS The TOKEN= macro operand points to an invalid SH31 block.

92060OMPEHVS The validity check of the $ZSHCT control structure failed.

92064OMPEHVS The validity check of the $ZSHCT control structure identifier failed.

92068OMPEHVS No $ZSHCT control table slots are available.

92200OMPEHVS The zIIP TCB address cannot be found.

92204OMPEHVS The validity checks of the $ZMSTATE service failed.


92208OMPEHVS The value of the TCB address is null.

92212OMPEHVS The specified TOKEN= macro operand is not valid.

92216OMPEHVS The validity check of the $ZSH31 data structure failed.

92220OMPEHVS In SRB-mode, the $ZHEAP FREE service request cannot be issued with the macro operandUSAGE=ANY.

92224OMPEHVS The owner TCB address of the heap virtual storage manager $ZHEAP FREE service requestdoes not match.

92228OMPEHVS The TCB address owner is not valid.

92232OMPEHVS A zero length value is supplied.

92236OMPEHVS The length exceeds the maximum size.

92240OMPEHVS The heap virtual storage manager $ZHEAP FREE service request is issued in an incorrectstate.

92244OMPEHVS The specified ADDR= macro operand is not valid.

92248OMPEHVS The specified LENGTH= macro operand is not valid.

92252OMPEHVS The specified cell pool ID is not valid.

92256OMPEHVS The specified MODE= macro operand is not valid.

92260OMPEHVS The TCB token cannot be found.

92264OMPEHVS The OMCT control table cannot be found.

92268OMPEHVS The specified TOKEN=TCB macro operand is not valid.

KO2Z000I OMPE Vvrm Command Processed

ExplanationThe issued subsystem command was successfullyprocessed.

System actionThe subsystem command is processed.

User responseNone.

KO2Z001I OMPE Vvrm SubsystemInitialization in Progress

ExplanationThe subsystem is being initialized.

System actionSubsystem initialization proceeds.

User responseNone.

KO2Z002E OMPE Vvrm IEFSSVTREQUEST=CREATE error RC=%%%% RSN=%%%%


ExplanationSubsystem initialization could not create thesubsystem interface (SSI) environment.

• RC= indicates the return code. For more information,see “KO2Z return codes” on page 431.

• RSN= indicates the reason code. For moreinformation, see “KO2Z reason codes” on page 431.

System actionSubsystem initialization terminated.


KO2Z003E OMPE Vvrm IEFSSI REQUEST=PUTerror RC=%%%% RSN=%%%%

ExplanationSubsystem initialization could not update its vectortable.





KO2Z004E OMPE Vvrm IEFSSIREQUEST=OPTIONS error RC=%%%% RSN=%%%%

ExplanationSubsystem initialization could not verify optionsprocessing.





KO2Z005E OMPE Vvrm IEFSSIREQUEST=ACTIVATE error RC=%%% RSN=%%%%

ExplanationSubsystem initialization could not activate thesubsystem.





KO2Z006E OMPE Vvrm Name/Token Paircreate error RC=%%%%

ExplanationSubsystem initialization could not define a system-level name/token pair.




KO2Z007I OMPE Vvrm subsysteminitialization fFailed. Invalidsubsystem name prefix specified

ExplanationSubsystem initialization failed. An incorrect subsystemname prefix was specified.

System actionSubsystem initialization processing terminated.

User responseSpecify a valid four-character subsystem name. Thefirst three characters should be OMP and the last


character can be any alphanumeric value, for example,OMPE. The default subsystem name is OMPE.

KO2Z008I OMPE Vvrm Subsystemsuccessfully initialized in activemode

ExplanationThe OMPE subsystem has been initialized in activemode. The OMPE subsystem is ready to Receiveservice request calls from OMPE Collectorcomponents.

System actionSubsystem initialization has completed successfully.

User responseNone.

KO2Z009E OMPE Vvrm INITPARM error: PID=%%%% INITPARM=%%%%%%

ExplanationThe OMPE subsystem detected an incorrect inputparameter. PID= shows the incorrect input parameter.INITPARM= shows the complete input parameterstring.

System actionSubsystem initialization processing terminated.

User responseSpecify valid input parameters when starting theOMPE subsystem.

KO2Z010E OMPE Vvrm %%%% Subsysteminitialization failed

ExplanationThe OMPE subsystem failed to initialize.


User responseCheck the SYSLOG for abends or additional messagesthat describe the reason for the failure. GatherSYSLOG, SVC dumps and contact IBM support.

KO2Z011I OMPE Vvrm Options member %%%%%%%% keyword %%%%%%%%

ExplanationThe OMPE subsystem issues this message to show theoptions member and the type of invalid keywordspecified.

System actionSubsystem initialization continues with the specifiedoption default.

User responseSpecify the valid user option and restart the OMPECollector.

KO2Z012E OMPE Vvrm %%%% Loopdetection timer set failed

ExplanationA subsystem function takes too long to complete. Thedefault timeout, specified by SSITIMER=30 seconds,exceeded.

System actionThe current subsystem function is terminated.


KO2Z013E OMPE Vvrm Mutually exclusivekeywords specified

ExplanationMutually exclusive OMPE subsystem initializationkeywords have been detected by the subsystem parseroutine.


User responseSpecify valid keywords on the OMPE subsystemINITPARM= parameter and restart the OMPEsubsystem.

KO2Z014E OMPE Vvrm IEFSSIREQUEST=QUERY error RC=%%%% RSN=%%%%


ExplanationThe service request router could not complete asubsystem interface (SSI) query request.



System actionThe caller's service request is rejected.


KO2Z015E OMPE Vvrm Configurationincomplete. Collector initializationfailed RC=%%%% RSN=%%%%

ExplanationThe OMPE Collector failed to initialize because of amissing or incorrect initialization member dataspecified in RKD2PAR.



System actionOMPE Collector initialization terminated.

User responseVerify that the required components are specified inRKD2PAR and/or RKANMOD.

KO2Z016E OMPE Vvrm Invalid Collectorconfiguration parmlist. SR=%%%%

ExplanationThe indicated service request parameter list is notvalid.

System actionThe caller's service request is rejected.


KO2Z017E OMPE Vvrm WTO broadcast countupdate error

ExplanationSubsystem initialization could not update the write tooperator (WTO) broadcast count field maintained bythe z/OS communication task address space (CTAS).

System actionSubsystem initialization is terminated.


KO2Z018E OMPE Vvrm Diagnostic work areastorage obtain failure

ExplanationThe OMPE subsystem could not obtain ECSA storagefor a diagnostic work area structure.


User responseContact your systems programmer.

KO2Z019E OMPE Vvrm OMEGAMON XE FORDB2 PE IS ALREADY ACTIVE.START REJECTED

ExplanationThe OMPE Collector is already active.

System actionThe OMPE Collector Start request is rejected.

User responseStop the target OMPE Collector. Wait for the OMPECollector to end. Restart the Collector.

KO2Z020I OMPE Vvrm Collector optionssuccessfully initialized

ExplanationThe OMPE Collector global options defined inRKD2PAR member OMPEOPTS have been successfullydefined.


System actionOMPE Collector Initialization continues.

User responseNone.

KO2Z021I OMPE Vvrm Subsystem re-initialization performed by STARTservice request

ExplanationThe OMPE Collector subsystem instance has beensuccessfully reinitialized.

System actionOMPE Collector initialization continues.

User responseNone.

KO2Z022I OMPE Vvrm MEMBER= %%%%%%%% SVC screening initializationfailed.

ExplanationThe initialization of the SVC screening subsystemcomponent failed.

System actionThe initialization of the OMEGAMON Collectorcontinues.

User responseAdd the SVC screening member OMPESV00 to theRKANPAR parameter library data set and restart theOMEGAMON Collector.

KO2Z024E OMPE Vvrm KO2ZMSGB messageprocessing error RC=%%% RSN=%%%

ExplanationThe general OMPE subsystem message processingroutine failed to issue the target WTO message.



System actionThe subsystem terminated with abend code U2008.


KO2Z026E OMPE Vvrm Collector component%%%%/%%%% statementmissing from RKANPAR.

ExplanationOMPE Collector initialization detected that a requiredcollector component is missing in the configuration.

System actionThe OMPE Collector is abnormally terminated.

User responseInclude the required component in the RKANPAR andrestart the OMPE Collector.

KO2Z027I OMPE Vvrm Invalid OMPEOPTSoption specified: %%%%%%%%%

ExplanationThe specified OMEGAMON for Db2 PE Collector useroption is invalid.

System actionThe invalid user option is ignored. The default value isused.

User responseVerify that the user option is defined correctly in theRKD2PAR member OMPEOPTS.

KO2Z028E OMPE Vvrm START Service requesterror RC=%%% RSN=%%%%

ExplanationA request to internally start the OMPE subsystemfailed. The subsystem could not locate load modulesprefixed with KO2Z* in the first load module libraryspecified by the STEPLIB DDname of the OMPECollector JCL procedure.

System actionThe OMPE subsystem Start request is terminated.


User responseEnsure that load modules prefixed with KO2Z* residein the first library specified by the STEPLIB DDname.Additionally, the first load module library that containsthese load modules must have a suffix of TKANMOD.

KO2Z029I OMPE Vvrm Subsystem %%%%belongs to collector %%%%.Collector %%%% start rejected.

ExplanationThe starting OMPE Collector cannot specify asubsystem name that is associated with a differentOMPE Collector.

System actionThe OMPE collector Start request is rejected.

User responseSpecify a unique collector subsystem name in theOMPE Collector started task JCL procedure PARM=keyword, then restart the OMPE Collector.

KO2Z030I OMPE Vvrm XCF timer resetsuccessful XCFTIMER=%%

ExplanationThe OMPE/XCF XCF timer interval has beensuccessfully reset.

System actionOMPE Collector processing continues.

User responseNone.

KO2Z031E OMPE Vvrm CSVDYLPA dynamicLPA %%%%%% failed SSM=%%%%%%%% RC=%%%% RSN=%%%% FLGS=%%%%

ExplanationThe OMPE Collector initialization failed to add/delete amodule to/from the dynamic LPA.

System actionOMPE Collector initialization is abnormally terminated.


KO2Z032E OMPE Vvrm Invalid parameterdata supplied. PARM=%%%%%%%%

ExplanationThe OMPE Collector initialization detected invalidparameters supplied on the PARM= statement of theOMPE Collector started task JCL procedure.


User responseSpecify valid parameters and restart the OMPECollector.

KO2Z033E OMPE Vvrm Collector membername %%%%%%%% not found inRKANPAR concatenation

ExplanationThe OMPE Collector initialization could not locate thespecified member name in the RKANPAR parameterlibrary concatenation.


User responseSpecify the missing collector member name andrestart the OMPE Collector.

KO2Z034I OMPE Vvrm Searching RKANPARfor "EXEC %%%% componentstatement

ExplanationThe OMPE Collector initialization could not locate thespecified collector component in the RKANPARparameter library concatenation.


User responseSpecify the missing collector component and restartthe OMPE Collector.


KO2Z035I OMPE Vvrm Server virtual storagelimit MEMLIMIT(NOLIMIT) settingdiscovered

ExplanationThe OMPE Collector initialization detected that there isno 64-bit memory object limit size imposed on theOMPE Collector.

System actionOMPE Collector initialization continues.

User responseNone.

KO2Z036E OMPE Vvrm Vector table swapfailed SSM=%%%% RC=%%%%RSN=%%%%

ExplanationThe OMPE Collector subsystem initialization is unableto swap the SSVT matrix table.



KO2Z037E OMPE Vvrm The range of thedynamic subsystem name exceedsIX=%% RC=%%%% RSN=%%%%%%%%

ExplanationThe two digit suffix of the OMEGAMON Collectorsubsystem is out of range.

System actionThe OMEGAMON Collector stopped abnormally withABEND code U2008.

User responseContact IBM Support to report this problem.

KO2Z038E OMPE V%%% SSI call failed RC=%%%% RSN=%%%% SSIRC=%%%%

ExplanationThe subsystem service request failed.

System actionThe subsystem function request is rejected with errorcodes and reason codes.

User responseProvide the OMPE collector job log and the SVC dumpfor IBM support.

KO2Z039I OMPE Vvrm %%%%%%%%command request %%%%%%RC=%%%% RSN=%%%%%%%%

ExplanationThe issued command failed.

System actionThe OMEGAMON Collector ignores the issuedcommand.

User responseCheck the error codes and the reason codes for furtherinformation.

KO2Z040W OMPE Vvrm Member %%%%%%not found in RKANPAR. Using allsubsystem defaults

ExplanationThe OMPE Collector initialization detected thatRKANPAR parameter library member OMPE00 ismissing from the configuration.

System actionOMPE Collector initialization continues using allinternal defaults.

User responseNone.

KO2Z041E OMPE Vvrm RDJFCB errorDDName=%%%% RC=%%%%

ExplanationThe OMPE subsystem detected a read JFCB blockerror while trying to determine the status of a data set.



System actionThe subsystem function is abnormally terminated.


KO2Z042E OMPE Vvrm OPEN failureDDName=%%%% RC=%%%%RSN=%%%%

ExplanationThe subsystem could not open the indicated data set.





KO2Z043E OMPE Vvrm FIND failure Member=%%%% RC=%%%%

ExplanationThe subsystem could not locate the indicated member.


• Member= indicates the data set member.


User responseVerify that the data set member exists. Correct theproblem and restart the OMPE subsystem.

KO2Z044E OMPE Vvrm Storage obtain failedMember=%%%%%%%

ExplanationThe subsystem could not obtain local storage toprocess data from the indicated member.



KO2Z045E OMPE Vvrm Record input overflowMember=%%%%%%%

ExplanationThe subsystem detected a record overflow conditionwhile reading input member records from theindicated member name.



KO2Z046E OMPE Vvrm Parameters READerror Member=%%%%%%%

ExplanationA subsystem failure was detected reading record datafrom the indicated data set member.

System actionThe subsystem function is terminated.


KO2Z047E OMPE Vvrm DYNALLOC error ERR=%% INFO=%% DSN=%%%%%%%%

ExplanationThe subsystem failed to dynamically allocate thespecified data set.


User responseVerify that the specified data set name is correct.Correct the problem and re-execute the specifiedfunction.


KO2Z048W OMPE Vvrm Using defaultDDname=%%%% to locatemember=%%%%

ExplanationThe OMPE Collector initialization routine is using thedefault ddname to locate the specified configurationmember name.

System actionOMPE collector initialization continues.

User responseNone.

KO2Z049E OMPE Vvrm No input recordsfound. Member=%%%%%%%

ExplanationThe subsystem did not recognize any input recordsspecified in the target member name.

System actionThe subsystem function is terminated.

User responseCorrect the problem and re-execute the specifiedfunction.

KO2Z050E OMPE Vvrm READ Failure.Member=%%%% Unsupported

ExplanationThe subsystem detected an incorrectly specifiedmember name.

System actionThe subsystem function terminated.

User responseSpecify a supported member name.

KO2Z051E OMPE Vvrm Memory objectrequest failed SSM=%%%% RC=%%%% RSN=%%%% IARV64-RC=%%%% RSN=%%%%

ExplanationThe OMPE Collector subsystem could not successfullycreate the specified memory object.

System actionOMPE collector processing continues.


KO2Z052E OMPE Vvrm Memory objectrequest failed SSM=%%%% FC=%%%% RC=%%%% RSN=%%%%IARV64-RC=%%%% RSN=%%%%

ExplanationThe OMPE Collector subsystem could not successfullycreate the specified memory object function.



KO2Z053E OMPE Vvrm SSM=%%%%abnormally terminated RC=%%%% RSN=%%%%

ExplanationThe identified OMPE Collector subsystem moduleterminated abnormally.



KO2Z055I OMPE Vvrm SSM=%%%%%%%%using %%%%%%%% heapstorage buffer pool %%%%%%%%.

ExplanationThe subsystem component of the OMPE Collector iscurrently using the 31-bit heap virtual storagemanager.


System actionNone.

User responseNone.

KO2Z056I OMPE Vvrm DD=%%%%%%%%allocated to VOL=%%%%% DSN=%%%%%%%%%%.

ExplanationAt OMPE Collector initialization, the current list of allSTEPLIB data sets that are allocated by OMEGAMONXE for DB2 PE on z/OS is displayed:

• <v1> shows the STEPLIB sequence number• <v2> shows the data definition name• <v3> shows the volume serial number where the

STEPLIB dataset resides• <v4> shows the STEPKIB dataset name

System actionThe OMPE Collector initialization proceeds.

User responseNone.

KO2Z057I OMPE Vvrm Subsystem messagelog %%%%%%%% %%%%%%%RC=%%%% RSN=%%%%%%%

ExplanationIn the log data set, the status of a dynamically addedor removed message is indicated.

System actionThe message log is activated or inactivated.

User responseNone.

KO2Z058I OMPE Vvrm XCF gateway is at PTFmaintenance level %%%%%%%.

ExplanationAt OMPE Collector initialization, the currentmaintenance level of the XCF gateway is displayed.

System actionThe OMPE Collector initialization proceeds.

User responseNone.

KO2Z059I OMPE Vvrm OMPEOPTS useroption %%%%%%%% set to %%%%%%%%%%%%%%%%.

ExplanationAt OMPE Collector initialization, the values of the real-time user options that are defined by the RKANPARparameter library member OMPEOPTS are displayed.

System actionThe OMPE Collector initialization continues.

User responseNone.

KO2Z060E OMPE Vvrm SSM=%%%%%%%%IARV64 detach failed USERTKN=%%%%_%%%% RC=%%%% RSN=%%%%

ExplanationThe OMPE Collector subsystem failed to detach a 64-bit memory object.



KO2Z061E OMPE Vvrm Member=%%%% Noparm data found

ExplanationThe OMPE Collector subsystem detected than invalidparameter data is specified.


User responseSpecify valid parameter data and re-execute thesubsystem function.


KO2Z062E OMPE Vvrm Member=%%%%RID=%%%% KEY=%%%%%%%unrecognized/misplaced keyword

ExplanationThe subsystem detected an incorrect parameterrecord while reading the indicated member name. TheRID= value identifies the member record number andthe KEY= value identifies the incorrect keyword.

System actionThe subsystem function terminated.

User responseCorrect the problem and re-execute the subsystemfunction.

KO2Z063E OMPE Vvrm Member=%%%%unsupported

ExplanationThe subsystem parse routine detected an incorrectinput member name.


User responseSpecify a supported member name and re-execute thesubsystem function.

KO2Z064E OMPE Vvrm XCF timer reset errorXCFTIMER=%% is invalid

ExplanationThe subsystem parse routine detected that an invalidXCF timer value was specified.

System actionThe subsystem command is abnormally terminated.

User responseSpecify a numeric timer interval when executing thecommand.

KO2Z065E OMPE Vvrm Member=%%%%initialization failed

ExplanationThe subsystem failed to parse and initialize thespecified member record data.


User responseSpecify valid member data keywords and re-executethe subsystem function.

KO2Z069E OMPE Vvrm Server virtual storagelimit MEMLIMIT(x"!!!!!!!!_!!!!!!!!"MB) setting discovered

ExplanationThe OMPE Collector subsystem discovered the 61-bitmemory object setting value specified for the OMPECollector started task.

System actionNone.

User responseNone.

KO2Z069I OMPE Vvrm The value for thevirtual storage limit of the server isMEMLIMIT(%%%%%%%%).

ExplanationDepending on the specified value for the virtualstorage limit of the server, one of the followingmessages might be displayed:Not specified

KO2Z035I OMPE Vvrm The value for the virtualstorage limit of the server is MEMLIMIT(NOLIMIT).

MEMLIMIT=NOLIMITKO2Z035I OMPE Vvrm The value for the virtualstorage limit of the server is MEMLIMIT(NOLIMIT).

MEMLIMIT=4MKO2Z069I OMPE Vvrm The value for the virtualstorage limit of the server isMEMLIMIT(x"00000000_00000004"MB).

The maximum value that can be specified forMEMLIMIT is 2048M.

KO2Z073E OMPE Vvrm Virtual storage heap %%%% element %%%%%% failed.RC=%%%% RSN=%%%%%%%%



System actionThe virtual storage heap request failed with errorcodes and reason codes.

User responseCheck the error codes and the reason codes for moreinformation.

KO2Z074I OMPE Vvrm DAPICOMM structuretable %%%%%%%%%% RC=%%%% RSN=%%%%%%%%

ExplanationThe status of the Common Collector structure that isused to communicate the D5API request from theAgent address space is shown.

System actionThe initialization of the OMGAMON Collectorcontinues.

User responseNone.

KO2Z075I OMPE Vvrm Common field tableinitialization completed. RC=%%%% RSN=%%%%%%%%

ExplanationThe initialization of the common field table iscompleted. The common field table is a dictionary thatcontains all data fields and their describing attributes.It is shared among the components within the addressspace. The common field table is prerequisite for theproper function of the user interfaces.

System actionNone.

User responseNone, if the return codes and the reason codes are setto zero. Otherwise, contact IBM Support.

KO2Z076I OMPE Vvrm Common field tablerelease completed. RC=%%%%RSN=%%%%%%%%

ExplanationThe common field table is released.

System actionNone.

User responseNone if the return codes and the reason codes are setto zero. Otherwise, contact IBM Support.

KO2Z077I OMPE Vvrm CMD Display

ExplanationShows the first line of the multi-line write to operator(WTO) message output. This message is followed bymulti-line WTO data lines.

System actionThe command output is displayed.

User responseNone.

KO2Z078I display text from command DOMPE, STATUS

ExplanationShows the DISPLAY OMPE,STATUS command datalines. This message displays the following information:

• Subsystem name• Subsystem initialization date and time• Current TRACE status selected• Current DEBUG status selected• SMF record number (currently unused)• PARMLIB(RKD2PAR) OMPEnn member name

selected• PARMLIB(RKD2PAR) OMPEnn member parameter

data set name selected• LOADLIB(TKANMOD) Load module data set name

selected• Status of the Event Notification Facility Task (ENF) –

(currently unused)• Name of the sysplex selected• Name of the XCF group selected• SSI processing trap selected for TSO/E user IDs

(currently set to none)


• SSI processing trap selected for STC address spaces(currently set to none)

• SSI processing trap selected for JOB address spaces(currently set to none)

• SVC screening member name selected (currentlyunused)

• Name of the automatic command member name(currently unused)

• Name of the system-level name/token pair createdby the subsystem

• The input parameters specified in the INITPARM SSIkeyword to initialize the subsystem

• Name of the generic operator command interfacemember (currently unused)

• Subsystem load module protection option selected• Resource manager interface member name selected

(currently unused)• Resource manager interface abend limit (currently

unused)• Current setting of the RKD2PAR member refresh

status (currently set to LOCK)• Type of cross-memory environment selected and

created by the subsystem• Maximum number of XCF subtasks requested to be

attached to process Receive requests

System actionThe command data output is displayed.

User responseNone.

KO2Z079I Display end line from command DOMPE, STATUS

ExplanationShows the DISPLAY OMPE,STATUS command end line.

System actionThe command end line is displayed.

User responseNone.

KO2Z080I OMPE Vvrm Subsystem debugmode is %%%

ExplanationThis message is displayed in response to the VARYOMPE,DEBUG=[ON|OFF) subsystem command.

System actionThe command is successfully executed.

User responseNone.

KO2Z081I OMPE Vvrm Subsystem has been[Activated | Inactivated]

ExplanationThis message is displayed in response to the VARYOMPE,[ACTIVE|INACTIVE] subsystem command.

System actionThe command is successfully executed.

User responseNone.

KO2Z083E OMPE Vvrm Invalid subsystemcommand. CMD=%%%%%%

ExplanationA not valid subsystem command was issued.

System actionThe subsystem command is rejected.

User responseSpecify a valid subsystem command.

KO2Z085I OMPE Vvrm Subsystem Tracemode is [ON|OFF]

ExplanationThis message is displayed in response to a VARYOMPE,TRACE=[ON|OFF] command.

System actionThe trace mode status is set to the specified state.

User responseNone.


KO2Z086I OMPE Vvrm XCF gatewayinitialization %%%%%%%%

ExplanationThe current status of the XCF gateway component isdisplayed. Values might be INITIALIZED or FAILED.

System actionIf the initialization of the OMEGAMON for Db2 PECollector is not completed, the status FAILED isdisplayed. The OMEGAMON for Db2 PE Collector endsabnormally.

User responseNone.

KO2Z087W OMPE Vvrm Subsystem shutdownalready in progress. Commandrejected

ExplanationA previous subsystem Shutdown command request isalready in progress. The system is being shut downand will not accept additional Shutdown commandrequests.

System actionThe current Shutdown command is rejected.

User responseNone.

KO2Z090E OMPE Vvrm SUB=%%%% REL=%%%% subsystem name unusable.Choose a different name RC=!!!!RSN=!!!!!!!!

ExplanationThe OMPE collector subsystem initialization detectedthat the specified subsystem name on the PARM=keyword of the OMPE Collector started task JCLprocedure cannot be activated.



KO2Z091E OMPE Vnnn Collector addressspace is terminating due toPESERVER failure.

ExplanationThe PESERVER subtask failed. It cannot be restarteddue to serveral ABENDS.

System actionThe OMEGAMON Collector address space isterminated.

User responseRestart the OMEGAMON Collector address space. Ifthe failure persists, contact IBM Support.

KO2Z092E OMPE Vvrm Collector <V1>Function=<V2> failed. SSM=<V3>RC=<V4> RSN=<V5>

ExplanationAn error occurred.

• <V1> is the function ID.• <V2> is the function routine name.• <V3> is the failing Collector subsystem module.• <V4> is the return code that is returned from the

function routine.• <V5> is the reason code that is returned from the

function routine.

System actionThe OMEGAMON for Db2 PE Collector is abnormallyterminated.


KO2Z092I OMPE Vvrm XCF gateway datareceive tasks shortage relieved

ExplanationThe shortage of the tasks to receive data is relieved.

System actionThe processing of incoming tasks to receive datacontinues.


User responseNone.

KO2Z095E OMPE Vvrm %%%% error RC=%%%% DDN=%%%% MEM=%%%%LIB=%%%%

ExplanationThe OMPE collector initialization detected an error inthe OMPE collector configuration.


User responseCorrect the configuration and restart the OMPECollector.

KO2Z096E OMPE Vvrm APF-authorizationrequired RC=%%%% RSN=%%%% LIB=%%%%%%%%

ExplanationThe OMPE collector initialization detected that thespecified load module library needs to be APF-authorized.


User responseAPF-authorize the identified load module library andrestart the OMPE Collector.

KO2Z097E OMPE Vvrm MEMBER=%%%%%%%% ECSA storage obtain failure

ExplanationThe OMPE collector initialization could not obtain therequired common storage buffer to complete thespecified function.



KO2Z099E OMPE Vvrm Parse error Member=%%%% keyword table overflow

ExplanationThe subsystem keyword parser detected an errorwhile parsing keyword data from the indicatedmember.

System actionThe parse function is terminated.


KO2Z200I OMPE Vvrm Load modules loadedfrom LIB=%%%%%

ExplanationAll required subsystem load modules have beensuccessfully loaded from the specified load modulelibrary by the loader function of the OMPE subsystem.

System actionSubsystem initialization continues.

User responseNone.

KO2Z201E OMPE Vvrm DYNALLOC Error.ERR=%% INFO=%% LIB=%%%%

ExplanationA dynamic allocation error was detected duringsubsystem initialization.


User responseVerify that the correct library name was specified andrestart the OMPE subsystem.

KO2Z202E OMPE Vvrm Subsystem loadlibrary OPEN error LIB=%%%%%%

ExplanationA data set Open error was detected during subsysteminitialization processing.

System actionSubsystem initialization is abnormally terminated.



KO2Z203E OMPE Vvrm BLDL failed for MOD=%%%% from LIB=%%%%%%%

ExplanationSubsystem initialization could not locate a requiredload module in the specified load module library.


User responseVerify that the correct load module library has beenspecified. Correct the problem and restart the OMPECollector.

KO2Z204E OMPE Vvrm ECSA load error MOD=%%%%%%% from LIB=%%%%

ExplanationSubsystem initialization could not load the requiredload modules in the common service area.



KO2Z205E OMPE Vvrm APF-auth error MOD=%%%% from LIB=%%%%%%%

ExplanationSubsystem initialization processing encountered anauthorization error.



KO2Z206E OMPE Vvrm TKANMOD DCBstorage obtain failed LIB=%%%%%%

ExplanationSubsystem initialization processing could not obtain24-bit virtual storage in the OMPE Collector addressspace required to dynamically define a DCB controlblock.



KO2Z210E OMPE Vvrm ATTACH call errorLMOD=%%% ARC=%%%% RC=%%%% RSN=%%%%

ExplanationThe Attach service request failed to attach theindicated specified load module.

System actionThe Attach service request is abnormally terminated.


KO2Z220E OMPE Vvrm OMPECT controlstructure ESQA storage obtainfailed

ExplanationSubsystem initialization processing could not obtainESQA storage for the OMPECT common controlstructure.



KO2Z221I OMPE Vvrm Load module pageprotection is active

ExplanationSubsystem initialization successfully page-protectedall commonly loaded load modules.



User responseNone.

KO2Z222I OMPE Vvrm PTRACE=ON Activatedfor MOD=%%%%

ExplanationSubsystem initialization successfully activatedSYSTRACE processing. Entry and exit subsystemfunctions are recorded in the z/OS SYSTRACE table.


User responseNone.

KO2Z603E OMPE Vvrm EOT resource manager%%%%%%%% abnormallyterminated

ExplanationThe indicated end-of-task OMPE Collector subsystemresource manager abnormally terminated.



KO2Z604E OMPE Vvrm EOM resourcemanager %%%%%%%%abnormally terminated

ExplanationThe indicated end-of-memory OMPE Collectorsubsystem resource manager abnormally terminated.



KO2Z605E OMPE Vvrm %%%% resourcemanager %%%%%%%%abnormally terminated

ExplanationThe identified OMPE Collector subsystem resourcemanager abnormally terminated.



KO2Z606I OMPE Vvrm Defined zIIP CPUIDs:%%%,%%%,%%%,%%%,%%%,%%%,%%%,

ExplanationAt OMPE Collector initialization, the number of zIIPprocessors that are currently defined for the MVSimage are indicated.

System actionThe OMPE Collector initialization continues.

User responseNone.

KO2Z608I OMPE Vvrm No data to display.CMD=%%%%

ExplanationA subsystem command was issued and there is nooutput data to display.

System actionSubsystem processing continues.

User responseNone.

KO2Z609E OMPE Vvrm Structure errordetected by command routine=%%%%

ExplanationA subsystem command was issued and an abendcondition was detected.




KO2Z611E OMPE Vvrm Parse error. Keywordnot found. Member=%%%% KEY=%%%%

ExplanationA parsing error was encountered for the specifiedmember name. The error is identified by the KEY=keyword.

System actionSubsystem function processing is terminated.

User responseCorrect the error and re-execute the subsystemfunction.

KO2Z612E OMPE Vvrm Parse error. Invalidkeyword table supplied

ExplanationAn internal parsing error was detected by thesubsystem parsing routine.



KO2Z613I Vvrm CMD Display nnn

ExplanationThis message is displayed as a data line of a multi-linewrite to operator (WTO) message in response to aDISPLAY OMPE, DIAGS command.


User responseNone.


ExplanationThis message is displayed as a data line of a multi-linewrite to operator (WTO) message in response to aDISPLAY OMPE, ZAP command. The followinginformation is displayed:Module

The name of the subsystem control sectionVersion

The control section subsystem version numberLevel

The current PTF levelDate

The assembled dateTime

The assembled timeTrace

The current trace option status


User responseNone.


ExplanationThis message is displayed as data line of a multi-linewrite to operator (WTO) message in response to aglobal storage list (GSL) DISPLAY OMPE, GSLcommand. The following information is displayed:GSL=nnn

The number of GSL structures currently created bythe subsystem.

SP=nnnThe storage subpool number of the GSL structure.

EPA=entryThe entry point address of the GSL processingroutine.

InUseThe number of GSL entries currently used by thesubsystem.

FreedThe number of GSL entries freed by the subsystem.

TotalStgThe total amount of common virtual storage usedby the subsystem.

Next-GSLThe address of the next GSL structure.


AddressThe address of the common virtual storageelement.

XlengthThe length of the common storage element.

SPThe subpool number of the virtual storageelement.

KeyThe storage protection key of the current storageelement.

FreeWhenWhen will the virtual storage element be freed.

OwnerThe owner of the virtual storage element.


User responseNone.

KO2Z618E OMPE Vvrm LXRES linkage indexreserve failed

ExplanationThe subsystem could not obtain a system linkageindex required to build the cross-memoryenvironment.



KO2Z619E OMPE Vvrm ETCRE entry tablecreate failed

ExplanationThe subsystem could not create a cross-memoryenvironment entry table entry.



KO2Z620E OMPE Vvrm ETCON entry tableconnect failed

ExplanationThe subsystem failed to connect a cross-memoryenvironment entry table.



KO2Z621E OMPE Vvrm Cross-memoryenvironment creation failed.CALL=%%%% ABEND=%%%%RSN=%%%%%

ExplanationThe subsystem abnormally terminated while trying tocreate the required cross-memory environment.

RSN= indicates the reason code. For more information,see “KO2Z reason codes” on page 431.

System actionSubsystem processing is abnormally terminated.


KO2Z622E OMPE Vvrm Task level name/tokenpair %%%% failed RC=%%%%

ExplanationThe subsystem could not create a task level name/token pair.


System actionSubsystem processing is abnormally terminated.


KO2Z623I OMPE Vvrm Cross-memoryenvironment successfully created


ExplanationThe subsystem successfully created the requiredcross-memory environment.

System actionSubsystem processing continues.

User responseNone.

KO2Z624E OMPE Vvrm Cross-memoryenvironment creation failed RC=%%%% RSN=%%%%

ExplanationThe subsystem could not create the required cross-memory environment.



System actionThe cross-memory environment is not created.


KO2Z625E OMPE Vvrm %%%% Module %%%% ABENDs exceeded and has beendisabled

ExplanationThe indicated load module has exceeded the numberof allowed abends and has been disabled.

System actionFuture calls to the indicated module will be rejected.


KO2Z631I OMPE Vvrm SSM=%%%%%%%%RESMGR=%%%%%%%%environmental error

ExplanationThe OMPE Collector subsystem detected anenvironmental error associated with the identifiedresource termination manager.




ExplanationThis message is displayed in response to a DISPLAYOMPE, XCF command.


User responseNone.

KO2Z637E OMPE Vvrm XCF environmentcreation failed RC=%%%% RSN=%%%%

ExplanationThe cross-coupling facility communication interfacecomponent failed to initialize.



System actionThe cross-coupling facility communicationenvironment is not initialized.


KO2Z638I OMPE Vvrm Session %%%%%%%%/%%%%%%%% joined XCF: %%%%%%%%/%%%%%%%% (%%%%%%%) .


ExplanationA classic Collector session or a common Collectorsession joined the specified XCF group name. The XCFmember name, the LU name, and the maintenancelevel are indicated.

System actionNone.

User responseNone.

KO2Z639E OMPE Vvrm XCF request %%%%SSM=%%%% failed RC=%%%%RSN=%%%%

ExplanationThe cross-coupling facility communication interfacecomponent issued an XCF request and the requestfailed.



System actionThe XCF service request caller is notified about thefailure with return and reason codes.


KO2Z640I OMPE Vvrm XCF SYSPLEX=%%%% GROUP=%%%% MEMBER=%%%%

ExplanationThis message shows sysplex name, group name, andmember name associated with a specific servicerequest.

System actionNone.

User responseNone.

KO2Z641E OMPE Vvrm IRB failed to attach %%%% ABEND=%%%% RSN=%%%%

ExplanationAn Attach failure on behalf of the Attach servicerequestor occurred.

System actionThe Attach service request is terminated.


KO2Z642E OMPE Vvrm XCF SEND requestfailed fetch/store access SSM=%%%% RC=%%%% RSN=%%%%

ExplanationThe XCF Send service request failed while validity-checking input parameter structures.

System actionThe XCF initialization task is terminated.


KO2Z643E OMPE Vvrm Receive task %%%%%%%% disconnected from XCFgroup %%%%%%%% member %%%%%%%%%%%%%%%%

ExplanationThe classic session successfully disconnected fromthe identified XCF group name and member name.

System actionNone.

User responseNone.

KO2Z643W OMPE Vrm The XCF requestor is nolonger connected. RSN=!!!!!!!ARSN=%%%%%%%% %%%%=%%%%%%%%-%%%%%%%%

ExplanationThe response for DB2 performance data is cancelledbecause the requestor is no longer active.


System actionThe XCF gateway component storage releases theresponse data buffer.

User responseCheck the RSN= reason code for additional diagnosticinformation.

KO2Z644E OMPE Vvrm XCF service failedMOD=%%%% ABEND=%%%%RSN=%%%%

ExplanationA failure in the XCF service routine occurred.

System actionThe XCF-related function is terminated.


KO2Z646E OMPE Vvrm XCF %%%%%%%%failed SR=%%%%/%% RC=%%%% RSN=%%%% MEMBER=%%%%%%%%%%%%%%%%

ExplanationErrors occurred in the XCF Message Receive routine.

System actionThe Message Receive request is rejected.

User responseThis error is possibly caused because a member of theOMPEXCF group is terminating. Verify that the XCFmember is still in the system. If not, restart themember.

KO2Z647E OMPE Vvrm XCF SCHEDIRB failedMOD=%%%% RC=%%%% RSN=%%%%

ExplanationThe XCF Message Receive routine could not schedule aSend request to the target member.

System actionThe Message Receive request is rejected.


KO2Z648E OMPE Vvrm XCF Load failed forSSM=%%%% ABEND=%%%%RSN=%%%%

ExplanationThe target load module specified on the CALL=operand of the Send service request could not be z/OSloaded.

System actionThe Send service request is terminated with return andreason codes.


KO2Z649E OMPE Vvrm XCF component LOADfailed SSM=%%%%% RC=%%%%RSN=%%%%

ExplanationThe component load module specified on the CALL=operand of the Send service request could not be z/OSloaded.

System actionThe Send service request is terminated with return andreason codes.


KO2Z650I OMPE Vvrm User options member%%%%%%%% not found in RKANPAR.Using internal defaults

ExplanationThe user options member could not be found in theRKANPAR parameter dataset concatenation.

System actionThe OMPE Collector initialization continues using allinternal defaults.

User responseNone.


KO2Z652E OMPE Vvrm SSM=%%%% sendrequest failed RC=%%%% RSN=%%%%

ExplanationThe XCF Send service request failed to complete.

System actionThe Send service request is rejected.


KO2Z653E OMPE Vvrm System level name/token pair %%%% RC=%%%%SSM=%%%%

ExplanationA system level token could not be created or deleted.

System actionThe OMPE Collector initialization is abnormallyterminated.


KO2Z654E OMPE Vvrm XCF environmentalerror RC=%%%% RSN=%%%%SR=%%%%/IXCMSGO MEMBER=%%%%%%%%%%%%%%%%

ExplanationThe XCF component detected an internal error whileprocessing a Data Send or Data Receive request.

System actionThe XCF request is abnormally terminated.


KO2Z655I OMPE Vvrm display text OMPEXCQ

ExplanationThis message is displayed in response to OMPE/XCFcommand D OMPE,XCFQ, which displays the status ofall OMPEXCF cell pools.

SysPlexShows the name of the sysplex.

GroupShows the OMPE/XCF group name in use.

XMEMpoolShows the address of the member cell pool.

GetCellShows the number of get cell requests.

FreeCellShows the number of free cell requests.

System actionThe command output is displayed.

User responseNone

KO2Z656E OMPE Vvrm Data space %%%%%% failed SSM=%%%%%%%%RC=!!!! RSN=!!!!!!!!'

ExplanationThe XCF component failed to create or delete arequired data space.

System actionThe XCF component is abnormally terminated.


KO2Z657E OMPE Vvrm XCF response failedRC=%%%% RSN=%%%%SENDER=%%%%%%%%RECEIVER=%%%%%%%%'

ExplanationThe XCF request for data failed to complete.

System actionThe XCF request is abnormally terminated.


KO2Z658 OMPE Vvrm The dependent WLMEnclave %%%%%% failed. RC=%%%% RSN=%%%%%%%%


ExplanationThe WLM enclave to support the zIIP enablementservices failed to initialize.


User responseCheck the error codes and the reason codes for moreinformation.

KO2Z659I OMPE Vnnn WLM Enclave%%%%%% successful.IIPHONORPRIORITY=%%%zIIPs=%%%%%%%%.

ExplanationThe zIIP offload WLM enclave is created or deleted.The message field IIPHONORPRIORITY= shows thevalue that is specified in the IEAOPTxx member of theMVS PARMLIB.

• If IIPHONORPRIORITY=NO is specified, standardprocessors do not process zIIP workloads.

• If IIPHONORPRIORITY=YES is specified, standardprocessors process zIIP workloads.

The message field zIIPs= shows the number of onlinezIIP processors that are detected by the OMPECollector initialization process.

System actionThe initialization of the subsystem continues.

KO2Z660 OMPE Vvrm zIIP Enablementfailed. RC=%%%% RSN=%%%%%%%%

ExplanationThe WLM enclave to support the zIIP enablementservices is initialized successfully.


User responseNone.

KO2Z661E OMPE Vvrm The zIIP servicefailed. SSM=%%%%%%%%

ABEND=%%%%% RSN=%%%%%%%%

ExplanationA processing failure is indicated by the zIIPenablement and disablement services component.

System actionThe zIIP service request failed with an U2008 ABENDcode and reason code.

User responseCheck the reason codes for more information.

KO2Z662I OMPE Vnnn Common routing tabletask %%%%%%%%%%AUTOTIME=%%%% ROUT=%%%%%%%%.

ExplanationThe message field %%%%%%%%%% shows one ofthe following status messages:CIFI failed

The initialization of the IFI processing failed.Defaults to

The AUTOTIME real time option is not specified. Adefault interval of 5 seconds is used when copyingthe PE Server routing table to the common routingtable.

InitializedThe DB2 routing table is initialized successfully.

OverflowErrThe PE Server routing table storage size does notmatch the common routing table storage size.

Parse errorThe AUTOTIME real time option that is specified inthe OMPEOPTS real time options member isinvalid. An interval of 5 seconds is used whencopying the PE Server routing table to the commonrouting table.

TerminatedThe virtual storage of the DB2 routing table isreleased successfully.

Wait-PEinitThe initialization of the DB2 routing table is waitingfor the PESERVER initialization to complete.

The message field AUTOTIME= specifies the number ofseconds at which the DB2 routing table is refreshed.

The message field ROUT= shows the ECSA virtualstorage address of the DB2 routing table.


System actionThe initialization of the subsystem continues.

KO2Z663I OMPE Vnnn The PESERVERsubtask DGOVMSTR restartedsuccessfully. RC=%%%% RSN=%%%% TCB=%%%%

Explanation:The PESERVER master subtask failed because DB2stopped. The PESERVER master subtask restartedsuccessfully.

KO2Z664I OMPE Vvrm The PESERVERsubtask %%%%%%%%completed successfully.

Explanation:The PESERVER master subtask completedsuccessfully.

KO2Z667I OMPE Vvrm XCF Gateway messageID Ko2Z665W suppressed. LPAR=%%%%%%%% COUNT=%%%%%%%%

ExplanationThe XCF send service request was sent to LPAR %%%%%%%%.

The message ID KO2Z665W was suppressed %%%%%%%% times.

System actionThe XCF send service request is rejected.

User responseStart the OMEGAMON PE Collector on the target LPAR.

KO2Z665W LPAR=Lparname not connected toservice XCF requestSSID=Subsystem-ID CBA=Service-request RSN=Reason-code.

Explanation• Lparname specifies the remote XCF gateway target

LPAR.• Subsystem-ID specifies the target DB2 subsystem.• Service-request specifies the remote control block

access request routine• Reason-code is RSN=0000 1292 for version 5.1.0 or

RSN=0000 1396 for version 5.1.1

A member of the XCF-gateway sent a request to amember (LPAR) that resides on a remote XCF-gateway.The member on the remote XCF-gateway is not yet

fully initialized, or it does not exist. Therefore DB2subsystem monitoring data cannot be exchanged withthe specified remote XCF gateway.

User responseVerify that the remote XCF-Gateway LPAR issuccessfully initialized and connected. Restart therequest.

KO2Z668E OMPE Vvrm NTH SRB ABENDed.CC=%%%%%%%% ABENDCODE=%%%%% RSN=%%%%%%%%

ExplanationNear Term History collector instance terminatedabnormally while running in enclave SRB-mode on azIIP processor.

System actionThe NTH collector instance is abnormally terminated.

User responseContact IBM Support.

KO2Z669W The maintenance level of the XCFgateway is not compatible withOMEGAMON for Db2 PE <V1>.Sending system:<V2>/<V3>.Receiving system:<V4>/<V5>

ExplanationThe PTF maintenance levels of the sending and thereceiving OMEGAMON Collector XCF gateway must bethe same.

• <V1> is version 5.4.0.• <V2> is the name of the sending system where the

local OMEGAMON Collector is running.• <V3> is the PTF maintenance level of the sending

OMEGAMON Collector XCF gateway.• <V4> is the name of the receiving system where the

remote OMEGAMON Collector is running.• <V5> is the PTF maintenance level of the receiving

OMEGAMON Collector XCF gateway.

System action:The request for data is rejected by the receiving XCFgateway.


User responseVerify the PTF maintenance levels of the local and theremote XCF gateway by checking the message IDKO2Z058I in the job log of the local and the remoteOMEGAMON Collector address space.

If the PTF maintenance levels do not match, install thelatest maintenance level on all OMEGAMON Collectorsand shut down and restart the OMEGAMON Collectoraddress spaces.

KO2Z670W The request to send data isrejected by OMEGAMON for Db2PE because the maintenancelevels of the XCF gateways are notcompatible.

ExplanationThe PTF maintenance levels of the sending and thereceiving XCF gateway do not match.

• <V1> is the version number of OMEGAMON for Db2PE on the sending system.

System action:The local XCF gateway rejects the request to senddata.

User responseInstall the latest maintenance level on all OMEGAMONCollectors and shut down and restart the OMEGAMONCollector address spaces.

KO2Z806I OMPE Vnnn Session %%%%%%%%/%%%%%%%% disconnectedfrom XCF group %%%%%%%%/%%%%%%%% (%%%%%%%).

ExplanationThe classic session or the common collector sessionsuccessfully disconnected from the specified XCFgroup name.

System actionNone.

User responseNone.

KO2Z808E OMPE Vvrm SSM=%%%%%%%%SR=%%%%%%%% failed RC=%%%% RSN=%%%% MEMBER=%%%%%%%%%%%%%%%%

ExplanationThis message is issued by the OMPE Collectorsubsystem to indicate that the service request issuedby the OMPE Server caller has failed.



System actionThe service request is rejected.


KO2Z809W OMPE Vvrm Server %%%%previously bound to COMPID=%%%% BIND=%%%% used

ExplanationThis message is issued by the OMPE Collectorsubsystem when it detects that a server is alreadyconnected to the XCF component. If the BIND=REUSEoption is in effect, the OMPE Collector subsystemproceeds to reconnect the server. If theBIND=NOREUSE option is in effect, the subsystemfails the BIND service request.

System actionThe BIND service request is handled based on theBIND option specified.

User responseIf BIND=NOREUSE is in effect, specify BIND=REUSE inmember RKD2PAR(OMPE00) to allow BIND to reusethe same name/token pair.

KO2Z810E OMPE Vvrm OMPE collector %%%%%%%% SSID=%%%%%% %%MEMBER=%%%%%%%%%%%%%%%% response not received

ExplanationThis message is issued by the OMPE Collectorsubsystem XCF component to indicate that a requestfor DB2 performance data sent to a remote LPAR/VMID did not receive a response.

System actionThe Send service request is abnormally terminated.



KO2Z895E OMPE Vvrm SSI Module %%%%exceeded execution limit

ExplanationThe indicated load module has exceeded its executionlimit.

System actionThe z/OS subsystem interface (SSI) function isabnormally terminated.


KO2Z896E OMPE Vvrm SSM=%%%%%%%%exceeded %% seconds executiontime limit

ExplanationThis message is issued by the OMPE Collectorsubsystem XCF component to indicate that thespecified load module has exceeded its executionlimit.

System action:The request is abnormally terminated.


KO2Z900I OMPE Vvrm Subsystem Shutdownin Progress

ExplanationThe VARY OMPE,SHUTDOWN command is currentlybeing processed.

System actionThe subsystem initiates shutdown processing.

User responseNone.

KO2Z901W OMPE Vvrm XCF gateway datareceive tasks shortage detected

ExplanationTasks to receive data are currently busy processing thecorresponding requests.

System actionRequests to receive data are queued for laterprocessing.

User responseYou might want to increase the number of XCFgateway RECEIVE tasks that are specified by theXCFTASKS OMPEOPTS user option and restart thetasks that were started by the OMEGAMON for Db2 PECollector.

KO2Z902I OMPE Vvrm XCF gateway datareceive tasks shortage relieved

ExplanationThe shortage of the tasks to receive data is relieved.

System actionThe processing of incoming tasks to receive datacontinues.

User responseNone.

KO2Z904E OMPE Vvrm System level name/token pair delete failed RC=%%%%%%

ExplanationThe subsystem could not delete a system level name/token pair.


System actionThe subsystem is abnormally terminated.


KO2Z907I OMPE Vvrm System level name/token pair retrieve failed RC=%%%%%%


ExplanationThe subsystem could not retrieve a system-levelname/token pair.


System actionThe subsystem terminated.


KO2Z920I OMPE Vvrm Commandsuccessfully issued

ExplanationThe issued command has been successfully executed.


User responseNone.

KO2Z921E OMPE Vvrm Invalid PARMspecified. Function terminated

ExplanationThe subsystem utility program detected a not validinput parameter.

System actionThe utility function is terminated.

User responseCorrect the problem and re-submit the utility request.

KO2Z922E OMPE Vvrm Command not allowedfrom TSO/E Session

ExplanationThe utility program cannot be executed from a TSO/Esession as a called program or command processor.


User responseExecute the utility function as a batch job or startedtask.

KO2Z923E OMPE Vvrm Subsystem %%%%not found. Reset rejected

ExplanationThe subsystem utility program cannot locate theindicated OMPE subsystem that has been requested asa target of the reset function.


User responseSpecify a valid OMPE subsystem name and re-executethe utility function.

KO2Z924I OMPE Vvrm Subsystem %%%%Successfully reset

ExplanationThe subsystem utility program successfully reset theindicated OMPE subsystem name.

System actionThe indicated OMPE subsystem name is reset.

User responseNone.

KO2Z926E OMPE Vvrm Unable to postasynchronous API callerSSM=<V1> RC=<V2> RSN=<V3>

ExplanationAn error occurred when trying to post the API caller.

• <V1> is the failing OMEGAMON for Db2 PE Collectorsubsystem module name.

• <V2> is the return code that is issued by the failingmodule.

• <V3> is the reason code that is issued by the failingmodule.

System actionThe asynchronous API call is abnormally terminated.



KO2Z956I OMPE Vvrm Subsystem has beensuccessfully shut down

ExplanationNone.

System actionSubsystem processing is terminated.

User responseNone.

KO2Z957I OMPE Vvrm is issued on behalf ofPE Server subtask %%%%%%%%QN=%%%%%%%% RN=%%%%%%%%

ExplanationA resource serialization request has been issued bythe PE Server subtask to alert OMPE components thatnormal PESERVER termination is in progress:

• <v1> shows the type of serialization request• <v2> shows the resource major name• <v3> shows the resource minor name

System actionOMPE Collector address space termination continues

User responseNone.

KO2Z958I OMPE V530 PE Server RTG servicerequest failed. RC=000C RSN=%%%%%%%

ExplanationThe OMPE Collector subsystem was unable to processa common collector request for DB2 performancemonitoring data.

• RC=000C indicates that a severe error occurredprocessing an initialization function.

• RSN= shows the reason code associated with theerror return code.

• RSN=00091228 OMPE Collector started taskaddress space is not up and running.

• RSN=00091232 OMPE Collector started taskaddress space not responding.

System actionThe Service request for DB2 performance monitoringdata is rejected.

User responseStart the OMPE Collector started task address space.

KO2Z959I OMPE Vnnn Initializationverification procedures bypassed.EXECIVPS=NO

ExplanationThe OMPE Collector subsystem by default, atinitialization time, executes the initializationverification procedures. When EXECIVPS=NO isspecified, the initialization verification procedures arebypassed.

System actionThe initialization verification procedures are notprocessed.

User responseSpecifiy EXECIVPS=YES in RK2DPAR memberOMPEOPTS to have the initialization verificationprocedures executed during OMPE Collector startedtask address space initialization.

KO2Z960E OMPE V530 PE Serverenvironment error. RTG containeraddress not initialized. RC=000CRSN=%%%%%%%

ExplanationThe OMPE Collector subsystem was unable to locatethe PE Server list of monitored DB2 subsystems.

• RSN=00088544 - PE Server subtask failed toproperly initialize.

• RSN=00088548 - PE Server routing table address ofDB2 subsystems is not initialized.

• RSN=00088552 - PE Server routing table structurefailed validity checks.

• RSN=00088556 - PE Server routing table monitoredDB2 subsystem container contains zero entries.

• RSN=00088560 - PE Server routing table monitoredDB2 subsystems container contains.


System actionThe OMPE Collector subsystem fails to initialize itsinternal structures that point to the PE Server list ofmonitored DB2 subsystem. Classic and CommonCollector sessions will fail display any monitored DB2subsystem data.

User responseReview the job log for additional error messages thatmay have been issued by the PE Server componentand verify that the RKD2PAR member OMPEMSTRdoes not contain validity check errors.

KO2Z961I OMPE Vvrm OMPE Collector doesnot support executing in areusable ASID

ExplanationThe OMPE Collector address space has been started ina reusable ASID which is not supported.

System actionOMPE Collector address space is abnormallyterminated.

User responseStart the OMPE Collector without specifyingREUSASID=YES.

KO2Z962E OMPE Vvrm Class PE routingservice error. SSM=%%%%%%%% SSID=%%%% RC=%%%%RSN=%%%%%%%

ExplanationA request to discover the status of a DB2 subsystemdid not complete successfully.

• <v1> shows the requesting OMPE Collectorsubsystem module name

• <v2> shows the target DB2 subsystem identifier• <v3> shows the service request return code• <v4> shows the service request reason code

System actionThe DB2 subsystem instance request is rejected.

User responseStart the OMPE Collector started task address space.

KO2Z999E OMPE Vvrm Subsystem error.module=%%%%%%%% ABEND=%%%% REASON=%%%%%%%%

ExplanationThe OMPE subsystem recovery/termination managerindicates that the currently executing subsystemfunction was terminated.

System actionThe subsystem might be shut down depending on theseverity of the abend.



Chapter 3. Troubleshooting and supportThis section summarizes what you can do if you encounter problems.

Troubleshooting during installationWhen you install OMEGAMON XE for DB2 PE, you might encounter specific problems. The followingexamples help you make a corrective action that resolves the problem, or provide your IBMrepresentatives with enough information so that they can resolve it.

In general, when you get an error message, complete these steps:

1. Try to specify what the problem is.2. Determine the resource that is affected.3. Obtain more information.

Error in RKLVLOG indicating that the connection failedThis error occurs when the HTTP/HPPTS daemon tries to obtain a special port. You receive repeatingmessages in the RKLVLOG indicating that the connection failed with errno 93.

This error happens when the HTTP/HPPTS daemon tries to obtain a special port. You will see the followingerror message:(0000-E0A2716B:kbbssge.c,52,"BSS1_GetEnv") KDP_D2_STC="DSNFOM4S" (0001-E0A2716B:kbbssge.c,52,"BSS1_GetEnv") KDP_STATUS_REFRESH="60" (0002-E0A2716B:kdpd5api,257,"d5api_connect") KO2I1000W Connection to OMPE Server DSNFOM4S Failed Subsystem DSN7 Return=00000000 Reason=0000006A Retrying in 60 Seconds (0000-E0B367EB:kdebbcn.c,35,"KDEB_BaseConnect") connect failed, errno 93

To solve this problem, perform the following steps:

1. Stop the OMEGAMON Agent.2. Edit the member KD5ENV in <variable R1>.<variable R2>.RKANPARU and insert HTTPS:0\ as first

transport protocol for KDE_TRANSPORT. For example, KDE_TRANSPORT=\ IP.UDP PORT:1918USE:N\ IP6.PIPE PORT:1918 USE:N\ ... HTTPS:0\

3. Save the member and restart the OMEGAMON Agent.

Troubleshooting commandsThis section provides an overview of the Troubleshooting commands.

UsageThis section describes the DUMP command used to dump records from an input data set, and theTAPECOPY command used to copy records from an input data set to an output data set. The options forthese commands are almost identical. DUMP and TAPECOPY can each occur once in a job step. Thedescription of the subcommand options is intentionally brief, to avoid recurrences.

DUMP commandThis section provides an overview of the Troubleshooting command DUMP.

UsageThe DUMP command is a tool used for diagnosis. It provides, in dump format, a printout of an input dataset. All records in the input data set, a selected range of records, or specific record types can be dumped.


Usage notes• The DUMP command defines options for the record dump module.• Dumps are written to SYSPRINT in a hexadecimal dump format.• “Sample JCL for DUMP and TAPECOPY commands” on page 485 shows sample JCL for DUMP and

TAPECOPY commands.

Syntax

dump name

DUMP ( EXEC ( INPUTDD )

OFFSET (

4

integer )

CODES ( codelist )

SKIP (

0

integer )

STOPAFT (

0

integer )

MAXDUMP (

whole record

integer )

)

Subcommand optionsdump name

A user-defined name printed on the dump. If this field is omitted, the records are identified with thename DUMP0001.

Ensure that the specified name is not the same as a OMEGAMON for DB2 PE command keyword orabbreviation.

EXECSpecifies INPUTDD as the ddname of the input data set. INPUTDD is the only valid ddname for thisoption and must be specified.

OFFSETThe offset of the record code into the record. The record code is a 1-byte field at position offset-plus-1. For example, OFFSET(4) defines a record code in the fifth byte of the record. The offset mustbe a numeric value less than the actual length of the record. The maximum value is 999 999 999. Thedefault is 4.

CODESThe code values for records to be processed. Each code is a 2-digit hexadecimal number. You canspecify either of the following:

• A list of values, for example '01,02,03'• A range of values, for example '01-03,05-07'

Each entry must be separated by a comma. Enclose the code list in quotes if more than one value isspecified.

If this option is omitted, all record codes (00-FF) are processed.

SKIPThe number of records to be skipped before processing begins. The maximum value is 999 999 999.The default is 0, which means that processing begins with the first record.


STOPAFTThe number of records to be processed, starting after the number of records to be skipped (SKIPoption). The maximum value is 999 999 999. The default is 0, which causes all records (afterskipping, if specified) to be processed.

MAXDUMPThe length of the dump in bytes, starting from the beginning of the record. The default is the fulllength of the record. You can enter any integer in the range of 1 to 99 999. For example, if you specifyMAXDUMP(128), only the first 128 bytes of input records are dumped.

Note: Some IFCID records can be up to 32 KB in length. If you use the default for MAXDUMP (theentire record), very large reports can be produced.

Example using DUMP

In this example:

• The DUMP is named DUMPSTAT.• The ddname of the input data set is INPUTDD (the GLOBAL default).• The offset of 4 defines a record code in the fifth byte of the record.• Only records with a value of 01 or 02 in the fifth byte are dumped.• The first 125 records of the input data set are skipped.• The next 10 records that meet the specifications are dumped.• Only the first 1 000 bytes of each record are dumped.

DUMPSTAT DUMP (EXEC (INPUTDD)OFFSET (4)CODES ('01,02')SKIP (125)STOPAFT (10)MAXDUMP (1000))

Note: See also “Sample JCL for DUMP and TAPECOPY commands” on page 485.

TAPECOPY commandThis section provides an overview of the Troubleshooting command TAPECOPY.

UsageThe TAPECOPY command is a utility tool that you can use to select a specified subset or all records froman input data set, and copy them to an output data set. The selection logic is identical to that used for theDUMP command.

Usage notes• The TAPECOPY command defines options for the data set copy module.• Copies of selected portions of the input data set are produced on a user-specified output data set.

Chapter 3. Troubleshooting and support 483

Syntax

tape copy name

TAPECOPY ( EXEC ( INPUTDD )

OFFSET (

4

integer )

CODES ( codelist )

SKIP (

0

integer )

STOPAFT (

0

integer )

NEWCOPY ( ddname )

)

Subcommand optionstape copy name

A user-defined name identifying the records copied. If this field is omitted, the records are identifiedby the name COPY0001.

Ensure that the specified name is not the same as a OMEGAMON for DB2 PE command keyword orabbreviation.

EXECSpecifies INPUTDD as the ddname of the input data set. INPUTDD is the only valid ddname for thisoption and must be specified.

OFFSETThe offset of the record code into the record. The record code is a 1-byte field at position offset-plus-1. For example, OFFSET(4) defines a record code in the fifth byte of the record. The offset mustbe a numeric value less than the actual length of the record. The maximum value is 999 999 999. Thedefault is 4.

CODESThe code values for records to be processed. Each code is a 2-digit hexadecimal number. You canspecify either of the following:

• A list of values, for example '01,02,03'• A range of values, for example '01-03,05-07'

Each entry must be separated by a comma. Enclose the code list in quotes if more than one value isspecified.

If this option is omitted, all record codes (00-FF) are processed.

SKIPThe number of records that are skipped before processing begins. The maximum value is999 999 999.

The default is 0. If 0 is specified, processing begins with the first record.

STOPAFTThe number of records to be processed, starting after the number of records to be skipped (SKIPoption). The maximum value is 999 999 999.

The default is 0. This causes all records (after skipping, if specified) to be processed.

NEWCOPYThe ddname of the output data set. The default is TAPECOPY.


Example using TAPECOPY

In this example:

• The TAPECOPY is named COPYSTAT.• The ddname of the input data set is INPUTDD (the GLOBAL default).• The offset of 4 defines a record code in the fifth byte of the record.• Only records with a value of 01 or 02 in the fifth byte are copied.• The first 50 records of the input data set are skipped.• The next 10 records that meet the specifications are copied.• The ddname of the output data set is OUTDATA.

COPYSTAT TAPECOPY(EXEC (INPUTDD)OFFSET (4)CODES ('01,02')SKIP (50)STOPAFT (10)NEWCOPY (OUTDATA))

Sample JCL for DUMP and TAPECOPY commands

The following figure shows a sample JCL for the DUMP and TAPECOPY commands.

Note: The command syntax shown below is not appropriate in all circumstances. You must modify it tomeet your requirements and system setup.

//TPCDUMP1 JOB (INSTALLATION DEPENDENCIES)//*//*//*****************************************************************//*//*COPY INPUT DATA FILE TO SYSPRINT OR AN OUTPUT DATA FILE//*//*****************************************************************//*// PEMAIN EXEC PGM=FPECMAIN//STEPLIB DD DSN=FPE.FPELIB.RKANMOD,DISP=SHR//SYSPRINT DD SYSOUT=X//SYSOUT DD SYSOUT=X//*//* --- INPUT DATA SET ---//*//INPUTDD DD DSN=FPE.FPELIB.INPUT1,DISP=SHR//*//* --- OUTPUT DATA SET ---//*//OUTDATA DD DSN=FPE.FPELIB.OUTPUT1,// DISP=(NEW,CATLG),// UNIT=SYSDA,SPACE=(TRK,(10,10),RLSE),// DCB=(RECFM=VB,LRECL=4092,BLKSIZE=4096)//*//SYSIN DD *** --- TAPECOPY COMMAND EXAMPLE ---*COPY0001 TAPECOPY (EXEC(INPUTDD),SKIP(125),STOPAFT(10),NEWCOPY(OUTDATA))*** --- DUMP COMMAND EXAMPLE ---*DUMP0001 DUMP (EXEC(INPUTDD),SKIP(125),STOPAFT(10),MAXDUMP(1000))EXEC**

Figure 1. Sample JCL for the DUMP and TAPECOPY commands


Creating a diagnostic reportIf you have an error that you cannot resolve yourself, for example, if a function does not work correctly oran error message appears that you do not understand, you can create a diagnostic report that you cansend to IBM support as a problem management report (PMR).

You create a report from the System Overview window. To forward the report to IBM support, ensure thatyou have specified your e mail settings in the global settings.

To create a diagnostic report:

1. In the System Overview window, click Help > Diagnostics.

The Diagnostics window is displayed.2. Click the Start button to start recording diagnostic information.3. When you have recorded the entire information, click the Stop button.4. Do one of the following:

• Click the Send button to send the diagnostic report to IBM support.

The Send Diagnostic Information window is displayed. Type a brief description of the problem in theSubject field and click OK. The diagnostic report is sent to IBM support and deleted from yoursystem.

• Click the Save button.

The Save Diagnostic Information window is displayed. In the Scenario field, provide a detaileddescription of the error situation and click OK.

Responding to dialog boxesOMEGAMON for Db2 PE supports a modal dialog boxes, such as message boxes, to which you mustrespond before you can proceed with any other action.

If such a dialog box is in the background, do the following:

1. Press Alt+Tab.

A dialog box is displayed.2. Press the Tab key while holding the Alt key until the Java Cup and Steam Logo is selected.3. Release the Alt key.

The previously invisible dialog box is displayed in the foreground.4. Respond to the dialog box.

Troubleshooting for Performance Expert ClientThis topic describes the problems that you might encounter in Performance Expert Client.

Performance Expert Client does not work correctly after startupIf you have a firewall installed on your workstation, ensure that Performance Expert Client has correctaccess permissions. Otherwise, Performance Expert Client does not work correctly.

Launching Netscape as HTML browserIf launching an HTML browser from Performance Expert Client fails, the browser is opened separately.

Troubleshooting for Performance WarehouseThe following sections describe the problems that you might encounter in Performance Warehouse.


Solving code-page problems when accessing Performance WarehouseFor some installations, you might receive SQL0332 errors when accessing Performance Warehouse.

To solve this problem, set DB2CODEPAGE to a value that is compatible with the host SCCSID. In addition,the SYSIBM.SYSSTRINGS table must contain a row that maps the two values in the INCCSID OUTCCSIDcolumns. For more information about DB2CODEPAGE values, see the section National Language SupportConsiderations in one of the DB2 Connect Quick Beginnings books.

If you still cannot connect to Performance Warehouse, you might see the following message: SQL0332N- There is no available conversion for the source code page "1208 UNKNOWN 3" tothe target code page. Reason Code. SQLSTATE=57017.

To solve this problem, add DISABLEUNICODE=1 in the file sqllib\db2cli.ini for the DB2 subsystem, wheresqllib is the default DB2 Connect installation directory. See also the technical notes (Technotes)#1008683 and #1008573.

If DISABLEUNICODE does not work, you might get the following message: SQL0332N There is noavailable conversion for the source code page "01208" to the target code page"00437". Reason code "DSNXRIVB". SQLSTATE=57017.

To solve this problem, UNICODE support on z/OS must be enabled correctly including Enforced Subsetand Round Trip method in the conversion image. For more information, see APAR PQ40270 and PMR#68853.

Restarting the OMEGAMON CollectorBefore restarting the OMEGAMON Collector, which manages Performance Warehouse, disconnect from allPerformance Warehouse clients and all subsystems of Performance Expert Clients that are connected.

This is necessary because the clients might hold a lock on the Performance Warehouse data tables andprevent the OMEGAMON Collector from restarting and initializing.

Running a CONVERT step with an incorrect data setCONVERT steps assume Save data sets as input that were produced by Performance Expert batch reports.If a CONVERT step runs with an incorrect input data set, the OMEGAMON Collector fails (see error log)and is unable to run any processes. In this case, the OMEGAMON Collector must be stopped andrestarted.

Troubleshooting empty reportsThis topic lists and explains several reasons why your report might not contain any report data. Use thisinformation as a guide to identify possible reasons, including inappropriate command parameters.

At its core, OMEGAMON XE for DB2 PE identifies data to be collected and reported by IFCIDs. The basicrule is that data to be reported needs to be collected and made available as input data to the reportgeneration process. If required IFCIDs are missing, the generated report ends with NO DATA TOREPORT.

The problem of missing IFCIDs might also be caused by different versions of DB2 or OMEGAMON XE forDB2 PE. Both products might support different sets of IFCIDs, which can lead to situations where anIFCID is either not provided by a DB2 version or cannot be processed by an OMEGAMON XE for DB2 PEversion. The same problem might arise if data from other sources, like SMF or GTF, is used for reports.

OMEGAMON XE for DB2 PE provides flexible means to specify which data to collect and which data toreport. However, it provides no means to protect against inappropriate use of commands, subcommandsand subcommand options, which also can result in empty reports.

The following sections list possible reasons why your report might end with a final message of NO DATATO REPORT.


Messages indicating unsupported IFCIDs or IFCID formatsIf the job summary log shows message FPEC4015I NUMBER OF RECORDS FROM UNSUPPORTEDRELEASES OF DB2 WAS ..., OMEGAMON XE for DB2 PE has detected IFCIDs in its input data that it isnot supposed to handle. Either the input data is from an outdated DB2 version and the IFCID is no longersupported by OMEGAMON XE for DB2 PE, or the input data contains IFCIDs from a newer DB2 version andOMEGAMON XE for DB2 PE is not yet aware of them.

If the job summary log shows message FPEC4020I NUMBER OF RECORDS FROM UNSUPPORTEDPRODUCT RELEASES WAS ..., the input data (such as input data in DPMOUT format) was created byearlier versions of OMEGAMON XE for DB2 PE or OMEGAMON XE for DB2 PM and is no longer supported.

Identifying missing IFCIDsReport sets such as Accounting, Locking, or Statistics require specific IFCIDs from DB2 instrumentationdata. If the input data sets (specified with the INPUTDD statement in your job stream) do not containthese IFCIDs, the generated report ends with NO DATA TO REPORT.

For example, an Accounting report requires IFCIDs 3 and 239 in the input data. If the job summary logshows nothing more than in the following example (no IFCIDs 3 and 239), your Accounting report remainsempty.

INPUT INPUT PROCESSED PROCESSED IFCID COUNT PCT OF TOTAL COUNT PCT OF TOTAL ------- ---------- ------------ ---------- ------------ 1 89 33.58% 0 0.00% 2 88 33.20% 0 0.00%

Note: The job summary log gives a clear indication about which IFCIDs are contained in your input data. Ifan IFCID is not listed in the IFCID column or the INPUT COUNT column shows a count of 0, your inputdata does not contain this IFCID.

Reasons for missing IFCIDsIFCIDs might be missing in your reports because they are either not collected (missing in the input datafor the report generation) or being accidentally suppressed or filtered by inappropriate use of commands,subcommands, or subcommand options.

To identify why specific IFCIDs are not collected, review the methods of how the data was collected. Forexample, the DB2 startup parameters might determine that certain trace classes (with their impliedIFCIDs) are not started.

If your input data to specific reports contains the required IFCIDs, but your reports still do not show anydata, it is likely that restrictive command or subcommand options are in use in your job stream.

• The GLOBAL command might apply global filters to all data serving as input to subsequent OMEGAMONXE for DB2 PE commands like ACCOUNTING or STATISTICS.

• OMEGAMON XE for DB2 PE commands like ACCOUNTING or STATISTICS might use subcommandoptions that further restrict the data. The most important ones are:

– FROM/TO might limit the time frame too much.– INCLUDE/EXCLUDE might limit a DB2 trace class or an IFCID.

For example, a Statistics report requires IFCIDs 1 and 2. The following job summary log shows that 48records of each IFCID are included in the input data. However, none of these are being processed(PROCESSED COUNT equals 0) during the report generation and consequently the Statistics report isempty.

INPUT INPUT PROCESSED IFCID COUNT PCT OF TOTAL COUNT ------- ---------- ------------ ---------- 1 48 25.00% 0 2 48 25.00% 0


Insufficient amount of Statistics record pairs (IFCIDs 1 and 2)Output in a Statistics report requires at least two DB2 Statistics record pairs (IFCIDs 1 and 2) in the inputdata. These IFCIDs are collected at a configurable interval (DB2 system parameter STATIME).

An empty Statistics report usually indicates that either the input data does not cover at least two intervalsor that filters restrict the amount of data being processed during report generation.

The following example of a job summary log shows that a sufficient amount of IFCID 1 and 2 records arein the input data (INPUT COUNT column). However, filters have limited the number of processed recordsbelow the required minimum of two record pairs (PROCESSED COUNT column). Consequently, theStatistics report is empty.

INPUT INPUT PROCESSED PROCESSED IFCID COUNT PCT OF TOTAL COUNT PCT OF TOTAL ------- ---------- ------------ ---------- ------------ 1 48 25.00% 1 1.02% 2 48 25.00% 1 1.02%

The following job stream example shows how improper use of subcommand options cause an emptyStatistics report. Here, the REDUCE step causes a summarization of input data to an interval of 60minutes, with a boundary to the start of the hour. However, in the REPORT step the FROM and TOsubcommand options limit the data to 30 minutes, which is less than a single interval.

⋮STATISTICS REDUCE INTERVAL(60) BOUNDARY(60) REPORT FROM (12/22/13,12:15:00.00) TO (12/22/13,12:45:00.00)⋮

Messages indicating incomplete Accounting data (IFCIDs 3 and 239)If the job summary log shows one or more of the following messages, incomplete Accounting data wasfound in the input data and your Accounting report might be incomplete. In the worst case, the reportmight end with NO DATA TO REPORT.

• FPEA4531I GENERAL ACCOUNTING DATA FOR LUWID INSTANCE <V1> IS MISSING. IFCID 3IS MISSING.

• FPEA4532I ACCOUNTING DATA FOR A NUMBER OF PACKAGES FOR LUWID <V1> IS MISSING.ONE OR MORE IFCID 239 IS MISSING.

• FPEA4534I COORDINATING PARALLEL TASK FOR LUW INSTANCE <V1> IS NOT REPORTED ASNOT ALL INFORMATION FOR ASSISTING PARALLEL TASKS FROM MEMBER <V1> ISAVAILABLE.

Accounting reports require IFCID 3 for reporting a thread. However, package or program data belonging toa thread is contained in multiple 239 IFCIDs. A 1:n relation is established within the data. For correctreporting a complete set of these IFCIDs is required in the input data.

In case of DB2 Query Parallelism, additional sets of IFCIDs 3 and 239 are required. They were createdfrom parallel processors or from DB2 systems that assisted an initiating agent. Dependent on the degreeof parallelism, this can result in a 1:p relation between agent and parallel tasks. In other words, correctAccounting processing needs from the agent one IFCID 3 and n IFCIDs 239, and for each of the p paralleltasks also one IFCID 3 and a certain number of IFCIDs 239.

Accounting processing needs a complete set of these IFCIDs for a correct reporting. If either IFCIDs 239belonging to an IFCID 3 are missing, or if IFCIDs 239 are available but their IFCID 3 is missing, the entirethread is excluded from further processing and reporting.


Product legal notices

This information was developed for products and services offered in the U.S.A.

This material may be available from IBM in other languages. However, you may be required to own a copyof the product or product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense 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 PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan

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

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

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

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

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

The licensed program described in this information and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurements may have been estimated


through extrapolation. Actual results may vary. Users of this document should verify the applicable datafor their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. ©Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information

This publication documents intended Programming Interfaces that allow the customer to write programsto obtain the services of OMEGAMON for Db2 Performance Expert.

This publication documents information that is NOT intended to be used as Programming Interfaces ofOMEGAMON for Db2 Performance Expert.

This publication primarily documents intended Programming Interfaces that allow the customer to writeprograms to obtain the services of OMEGAMON for Db2 Performance Expert.

This publication also documents information that is NOT intended to be used as Programming Interfacesof OMEGAMON for Db2 Performance Expert. This information is identified where it occurs by anintroductory statement to a topic or section.

This publication primarily documents information that is NOT intended to be used as ProgrammingInterfaces of OMEGAMON for Db2 Performance Expert.

This publication also documents intended Programming Interfaces that allow the customer to writeprograms to obtain the services of OMEGAMON for Db2 Performance Expert. This information is identifiedwhere it occurs by an introductory statement to a topic or section.

Trademarks

492 Product legal notices

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at http://www.ibm.com/legal/copytrade.html.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Xeon, IntelSpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

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

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnites 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.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions:

Applicability: These terms and conditions are in addition to any terms of use for the IBM website.

Personal use: You may reproduce these publications for your personal, noncommercial use provided thatall proprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial use: You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not make derivative works ofthese publications, or reproduce, distribute or display these publications or any portion thereof outsideyour enterprise, without the express consent of IBM.

Rights: Except as expressly granted in this permission, no other permissions, licenses or rights aregranted, either express or implied, to the publications or any information, data, software or otherintellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS AREPROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,AND FITNESS FOR A PARTICULAR PURPOSE.

Privacy policy considerations

IBM Software products, including software as a service solutions, ("Software Offerings") may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering’s use of cookies is set forth below.

Product legal notices 493

http://www.ibm.com/legal/copytrade.html

This Software Offering does not use cookies or other technologies to collect personally identifiableinformation.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, seeIBM’s Privacy Policy at http://www.ibm.com/privacy and the section titled "Cookies, Web Beacons, andOther Technologies" in IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details. Also, seethe "IBM Software Products and Software-as-a-Service Privacy Statement" at http://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/software/info/product-privacy

Index

Aaccessibility features 2auxiliary command

troubleshooting command 481

Ccomments, sending 3cookie policy 491, 493

Ddiagnostics 486DUMP command 481

Eempty reports 487error messages, IBM support 8

IIBM support 8

Llegal notices

cookie policy 491, 493notices 491programming interface information 491, 492trademarks 491–493

Mmessage

FPEA4531I 489FPEA4532I 489FPEA4534I 489FPEC4015I 488

modal dialog boxes 486

Nnotices 491, 492

OOMEGAMON Collector

restarting 487

PPerformance Expert Client

Performance Expert Client (continued)Performance Expert Client does work correctly afterstartup 486

programming interface information 491, 492

Ssending comments 3service 2support home website 2

TTAPECOPY command 483trademarks 491–493troubleshooting

error 481launching Netscape as HTML browser 486main menu 481Performance Expert Client does work correctly afterstartup 486responding to dialog boxes 486restarting OMEGAMON Collector 487running a CONVERT step with an incorrect data set 487solving code-page problems when accessingPerformance Warehouse 487

troubleshooting commandDUMP command 481TAPECOPY command 483

Uupdates 2

Index 495

IBM®

Product Number: 5655-W37

GH12-7067

Messages and Troubleshooting Guide - IBM

Documents

Transcript of Messages and Troubleshooting Guide - IBM