IBM Tivoli Decision Support for z/OS

Version 1.8.2

Messages and Problem Determination



SH19-6902-15
IBM Tivoli Decision Support for z/OS
Version 1.8.2

Messages and Problem Determination



SH19-6902-15
 Before using this information and the product it supports, read the information in “Notices” on page 135.

Fourteenth Edition (March 2015)

This edition applies to version 1, release 8, modification level 2 of Tivoli Decision Support for z/OS (program
number 5698-B06) and to all subsequent releases and modifications until otherwise indicated in new editions.

© COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION. ALL RIGHTS RESERVED. Note to

U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp. 1994, 2015
Contents
Figures . . . . . . . . . . . . . . . v Running the Systems Diagnostics extract . . 92
Abnormal Termination (ABEND) . . . . . . 92
Preface . . . . . . . . . . . . . . vii Message (MSG) . . . . . . . . . . . . 93
Loop (LOOP) Procedure . . . . . . . . . 94
Who should read this book . . . . . . . . . vii
Incorrect Output (INCORROUT) Procedure. . . 95
What this book contains . . . . . . . . . . vii
Performance (PERFM) Procedure . . . . . . 95
Publications . . . . . . . . . . . . . . viii
Documentation (DOC) procedure . . . . . . 95
Tivoli Decision Support for z/OS library . . . viii
Collecting Documentation about All Problems . . . 96
Accessing terminology online . . . . . . . ix
Reporting the Problem to IBM . . . . . . . . 97
Accessing publications online . . . . . . . ix
Talking with a Level 1 Representative . . . . 97
Accessibility . . . . . . . . . . . . . . x
Talking with a Level 2 Representative . . . . 97
Tivoli technical training. . . . . . . . . . . x
Preparing Supporting Materials. . . . . . . 98
Support information . . . . . . . . . . . . x
Completing a Tivoli Decision Support for z/OS
Conventions used in this book . . . . . . . . x
Problem Description Worksheet. . . . . . . . 98
Typeface conventions . . . . . . . . . . xi
Changes in this edition . . . . . . . . . . xi
Chapter 4. Workstation Problem
Determination Procedure . . . . . . . 99
Part 1. Messages . . . . . . . . . . 1
Classifying a Problem . . . . . . . . . . . 99
Information Needed for All Problems. . . . . . 99
Chapter 1. Host Messages . . . . . . . 3 Specifying your Hardware and Software
Log Collector and Installation Preprocessing Environment . . . . . . . . . . . . . 99
Messages . . . . . . . . . . . . . . . 3 Collecting Documentation about All Problems . . 100
Examples of Output from COLLECT, PURGE Collecting Information about Specific Problems . . 101
and RECALCULATE . . . . . . . . . . 34 TRAP . . . . . . . . . . . . . . . 101
REXX-SQL Interface Messages . . . . . . . . 35 Message (MSG). . . . . . . . . . . . 101
IMS Feature Messages . . . . . . . . . . . 37 Loop (LOOP) Procedure . . . . . . . . . 101
CICS Feature Messages . . . . . . . . . . 48 Incorrect Output (INCORROUT) Procedure . . 102
AS/400 Messages . . . . . . . . . . . . 50 Performance (PERFM) Procedure . . . . . . 102
DEFINE/DROP Report and Report Group Messages Documentation (DOC) Procedure. . . . . . 102
(REXX Utility) . . . . . . . . . . . . . 51 Reporting the Problem to IBM. . . . . . . . 103
Batch Reporting Messages (REXX Utility) . . . . 55 Completing the Tivoli Decision Support for z/OS
Migration Messages . . . . . . . . . . . 59 Workstation Problem Description Worksheets. . . 103
Information/Management Record Creation
(Exception Reporting) Messages . . . . . . . 63
Log Data Manager Messages . . . . . . . . 64 Part 3. Appendixes . . . . . . . . 105
Web Reporting Messages . . . . . . . . . . 68
Usage and Accounting Collector Messages . . . . 69 Appendix A. Dump File Content and
Trace Options . . . . . . . . . . . 107
Chapter 2. AS/400 Messages Issued on Information in the Dump File . . . . . . . . 107
AS/400 System . . . . . . . . . . . 85 Abend Information . . . . . . . . . . 107
User Abend Codes . . . . . . . . . . 108
Trace Information . . . . . . . . . . . 108
Part 2. Problem Determination . . . 87 Record or Row Reject Information . . . . . 109
Error Situations Recording . . . . . . . . 110
Chapter 3. Host Problem Determination Dialog Trace . . . . . . . . . . . . . . 110
Procedure . . . . . . . . . . . . . 89
Classifying a Problem . . . . . . . . . . . 89 Appendix B. Using IBM-supplied
Using Keywords to Describe a Problem . . . . 89 Diagnostic and Service Aids . . . . . 113
Searching the Software Support Database . . . 90 First Failure Support Technology . . . . . . . 113
Identifying Symptoms and Selecting Keywords 90 Implementation. . . . . . . . . . . . 113
Collecting Information about Any Problem . . . . 91 Data-dump Content . . . . . . . . . . 114
Specifying Your Software Environment . . . . 91 FFST Message . . . . . . . . . . . . 114
Information Needed for All Problems. . . . . 92 FFST Symptom String . . . . . . . . . 114
Collecting Information about specific problems . . 92 Tivoli Decision Support for z/OS Data Areas 115
System Diagnostics . . . . . . . . . . . 92 Data-dump Formatter . . . . . . . . . 115

iii
 Operator Commands . . . . . . . . . . 116 Searching the Internet . . . . . . . . . 131
Output Options. . . . . . . . . . . . 117 Obtaining fixes . . . . . . . . . . . . . 131
Receiving weekly support updates . . . . . . 132
Appendix C. Problem Description Contacting IBM Software Support . . . . . . 132
Worksheet for the Host . . . . . . . 119 Determining the business impact . . . . . . 133
Describing problems and gathering information 134
Submitting problems . . . . . . . . . . 134
Appendix D. Problem Description
Worksheet for the Workstation Notices . . . . . . . . . . . . . . 135
Performance Feature . . . . . . . . 123 Trademarks . . . . . . . . . . . . . . 137

Appendix E. Problem Description Bibliography . . . . . . . . . . . . 139

Worksheet for the AS/400 System TDS publications . . . . . . . . . . . . 139
Performance Feature . . . . . . . . 127
Glossary . . . . . . . . . . . . . 141
Appendix F. Support information . . . 131
Searching knowledge bases . . . . . . . . . 131 Index . . . . . . . . . . . . . . . 143
Searching the information center . . . . . . 131

iv Tivoli Decision Support for z/OS: Messages and Problem Determination

Figures
1. An Example of Messages Generated by a 6. Tivoli Decision Support for z/OS Problem
COLLECT Statement . . . . . . . . . 34 Description Worksheet (Part 2 of 3) . . . . 120
2. An Example of Messages Generated by a 7. Tivoli Decision Support for z/OS Problem
PURGE Statement . . . . . . . . . . 35 Description Worksheet (Part 3 of 3) . . . . 120
3. An Example of Messages Generated by a 8. Workstation Performance Feature Problem
RECALCULATE Statement . . . . . . . 35 Description Worksheet . . . . . . . . 124
4. Set/Reset Trace Options Window . . . . . 111 9. AS/400 Feature Problem Description
5. Tivoli Decision Support for z/OS Problem Worksheet . . . . . . . . . . . . 128
Description Worksheet (Part 1 of 3) . . . . 119

v
vi Tivoli Decision Support for z/OS: Messages and Problem Determination
Preface
This book helps you identify and correct problems that can occur when using
IBM® Tivoli® Decision Support for z/OS® (hereafter also referred to as Tivoli
Decision Support for z/OS).

The terms MVS™, OS/390®, and z/OS are used interchangeably throughout this
book.

Who should read this book

This book is for users who:
v Need more information about a Tivoli Decision Support for z/OS message.
v Determine corrections to error conditions indicated by Tivoli Decision Support
for z/OS messages.
v Identify and document a Tivoli Decision Support for z/OS problem.
v Determine whether the problem is an installation error, a usage error, or an error
in the Tivoli Decision Support for z/OS product code.
v Report Tivoli Decision Support for z/OS problems to IBM.

These users can be system programmers, Tivoli Decision Support for z/OS
administrators, or users of a Tivoli Decision Support for z/OS feature.

Note: To get immediate message help for messages that occur when you are using
the Tivoli Decision Support for z/OS dialogs on the host and on the workstation,
press F1.

What this book contains

This book contains the following parts:

Part 1, “Messages,” on page 1

v Chapter 1, “Host Messages,” on page 3 lists the Tivoli Decision Support for
z/OS messages and their severity codes. It also explains each message, describes
the system action, and recommends a user response.
v Chapter 2, “AS/400 Messages Issued on AS/400 System,” on page 85 lists the
AS/400 messages that are issued on the AS/400 system. It also explains each
message, describes the system action, and recommends a user response.

Part 2, “Problem Determination,” on page 87 contains information needed to

diagnose and correct problems and addresses these tasks:
v Chapter 3, “Host Problem Determination Procedure,” on page 89 explains how
to determine whether Tivoli Decision Support for z/OS caused the problem,
search a software-support database to determine if the problem has been
reported previously, and how to isolate failing program code and find a solution.
v Chapter 4, “Workstation Problem Determination Procedure,” on page 99 explains
how to isolate failing program code and find a solution.

Part 3, “Appendixes” contains the following information:

vii
What This Book Contains

v Appendix A, “Dump File Content and Trace Options,” on page 107 describes the
contents of the DRLDUMP data set and how to activate traces.
v Appendix B, “Using IBM-supplied Diagnostic and Service Aids,” on page 113
describes the IBM licensed program that provides immediate problem
notification and first-failure data capture.
v Appendix C, “Problem Description Worksheet for the Host,” on page 119
contains a problem description worksheet for the host.
v Appendix D, “Problem Description Worksheet for the Workstation Performance
Feature,” on page 123 contains a problem description worksheet for the
Workstation Performance featureWorkstation Performance feature.
v Appendix E, “Problem Description Worksheet for the AS/400 System
Performance Feature,” on page 127 contains a problem description worksheet for
the AS/400 System Performance feature.
v Appendix F, “Support information,” on page 131 describes how to obtain
support for IBM software products.

Publications
This section lists publications in the Tivoli Decision Support for z/OS library and
any other related documents. It also describes how to access Tivoli publications
online, how to order Tivoli publications, and how to submit comments on Tivoli
publications.

Tivoli Decision Support for z/OS library

The following documents are available in the Tivoli Decision Support for z/OS
library:
v Administration Guide and Reference, SH19-6816
Provides information about initializing the Tivoli Decision Support for z/OS
database and customizing and administering Tivoli Decision Support for z/OS.
v AS/400 System Performance Feature Guide and Reference, SH19-4019
Provides information for administrators and users about collecting and reporting
performance data generated by AS/400 systems.
v CICS Performance Feature Guide and Reference, SH19-6820
Provides information for administrators and users about collecting and reporting
performance data generated by Customer Information and Control System
(CICS®).
v Distributed Systems Performance Feature Guide and Reference, SH19-4018
Provides information for administrators and users about collecting and reporting
performance data generated by operating systems and applications running on a
workstation.
v Guide to Reporting, SH19-6842
Provides information for users who display existing reports, for users who create
and modify reports, and for administrators who control reporting dialog default
functions and capabilities.
v IMS Performance Feature Guide and Reference, SH19-6825
Provides information for administrators and users about collecting and reporting
performance data generated by Information Management System (IMS™).
v Language Guide and Reference, SH19-6817
Provides information for administrators, performance analysts, and
programmers who are responsible for maintaining system log data and reports.

viii Tivoli Decision Support for z/OS: Messages and Problem Determination
 Tivoli Decision Support for z/OS library

v Messages and Problem Determination, SH19-6902

Provides information to help operators and system programmers understand,
interpret, and respond to Tivoli Decision Support for z/OS messages and codes.
v Network Performance Feature Installation and Administration, SH19-6901
Provides information for network analysts or programmers who are responsible
for setting up the network reporting environment.
v Network Performance Feature Reference, SH19-6822
Provides reference information for network analysts or programmers who use
the Network Performance feature.
v Network Performance Feature Reports, SH19-6821
Provides information for network analysts or programmers who use the
Network Performance feature reports.
v Resource Accounting for z/OS, SH19-4495
Provides information for users who want to use Tivoli Decision Support for
z/OS to collect and report performance data generated by Resource Accounting
for z/OS.
v System Performance Feature Guide, SH19-6818
Provides information for performance analysts and system programmers who
are responsible for meeting the service-level objectives established in your
organization.
v System Performance Feature Reference Volume I, SH19-6819
Provides information for administrators and users with a variety of backgrounds
who want to use Tivoli Decision Support for z/OS to analyze z/OS, z/VM®,
zLinux, and their subsystems, performance data.
v System Performance Feature Reference Volume II, SH19-4494
Provides information for administrators and users with a variety of backgrounds
who want to use Tivoli Decision Support for z/OS to analyze z/OS, z/VM,
zLinux, and their subsystems, performance data.
v Usage and Accounting Collector User Guide, SC23-7966
Provides information about the functions and features of the Usage and
Accounting Collector.
v IBM Online Library z/OS Software Products Collection Kit, SK3T-4270
CD containing all z/OS documentation.

Accessing terminology online

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

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

Accessing publications online

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

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

Preface ix
Accessing publications online

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click the Tivoli Decision Support for
z/OS link to access the product library at the Tivoli software information center.

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

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

For additional information, see the Accessibility Appendix in the Administration

Guide and Reference.

Tivoli technical training

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

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

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v Contacting IBM Software Support: If you still cannot solve your problem, and
you need to work with someone from IBM, you can use a variety of ways to
contact IBM Software Support.

For more information about these three ways of resolving problems, see
Appendix F, “Support information,” on page 131.

Conventions used in this book

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

The following terms are used interchangeably throughout this book:

v MVS, OS/390, and z/OS.
v VM and z/VM.

Except for editorial changes, updates to this edition are marked with a vertical bar
to the left of the change.

x Tivoli Decision Support for z/OS: Messages and Problem Determination

 Typeface conventions

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip, and Operating system considerations)
v Column headings in a table
v Keywords and parameters in text
Italic
v Citations (titles of books, diskettes, and CDs)
v Words defined in text
v Emphasis of words (words as words)
v Letters as letters
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Changes in this edition

This edition is an update of the previous edition of the same book. The changes
relate to 1.8.2 GA APAR documentation, and subsequent APARs.
v
v New message are:
– “DRL0471E” on page 32
– “DRL0472E” on page 32

Except for editorial changes, updates to this edition are marked with a vertical bar
[|] to the left of the change.

Preface xi
Changes in this edition

xii Tivoli Decision Support for z/OS: Messages and Problem Determination
Part 1. Messages
Chapter 1. Host Messages . . . . . . . . . 3
Log Collector and Installation Preprocessing
Messages . . . . . . . . . . . . . . . 3
Examples of Output from COLLECT, PURGE
and RECALCULATE . . . . . . . . . . 34
REXX-SQL Interface Messages . . . . . . . . 35
IMS Feature Messages . . . . . . . . . . . 37
CICS Feature Messages . . . . . . . . . . 48
AS/400 Messages . . . . . . . . . . . . 50
DEFINE/DROP Report and Report Group Messages
(REXX Utility) . . . . . . . . . . . . . 51
Batch Reporting Messages (REXX Utility) . . . . 55
Migration Messages . . . . . . . . . . . 59
Information/Management Record Creation
(Exception Reporting) Messages . . . . . . . 63
Log Data Manager Messages . . . . . . . . 64
Web Reporting Messages . . . . . . . . . . 68
Usage and Accounting Collector Messages . . . . 69

Chapter 2. AS/400 Messages Issued on AS/400

System . . . . . . . . . . . . . . . 85

1
2 Tivoli Decision Support for z/OS: Messages and Problem Determination
Chapter 1. Host Messages
Tivoli Decision Support for z/OS is a reporting system that collects performance
data logged by computer systems, summarizes the data, and presents it in a
variety of forms for use in systems management. Tivoli Decision Support for z/OS
consists of a base product and several optional features.

This chapter contains descriptions of messages generated during batch processing

and when the log collector is invoked from the online dialog. The messages
include any that are a result of log collector language use, report definition
language use, abends, and any other Tivoli Decision Support for z/OS error
conditions from batch processes. (Messages that occur when you are working with
Tivoli Decision Support for z/OS dialogs are explained in the message help; they
are not described in this book.)

Tivoli Decision Support for z/OS host messages use this format:
DRLnnnnc Message text.

Where:
v DRL identifies the message as having been issued by Tivoli Decision Support for
z/OS.
v nnnn is a unique four-digit number assigned to the message:
– 0nnn indicates a log-collector message.
– 1nnn indicates a REXX/SQL interface message.
– 2nnn indicates an exit (for example, CICS or IMS) message.
– 3nnn indicates a REXX utility (for example, DRLERDEF or DRLEBATR)
message.
v c is the severity code:
– I represents an informational message, with return code=0.
– W represents a warning message, with return code=4.
– E represents an error message, with return code=8.
– S represents a severe message, with return code=12.
– T represents a terminating error message, with an Abend return code. (See
“User Abend Codes” on page 108.)
v Message text is descriptive text about Tivoli Decision Support for z/OS status or
operation.

Log Collector and Installation Preprocessing Messages

As explained in the Language Guide and Reference, the log collector is a program that
processes data from log data sets and stores the results in tables. It runs either
online (invoked from the Tivoli Decision Support for z/OS dialogs) or in batch
(executed using z/OS job control language). In each case, the log collector must
have an output file DRLOUT allocated to it. This section describes the messages
that the log collector writes to the DRLOUT file.

Note: The system action associated with a message is often described as this:
The log collector stops processing the current statement and
continues with the next.

3
DRL0000T • DRL0012E

It means that the statement has no effect; the exception is COLLECT, if the error
occurs after a commit. In many cases, the log collector continues checking the
statement, without executing it, so more messages about the same statement might
appear.

The installation preprocessor is a program which is used during component

installation. Since it shares error recovery routines with the log collector, the
installation preprocessor can also issue some of the following messages.

User response: Ensure that a usable file is allocated.

DRL0000T The log collector run terminated
abnormally. The DRLDUMP file
contains detailed information. DRL0003I
Explanation: The program run terminated abnormally Explanation: This message is used to insert a blank
for one of these reasons: line between other messages. (For an example, see
v An operating system service invoked by the program Figure 1 on page 34.)
requested an abnormal termination. System action: None.
v The program detected an abnormal situation, such as
an unexpected return code from SQL, an unexpected User response: None.
program check interrupt, or an invalid value of some
variable. DRL0007S "text" is an invalid parameter.
v The dynamic storage stack was exceeded.
Explanation: text appears as a keyword in the
System action: Detailed information about the parameter string supplied to the program (typically as
problem is written to the DRLDUMP file. The the PARM string of the JCL EXEC statement). However,
completion code (abend code) depends on what caused text is not among the keywords recognized by the
the termination: program.
v If the termination was requested by the operating System action: The program stops without processing
system, the code is the one supplied by the system. It any more statements.
identifies the reason for the termination.
User response: Correct the parameter string.
v If the termination is caused by a should-not-occur
situation detected by the program, the code is user
abend code 2 (U002). DRL0011E Information about update update in
v If the reason is dynamic stack overflow, the code is system table system table is damaged.
user abend code 1 (U001). Restore the update definition.

User response: Use the abend code and the Explanation: The contents of the system table system
information written to the DRLOUT and DRLDUMP table are damaged, perhaps because something other
files to establish the reason for termination. The than the log collector was used to update the table. The
termination may be caused by a program error in your damaged information is a part of the definition of the
exit procedure or in the program. If you suspect an update update. The definition cannot be used.
error in the program, save the contents of the System action: The log collector stops processing the
DRLDUMP file, and note as much detail as possible of current statement and continues with the next.
what you were doing when the error occurred. Report
the error to IBM as explained in “Reporting the User response: Execute the DROP UPDATE and
Problem to IBM” on page 97. DEFINE UPDATE statements for the update update to
restore the definition.

DRL0001T The log collector run is terminated

because the ddname file is not available. DRL0012E Information about record record in
system table system table is damaged.
Explanation: This message is preceded by a message Restore the record definition.
identifying a problem with the ddname file (DRLOUT or
DRLDUMP). Because of this problem, the file can no Explanation: The contents of the system table system
longer be used; however, the program needs the file for table are damaged, perhaps because something other
its operation. than the log collector was used to update the table. The
damaged information is a part of the definition of the
System action: The program is abnormally terminated record record. The definition cannot be used.
with abend code U016. No more information is
provided about the problem. System action: The log collector stops processing the
current statement and continues with the next.

4 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0021E • DRL0034E

User response: Execute the DROP RECORD and User response: Check the output for more messages
DEFINE RECORD statements for the record record to about the error. Study the cause of the error and act
restore the definition. accordingly.

DRL0021E The file ddname could not be opened. DRL0031E The statement "text" is not recognized.
Explanation: The log collector cannot open the ddname Explanation: The text appears in a place where a
file. statement name is expected. However, it is not the
name of any statement of the log collector language.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Ensure that the file exists and can be
opened. User response: Check the syntax diagram in Language
Guide and Reference and correct the statement. Notice
that the different clauses of the statement must be
DRL0022E Abend code encountered accessing file
written in the order shown in the diagram. Notice also
ddname.
that the error might be located much earlier in the
Explanation: The program encountered an abend input than the token text. A large portion of input
when accessing the ddname file. extending past the error might still conform to the
syntax. The message identifies the point where the
System action: The program stops processing the input no longer matches the syntax.
current statement and continues with the next.
User response: Check the output for more messages DRL0032E The variable variable does not exist.
about the error. For example, if the file is an input file,
processing is interrupted. If the file is an output file, an Explanation: The input text contains a variable marker
out-of-space condition might have occurred. Study the &variable, but the variable variable is not defined.
cause of the error and act accordingly.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0023E Block count error encountered after n
User response: Specify a value for the variable using
records on ddname file.
the SET statement or PARM string of the JCL EXEC
Explanation: The program encountered a block count statement. Notice that all variables are dropped at the
error after n records in the ddname file. end of the log collector run.

System action: The program stops processing the

current statement and continues with the next. DRL0033E The expression or condition starting
with text is too long or too complex.
User response: Check the output for more messages
about the error. Study the cause of the error and act Explanation: Either the expression or condition text,
accordingly. or its internal representation is longer than 2000
characters.

DRL0024E Permanent I/O error encountered after n System action: The log collector stops processing the
records on file ddname. current statement and continues with the next.

Explanation: The program encountered an I/O error User response: Try to simplify the expression or
after n records in the ddname file. condition. Is it part of an update definition? Then you
can break out parts of the expression and put them in
System action: The program stops processing the the LET clause.
current statement and continues with the next.
User response: Check the output for more messages DRL0034E "text" is not a valid variable marker.
about the error. Study the cause of the error and act
accordingly. Explanation: The text begins with an ampersand, but
is not a valid variable marker. A variable marker
consists of an ampersand (&) followed by an identifier.
DRL0025E Block size error encountered after n
records on file ddname. System action: The log collector stops processing the
current statement and continues with the next.
Explanation: The program encountered a block size
error after n records in the ddname file. User response: Correct the variable marker.
System action: The program stops processing the
current statement and continues with the next.

Chapter 1. Host Messages 5

DRL0035E • DRL0042E

DRL0035E An invalid field format "text" is DRL0039E "text" is not a valid floating-point
specified for field field. constant.
Explanation: text was specified as the field format for Explanation: The token text looks like a floating-point
the field field, but it does not identify any field format constant, but is not a valid floating-point constant (for
known to the log collector. example: the exponent is incomplete or is outside the
allowed range).
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Refer to Language Guide and Reference
for a list of valid field formats. User response: Correct the constant.

DRL0036E The offset of the field field is undefined. DRL0040E Syntax error: unexpected text "" (two
Offset must be specified when the quotation marks) is found.
previous field format is CHAR(*).
Explanation: Two consecutive quotation marks were
Explanation: The offset of field has been omitted. The found where they are not allowed by the syntax.
offset cannot be determined because the previous field Consecutive quotation marks are allowed only within a
has the format CHAR(*), and no field can follow a field delimited identifier, string constant, or comment.
with that format.
System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next.
User response: Correct the error.
User response: Add an offset specification for the
field.
DRL0041E Syntax error: unexpected text "text" is
found.
DRL0037E The format specified for the field field
Explanation: The token text was found where it is not
conflicts with the length of the field.
allowed by the syntax.
Explanation: A given format can only be specified for
System action: The log collector stops processing the
fields of certain lengths. For example:
current statement and continues with the next.
v DATE(DDMMYY) can only be specified for a 6-byte
field. User response: Check the syntax diagram in Language
Guide and Reference and correct the statement. Notice
v BINARY can only be specified for a field of 1, 2, 3, 4,
that different clauses of the statement must be written
or 8 bytes.
in the order shown in the diagram. Notice also that the
v BIT(16) can only be specified for a 2-byte field. error might be located much earlier in the input than
v CHAR(*) can only be specified for a varying-length the token text. A large portion of input extending past
field (a field with LENGTH *). the error might still conform to the syntax. The
message identifies the point where the input no longer
System action: The log collector stops processing the
matches the syntax.
current statement and continues with the next.
User response: Refer to Language Guide and Reference
DRL0042E Syntax error: unexpected text "text1" is
for information about the lengths allowed for different
found after "text2".
field formats. Ensure that the format agrees with the
length specification. Explanation: The token text2, which conforms to the
syntax, was followed by the token text1. The syntax
does not allow this sequence.
DRL0038E "text" is not a valid integer constant.
System action: The log collector stops processing the
Explanation: The token text looks like an integer
current statement and continues with the next.
constant, but is not a valid integer constant (for
example, its value is outside the range of integers). User response: Check the syntax diagram in Language
Guide and Reference and correct the statement. Notice
System action: The log collector stops processing the
that different clauses of the statement must be written
current statement and continues with the next.
in the order shown in the diagram. Notice also that the
User response: Correct the constant. error might be located much earlier in the input than
the token text1. A large portion of input extending past
the error might still conform to the syntax. The
message identifies the point where the input no longer
matches the syntax.

6 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0043E • DRL0051E

User response: Change the string.

DRL0043E Syntax error: "text1" found where text2 is
expected.
DRL0047E The delimited identifier starting with
Explanation: The token text1 was found where it is
text is not terminated.
not allowed by the syntax. The text2 states what the
syntax allows in place of text1. Explanation: A delimited identifier ("identifier")
without an ending quotation mark (") was found.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Check the syntax diagram in Language
Guide and Reference and correct the statement. Notice User response: Add the quotation mark (") at the end
that different clauses of the statement must be written of the identifier.
in the order shown in the diagram. Notice also that the
error might be located much earlier in the input than
the token text1. A large portion of input extending past DRL0048E The string starting with text is not
the error might still conform to the syntax. The terminated.
message identifies the point where the input no longer Explanation: A string constant without an ending
matches the syntax. apostrophe (‘) was found.
System action: The log collector stops processing the
DRL0044E Syntax error: "text1" found after "text2", current statement and continues with the next.
where text3 is expected.
User response: Add the apostrophe (‘) to the end of
Explanation: The token text1 was found following the string constant.
text2, where it is not allowed by the syntax. The text3
states what the syntax allows in place of text1.
DRL0049E An invalid character "c" is found.
System action: The log collector stops processing the
current statement and continues with the next. Explanation: The input text contains a character that
is not valid.
User response: Check the syntax diagram in Language
Guide and Reference and correct the statement. Notice System action: The log collector stops processing the
that different clauses of the statement must be written current statement and continues with the next.
in the order shown in the diagram. Notice also that the User response: Correct the character. Refer to Language
error might be located much earlier in the input than Guide and Reference for a description of valid characters.
the token text1. A large portion of input extending past
the error might still conform to the syntax. The
message identifies the point where the input no longer DRL0050E An invalid character "c" is found after
matches the syntax. "text".
Explanation: The input text contains an invalid
DRL0045E The identifier starting with text is too character c after the text text.
long. The maximum length is 18 bytes. System action: The log collector stops processing the
Explanation: An identifier cannot exceed 18 bytes. The current statement and continues with the next.
length of a delimited identifier ("identifier") does not User response: Correct the character. Refer to Language
include the enclosing quotation marks. The length Guide and Reference for a description of valid characters.
includes any shift-out and shift-in characters that
enclose sequences of double-byte characters.
DRL0051E The preceding n message(s) refer to the
System action: The log collector stops processing the expression for name.
current statement and continues with the next.
Explanation: This message helps you locate the errors
User response: Change the identifier. indicated by the messages issued before this message.
If name is the name appearing to the left of an equal
DRL0046E The string starting with text is too long. sign in a LET, GROUP BY, or SET clause, the messages
The maximum length is 254 bytes. apply to the expression appearing to the right of that
equal sign. If name is a language keyword such as
Explanation: The string specified by a constant cannot WHERE or OFFSET, the messages apply to the
exceed 254 bytes. The length of the string includes any expression following that keyword.
shift-out and shift-in characters that enclose sequences
of double-byte characters. System action: The log collector stops processing the
current statement and continues with the next.
System action: The log collector stops processing the
current statement and continues with the next. User response: None.

Chapter 1. Host Messages 7

DRL0052E • DRL0057E

DRL0052E The expression is too complex. DRL0054E The field field belongs to a section that
cannot be referenced in this context.
Explanation: An expression contains a nested
structure of a depth that exceeds the capacity of Tivoli Explanation: The section containing the field field
Decision Support for z/OS. There are two kinds of cannot be referenced for one (or both) of these reasons:
nested structures: the parentheses and the constructs v The section is repeated, or is a subsection of a
involving alternatives (the VALUE function and case repeated section, and the present context does not
expressions). identify a unique occurrence of that repeated section.
The nesting depth of parentheses at a given point is v In a DEFINE RECORD statement, the section is
equal to the number of pairs of parentheses enclosing referenced before it is defined.
that point. The parentheses include those that are a part
System action: The log collector stops processing the
of function calls with more than one argument and the
current statement and continues with the next.
implicit parentheses inserted to enforce the precedence
of operations. For example, A*B+C*D has these implicit User response: Use the subsequent message
parentheses: (A*B)+(C*D). DRL0051E to identify the expression that contains the
reference. Refer to Language Guide and Reference for
The nesting depth of alternative structures at a given
exact rules. Restructure your definition so that the
point is the number of nested VALUE calls and case
required information is accessible.
expressions containing that point, plus the number of
preceding arguments within each VALUE call, plus the
number of preceding THEN clauses within each case DRL0055E The name abc specified as the first
expression. argument of FIELD is not a field name.
This message indicates that one or both of these nesting Explanation: The first argument of FIELD must be a
depths exceed the maximum that can be handled by field name.
Tivoli Decision Support for z/OS.
System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next.
User response: Use the subsequent message
User response: Use the subsequent message DRL0051E to identify the expression that contains the
DRL0051E to identify the expression in error. If invocation of FIELD. Ensure that the argument is a
possible, define parts of the expression separately, using field name.
LET. Otherwise, try to restructure the expression to
reduce the nesting depth. For example, change the
sequence of operators and specify complex cases first, DRL0056E The name abc specified as the argument
in case expressions. of SECTNUM is not a section name.
Explanation: The argument of SECTNUM must be a
DRL0053E The name abc is not defined. section name.

Explanation: abc is not among the names recognized System action: The log collector stops processing the
in the context where it is used. current statement and continues with the next.

Note that different names might be recognized in User response: Use the subsequent message
different parts of a statement. For example, the only DRL0051E to identify the expression that contains the
names recognized to the right of an equal sign in a SET invocation of SECTNUM. Ensure that the argument is a
clause of a DEFINE UPDATE statement are the names field name.
of fields in the record (or columns in the table) that is
the source of the update and the names defined by DRL0057E The section section cannot be referenced
means of a LET clause. in this context.
System action: The log collector stops processing the Explanation: The section cannot be referenced for one
current statement and continues with the next. (or both) of these reasons:
User response: Use the subsequent message v The section is repeated, or is a subsection of a
DRL0051E to locate the expression that contains the repeated section, and the present context does not
name. Refer to Language Guide and Reference for identify a unique occurrence of that repeated section.
information about the objects (such as fields or v In a DEFINE RECORD statement, the section is
columns) that can be referenced at a specific part of the referenced before it is defined.
statement. Specify the name of one of these objects.
System action: The log collector stops processing the
current statement and continues with the next.
User response: Use the subsequent message

8 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0060E • DRL0067E

DRL0051E to identify the expression that contains the User response: Ensure that all names introduced in an
reference. Refer to Language Guide and Reference for update definition are distinct from the names of
exact rules. Restructure your definition so that the columns in the source table.
required information is accessible.
DRL0065E Argument number n of function is of
DRL0060E The name abc is already defined. incorrect type.
Explanation: abc is specified as the name of: Explanation: In an invocation of function, the data
v A LET expression type of the indicated argument is not allowed for this
argument.
v The timestamp or interval column in a DISTRIBUTE
clause
Note: If function is one of the arithmetic, string, or
v The interval type, start time, end time, or status comparison operators such as +, | |, or =, argument
column in an APPLY SCHEDULE clause number 1 means the left-hand operand, and argument
However, the same name has been used earlier in the number 2 means the right-hand operand. If function is
same update definition for a similar purpose. prefix -, argument number 1 means the expression
following the operator.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Ensure that all names introduced in
the same update definition are unique. User response: Use the subsequent message
DRL0051E to identify the expression that contains the
invocation of the function. Refer to Language Guide and
DRL0061E The name identifier conflicts with a Reference for information on the allowed types of
source field name. arguments for function and for rules on the use of
Explanation: The identifier is specified as the name of: arithmetic, string, and comparison operators.

v A LET expression Ensure that the argument is of the required type. For
v The timestamp or interval column in a DISTRIBUTE example, use a constant of a different type, redefine a
clause field to yield a correct data type, or apply a conversion
function if suitable.
v The interval type, start time, end time, or status
column in an APPLY SCHEDULE clause
DRL0066E The arguments of function have an
However, identifier is also the name of a field in the incorrect combination of types.
record that is the source of the update. You cannot use
the name for the specified purpose because it causes Explanation: In an invocation of function, each of the
ambiguity. arguments by itself has a data type acceptable for that
argument, but the actual combination of data types of
System action: The log collector stops processing the the arguments is not allowed.
current statement and continues with the next.
System action: The log collector stops processing the
User response: Ensure that all names introduced in an current statement and continues with the next.
update definition are distinct from the names of fields
in the source record. User response: Use the subsequent message
DRL0051E to identify the expression that contains the
invocation of the function. Refer to Language Guide and
DRL0062E The name identifier conflicts with a Reference for information on the allowed types of
source column name. arguments for function and for rules on the use of
Explanation: The identifier is specified as the name of: arithmetic, string, and comparison operators.
v A LET expression Ensure that the arguments have an allowed
v The name of the timestamp or interval column in a combination of types. For example, use a constant of a
DISTRIBUTE clause different type, redefine a field to yield a correct data
type, or apply a conversion function if suitable.
v The interval type, start time, end time, or status
column in an APPLY SCHEDULE clause.
DRL0067E The arguments of VALUE are of
However, identifier is also the name of a column in the
different types.
table that is the source of the update. You cannot use
the name for the specified purpose because it causes Explanation: All arguments in an invocation of
ambiguity. VALUE must be of the same type.
System action: The log collector stops processing the System action: The log collector stops processing the
current statement and continues with the next. current statement and continues with the next.

Chapter 1. Host Messages 9

DRL0068E • DRL0075E

User response: Use the subsequent message constant of a different type, redefine a field to yield a
DRL0051E to identify the expression that contains the correct data type, or apply a conversion function if
invocation of the function. Ensure that all arguments suitable.
are the same type. For example, use a different type of
constant, redefine a field to yield a correct data type, or
DRL0071E The lookup table table or its column
apply a conversion function if suitable.
does not exist.
Explanation: A lookup expression is incorrect for one
DRL0068E The values specified for different cases
of these reasons:
are of different types.
v The lookup table (the table specified after the
Explanation: In a case expression, all expressions keyword IN) does not exist.
following the keywords THEN (and ELSE, if present)
v The lookup table exists, but it does not contain one
must specify the same type of values.
or more of the columns referenced in the expression.
System action: The log collector stops processing the
System action: The log collector stops processing the
current statement and continues with the next.
current statement and continues with the next.
User response: Use the subsequent message
User response: Use the subsequent message
DRL0051E to identify the expression. Ensure that all
DRL0051E to locate the expression. Ensure that the
expressions specify the same type of values. For
lookup table exists and has all the columns referenced
example, use a different type of constant, redefine a
in the expression.
field to yield a correct data type, or apply a conversion
function if suitable.
DRL0072E An error occurred executing an SQL
statement on table: sqlcode = sqlcode
DRL0069E The value specified for case n is of
incorrect type. Explanation: A DB2® error occurred when an SQL
command was issued on the specified table. The
Explanation: In a case expression, the expression that
sqlcode contains the return code from DB2.
follows the THEN keyword number n is not of a type
allowed for the result of a case expression (for example, System action: The action run ended.
a labeled duration or a truth value.)
User response: Refer to DB2 messages and codes,
SC26-4379, for an explanation of the cause.
Note: If the case expression contains nested case
expressions, the keywords THEN and ELSE of these
sub expressions are not included in the n. If the n is 1 DRL0075E Argument number n of function has an
greater than the number of THEN keywords in the incorrect value.
expression, it refers to the expression following the
ELSE keyword. Explanation: In an invocation of function, the indicated
argument is specified by means of a constant or a
System action: The log collector stops processing the combination of constants. The value thus specified is
current statement and continues with the next. not valid for this argument.
User response: Use the subsequent message
DRL0051E to locate the expression. Ensure that the Note: If function is one of the arithmetic, string, or
expression is of an allowed type. comparison operators such as +, | |, or =, argument
number 1 means the left-hand operand, and argument
number 2 means the right-hand operand. If function is
DRL0070E The keyword keyword, that identifies a prefix -, argument number 1 means the expression
labeled duration, follows a non-numeric following the operator.
expression.
System action: The log collector stops processing the
Explanation: The keyword keyword is supposed to current statement and continues with the next.
follow an expression that specifies the number of time
units identified by the keyword. The expression must User response: Use the subsequent message
specify a numeric value (that is, a value of type integer DRL0051E to identify the expression that contains the
or floating-point). invocation of the function. Refer to Language Guide and
Reference for information on the allowed values of
System action: The log collector stops processing the arguments for function and for rules on the use of
current statement and continues with the next. arithmetic, string, and comparison operators.
User response: Use the subsequent message Ensure that the argument has a correct value.
DRL0051E to locate the expression containing the
keyword. Ensure that the expression preceding the
keyword specifies a numeric value. For example, use a

10 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0076E • DRL0095E

User response: Ensure that the value to be assigned

DRL0076E The result of function is outside the
has a data type that is compatible with the type of the
range of values of type type.
column.
Explanation: The function is applied to argument(s)
specified as constants or combinations of constants. The
DRL0082E The column column is too short for the
result of function is supposed to be the type type, but
date/time value.
function applied to the specified values yields a value
outside that type (for example, a value larger than 231-1 Explanation: A date/time value (a date, a time, or a
when the result is supposed to be an integer). timestamp) is assigned to the column column which is
of the character string type. Before assignment, the
System action: The log collector stops processing the
value is converted to a character string. A date value is
current statement and continues with the next.
converted to a string of 10 characters; a time value is
User response: Use the subsequent message converted to a string of 8 characters; a timestamp value
DRL0051E to identify the expression that contains the is converted to a string of 26 characters. The column
invocation of the function. Ensure that you specify column is shorter than the resulting string, and the
correct values. assignment cannot be performed. (The date/time
strings are not truncated on assignment.)
DRL0077E An invalid character c is found after text, System action: The log collector stops processing the
c1 or c2 are valid values. current statement and continues with the next.
Explanation: The input text contains the invalid User response: Ensure that the column can
character c after the text text. Only the c1 or c2 accommodate the converted date/time value.
characters are allowed.
System action: The log collector stops processing the DRL0090E The function FIELD cannot be applied
current statement and continues with the next. to field field.
User response: Correct the character. Refer to the Explanation: The FIELD function can only be applied
Language Guide and Reference for a description of the to a field that might have multiple occurrences within a
valid characters. record. Its purpose is to select a specific occurrence of
the field. The field field is not contained in a repeated
section and cannot have multiple occurrences.
DRL0080E The value specified for name is not of
type type. System action: The log collector stops processing the
current statement and continues with the next.
Explanation: The name is a language keyword such as
OFFSET or LENGTH. The expression following this User response: Check that you specify the correct
keyword must specify the value type type, but the field, and that the repeated sections in the record are
actual expression specifies a value of another type. properly defined.
System action: The log collector stops processing the
current statement and continues with the next. DRL0091E Incorrect number of indices is specified
for field field. The correct number is n.
User response: Ensure that the expression specifies a
value of the required type. For example, use a constant Explanation: The field field, specified as the first
of a different type, redefine a field to yield a correct argument of the FIELD function, is contained in n
data type, or apply a conversion function if suitable. levels of repeated sections; n indices are thus required
to identify a unique occurrence of the field. The
invocation of FIELD specifies a different number of
DRL0081E The value specified for column column
indices.
is incompatible with the column type.
System action: The log collector stops processing the
Explanation: An update definition specifies a value to
current statement and continues with the next.
be assigned to column. The value is of a type that
cannot be assigned to the column. Note that an integer User response: Specify the correct number of indices.
or a floating-point number can be assigned only to a Refer to Language Guide and Reference for more
column of the type integer, small integer, floating-point, information on references to fields in repeated sections.
or decimal. A character string can be assigned only to a
column of the type character string, graphic string,
DRL0095E The lookup condition has too many
date, time, or timestamp. A date/time value can be
terms. The maximum number is 15.
assigned only to a column of the same type or to a
column of the character string type. Explanation: A lookup expression specifies a condition
that consists of more than 15 terms connected with
System action: The log collector stops processing the
AND operators.
current statement and continues with the next.

Chapter 1. Host Messages 11

DRL0100E • DRL0122E

System action: The log collector stops processing the

DRL0106E The name condition for the log log is
current statement and continues with the next.
invalid.
User response: Simplify the condition, or modify the
Explanation: One of these conditions is not valid:
lookup process, for example by restructuring the
lookup table. v The FIRST RECORD or LAST RECORD condition for
log.
v The WHERE condition specified on the COLLECT
DRL0100E The log log already exists.
statement for log
Explanation: The log name specified in the DEFINE
System action: The log collector stops processing the
LOG statement is the name of an existing log.
current statement and continues with the next.
System action: The log collector stops processing the
User response: Refer to Language Guide and Reference
current statement and continues with the next.
for information about valid conditions for DEFINE
User response: If you intend to define a new log, use LOG or COLLECT. Ensure that the correct condition is
another name. If you intend to replace the log log, drop specified.
the log before defining it again.
DRL0107E The name of the log must not exceed 16
DRL0101E The log log does not exist. bytes.

Explanation: The log is specified in a statement, but it Explanation: The maximum length of a log name is 16
does not exist. bytes. The length includes any shift-out and shift-in
characters that enclose sequences of double-byte
System action: The log collector stops processing the characters.
current statement and continues with the next.
System action: The log collector stops processing the
User response: Correct the statement or define the log. current statement and continues with the next.
User response: Specify a name that is not longer than
DRL0102I The log log is defined. 16 characters.
Explanation: The log has been defined successfully.
System action: Processing continues. DRL0108W No records were processed from
ddname .
User response: None.
Explanation: The log collector did not process any
records from the input file specified.
DRL0103I The log is altered.
System action: Normal processing continues.
Explanation: The log log has been altered successfully.
User response: Check that the input file contains IMS
System action: Processing continues. records that are to be processed. If it does not contain
User response: None. these records, no records will be processed. If it does
contain these records, check for other messages that
may indicate that an error has occurred.
DRL0104I The log log is dropped.
Explanation: The log has been dropped successfully. DRL0121E The record record already exists.
System action: Processing continues. Explanation: The DEFINE RECORD statement
User response: None. specified a record that already exists.
System action: The log collector stops processing the
DRL0105I The comment is stored for the log log. current statement and continues with the next.

Explanation: COMMENT ON LOG was successful for User response: Either specify a different record name
log. or drop the existing record definition.

System action: Processing continues.

DRL0122E The record record does not exist.
User response: None.
Explanation: The record record is specified in a
statement, but it does not exist.
System action: The log collector stops processing the
current statement and continues with the next.
User response: Correct the error.

12 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0123E • DRL0135E

System action: The log collector stops processing the

DRL0123E The record record does not contain the
current statement and continues with the next.
field field.
User response: Specify a name that does not start and
Explanation: The field field of the record record is
end with an asterisk.
specified in a statement, but it does not exist.
System action: The log collector stops processing the
DRL0130I The comment is stored for the record
current statement and continues with the next.
record.
User response: Correct the error.
Explanation: COMMENT ON RECORD was
successful for record.
DRL0124E No records are defined for this log.
System action: Processing continues.
Explanation: No records are defined for this log.
User response: None.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0131I The comment is stored for the field field
User response: Either define the records or, if the in record record.
incorrect log is specified, correct the log name.
Explanation: COMMENT ON FIELD was successful
on field in record.
DRL0125I The record record is defined.
System action: Processing continues.
Explanation: DEFINE RECORD was successful for
User response: None.
record.
System action: Processing continues.
DRL0132E There is no update or record procedure
User response: None. defined for any record in this log. The
log cannot be processed.
DRL0126I The record record is altered. Explanation: Records are defined for the log to be
collected, but no processing is defined for them. The
Explanation: ALTER RECORD was successful for
processing of a record might be defined in two ways:
record.
v By specifying the record as the source of an update
System action: Processing continues. definition
User response: None. v By specifying the record as input to a record
procedure
DRL0127I The record record is dropped. No record in the log is used in this way.
Explanation: DROP was successful for record. System action: The log collector stops processing the
current statement and continues with the next.
System action: Processing continues.
User response: Ensure that some processing is defined
User response: None. for at least one record in the log.

DRL0128E All records in this log are defined DRL0133E An error is found in the definition of
without fields. The log cannot be record record.
processed.
Explanation: This message identifies a record in error.
Explanation: No record definitions containing fields A previous message identifies the error.
exist for this log.
System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next.
User response: Correct the error.
User response: Perform DEFINE RECORD for the
required records.
DRL0135E The record record does not contain a
section section.
DRL0129E A record name must not both start and
end with an asterisk (*). Explanation: The section section specified for record
does not exist.
Explanation: A record name cannot both start and end
with an asterisk (*). System action: The log collector stops processing the
current statement and continues with the next.

Chapter 1. Host Messages 13

DRL0136W • DRL0142E

User response: Redefine the record or correct the

DRL0139E The section section is already defined.
section name.
Explanation: The message is issued in one of these
situations:
DRL0136W Split SMF type type record cannot be
collected due to invalid record sequence. v A DEFINE RECORD statement specifies section as the
name of two different sections.
Explanation: Split SMF records of type type must
v An ALTER RECORD statement attempts to add a
directly follow the initial record to be collected
section section to a record that already has a section
successfully.
with that name.
System action: The log collector ignores the split SMF
System action: The log collector stops processing the
records and continues with the next record.
current statement and continues with the next.
User response: None.
User response: Ensure that all sections within a record
have different names.
DRL0137E The section section in record record is not
repeated.
DRL0140E Too many fields are specified for the
Explanation: This message is issued in one of these record or the log header.
situations:
Explanation: A maximum of 2000 fields can be
v A DEFINE UPDATE or ALTER UPDATE statement specified in a record or a log header.
specifies an update FROM record SECTION section.
System action: The log collector stops processing the
v A COLLECT statement encountered an update
current statement and continues with the next.
FROM record SECTION section.
v A LIST RECORD statement specifies RECORD record User response: Correct the error.
SECTION section.
In each case, the SECTION clause indicates that the DRL0141E Too many sections are specified for the
requested operation (update or listing) is to be repeated record.
once for each occurrence of section section. This can be Explanation: A maximum of 300 sections can be
specified only for a repeated section section. specified in a record.
System action: The log collector stops processing the System action: The log collector stops processing the
current statement and continues with the next. current statement and continues with the next.
User response: Refer to Language Guide and Reference User response: Correct the error.
for an explanation of how repeated sections are
processed. Decide which repeated section you want to
process (if any). Note that the choice of the section DRL0142E The field field is already defined.
determines which fields you can access. Explanation: The message is issued in one of these
situations:
DRL0138E The section section is not previously v A DEFINE RECORD statement specifies field as the
defined in the record record. name of two different fields in the record.
Explanation: This message is issued in one of these v A DEFINE LOG statement specifies field as the name
situations: of two different fields in the log header.
v A DEFINE RECORD statement for the record record v An ALTER RECORD statement attempts to add the
defines a section IN SECTION section. The section field field to a record that already has a field with
section must be defined earlier in the same statement. that name.
v An ALTER RECORD statement for the record record v An ALTER LOG statement attempts to add the field
defines fields IN SECTION section or a section IN field to a log header that already has a field with
SECTION section. The record must already have the that name.
section section. System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next. User response: Ensure that all fields within a record
User response: For DEFINE RECORD, ensure that the or a log header have different names.
section is defined earlier in the same statement. For
ALTER RECORD, ensure that the record already has
the section.

14 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0143E • DRL0153I

DRL0143E The precision or scale for the field field DRL0150E The IDENTIFIED BY condition for the
is invalid. record record is invalid.
Explanation: The format of the field field is specified Explanation: The condition specified as the
as DECIMAL(p,s) or ZONED(p,s), where p is the IDENTIFIED BY condition is not valid. This error
precision and s is the scale. The allowed values for message is preceded by one or more error messages
precision are 1 through 31, and the allowed values for identifying the error(s).
scale are 0 through p.
System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next.
User response: Correct the error.
User response: Correct the field format specification.
DRL0151E An invalid condition or expression is
DRL0145E The number of bits in a BIT format specified for section section of record
must be a multiple of 8. record.
Explanation: The number of bits is not a multiple of 8. Explanation: One of these items is not valid:
System action: The log collector stops processing the v The condition specified as the PRESENT IF condition
current statement and continues with the next. for the section
v The expression specified as the offset, length, or
User response: Correct the error.
number of occurrences of the section
This message is preceded by one of more messages
DRL0147E The record record is the source of the
identifying the error(s) and the condition or expression
update update.
in error.
Explanation: The definition of the record record
System action: The log collector stops processing the
contains an error that has been identified by one or
current statement and continues with the next.
more error messages. This message follows the error
message(s) for record and explains why an error in the User response: Correct the error.
record prevents the execution of a COLLECT statement:
The record record is the source of the update update,
DRL0152E The length of section section of record
and the target of the update is one of the tables
record is undefined: neither LENGTH
specified in the INCLUDE clause of the statement.
nor any named fields are specified.
System action: Processing of the statement is
Explanation: If the length of a section is not specified
terminated and the log collector continues with the
explicitly by means of a LENGTH clause, it is
next.
determined by the fields contained in that section. It is
User response: Correct the definition of the record then defined to be the minimum length that
record, or remove the table from the INCLUDE clause. accommodates all named fields. If no named fields are
defined for the section, the length cannot be
determined.
DRL0148E The record record is used as input to
record procedure procedure. System action: The log collector stops processing the
current statement and continues with the next.
Explanation: The definition of the record record
contains an error that has been identified by one or User response: Ensure that the length is specified in
more error messages. This message follows the error one of the two ways. If you must define a section that
message(s) for the record record and explains why an extends to the end of the containing record or section,
error in the record prevents execution of the current specify a large length by means of a LENGTH clause.
statement: The record record is used as input to the Refer to Language Guide and Reference for exact rules
record record procedure, which is required for the about specifying length.
execution of the statement.
System action: The log collector stops processing the DRL0153I The section subsection of record record is
current statement and continues with the next. a section within section section, which
has no LENGTH defined. The section
User response: Correct the definition of the record
section will have its length defined by
record.
the length of its fields.
Explanation: This information message reminds the
user that, in the absence of an explicit length
specification for the section section, the length of the

Chapter 1. Host Messages 15

DRL0154I • DRL0168E

section will be determined by the named fields of the current statement and continues with the next.
section section, and not by the length of the subsection
User response: Ensure that the name load module
subsection. The length will be defined as the minimum
containing the procedure is present in an accessible
length that accommodates all named fields of section,
load library.
and might be insufficient to accommodate the
subsection.
DRL0163I The comment is stored for record
System action: Processing continues.
procedure procedure.
User response: Add a LENGTH clause for the section
Explanation: COMMENT ON RECORDPROC was
section, or ensure that the total length of the fields of
successful for the name procedure.
the containing section is at least equal to the length of
the subsection. System action: Processing continues.
User response: None.
DRL0154I The section section of record record has
no OFFSET specified. Offset 0 is
assumed. DRL0164E The record procedure procedure already
exists.
Explanation: If the offset of a section is not specified
explicitly by means of an OFFSET clause, the section is Explanation: The procedure record procedure, specified
assumed to start immediately after the end of a in DEFINE RECORDPROC already exists.
preceding section, identified according to the rules System action: The log collector stops processing the
stated in Language Guide and Reference. If the preceding current statement and continues with the next.
section does not exist, the section is assumed to start at
offset 0. This information message tells the user that User response: Correct the error.
this last alternative was applied for the section section.
System action: Processing continues. DRL0165I The record procedure procedure is
defined.
User response: Refer to Language Guide and Reference
for exact rules about specifying length. Specify OFFSET Explanation: DEFINE RECORDPROC was successful
if offset 0 is not what you intended. for record procedure procedure.
System action: Processing continues.
DRL0155E The section section of record record is User response: None.
specified to be a subsection of itself.
Explanation: The section section specifies IN SECTION DRL0166I The record procedure procedure is
section, which means that section is a subsection of itself. dropped.
This is not possible.
Explanation: DROP RECORDPROC was successful for
System action: The log collector stops processing the record procedure procedure.
current statement and continues with the next.
System action: Processing continues.
User response: Change the SECTION name or the IN
SECTION name. User response: None.

DRL0161E The record procedure procedure does not DRL0167I The record procedure procedure is
exist. altered.

Explanation: The procedure record procedure is Explanation: ALTER RECORDPROC was successful
specified in a statement, but it is not defined to the log for record procedure procedure.
collector. System action: Processing continues.
System action: The log collector stops processing the User response: None.
current statement and continues with the next.
User response: Ensure that the procedure is defined. DRL0168E The record procedure procedure is
involved in a circular process.
DRL0162E The log procedure procedure could not be Explanation: The procedure record procedure is defined
loaded. so that its input is derived, directly or indirectly, from
Explanation: The log procedure procedure is required its own output. For example, procedure is a procedure
for the log to be processed, but it can not be loaded. for record REC1 built by a procedure PROC2 for a
record REC2 built by the procedure procedure. Such a
System action: The log collector stops processing the circular process is not allowed.

16 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0171E • DRL0185I

System action: The log collector stops processing the User response: None.
current statement and continues with the next.
User response: Check the definitions of the records DRL0182I Product de-registration successful.
built by the record procedure procedure, the record
Explanation: This message is issued at termination
procedures for these records, and so on. Modify them
when the customization for product registration was
so that the process is not circular.
completed. See message DRL0181I for more
information.
DRL0171E The record procedure procedure could not
System action: Processing continues.
be loaded.
User response: None.
Explanation: The record procedure procedure is
required for the specified processing, but it can not be
loaded. DRL0183I Product registration failed rc=nn
System action: The log collector stops processing the Explanation: An attempt was made to perform
current statement and continues with the next. product registration, but this was not successful. The
return code gives an indication of the problem
User response: Ensure that the load module name
encountered. See SA38-0698-00 MVS Programming:
containing the procedure is present in an accessible
Product Registration, Register Service (IFAEDREG) Return
load library.
for more information.
System action: Processing continues.
DRL0172E The record record specified for record
procedure procedure does not exist. User response: If the error can be corrected from the
error description then correct the problem. Otherwise
Explanation: The DEFINE RECORDPROC statement
contact your IBM support for assistance.
for record procedure procedure specifies the record
record in its FOR clause, but the record is not defined.
DRL0184I Product de-registration failed rc=nn
System action: The log collector stops processing the
current statement and continues with the next. Explanation: An attempt was made to perform
product de-registration, but this was not successful. The
User response: Correct the error.
return code gives an indication of the problem
encountered. See SA38-0698-00 MVS Programming:
DRL0174I Record number n is the last log record Product Registration, Register Service (IFAEDREG) Return
processed. for more information.
Explanation: This message is issued after a record System action: Processing continues.
procedure is terminated by an error.
User response: If the error can be corrected from the
System action: Processing continues. error description then correct the problem. Otherwise
contact your IBM support for assistance.
User response: None.

DRL0185I No product registration performed.

DRL0176E The CSTACK variable is invalid.
Explanation: This message is issued at initialization
Explanation: The CSTACK variable specifies the size
when product registration is not attempted. Product
of the stack to be used for exit procedures written in C
registration is not attempted when the customization
language. As described in Language Guide and Reference,
for product registration has not been completed.
the value of the variable must be a sequence of digits,
optionally followed by the letter K. System action: Processing continues.
System action: The log collector stops processing the User response: If you have installed Tivoli Decision
current statement and continues with the next. Support for z/OS as part of the Capacity Management
Analytics (CMA) bundle then you need to complete the
User response: Correct the CSTACK variable.
product registration task for Tivoli Decision Support for
z/OS. If your install is not part of a CMA bundle, then
DRL0181I Product registration for product-id no action is required.
successful.
Explanation: This message is issued at initialization
when the customization for product registration was
completed. See DRLJCCMA in SDRLCNTL for details.
System action: Processing continues.

Chapter 1. Host Messages 17

DRL0200E • DRL0214E

DRL0200E The update update already exists. DRL0210E The update does not specify the value
of any column.
Explanation: The update can not be defined because
an update with the same name already exists. Each Explanation: The update being defined does not have
update name must be unique. any of the clauses: GROUP BY, SET, or MERGE that
define the contents of the target table.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Change the update name or drop the
old update definition. User response: Ensure that the update contains at
least one of these clauses: GROUP BY, SET, MERGE.
DRL0201I The update update is defined.
DRL0211E The WHERE condition in update update
Explanation: The update is successfully defined.
is invalid.
System action: Processing continues.
Explanation: The condition specified in the WHERE
User response: None. clause of update is not valid. This message is preceded
by one or more messages identifying the error(s).

DRL0202I The update update is dropped. System action: The log collector stops processing the
current statement and continues with the next.
Explanation: The update is successfully dropped.
User response: Correct the error.
System action: Processing continues.
User response: None. DRL0212E The section section specified in update
update does not exist.
DRL0203I The update update is altered. Explanation: The update is specified to be FROM
Explanation: The update is successfully altered. SECTION section of a record. The section existed when
the update was defined. However, the record must
System action: Processing continues. have been redefined afterwards, because it no longer
User response: None. contains the section section.
System action: The log collector stops processing the
DRL0204E The update update does not exist. current statement and continues with the next.

Explanation: The operation failed because the User response: Correct the update definition or add
specified update does not exist. the section to the record definition.

System action: The log collector stops processing the

current statement and continues with the next. DRL0213E The column column, specified as
argument number 2 of AVG or
User response: Correct the error. PERCENTILE, is not defined by means
of COUNT or SUM.
DRL0205I The comment is stored for update Explanation: Argument number 2 of the accumulation
update. functions AVG and PERCENTILE must be a column
Explanation: COMMENT ON UPDATE was successful with a value defined in the same update by means of
on update. the accumulation function COUNT or SUM.

System action: Processing continues. System action: The log collector stops processing the
current statement and continues with the next.
User response: None.
User response: Correct the AVG or PERCENTILE to
specify another column or change the accumulation
DRL0206E The update update is not defined. function for column.
Explanation: DEFINE UPDATE failed. A previous
message explains the reason. DRL0214E The column column is defined by
MERGE and cannot be changed to SET
System action: The log collector stops processing the
or GROUP BY.
current statement and continues with the next.
Explanation: Columns specified in the MERGE clause
User response: Correct the error.
of a DEFINE UPDATE statement cannot be changed to

18 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0215E • DRL0222W

a SET or GROUP BY column in an ALTER UPDATE in the same way by all definitions: Either the column
statement. must be a GROUP BY column in all definitions, or all
definitions must specify the value of the column using
System action: The log collector stops processing the
the same accumulation function. A subsequent message
current statement and continues with the next.
(DRL0331E) identifies an update that does not follow
User response: If the column must be changed, drop this rule.
and redefine the update.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0215E The value of column column is specified
User response: Correct the accumulation function for
more than once.
column.
Explanation: A column can be specified only once in
an update definition.
DRL0220E Different update definitions for the
System action: The log collector stops processing the table table have different GROUP BY
current statement and continues with the next. columns.

User response: Ensure that you specified the correct Explanation: If different update definitions specify the
column name. contents of the same table, their GROUP BY columns
must be the same. A subsequent message (DRL0331E)
identifies an update that does not follow this rule.
DRL0216E Argument number 3 of PERCENTILE is
not in the range 1–99. System action: The log collector stops processing the
current statement and continues with the next.
Explanation: Argument number 3 of the accumulation
function PERCENTILE must be an integer constant in User response: Make the GROUP BY clauses of all
the range 1–99. updates TO the table table identical.

System action: The log collector stops processing the

current statement and continues with the next. DRL0221W The GROUP BY columns cannot be
checked against primary key because
User response: Change the integer value. table table is not found in the view view.
Explanation: If a primary key is defined for the target
DRL0217E The field field in DISTRIBUTE is not table of an update, the columns specified in the
numeric. GROUP BY clause of the update must be identical to
Explanation: All fields or columns to be distributed the primary key columns. (Otherwise, a COLLECT
must be numeric. using the update will probably result in an SQL error.)
To verify that the above condition is met, the log
System action: The log collector stops processing the collector uses the information contained in the view
current statement and continues with the next. view. However, the view did not contain information
User response: Correct the DISTRIBUTE clause. about the table table, so the check can not be made.
System action: Processing continues.
DRL0218E In the expression for column column, the User response: Consider redefining the view so that it
argument number 1 of function is not will contain information about the table table.
numeric. Alternatively, perform the check yourself: If the table
Explanation: Argument number 1 of function (SUM, table has primary key columns, verify that the GROUP
AVG, or PERCENTILE) must be numeric (that is, of the BY clause specifies exactly these columns.
integer or floating-point type). The error was found in
the clause specifying the value of column column. DRL0222W The GROUP BY columns cannot be
System action: The log collector stops processing the checked against primary key because
current statement and continues with the next. the view view cannot be read.

User response: Change the expression used in the Explanation: If a primary key is defined for the target
specification of column column. table of an update, the columns specified in the
GROUP BY clause of the update must be identical to
the primary key columns. (Otherwise, a COLLECT
DRL0219E Different update definitions for the using the update will probably result in an SQL error.)
table table specify the value of column To verify that the above condition is met, the log
column in different ways. collector uses the information contained in the view
Explanation: If different update definitions specify the view. However, the view can not be read.
value of the same column, the value must be specified System action: Processing continues.

Chapter 1. Host Messages 19

DRL0223W • DRL0231E

User response: Ensure that the view is defined and User response: Correct the parameter to specify source
contains information about the table. Alternatively, fields or columns.
perform the check yourself: If the table has primary key
columns, verify that the GROUP BY clause specifies
DRL0227E The value of column has an incorrect
exactly these columns.
length.
Explanation: The value of the expression assigned to
DRL0223W The GROUP BY columns do not match
column is of an incorrect length. For example, in an
primary key columns.
update definition’s MERGE clause, the value of the
Explanation: The columns specified in the GROUP BY expression specified for the interval type column must
clause of the update definition are not identical to the have a length of 3.
primary key columns of the target table. A COLLECT
System action: The log collector stops processing the
will probably result in an SQL error.
current statement and continues with the next.
System action: Processing continues.
User response: Correct the expression assigned to the
User response: Correct the GROUP BY clause or column column.
redefine the target table.
DRL0228E The column column is not of type type.
DRL0224E The MERGE and SET clauses of an
Explanation: The assignment to column requires it to
update definition are mutually
be of type type, which it is not. For example, columns
exclusive.
assigned AVG values must be of the floating-point
Explanation: An ALTER UPDATE statement attempts type.
to add a MERGE clause to an update definition that
System action: The log collector stops processing the
has a SET clause, or a SET clause to an update
current statement and continues with the next.
definition that has a MERGE clause. However, an
update definition cannot have both. User response: Change the column name, column
type, or accumulation function.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0229E The field field in DISTRIBUTE is
User response: Remove the SET or the MERGE clause
specified more than once.
from the update definition before adding the other
clause. Explanation: Specify each field to be distributed only
once.
DRL0225E The name abc specified by keyword is System action: The log collector stops processing the
already used as the name of a field or current statement and continues with the next.
column of source.
User response: Change the definition so the field is
Explanation: The name abc introduced by keyword defined only once.
clause is identical to the name of a field (or column) of
the record (or table) source, which is the source of the
update. You cannot use the name for the specified DRL0230E The SECTION parameter cannot be
purpose because it causes ambiguity. used when the source of the update is a
table.
System action: The log collector stops processing the
current statement and continues with the next. Explanation: The SECTION parameter can be used
only to identify a section of a record definition.
User response: Change the parameter.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0226E The name identifier specified in keyword
clause is not a field or column of source. User response: Correct the error.

Explanation: The name identifier specified in the

keyword clause is expected to be the name of a field (or DRL0231E The value of the column column of table
column) in the record (or table) source name, which is table is specified by more than one
the source of the update. The record (or table) does not update using the accumulation function
contain a field (or column) with this name. PERCENTILE.

System action: The log collector stops processing the Explanation: If the value of a column is specified by
current statement and continues with the next. means of the accumulation function PERCENTILE, the
value can be specified in only one update definition.
System action: The log collector stops processing the

20 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0232E • DRL0245W

current statement and continues with the next.

DRL0241E The table table does not exist.
User response: Remove the assignment to the column
Explanation: The operation failed because the
from all update definitions but one.
specified table table does not exist.
System action: The log collector stops processing the
DRL0232E The accumulation function
current statement and continues with the next.
PERCENTILE cannot be used when the
source of the update is a table. User response: Correct the error.
Explanation: The accumulation function PERCENTILE
can only be used in an update where the source is a DRL0242E The table table1 does not contain the
record. column column2.
System action: The log collector stops processing the Explanation: The column column2 of table table1 is
current statement and continues with the next. specified in a statement, but it does not exist.
User response: Consider an alternative way of System action: The log collector stops processing the
computing the information you need, for example, current statement and continues with the next.
counting values that exceed a certain threshold.
User response: Change the update definition or
change and recreate the table.
DRL0233E The argument number n of APPLY
SCHEDULE is of incorrect type.
DRL0243E The control table table does not exist.
Explanation: The correct type for argument 1 (interval
Explanation: The functions DAYTYPE, PERIOD, or
type) is character string. The correct type for argument
APPLY SCHEDULE can not be performed because the
2 (interval start) and argument 3 (interval end) is
control table table is missing.
timestamp.
System action: The log collector stops processing the
System action: The log collector stops processing the
current statement and continues with the next.
current statement and continues with the next.
User response: Contact the Tivoli Decision Support for
User response: Ensure that the argument is of the
z/OS administrator. Refer to Language Guide and
required type. For example, use a different type of
Reference for an explanation.
constant, redefine a field to yield a correct data type, or
apply a conversion function if suitable.
DRL0244E The column column of control table table
is missing or has an incorrect type.
DRL0234E The column column cannot be used as a
grouping column. Explanation: The functions DAYTYPE, PERIOD, or
APPLY SCHEDULE can not be performed because the
Explanation: A GROUP BY clause of an update
column column in control table table either is not
definition specifies that the column column must hold a
present or has an incorrect type.
grouping value. The column is either a decimal
column, or a long string column. System action: The log collector stops processing the
current statement and continues with the next.
System action: The log collector stops processing the
current statement and continues with the next. User response: Contact the Tivoli Decision Support for
z/OS administrator. Refer to Language Guide and
User response: Redefine the column or specify
Reference for an explanation.
another column.

DRL0245W The length of string column column in

DRL0235E There is a circular update involving
the table table exceeds the length
tables table list.
supported by the log collector.
Explanation: Each table in the table list is updated
Explanation: The maximum length of a CHARACTER
from itself via a cascaded update involving other tables
or VARCHAR column supported by the log collector is
in the table list. A table cannot be updated from itself.
254 bytes. The maximum length of a GRAPHIC or
System action: The log collector stops processing the VARGRAPHIC column supported by the log collector
current statement and continues with the next. is 126 double-byte characters.
User response: Check update definitions involving the System action: The processing continues, but the
tables listed in the table list. You may have an old following will happen if the log collector reads data
update definition that was not dropped. Correct the from the table:
error. v When the log collector reads a string of more than
254 bytes from a CHARACTER or VARCHAR

Chapter 1. Host Messages 21

DRL0246E • DRL0305I

column, it truncates the string to 254 bytes. This

DRL0301I operation ended at timestamp.
might result in damaging a sequence of double-byte
characters contained in the string. Explanation: The operation (COLLECT, LIST RECORD,
v When the log collector reads a string of more than LOGSTAT, or PURGE) completed processing at
126 double-byte characters from a GRAPHIC or timestamp.
VARGRAPHIC column, it truncates the string to 126 System action: Processing continues.
(double-byte) characters. It then adds the shift-out
and shift-in characters at the ends of the string, as User response: None.
for all graphic strings.
User response: Ensure that this warning message does DRL0302I Processing data set name on volume.
not indicate a problem that must be corrected. Explanation: This message identifies the log data set
being processed and the volume where it is located.
DRL0246E The table table is specified more than System action: Processing continues.
once in an INCLUDE or EXCLUDE
clause. User response: None.
Explanation: A table name can only appear once in
the same INCLUDE or EXCLUDE clause. DRL0303W The log data set has already been
processed.
System action: The log collector stops processing the
current statement and continues with the next. Explanation: The log data set has already been
collected. Tivoli Decision Support for z/OS uses the
User response: Correct the error. first 80 bytes of the first selected record to identify the
data set. The data set name is not used for
DRL0247E The EXCLUDE clause did not exclude identification.
any tables. System action: COLLECT continues if other input log
Explanation: None of the tables specified by the data sets are specified in the collect job. Debug
EXCLUDE clause is among the tables that would information will be displayed in DRLDUMP. The log
otherwise be selected for processing. record number being processed will be displayed as
well as the first 80 bytes of the record which caused the
System action: The log collector stops processing the message.
current statement and continues with the next.
User response: Ensure that this warning message does
User response: Check the EXCLUDE clause. If the not indicate any problem that needs to be corrected.
clause does not specify the tables you want to exclude,
correct it. If there are no tables to be excluded, remove
the clause. DRL0304W The log data set is being reprocessed.
Explanation: The log data set has already been
DRL0251E The SQL statement or condition is too collected but, because the REPROCESS parameter is
long. specified on the COLLECT statement, the log is
processed again.
Explanation: An SQL statement in the log collector
cannot be longer than 10000 characters. System action: COLLECT starts from the beginning of
the log.
System action: The log collector stops processing the
current statement and continues with the next. User response: Ensure that the warning message does
not indicate a problem that must be corrected.
User response: Correct the error.

DRL0305I The log data set has been partly

DRL0300I operation started at timestamp. processed.
Explanation: The operation (COLLECT, LIST RECORD, Explanation: The log data set has been partly
LOGSTAT, or PURGE) began processing at timestamp. collected; the previous COLLECT for this data set was
System action: Processing continues. terminated before the entire log was processed.

User response: None. System action: The first n records (as identified by
message DRL0306I) are skipped, and COLLECT
continues processing the remaining records in the log
data set.
User response: None.

22 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0306I • DRL0315I

User response: None.

DRL0306I The first n records are skipped.
Explanation: This is a continuation of message
DRL0312I A database update started after n
DRL0305I. Please see that message.
records due to volume switch.
System action: Processing continues.
Explanation: This message is issued when DRLLOG is
User response: None. a multi-volume data set. The end of a volume was
reached, and the log collector started a database update
before processing the next volume.
DRL0307E The value specified by the COMMIT
AFTER clause is not valid. System action: Processing continues.
Explanation: The COMMIT AFTER n RECORDS User response: None.
parameter specified an invalid value. For example, a
zero (0) is not allowed.
DRL0313I The collect buffer was filled n times.
System action: COLLECT terminates. Consider increasing the collect buffer
size.
User response: Correct the error.
Explanation: This message shows the number of times
the collect buffer was filled during processing of the
DRL0308I A database update started after n
log data set.
records due to a buffer-full condition, at
timestamp. System action: Processing continues with degraded
performance.
Explanation: The collect buffer was full and a
database update was started, at timestamp. User response: Increase the value specified for the
BUFFER SIZE parameter in the COLLECT statement.
System action: Processing continues.
The elapsed time for the collect increases significantly
User response: None. each time the collect buffer is filled. A larger buffer size
will reduce the number of times the collect buffer is
filled and decrease the total elapsed time for the collect
DRL0309I A database update started after n run.
records, at timestamp.
Explanation: COMMIT AFTER n RECORDS was DRL0314I Data set name: data-set-name.
specified on the COLLECT statement, and a multiple of
n records have been read, at timestamp. Explanation: This message provides the data set name
for an object referred to by the preceding message.
System action: Processing continues.
System action: Processing continues.
User response: None.
User response: Refer to the explanation for the
preceding message.
DRL0310I A database update started after n
records due to end of log, at timestamp.
DRL0315I Records read from the log or built by
Explanation: The end of the log data set has been log procedure:
reached, at timestamp.
| Explanation:
System action: Processing continues.
| This message is followed by a table showing the record
User response: None. | types in the log being processed, or, if the log
| procedure was used, the record types built by the log
DRL0311I A database update started after n | procedure. For each record type, the table shows the
records due to data set switch, at | number of records of that type that were actually found
timestamp. | and processed. The table also shows the number of
| unrecognized records, and the total number of records.
Explanation: This message is issued when DRLLOG | If ON TIMESTAMP OVERLAP SKIP was specified on
consists of several concatenated data sets. The end of a | the collect statement and records were skipped then a
data set was reached, at timestamp, and the log collector | count of skipped records is also shown in the table. The
started a database update before processing the next | table is built from messages DRL0317I through
concatenated data set. After the database update | DRL0322I. For an example of such a table, see Figure 1
completes, the statistics for the data set will be | on page 34.
presented, at timestamp.
System action: Processing continues.
System action: Processing continues.
User response: None.

Chapter 1. Host Messages 23

DRL0316I • DRL0334E

DRL0316I Records built by record procedures: DRL0329E ON TIMESTAMP OVERLAP

SKIP/STOP invalid. Log log-name does
Explanation: This message is followed by a table
not contain a TIMESTAMP expression
showing the record types built by record procedures.
parameter.
For each record type, the table shows the number of
records of that type that were found and processed. Explanation: ON TIMESTAMP OVERLAP SKIP and
The table also shows the number of unrecognized ON TIMESTAMP OVERLAP STOP can only be
records, and the total number of records. The table is specified on the COLLECT statement if the log being
built from messages DRL0317I through DRL0321I. For collected was defined with a TIMESTAMP expression.
an example of such a table, see Figure 1 on page 34.
System action: The log collector stops processing the
System action: Processing continues. current statement and continues with the next.
User response: None. User response: Correct the COLLECT statement or
add a TIMESTAMP expression to the log being
collected.
DRL0317I DRL0318I DRL0319I DRL0320I DRL0321I
DRL0322I
DRL0330E The collect initialization failed.
Explanation: Messages DRL0317I through DRL0322I
are used to build the table that follows the messages Explanation: This message follows other message(s)
DRL0315I and DRL0316I. See the explanation for these explaining the cause of the failure.
messages. For an example, see Figure 1 on page 34.
System action: The log collector stops processing the
System action: Processing continues. current statement and continues with the next.
User response: None. User response: Correct the error.

DRL0323I DRL0324I DRL0325I DRL0326I DRL0327I DRL0331E An error was found in update update.
Explanation: Messages DRL0323I through DRL0327I Explanation: This message identifies an update in
are used to build a table that shows the number of error. A previous message identifies the cause of the
rows inserted and updated in the collect buffer and in error.
the database tables. For an example, see Figure 1 on
System action: The log collector stops processing the
page 34.
current statement and continues with the next.
For more information on how to interpret collect
User response: Correct the error.
messages, refer to the Administration Guide and
Language Guide and Reference.
DRL0333I The record record has no fields and is
System action: Processing continues.
not used.
User response: None.
Explanation: The record is excluded.
System action: Processing continues; COLLECT and
DRL0328W The log data set is being skip processed.
LOGSTAT operations continue their execution.
Explanation: ON TIMESTAMP OVERLAP SKIP was
User response: ALTER the record or DROP and
specified on the COLLECT statement and the log
redefine it.
collector has found that the data set name of the log
being processed matches a previously collected log and
the first identified record in the log has a timestamp DRL0334E ON TIMESTAMP OVERLAP STOP was
that is prior to the specified and log contains records with
DRLLOGDATASETS.LAST_TIMESTAMP value for the timestamp data overlapping a
previously collected log. previously collected log.
System action: Skip processing is activated. The log Explanation: ON TIMESTAMP OVERLAP STOP was
collector skips records within the the range indicated specified on the COLLECT statement and the log
by the FIRST_TIMESTAMP and LAST_TIMESTAMP collector has found that the data set name of the log
entries for the log in the DRLLOGDATASETS system being processed matches a previously collected log and
table. the first identified record in the log has a timestamp
that is prior to the
User response: Determine why the duplicate log was
DRLLOGDATASETS.LAST_TIMESTAMP value for the
produced. Even if skip processing has allowed valid
previously collected log.
data to be collected reprocessing the data in this way
impacts on system resource. System action: The log collector stops processing the
current statement and continues with the next.

24 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0335E • DRL0341I

User response: Determine why the duplicate log was information was lost. Consider redefining the update to
produced and take appropriate actions to resume prevent this kind of problem. (The source records can
normal processing. it. be examined using the DISPLAY function of the
administration dialog. The source rows can be
examined using QMF.)
DRL0335E The processing terminated due to an
error found by log or record procedure
procedure. DRL0338W The section section of record record was
skipped n time(s) due to error in offset,
Explanation: The log or record procedure procedure
length, or number.
returned with a request for termination of the
processing of the log. Explanation: One or more occurrences of section
section of record cannot be located because the offset,
System action: The log collector stops processing the
length, or number attribute of the section cannot be
current statement and continues with the next.
evaluated. The number n is the number of unsuccessful
User response: Correct the error. attempts to locate an occurrence of the section, and
might be larger than the actual number of skipped
occurrences (for example, when several updates tried to
DRL0336W n records or rows were skipped in locate the same occurrence).
update update of table table due to a null
GROUP BY value. System action: Processing continues.

Explanation: A source record or row is skipped if any User response: None.

of the grouping values for that row is null. A grouping
value is that specified by the expression to the right of
DRL0339E Processing terminated due to invalid
an equal sign in the GROUP BY clause. It might be null
return code return code returned by log
because the data in the source record or row that are
or record procedure procedure.
used to compute the value are missing, or invalid, or
result in a computation error. Explanation: The log or record procedure procedure
returned with an invalid return code, which caused the
System action: Processing continues.
processing of the log to stop.
User response: The DRLDUMP file contains
System action: The log collector stops processing the
information that identifies the skipped records or rows.
current statement and continues with the next.
Examine these records or rows to see if the content was
indeed invalid, and if not, what information was lost. User response: Correct the error.
Consider redefining the update to prevent this kind of
problem. (The source records can be examined using
DRL0340W The name condition for the log is not
the DISPLAY function of the administration dialog. The
satisfied.
source rows can be examined using QMF™.)
Explanation: The name condition (FIRST RECORD or
LAST RECORD), as coded in the DEFINE LOG
DRL0337W For n records or rows in an update of
statement, was not met when applied to the first or last
table table, one or more values were set
record read from the log.
to null because of error.
System action: Processing continues.
Explanation: The following has happened for n source
records or rows: A value (one or more) obtained from User response: Ensure that the warning message does
the row was to be used in the update, for example as not indicate a problem that must be corrected.
the argument of an accumulation function (but not as a
grouping value). The value can not be evaluated
because the data in the record or row is invalid or DRL0341I The first-record timestamp is timestamp.
resulted in a computation error; a null value was used Explanation: A TIMESTAMP clause is specified in the
instead in the update. log definition. The timestamp for the first record from
(Notice that the message does not signal the null values the log data set is timestamp.
that result from missing data. Such a null value is not System action: Processing continues.
considered an error.)
User response: None.
System action: Processing continues.
User response: The DRLDUMP file contains
information that identifies the first source record of
each type (or the first row of each source table)
included in the count. Examine these records or rows to
see if the content was indeed invalid, and if not, what

Chapter 1. Host Messages 25

DRL0342I • DRL0349W

System action: Processing continues.

DRL0342I The last-record timestamp is timestamp.
User response: The DRLDUMP data set contains
Explanation: A TIMESTAMP clause is specified in the
information that identifies the record or row that
log definition. The timestamp for the last record from
caused the error. Check the DISTRIBUTE clause against
the log data set is timestamp.
the contents of the record or row and correct the cause
System action: Processing continues. of the error. (The source records can be examined using
the DISPLAY function of the administration dialog. The
User response: None.
source rows can be examined using QMF.)

DRL0343I The first-record timestamp is invalid.

DRL0347W n records or rows were skipped in
Explanation: A TIMESTAMP clause is specified in the update update, table table due to invalid
log definition. The timestamp for the first record arguments of MERGE.
selected from the log data set cannot be evaluated
Explanation: A source record or a row of a source
because of absent or invalid data, or because of a
table is skipped if one or more arguments of MERGE
calculation error.
are invalid, for example:
System action: Processing continues. v The argument cannot be evaluated because of
User response: Check the data in the log data set and missing data, invalid data, or computation errors.
make sure it is valid. Check the TIMESTAMP v The interval type code (argument 1) is not one of the
expression in the log definition, and correct it if allowed interval type codes.
necessary. v The interval start time (argument 2) is later than the
interval end time (argument 3).
DRL0344I The last-record timestamp is invalid. v The quiet interval (argument 4) is negative.
Explanation: A TIMESTAMP clause is specified in the System action: Processing continues.
log definition. The timestamp for the last record
User response: The DRLDUMP data set contains
selected from the log data set cannot be evaluated
information that identifies the record or row that
because of absent or invalid data, or because of a
caused the error. Check the MERGE clause against the
calculation error.
contents of the record or row and correct the cause of
System action: Processing continues. the error. (The source records can be examined using
the DISPLAY function of the administration dialog. The
User response: Check the data in the log data set and source rows can be examined using QMF.)
make sure it is valid. Check the TIMESTAMP
expression in the log definition, and correct it if
necessary. DRL0348W COLLECT initialization resulted in no
tables selected for processing.

DRL0345E The specified buffer size is n. The Explanation: No tables were selected for COLLECT
minimum allowed value is nmin. processing.

Explanation: The minimum allowed buffer size on System action: The log collector stops processing the
COLLECT and LIST RECORD is nmin. current statement and continues with the next.

System action: The log collector stops processing the User response: Investigate the reason for failure of the
current statement and continues with the next. COLLECT statement to select tables for processing. Is
the EXCLUDE parameter present? If so, check its
User response: Specify a larger buffer size. content. Correct the error.

DRL0346W n records or rows were skipped in DRL0349W Data values in table table were changed
update update, table table due to invalid to null in n columns due to overflow.
arguments of DISTRIBUTE.
Explanation: An overflow is a situation during the
Explanation: A source record or row is skipped if one execution of a COLLECT, LIST RECORD, or
or more arguments of DISTRIBUTE are invalid, for RECALCULATE statement when the result of an
example: accumulation function exceeds the capacity of the
v The START, END, or BY expression cannot be column supposed to receive it. In the case of COLLECT
evaluated because of missing data, invalid data, or and RECALCULATE, the column is a column in the
computation errors. target table, and its capacity is determined by the SQL
v The START time is later than the END time. data type of the column. In the case of LIST RECORD,
the column is a part of the output list, and its capacity
v The BY value is not a multiple of 60.
is determined by the type of expression defining it.

26 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0350E • DRL0355E

According to the options defined for the statement, the modifying the argument of the accumulation function
processing was to continue in case of an overflow. to change the type of the result from integer to
Every time an overflow occurred, the current value of floating-point (if it is not already floating-point). If the
the accumulation function was discarded, the column statement is COLLECT or LIST RECORD, consider
was reset to null, and the accumulation continued specifying ON OVERFLOW CONTINUE.
starting from null. If the column appeared as argument
number 2 of an AVG or PERCENTILE function in the
DRL0351E The COLLECT processing is terminated
same update, the current value of that AVG or
by an overflow.
PERCENTILE was similarly discarded and reinitialized.
All discarded values were written to the DRLDUMP Explanation: An overflow is the situation when the
file, together with the identification of the column and result of an accumulation function becomes too large to
the currently processed record or row. be stored in the specified column.
The columns of the table table were reinitialized in this The COLLECT statement specified (explicitly or by
way n times during the execution of the statement. default) that the processing is to stop in case of
overflow. This message is preceded by message
System action: Processing continues.
DRL0350E that provides further details.
User response: Refer to the DRLDUMP file for exact
System action: The processing is stopped and the
information on what has happened. Check if the
database updates are rolled back to the most recent
overflow was caused by an incorrectly defined
commit point. The log collector continues with the next.
argument of the accumulation function. Examine the
source record or row to see if the overflow was caused User response: See explanation and user response for
by invalid data. If the statement is COLLECT, consider message DRL0350E.
redefining the target table to give the column a higher
capacity (integer instead of small integer, floating-point
instead of integer, and a higher precision for a decimal DRL0353E n records or rows were skipped in
column). If the statement is LIST RECORD, consider update update, table table due to invalid
modifying the argument of the accumulation function arguments of APPLY SCHEDULE.
to change the type of result from integer to Explanation: A source record or row is skipped if one
floating-point. (The RECALCULATE statement is or more arguments of APPLY SCHEDULE are invalid,
always terminated by an overflow, so that this message for example, the interval start time is later than the
can never be issued for it.) interval end time.
System action: Processing continues.
DRL0350E Overflow occurred in column column of
table table. User response: The DRLDUMP data set contains
information that identifies the record or row that
Explanation: The value of column column was to be caused the error. Check the APPLY SCHEDULE clause
computed by a COLLECT, LIST RECORD, or against the contents of the record or row and correct
RECALCULATE statement. The value of column column the cause of the error. (The source records can be
is specified by means of an accumulation function with examined using the DISPLAY function of the
a numeric result. The result exceeds the capacity of the administration dialog. The source rows can be
column. This situation is called an overflow. examined using QMF.)
In the case of COLLECT and RECALCULATE, the
column is a column in the target table, and its capacity DRL0355E No updates or valid records are defined
is determined by the SQL data type of the column. In for the tables in the INCLUDE list.
the case of LIST RECORD, the column is a part of the
output list, and its capacity is determined by the type Explanation: The COLLECT statement was not
of expression defining it. executed because no valid updates exist for the tables
specified in the INCLUDE clause, or the updates exist,
System action: The log collector stops processing the but their source records do not exist or are invalid.
current statement and continues with the next.
System action: The log collector stops processing the
User response: Check if the overflow was caused by current statement and continues with the next.
an incorrectly defined argument of the accumulation
function. Examine the source record or row to see if the User response: Ensure that the included tables have
overflow was caused by invalid data. Examine the data valid update and record definitions.
specified by RECALCULATE. If the statement is
COLLECT or RECALCULATE, consider redefining the
target table to give the column a higher capacity
(integer instead of small integer, floating-point instead
of integer, and a higher precision for a decimal
column). If the statement is LIST RECORD, consider

Chapter 1. Host Messages 27

DRL0356I • DRL0368E

current statement and continues with the next.

DRL0356I To update the database, the algorithm
algorithm was most used. User response: Correct the error.
Explanation: The algorithm algorithm was most used
to update the database. DRL0364E The list file ddname is used in a previous
list specification.
System action: Processing continues.
Explanation: Two list specifications specified the same
User response: If the COLLECT process uses the
output file. Each listed record type must be written to
DIRECT or SCAN algorithm to update the DB2
its own output file; they cannot be mixed.
database, you may want to manually specify that
algorithm in the COLLECT statement. This will prevent System action: The log collector stops processing the
Tivoli Decision Support for z/OS from running the current statement and continues with the next.
SQL query that determines which algorithm to use,
with the result that the process performance is User response: Correct the error.
improved. For details about the COLLECT parameters,
refer to the Language Guide and Reference. DRL0365E The number of columns to be listed
exceeds the allowed maximum.
DRL0358E REPROCESS and ON TIMESTAMP Explanation: No more than 120 columns can be listed
OVERLAP are mutually exclusive. at the same time. This maximum is decreased by 1 for
Explanation: REPROCESS and ON TIMESTAMP each AVG and PERCENTILE column.
OVERLAP STOP were both specified on the COLLECT System action: The log collector stops processing the
statement. These options are mutually exclusive and current statement and continues with the next.
cannot be specified on the same COLLECT statement.
User response: Correct the error. You can list the same
System action: The log collector stops processing the record type to another output file in the same
current statement and continues with the next. processing of the log.
User response: Correct the COLLECT statement and
rerun the collect job. DRL0366E The LIST RECORD statement requires a
GROUP BY clause.
DRL0361E To column number n, specified in Explanation: If the columns to be listed are specified
ORDER BY clause, does not exist. both with and without accumulation functions, a
Explanation: n is higher than the number of columns GROUP BY clause is required. The GROUP BY clause
to be listed. must then contain exactly those columns that have no
accumulation function.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.
User response: Correct the error.
User response: Correct the error.

DRL0362E The column column, specified in ORDER

BY clause, does not exist. DRL0367E The GROUP BY item number n is not a
column specification.
Explanation: column does not appear as the
specification of a column to be listed. Explanation: The item number n of the GROUP BY
clause is not present among the column specifications
System action: The log collector stops processing the in the FIELDS clause. Thus, no grouping can be done
current statement and continues with the next. on that column.
User response: Correct the error. Specify the column System action: The log collector stops processing the
number if the column specification is not a single field current statement and continues with the next.
name.
User response: Correct the error.

DRL0363E The record record does not belong to the

same log as the record in the previous DRL0368E The column specification number n is
list specification. not present in GROUP BY clause.

Explanation: If several record types are listed in the Explanation: The GROUP BY clause specifies that
same processing of the log, all record types must grouping may be done. Column number n is not
belong to the same log. specified to be a grouping column (it is not present in
the GROUP BY clause). The column has no
System action: The log collector stops processing the

28 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0369I • DRL0381I

accumulation function specified and cannot be

DRL0376E The record length exceeds the maximum
accumulated.
record length for the file file.
System action: The log collector stops processing the
Explanation: The record length exceeds the maximum
current statement and continues with the next.
record length for file.
User response: Add the column expression to the
System action: The log collector stops processing the
GROUP BY arguments or specify an accumulation
current statement and continues with the next.
function for the column.
User response: Correct the error.
DRL0369I The column number n is specified more
than once in ORDER BY. DRL0377W The LIST RECORD processing is
interrupted due to a buffer-full
Explanation: The ORDER BY clause contains the same
condition.
expression twice. This duplication has no effect on the
list processing. Explanation: The list output was buffered due to a
GROUP BY or ORDER BY clause in the list
System action: Processing continues.
specification. The buffer filled up before the input log
User response: None. processing was finished. The buffered rows were
written to the output file(s), and the processing was
ended.
DRL0370E An error was found in the WHERE
clause of the list specification of record System action: Processing continues for the rows read
record. before the buffer-full condition.

Explanation: Either the WHERE condition is not a User response: Rerun LIST RECORD with a larger
condition, or a previous message explains the cause of buffer.
the error.
System action: The log collector stops processing the DRL0378E The LIST RECORD processing is
current statement and continues with the next. terminated by an overflow.
User response: Correct the error. Explanation: An overflow is the situation when the
result of an accumulation function becomes too large to
be stored in the specified column.
DRL0371E An error was found during initialization
of LIST RECORD record. The LIST RECORD statement specified (explicitly or by
default) that the processing is to stop in case of
Explanation: This message indicates that an error was overflow. This message is preceded by message
found in the list specification for record. A previous DRL0350E that provides further details.
error message explains the cause of the error.
System action: The log collector stops processing the
System action: The log collector stops processing the current statement and continues with the next.
current statement and continues with the next.
User response: See explanation and user response for
User response: Correct the error. message DRL0350E.

DRL0372E Argument number n of the FIELDS DRL0380I n records read from the input log.
clause is not a valid expression.
Explanation: This message, issued at the end of a LIST
Explanation: The argument might be a condition. Or a RECORD operation, indicates the quantity of records
previous message identifies the cause. read from the input log.
System action: The log collector stops processing the System action: Processing continues.
current statement and continues with the next.
User response: None.
User response: Correct the error.

DRL0381I n records written to the file file.

DRL0375E FIELDS definition is not allowed.
Explanation: This message, issued at the end of a LIST
Explanation: The FIELDS clause is not allowed in the RECORD operation, indicates the quantity of records
section part of an ALTER RECORD statement. written to the named file.
System action: The log collector stops processing the System action: Processing continues.
current statement and continues with the next.
User response: None.
User response: Correct the error.

Chapter 1. Host Messages 29

DRL0401E • DRL0433W

DRL0401E An invalid SQL condition is specified DRL0409I The purge condition for table is dropped.
for table.
Explanation: DROP PURGE FROM was successful for
Explanation: The SQL condition specified in the table.
WHERE clause of DEFINE PURGE or RECALCULATE
System action: Processing continues.
for the table table is not valid.
User response: None.
System action: The log collector stops processing the
current statement and continues with the next.
DRL0410I The purge condition for table is altered.
User response: Correct the error.
Explanation: DEFINE PURGE was successful for table.
DRL0402E The SQL condition exceeds 254 System action: Processing continues.
characters.
User response: None.
Explanation: The SQL condition specified in the
WHERE clause of DEFINE PURGE or RECALCULATE
for the table cannot exceed 254 characters. DRL0411E Purging data from table with the purge
condition condition failed.
System action: The log collector stops processing the
current statement and continues with the next. Explanation: Check the output for an SQL message
that explains the reason.
User response: Correct the error.
System action: Processing continues.

DRL0403I The purge condition for table is added. User response: The error message indicates a problem
that must be corrected.
Explanation: The purge condition for table was
successfully added.
DRL0415E There are no tables to be purged.
System action: Processing continues.
Explanation: The PURGE statement failed because
User response: None. there were no included tables that had a purge
condition defined.
DRL0404I DRL0405I DRL0406I System action: The log collector stops processing the
current statement and continues with the next.
Explanation: Messages DRL0404I through DRL0406I
are used to build a table that shows the number of User response: Correct the error.
rows deleted from different tables during a purge
process. For an example of such a table, see Figure 2 on
page 35. DRL0431E The ISPF operation operation failed with
return code n.
System action: Processing continues.
Explanation: ISPF operations do not work in this
User response: None. context.
System action: The log collector stops processing the
DRL0407W Purging data from table with the purge current statement and continues with the next.
condition condition was not successful.
User response: Correct the error.
Explanation: Check the output for an SQL message
that explains the reason.
DRL0432W There is no record to be displayed.
System action: Processing continues.
Explanation: The log was processed but contained no
User response: Ensure that the warning message does records of the requested type. No record was displayed.
not indicate a problem that must be corrected.
System action: Processing continues.

DRL0408I No purge condition exists for the table User response: Ensure that the warning message does
table. not indicate a problem that must be corrected.

Explanation: DROP PURGE FROM was not

performed on table because no purge condition existed. DRL0433W No record is displayed. The first record
to be displayed is n1, but the log
System action: Processing continues. contains only n2 records.
User response: None. Explanation: The sequence number of the first record

30 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0434E • DRL0448E

to be displayed is higher than the number of records in User response: Check the output for messages issued
the log. before this message for more information on why the
processing was interrupted. Correct the error.
System action: No record is displayed.
User response: Specify a record number that is not
DRL0443E The INSERT clause specifies only the
higher than the number of records in the log.
values of GROUP BY columns. The
table already contains a row with these
DRL0434E An error was found during initialization values.
of DISPLAY of record record.
Explanation: The RECALCULATE statement is
Explanation: The log collector was invoked to assist in applied to a table that is the target of one or more
the dialog function DISPLAY RECORD. The definition update definitions. The INSERT clause of the statement
of the specified record cannot be used. The reason is specifies values for only those columns that are used as
explained by preceding messages. GROUP BY columns in these updates. The table
already contains a row with these values.
System action: The record is not displayed.
System action: The table is not updated. The log
User response: Ensure that the record definition is collector stops processing the current statement and
correct. continues with the next.
User response: Depending on what you intend to
DRL0435W No record is displayed. Records of the achieve, alter the clause to specify values of non-key
requested type exist in the log, but none columns, or specify a combination of key values that is
after record number n. not present in the table.
Explanation: At least one record of the specified type
exists in the log, but the sequence number of the first DRL0444E The INSERT clause does not specify
record to be displayed was specified to be higher than values of all GROUP BY columns.
the last record of the specified type.
Explanation: The RECALCULATE statement is
System action: No record is displayed. applied to a table that is the target of one or more
User response: Do not specify a record number, or update definitions. The INSERT clause of the statement
specify a lower record number. does not specify values for all columns that are used as
GROUP BY columns in these updates.

DRL0441E An incorrect number of values is System action: The table is not updated. The log
specified in the INSERT clause. collector stops processing the current statement and
continues with the next.
Explanation: If the INSERT clause of the
RECALCULATE statement does not specify any User response: Specify values of all GROUP BY
column names, the number of values specified by the columns.
clause must be equal to the number of columns in the
table. If the INSERT clause specifies one or more DRL0445I DRL0446I DRL0447I
column names, the number of values must be the same
as the number of column names. Explanation: Messages DRL0445I through DRL0447I
are used to build a table that shows the number of
System action: The log collector stops processing the rows updated, deleted from, and inserted by a
current statement and continues with the next. RECALCULATE statement. For an example of such a
User response: Ensure that the number of values is table, see Figure 3 on page 35.
equal to the number of columns in the table, or to the System action: Processing continues.
number of specified column names.
User response: None.
DRL0442E An error occurred during initialization
of RECALCULATE. DRL0448E The RECALCULATE statement is
terminated by an overflow.
Explanation: An error occurred during initialization of
RECALCULATE. Message DRL0442E might be issued Explanation: An overflow is the situation when the
in conjunction with other messages that describe the result of an accumulation function becomes too large to
cause of the error and explain why processing was be stored in the specified column. This message is
interrupted. preceded by message DRL0350E that provides further
details.
System action: The log collector stops processing the
current statement and continues with the next. System action: The log collector stops processing the
current statement and continues with the next.

Chapter 1. Host Messages 31

DRL0449E • DRL0980E

User response: See explanation and user response for

DRL0461E The ALTER statement was not
message DRL0350E.
processed.
Explanation: A previous message explains why the
DRL0449E The INSERT clause specifies null value
processing stopped.
for one or more GROUP BY columns.
System action: The log collector stops processing the
Explanation: The RECALCULATE statement is
current statement and continues with the next.
applied to a table that is the target of one or more
update definitions. The INSERT clause of the statement User response: Correct the error.
specifies a null value for a column that is used as a
GROUP BY column in these updates.
| DRL0471E module-name : Error in query before
System action: The table is not updated. The log | service service . Routine failed RC=return
collector stops processing the current statement and | code
continues with the next.
| Explanation: An unexpected error occurred
User response: Check the INSERT clause. Ensure that | attempting a Query service using CSRCESRV (MVS
all values specified for GROUP BY columns are | Expand and Compress services) prior to Expanding or
non-null. | Compressing a record. The return code is the return code
| from the CSRCESRV macro. See MVS Programming
| Assembler Services Reference Vol 1 for possible return
DRL0450E The table table is specified more than
| codes
once.
| System action: The log collector stops processing and
Explanation: The table table appears more than once in
| has probably abended with a message similar to
the list of tables to be recalculated.
| ABEND=S000 U0002 REASON=00000000.
System action: The log collector stops processing the
| User response: This is an internal error. Save the input
current statement and continues with the next.
| log and job output, then contact IBM support.
User response: Correct the statement and rerun
RECALCULATE.
| DRL0472E module-name: Error in service service.
| Routine failed RC=return code.
DRL0451E The table table is not based on any of
| Explanation: An unexpected error occurred
the specified tables.
| attempting an Expand or Compress service using
Explanation: The table table appears in the list of | CSRCESRV (MVS Expand and Compress services). The
tables to be recalculated. It requires an update | return code is the return code from the CSRCESRV
definition from another table in the list, or from the | macro. See MVS Programming Assembler Services
table specified in the clause that follows the list. No | Reference Vol 1 for possible return codes.
such update definition exists.
| System action: The log collector stops processing and
System action: The log collector stops processing the | has probably abended with a message similar to
current statement and continues with the next. | ABEND=S000 U0002 REASON=00000000.
User response: Correct the statement and rerun | User response: This is an internal error. Save the input
RECALCULATE. | log and job output, then contact IBM support.

DRL0452E The UPDATE clause specifies null value DRL0980E FFST Initialization failed with return
for one or more GROUP BY columns. code return code.
Explanation: The RECALCULATE statement is Explanation: This message is issued in connection
applied to a table that is the target of one or more with an abnormal termination of program processing. If
update definitions. The UPDATE clause of the the abnormal termination is of the kind that might
statement specifies a null value for a column that is indicate a program error, the program attempts to
used as a GROUP BY column in these updates. register it with FFST™/MVS (First Failure Support
Technology™ for Multiple Virtual Storage). FFST/MVS
System action: The table is not updated. The log is an IBM licensed program that improves availability
collector stops processing the current statement and for IBM and vendor software applications by providing
continues with the next. immediate problem notification and first-failure data
User response: Check the UPDATE clause. Ensure that capture for software problems.
all values specified for GROUP BY columns are The most likely reason for the message is that
non-null. FFST/MVS is not installed. You might then also receive

32 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL0981E • DRL0994S

message CSV003I stating that one of the FFST modules

DRL0991S The DB2 subsystem name is not active.
cannot be loaded.
Explanation: You tried to run the log collector or the
If FFST is installed, the message indicates that the
installation preprocessor, specifying name as the name
communication with FFST cannot be established, and
of the DB2 subsystem. The subsystem is not active.
the termination will not be registered.
System action: The program is not run.
System action: Abnormal termination is not registered
with FFST/MVS. Processing continues. User response: Try again when the subsystem is
active.
User response: If FFST is not installed, you can ignore
this message. If message CSV003I is issued, it can also
be ignored. The information about the abnormal DRL0992S Release level mismatch between the
termination can be found in the DRLDUMP file (the DB2 subsystem name and Call
information is the same as that registered in FFST). Attachment Facility.
If FFST is installed, you can still ignore the message if Explanation: You tried to run the log collector or the
the DRLDUMP file is sufficient. If you need the installation preprocessor, specifying name as the name
FFST/MVS support, refer to the FFST/MVS of the DB2 subsystem. The DB2 Call Attachment
documentation, and look up the return code and the Facility failed when trying to connect to the subsystem.
message(s) that were issued. Remove the cause of the The likely reason for the failure is that the Call
failure. Attachment Facility you are using has a different
release level than the DB2 subsystem.
DRL0981E An FFST software probe failed with System action: The program is not run.
return code return code.
User response: Ensure that the STEPLIB or LOADLIB
Explanation: Processing of the FFST software probe you are using contains the correct version of the
failed. modules DSNALI, DSNHLI2, and DSNTIAR.
System action: No FFST dump is produced.
Information about the error is written to the DRL0993S The DB2 subsystem name is unknown,
DRLDUMP file. Processing continues. or you are not authorized to use it.
User response: If you need the FFST dumps, refer to Explanation: You tried to run the log collector or the
the FFST documentation, and look up the return code installation preprocessor, specifying name as the name
and the message(s) that were issued. Remove the cause of the DB2 subsystem. Either a subsystem with this
of the failure. name does not exist, or you are not authorized to use
it.
DRL0982E FFST Termination failed with return System action: The program is not run.
code return code.
User response: Ensure that you specify a correct
Explanation: Termination of FFST failed. subsystem and that you have the necessary
authorization.
System action: Processing continues.
User response: Refer to the FFST/MVS
DRL0994S The plan name does not exist, or you are
documentation, and look up the return code and the
not authorized to use it.
message(s) that were issued. Remove the cause of the
failure. Explanation: You tried to run the log collector or the
installation preprocessor. These programs need the plan
name for their execution. Either the plan does not exist,
DRL0990S The DB2 Call Attachment Facility
or you are not authorized to use it.
cannot be loaded.
System action: The program is not run.
Explanation: You tried to run the log collector or the
installation preprocessor, but one or more of the User response: Ensure that the plan exists and you
modules DSNALI, DSNHLI2, and DSNTIAR cannot be have the necessary authorization.
loaded.
System action: The program is not run.
User response: Ensure that the library containing the
modules is specified as STEPLIB or LOADLIB.

Chapter 1. Host Messages 33

Examples of Output

Examples of Output from COLLECT, PURGE and

RECALCULATE

DRL0300I Collect started at 1992-12-04-10.04.15

DRL0302I Processing SMF.DATA.SET on VOL001.
DRL0341I The first-record timestamp is 1992-06-03.00.01.730000.
DRL0308I A database update started after 2608 records due to a
buffer-full condition.
DRL0342I The last-record timestamp is 1992-06-03.11.52.40.220000.
DRL0310I A database update started after 4582 records due to end of log.
DRL0313I The collect buffer was filled 1 times. Consider increasing the collect buffer size.
DRL0003I
DRL0315I Records read from the log or built by log procedure:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_000 | 0
DRL0319I SMF_006 | 6
DRL0319I SMF_007 | 0
. . . .
. . . .
. . . .
DRL0319I SMF_090 | 0
DRL0320I Unrecognized | 3
DRL0318I -------------------|----------
DRL0321I Total | 4582
DRL0003I
DRL0316I Records built by record procedures:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_030_X | 2012
DRL0319I SMF_070_X | 200
DRL0318I -------------------|----------
DRL0321I Total | 2212
DRL0003I
DRL0323I -------Buffer------ ------Database-----
DRL0324I Table name | Inserts Updates Inserts Updates
DRL0325I ---------------------------------------------------------------------
DRL0326I DRL .AVAILABILITY_D | 3 23 2 1
DRL0326I DRL .AVAILABILITY_M | 3 1 2 1
DRL0326I DRL .AVAILABILITY_T | 9 76 9 0
. . . . . . .
. . . . . . .
. . . . . . .
DRL0326I DRL .MVS_WORKLOAD_H | 144 366 132 12
DRL0326I DRL .MVS_WORKLOAD_M | 60 12 48 12
DRL0325I ---------------------------------------------------------------------
DRL0327I Total | 2643 99019 2148 495
DRL0003I
DRL0301I Collect ended at 1992-12-04-10.09.43.

Figure 1. An Example of Messages Generated by a COLLECT Statement. It Illustrates the Use of Messages
DRL0404I through DRL0406I.

34 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL1000E • DRL1003E

DRL0300I Purge started at 1993-01-23-19.27.34

DRL0404I Table name | Deletes
DRL0405I ----------------------------|----------
DRL0406I SLR .VM_ACCOUNTING_D | 642
DRL0406I SLR .VM_ACCOUNTING_M | 0
DRL0301I Purge ended at 1993-01-23-19.28.01

Figure 2. An Example of Messages Generated by a PURGE Statement. It Illustrates the Use of Messages DRL0317I
through DRL0327I.

DRL0445I Table name | Updates Deletes Inserts

DRL0446I ----------------------------|------------------------------
DRL0447I DRL .NW_RTM_RESPONSE_D | 5 0 8
DRL0447I DRL .NW_RTM_RESPONSE_W | 0 0 4
DRL0447I DRL .NW_RTM_RESPONSE_M | 11 0 19
. . . . . .
. . . . . .
. . . . . .
DRL0447I DRL .AVAILABILITY_M | 25 0 2
DRL0447I DRL .AVAILABILITY_T | 7 0 1

Figure 3. An Example of Messages Generated by a RECALCULATE Statement. It Illustrates the Use of Messages
DRL0445I through DRL0447I.

REXX-SQL Interface Messages

This section describes REXX-SQL interface messages generated during batch
processing. Tivoli Decision Support for z/OS implements the REXX-SQL interface
in the DRL1SQLX module. As described in the Administration Guide, the module
retrieves its input data from arguments on CALL instructions and from predefined
REXX variables. The output from the execution of a SELECT statement is returned
in an array of REXX variables the module creates. The module supports all DB2
data types except graphic strings. The return code from the module is set in the
REXX variable RESULT. For information about invocation, refer to the
Administration Guide.

DRL1000E SQL could not be initialized. SQLCODE DRL1002E The variable DB2SUBS, specifying the
contains the return code from the DB2 DB2 subsystem name, cannot exceed 4
CAF connection. characters.
Explanation: Tivoli Decision Support for z/OS cannot Explanation: The calling REXX EXEC has specified a
connect to DB2. DB2 subsystem name that is longer than four
characters.
System action: Tivoli Decision Support for z/OS does
not process the SQL statement. System action: Tivoli Decision Support for z/OS does
not process the SQL statement.
User response: Refer to DB2 Messages and Codes,
SC26-4379, for an explanation of the cause. User response: Correct the subsystem name and
perform the operation again.
DRL1001E The variable DB2SUBS, specifying the
DB2 subsystem name, was not set. DRL1003E No SQL statement was passed as
argument.
Explanation: The calling REXX EXEC did not specify
the name of the DB2 subsystem. Explanation: The SQL statement parameter was
missing from the call to the SQL interface module.
System action: Tivoli Decision Support for z/OS does
not process the SQL statement. System action: Tivoli Decision Support for z/OS does
not process the SQL statement.
User response: Set the subsystem name and perform
the operation again. User response: Add the SQL statement and perform
the operation again.

Chapter 1. Host Messages 35

DRL1004E • DRL1013W

DRL1004E SQLSTEM cannot exceed 240 characters. DRL1009E A REXX variable could not be set due to
insufficient storage.
Explanation: The maximum length of the SQLSTEM
variable is 240 characters. Explanation: REXX storage is full.
System action: Tivoli Decision Support for z/OS does System action: Tivoli Decision Support for z/OS halts
not process the SQL statement. processing of the SQL statement.
User response: Specify a value shorter than 240 User response: Increase the storage available to the
characters and perform the operation again. REXX EXEC.

DRL1005E The REXX variable variable could not be DRL1010W SQLMAX is not a valid number. The
set. default was used.
Explanation: Tivoli Decision Support for z/OS cannot Explanation: The SQLMAX variable does not contain
set the REXX variable variable. a valid numeric value. Tivoli Decision Support for
z/OS used the default SQLMAX value 5000 instead.
System action: Tivoli Decision Support for z/OS does
not process the SQL statement. System action: Processing continues.
User response: Contact your system programmer. User response: Ensure that the warning message does
not indicate a problem that must be corrected.
DRL1006E Column number n has the SQL data
type type, which is not supported. DRL1011E The SQLHANDLE value is invalid on
INIT. INIT may have been issued twice.
Explanation: Column n has a data type that is not
supported by the REXX-SQL interface. The SQL code Explanation: The SQLHANDLE variable is reserved
for the data type is type. and is not to be changed. It must have no value on the
first INIT call, and the value 0 on subsequent INIT
System action: Tivoli Decision Support for z/OS does
calls. The INIT call sets it to a value and a TERM call
not process the SQL statement.
resets it to zero (0).
User response: Do not include this column in the
System action: This INIT was not processed.
SELECT statement.
User response: Change the REXX EXEC to remove the
cause of this error.
DRL1007W Not all rows were returned when
SQLMAX was reached.
DRL1012E The SQLHANDLE value is invalid on
Explanation: The REXX variable SQLMAX limits the
TERM. INIT may be missing.
number of rows returned on a SELECT statement. If
you do not specify SQLMAX, Tivoli Decision Support Explanation: The SQLHANDLE variable does not
for z/OS uses a default value of 5000 rows. contain the kind of value that an INIT call stores in it.
The SQLHANDLE variable is reserved and must not be
System action: Processing ends. The remaining rows
changed by the REXX EXEC.
are not read.
System action: This TERM was not processed.
User response: If the number of rows returned is not
However, Tivoli Decision Support for z/OS performs
sufficient, increase the MAXROWS value.
an SQL COMMIT at the end of the task.
User response: Change the REXX EXEC to remove the
DRL1008E REXX variables could not be accessed.
cause of this error.
IRXEXCOM return code is -1.
Explanation: Tivoli Decision Support for z/OS loaded,
| DRL1013W SQLMAX exceeds maximum value (m).
but cannot access the REXX routine IRXEXCOM, which
communicates REXX variables between the REXX | Explanation: The SQLMAX value is greater than the
EXEC and the SQL interface routine. | maximum value m supported by the REXX-SQL
| interface. Tivoli Decision Support for z/OS used the
System action: Tivoli Decision Support for z/OS does
| maximum SQLMAX value instead.
not process the SQL statement.
| System action: Processing continues.
User response: Contact your system programmer.
| User response: Set SQLMAX to a value less than or
| equal to the supported value.

36 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2001E • DRL2007E

IMS Feature Messages

These messages are issued by the IMS collect feature.

include I/O errors or insufficient storage. This message

DRL2001E csect procedure at label. GETMAIN failed
can be issued by procedures DRL2IMSK and
for node allocation.
DRL2LOGP with labels OUTCKER, WRITERR2, and
Explanation: A GETMAIN failed while trying to WRITERR3.
acquire additional storage for the internal node name,
System action: Processing stops.
indicating a lack of virtual storage. This message can be
issued by procedure DRL2IFAL or DRL2IMSH with User response: See any accompanying messages. You
labels NOFREESP or ALBINER. must decide the potential impact of the failure. Decide
whether to return to the beginning and reprocess all
System action: Processing stops.
data, or whether you can restart from the point where
User response: See any accompanying messages. the failure occurred with no appreciable loss of data.
Rerun the job from the last successful checkpoint and
database commit, specifying a suitable TABLEFLUSH
DRL2005E csect procedure at label. An error occurred
parameter to let the program invoke recovery.
when resolving pointers.
Explanation: An error occurred while Tivoli Decision
DRL2002E csect procedure at label. Duplicate key
Support for z/OS was trying to rebuild internal tables
found.
from the input checkpoint file. This message can be
Explanation: An attempt to update an internal table issued by procedure DRL2IMSH with label RESLERR.
failed. All keys must be unique, and old entries must
System action: If the pointer is not an SPA pointer,
be cleared before new entries can be inserted. This
processing terminates. If the pointer is an SPA pointer,
message can be issued by procedures DRL2IFCE,
this message is accompanied by message DRL2069W
DRL2IFCI, DRL2IFCR, DRL2IFCU, DRL2IFC1, and
and processing continues.
DRL2IFC2 with labels DUPKEYEI, DUPKEYER,
DUPKEYRT, DUPKEYUR, DUPKEYD1, and System programmer response: Collect relevant
DUPKEYD2, respectively. information about the sequence of events leading to
this error. Save the input checkpoint file and previously
System action: Processing stops.
processed log data. Contact your IBM representative.
System programmer response: Contact your IBM
User response: See any accompanying messages. If
representative.
processing terminates, inform your system programmer
User response: See any accompanying messages. of all symptoms.
Ensure that you have not tried to process across a gap
in your input IMS log, or that you have not processed
DRL2006E csect procedure at label. The input file
across an IMS emergency restart or cold start. Ensure
allocated to DRLICHKI is empty.
that you have not mistakenly processed logs from
different IMS systems. Ensure that the necessary IMS Explanation: An empty data set was allocated to the
log records are available, if an IMS archive exit has input checkpoint file (ddname DRLICHKI). This
been used. Sequence number, date, and time indicators message can be issued by procedure DRL2IMSH with
in accompanying messages may help indicate such a label INFILERR.
problem.
System action: Processing stops.
If you find that incorrect data has been passed to the
log procedure, separate the data into parts and try User response: Do not allocate an empty data set to
again to process it. the input checkpoint file (ddname DRLICHKI). Rerun
the job.
If the error persists, contact your system programmer.

DRL2007E csect procedure at label. Checkpoint ID in

DRL2004E csect procedure at label. An error occurred checkpoint file is invalid.
when writing the ddname file.
Explanation: Tivoli Decision Support for z/OS is
Explanation: An error occurred when Tivoli Decision processing an incorrect data set as an input checkpoint
Support for z/OS tried to write to the data set file. This message can be issued by procedure
allocated—either to the output log-procedure DRL2IMSH with label CPIDERR.
checkpoint file (ddname DRLICHKO) or to the output
composite record (ddname DRLICOMP). Causes might System action: Processing stops.

Chapter 1. Host Messages 37

DRL2008I • DRL2014E

User response: Check the allocation for the job. If the cases, save all output, all checkpoint files, and all log
input checkpoint file (ddname DRLICHKI) is present, data, and contact your system programmer.
ensure either that it is DUMMY, or that only a valid
checkpoint file is allocated.
DRL2011E csect procedure at label. parameter
parameter error.
DRL2008I A checkpoint is taken at IMS log
Explanation: This message indicates that an error was
sequence number hexadecimal value at
detected in parameter, being processed from ddname
approximately Julian date time.
DRLIPARM. It can be issued by many procedures with
Explanation: The log procedure is taking a checkpoint. many possible labels.
The last processed IMS record had logical log sequence
System action: Processing stops.
number hexadecimal value and the data was taken on
Julian date at time. User response: See any accompanying messages.
Ensure that you have not coded any comment in the
Note: The date and time is provided as found in the first eight fields just after the equals (=) sign of the
processed IMS records and is reported in printable numeric parameters in the DRLIPARM. Correct any
packed-decimal IMS Julian date and time format. syntax errors in the parameters and rerun.
System action: Processing continues.
DRL2012I The default IMSID is set to IMS.
User response: None.
Explanation: No IMSID is specified. Tivoli Decision
Support for z/OS assumes the default.
DRL2009E csect procedure at label. Total records read
from checkpoint file is not the same as System action: Processing continues.
the number of records expected.
User response: None.
Explanation: The log procedure tried to process an
input checkpoint file that was not written correctly, and
DRL2013I n duplicate keys were found while
thus unusable. The first record in the checkpoint file
creating SPA entries.
contains the number of records expected to be written
to the file. This message can be issued by procedure Explanation: While processing IMS conversational
DRL2IMSH with label CPFILER. records, Tivoli Decision Support for z/OS tried to
create a new conversational control block entry in
System action: Processing stops.
internal tables and found that the entry already existed
System programmer response: Contact your IBM and had not been freed.
representative.
System action: Tivoli Decision Support for z/OS
User response: See any accompanying messages. overwrites and establishes new pointers. Processing
Check for error messages in the output from the job continues.
that created the checkpoint file you are now trying to
User response: None.
read.
Try to recreate the checkpoint file by reprocessing the
DRL2014E csect procedure at label. Cannot create the
appropriate data from the last run. Then try to read the
node entry.
newly created checkpoint file.
Explanation: An internal error occurred. This message
If the problem persists and no error messages are
can be issued by procedures DRL2IFCL and DRL2InnE
issued, and no abends are encountered that might
with labels NTCRUR01, CPERFAIL, CPEIFAIL,
cause such a problem, save all output, log data, and
CRRTFAIL, and LKURFAIL.
checkpoint files and contact your system programmer.
System action: Processing stops.
DRL2010E csect procedure at label. Null or invalid System programmer response: Contact your IBM
pointer. representative.
Explanation: An internal error occurred. This message User response: See any accompanying messages. In all
can be issued by many procedures with many possible cases, save all output, all checkpoint files, and all log
labels. data, and contact your system programmer.
System action: Processing stops.
System programmer response: Contact your IBM
representative.
User response: See any accompanying messages. In all

38 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2015E • DRL2022I

DRL2015E csect procedure at label. imsid is different DRL2019I The stop time as specified in the
from the default or the specified IMSID parameter has been reached.
and IMSIDCHECK=FAIL.
Explanation: The program terminates, because the
Explanation: The default or specified IMSID does not date and time specified in the STOP parameter are
correspond to the IMSID that Tivoli Decision Support found in the IMS records being processed.
for z/OS found in the IMS type X‘42’ log records. The
System action: Processing stops.
parameter IMSIDCHECK=FAIL is specified. This
message can be issued by procedure DRL2IMST with User response: None.
label IMIDFAIL.
System action: Processing stops. DRL2020E csect procedure at label. Cannot load the
module name.
User response: Correct the specification of the IMSID
to the one indicated in this message, or change Explanation: The program cannot load the specified
IMSIDCHECK=FAIL to IMSIDCHECK=CONTINUE, module because of a problem with virtual storage, or
and reprocess the data. because the module either cannot be found or was not
valid. This message can be issued by procedure
DRL2LOGP with label IMSLERR.
DRL2016W imsid is different from the default or the
specified IMSID and System action: If the module is DRL2InnL, processing
IMSIDCHECK=CONTINUE. terminates. If the module is a DRL3Innx report module,
processing continues.
Explanation: The default or specified IMSID does not
correspond to the IMSID found in the IMS type X‘42’ System programmer response: Contact your IBM
log records. The parameter IMSIDCHECK=CONTINUE representative.
is specified.
User response: See any accompanying messages.
System action: Processing continues. Ensure that you specified a valid IMSVER or REPORTS
parameter.
User response: Ensure that you wish to use the IMSID
as specified or defaulted as a key value. If not, change If the module is valid, save all output, including the
the IMSID parameter and force IMSIDCHECK=FAIL. product installation procedures, and contact your
system programmer.
DRL2017W Checkpoint statistics data not found.
Composite record not created from the DRL2021W No available entry in the array for the
IMS type X‘47’ log record. allocated pointer. All the maximum
number of array entries entries have been
Explanation: Tivoli Decision Support for z/OS found
used.
type X‘47’ region checkpoint records before finding any
IMS checkpoint start X'4001' record. You are probably Explanation: All entries in the pointer arrays have
processing an incomplete log. been used.
System action: Processing continues. System action: Processing stops.
User response: None. User response: Ensure that you were processing valid
IMS data correctly, then restart from the previous
usable checkpoint. Increase the MAXFREE parameter
DRL2018E csect procedure at label. The node name is
specification or specify the TABLEFLUSH parameter to
not found in table.
reduce the amount of data pending in storage.
Explanation: An internal error occurred. This message
can be issued by procedure DRL2IPNF with label
DRL2022I IMS log processing started at date and
FREENDNF.
time.
System action: Processing stops.
Explanation: Processing started for the input data at
System programmer response: Contact your IBM the IMS date and time indicated. The message appears
representative. only if the user specifies a START date and time
parameter.
User response: See any accompanying messages. In all
cases, save all output, all checkpoint files, and all log System action: Processing continues.
data and contact your system programmer.
User response: None.

Chapter 1. Host Messages 39

DRL2023E • DRL2031W

data, and contact your system programmer.

DRL2023E csect procedure at label. The START
parameter is greater than or equal to the
STOP parameter. DRL2027E csect procedure at label. node has already
been written.
Explanation: The START parameter for the log
procedure specifies a time later than that specified in Explanation: An internal error occurred. This message
the STOP parameter. This message can be issued by the can be issued by procedure DRL2IFK1 with label
procedure DRL2IMSJ with the label TIMEERR. WRGINP12.
System action: Processing stops. System action: Processing stops.
User response: Correct the START and STOP User response: See any accompanying messages. In all
parameters and rerun the job. cases, save all output, all checkpoint files, and all log
data, and contact your system programmer.
DRL2024E csect procedure at label. The binary node
array limit is exceeded. DRL2028E csect procedure at label. WFIScannot yet
completed.
Explanation: An internal error occurred. This message
can be issued by procedure DRL2IMSH with label Explanation: An internal error occurred. This message
ALARYER. can be issued by procedure DRL2IFK1 with label
WRGINP15.
System action: Processing stops.
System action: Processing stops.
System programmer response: Contact your IBM
representative. User response: See any accompanying messages. In all
cases, save all output, all checkpoint files, and all log
User response: Try to process the next log without the
data, and contact your system programmer.
input checkpoint file. In all cases, save all output, all
checkpoint files, and all log data and contact your
system programmer. DRL2029I TABLEFLUSH is invoked.
Explanation: Tivoli Decision Support for z/OS scans
DRL2025E csect procedure at label. IMS log sequence and flushes storage tables according to the IMS
number second hex number is not greater measured age of the various transaction entries, as
than the previous log sequence number specified by TABLEFLUSH.
first hex number.
System action: Processing continues.
Explanation: The log procedure detected an
out-of-sequence condition while processing the input User response: None.
log data. This message can be issued by procedure
DRL2IMSL with label IMS_log_record_seq. DRL2030W Output count n exceeds maximum output
System action: Processing stops. limit.

User response: Ensure that: Explanation: Only maximum output limit of program
outputs are being matched to a transaction or batch
v The IMS log data you passed to the log procedure is message program which actually issued n outputs.
not out of order
v You used the correct log-procedure input checkpoint All excess outputs are written as unconnected subtype
file (ddname DRLICHKI). X'FB' records for later processing and analysis, if
needed.
Correct the sequence and reprocess.
System action: Processing continues.
Note: You might need to purge some data from the User response: None.
database before reprocessing.
DRL2031W The composite record length has
DRL2026I csect procedure at label. An error occurred exceeded maximum value. The record is
when linking D1 to UOR. truncated.
Explanation: An internal error occurred. This message Explanation: In trying to write a composite record to
can be issued by procedure DRL2IMSQ with label DRLICOMP, Tivoli Decision Support for z/OS tried to
ERLKD1UR. include too much data in the record. To prevent any
processing errors, the record truncates at the nearest
System action: Processing stops.
practical limit to the maximum (30 000 bytes).
User response: See any accompanying messages. In all
System action: Processing continues.
cases, save all output, all checkpoint files, and all log

40 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2032W • DRL2044E

| User response: Contact your IBM customer service User response: Check for errors in the specified data
| representative. set names and retry the job.

DRL2032W The parameter n value is too big. The DRL2038E csect procedure at label. An error is
default is used. encountered while writing the file
ddname.
Explanation: The value n that was specified for the
MAXOUTPUT or MAXUOR parameter is greater than Explanation: An error occurred when Tivoli Decision
the maximum allowed, so Tivoli Decision Support for Support for z/OS tried to close the input (ddname
z/OS used the default instead. DRLLOG) or output composite record (ddname
DRLICOMP). This message can be issued by procedure
System action: Processing continues.
DRL2LOGP with label CLOERR1 or CLOERR2.
User response: Correct the specification of the
System action: Processing stops.
parameter that is in error.
User response: See accompanying messages for other
possible errors.
DRL2033W The UOR count n exceeds maximum
UOR limit. Ensure that data set names were specified correctly and
retry the job.
Explanation: Only maximum UOR limit of records
related to a unit-of-recovery (UOR) commit are being
matched to a batch message program that actually DRL2039I n composites are generated by input
committed n times. DRRN entries.
System action: Processing continues. Explanation: Due to n specified in TABLEFLUSH,
Tivoli Decision Support for z/OS forced incomplete
User response: None.
transactions from storage tables.
System action: Processing continues.
DRL2034W The stray UOR count n exceeds
maximum UOR limit. User response: Check to see whether you must
specify the TABLEFLUSH parameter. Ensure that the
Explanation: Only maximum UOR limit number of
TABLEFLUSH parameter is really necessary.
records related to a unit-of-recovery (UOR) commit are
being matched to a batch message program that
actually committed n times. DRL2040I n composites generated by output
DRRN entries.
System action: Processing continues.
Explanation: Due to n specified in TABLEFLUSH,
User response: None.
Tivoli Decision Support for z/OS forced incomplete
transactions from storage tables.
DRL2035E csect procedure at label. TABLEFLUSH is
System action: Processing continues.
required but not requested.
User response: Check to see whether you must
Explanation: Tivoli Decision Support for z/OS
specify the TABLEFLUSH parameter. Ensure that the
reached storage limits and the log procedure was
TABLEFLUSH parameter is really necessary.
unable to recover because no TABLEFLUSH limit was
set to allow the flushing of old entries.
DRL2043I csect procedure at label. Default IMSVER
System action: Processing stops.
is assumed to be version.
User response: Ensure that an appropriate restart is
Explanation: The default version of IMS/ESA®
possible and rerun the job. Specify a suitable
(Version 3, Release 1) is assumed, because no IMSVER
TABLEFLUSH parameter.
parameter is specified.
System action: Processing continues.
DRL2036E csect procedure at label. An error is
encountered when opening the file User response: None.
ddname.
Explanation: An error occurred when Tivoli Decision DRL2044E csect procedure at label. parameter
Support for z/OS tried to open the input (ddname parameter error.
DRLLOG) or output composite record (ddname
Explanation: This message indicates that an error was
DRLICOMP). This message can be issued by procedure
detected in the parameter parameter processed from
DRL2LOGP with label OPERR1 or OPERR2.
ddname DRLIPARM. This message can be issued by
System action: Processing stops. many procedures with many possible labels.

Chapter 1. Host Messages 41

DRL2045W • DRL2052I

System action: Processing stops.

DRL2049W The report module name is not found.
User response: See any accompanying messages.
Explanation: The program cannot load the specified
Correct any syntax errors in the parameters and rerun
module because it cannot find the module.
the job.
System action: Processing continues for all routines
except the report module, which is terminated.
DRL2045W An error is encountered while writing
the report module report file. The report System programmer response: Contact your IBM
module is deleted. representative.
Explanation: A problem, such as an I/O error or User response: See any accompanying messages.
insufficient storage, was encountered when Tivoli Ensure that you are not trying to call a module that
Decision Support for z/OS tried to write output to the does not exist, by including an incorrect specification in
file for report module. the IMSVER or REPORTS parameters.
System action: Processing continues for all routines If the parameters are correct save all output, including
except the report module, which is terminated. the product installation procedures, and contact your
system programmer.
User response: Ensure that the warning message does
not indicate a problem that must be corrected.
DRL2050W An error is encountered in report
module name. The report module is
DRL2046W An error is encountered when opening
deleted.
the report module report file. The report
module is deleted. Explanation: Tivoli Decision Support for z/OS
encountered a problem within the report module name.
Explanation: A problem, such as an I/O error or
insufficient storage, was encountered when Tivoli System action: Processing continues for all routines
Decision Support for z/OS tried to open the file for the except the report module, which is terminated.
report module.
User response: If the report module is an
System action: Processing continues for all routines IBM-supplied module, save all output, all checkpoint
except the report module, which is terminated. files, and all log data, and contact your system
programmer.
User response: Ensure that the warning message does
not indicate a problem that must be corrected.
DRL2051W The restart location is not found in the
input IMS log.
DRL2047W A severe error occurred in the program.
Explanation: Tivoli Decision Support for z/OS
Explanation: An unrecoverable error was detected in
processed an input checkpoint file, and the restart
another routine.
position cannot be found in the input log data sets
System action: Processing stops. processed.

User response: See any accompanying messages for System action: Processing stops.
more information about the error.
User response: Ensure that the correct input
checkpoint file and the correct input log data sets are
DRL2048W An error is encountered while closing specified, and rerun the job.
the report module file.
Explanation: Tivoli Decision Support for z/OS DRL2052I IMS log processing stopped at date and
encountered a problem, such as an I/O error or time.
insufficient storage, when trying to close the file for the
Explanation: This message indicates the last date and
report module.
time encountered on the IMS log processed, and reports
System action: Processing continues for all routines in printable packed decimal Julian date and time
except the report module, which is terminated. format.

User response: Ensure that the warning message does System action: Processing continues.
not indicate a problem that must be corrected.
User response: None.

42 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2053I • DRL2062W

not indicate a problem that must be corrected.

DRL2053I number records were read from
DRLLOG.
DRL2059W The output checkpoint file is allocated.
Explanation: n records are read from the input data
The WRITEPENDING parameter is
sets allocated to ddname DRLLOG.
ignored.
System action: Processing continues.
Explanation: You allocated an output checkpoint file
User response: None. requesting that all pending transactions be written at
end-of-job. The presence of the output checkpoint file
overrides the WRITEPENDING parameter, to avoid the
DRL2054I Processing log data set name on volume
possibility of duplication.
volume.
System action: Processing continues.
Explanation: This message indicates the first data set
name, on the first volume being processed, as the input User response: Ensure that the warning message does
IMS log allocated to ddname DRLLOG. not indicate a problem that must be corrected.
System action: Processing continues.
DRL2060W IMS data on the checkpoint file record
User response: None.
has exceeded n. The data is truncated.
Explanation: In writing records to the output
DRL2055E csect procedure at label. An error is
checkpoint file, an IMS record truncated when it
encountered while reading the file
reached the maximum allowable length of 30 000 bytes.
ddname.
System action: Processing continues.
Explanation: Tivoli Decision Support for z/OS
encountered a read error in the ddname file. | User response:
System action: Processing stops. | Contact your IBM customer service representative.
User response: Check for errors in the specified data
set and retry the job. DRL2061W n output nodes not matched to any
input node using the "input node +
time" matching criterion.
DRL2056W The input file allocated to ddname is
empty. Explanation: While processing the input log, the log
procedure was unable to match apparent transaction
Explanation: The file allocated to DRLLOG is empty.
output messages to any input messages and
System action: Processing continues. transactions, using either the primary RTKN key or the
secondary LTERM and date and time search key.
User response: Ensure that the warning message does
not indicate a problem that must be corrected. System action: Processing continues.
User response: Ensure that the warning message does
DRL2057W An error is encountered when opening not indicate a problem that must be corrected.
the file DRLIPARM. The defaults are
assumed.
DRL2062W The output node at n is not matched to
Explanation: An error occurred when Tivoli Decision any input node as it does not have valid
Support for z/OS tried to open the input parameter fields to match on.
file.
Explanation: While processing the input log, the log
System action: Processing continues. procedure cannot match an apparent transaction output
message at a relative record number to any input, due
User response: Ensure that the warning message does to invalid data in the expected LTERM and the date
not indicate a problem that must be corrected. and time fields.
System action: Processing continues.
DRL2058W Cannot load the module name. The
default parameters are assumed. User response: Ensure that the warning message does
not indicate a problem that must be corrected.
Explanation: Module name cannot be loaded. Because
input parameters cannot be read, default parameters
are assumed.
System action: Processing continues.
User response: Ensure that the warning message does

Chapter 1. Host Messages 43

DRL2063E • DRL2072I

procedure DRL2IMST with label COLDSTRT.

DRL2063E csect procedure at label. This call type is
not supported. System action: Processing stops.
Explanation: The log procedure was called with an User response: Do not process this log data using an
invalid call type. This message can be issued by input checkpoint file.
procedure DRL2IMSL with label Invalid_Call_Type.
System action: Processing stops. DRL2068W The processing has been stopped
because of an error at the IMS log
System programmer response: Contact your IBM
sequence number hexadecimal value at
representative.
approximately date and time.
User response: See any accompanying messages. In all
Explanation: The routine was informed that an error
cases, save all output, all checkpoint files, and all log
occurred elsewhere. The last known date and time of
data and contact your system programmer.
the IMS data being processed was date and time. The
sequence number of the last processed record was
DRL2064I IMSID started at date and time has hexadecimal value.
switched OLDS at date and time as
System action: Processing stops.
indicated by IMS type X‘42’ log record
at hexadecimal value. User response: See any accompanying messages.
Explanation: Tivoli Decision Support for z/OS
encountered a type X‘42’ record that contained a DRL2069W Cannot resolve the pointer from an
different OLDS switch date and time from the input DRRN entry to a SPA entry. The
previously encountered OLDS switch date and time. pointer has been made null.
System action: Processing continues. Explanation: On restart, using an input checkpoint
file, SPA pointers cannot be resolved. Processing is
User response: None.
allowed to continue after the pointers are set to null.
This message is accompanied by message DRL2005E.
DRL2065I The processing has been restarted from
the IMS log sequence number System action: Processing continues.
hexadecimal value at approximately date
and time. User response: Ensure that the warning message does
not indicate a problem that must be corrected.
Explanation: Tivoli Decision Support for z/OS read an
input checkpoint file, and the log procedure restarted
processing on the corresponding input IMS log. DRL2070I Batch driver parameters:

System action: Processing continues. Explanation: This message is followed by a list of the
parameters specific to the batch driver, their values and
User response: None. how they were determined, default or specified in
DRLIPARM.
DRL2066E csect procedure at label. IMSID imsid is System action: None.
different from IMSID imsid as read from
the input checkpoint file. User response: None.

Explanation: The IMSID stored in the input

checkpoint file differs from the IMSID found on the DRL2071I Parameters used in this run:
input log file. This message can be issued by procedure Explanation: This message is followed by a list of the
DRL2IMST with label IMIDDIFF. parameters, their values and how they were
System action: Processing stops. determined, default or specified in DRLIPARM.

User response: Do not process this log data using this System action: None.
input checkpoint file. User response: None.

DRL2067E csect procedure at label. An input DRL2072I Statistics for NODEs created this run:
checkpoint file cannot be provided with
an IMS session which is restarted. Explanation: This message is followed by a list of the
NODE types with length, initially allocated, finally
Explanation: Tivoli Decision Support for z/OS allocated and the number pending at end-of-run.
successfully read an input checkpoint file, but the first
X'4001' record found on the input log file indicates an System action: None.
IMS cold start or restart. This message can be issued by User response: None.

44 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2073I • DRL2079E

of times the required IMS type x‘07’ record was not

DRL2073I Statistics for composite records created
found in the SET07BUF buffer. z - number of IMS type
this run:
x‘07’ records buffered in SET07BUF buffer.
Explanation: This message is followed by a list of the
System action: Processing continues.
composite record types with description, count,
minimum and maximum length and total bytes. User response: If log processing completed
successfully, compare the number of type X‘07’ records
System action: None.
buffered (z) with the value specified or defaulted for
User response: None. the DRLIPARM SET07BUF value. If the number of
records read is significantly lower than the SET07BUF
parameter value and this log represented a typical run,
DRL2074W D1D1 node on the checkpoint file
consider reducing the SET07BUF value to reduce
record has exceeded n.
virtual storage requirements for the collect. If message
Explanation: In writing records to the output DRL2075I was also issued increase the SET07BUF value
checkpoint file, a D1D1 node chain has been truncated to at least the number of type X‘07’ records read.
when it reached the maximum allowable length of
32700 bytes.
DRL2077I SET07BUF buffer using DD DRLIMS07
System action: The collect terminates normally but the for input.
checkpoint produced is incomplete and must not be
Explanation: The collector job has run with a
used as input checkpoint processing for the next IMS
DRLIMS07 DD. IMS type X‘07’ log records will be
log data set. This problem might be caused by an IMS
buffered from this DD, and not from the IMS logs.
error.
System action: Processing continues.
User response: Save all output, all checkpoint files,
and all log data, and contact your system programmer. User response: The DRLIMS07 DD must hold only
type X‘07’ records. If this is the case, no action is
required.
DRL2075E SET07BUF is out of space after xx
records. Log collector run terminated.
DRL2078E SET07BUF Active IMS type X‘07’ log
Explanation: The buffer used to hold IMS type X‘07’
records found without corresponding
log records for transaction processing was not large
SET07BUF entry. Log collector run
enough to hold all the type X‘07’ records contained in
terminated.
the log.
Explanation: The collector job has detected a type
System action: Processing stops after counting the
X‘07’ record in the IMS logs being processed that does
total number of type X‘07’ records in the log.
not exist in the SET07BUF buffer.
User response: Refer to message “DRL2076I” for a
System action: Processing terminates.
count of the total number of type X‘07’ records found
in the log data set. Increase the SET07BUF parameter User response: This is typically caused when
setting to at least this value before attempting to collect DRLIMS07 is used, but does not hold all type X‘07’
the log again. Increasing the SET07BUF value may records. Check that DRLIMS07 holds all type X‘07’
require additional virtual storage. records for all logs being processed, and rerun the job.

DRL2076I SET07BUF buffer usage statistics. Max DRL2079E DRLTMP07 file opened for input but no
number of Set07Buf entries searched = u records in the file. Log collector run
Min number of Set07Buf entries terminated.
searched = v Avg number of Set07Buf
Explanation: The collector job has opened the
entries searched = w Number of times
DRLTMP07 for input and has detected that there are no
Set07Buf Searched = x No. of times 07
records in the file. This is an indication that the
record not found = y No. of Set07Buf
DRLTMP07 file has been corrupted.
entries = z
System action: Processing terminates.
Explanation: This message provides usage statistics
for the SET07BUF buffer that buffers IMS type x‘07’ System programmer response: Contact your IBM
records. These statistics are: u - maximum number of representative.
SET07BUF records searched for an IMS type x‘07’
record v - minimum number of SET07BUF records User response: Try to determine the cause of the
searched for an IMS type x‘07’ record w - average corruption of the DRLTMP07 file. If the error persists,
number of SET07BUF records searched for an IMS type contact your system programmer.
x‘07’ record x - number of times the SET07BUF buffer
was searched for an IMS type x‘07’ record y - number

Chapter 1. Host Messages 45

DRL2080W • DRL2086I

(TABLEFLUSH=nnnn parameter).
DRL2080W DRLTMP07 file found allocated to
DUMMY or SYSOUT has been closed
and will not be used. Processing DRL2083I TABLEFLUSH freed n bytes of node
continues. storage.
Explanation: Explanation: This message is issued immediately after
message DRL2082I following the completion of a table
System action: Processing continues.
flush process. It shows the number of bytes of table
System programmer response: Contact your IBM entry storage that were freed.
representative.
System action: Processing continues.
User response: Try to determine the cause of the
User response: You can use this message to help tune
corruption of the DRLTMP07 file. If the error persists,
your TABLEFLUSH and FLUSHTYPE settings. The
contact your system programmer.
largest value reported in a DRL2083I message in a
collect step is indicative of the maximum amount of
DRL2081I TABLEFLUSH type processing started virtual storage that could be saved by flushing more
after n records. frequently (using a smaller value of
FLUSHTYPE=COUNT=nnnnnnn). An average of these
Explanation: Table flush processing was requested by
values is reported in the table flush processing statistics
the TABLEFLUSH or FLUSHTYPE parameters,
(message DRL2084I) at the end of the collect step.
FLUSHMSGS=YES was specified, and the conditions
defined by the specified or defaulted FLUSHTYPE
conditions were met. The flush type can be SOS for a DRL2084I TABLEFLUSH processing statistics.
short-on-storage condition, CHKPT for a checkpoint
Explanation: This message is followed by sums and
condition or COUNT if flushing based on the number
averages for table flush values recorded during the
of records processed was requested.
collect step.
System action: Processing continues.
System action: Processing continues.
User response: If a short-on-storage table flush
User response: Review the table flush statistics and
occurred you should consider increasing the REGION
consider whether they reflect processing that is
size used by the collect step. If excessive table flush
appropriate for your environment. Refer to the topic
processing messages are issued consider specifying
"Log procedure DRLOUT reports" in Chapter 2 "How
FLUSHMSGS=NO to suppress the messages produced
the IMS CSQ feature uses log and record procedures
for each invocation of table flush processing.
within the IMS Shared Queue" of the IMS Performance
Feature Guide and Reference..
DRL2082I TABLEFLUSH complete: ouow count
OUOWs written as composite records.
DRL2085I WRITEPENDING processing started
puow count input PUOWs flushed (n
after n records.
completed).
Explanation: Write pending processing was requested
Explanation: This message indicates the completion of
by the WRITEPENDING=YES parameter and the log
the table flush process started when the preceding
procedure has started writing composite records for
DRL2081I message was issued. Each flushed OUOW
incomplete data held in internal tables.
table entry is written as one or more composite records
to the Tivoli Decision Support for z/OS collector record System action: Processing continues.
stream, or to the DRLICOMP DDname if the log
procedure is being run by DRLSLOGP. The second line User response: None.
indicates how many IMS transactions (represented by
input PUOWs) are included in the composite record DRL2086I WRITEPENDING complete: ouow count
data, and how many of those transactions had OUOWs written as composite records.
complete data when they were flushed. Sums of the puow count input PUOWs flushed (n
three values given in this message are reported in the completed).
table flush processing statistics (message DRL2084I) at
the end of the collect step. Explanation: This message indicates the completion of
the write pending process started when the preceding
System action: Processing continues. DRL2085I message was issued. Each flushed OUOW
User response: If the proportion of completed input table entry is written as one or more composite records
PUOWs is too low you could consider reducing the to the Tivoli Decision Support for z/OS collector record
frequency of table flush processing stream, or to the DRLICOMP DDname if the log
(FLUSHTYPE=COUNT=nnnnnnnn parameter) or procedure is being run by DRLSLOGP. The second line
increasing the age limit for flushed entries indicates how many IMS transactions (represented by

46 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2087I • DRL2093W

input PUOWs) are included in the composite record processing continues. No check is done if VERIFY is
data, and how many of those transactions had defaulted or set to NONE.
complete data when they were flushed.
This is typically caused when logs have been input for
System action: Processing continues. the wrong IMS release. Ensure the log is for a single
IMS release.
User response: If the proportion of completed input
PUOWs is too low you could consider using checkpoint
processing to write the pending records to the DRL2091W More than one statistic record read
DRLICHKO DDname for input to a subsequent collect X'4500'. Record number rn, log number
where the IMS log records required to complete the ln, IMS Release release not matching
PUOW information may be available. record number rn, log number ln, IMS
Release release.
DRL2087I Buffer usage statistics for IMS 07 record Explanation: The collector job has detected more than
buffer Set07Buf. one statistic record X'4500' and the IMS versions do not
match. TDSz does not support IMS shared queues
Explanation: This message is followed by statistics for
across different versions of IMS.
SET07BUF processing recorded during the collect step.
System action: Processing continues.
System action: Processing continues.
User response: Ensure all logs input to the IMS log
User response: Review the SET07BUF statistics and
collector in a single run are for the same release of IMS.
consider whether they reflect processing that is
If you change the VERIFY parameter to FAIL and rerun
appropriate for your environment. Refer to the topic
the job, messages will be written but processing
"Log Procedure DRLOUT reports" in Chapter 2 "How
terminates. No check is done if VERIFY is defaulted or
the IMS CSQ feature uses log and record procedures"
set to NONE.
of the IMS CSQ Feature Guide and Reference.

DRL2092E drliparm/collect IMS version version does

DRL2088I n R2 records written by record
not match statistic X'4500' IMS Release
procedure DRLSIxx2.
release, record number rn, log number ln,
Explanation: This message reports the number of run terminated.
transaction data (R2) records written by the IMS shared
Explanation: The default or specified IMS version
queue feature record procedure DRLSIxx2 (where xx
does not correspond to the IMS release found in the
indicates the IMS version of the log being processed: 81
IMS statistic record X'4500'. This is typically caused
for IMS V810; 91 for IMS V910 and A1 for IMS V10). If
when logs have been input for the wrong IMS release.
the log is being processed stand-alone then the records
are written to the DRLIRPT2 file, otherwise the records System action: Processing terminates.
enter the Tivoli Decision Support for z/OS record
User response: Ensure that you wish to use the IMS
stream for further processing.
version specified, or defaulted as a key value. If not,
System action: Processing continues. change the DRLSLOGP IMSVER parameter, or change
the IMS log Collect component. If you change the
User response: None. This message is intended only
VERIFY parameter to WARN and rerun the job,
as an indication of the transaction volume in the log.
messages will still be written and processing continues.
No check is done if VERIFY is defaulted or set to
DRL2090E More than one statistic record read NONE.
X'4500'. Record number rn, log number
ln, IMS Release release not matching
DRL2093W drliparm/collect IMS version version does
record number rn, log number ln, IMS
not match statistic X'4500' IMS Release
Release release, run terminated.
release, record number rn, log number ln.
Explanation: The collector job has detected more than
Explanation: The default or specified IMS version
one statistic record X'4500' and the IMS versions do not
does not correspond to the IMS release found in the
match. TDSz does not support IMS shared queues
IMS statistic record X'4500'. This is typically caused
across different versions of IMS.
when logs have been input for the wrong IMS release.
System action: Processing terminates.
System action: Processing continues.
User response: Ensure all logs input to the IMS log
User response: Ensure that you wish to use the IMS
collector in a single run are for the same release of IMS.
version specified, or defaulted as a key value. If not,
If you change the VERIFY parameter to WARN and
change the DRLSLOGP IMSVER parameter, or change
rerun the job, messages will still be written and
the IMS log Collect component. If you change the
VERIFY parameter to FAIL and rerun the job, messages

Chapter 1. Host Messages 47

DRL2094E • DRL2101E

will be written but processing terminates. No check is System action: Processing continues.
done if VERIFY is defaulted or set to NONE.
User response: This is typically caused when logs
have not been merged from all systems. Check that
DRL2094E invalid IMS version version encountered logs have been merged from all systems, and rerun the
in procedure procedure, run terminated. job. If you change the VERIFY parameter to FAIL and
rerun the job, messages will be written but processing
Explanation: The default or specified IMS version is
terminates. No check is done if VERIFY is defaulted or
not supported.
set to NONE.
System action: Processing terminates.
User response: Change the DRLSLOGP IMSVER DRL2097E There is an active system imsid but no
parameter, or change the IMS log Collect component. If log records found for this system, run
you change the VERIFY parameter to WARN and rerun terminated.
the job, messages will be written but processing
Explanation: The collector job has detected
terminates. No check is done if VERIFY is defaulted or
transactions for an active IMS system, but has not
set to NONE.
found log records for the system. This is typically
caused when logs have not been merged from all
DRL2095E Shared and non-shared queue records systems.
found.
System action: Processing terminates.
Explanation: The collector job has detected
User response: Check that logs have been merged
transactions for more than one active IMS system.
from all systems, and rerun the job. If you change the
However, there are non-shared queue records found.
VERIFY parameter to WARN and rerun the job,
This implies that there should only be transactions
messages will still be written and processing continues.
from and about one system.
No check is done if VERIFY is defaulted or set to
System action: Processing terminates. NONE.

User response: This is typically caused when logs

have not been merged from all systems. Check that DRL2098W There is an active system imsid but no
logs have been merged from all systems, and rerun the log records found for this system.
job. If you change the VERIFY parameter to WARN and
Explanation: The collector job has detected
rerun the job, messages will still be written and
transactions for an active IMS system, but has not
processing continues. No check is done if VERIFY is
found log records for the system. This is typically
defaulted or set to NONE.
caused when logs have not been merged from all
systems.
DRL2096W Shared and non-shared queue records
System action: Processing continues.
found.
User response: Check that logs have been merged
Explanation: The collector job has detected
from all systems, and rerun the job. If you change the
transactions for more than one active IMS system.
VERIFY parameter to FAIL and rerun the job, messages
However, there are non-shared queue records found.
will be written but processing terminates. No check is
This implies that there should only be transactions
done if VERIFY is defaulted or set to NONE.
from and about one system.

CICS Feature Messages

These messages are issued by the CICS record procedure.

not exceed the number of dictionary entries (fields) for

DRL2101E Dictionary not found for CICS
any matching dictionary block found.
class=class monitoring record. CICS
applid=applid and MVS system System action: Processing stops.
ID=system.
User response: Ensure that a valid dictionary record
Explanation: The CICS record procedure (DRL2CICS) precedes the identified records. You can achieve this by
did not find a matching dictionary block. The following these steps:
procedure searches existing dictionary blocks for a 1. Create a dictionary record using either the CICS
block matching the input record values for system, utility program DFHMNDUP (for CICS Version 3 or
applid, and class. The procedure also checks that the
highest field connector value in the input record does

48 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2102I • DRL2116W

higher) or (for CICS Version 2 only) the Tivoli

DRL2111W n CICS monitoring records written to
Decision Support for z/OS DRL1CIEX utility.
dataset data set name because matching
2. COLLECT this dictionary record. DRL2CICS stores dictionaries could not initially be found:
it in the CICS_DICTIONARY table. The first time
DRL2CICS is called (at COLLECT initialization), all Explanation: The CICS record procedure (DRL2CICS)
dictionaries are read from CICS_DICTIONARY. had no matching dictionary block when it processed a
record in the log. The messages that follow this
3. COLLECT again the log that failed with this
message (DRL2112I–2115I) list the CICS systems
message. Records are processed from the last
affected, how many records without dictionaries were
COMMIT point that occurred before this message.
encountered, and whether a dictionary was eventually
found.
DRL2102I CICS monitoring field field not defined
System action: Tivoli Decision Support for z/OS does
in CICS_FIELD table.
not process the affected records—it passes them
Explanation: The CICS monitoring field field in the unaltered to the DRLNDICT data set.
currently processed dictionary record is not present in
User response: To successfully collect the records for
the CICS_FIELD table.
the CICS systems listed in the DRL2114I messages that
System action: Processing continues. Any data for the have Found = Yes, rerun collect with the DRLNDICT
field field is lost. data set as the new input log (and an empty data set as
the new DRLNDICT output data set).
User response: Define the field field in the
CICS_FIELD table and the corresponding record If any CICS systems listed in the DRL2114I messages
definition: either SMF_CICS_T (for all CICS Versions), have Found = No, you must first generate a dictionary
or (for CICS Version 2 only) SMF_CICS_A. Ensure that for the CICS system. If the CICS system is CICS/MVS,
the field offsets are the same in both the CICS_FIELD stop and start CMF. If the system is CICS/ESA, you
table and the record definition. can stop and start CMF, or you can use the
DFHMNDUP utility to generate a dictionary record.
You must run a collect job with the data set containing
DRL2109E The DRLNDICT file record length is too the generated dictionary record as input, and then
short. The current record needs a record rerun collect with the data sets containing the
length of n bytes. uncollected records (the DRLNDICT data sets).
Explanation: The CICS record procedure (DRL2CICS)
cannot write to the ddname DRLNDICT, because the DRL2112I, DRL2113I, DRL2114I, DRL2115I
record length is too short.
Explanation: Messages DRL2112I through DRL2115I
System action: Tivoli Decision Support for z/OS halts are used to build up a table of CICS systems that had
collect execution. missing dictionary records. See message DRL2111W for
User response: Check that the logical record length is an explanation.
no less than the length in the error message. Change
your collect JCL to allocate a sequential data set with DRL2116W n other CICS records without
LRECL = 32754, BLOCKSIZE = 32760, and dictionaries were written, but only the
RECFM = VB. Rerun collect. first 20 systems are shown using
message DRL2114I.
DRL2110W The file DRLNDICT could not be Explanation: There were missing CICS dictionaries for
opened. more than 20 CICS systems.
Explanation: The CICS record procedure (DRL2CICS) System action: The remaining CICS systems are not
needs an output data set allocated to the ddname listed, but their records are written to the DRLNDICT
DRLNDICT. data set.
System action: Tivoli Decision Support for z/OS halts User response: Take the action described for message
collect execution. DRL2111W for the listed systems. Recollect using the
User response: Change your collect JCL to allocate a DRLNDICT data set as input (and a new data set
sequential data set with LRECL = 32754, allocated as DRLNDICT). If there are more systems
BLOCKSIZE = 32760, and RECFM = VB. Rerun without dictionaries, up to 20 of them will be listed in
collect. the rerun.

Chapter 1. Host Messages 49

DRL2117E • DRL2205E

sections. Record in error = n.

DRL2117E Write failed to the DRLNDICT file.
Return code=return code. Explanation: The CICS record procedure (DRL2CIST)
has encountered a record where the total record length
Explanation: The CICS record procedure (DRL2CICS)
and the end of the data sections are inconsistent. The
cannot write records to the ddname DRLNDICT.
(valid) data sections in the record are processed, and
System action: Tivoli Decision Support for z/OS halts the data that follows these valid data sections is
collect execution. ignored.
User response: Check that your DRLNDICT data set System action: Processing continues. No valid data in
is correctly allocated. Change your collect JCL to record n is lost.
allocate a sequential data set with LRECL = 32754,
User response: Examine record n to determine the
BLOCKSIZE = 32760, and RECFM = VB. Rerun
reason for the inconsistency. If required, contact your
collect.
system programmer.

DRL2118I Inconsistency in CICS statistics record.

Processing continues with valid data

AS/400 Messages
These messages are issued by the AS/400 System Performance feature.

DRL2201E Parameter parameter does not match any DRL2203E Identifier record on log file is missing
expected parameter. or invalid. It contains string where
SOURCE is expected.
Explanation: The value specified for the PARM
parameter on the DEFINE LOG statement, for the log Explanation: The SOURCE record on the OS/400 log
specified on the COLLECT statement, does not match file was not found.
any of the expected values. Expected values are: QHST,
System action: Collect run is terminated.
QJRNL, QSYS, QPOOL, QDISK, and QCONF. These
values are specified on the DEFINE LOG statement User response: Read OS/400 log files description in
shipped with the AS/400 System Performance feature. Chapter 2 in the AS/400 System Performance feature Guide
This error might occur if the DEFINE LOG statement and Reference. Change the DSNAME parameter on the
was created or modified by the user. DRLLOG DD statement to point to a valid OS/400 log
file specified or investigate why the SOURCE record is
System action: Collect run is terminated.
missing or invalid.
User response: Check the log name on the COLLECT
statement and the PARM parameter on the
DRL2204W Unexpected line number n1 found on
corresponding DEFINE LOG statement. Correct the
history record. n2 was expected.
PARM parameter to contain any of the values above
depending on log type. Explanation: The log procedure DRL2O400 detected
that line numbers on message lines are not consecutive
when building an OS400_HISTORY_MSG record.
DRL2202E Identifier record on log file does not
identify the same log as the COLLECT System action: The OS400_HISTORY_MSG record that
statement. Log identifier log identifier1 is being built is bypassed. Collect continues.
found on the record. log identifier2 was
expected. User response: Investigate why line numbers are not
consecutive.
Explanation: The log type entry on the SOURCE
record is not equal to the expected log type entry.
DRL2205E OS/400 version in identifier record of
System action: Collect run is terminated. log file is missing.
User response: Read the OS/400® log files description Explanation: The OS/400 version in the identifier
in Chapter 2 in the AS/400 System Performance Feature record of the log file being processed was not found.
Guide and Reference. Change the DSNAME parameter on
the DRLLOG DD statement, or the log name on the System action: Collect run is terminated.
COLLECT statement. The log file specified on the User response: Update the SP400 file with the one
DRLLOG DD statement must be of the same type as shipped with the current version. Files captured using
the log specified on the COLLECT statement. SP400 before the current release can no longer be

50 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL2206E • DRL3007W

processed, unless they are updated with the OS/400

DRL8003 Elapsed time(s): Q1 CPU use(d): Q2 Tot
version. To collect the actual failing log, run the
AUX stg(MB): Q3 Avail AUX stg(MB):
DRLJ4VRS job that writes the OS/400 version into the
Q4 pages: Q5 I/O reqs: Q6 Jobs Q7 Nbr
record identifier.
of ASP:s: Q8
Explanation: This message is produced by the SP400
DRL2206E OS/400 version in identifier record of
monitoring job, which is activated by the STRSPSRV
log file is invalid or out of maintenance.
SP400 command. It contains average values, computed
Explanation: The value found for the OS/400 version for a selected time interval, of performance data. It is
in the identifier record of the log file is invalid or it is a written into the system history log, every number of
version that is out of maintenance. minutes previously selected.

System action: Collect run is terminated. System action: None.

User response: Check whether your current AS/400 User response: None.
version is a supported one.

DEFINE/DROP Report and Report Group Messages (REXX Utility)

This section describes messages generated by Tivoli Decision Support for z/OS’s
report definition language during batch processing. Refer to the Language Guide and
ReferenceLanguage Guide and Reference for information about the report definition
language.

Explanation: Before importing the query to QMF,

DRL3001I The report/group, report ID/group ID, is
Tivoli Decision Support for z/OS searches for variable
defined.
definitions. Tivoli Decision Support for z/OS cannot
Explanation: The definition of the report or group find the SQL statement WHERE. This error also occurs
executed successfully. if the table name (defined by the SQL statement FROM)
is blank.
System action: None.
System action: Tivoli Decision Support for z/OS
User response: None.
ignores the missing WHERE statement and processes
the statement.
DRL3002I The report/group, report ID/group ID, is
User response: Add or correct the WHERE statement
dropped.
in the query.
Explanation: The report or group is dropped
successfully.
DRL3006W No end quote is found in string.
System action: None.
Explanation: The string is missing an end-quote
User response: None. delimiter. (Quoted strings cannot span more than one
line.)
DRL3003W The length of the description text, table System action: Tivoli Decision Support for z/OS
name, or default value exceeds n inserts an end-quote delimiter at the end of the string
characters. The description text, table name, and processes the statement.
or default value is truncated.
User response: Insert an end-quote delimiter in the
Explanation: The definition for the description text, string. Valid end-quote delimiters are the single quote
table name, or default value is incorrect. The length (’) or the double quote (”).
exceeds the maximum number of characters allowed
(number).
DRL3007W No shift-in is found in string.
System action: Tivoli Decision Support for z/OS
Explanation: A string containing double-byte
truncates the value and processes the statement.
characters is missing a shift-in (X'0F').
User response: Correct the definition.
A string containing double-byte characters must be
delimited using identifiers (identifiers). This string must
DRL3004W No WHERE statement is found in the also be delimited using a shift-out (X'0E') and a shift-in
query query. (X'0F').

Chapter 1. Host Messages 51

DRL3008E • DRL3017E

System action: Tivoli Decision Support for z/OS ends System action: Processing stops.
the string at the end of the character row and processes
User response: Correct the input parameter using one
the statement.
of the valid values listed in the message.
User response: Incorporate a shift-in delimiter to end
the string containing double-byte characters.
DRL3013E The DRLIN file file could not be found.
Explanation: The file file was defined in the list of
DRL3008E The report/group, report ID/group ID, is
concatenated DRLIN files, but cannot be found.
already defined.
System action: Processing terminates
Explanation: You are trying to define a report or
group that is already defined. User response: Ensure that all files identified by the
ddname DRLIN exist.
System action: Processing stops.
User response: Use a different ID, or delete the
DRL3014E The input file DRLIN is empty, or
existing report or group before defining a new one with
contains only comments.
the same ID.
Explanation: The input file DRLIN requires one or
more commands to be executed, but it is empty, or
DRL3009E If an input parameter is given, it must
contains only comments.
be set to a value. SYSTEM=value
SYSPREFIX=value PREFIX=value System action: None.
SHOWINPUT=value SHOWSQL=value
MODE=value User response: Ensure that the correct file was
allocated to DRLIN.
Explanation: The call to the DRLERDEF EXEC is
incorrect. An input parameter is defined but is not
assigned a value. DRL3015E object/statement/option, value, is not
recognized.
System action: Processing stops.
Explanation: An object, statement, or option is invalid.
User response: Assign a value to the input parameter.
To use defaults, remove the input parameter. System action: Processing stops.
User response: Check for syntax errors in the DEFINE
DRL3010E The call to the DRLERDEF EXEC or DROP statements. Valid objects are REPORT or
contains an invalid input parameter: GROUP. Valid statements are DEFINE or DROP. For
parameter. information on valid options, refer to descriptions of
the DEFINE and DROP commands in Language Guide
Explanation: The call to the DRLERDEF EXEC and ReferenceLanguage Guide and Reference.
contains an invalid input parameter.
System action: Processing stops. DRL3016E Error defining/droppingreport/group, report
ID/group ID.
User response: Correct the input parameter.
Explanation: An error occurred during execution of
the DEFINE or DROP statements.
DRL3011E The call to the EXEC DRLERDEF
contains one or more invalid input System action: Processing stops.
parameters.
User response: Check for syntax errors in the DEFINE
Explanation: The call to the EXEC DRLERDEF or DROP statements. Valid objects are: REPORT or
contains one or more invalid input parameters. GROUP. Valid statements are: DEFINE or DROP. For
information on valid options, refer to descriptions of
System action: Processing stops.
DEFINE and DROP in Language Guide and
User response: Correct the input parameter(s). See ReferenceLanguage Guide and Reference.
previous messages.
DRL3017E START failed due to a parameter error:
DRL3012I invalid value value for SHOWINPUT, dsq_start_parm_error.
SHOWSQL or MODE. Valid values are
Explanation: QMF cannot be started.
valid values.
System action: Processing stops.
Explanation: In the call to the EXEC DRLERDEF, the
SHOWINPUT, SHOWSQL or MODE input parameter User response: See previous messages issued by QMF.
contained an invalid value.

52 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3018E • DRL3028E

DRL3018E A QMF error occurred when defining DRL3023E Conflicting values, values, for the
the report report ID. BATCH option.
Explanation: A QMF error occurred. Explanation: The DEFINE REPORT statement
contains an invalid definition for the BATCH option.
System action: Processing stops.
(Only one value is allowed for the run cycle.)
User response: See previous messages issued by QMF.
System action: Processing stops.
User response: Correct the definition of the BATCH
DRL3019E No start quote found for description text
option.
or default value.
Explanation: The DESCRIPTION and DEFAULT
DRL3024E Syntax error or missing semicolon at the
options for the DEFINE REPORT statement must use
end of the statement.
quotation marks as delimiters. The start-quote
delimiter—a single quote (‘) or a double quote (“)—is Explanation: The DEFINE or DROP statement either
missing. contains a syntax error or is missing a semicolon.
System action: Processing stops. System action: Processing stops.
User response: Delimit the option using quotes. User response: Correct the statement, remembering to
end each statement with a semicolon.
DRL3020E The report ID/group ID is not specified.
DRL3025E invalid report type: type. Valid types are
Explanation: The DEFINE statement is missing the
QUERY, TABDATA, and GRAPHDATA.
report or group ID.
Explanation: The DEFINE REPORT statement
System action: Processing stops.
contained an invalid definition for the TYPE option.
User response: Specify the ID.
System action: Processing stops.
User response: Correct the definition of the TYPE
DRL3021E The file file is not allocated or file type
option. Valid values are QUERY, TABDATA, or
cannot be processed.
GRAPHDATA. The default value is QUERY.
Explanation: The file file is not allocated.
v QMF queries and forms are imported from DRL3026E The QUERY or FILE option must be
DRLDEFS1, DRLDEFS2, or DRLDEFS3 (searched in specified if the report type is QUERY,
that order). DRLDEFS1 must be defined. TABDATA, or GRAPHDATA.
v The input file DRLIN must be allocated. It contains
Explanation: The DEFINE REPORT statement must be
the statement(s) to be executed.
v QUERY for QUERY type reports
v The output file DRLOUT must be allocated. All v FILE for TABDATA/GRAPHDATA type reports
output messages are written to DRLOUT.
System action: Processing stops.
System action: Processing stops.
User response: Define the QUERY or FILE option.
User response: Allocate the file.

DRL3027E The FILE option must be specified if the

DRL3022E Unable to allocate data set data set name. BATCH SAVE option is specified.
Command: ALLOCATE Return code:
return code Explanation: If you define the BATCH SAVE option,
you must also define the FILE option in the
Explanation: Allocation of the requested data set did DEFINE REPORT statement.
not complete correctly. An ALLOCATE return code and
accompanying error message are returned. System action: Processing stops.

System action: Processing stops. User response: Define the FILE option.

User response: Use the text of the TSO/E error

message that accompanies the return code to determine DRL3028E If the report type is type, do not specify
the cause of the error. Refer to TSO/E Messages, the QUERY option.
GC28-1885, for an explanation of the cause. Correct the Explanation: The DEFINE REPORT statement
error. contains conflicting options. The QUERY option cannot
be used if the report type is TABDATA or
GRAPHDATA.

Chapter 1. Host Messages 53

DRL3029E • DRL3039S

System action: Processing stops. Support for z/OS assumes that the report or group is
public.
User response: Correct the conflicting options.

DRL3035E No table name is found in QUERY

DRL3029E If BATCH is specified, the report type
query.
must be QUERY.
Explanation: The query to be imported to QMF does
Explanation: The DEFINE REPORT statement
not contain a table name. The SQL statement FROM
contains conflicting options. If you specify the BATCH
cannot be found.
option, the report type must be QUERY.
System action: Processing stops.
System action: Processing stops.
User response: Check for errors in the QUERY query.
User response: Correct the conflicting options.

DRL3036E QMF command: START qmf_command.

DRL3030E The optionvariable is too long. The
maximum length is n characters. Explanation: QMF cannot be started.
Explanation: The DEFINE REPORT statement System action: Processing stops.
contains an incorrect definition for the QUERY, FORM,
User response: See previous messages issued by QMF.
CHART, FILE, or MACRO option. The length exceeds
the allowed maximum.
DRL3038S A severe DB2 error occurred in EXEC
System action: Processing stops.
DRLERDEF.
User response: Correct the option.
Explanation: A severe DB2 error occurred.
System action: Processing stops.
DRL3032E Object QUERY or FORMobject name is not
found. The following data set(s) were System programmer response: Determine the cause of
searched: data set name(s). the error. The SQL interface in REXX is implemented in
the DRL1SQLX module. A call to the interface resulted
Explanation: QMF queries and forms are imported
in a severe error. See messages generated by the
from DRLDEFS1, DRLDEFS2, or DRLDEFS3 (searched
interface.
in that order). At least one of the files must be
allocated. Tivoli Decision Support for z/OS cannot find User response: Record all listed messages and contact
the QUERY or FORM in any of the data sets listed in your system administrator.
the message.
System action: Processing stops. DRL3039S An error occurred when trying to
perform ROLLBACK.
User response: Ensure that the correct files are
allocated. Ensure the QUERY or FORM name is spelled Explanation: An error has occurred, and all changes
correctly. that were made to tables before the error occurred must
be rolled back. Tivoli Decision Support for z/OS
processed the SQL command ROLLBACK, but it did
DRL3033E The group group ID does not exist.
not complete correctly. (The tables might contain
Explanation: Tivoli Decision Support for z/OS cannot corrupt data.)
find the named group. Before you define the report,
System action: Processing stops.
you must define one or more groups to which the
report belongs. System programmer response: Determine why
ROLLBACK did not complete correctly. Correct the
System action: Processing stops.
data in the tables. Check to see if the original command
User response: Define the group before you define the issued by the user was DEFINE. If so, you might be
report. able to correct the tables by executing a DROP
command.
DRL3034E The report/group report ID/group ID, User response: Record all listed messages and contact
owner owner, does not exist. your system administrator.
Explanation: You are trying to drop a report or group
that is not defined.
System action: Processing stops.
User response: Ensure that the OWNER option is
defined correctly. If it is omitted, Tivoli Decision

54 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3040S • DRL3107E

System programmer response: Determine why

DRL3040S An error occurred when trying to
COMMIT did not complete correctly. Correct the data
perform COMMIT.
in the tables, if necessary.
Explanation: After each DEFINE REPORT command,
User response: Record all listed messages and contact
the SQL command COMMIT is executed to commit the
your system administrator.
database changes made. The SQL command COMMIT
did not complete correctly.
System action: Processing stops.

Batch Reporting Messages (REXX Utility)

These messages are issued during batch reporting.

tabular reports to the DSQPRINT data set. Tivoli

DRL3100I The tabular/graphic report report ID is
Decision Support for z/OS saves tabular reports in the
printed to/saved as name.
DRLREP data set, and graphic reports in the ADMGDF
Explanation: One of the following: data set.
v The tabular report report ID has been successfully System action: None.
printed to DSQPRINT.
User response: None.
v The graphic report report ID has been successfully
printed to the graphic printer printer name.
v The tabular report report ID has been successfully DRL3104I The DSQPRINT, DRLREP, or ADMGDF
saved as member name name in the data set defined file is not allocated; tabular/graphic
by the ddname DRLREP. reports cannot be printed/saved.
v The graphic report report ID has been successfully Explanation: Tivoli Decision Support for z/OS writes
saved as member name name in the data set defined tabular reports to the DSQPRINT data set. Tivoli
by the ddname ADMGDF. Decision Support for z/OS saves tabular reports in the
DRLREP data set, and graphic reports in the ADMGDF
System action: The command was processed.
data set.
User response: None.
System action: None; tabular reports cannot be
printed/saved (DSQPRINT/DRLREP), or graphic
DRL3101I The printer for graphic reports is printer reports cannot be saved (ADMGDF).
name.
User response: Allocate a data set to the appropriate
Explanation: The printer to be used for graphic file (DSQPRINT, DRLREP, or ADMGDF).
reports is printer name.
System action: None. DRL3105I The tabular/graphic report report ID
cannot be printed/saved.
User response: None.
Explanation: See previously given messages.
DRL3102I No printer was specified; graphic System action: Processing terminates for report ID, but
reports cannot be printed. continues with the next report (if there is one).
Explanation: You did not specify a printer. Graphic User response: See previously given messages.
reports are written to the printer specified in the
PRINTER parameter. The default printer for graphic
DRL3106E No report(s) found.
reports is the printer defined in the QMF profile.
Explanation: Either no batch report was found or no
System action: None; graphic reports are not printed.
report matches the selected subset.
User response: For graphic reports, identify a printer
System action: Processing stops.
in the PRINTER input parameter, or define a printer in
the QMF profile. User response: Ensure that the input parameters are
correct. If no input parameters are given, all batch
reports are printed.
DRL3103I The file file was allocated to data set
name.
DRL3107E Unable to print or save reports.
Explanation: Tivoli Decision Support for z/OS writes

Chapter 1. Host Messages 55

DRL3108E • DRL3117E

Explanation: The necessary file is not allocated, and

DRL3112E invalid value value specified for input
no printer is defined.
parameter CYCLE. Valid values are:
v The default printer for graphic reports is the printer DAILY, WEEKLY, or MONTHLY.
defined in the QMF profile.
Explanation: A call issued to the DRLEBATR EXEC
v Tabular reports are saved to the DRLREP file.
contains an invalid value in the CYCLE input
v Graphic reports are saved to the ADMGDF file. parameter.
v Tabular reports are written to the DSQPRINT file.
System action: Processing stops.
v Graphic reports are written to the printer given as
input parameter. User response: Correct the input parameter using one
of the valid values listed in the message.
System action: Reports cannot be printed or saved.
Processing stops.
DRL3113E An error occurred in the QMF command
User response: Allocate the file necessary to perform SET GLOBAL (variable=variable value).
the requested action.
Explanation: A QMF error occurred; input parameters
cannot be defined as global variables in QMF.
DRL3108E An invalid value value is specified for
the variable variable. System action: Processing stops.

Explanation: The variable’s input parameter contains User response: See previous messages issued by QMF.
an invalid value.
System action: Processing stops. DRL3114E An error occurred while running the
QUERY query in the report report ID.
User response: Correct the input parameter.
Explanation: An error occurred when the QMF
command RUN QUERY was executed.
DRL3109E The start or end quote is missing.
System action: Processing stops.
Explanation: The variable value is missing either a
start-quote delimiter or an end-quote delimiter. User response: See previous messages issued by QMF.

System action: Processing stops.

DRL3115E START failed due to a parameter error:
User response: Insert the missing start quote or end dsq_start_parm_error.
quote for the variable listed in the previous message.
Explanation: A parameter error prevented the START
command from being completed.
DRL3110E invalid input parameter: parameter, for
EXEC DRLEBATR. System action: QMF cannot be started. Processing
stops.
Explanation: A call issued to the DRLEBATR EXEC
contained an incorrect input parameter. User response: See previous messages issued by QMF.

System action: Processing stops.

DRL3116E QMF START MODE=B
User response: Valid input parameters are: CYCLE, DSQSSUBS=DB2 subsystem
GROUP, REPORT, PRINTER, &variable, SYSTEM,
SYSPREFIX, and PREFIX. Explanation: A parameter error prevented the START
command from being completed.

DRL3111E If the input parameter parameter is given, System action: QMF cannot be started. Processing
it must be set to a value. stops.

Explanation: A call issued to the DRLEBATR EXEC User response: See previous messages issued by QMF.
contains an input parameter without an assigned value.
System action: Processing stops. DRL3117E Unable to allocate data set data set name.
Command: ALLOCATE Return code:
User response: Assign a value to the input parameter. return code
If you want to use defaults, remove the input
parameter. Explanation: DRLEBATR attempted to allocate the
data set identified by the ddname DRLREP to save a
tabular report. However, the requested data set cannot
be correctly allocated. An ALLOCATE return code and
accompanying error message are returned.
System action: Processing terminates for the tabular

56 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3118I • DRL3125E

report currently being processed. DRLEBATR continues reinstalled. If this does not solve the problem, report
with the next report if any. the problem to IBM.
User response: Use the text of the TSO/E error
message that accompanies the return code to determine DRL3122E Query and column information do not
the cause of the error. Refer to TSO/E Messages, match for report report ID.
GC28-1885, for an explanation of the cause. Correct the
Explanation: Information about the columns in the
error.
query is stored in the system table
DRLREPORT_COLUMNS when the component is
DRL3118I There is no data for report report ID. installed (predefined report), or when the report is
created (user-defined report). The number of columns
Explanation: The query for the report report ID did
stored in the system table does not match the number
not return any rows that matched the selection criteria.
of columns received when the query is executed.
System action: This message is always followed by
System action: This message is always followed by
DRL3105I.
DRL3105I.
User response: If the report contains prompt variables,
User response: If this is a user-defined report, open
by changing the values of one or more prompt
the report definition and correct the problem. If this is
variables you might obtain result rows.
a predefined report, drop the report and install the
component again. Even though the component status is
DRL3119E Substitution value missing for already 'Installed', the dropped report will be
variable(s) in the query query. reinstalled. If this does not solve the problem, report
the problem to IBM.
Explanation: One (or more) variable(s) that was (were)
present in the query cannot be substituted when the
query is run. DRL3123E Chart could not be produced.
GDDMREXX is not available.
System action: This message is always followed by
DRL3105I. Explanation: The call to GDDM through GDDMREXX
failed. The reason might be that GDDM is not installed,
User response: The variable 'variable name' is present or the data set containing GDDMREXX is not allocated.
in the query, but was not detected and stored in a
system table when the report was installed (predefined System action: This message is always followed by
reports are stored during component installation). If the DRL3105I.
cause is that a variable is missing from a system table,
User response: If GDDM is not used, the variable
drop the report and reinstall the component. Although
GDDMUSE in the customization module DRLEINI1
the component status is already 'Installed', the dropped
must be changed to 'NO'.
report will be reinstalled. If this does not solve the
problem, report the problem to IBM.
DRL3124W Your SQLMAX limit was reached for
report report ID.
DRL3120I
Explanation: The read of the DB2 table stopped when
Explanation: This message is used to insert
the SQLMAX number of rows was reached. SQLMAX
information headings in the list of messages issued by
is specified with the DRLMAX parameter.
DRLEBATR.
System action: The report was processed.
System action: Processing continues.
User response: Increase the DRLMAX value in the
User response: None.
parameter to the DRLEBATR exec, if you want to see
all data in the report.
DRL3121E No query found for report report ID.
Explanation: The query for report report ID was not DRL3125E An SQL error occurred in DRLERDIR
found in the system tables. for report report ID.

System action: This message is always followed by Explanation: Refer to previously given messages.
DRL3105I.
System action: This message is always followed by
User response: If this is a user-defined report, open DRL3105I.
the report definition and correct the problem. If this is
User response: If you cannot find the cause of the
a predefined report, drop the report and install the
error, report the problem to IBM.
component again. Even though the component status is
already 'Installed', the dropped report will be

Chapter 1. Host Messages 57

DRL3126W • DRL3132E

DRL3126W Report width exceeded the output DRL3131E GROUP column missing in report report
record length. Data is truncated. ID.
Explanation: When the report was generated, the Explanation: The report report ID contains a column
length of one or more result rows exceeded the record with usage code ACROSS. Such reports must also have
length for the output data set. The report was at least one column with usage code GROUP.
truncated.
System action: This message is always followed by
System action: The report was processed. DRL3105I.
User response: Ensure that the target for the report User response: The ACROSS data must be 'grouped'
has a record length which is sufficient for the report. with one (or more) column(s) in the report. Add usage
You might need to re-allocate the output data set. code GROUP to the appropriate column(s).

DRL3127E A form text variable does not have a DRL3132E More than one ACROSS usage code in
matching column. report report ID.
Explanation: A form text variable of the type &n Explanation: The selected report contains more than
appears in the column information (where 'n' refers to one column with the ACROSS usage code. However,
the column number of the form). However, this column only data from one query column can be aggregated
does not exist. ACROSS.
System action: This message is always followed by System action: This message is always followed by
DRL3105I. DRL3105I.
User response: If this is a user-defined report, open User response: Correct the definitions so that only one
the report definition and correct the problem. Form text query column contains the ACROSS usage code.
variables can be defined in either report headings and
footings or column headings. If this is a predefined
report, drop the report and install the component again.
Even though the component status is already 'Installed',
the dropped report will be reinstalled. If this does not
solve the problem, report the problem to IBM.

DRL3128E A variable assigned to limit the number

of result rows was not numeric.
Explanation: The variable assigned to limit the
number of result rows in the report, was not numeric.
System action: This message is always followed by
DRL3105I.
User response: Specify a numeric value for the
variable.

DRL3130E A column in report report ID has an

invalid usage code.
Explanation: A column in report report ID has a usage
code which is not supported.
System action: This message is always followed by
DRL3105I.
User response: If this is a user-defined report, open
the report definition and correct the problem. If this is
a predefined report, drop the report and install the
component again. Even though the component status is
already 'Installed', the dropped report will be
reinstalled. If this does not solve the problem, report
the problem to IBM.

58 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3150I • DRL3160W

Migration Messages

DRL3150I Migration of SLR V3R3 table table to DRL3155E The variable variable value not found. The
Tivoli Decision Support for z/OS DB2 following dataset(s) were searched:
table table performed successfully. dataset name(s)
Explanation: The data from the SLR V3R3 table table Explanation: QMF queries and forms are imported
has been successfully inserted into the corresponding from DRLDEFS1 and DRLDEFS2. The variable variable
Tivoli Decision Support for z/OS DB2 table. value was not found in the data set(s) listed in the
message.
System action: Processing continues.
System action: Processing stops.
User response: None.
User response: Check that the correct files are
allocated.
DRL3151I SLR DB2 table table not migrated.
Explanation: Migration of the SLR table table failed
DRL3156E START failed due to a parameter error:
when data was to be inserted into the corresponding
parameter
Tivoli Decision Support for z/OS DB2 table.
Explanation: A parameter error prevented the
System action: Processing continues.
successful completion of START.
User response: The migration process failed during
System action: QMF cannot be started. The processing
execution of a QMF RUN command to insert SLR table
is terminated.
data into an Tivoli Decision Support for z/OS DB2
table. Check the output for QMF message preceding User response: See previous messages issued by QMF.
this one for the cause and an explanation of why the
QMF command failed.
DRL3157E QMF command: START qmf_command
Explanation: QMF cannot be started.
DRL3152E Missing input parameter(s) for EXEC
DRLEMIGR. System action: Processing stops.
Explanation: One or more input parameters are User response: See previous messages issued by QMF.
missing in the generated JCL.
System action: Processing stops. DRL3158E An error occurred in the QMF command
SET GLOBAL (variable=variable value).
User response: Supply the missing parameters for
DRLEMIGR in the generated JCL. Explanation: A QMF error occurred; input parameters
cannot be defined as global variables in QMF.
DRL3153E The DRLOUT file is not allocated. System action: Processing stops.
Explanation: The DRLOUT file must be allocated. All User response: See previous messages issued by QMF.
Tivoli Decision Support for z/OS output messages are
written to DRLOUT.
DRL3159E An error occurred running the query
System action: Processing stops. query.
User response: Allocate the file. Explanation: An error occurred when the QMF
command RUN QUERY was executed.
DRL3154E No definition dataset was found. System action: Processing stops.
Explanation: No file DRLDEFS1 or DRLDEFS2 was User response: See previous messages issued by QMF.
allocated. QMF queries and forms are imported from
DRLDEFS1 and DRLDEFS2. At least one of the files
must be allocated. DRL3160W Unable to erase temporary table
DRLTEMP.
System action: Processing stops.
Explanation: Temporary table DRLTEMP cannot be
User response: Allocate the file(s). erased.
System action: Processing continues.
User response: None.

Chapter 1. Host Messages 59

DRL3161E • DRL3179E

DRL3161E Unable to import the unloaded SLR DRL3174E An error occurred when trying to
table table to QMF. perform function.
Explanation: An error occurred when the QMF Explanation: A COMMIT or ROLLBACK operation
command IMPORT was executed. failed.
System action: Processing stops. System action: The migration process is terminated.
User response: See previous messages issued by QMF. User response: Try to migrate the failing table again.
If the error remains, contact your IBM representative.
DRL3162I No data available in SLR V3R3 table
table name for migration. DRL3175E invalid data record in the IXF file.
Explanation: The SLR table 'tablename' did not Explanation: The IXF file created in a previous job
contain any data, and was not migrated. step contained an invalid data record.
System action: The processing continues with the next System action: The migration process is terminated.
table to be migrated.
User response: Try to migrate the failing table again.
User response: Verify that the correct SLR table was If the error remains, contact your IBM representative.
selected.
DRL3176E Input IXF file is empty.
DRL3170E Unable to allocate data set Data set name.
Explanation: The IXF file created in a previous job
Command: ALLOCATE Return code:
was empty.
return code.
System action: The migration process is terminated.
Explanation: Either the IXF file generated by a
previous job step, or the data set containing predefined User response: Verify that the SLR table is not empty.
queries cannot be allocated. Try to migrate the failing table again. If the error
remains, contact your IBM representative.
System action: The migration process is terminated.
User response: If you cannot determine why the data
DRL3177E Input query file file name is empty.
set cannot be allocated, contact your IBM
representative. Explanation: The file that contains predefined queries
used in the migration process is empty. The file was
created when Tivoli Decision Support for z/OS was
DRL3171E invalid header record in the IXF file.
installed.
Explanation: The IXF file created in a previous job
System action: The migration process is terminated.
step contained an invalid header record.
User response: Verify that the data set is empty and
System action: The migration process is terminated.
contact your IBM representative for advice.
User response: Try to migrate the failing table again.
If the error remains, contact your IBM representative.
DRL3178E Unsupported SQL data type in column
record column number.
DRL3172E invalid table record in the IXF file.
Explanation: An SLR table cannot be migrated
Explanation: The IXF file created in a previous job because it has a column with a data type that is not
step contained an invalid table record. supported in Tivoli Decision Support for z/OS. Column
number is the number of the failing column.
System action: The migration process is terminated.
System action: The migration process is terminated.
User response: Try to migrate the failing table again.
If the error remains, contact your IBM representative. User response: Do not attempt to migrate the failing
SLR table.
DRL3173E invalid column record in the IXF file.
DRL3179E No table record found in the IXF file.
Explanation: The IXF file created in a previous job
step contained an invalid column record. Explanation: The IXF file created in a previous job
step does not contain any table records.
System action: The migration process is terminated.
System action: The migration process is terminated.
User response: Try to migrate the failing table again.
If the error remains, contact your IBM representative. User response: Try to migrate the failing table again.
If the error remains, contact your IBM representative.

60 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3180E • DRL3263W

System action: Processing continues.

DRL3180E No column records found in the IXF
file. User response: None.
Explanation: The IXF file created in a previous job
step does not contain any column records. DRL3255I Table table name Module module name
Type type has number virtual columns
System action: The migration process is terminated.
Explanation: This message gives the number of virtual
User response: Try to migrate the failing table again.
columns for table table name.
If the error remains, contact your IBM representative.
System action: Processing continues.
DRL3181E No data records found in the IXF file. User response: None.
Explanation: The IXF file created in a previous job
step does not contain any data records. DRL3256I Duplicate report, report name = report
name
System action: The migration process is terminated.
Explanation: A duplicate SLR report report name was
User response: Try to migrate the failing table again.
found, and the duplicate report was not processed.
If the error remains, contact your IBM representative.
System action: Processing continues.
DRL3250I Data set data set name(member name) User response: None.
contains the following reports:
Explanation: Data set name and member name where DRL3260W No SLR reports found in data set data set
the source for the SLR report command, is located. The name(member name).
report ID is given in the next message DRL3251I.
Explanation: No SLR report commands were found in
System action: Processing continues. data set name (member name).
User response: None. System action: Processing continues.
User response: Check why there were no report
DRL3251I - report id: report ID commands in data set name (member name).
Explanation: Report-id assigned to the report
command. DRL3261W Error opening ISPF table member name,
RC = return code
System action: Processing continues.
Explanation: The SLR ISPF table member member name
User response: None.
cannot be opened.
System action: Processing continues.
DRL3252I Start processing ISPF table member name
User response: Check if the member member name is
Explanation: Processing starts for SLR ISPF table
required for migrating the report.
member member name.
System action: Processing continues.
DRL3262W Table source member member name not
User response: None. found for SLR table table name
Explanation: SLR table source member member name
DRL3253I Data set data set name with number not found for table table name.
members used for view source
System action: Processing continues.
Explanation: Data set data set name is used as source
User response: Check that the correct SLR table source
for SLR view definitions.
data set is specified.
System action: Processing continues.
User response: None. DRL3263W View source for table name not processed,
view source
DRL3254I Data set data set name with number Explanation: SLR view source for table table name was
members used for table source not processed.
Explanation: Data set data set name is used as source System action: Processing continues.
for SLR table definitions.

Chapter 1. Host Messages 61

DRL3264W • DRL3279E

User response: Check that the SLR view source for and Reference, SC34-4266, for an explanation of the table
table table name is correct. function table function and return code return code.
Correct the problem and rerun.
DRL3264W Table table name not found in file
ERMTF2 DRL3274E SLR master table contains number rows
for TABNAME=table name
Explanation: Table table name was not found in the file
ERMTF2. Explanation: Zero or more than one row was found
for table table name in SLR master table, when the
System action: Processing continues.
expected number of rows is one.
User response: Check that the SLR table name table
System action: Processing stops.
name is correct.
User response: Check that the SLR reports specify
SLR tables that exist.
DRL3265W Unable to split SELECT row for report
report ID, row = row
DRL3275E No rows in SLR COLUMNTABLE for
Explanation: A long SQL SELECT row row for report
TABNAME=table name
report ID cannot be split into two or more rows.
Explanation: Table table name was not found in the
System action: Processing continues.
SLR column table.
User response: Check the SQL query for report report
System action: Processing stops.
ID and perform a manual split of row row.
User response: Check that the SLR reports specify
SLR tables that contain columns.
DRL3270E DD-name DD name not found.
Explanation: The DD name file was not allocated in
DRL3276E SLR LIST of MASTERTABLE - Table
the JCL.
table name- RC = return code
System action: Processing stops.
Explanation: Listing of the SLR master table ended
User response: Check if file name DD name is correct. with a non-zero return code.
If correct, allocate the file. If incorrect, re-generate the
System action: Processing stops.
JCL using the Tivoli Decision Support for z/OS dialog.
User response: Look in the job log output to obtain
information about the error.
DRL3271E No SLR reports found.
Explanation: No SLR report commands were found in
DRL3277E SLR LIST of COLUMNTABLE - Table
the SLR report command source data set.
table name- RC = return code
System action: Processing stops.
Explanation: Listing of SLR column table ended with
User response: Rerun with a SLR report command a non-zero return code.
source data set containing the report commands.
System action: Processing stops.
User response: Look in the job log output to obtain
DRL3272E SLR report group group name not found
information about the error.
in ISPF table member name
Explanation: SLR report group group name was not
DRL3278E Sequence error in array sec02 detected
found in SLR ISPF table member member name.
Explanation: A sequence error was detected in array
System action: Processing stops.
sec02.
User response: Check that the specified SLR report
System action: Processing stops.
group name exists, then rerun.
User response: Delete the work files and rerun the
job.
DRL3273E Table function table function for table
table name failed, RC=return code
DRL3279E Start of SLR failed, - RC = return code
Explanation: ISPF table function table function failed
for table table name, return code is return code. Explanation: SLR failed to start, the return code is
return code.
System action: Processing stops.
System action: Processing stops.
User response: Refer to ISPF Dialog Management Guide

62 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3200I • DRL3208S

User response: Refer to Service Level Reporter Version 3: code. Correct the problem and rerun the job.
Diagnosis, LY19-6253, for an explanation of the return

Information/Management Record Creation (Exception Reporting)

Messages

DRL3200I An Info/Mgmt problem record record ID, DRL3204E If an input parameter is given, it must
generated for exception: datetime be set to a value. SYSTEM=value
description. PREFIX=value MODE=value
SHOWSQL=value APPLID=value
Explanation: An Information/Management problem
SESSMBR=value PRIVCLASS=value
record has been successfully generated.
Explanation: The call to the DRLEREGE EXEC is
System action: Processing continues.
incorrect. An input parameter is defined but is not
User response: None. assigned a value.
System action: Processing stops.
DRL3201I Information/Management session
User response: Assign a value to the input parameter.
terminated.
To use defaults, remove the input parameter.
Explanation: The session with Information/
Management has been terminated.
DRL3205E invalid input parameter parameter for the
System action: Processing stops. EXEC DRLEREGE.

User response: See previous messages issued during Explanation: The call to the DRLEREGE EXEC
processing. contains an invalid input parameter.
System action: Processing stops.
DRL3202S More than one record is returned from
User response: Correct the input parameter.
search. Search argument:
RNID_SYMBOL=record ID
DRL3206E invalid value value for MODE or
Explanation: More than one problem record returned
SHOWSQL. Valid values are valid values.
from Information/Management SEARCH for record ID.
The search was done in response to a current date Explanation: In the call to the DRLEREGE EXEC, the
change during execution of Information/Management. MODE or SHOWSQL input parameter contained an
The purpose was to retrieve the date assigned by invalid value.
Information/Management to the problem record. The
System action: Processing stops.
date of the problem record and the correspondent
exception row in the Tivoli Decision Support for z/OS User response: Correct the input parameter using one
EXCEPTION_T table need be the same. of the valid values listed in the message.
System action: The generated Information/
Management problem record is deleted. Processing DRL3207E The DRLOUT file is not allocated.
stops.
Explanation: The DRLOUT file must be allocated. All
User response: Investigate why the Tivoli Decision Support for z/OS output messages are
Information/Management SEARCH returned more than written to DRLOUT.
one record. Remove the cause of the problem and
rerun. System action: Processing stops.
User response: Allocate the file.
DRL3203W Either no exception row(s) are found in
the table table, or all exception rows are DRL3208S The problem record ID (RNID) is not
already updated in Information/ returned from Information/Management.
Management.
Explanation: Information/Management failed to
Explanation: No exception rows in the table table were return a problem record ID for the CREATE RECORD
eligible for Information/Management processing. function.
System action: Processing stops. System action: Processing stops.
User response: None. User response: Investigate why Information/

Chapter 1. Host Messages 63

DRL3209E • DRL3303I

Management failed to return a problem record ID. record is not generated.

Remove the cause of the problem and rerun.
Explanation: This is a processing failure follow up
message informing that no Information/Management
DRL3209E The input field field is flagged with problem records were generated.
error code.
System action: Processing stops.
Explanation: The message(s) are written in response to
User response: See previous message(s).
a Information/Management processing failure. The
message(s) contain Information/Management error
information. DRL3213E Unable to initialize Information/
Management.
System action: Processing stops.
Explanation: The Information/Management
User response: Use the information in the above
environment cannot be initialized. A possible reason
message(s) along with the additional error information
might be that the application ID was not found as an
written from the point of failure to determine the cause
eligible user in the privilege class.
of the Information/Management processing failure.
Correct the error and rerun. System action: This message is followed by message
DRL3214E for easier problem determination. Processing
is then terminated.
DRL3210E API timeout occurred -
Information/Management session User response: See following message(s).
terminated.
Explanation: The Information/Management session DRL3214E Information/Management error codes
was terminated by a timeout. No Information/ follow:
Management TERM function is executed.
Explanation: When an Information/Management
System action: Processing stops. transaction does not complete successfully, some
reserved REXX variables are listed after this message.
User response: See previous message(s).
These variables have been set by Information/
Management, and are listed here for easier problem
DRL3211E Unable to terminate determination.
Information/Management session.
System action: Processing stops.
Explanation: The Information/Management session
User response: Use the Information/Management
cannot be terminated.
error codes listed under this message and determine
System action: Processing stops. the cause of the error. Refer to Information/Management
API Guide and Reference, SC34-4335, for an explanation.
User response: See previous message(s).

DRL3212I An Information/Management problem

Log Data Manager Messages

These messages are issued by the log data manager.

data sets with the same log type and log ID are
DRL3301I The data set data set name was created
concatenated by the log data manager.
for the file file.
System action: The log collector is being called.
Explanation: The data set data set name was created for
the log collector output file DRLOUT or DRLDUMP. User response: None.
System action: Processing continues.
DRL3303I The log collector processed the log data
User response: None.
set data set name with return code return
code.
DRL3302I The log collector was called to process
Explanation: The log data set was successfully
these log data sets: log data sets.
collected. The return code is 0 or 4.
Explanation: This message lists which log data sets
System action: The log data set was collected.
will be processed in this call to the log collector. Log

64 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3304I • DRL3312E

User response: If the return code is 4, check DRLOUT

DRL3308E The value value is invalid for the
to find out why.
parameter parameter.
Explanation: An invalid value was specified for the
DRL3304I The file ddname file should not be
parameter to DRLELDMC.
allocated by the JCL for the
DRLELDMC EXEC. It will be ignored. System action: No log data sets were collected.
Explanation: The files DRLIN and DRLLOG are User response: Correct the parameter value.
dynamically allocated by the DRLELDMC exec. They
must not be specified in the JCL.
DRL3309E The file file containing log collector
System action: Processing continues using internally statements could not be read or is
generated DRLIN and DRLLOG files. empty.
User response: Remove the file definition from the Explanation: The file file that is specified to contain
JCL. the log collector statement for the collect of a log data
set does not exist or is empty. If the file is a partitioned
data set (PDS), the member you specified might not
DRL3305I No data sets are ready for collect.
exist.
Explanation: No log data set on the Log Data Sets To
System action: The log data set was not collected.
Be Collected list corresponds to the LOGTYPE and
LOGID parameters specified. User response: Use the log data manager dialog to
specify the required collect statement.
System action: No data sets are collected.
User response: Check the Log Data Sets To Be
DRL3310E The input parameter parameter is invalid
Collected window and the LOGTYPE and LOGID
for EXEC DRLELDMC.
parameters on the DRLELDMC call. If the parameters
are incorrect, change them. If they are correct, there are Explanation: The specified variable is not one of the
no log data sets to be collected. valid input parameters to DRLELDMC.
System action: No log data sets were collected.
DRL3306I The entry for the log data set data set
User response: Remove the parameter.
name for log type log type, that was
collected on timestamp, was purged.
DRL3311E If the input parameter parameter is
Explanation: The log data manager information about
specified, it must be set to a value.
a successfully collected data set is deleted, together
with the DRLOUT and DRLDUMP files, because the Explanation: All specified parameters must have a
specified retention period has passed and the value. No value was specified for the parameter
parameter PURGE=YES was specified on the parameter. Blank is not allowed after the equal sign.
DRLELDMC job. The collected data is not affected.
System action: No log data set was collected.
System action: Processing continues.
User response: Correct the error and run the job
User response: None. again.

DRL3307E There is no collect statement defined for DRL3312E The allocation of the filename data set
LOGTYPE logtype, LOGID logID. data set name failed. The return code is
return code.
Explanation: An attempt was made to collect a log
data set that was recorded by the log data manager as Explanation: The TSO ALLOCATE instruction failed
belonging to LOGTYPE=logtype and LOGID=logID. with return code return code when the data sets data set
However, there is no log data manager collect names were allocated to the file DRLLOG, DRLOUT, or
statement specified for this combination of LOGTYPE DRLDUMP. If the allocation of the DRLLOG file failed,
and LOGID. note that several log data sets can be concatenated into
one file. If the allocation of the DRLOUT or DRLDUMP
System action: Log data sets with this combination of
file failed, note that the name of the DRLOUT and
LOGTYPE and LOGID were not collected.
DRLDUMP data set is generated from a combination
User response: Use the log data manager dialog to of:
specify a collect statement or change the LOGID on the v The DSPREFIX high level qualifier
Data Set To Be Collected list. v A date and a time qualifier
v The string 'DRLOUT' or 'DRLDUMP'.

Chapter 1. Host Messages 65

DRL3314E • DRL3323E

This is an example of a DRLDUMP data set name: collected (with return code 0 or 4), but no record in the
DRL.D95136.T162403.DRLDUMP log was recognized.

System action: No log data sets were collected. System action: The log data set was placed on the Log
Data Sets Collected Successfully list.
User response: If DRLLOG cannot be allocated, check
the listed log data sets. If DRLOUT or DRLDUMP User response: Check why no record was recognized.
cannot be allocated, check the correctness of the It may be due to some error, even if the log data
DSPREFIX parameter. Its default value is DRL. manager registered the collect as successful. The log
data set may be of the wrong type, or it may be empty.
If you want to collect the log data set again, use the
DRL3314E The collect statement for LOGTYPE add function in the dialog, or run the DRLELDML
logtype, LOGID logID, contains the exec.
option COMMIT AFTER BUFFER FULL
ONLY, which is not allowed.
DRL3320I The log data set data set name is now
Explanation: When the COMMIT AFTER BUFFER ready for collect by the log data
FULL ONLY option is specified on the collect manager.
statement, the log collector will not report statistics on
individual concatenated log data sets. The log data Explanation: This log data set was added to the Log
manager cannot handle the result from a collect when Data Sets Ready For Collect list. It will be collected
this option is specified. when the DRLELDMC batch exec is run, depending on
the value of the LOGTYPE and LOGID parameters.
System action: The log data set was not collected.
System action: This log data set was added to the Log
User response: Remove the option from the collect Data Sets Ready For Collect list.
statement.
User response: None.

DRL3315E The log collector processed the log data

set data set name with return code return DRL3321E A log data set with the name data set
code. name and the log type log type already
exists on the To Be Collected list.
Explanation: The collect of the log data set failed.
Explanation: A log data set with the same name as the
System action: The log data set was placed on the list log data set you attempted to add is already present on
of Log Data Sets Collected With Failure. the Log Data Sets To Be Collected list for the specified
User response: To find out why the collect failed, look log type. Only one data set with the same name can
for messages about the failing log data set in the exist at the same time. However, it is possible to record
DRLOUT and DRLDUMP files using the Log Data Sets the same data set under different log type names.
Collected With Failure window. System action: No information was added.
User response: If the content of this data set is
DRL3316I The log collector did not process the log different from the already recorded data set, copy the
data set data set name. data set to a new data set with a different name.
Explanation: The log collector failed to collect a log
data set that was concatenated before this log data set. DRL3322E The value value is invalid for the
As a consequence, the log collector did not process any parameter parameter.
logs concatenated after the log in error.
Explanation: The specified value is invalid for the
System action: This log data set is left on the Log parameter to DRLELDML.
Data Sets To Be Collected list and will be collected the
next time DRLELDMC is run. System action: The log data set was not recorded in
the Log Data Sets To Be Collected list.
User response: Investigate the reason why the collect
of the previous log data set failed before DRLELDMC User response: Specify a valid value. Check the
is run again. You will find the failing log data set on Administration Guide to find out what values are valid.
the Log Data Sets Collected With Failure window.
DRL3323E Catalog information about the DRLLOG
DRL3317I The log collector processed the log data file could not be retrieved.
set data set name with return code return Explanation: The data set specified in the DRLLOG
code, but no data was collected. DD statement is not properly catalogued.
Explanation: The log data set was successfully System action: The log data set was not recorded in
the Log Data Sets To Be Collected list.

66 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL3324E • DRL3330I

User response: Catalogue the data set.

DRL3329I The parameter parameter is defined more
than once. The last definition is used.
DRL3324E The input parameter parameter is invalid
Explanation: You have specified the parameter more
for EXEC DRLELDML.
than once.
Explanation: The specified parameter is not one of the
System action: Processing continues. The last
valid input parameters to DRLELDML.
definition of the parameter was used by the log data
System action: The log data set was not recorded in manager.
the Log Data Sets To Be Collected list.
User response: Remove the parameter you do not
User response: Remove the parameter. want to use the next time this job is run.

DRL3325E If the input parameter parameter is DRL3330I No data sets are ready for cleanup.
specified, it must be set to a value.
Explanation: No log data sets on the Log Data Sets To
Explanation: All specified parameters must have a Be Collected list with status SELECT corresponds to the
value. No value was specified for the parameter LOGTYPE and LOGID parameters specified.
parameter. Blank is not allowed after the equal sign.
System action: No log data manager information
System action: The log data set was not recorded in about log data sets was changed.
the Log Data Sets To Be Collected list.
User response: Check if there is any log data set in
User response: Give the parameter a value. Valid the Log Data Sets To Be Collected window that has
values are listed in the Administration Guide. SELECT in the Status column. If so, check that the
LOGTYPE and LOGID parameters you have specified
are correct.
DRL3326E The LOGTYPE parameter is missing. It
is required.
Explanation: The LOGTYPE parameter is the only
parameter that does not have a default value. Thus,
this parameter must always be specified.
System action: The log data set was not recorded in
the Log Data Sets To Be Collected list.
User response: Specify a value.

DRL3327E The value of the input parameter

parameter starts with an apostrophe (')
which is not allowed.
Explanation: Do not enclose character strings in
apostrophes.
System action: No log data sets were collected.
User response: Remove the apostrophe.

DRL3328E The LOGTYPE log type must be defined

before any log data sets can be recorded
with that log type.
Explanation: The component that defines the log type
must be installed, or a DEFINE LOG statement must be
run, before any log data sets can be recorded for the
log type.
System action: The log data set wad not recorded in
the Log Data Sets To Be Collected list.
User response: Install the component that defines the
log type.

Chapter 1. Host Messages 67

DRL5000S • DRL5300I

Web Reporting Messages

These messages are issued by the Web Reporting application. They are found in
the Websphere Application Server error logs.

Explanation: There was an exception injecting the

DRL5000S function got null response writer.
published file.
Explanation: The function failed to get a response
System action: Web transaction terminates.
writer for transmitting information back to the client.
User response: Examine the exception stack trace for
System action: Web transaction terminates.
obvious problems, or submit logs to IBM for
User response: Forward WAS logs to IBM for investigation.
investigation.
DRL5198E function text
DRL5100E function filename is invalid: reason
Explanation: An unexpected exception occurred. This
Explanation: Filename is invalid. is a catch-all for unexpected problems.
System action: Web transaction terminates. System action: Web transaction terminates.
User response: Correct the filename then retry. User response: Forward WAS logs to IBM for
investigation.
DRL5101E function no environment variable for
variable DRL5199E function debug: text
Explanation: The specified environment variable is not Explanation: Reserved for internal use.
set.
System action: Web transaction terminates.
System action: Web transaction terminates.
User response: Report to IBM.
User response: Configure the environment variable as
per installation instructions then retry.
DRL5200W function no environment variable for
variable
DRL5102E function error opening report design
Explanation: The specified environment variable is not
filename
set.
Explanation: Cannot open the specified report design
System action: Web transaction continues, default
file.
value of variable is used.
System action: Web transaction terminates.
User response: No response necessary unless default
User response: Check whether the report design file value is incorrect.
exists. it is located under the tdszweb_designdir area.
DRL5300I text
DRL5103E function exception sending graphic
Explanation: All DRL5300I messages are for
filename
debugging purposes.
Explanation: Cannot send the specified graphic file.
System action: Web transaction continues.
System action: Web transaction terminates.
User response: If debugging is not required, set
User response: Check whether the report design tdszweb_loglevel to INFO or below.
graphic file exists.

DRL5104E function exception injecting file filename

68 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4001S • DRL4010I

Usage and Accounting Collector Messages

These messages are issued by the Usage and Accounting Collector application.
They are found in the Usage and Accounting Collector error logs.

DRL4001S pgmname ddname DD Cannot Be DRL4006W pgmname ddname DD, VSAM file not
Opened - Run Terminated, status=nn. available(wait), status=nn.
Explanation: The DD ddname cannot be opened. Explanation: The DD ddname cannot be opened
because the file is not available. The file associated with
System action: Processing stops.
DD ddname is in use by another task.
User response: Check the file associated with DD
System action: A 5 second wait is issued. Then the
ddname. Make sure that the DD has been properly
open will be attempted again. The wait will be issued a
specified in the JCL and that it matches the description
maximum on 10 times. If, after 10 attempts, the file is
in the TDSz Information Center for program pgmname.
still unavailable, processing stops.
User response: If this task does not free the file within
DRL4002S pgmname ddname DD Bad operation -
the specified time limit, processing will be terminated.
Run Terminated, status=nn.
Rerun this job when the file is no longer in use by
Explanation: An I/O operation for a file at DD another task.
ddname failed.
System action: Processing stops. DRL4007E pgmname ddname DD, invalid
operation, status=nn, Key=keydata .
User response: Check for errors in the specified data
set and retry the job. Explanation: An I/O operation for a file at DD
ddname failed. This message can result from a delete
request for data not in the file or changes to a record
DRL4003S pgmname ddname DD Bad I/O - Run that is not found
Terminated, status=nn.
System action: Processing continues.
Explanation: The file at DD ddname received an I/O
error. User response: Check that the operation requested is
valid for the information in the keydata..
System action: Processing stops.
User response: Check for errors in the specified data DRL4008S pgmname Process failed during sort
set and retry the job. phase, return code n.
Explanation: Internally invoked sort failed.
DRL4004E pgmname ddname DD Bad operation,
status=nn. System action: Processing stops.
Explanation: An I/O operation for file at DD ddname User response: Check the sort or look for other error
failed. messages.
System action: Processing continues.
DRL4009I pgmname ddname DD, operation
User response: Check for errors in the specified data successful, Key=keydata .
set and make appropriate changes to the JCL
parameters. Explanation: The requested operation was successful
for data with the matching key=keydata.

DRL4005W pgmname ddname DD, Unable to open System action: Processing continues.
VSAM file for I/O, status=nn.
User response: None.
Explanation: The DD ddname cannot be opened.
System action: Processing continues. Additional DRL4010I pgmname No match in account table for
message(s) will be issued to relay the final status of Job=jobname, Account field=data.
open processing.
Explanation: Account code conversion did not find a
User response: Look for the additional messages and match for the specified job and account data. An
proceed as they direct. informational message is issued for the first 100
no-match conditions.

Chapter 1. Host Messages 69

DRL4011I • DRL4020S

System action: Processing continues.

DRL4016W pgmname Specify the following control
User response: Use the information in these messages cards for equivalent processing:
and the exception file to improve the account code statement.
conversion match rate.
Explanation: An obsolete control statement has been
specified, see DRL4015W for the obsolete statement.
DRL4011I pgmname n Unmatched records in the
System action: Processing continues.
Account Code Conversion process.
User response: Remove the obsolete control statement
Explanation: Account code conversion did not find a
and use the replacement. Then rerun the job.
match for the specified number of records. This is an
Informational message issued at the end of processing.
DRL4017S pgmname invalid date selection:
System action: Processing continues.
fromdate todate.
User response: Use the number of unmatched records
Explanation: An invalid date selection range was
to determine the success rate of account code
specified.
conversion.
System action: Processing stops.
DRL4012S pgmname No input records were User response: Check for errors in the specified date
selected for processing. range.
Explanation: The processing requested contained no
data to process. The problem may be caused by using a DRL4018S pgmname Only 10 ACCOUNT FIELDn
date selection range for dates not found in the input control statements allowed.
data.
Explanation: Where n is a value from 0 to 9, the
System action: Processing stops. ACCOUNT FIELDn control statement can be specified
only 10 times.
User response: Check for other messages and record
counts to determine why no records were processed. System action: Processing stops.
User response: Correct the ACCOUNT FIELDn control
DRL4013E pgmname invalid Version = Version. statements and make sure that only ten statements are
entered.
Explanation: The VERSION control statement
requested an invalid version number.
DRL4019S pgmname Start and length of
System action: Processing continues.
ACCOUNT FIELDn control statements
User response: Correct the VERSION control must be numeric: statement
statement and rerun the job.
Explanation: The ACCOUNT FIELDn control
statement must contain numeric values for the starting
DRL4014W pgmname command is obsolete. position and length of field.

Explanation: The command is an obsolete control System action: Processing stops.

statement.
User response: Correct the ACCOUNT FIELDn control
System action: Processing continues. statements and rerun job.

User response: Remove the command control

statement and use the SHIFT control statements. Then DRL4020S pgmname Total length of ACCOUNT
rerun the job. FIELDn cannot exceed 80
Explanation: The ACCOUNT FIELDn control
DRL4015W pgmname Obsolete control statement: statements limit fields to an overall total length of 80
statement. bytes.

Explanation: The statement is an obsolete control System action: Processing stops.

statement.
User response: Correct the ACCOUNT FIELDn control
System action: Processing continues. statements so that the overall total length does not
exceed the limit.
User response: Remove the statement control
statement and replace it with the command contained
in the DRL4016W message.

70 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4021S • DRL4031E

User response: Contact IBM support and have the

DRL4021S pgmname invalid order for ACCOUNT
debug info available.
FIELDn control statement: statement
Explanation: The ACCOUNT FIELDn control
DRL4027S pgmname invalid parameter in control
statements must be specified in order.
statement: parameter
System action: Processing stops.
Explanation: The control statement was not valid.
User response: Correct the ACCOUNT FIELDn control
System action: Processing stops.
statement order. Start with n=0, followed by the next
higher value for n. User response: See the TDSz Information Center for
specification of the control statement. Correct the listed
parameter in the control statement and rerun the job.
DRL4022E pgmname invalid control statement:
statement.
DRL4028I pgmname No match in account code
Explanation: The control statement was not valid and
table for: data.
was not included in this execution.
Explanation: Account code conversion did not find a
System action: Processing continues.
matching entry for data.
User response: See the TDSz Information Center for
System action: Processing continues. An informational
specification of the control statement. Correct the
message issued for the first 100 no-match conditions.
control statement and rerun the job.
User response: Use the information in these messages
and the exception file to improve the account code
DRL4023I pgmname Invoking control statement:
conversion match rate.
statement.
Explanation: The above control statement will be used
DRL4029I pgmname Selection dates: fromdate
during this execution. Processing will be altered by
todate.
invoking the above control statement.
Explanation: The dates in the message will be used
System action: Processing continues.
for date selection.
User response: If this is not the desired result, the
System action: Processing continues.
trigger to this message must be removed or changed.
User response: None.
DRL4024E pgmname Call to DRLCDCTN failed,
status=nn, Key=Dictionarykey. DRL4030W pgmname Box ID error, cannot process:
ident
Explanation: The dictionary processing routine failed.
Processing continues without the dictionary file. Explanation: The BoxID processing was not able to
locate the dictionary information for ident. The default
System action: Processing continues.
dictionary definition will be used.
User response: Check for errors related to the
System action: Processing continues.
dictionary file.
User response: None.
DRL4025I pgmname Compile Date: yyyy/mm/dd
Compile Time: hh:mm:ss DRL4031E pgmname Call to DRLCDCTN failed,
status=nn
Explanation: This is an informational message that
shows the date and time of compile. This information Explanation: The BoxID processing call to
may be requested when working with IBM support. DRLCDCTN failed with a non-zero status code.
Additional messages for program DRLCDCTN may be
System action: Processing continues.
displayed.
User response: None
System action: Processing continues.
User response: Look for other error messages for
DRL4026S pgmname Logic Error, debug info
program DRLCDCTN and proceed as they direct.
Explanation: The program encountered a problem and
cannot recover.
System action: Processing stops.

Chapter 1. Host Messages 71

DRL4032S • DRL4041W

DRL4032S pgmname Error in account code DRL4037E pgmname tablename table size
conversion module DRLCTBLE. exceeded, maximum size = n
Explanation: The program encountered a problem in Explanation: An internal table has exceeded the
the account code conversion process. maximum number of entries.
System action: Processing stops. System action: Processing continues using the full
table.
User response: Look for other error messages from the
DRLCTBLE module and proceed as they direct. User response: Contact IBM support to request an
increase in the table size.
DRL4033S pgmname No Define Fields specified.
DRL4038W pgmname invalid DEFINE value for
Explanation: Account code conversion requires at least
location: location, statement.
one Define Field.
Explanation: The DEFINE control statement contains
System action: Processing stops.
an invalid argument for location. Location must be a
User response: Add a Define Field control statement numeric value between 1 and 128, inclusive.
and rerun the job.
System action: Processing continues without this
control statement.
DRL4034W pgmname type Bypassed, Offset=n
User response: Correct the invalid location argument
Length=n Ident=identdata
and rerun the job.
Explanation: The Define User Field or Box Identifier
cannot be built.
DRL4039W pgmname invalid DEFINE value for
System action: Processing continues. The dictionary length: length, statement.
entry contains offset and length values that are not
Explanation: The Define control statement contains an
valid for the data. These warning messages can occur
invalid argument for length. Length must be a numeric
as the result of normal processing and may not indicate
value between 1 and 128, inclusive.
a problem.
System action: Processing continues without this
User response: The identdata information can be used
control statement.
to identify the dictionary definitions. Use the LIMIT
DRL4034W MSG control statement to limit the number User response: Correct the invalid length argument
of warning messages such as this one. and rerun the job..

DRL4035W pgmname invalid function request: DRL4040W pgmname invalid DEFINE value
function location+length>128: location, length,
statement.
Explanation: The program was asked to perform a
function that it does not support. Explanation: The DEFINE control statement contains
an invalid combination of location and length. When
System action: Processing continues.
added together these values cannot not exceed 128.
User response: Verify that the execution library
System action: Processing continues without this
contains Usage and Accounting Collector programs
control statement.
from the same release. Then rerun the job.
User response: Correct the invalid location/length
argument and rerun the job.
DRL4036I pgmname Maximum number of input
records has been processed, MAX
INPUT n DRL4041W pgmname invalid CPU normalization
factor: statement.
Explanation: The maximum number of input records
has been processed as specified by the MAX INPUT Explanation: The CPU normalization statement
control statement. contains and invalid factor. The factor must be numeric
and can contain one decimal place.
System action: Processing continues using the input
read already read. System action: Processing continues without this
statement.
User response: Remove the MAX INPUT control
statement if you want all the input processed. User response: Correct the factor in the CPU
normalization statement and rerun the job.

72 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4042W • DRL4051W

User response: Dump the input record and determine

DRL4042W pgmname invalid Priority Surcharge.
if the data is valid. If the record is not valid, correct it
Priority must be numeric: statement.
and rerun the job.
Explanation: The Priority Surcharge statement
contains a non-numeric priority.
DRL4047S pgmname No control statements.
System action: Processing continues without this
Explanation: Process requires at least one control
statement.
statement.
User response: Correct the priority value in the
System action: Processing stops.
Priority Surcharge statement and rerun the job.
User response: Re-run the job with at least one control
statement.
DRL4043W pgmname invalid DOUBLE QUOTE
parameter, quote, double quote will be
used. DRL4048S pgmname First input card not CC1,
statement.
Explanation: The double quote replacement was not
specified correctly. The default, double quote, will be Explanation: Process requires the first control
used to separate identifiers in the CSR+ record. statement to be a CC1.
System action: Processing continues using a double System action: Processing stops.
quote for a separator.
User response: See the TDSz Information Center for
User response: See the TDSz Information Center for specification of the CC1 control statement. Rerun the
specification of the DOUBLE QUOTE control statement. job with a CC1 as the first input control statement.
Correct the DOUBLE QUOTE parameter and rerun the
job.
DRL4049S pgmname No CC2 cards input.

DRL4044W pgmname Non-numeric value found in Explanation: Process requires a CC2 control statement.
percent charge: statement. System action: Processing stops.
Explanation: A proration table statement contains a User response: See the TDSz Information Center for
non-numeric percent charge. The percentage must be a specification of the CC2 control statement. Re-run the
numeric value. job with a CC2 control statement.
System action: The percent charge is set to zero and
processing continues. DRL4050S pgmname Found non-CC2 when
User response: Use the statement to locate the entry processing CC2 control statements.
with the bad value. Correct the percent charge so that it Explanation: Control statements are in the wrong
contains a numeric value. Then rerun the job. order. A non-CC2 control statement was encountered
while processing CC2 control statements.
DRL4045S pgmname The summary file input System action: Processing stops.
appears to be a TUAM summary file.
User response: Re-run the job with the CC2 control
Explanation: This process is expecting the summary statement in the proper order.
file created by DRLCMONY. The data looks like a
TUAM summary file.
DRL4051W pgmname Device address not defined
System action: Processing stops. on CC2 input control statements.
User response: If the input file is a DRLCMONY Explanation: The CC2 control statements define a
summary file, re-run the job with a control statement: table of device addresses attached to the computer
BYPASS SERVER SUMMARY CHECK. system. A device was found that has not been defined.
System action: Processing stops.
DRL4046W pgmname invalid record type, record #
n, recordtype. User response: Re-run the job with a complete set of
CC2 control statements that define all the devices.
Explanation: The input record is not a known type.
The record will not be processed. This message is
issued for the first 25 records that have an invalid
record type.
System action: The record is dropped and processing
continues.

Chapter 1. Host Messages 73

DRL4052W • DRL4062S

processed. See the TDSz Information Center for

DRL4052W pgmname Time error, CPU > Elapsed:
information about DRLCMONY and the Calendar file.
cputime, elapsedtime, record#.
Explanation: The CPU time is greater than the elapsed
DRL4058W pgmname Duplicate rate found in rate
time. The record is dropped from processing.
file: ratetable ratecode rateindex.
System action: Processing continues without this
Explanation: A duplicate rate was found in the rate
record.
file.
User response: Perform research to see if the data
System action: Processing continues.
source produced invalid data.
User response: Use the DRLCRTLD program to delete
the duplicate entry using the DELETE command. See
DRL4053I pgmname Generic processing I/O counts
the TDSz Information Center for information about
Explanation: The generic I/O routine uses this DRLCMONY and deleting rate records.
message to show the number of records processed.
System action: Processing continues. DRL4059W pgmname Update request failed. Record
not found: recordkey.
User response: None.
Explanation: A record update failed for the specified
key because the record cannot be found.
DRL4054S pgmname invalid position value on Rate
Record: statement. System action: Processing continues.
Explanation: The Rate record position value was not User response: Look for additional messages that
numeric. explain the problem and indicate the action to take.
Take appropriate action to resolve the failure and then
System action: Processing stops.
rerun the job.
User response: See the TDSz Information Center for
DRLCMONY and rate table record layout. Correct the
DRL4060W pgmname Add request failed. Record
Rate record parameter and rerun the job.
already exists: recordkey.
Explanation: A record add failed for the specified key
DRL4055I pgmname Calendar processing
because the record was already in the file.
information
System action: Processing continues.
Explanation: This is an informational message
showing the calendar data used for this execution. User response: Look for additional messages that
explain the problem and indicate the action to take.
System action: Processing continues.
Take appropriate action to resolve the failure and then
User response: None. rerun the job.

DRL4056S pgmname Less than two records read DRL4061S pgmname Too many colons in account
from Calendar file. code table entry: entry#.

Explanation: Insufficient data in the calendar file. Explanation: The account code table contains an entry
Rebuild the calendar file. with too many colons.

System action: Processing stops. System action: Processing stops.

User response: Rebuild the calendar file using User response: Find the entry in the account code
appropriate input to reflect the time periods to be table and correct the number of colons. Rerun the job.
processed. See the TDSz Information Center for
information about DRLCMONY and the Calendar file.
DRL4062S pgmname Missing comma in account
code table entry: entry#.
DRL4057S pgmname Accounting period date not
Explanation: The account code table contains an entry
found in Calendar file.
with a missing comma.
Explanation: The accounting date was not found in
System action: Processing stops.
the Calendar file.
User response: Find the entry in the account code
System action: Processing stops.
table and add a comma at the appropriate position.
User response: Rebuild the calendar file using Rerun the job.
appropriate input to reflect the time periods to be

74 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4063I • DRL4073S

User response: Correct the DEFINE FIELDn control

DRL4063I pgmname Number of passes through
statements so the limit is not exceeded and rerun the
account code logic: n.
job.
Explanation: This is an informational message that is
issued at the end of processing.
DRL4069S pgmname Total length of DEFINE
System action: Processing continues. FIELDSn cannot exceed n.
User response: None. Explanation: The DEFINE FIELDn control statements
limit fields to an overall total length of n bytes.
DRL4064I pgmname Number of passes through System action: Processing stops.
account table: n.
User response: Correct the DEFINE FIELDn control
Explanation: This is an informational message that is statements so the overall total length does not exceed
issued at the end of processing. the limit. Then rerun the job.
System action: Processing continues.
DRL4070S pgmname Only 10 DEFINE MOVEFLDn
User response: None.
control statements allowed.
Explanation: Whenever n is a value from 1 to 10, the
DRL4065S pgmname Account code table and input
DEFINE MOVEFLDn control statement can be specified
file are out of sequence.
only 10 times.
Explanation: The account code table and the input file
System action: Processing stops.
are not in the same sort sequence.
User response: Correct the DEFINE MOVEFLDn
System action: Processing stops.
control statements and make sure that no more than
User response: Correct the sort sequence for the ten statements are entered. Then rerun the job.
account code table and input file. Rerun the job.
DRL4071S pgmname DEFINE MOVEFLDn control
DRL4066S pgmname Only 10 DEFINE FIELDn statement does not contain literal:
control statements allowed. statement.

Explanation: The DEFINE FIELDn control statement Explanation: The DEFINE MOVEFLDn control
can be specified only 10 times, where n is the value statement requested a literal replacement, but did not
from 1 to 10. include text for the replacement.

System action: Processing stops. System action: Processing stops.

User response: Correct the DEFINE FIELDn control User response: See the TDSz Information Center for
statements and make sure that only ten statements are DEFINE MOVEFLDn control statement. Correct the
entered. Then rerun the job. control statement and rerun job.

DRL4067S pgmname Start and length of DEFINE DRL4072S pgmname Start and length of DEFINE
FIELDn control statements must be MOVEFLDn control statement must be
numeric: statement. numeric: statement.

Explanation: The DEFINE FIELDn control statement Explanation: The DEFINE MOVEFLDn control
must contain numeric values for the starting position statement must contain numeric values for the starting
and length of field. position and the length of the field.

System action: Processing stops. System action: Processing stops.

User response: Correct the DEFINE FIELDn control User response: Correct the DEFINE MOVEFLDn
statement and rerun job. control statement and rerun job.

DRL4068S pgmname DEFINE FIELDn start location DRL4073S pgmname DEFINE MOVEFLDn start
+ length exceeds n: statement. location + length exceeds n: statement

Explanation: The DEFINE FIELDn control statement Explanation: The DEFINE MOVEFLDn control
contains a sum of start location and length that exceeds statement contains a sum of start location and length
the limit. that exceeds the limit.

System action: Processing stops. System action: Processing stops.

Chapter 1. Host Messages 75

DRL4074S • DRL4101W

User response: Correct the DEFINE MOVEFLDn Information Center for Account Code Conversion).
control statement so the limit is not exceeded and rerun Then rerun the job.
the job.
DRL4079W pgmname Only one SELECT or
DRL4074S pgmname Total length of DEFINE RECORD = control statement allowed:
MOVEFLDn cannot exceed n. statement.
Explanation: The DEFINE MOVEFLDn control Explanation: Only one SELECT or RECORD = control
statements limit fields to an overall total length of n statement is allowed per execution.
bytes.
System action: Processing continues without this
System action: Processing stops. control statement.
User response: Correct the DEFINE MOVEFLDn User response: Remove the control statement that is
control statements so the overall total length does not not needed. Then rerun the job.
exceed the limit. Then rerun the job.
DRL4080W pgmname Non-numeric record specified
DRL4075I pgmname DEFINE MOVEFLDn control in subsystem RECORD control
statement literal, does not start with a statement: statement.
single quotation mark: statement.
Explanation: The subsystem RECORD control
Explanation: The DEFINE MOVEFLDn control statement must specify a numeric record number.
statement must start the text literal with a single
System action: Processing continues without this
quotation mark.
statement.
System action: Processing continues.
User response: Correct the subsystem RECORD
User response: Correct the DEFINE MOVEFLDn control statement and rerun the job.
control statements and rerun job.
DRL4081W pgmname Unsupported subsystem,
DRL4076S pgmname invalid order for DEFINE release: releaseID.
FIELDn control statement: statement
Explanation: A subsystem record with an unknown
Explanation: The DEFINE FIELDn control statements release was encountered. Contact IBM support to see if
must be specified in order. support is available for the subsystem release.
System action: Processing stops. System action: Record is dropped and processing
continues.
User response: Correct the order of DEFINE FIELDn
control statements. Start with n=0, followed by the next User response: Contact IBM support to see if support
higher value for n. Then rerun the job. is available for the subsystem release.

DRL4077S pgmname DEFINE FIELDn numeric DRL4100W pgmname SMF Type 30 record has no
values must be integers: statement. subsystem section. , record skipped:
data.
Explanation: The DEFINE FIELDn control statement
numeric values must be whole integers with no Explanation: The SMF 30 record did not contain valid
decimal places. triplet information for the Subsystem Section. The
record was dropped.
System action: Processing stops.
The SMF 30 record was not formed correctly. If this
User response: Correct the DEFINE FIELDn control
error message occurs more than once, there may be a
statement and rerun job.
problem with the SMF data.
System action: Processing continues.
DRL4078S pgmname No entries in the account
code table. User response: Look for other indications of SMF
problems in the system log.
Explanation: The account code table contained no
entries.
DRL4101W pgmname invalid Job Log date
System action: Processing stops.
(SMF30RSD) record dropped: record#.
User response: Add entries to the account code table
Explanation: The SMF record did not contain a valid
or turn off account code conversion (see the TDSz
Job Log date. The record was dropped.

76 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4102W • DRL4109S

The SMF 30 record was not formed correctly. The

DRL4105W pgmname type record error, CPU time >
SMF30RSD contains an invalid value. If this error
Elapsed time: job=jobname
message occurs more than once, there may be a
step=stepname start date=sdate start
problem with the SMF data.
time=stime.
System action: Processing continues.
Explanation: The CPU time is greater than the elapsed
User response: Look for other indications of SMF time for the specified JES, STC, TSO or Step record.
problems in the system log. This warning message is issued only when requested
by the PRINT REJECTS control statement. The record is
marked with a 'Y' in the delete code; this causes the
DRL4102W pgmname The value in fieldname record to be bypassed.
exceeds internal limits: job=jobname
step=stepname program=pgmname . System action: Processing continues.

Explanation: The resource field has exceeded the User response: Perform research to see if the SMF
internal limit of a binary full word. Data was truncated data contains invalid data..
to a value of 4,294,967,295. It is possible that the
resource value is not accurate.
DRL4106W pgmname No record conversion for
System action: Processing continues. record type = n.
User response: Perform additional research to Explanation: The input record was not a known
determine if the SMF 30 record for the reported job is record type. The record was written to the
valid. If the data is valid, report the information to IBM Unsupported file.
support.
System action: Processing continues.
User response: The record is written to the
DRL4103W pgmname Record has negative CPU
CIMSUNSP DD. Review the CIMSUNSP DD to
Time or SIO Count: job=jobname
determine the type of record that was bypassed.
step=stepname start date=sdate start
time=stime.
DRL4107E pgmname External transaction record
Explanation: A negative value was found in the CPU
error: transaction.
time or SIO count field, for the specified job. This
warning message is issued for the first 100 occurrences Explanation: The external transaction failed validation.
when requested by the PRINT REJECTS control
System action: This error message is issued for the
statement. The record is marked with an 'X' in the
first 10 transactions that fail validation. Transaction is
delete code; this causes the record to be bypassed.
discarded and processing continues.
System action: Processing continues.
User response: Ensure that numeric fields are correct
User response: Perform research to see if the SMF and dates are valid. Correct problems and then process
data contains invalid data. the discarded transactions. See the TDSz Information
Center for Processing External Transactions for details.
DRL4104W pgmname type record has No CPU time
& No SIOs: Job=jobname DRL4108S pgmname Only PARSE ACCOUNT
step=stepname start date=sdate start FIELD0-9 are accepted: statement
time=stime.
Explanation: The PARSE ACCOUNT FIELDn control
Explanation: A zero value was found in the CPU time statement can be specified only 10 times, where n is
or SIO count field for the specified STC, TSO or Step values 0 through 9.
record. A warning message is issued for the first 100
System action: Processing stops.
occurrences when requested by the PRINT REJECTS
control statement. The record is marked with an 'X' in User response: Correct the PARSE ACCOUNT FIELDn
the delete code; this causes the record to be bypassed. control statements and make sure that only ten
statements are entered. Then rerun the job.
System action: Processing continues.
User response: Perform research to see if the SMF
DRL4109S pgmname Start and Length of PARSE
data contains invalid data.
ACCOUNT FIELDn control statements
must be numeric: statement
Explanation: The PARSE ACCOUNT FIELDn control
statement must contain numeric values for the starting
position and length of field.

Chapter 1. Host Messages 77

DRL4110S • DRL4118W

System action: Processing stops.

DRL4114W pgmname Account not found: statement.
User response: Correct the PARSE ACCOUNT FIELDn
Explanation: The account code was not found in the
control statement and rerun job.
client file.
System action: Processing continues.
DRL4110S pgmname Total length of PARSE
ACCOUNT FIELDn cannot exceed 59. User response: Correct the control statement to
specify a valid account code or add the account code to
Explanation: The PARSE ACCOUNT FIELDn control
the client file. Then rerun the job.
statements can define fields with an overall total length
of 59 bytes.
DRL4115I pgmname Current Year: year Current
System action: Processing stops.
Month: month
User response: Correct the PARSE ACCOUNT FIELDn
Explanation: Date information was not available in
control statements so the overall total length does not
the client file so the specified date information was
exceed the limit. Then rerun the job.
used as a default.
System action: Processing continues.
DRL4111S pgmname Total length of PARSE
ACCOUNT FIELDn output fields cannot User response: None.
exceed 128
Explanation: The PARSE ACCOUNT FIELDn control DRL4116S pgmname YEAR-END processing was
statements can define output fields with an overall total already performed.
length of 128 bytes.
Explanation: The YEAR-END processing has already
System action: Processing stops. occurred for this Client file.
User response: Correct the PARSE ACCOUNT FIELDn System action: Processing stops.
control statements so the overall total length of the
User response: If Year-End processing is still required,
output fields does not exceed the limit. Then rerun the
use the YEAR-END PURGE control statement to
job.
override this check.

DRL4112W pgmname recordID Contains an invalid

DRL4117W pgmname Update of configuration
CPUField CPU time.
information not allowed.
Explanation: The SMF30TFL field indicated that a
Explanation: The request to update the configuration
CPU field was invalid. This message is issued for the
information in the Client file is denied.
first 250 occurrences.
System action: Processing continues.
The SMF30TFL flag was properly interpreted and the
CPU field was set to zero. The SMF 30 record was User response: The requested update is not
flagged as having an invalid CPU time so it was reset supported. Remove the update request and rerun the
to prevent corruption of data. job.
System action: Processing continues.
DRL4118W pgmname Exceeded maximum size of
User response: Monitor the frequency of this warning
Alternate Account Code table: Max=n.
message, and if needed, research the SMF30TFL flag in
the SMF 30. See the TDSz Information Center for the Explanation: The maximum number of Alternate
SMF30TFL control statement. Account Codes has been loaded. No more will be
loaded for this execution.
DRL4113W pgmname Record output Location Error: System action: Processing continues.
statement.
User response: Split the Alternate Account Code file
Explanation: The control statement specified a location into smaller pieces that will not exceed the maximum.
plus length that was greater than 32. Rerun the job using 2 steps to process the input.
Include one of the smaller versions of the file with each
System action: Processing continues.
step.
User response: Correct the control statement and
rerun the job.

78 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4119I • DRL4127W

DRL4119I pgmname Local time differs from GMT DRL4123W pgmname Time error, CPU > Elapsed:
by n hours CPU Elapsed.
Explanation: The difference in time between local and Explanation: The CPU time is greater than the elapsed
GMT has been received from the CEEGMTO callable time. The elapsed time is reset to the CPU time. This
service. This value will be used to convert GMT times warning message is issued the first 10 times that the
to local times. This message is issued as a result of the conditions occurs. This message is then followed by
'SET GMT OFFSET TO SYSTEM' control statement. two 4999 messages that contain a short display of the
QWHC and QWAC sections.
System action: Processing continues.
System action: Processing continues.
User response: Perform one of the following tasks:
v If the value produced is not correct, use a 'SET GMT User response: Perform research to see if the data
OFFSET TO n' control statement to set a different source produced invalid data.
offset.
v Use default processing, and the GMT offset will be DRL4124W pgmname Triplet error: type record#
gotten from the CICS input record. offset length n
Explanation: The SMF record being processed
DRL4120E pgmname CEEGMTO failed - GMT contained an invalid triplet. The record cannot be
offset set to 0: ReturnCode processed.
Explanation: The difference in time between local and System action: The record is dropped and processing
GMT cannot be obtained from the CEEGMTO callable continues.
service. The GMT times will be used.
User response: Perform research to see if the data
This message is issued as a result of the 'SET GMT source produced invalid data.
OFFSET TO SYSTEM' control statement and a failed
call to CEEGMTO.
DRL4125W pgmname Record has negative CPU
System action: Processing continues. time.
User response: If the value produced is not correct, Explanation: A negative value was found for the CPU
perform one of the following tasks: time. Value was reset to zero. This warning message is
v Either Correct the CEEGMTO callable service or use issued for the first 100 occurrences.
the 'SET GMT OFFSET TO n' control statement. System action: Processing continues.
OR
User response: Perform research to see if the data
v Accept default processing, and the CICS input source is producing invalid data.
record will be used to determine the GMT offset.

DRL4126W pgmname ZERO CPU control statements

DRL4121W pgmname CPU Time > (Dispatch Time + exceeded limit of n entries.
80): CPU Dispatch record#
Explanation: Only n ZERO CPU control statements
Explanation: The CPU time is greater than the are supported.
dispatch time plus .00128 seconds. This warning
message issued for the first 100 occurrences. System action: Entry is ignored and processing
continues.
System action: Processing continues.
User response: Contact IBM and request additional
User response: Perform research to see if the data support for ZERO CPU control statements.
source contains invalid data.

DRL4127W pgmname DUPLICATE CPU, CICS

DRL4122E pgmname DB2 Product Section is too Attach cannot be used with ZERO CPU
long: length=n
Explanation: The DUPLICATE CPU control statement
Explanation: The DB2 Product Section has exceeded included the CICS Attach type, but the ZERO CPU
the maximum supported length of 500 bytes. control statement was also specified. This combination
System action: The record is dropped and processing is not allowed.
continues. System action: This execution was allowed, but
User response: Check for maintenance that will without the CICS Attach type in the DUPLICATE CPU
address the product section size limit. control statement.The CICS Attach is automatically
removed from the DUPLICATE CPU request and
processing continues.

Chapter 1. Host Messages 79

DRL4128W • DRL4137S

User response: Either remove the CICS Attach option User response: Look for additional messages s to
from the DUPLICATE CPU control statement or stop determine how to resolve the problem.
using the ZERO CPU control statement.
DRL4133E pgmname Dictionary file is missing
DRL4128W pgmname Only 4 Define Fields are used information: key
when Account Code Conversion is
Explanation: The dictionary processing cannot locate
turned off.
information for the dictionary key.
Explanation: No Account Code Conversion was
System action: Processing continues. Additional
requested for this execution so only the first 4 Define
messages show the type of information that was not
Fields will be used.
available with the dictionary key.
System action: Processing continues, but only 4 Define
User response: Look at the additional messages to
Fields will be used.
determine the missing information and add it to the
User response: Remove the Define Fields control dictionary. Then rerun the job.
statements that are not used.
DRL4134W pgmname Duplicate field requested:
DRL4129E pgmname Dictionary file is not fieldname outputname
available
Explanation: The field name has already been
Explanation: The dictionary file cannot be loaded to requested.
perform the required processing.
System action: Processing continues.
System action: The requested dictionary processing is
User response: Review the control statements and
bypassed, but processing continues.
remove any duplicate requests. Then rerun the job.
User response: Look for additional error messages
about the dictionary file.
DRL4135S pgmname No RESOURCE fields have
been requested.
DRL4130E pgmname BOXID not found, DEFAULT
Explanation: The results of this processing produced a
EXCEPTION: BoxID
request with no resources.
Explanation: The BoxID definition was not found in
System action: Processing stops.
the dictionary file and DEFAULT EXCEPTION has been
specified. User response: Review the control statements and
make sure that at least one resource will be in the
System action: The record written to the exception file
output file. Look for RESOURCE control statements
does not have a matching dictionary definition.
and dictionary resource flag settings.
Processing continues.
User response: Build a dictionary definition using the
DRL4136S pgmname Storage was not available:
BoxID criteria for this record. Then process the
storagesize returncode
exception file.
Explanation: The program cannot obtain the storage.
DRL4131E pgmname Dictionary file error: error System action: Processing stops.
Explanation: The dictionary file does not contain the User response: Increase the region size. Then rerun
required information. the job.
System action: The dictionary processing cannot take
place because of the reported error. Processing DRL4137S pgmname Storage was not freed:
continues. storagesize returncode
User response: Restore or rebuild the dictionary file. Explanation: The program cannot free storage.
Then rerun the job.
System action: Processing stops.

DRL4132E pgmname functioncall failed: returncode User response: Rerun the job.

Explanation: The function call failed during dictionary

processing.
System action: The dictionary processing cannot take
place. Processing continues.

80 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4138E • DRL4147W

DRL4138E pgmname Maximum number of DRL4143W pgmname Exceptiontype

command were processed: Max=n
Explanation: An input record cannot be processed and
Explanation: The command limit for the command was written to the exception file. The type of exception
has been reached. No more command will be is contained in the text of the message.
processed.
System action: Input record is written to exception file
System action: Processing continues. and processing continues.
User response: Contact IBM support to see if the limit User response: Research the exception and determine
can be increased. After the increase, rerun the job. if appropriate action was taken.

DRL4139I pgmname Sort failed after processing n DRL4144I pgmname The largest Account Code
records encounter during this run was n
characters
Explanation: An internal sort failed after n records
were processed. Explanation: The largest Account Code encounter
during this run was n characters.
System action: Processing stops.
Use the value in n for any sort steps that are needed to
User response: If the sort failed because of insufficient
sort the data by account code. Any default sort steps
resources, use the value n to set PROCESS INPUT.
will use a value of 128 characters for the account code
Decrease the value n by 10% and supply in the
length. This message is issued so that these sorts can be
PROCESS INPUT n control statement. Then rerun the
changed to use a more efficient account code length
job.
that reflects the actual data.
Multiple passes of the input will be made until the
System action: Processing continues.
entire file is processed. No additional resources will be
needed. User response: None.

DRL4140I pgmname Sort has processed n input DRL4145W pgmname The Status and Statistics file
records: sorttype is not available. All Restart/Check-point
processing will be bypassed.
Explanation: Informational sort progress message that
displays number of records that have been processed. Explanation: An attempt to open the status file failed.
All Restart/Check-point processing will be bypassed.
System action: Processing continues.
System action: Processing continues.
User response: None.
User response: If Restart/Check-point and statistical
information are to be maintained, use DRLNSTC in
DRL4141I pgmname PROCESS INPUT number of
DRL.SDRLCNTL to allocate the file for the next run.
records has been reached: n
Explanation: The number of input records specified in
DRL4146S pgmname Restart allocation failed
the PROCESS INPUT control statement has been
DSN=dsnname S99ERROR=n
reached. Processing will be completed for these input
S99INFO=n
records and than the next n number of records from the
input file will processed. Explanation: An attempt to restart the Extract
processing failed because of an allocation error on a
System action: Processing continues.
required file.
User response: None.
System action: Processing stops. Restart processing
cannot be used because a file is not available.
DRL4142I pgmname Initial Sort processed n input
User response: Rerun the job using a RESTART NO
records
control statement.
Explanation: Informational message that displays
number of records written by the initial sort.
DRL4147W pgmname Restart allocation failed
System action: Processing continues. DSN=dsnname S99ERROR=n
S99INFO=n
User response: None.
Explanation: An attempt to restart the Extract
processing failed because of an allocation error on a
required file. Restart processing cannot be used because
another file is not available. Job will continue running

Chapter 1. Host Messages 81

DRL4148S • DRL4156S

as if the RESTART NO control statement was specified.

DRL4152S pgmname Restart could not position
System action: Processing continues without Restart. DSN=dsnname, ddname status=nn

User response: None. Explanation: An attempt to restart the Extract

processing failed.
DRL4148S pgmname Restart I/O error System action: Processing stops.
DSN=dsnname copying to ddname
User response: Correct the files needed for the restart
status=nn
and rerun the job.
Explanation: An attempt to restart the Extract
Or
processing failed because of an I/O error on a required
file. Rerun the job using a RESTART NO control statement
to bypass the restart and start from the beginning..
System action: Restart processing cannot be used
because of the I/O error on the file. Processing stops.
DRL4153I pgmname Restart on DSN=dsnname
User response: Either restore the file and rerun the job
ddname skipped n records
or rerun the job using a RESTART NO control
statement to bypass the restart and start from the Explanation: Restart processing has repositioned the
beginning. starting point of the file.
System action: Processing continues.
DRL4149W pgmname Restart I/O error
User response: None.
DSN=dsnname copying to ddname
status=nn
DRL4154W pgmname Alias aliasname was not
Explanation: An attempt to restart the Extract
found
processing failed because of an I/O error on a required
file. Explanation: The requested alias member that was
mapped by the DRLMALS file in DRL.SDRLCNTL
System action: Processing continues without Restart.
cannot be found. Default processing will be used.
Restart processing cannot be used because a file access
received and I/O error. Job continues running as if the System action: Processing continues.
RESTART NO control statement had been specified
User response: Check the JCL for the proper allocation
User response: None of the alias PDS. Check the DRLMALS member in the
alias PDS and make sure the proper member was
specified. Add the alias to the PDS if required and
DRL4150W pgmname Restart failed
rerun the job
Explanation: An attempt to restart the Extract
processing failed.
DRL4155W pgmname No input to process for
System action: Processing continues without Restart. controlling dictionary key: key
User response: None. Explanation: No input to process for the dictionary
key. The initial sort contained data for the dictionary
key; but record validation, date selection and other
DRL4151S pgmname Restart failed, status=nn
processing resulted in no records being selected for
Explanation: An attempt to restart the Extract additional processing.
processing failed.
System action: Processing continues.
System action: Processing stops.
User response: Check control statements, messages
User response: Correct the files needed for the restart and reports to see why the data was not selected..
and rerun the job.
Or DRL4156S pgmname Unknown IMS Type 7 record
length: length record# .
Rerun the job using a RESTART NO control statement
to bypass the restart and start from the beginning. Explanation: An IMS type 7 record contained an
invalid length. The record may not have been formed
properly.
System action: Processing stops.
User response: Dump the input record and determine

82 Tivoli Decision Support for z/OS: Messages and Problem Determination

 DRL4157W • DRL4166S

if the data is valid. Remove the bad record from the

DRL4162S pgmname Duplicate rate record:
input file and rerun the job.
ratetable ratecode rateindex ratevalue.
Explanation: The rate file contains a duplicate entry.
DRL4157W pgmname invalid date in input: record#.
System action: Processing stops.
Explanation: The input record contained an invalid
date. The record will not be processed. User response: Process program DRLCRTRP to review
rate file. Correct the duplicate rate entry and rerun job.
System action: The record with the bad date is
See the TDSz Information Center for DRLCMONY and
dropped and processing continues.
loading the rate table.
User response: Dump the input record and determine
if the data is valid.
DRL4163S pgmname invalid rate file Release ID:
releaseID.
DRL4158W pgmname Negative resource field:
Explanation: The rate file release ID does not match
fieldname record#.
the supported values.
Explanation: The input record contained a negative
System action: Processing stops.
value in the resource field. The record will not be
processed. User response: Re-load the rate file using program
DRLCRTLD.
System action: The record is dropped and processing
continues.
DRL4164W pgmname Rate value not defined for
User response: Dump the input record and determine
Table/Rate/Shift, using shift 1: ratetable
if the data is valid..
ratecode rateshift.
Explanation: The above combination of
DRL4159W pgmname Rate code not defined in rate
Table/Rate/Shift does not have a rate value. The Shift
table: ratecode value ratetable.
will be changed to a 1 and the value associated with
Explanation: The rate code cannot be found in the this new combination will be used.
rate table. Processing for the rate code was not
System action: The shift is changed to 1 and
performed. The number in value represents the total
processing continues.
resources for the rate code.
User response: If the shift 1 value is OK, no other
System action: Processing continues.
action is required. Otherwise, define a value for the
User response: Define the rate code in the rate table. combination of ratetable/ratecode/rateshift.
See the TDSz Information Center for DRLCMONY and
loading the rate table.
DRL4165W pgmname No client configuration record
found, default to Load tracking ID =
DRL4160W pgmname Client not on master file: 1000000000.
clientkey
Explanation: The load tracking ID cannot be obtained
Explanation: The client was not found on the master from the client configuration record. The Client file
file and was not updated. may be damaged.

System action: Processing continues. System action: Processing continues. The default load
tracking ID will be used.
User response: Define the client to the master file. See
the TDSz Information Center for program DRLCCLNT. User response: Use the DRLCBDGT program to verify
that the client information is OK. Either restore the
Client file or, if necessary, rebuild the Client file. Then
DRL4161S pgmname Rate table not defined in Rate rerun the job. User does not need to rerun, unless the
file: ratetable. default load tracking ID cannot be used.
Explanation: The rate table cannot be found in the
rate file. DRL4166S pgmname Error in input: record#
System action: Processing stops. errortype.

User response: Define the rate table in the rate file. Explanation: The input record contains invalid data
See the TDSz Information Center for DRLCMONY and and cannot be properly parsed.
loading the rate table. System action: Processing stops.
User response: Dump the input record and determine

Chapter 1. Host Messages 83

DRL4167W • DRL4999I

if the data can be corrected and the file reprocessed. if the date/time is valid. If they are not valid, correct
Use the information in the error type to determine the them and rerun the job.
type of data problem.
DRL4171W pgmname invalid date in input: record.
DRL4167W pgmname REPORT DATE control
Explanation: The input record contained an invalid
statement will use report dates instead
date. The record will not be processed. The message
of actual usage dates.
contains a limited display of the input record.
Explanation: The accounting date fields will contain
System action: The record with the bad date is
the report date instead of the actual usage dates. Use
dropped and processing continues.
this option with care because it modifies the actual
usage date information with a date based on execution User response: Dump the input record ,correct the
of the Usage and Accounting Collector process. IBM date. Then rerun the job.
does not recommend using the REPORT DATE control
statement.
DRL4172W pgmname Non-numeric value in
System action: Processing continues. resource: record.
User response: Avoid using the REPORT DATE Explanation: The input record contained a
option. non-numeric value in the resource field. The record will
not be processed. The message contains a limited
display of the input record.
DRL4168W pgmname Client update turned off
because Server Mode was specified. System action: The record with the bad resource is
dropped and processing continues.
Explanation: When processing in Server Mode the
Client file cannot be updated. The CLIENT FILE User response: Dump the input record, correct the
UPDATE and PROCESS SERVER MODE control resource, and rerun the job.
statements were requested for this execution.
System action: The CLIENT FILE NOUPDATE control DRL4173S pgmname Missing or invalid SELECT
statement is used and processing continues. control statement. Correct or add the
SELECT control statement and rerun the
User response: Remove the CLIENT FILE UPDATE
job.
control statement for the next run.
Explanation: There was no SELECT control statement
to identify the subsystem.
DRL4169W pgmname CurrentCloseDate option not
found in Client file, no DEFAULT System action: Processing stops.
CLOSE DAY, Backload turned on.
User response: Correct or add the SELECT control
Explanation: The process to determine the close date statement and rerun the job.
did not find the CurrentCloseDate option in the Client
file and there was no DEFAULT CLOSE DAY specified.
The close date processing will use the BACKLOAD DRL4999I pgmname trace-data
DATA control statement. Explanation: Message was issued as the result of a
System action: The BACKLOAD DATA control trace request.
statement is used and processing continues. System action: Processing continues.
User response: If the BACKLOAD DATA control User response: None.
statement was not the proper option, either set the
CurrentCloseDate in the client file or include a
DEFAULT CLOSE DAY control statement. Then rerun
the job.

DRL4170W pgmname invalid date/time in input:

record#.
Explanation: The input record contained an invalid
date/time. The record will not be processed.
System action: The record with the bad date/time is
dropped and processing continues.
User response: Dump the input record and determine

84 Tivoli Decision Support for z/OS: Messages and Problem Determination

Chapter 2. AS/400 Messages Issued on AS/400 System
This chapter contains descriptions of AS/400 messages that are issued on the
AS/400 system during batch processing and when the log collector is invoked
from the online dialog.

Explanation: The TYPE data has been correctly

DRL000A Unable to read the requested QHST file.
captured.
Explanation: An error occurred during the reading of
System action: The command was processed.
the QHST file. An fread function returned a number of
successfully read full items that was less than the User response: None.
number of records in the file.
System action: Processing stops. DRL0002 Tivoli Decision Support for z/OS SP400
capturing of TYPE data in progress.
User response: Rerun the job. If you still get the error,
contact AS/400 system support. Explanation: The TYPE data capturing is in progress.
System action: Processing continues.
DRL000B Unable to open the requested QHST
file. User response: None.

Explanation: An error occurred during the opening of

the QHST file. An fopen function returned a NULL DRL0003 Tivoli Decision Support for z/OS SP400
pointer value. server job already active.

System action: Processing stops. Explanation: The SP400 server has already been
started and now it is active. No actions are taken if you
User response: Rerun the job. If you still get the error, try to start it again.
contact AS/400 system support.
System action: None.

DRL000C Unable to write header record to file. User response: None.

Explanation: An error occurred during the attempt to

write data into the FILE file. An fwrite function failed. DRL0004 Tivoli Decision Support for z/OS SP400
server job already in job queue.
System action: Processing stops.
Explanation: The SP400 server has already been
User response: Check to see whether the FILE file started and now it is in the job queue. No actions are
exists. Rerun the job. If you still get the error, contact taken if you try to start it again.
AS/400 system support.
System action: None.

DRL000D Maximum number of history files User response: None.

exceeded.
Explanation: The number of history files on the DRL0008 OS/400 job accounting is not active. No
system exceeds 273. The Tivoli Decision Support for accounting data can be captured.
z/OS SP400 feature can process a maximum of 273 Explanation: The OS/400 job accounting is not active.
history files.
System action: Processing stops.
System action: Processing stops.
User response: Create a journal and its receiver and
User response: Save and delete the old history files try the command again.
(WRKF QSYS/QHST*) until there are fewer than 274 of
them. Rerun the job.
DRL0009 Tivoli Decision Support for z/OS SP400
data capturing of TYPE has ended in
DRL0001 Tivoli Decision Support for z/OS SP400 error.
capturing of TYPE data has completed
normally. Explanation: The Tivoli Decision Support for z/OS

85
DRL0010 • DRL8003

SP400 data capturing of TYPE data has ended in error.

System action: Processing stops.
User response: Check the previous error messages
and try the command again.

DRL0010 Errors occurred during running of TYPE

API.
Explanation: The TYPE API invoked returned in error.
System action: Processing stops.
User response: System error.

DRL0011 No active collection.

Explanation: The STRSP400(DRLQPFR) is running on
*ACTIVE collection but there is not a collection active.
System action: Processing stops.
User response: Start Collection Services.

DRL0012 Data not within range of collection.

Explanation: The STRSP400(DRLQPFR) is running on
*ACTIVE collection with date and/or time out of range
of collection.
System action: Processing stops.
User response: Change the date and time for data
capturing or run STRSP400(DRLQPFR) to capture data
from *ALL collections present on the system.

DRL8003 Elapsed time(s): Q1 CPU use(d): Q2 Tot

AUX stg(MB): Q3 Avail AUX stg(MB):
Q4 pages: Q5 I/O reqs: Q6 Jobs Q7 Nbr
of ASP:s: Q8
Explanation: This message is produced by the SP400
monitoring job, which is activated by the STRSPSRV
SP400 command. It contains average values, computed
for a selected time interval, of performance data. It is
written into the system history log, every number of
minutes previously selected.
System action: None.
User response: None.

86 Tivoli Decision Support for z/OS: Messages and Problem Determination

Part 2. Problem Determination
Chapter 3. Host Problem Determination
Procedure . . . . . . . . . . . . . . 89
Classifying a Problem . . . . . . . . . . . 89
Using Keywords to Describe a Problem . . . . 89
Searching the Software Support Database . . . 90
Identifying Symptoms and Selecting Keywords 90
Collecting Information about Any Problem . . . . 91
Specifying Your Software Environment . . . . 91
Information Needed for All Problems. . . . . 92
Collecting Information about specific problems . . 92
System Diagnostics . . . . . . . . . . . 92
Running the Systems Diagnostics extract . . 92
Abnormal Termination (ABEND) . . . . . . 92
Message (MSG) . . . . . . . . . . . . 93
Loop (LOOP) Procedure . . . . . . . . . 94
Incorrect Output (INCORROUT) Procedure. . . 95
Performance (PERFM) Procedure . . . . . . 95
Documentation (DOC) procedure . . . . . . 95
Collecting Documentation about All Problems . . . 96
Reporting the Problem to IBM . . . . . . . . 97
Talking with a Level 1 Representative . . . . 97
Talking with a Level 2 Representative . . . . 97
Preparing Supporting Materials. . . . . . . 98
Completing a Tivoli Decision Support for z/OS
Problem Description Worksheet. . . . . . . . 98

Chapter 4. Workstation Problem Determination

Procedure . . . . . . . . . . . . . . 99
Classifying a Problem . . . . . . . . . . . 99
Information Needed for All Problems. . . . . . 99
Specifying your Hardware and Software
Environment . . . . . . . . . . . . . 99
Collecting Documentation about All Problems . . 100
Collecting Information about Specific Problems . . 101
TRAP . . . . . . . . . . . . . . . 101
Message (MSG). . . . . . . . . . . . 101
Loop (LOOP) Procedure . . . . . . . . . 101
Incorrect Output (INCORROUT) Procedure . . 102
Performance (PERFM) Procedure . . . . . . 102
Documentation (DOC) Procedure. . . . . . 102
Reporting the Problem to IBM. . . . . . . . 103
Completing the Tivoli Decision Support for z/OS
Workstation Problem Description Worksheets. . . 103

87
88 Tivoli Decision Support for z/OS: Messages and Problem Determination
Chapter 3. Host Problem Determination Procedure
This chapter helps you classify and describe problems you encounter while using
Tivoli Decision Support for z/OS. The discussions that follow can help you:
v Classify the type of problem you are having
v Collect information about a problem
v Complete the Tivoli Decision Support for z/OS problem description worksheet
v Report a problem to IBM

The procedures in this chapter describe how you select keywords and build a
symptom string to obtain documentation about the problem. The symptom string
and related documentation will help you discover whether the problem has
occurred before, or help you accurately describe the problem if you must contact
IBM service personnel.

Note: Use the information in this chapter to record all applicable facts about the
problem on the worksheet provided (Appendix C, “Problem Description Worksheet
for the Host,” on page 119).

Classifying a Problem
The first step in diagnosis is classifying the type of problem. Symptoms that
indicate the presence of a problem can be valuable clues in diagnosing and solving
the problem.

Using Keywords to Describe a Problem

Keyword string

A keyword is a word, acronym, or abbreviation used to describe one aspect of a

program failure. Use keywords to describe all aspects of a problem, from
identifying the Tivoli Decision Support for z/OS program number to identifying
the area of failure. Use the appropriate procedures to document the problem and
build a keyword string.

For example, if your Tivoli Decision Support for z/OS program terminates with a
system abend code, the keyword is ABEND. Other keywords are also formed to
describe particular aspects of the abnormal termination, such as the name of the
module where the abend occurred. You then combine these keywords to form a
keyword string like this:
569510100 R101 ABEND0C4 DRLPLOPR

In this example, 569510100 is the component ID (5695-101 is the Tivoli Decision

Support for z/OS program number), R101 identifies the release number, ABEND is
the type of problem, and 0C4 is the abend code. DRLPLOPR is the module where
the abend occurred.

The component ID is the first keyword in the string. It identifies the IBM licensed
program that failed.

The name of the module that abended can be found in the DRLDUMP data set
(described in Appendix A, “Dump File Content and Trace Options,” on page 107).

89
Classifying a Problem

The last three digits of the FMID show the release numbers for the Tivoli Decision
Support for z/OS features. They are:
Table 1. Tivoli Decision Support for z/OS Features
Component name Common English German Japanese
Base 201 2B2 2B0 2B1
System Performance 2A0 2C2 2C0 2C1
IMS Performance 2A1 2D2 2D0 2D1
CICS Performance 2A2 2E2 2E0 2E1
Network Performance 2A3 2F2 2F0 2F1
Workstation Performance 2A4 2G2 2G0 2G1
SP400 2A5 2H2 2H0 2H1
Resource Accounting for 2A8 2L2 2L0 2L1
z/OS

Searching the Software Support Database

Use the keyword string you create to search the software support database. This
helps you find out if the problem has been noted before. If a problem described in
the database is similar to yours, a solution is probably available. You can vary your
keyword string to widen or narrow the database search.

If you have the Information/Access IBM licensed program, you can use your
keyword string to search the RETAIN database for solutions to problems similar to
yours. IBM level 1 service personnel can help you develop the keyword string and
search the database for a similar problem. If the RETAIN database is not available
to you, the IBM support center will help you solve your problem.

Identifying Symptoms and Selecting Keywords

Look in Table 2 to find the symptoms that most closely match the symptoms you
are experiencing. Make a note of all the keywords that describe those symptoms.

Note: If your symptoms do not appear in Table 2, collect the information needed
for all problems as described in “Collecting Documentation about All Problems” on
page 96.
Table 2. Identifying Symptoms
Symptom Problem-type Keyword
v Abend message. ABEND
v Dump file contains a formatted dump.
v Application program reports an unexpected
return code.
v Unexpected output results. INCORROUT
v Tivoli Decision Support for z/OS does not
work as specified in a book.
v DRL message is wrong or is formatted
improperly.
v Heavy processor consumption without any LOOP
output on output file DRLOUT.
v A message repeats continuously.

90 Tivoli Decision Support for z/OS: Messages and Problem Determination

 Classifying a Problem

Table 2. Identifying Symptoms (continued)

Symptom Problem-type Keyword
v DRL error message. MSG
v DRL message is wrong or is formatted
improperly.
v Message text does not explain the problem
condition.
v Performance does not meet explicitly stated PERFM
expectations.
v Response time is slow.
v Tivoli Decision Support for z/OS publication DOC
library does not match actual Tivoli Decision
Support for z/OS operation.
v Missing, incorrect or ambiguous information
in the documentation.

Collecting Information about Any Problem

This section contains procedures for collecting specific types of information, and
for collecting information about an unidentified problem.

Make a copy of the worksheet in Appendix C, “Problem Description Worksheet for

the Host,” on page 119 and use it to document information related to the problem
you are having.

It is very important to completely document a problem before calling IBM for

assistance.

Specifying Your Software Environment

Specify the software in use when the problem occurred:
MVS Indicates the version, release, and modification level of MVS.
TSO Indicates the version, release, and modification level of TSO/E.
ISPF Indicates the version, release, and modification level of ISPF.
DB2 Indicates the version, release, and modification level of DB2.
QMF Indicates the version, release, and modification level of QMF.
GDDM
Indicates the version, release, and modification level of GDDM.
C Indicates the version, release, and modification level of C compiler
(applicable only if exit procedures written in C have been added)

Specify the systems that created the logs in the last collect run (IMS, CICS, RMF™,
or some other system). Indicate the version, release, and modification level of each
system.

If you need more information, an IBM support center representative can help you
gather it.

Chapter 3. Host Problem Determination Procedure 91

Collecting Information about Any Problem

Information Needed for All Problems

The information needed by IBM support personnel depends on whether the
problem is with batch or with the dialog.

For problems with batch, be prepared to provide:

v JCL messages
v The DRLOUT file
v The DRLDUMP file
v The log data set, if applicable

For problems with the dialog, be prepared to provide:

v Dialog messages
v A description of steps performed
v The tsoprefix.DRLOUT data set
v The tsoprefix.DRLDUMP data set

Collecting Information about specific problems

The sections that follow outline procedures for gathering information about specific
types of problems. If you cannot classify your problem, use the procedure in
“Collecting Documentation about All Problems” on page 96.

The DRLOUT data set contains the DRLIN statements (if default
SHOWINPUT=YES is kept) and messages generated by the log collector.

The DRLDUMP data set contains abend dumps, additional information about
records skipped and data columns set to null in a collect or list operation. It also
contains output from any traces activated. For more information about the contents
of the DRLDUMP data set and how log collector traces are activated, see
Appendix A, “Dump File Content and Trace Options,” on page 107.

System Diagnostics
The System Diagnostics function is used to take a snapshot of various system
tables. This is achieved by extracting data from the Tivoli Decision Support system
tables. The data is written to a sequential file called tsoprefix.DRLDIAG. If the file
has not been allocated, the Systems Diagnostic feature will allocate it when it is
executed.

The main purpose of this function is to provide IBM support personnel with an
overview of the components and subcomponents that have been installed. This
information can be useful when working on faults. Information about the log data
sets that have been collected is also extracted.

Running the Systems Diagnostics extract

The System Diagnostics feature can be executed by selecting option 4 from the
Utilities drop-down menu from the Administration panel. This executes in online
mode and the extracted data is written to the tsoprefix.DRLDIAG data set. This
data set is sent to IBM support personnel, on their request.

Abnormal Termination (ABEND)

If Tivoli Decision Support for z/OS comes to an abnormal end, use the ABEND
keyword to document the problem—regardless of whether it is a user abend or a
system abend. (If the program issues a message, you can also use the MSG
keyword.)

92 Tivoli Decision Support for z/OS: Messages and Problem Determination

 Collecting Information about Specific Problems

Tivoli Decision Support for z/OS typically produces a system dump for an abend;
however, if no dump is produced, the dump file may be full, in which case the
abend must be recreated with a larger dump file. Check for a message that an
error occurred while Tivoli Decision Support for z/OS was trying to produce a
dump. A symptom string in the dump provides information on what was
happening at the time of the abend.

Follow this procedure to produce a system dump:

1. Allocate the SYSMDUMP ddname to a data set with the following DCB
parameters:
v The dump data must be stored on a data set with sequential (PS)
organization.
v The logical record length (LRECL) must be 4160 bytes.
v The data set must have one of the following combinations of record format
(RECFM) and block size (BLKSIZE):
– RECFM=F,BLKSIZE=4160
– RECFM=FB,BLKSIZE=4160
– RECFM=FBS,BLKSIZE=n*4160 where n=1,2,...
If the data set meets these criteria, IPCS provides special purpose processing. In
special purpose processing, IPCS simulates system services, such as dynamic
address translation and control block formatting, when processing the
information source.

Note: The DCB for SYSMDUMP can be different for different MVS versions.
2. If the abend occurred in an ISPF dialog, you must also do this:
a. Allocate the SYSMDUMP data set with DISP=MOD. (If Tivoli Decision
Support for z/OS abends first, and then ISPF, both will write to the
SYSMDUMP data set. If you use DISP=SHR, only the ISPF dump will be
seen.)
b. Set the ISPF options in ISPF 0.7 to ENBLDUMP=ON.
3. Recreate the abend.
When you see TSO READY after ISPF has terminated, press Enter. A dump will
be produced.

Note: It is important that you do not press any other key than Enter.

Collect the information listed in “Information Needed for All Problems” on page
92 and read “Collecting Documentation about All Problems” on page 96 to
complete your documentation of the problem. Also, if FFST is installed and used,
produce an FFST data dump. For more information, see “First Failure Support
Technology” on page 113.

Message (MSG)
Use the MSG keyword to specify a message failure. Do this when:
v A message describes conditions that do not apply to actual Tivoli Decision
Support for z/OS operation.
v The text of a message is incorrect.
v Tivoli Decision Support for z/OS issues an Tivoli Decision Support for z/OS
message (a message with the DRL prefix), but the message is not documented or
is not documented correctly in Chapter 1, “Host Messages,” on page 3.
v The message precedes an abend.

Chapter 3. Host Problem Determination Procedure 93

Collecting Information about Specific Problems

If the message associated with the problem does not have the DRL prefix, it is
probably not a Tivoli Decision Support for z/OS message failure, so do not use the
MSG keyword. In some cases, you might want to use the INCORROUT keyword
in addition to the MSG keyword. For example:
v When a message describes conditions that do not apply to the actual program
operation
v When no message text appears
v When message text appears to contain incorrect data
v When the program issues a message under inapplicable conditions

For more information about the INCORROUT keyword, see “Incorrect Output
(INCORROUT) Procedure” on page 95.

To describe a message problem:

1. Look up the message in Part Part 1, “Messages,” on page 1 for an explanation.
The message description includes information on what action Tivoli Decision
Support for z/OS takes and what action you must take in response to the
message.
If you plan to report the problem, gather and record the appropriate
information before you take recovery action.
2. Write down the message identifier and the exact message text. If you contact
IBM for assistance, the support center representative will require the exact
message text.
3. Supplement the MSG keyword with the message identifier. You will use the
supplemented keyword when searching the software support database.
In this sample, DRL is the message prefix, identifying a Tivoli Decision Support
for z/OS message, 0992 is the message number, and S is the severity code.

Read “Collecting Documentation about All Problems” on page 96 to complete your

documentation of the problem.

Loop (LOOP) Procedure

Use the LOOP keyword to document any of these symptoms:
v Part of a program repeats itself.
v An Tivoli Decision Support for z/OS command does not complete after the
expected time.
v Processor usage is at much higher than typical levels.

Note: If new output is being produced on the DRLOUT file, Tivoli Decision
Support for z/OS is not in a loop.

Loop problems can involve many modules or a single module. Determine whether
any messages are associated with the loop, such as a particular message always
preceding the problem.

If the problem type is a loop, collect a dump of the Tivoli Decision Support for
z/OS address space that is looping in addition to what is listed in “Information
Needed for All Problems” on page 92.

Read “Collecting Documentation about All Problems” on page 96 to complete your

documentation of the problem.

94 Tivoli Decision Support for z/OS: Messages and Problem Determination

 Collecting Information about Specific Problems

Incorrect Output (INCORROUT) Procedure

Use the INCORROUT keyword to document a problem when any of these
symptoms appear:
v Unexpected output results.
v Output appears to be incorrect or incomplete.
v Output formats incorrectly.

Most incorrect output problems are due to improperly formatted user data, or
other types of missing or incorrect data.

If the problem type is incorrect output:

1. Specify the type of output that is incorrect.
2. Specify how the output differs from what was expected.
v Is all or part of the output missing?
v Is all or part of the output incorrect?
v Is the output duplicated?
v Is there more output than expected?

Note: Sometimes problems with other licensed programs or exit procedures can
generate incorrect output.
3. Specify if any tables, reports, or update definitions have been modified.
Consider objects that might have a connection with the incorrect output.
4. Read “Collecting Documentation about All Problems” on page 96 to complete
your documentation of the problem.

Performance (PERFM) Procedure

Use the PERFM keyword to document any of these symptoms:
v Processing of Tivoli Decision Support for z/OS events or commands (including
commands entered from a terminal in session with Tivoli Decision Support for
z/OS) takes an excessive amount of time to complete.
v Tivoli Decision Support for z/OS performance characteristics do not meet
explicitly stated expectations.

Note: Before reporting a performance problem with collect, consult the section
about collect performance in the Administration Guide. It describes factors that affect
performance and ways to improve collect performance.

If the problem type is performance, document the actual performance, the expected
performance, and the source of information about the expected performance. If a
document is the source, note the order number and page number of the document.

Read “Collecting Documentation about All Problems” on page 96 to complete your

documentation of the problem.

Documentation (DOC) procedure

Use the DOC keyword when either of these symptoms appears:
v The Tivoli Decision Support for z/OS product library contains incomplete or
inaccurate information about Tivoli Decision Support for z/OS installation,
operation, customization, messages, or service.
v Published descriptions of Tivoli Decision Support for z/OS disagree with
operational experience.

Chapter 3. Host Problem Determination Procedure 95

Collecting Information about Specific Problems

Note: Report a documentation problem only when it meets one or more of the
criteria listed. For suggestions or comments about the documentation, use the
reader’s comment form at the back of the applicable book.

If the problem type is documentation:

1. Identify the order number of the book that contains the inaccurate information.
The order number appears on the back cover of the book in the form
xxxx-xxxx-yy, where yy is a two-digit revision code. (Include the revision code if
it appears.)
If you are reporting inaccurate information contained in a technical newsletter
(TNL), identify the TNL number. The TNL number appears at the top of any
page in the TNL in the form xxxx-xxxx.
If you are reading a book online with BookManager®, you can find information
about the book number by selecting Describe from the BookManager menu bar.
When reporting a problem, include the topic number and heading.
2. Indicate all pages in the document that contain incorrect or incomplete
information.
3. Prepare a description of the problem that was caused by the incorrect or
incomplete information.
4. Read “Collecting Documentation about All Problems” to complete your
documentation of the problem.

To describe a problem with online help:

1. Type panelid on on the command line to display panel IDs.
2. Indicate the panel ID of the panel that contains the incorrect or incomplete
information.
3. Prepare a description of the problem that was caused by the incorrect or
incomplete information.
4. See “Collecting Documentation about All Problems” to complete the required
documentation.

Collecting Documentation about All Problems

Gather as much relevant information for any problem you encounter, even when
you cannot identify the type of problem. Record the information on a copy of the
checklist in “Completing a Tivoli Decision Support for z/OS Problem Description
Worksheet” on page 98.
1. Record the Tivoli Decision Support for z/OS component ID—569510100. The
component ID is the first keyword in the string, preceding the problem type
and other modifier keywords.
2. Record the release number for the feature (see Table 1 on page 90).
3. Record the maintenance level—the program update tape (PUT) level or, if
applicable, the custom-built program delivery offering (CBPDO) level.
4. Document any additional program temporary fixes (PTFs) or authorized
program analysis reports (APARs) that have been applied to your level of Tivoli
Decision Support for z/OS.
5. Reconstruct the sequence of events leading to the problem. Include any
commands entered just before the problem occurred. Write down the exact
scenario that led to the problem. Answer these questions:
v What were you trying to do?
v What did you expect to happen?
v What did happen?

96 Tivoli Decision Support for z/OS: Messages and Problem Determination

 Collecting Documentation about All Problems

v Can you recreate the problem?

6. Select the problem area that best fits the symptoms of your problem from those
listed under “Identifying Symptoms and Selecting Keywords” on page 90 and
write down the supplementary information required.
7. Specify your software environment according to “Specifying Your Software
Environment” on page 91.
8. Specify any unique information about the problem or about your system. For
example:
v Indicate any other applications that were running when the problem
occurred.
v Describe all user modifications to any active Tivoli Decision Support for
z/OS programs.

Reporting the Problem to IBM

To resolve some problems, you may need assistance from IBM support personnel.
When you contact IBM for help, the support representative will ask for your
account name and other customer identification, then a brief description of the
problem.

You can increase the effectiveness of your call by preparing a string of keywords
that describe the problem. Collecting the relevant documentation, such as message
logs and checkpoint files, as well as noting software and hardware levels, also
helps the representative to identify how the problem occurred. The support
representative can then find out more quickly whether the problem has been
reported before and locate a solution, or refer your problem to a higher level of
support personnel.

Talking with a Level 1 Representative

The IBM Level 1 representative asks you to describe your problem. The problem
description worksheet (see Appendix C, “Problem Description Worksheet for the
Host,” on page 119)contains most of the required information. The representative
uses the information to form a symptom string and search the RETAIN database.
The representative might ask you for more information to produce other keywords
to aid in the search.

If the search does not produce a solution to the problem, the representative ensures
that you have the necessary information to discuss the problem with a program
specialist. At this point, your call is placed on a queue for a program specialist,
also known as a level 2 support center representative.

Talking with a Level 2 Representative

To refine the keywords, the IBM Level 2 representative asks you for more
information. Using the refined keyword, the representative performs additional
searches of the database. If these searches do not produce a solution and the
problem is new, the representative may enter an authorized program analysis
report (APAR) into the support center database.

The level 2 representative assigns a number to your APAR. If you send IBM
documentation about your problem, write this APAR number in the upper-right
corner of each piece of documentation, and on the external label of each tape.

The APAR and any helpful documentation you send to IBM allow a program
specialist to examine the problem in greater detail. If the solution requires a coding

Chapter 3. Host Problem Determination Procedure 97

Reporting the Problem to IBM

change, it is put into a temporary fix (PTF) and then sent to you. All information
about the solution is entered into the RETAIN database. This procedure keeps the
database current with problem descriptions and solutions. The information is then
available for future RETAIN searches.

Preparing Supporting Materials

Keep all materials that show that the program does not work properly and present
them on request.

The material required is listed in “Collecting Information about Any Problem” on

page 91, in “Collecting Information about specific problems” on page 92, and in
“Collecting Documentation about All Problems” on page 96.

To speed up the handling of your problem, keep as much information as possible

in machine-readable form.

Completing a Tivoli Decision Support for z/OS Problem Description

Worksheet
The Tivoli Decision Support for z/OS problem description worksheet shown in
Appendix C, “Problem Description Worksheet for the Host,” on page 119
summarizes the information discussed in this chapter and serves as a checklist for
recording all applicable facts about a problem. The combination of the information
in this checklist and a symptom string helps you describe the problem accurately
to IBM service personnel.

98 Tivoli Decision Support for z/OS: Messages and Problem Determination

Chapter 4. Workstation Problem Determination Procedure
This chapter helps you classify and describe problems you encounter when using
these features of Tivoli Decision Support for z/OS:
v Workstation Performance feature
v AS/400 System Performance feature (AS/400 featureAS/400 feature)
The discussions that follow can help you:
v Classify the type of problem you are having
v Collect information about a problem
v Complete the appropriate problem description worksheet, which you can find
on pages Appendix D, “Problem Description Worksheet for the Workstation
Performance Feature,” on page 123 through Appendix E, “Problem Description
Worksheet for the AS/400 System Performance Feature,” on page 127.
v Report a problem to IBM

To some extent, the problem determination and reporting procedure is similar or

identical with the procedure used on the host. When this is the case, there will be a
reference to the corresponding section in Chapter 3, “Host Problem Determination
Procedure,” on page 89.

For more information, refer to

v Distributed Systems Performance Feature Guide and Reference, SH19-4018
v AS/400 System Performance Feature Guide and Reference, SH19-4019
v Problem Determination Guide for the Service Coordinator, S04G-1006

Classifying a Problem
See the information under “Classifying a Problem” on page 89.

Information Needed for All Problems

This section contains procedures for collecting specific types of information, and
for collecting information about an unidentified problem.

Make a copy of the relevant worksheet (on pages Appendix D, “Problem

Description Worksheet for the Workstation Performance Feature,” on page 123
through Appendix E, “Problem Description Worksheet for the AS/400 System
Performance Feature,” on page 127) and use it to document information related to
the problem you are having.

It is very important to completely document a problem before calling IBM for

assistance.

Be prepared to provide:
v Information about what you were doing
v Any dialog messages

Specifying your Hardware and Software Environment

Be prepared to provide information on the hardware configuration:
v Machine type and model

99
Information Needed for All Problems

v Screen type and resolution used

v Processor
v Memory

Specify the software in use when the problem occurred, including information
about version, release and modification level. This information can typically be
found on the help pull-down, under the Product Information or About options.

For the Workstation Performance featureWorkstation Performance feature:

v AIX
v TCP/IP
v Host Support File Transfer Program
v AIX SNA Services/6000
v AIX Host Connection Program/6000

For AS/400 System PerformanceAS/400 System Performance:

v Operating System/400® (OS/400)
v NetView® FTP
v NetView FTP/400
If you need more information, an IBM support center representative can help you
gather it.

Collecting Documentation about All Problems

Gather as much relevant information for any problem you encounter, even when
you cannot identify the type of problem. Record the information on a copy of one
of the checklists on pages Appendix D, “Problem Description Worksheet for the
Workstation Performance Feature,” on page 123 through Appendix E, “Problem
Description Worksheet for the AS/400 System Performance Feature,” on page 127.
1. Record the Tivoli Decision Support for z/OS component ID—569510100—and
release number.
2. Record the version, release, and modification levels.
3. Reconstruct the sequence of events leading to the problem. Include any
commands entered just before the problem occurred. Write down the exact
scenario that led to the problem. Answer these questions:
v What were you trying to do?
v What did you expect to happen?
v What did happen?
v Can you recreate the problem?
4. Select the problem area that best fits the symptoms of your problem from those
listed under “Identifying Symptoms and Selecting Keywords” on page 90 and
write down the supplementary information required.
5. Note the information described in “Specifying your Hardware and Software
Environment” on page 99.
6. Specify any unique information about the problem or about your system. For
example:
v Indicate any other applications that were running when the problem
occurred.
v Describe all user modifications to any active Tivoli Decision Support for
z/OS programs.

100 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Collecting Information about Specific Problems

Collecting Information about Specific Problems

The sections that follow outline procedures for gathering information about specific
types of problems. If you cannot classify your problem, use the procedure in
“Collecting Documentation about All Problems” on page 100.

TRAP
If your feature comes to an abnormal end, a TRAP screen will appear. Report what
you were doing, and that this action resulted in a TRAP condition.

Message (MSG)
Use the MSG keyword to specify a message problem. Do this when:
v A message describes conditions that do not apply to actual Tivoli Decision
Support for z/OS operation.
v The text of a message is incorrect.
v Tivoli Decision Support for z/OS issues an Tivoli Decision Support for z/OS
message but the message is not documented or is not documented correctly.
v The message precedes an abend.
In some cases, you may want to use the INCORROUT keyword in addition to the
MSG keyword. For example:
v When a message describes conditions that do not apply to the actual program
operation
v When no message text appears
v When message text appears to contain incorrect data
v When the program issues a message under inapplicable conditions

For more information about the INCORROUT keyword, see “Incorrect Output
(INCORROUT) Procedure” on page 102.

To describe a message problem:

1. Look up the message in the help. The message description includes information
on what action the feature takes and what action you must take in response to
the message. If you plan to report the problem, gather and record the
appropriate information before you take recovery action.
2. Write down the message identifier and the exact message text. If you contact
IBM for assistance, the support center representative will require the exact
message text.

Read “Collecting Documentation about All Problems” on page 100 to complete

your documentation of the problem.

Loop (LOOP) Procedure

Use the LOOP keyword to document any of these symptoms:
v Part of a program repeats itself.
v A Tivoli Decision Support for z/OS command does not complete after the
expected time.
v Processor usage is at much higher than typical levels.

Loop problems can involve many modules or a single module. Find out whether
any messages are associated with the loop, such as a particular message always
preceding the problem.

Chapter 4. Workstation Problem Determination Procedure 101

Collecting Information about Specific Problems

Read “Collecting Documentation about All Problems” on page 100 to complete

your documentation of the problem.

Incorrect Output (INCORROUT) Procedure

Use the INCORROUT keyword to document a problem when any of these
symptoms appear:
v Unexpected output results.
v Output appears to be incorrect or incomplete.
v Output formats incorrectly.

Most incorrect output problems are due to improperly formatted user data, or
other types of missing or incorrect data.

If the problem type is incorrect output:

1. Specify the type of output that is incorrect.
2. Specify how the output differs from what was expected.
v Is all or part of the output missing?
v Is all or part of the output incorrect?
v Is the output duplicated?
v Is there more output than expected?

Note: Sometimes problems with other licensed programs can generate incorrect
output.
3. Specify if any tables, reports, or update definitions have been modified.
Consider objects that might have a connection with the incorrect output.
4. Read “Collecting Documentation about All Problems” on page 100 to complete
your documentation of the problem.

Performance (PERFM) Procedure

Use the PERFM keyword to document any of these symptoms:
v Processing of Tivoli Decision Support for z/OS events or commands (including
commands entered from a terminal in session with Tivoli Decision Support for
z/OS) takes a lot of time to complete.
v Tivoli Decision Support for z/OS performance characteristics do not meet
explicitly stated expectations.

If the problem type is performance, document the actual performance, the expected
performance, and the source of information about the expected performance. If a
document is the source, note the order number and page number of the document.

Read “Collecting Documentation about All Problems” on page 100 to complete

your documentation of the problem.

Documentation (DOC) Procedure

Use the DOC keyword when either of these symptoms appears:
v The Tivoli Decision Support for z/OS product library contains incomplete or
inaccurate information about Tivoli Decision Support for z/OS installation,
operation, customization, messages, or service.
v Published descriptions of Tivoli Decision Support for z/OS disagree with
operational experience.

102 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Collecting Information about Specific Problems

Note: Report a documentation problem only when it meets one or more of the
criteria listed. For suggestions or comments about the documentation, use the
reader’s comment form at the back of the applicable book.

If the problem type is documentation:

1. Identify the order number of the book that contains the inaccurate information.
The order number appears on the back cover of the book in the form
xxxx-xxxx-yy, where yy is a two-digit revision code. (Include the revision code if
it appears.)
If you are reporting inaccurate information in a technical newsletter (TNL),
identify the TNL number. The TNL number appears at the top of any page in
the TNL in the form xxxx-xxxx.
If you are reading a book online with BookManager, you can find information
about the book by selecting Describe from the BookManager menu bar. When
reporting a problem, include the topic number and heading.
2. Indicate all pages in the document that contain incorrect or incomplete
information.
3. Prepare a description of the problem that was caused by the incorrect or
incomplete information.
4. Read “Collecting Documentation about All Problems” on page 100 to complete
your documentation of the problem.

See “Collecting Documentation about All Problems” on page 100 to complete the
required documentation.

Reporting the Problem to IBM

See the information under “Reporting the Problem to IBM” on page 97.

Completing the Tivoli Decision Support for z/OS Workstation Problem

Description Worksheets
The problem description worksheets on pages Appendix D, “Problem Description
Worksheet for the Workstation Performance Feature,” on page 123 through
Appendix E, “Problem Description Worksheet for the AS/400 System Performance
Feature,” on page 127 summarize the information discussed in this chapter and
serve as checklists for recording all applicable facts about a problem.

Chapter 4. Workstation Problem Determination Procedure 103

104 Tivoli Decision Support for z/OS: Messages and Problem Determination
Part 3. Appendixes

105
106 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix A. Dump File Content and Trace Options
This section contains diagnosis, modification, or tuning information for the log
collector.

This appendix describes

v The contents of the DRLDUMP data set
v How to activate traces

Information in the Dump File

The dump file contains information gathered during abend or error situations
processing. The dump file is allocated to the DRLDUMP data set. The dump file
output is mainly of these types:
v Abend information
v Trace information
v Record or row reject information
v Error situations recording

Abend Information
The abend information is produced when an abend, system or user, occurs. The
abend information contains these parts:
v Termination cause
v Module stack
v Register content
v Error data items

Termination Cause
The termination cause gives information on the abend type. Tivoli Decision
Support for z/OS differs between:
v Abnormal termination
Abnormal termination is used when the abend is not of the program check or
program error type (see below). The abend code is given. If the abend is due to
internal stack memory limitation the text is replaced by Dynamic storage limit
exceeded. If the abend is due to a missing or invalid Tivoli Decision Support for
z/OS service function the text is replaced by Server absent or not
initialized. If the abend is due to an error in the program check service routine
the text is replaced by Program check in program check handler.
v Program check
Program check is used when an 0Cx abend is encountered. The program check
type is given in plain text.
v Program error
Program error is used when the abend is triggered as a result of a program
failure. The program error supplies an identifier showing the point where the
abend was invoked.

This part also gives information on

v Abending module name
v Abending module address
v Abend instruction offset in the abending module

107
Information in the Dump File

Optionally, for program checks, 16 bytes of instruction code from the abend
instruction offset are given.

Module Stack
The module stack shows the path of modules, from the one executed (normally
DRLPLC), leading up to the abend module. For each module, the address of the
module and the call offset to the next module in the path, is shown.

Register Content
The register content part shows the content of the general and float registers at the
point of abend. This part also shows the latest call (in the form of a R14 offset) in
the abending module, if applicable.

Error Data Items

If the abend type is program error, the error data items part might be included.

User Abend Codes

The Tivoli Decision Support for z/OS log collector issues these user abend codes:
U0001 Dynamic storage exceeded
U0002 Program error or system abend
U0003 Program error in basic service routines
U0004 Program check in the program check handler
U0005 A GETMAIN for virtual storage failed
U0016 Non-program error termination:
v DRLOUT or DRLDUMP not available
v SQL timeout (lock contention)
v SQL duplicate keys (GROUP BY columns different from key columns)

Note: Diagnostics for codes U0001 and U0002 are written to DRLDUMP.
Diagnostics for codes U0003 and U0004 might be written. No diagnostics are
written to DRLDUMP for code 0016; instead, a message tells you what occurred.
When code 0005 occurs detailed information is written to the DRLDUMP data set.
Specify a larger REGION and/or a smaller COLLECT buffer size.

Trace Information
Trace capabilities are implemented in the Tivoli Decision Support for z/OS dialog
and in the log collector. You can also trace SQL statements. It is possible to trace
only certain parts of the processing.

The descriptions that follow show how to set up the different traces, and what
kind of output can be expected from each trace.

The dialog trace, started from the Tivoli Decision Support for z/OS dialogs, is
described in “Dialog Trace” on page 110.

SQL Trace
Trace of SQL statements is requested by setting the trace variable '&ZZSQLSHOW',
either in the PARM field of an EXEC or in the CALL statement. In the dialog, this
is done by setting the Trace SQL calls option to 1 on the Process Tivoli Decision
Support for z/OS Statements window (DRLDACML).

Two types of SQL trace are:

v Trace of SQL statements
This trace is set by &ZZSQLSHOW=STMT. The trace shows executed SQL
statements.

108 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Information in the Dump File

v Trace of SQL operations

This trace is set by &ZZSQLSHOW=OPER. The trace shows the SQL operations
executed (toward the internal SQL interface).
Both traces may be set by setting &ZZSQLSHOW=ALL. In fact, this is what is set
if the SQL trace is set through the dialog.

Trace of Compiled Programs

Trace of compiled programs is requested by setting the trace variables
&ZZCOMPSHOW, &ZZCOMPPROG and &ZZCOMPSNAP. The trace variables
may be set either in the PARM field (for example,
&ZZCOMPSNAP=PROGNAME), or by SET statements in the DRLIN file (for
example, SET ZZCOMPSNAP='PROGNAME').

If a variable content, for example &ZZCOMPSHOW='PROGNAME', is identical

with the first part of a program name or the whole name, the trace is produced.
&ZZCOMPSHOW
Produces diagnostics snapshots of the compile process.
&ZZCOMPPROG
Produces an image of a compiled module.
&ZZCOMPSNAP
Produces diagnostics snapshots of data obtained by executing specific
functions of the compiled module.

Use caution when using trace indicators. A lot of output may be produced and the
DRLDUMP file might need reallocation.

Record or Row Reject Information

Record or row reject information is produced under normal processing when the
processing of the record or row is interrupted.

There is a distinction between rejection of a record and rejection of a table row.

When a record is rejected, both the input (record) and the output row (if
applicable) are skipped. When a table row is rejected, only the output row is
skipped.

Note: If a record or row is rejected when a table row is built, only one specific
update definition will be affected. The record or row might still be valid for
another definition having the same record or row as a base.

When a record or row is rejected, you will get a job termination return code
(warning), and warning message(s) will be written to the output file allocated to
DRLOUT.

The reasons for rejecting a record are:

v A record returned from a log procedure is bad.
v A record returned from a record procedure is bad.
v A record results in null in key (GROUP BY) columns in a (generated) table row.
v A record results in error in the DISTRIBUTE interval.
v A record results in error in the MERGE interval.

This information is written for a rejected record:

v Rejection text specifying one of the above reasons.
v Input record name (not for reason 1).

Appendix A. Dump File Content and Trace Options 109

Information in the Dump File

v The name of the output table (only for reasons 3, 4, and 5).
v The sequence number of the record in the input log.
v The names of any output columns set to null (only for reason 3).

The reasons for rejecting a row are:

v A table row results in null in key (GROUP BY) columns in a (generated) table
row.
v A table row results in error in the DISTRIBUTE interval.
v A table row results in error in the MERGE interval.

This information is written for a rejected table row:

v Rejection text specifying one of the above reasons.
v The name of the input table.
v The name of the output table.
v The data of the input row (up to 4096 bytes).
v The names of any output columns set to null (only for reason 1).

Error Situations Recording

Several error situations occur for which information is logged. Whenever
unexpected messages are shown, or an error has occurred, DRLDUMP will
normally contain more information. Many of these situations are described here:
v Record results in null in data columns
DRLDUMP will contain a text line identifying the record name and the sequence
number of the record in the log plus a text line for each null column with the
name of the column. In order not to fill DRLDUMP with these lines, they will be
written only the first time they occur for each record type.
v SQL error
DRLDUMP will contain the SQL return code plus the SQL descriptor with the
sqltype, data, data indicator, and data length for each column in the call causing
the error.
v DB2/CAF error
DRLDUMP will contain the CAF return and reason codes. DB2/CAF errors will
normally cause an abend of type Program error or SQL error. When this abend
is due to CAF operations, the return and reason codes are part of the abend
output. But if an error occurs during disconnect of CAF, no abend will be issued
and the return and reason codes will be written as text to DRLDUMP.

Dialog Trace
IBM Service personnel might ask you to enable EXECs in the dialog for trace. To
do this, type DRLESTRA on the command line in an Tivoli Decision Support for
z/OS dialog.

The Set/Reset trace options window (Figure 4 on page 111) appears. For EXECs
that are already enabled for trace, the word Trace is shown in the Option column.

110 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Dialog Trace

Options Help

Set/Reset trace options ROW 1 TO 10 OF 59

Select one or more items for processing. Press F5 to enable the trace.
Press F11 to disable the trace.

/ EXEC name Option

_ DRLEAADM
_ DRLEACIN
_ DRLEACMP
_ DRLEACMS
_ DRLEACOP
_ DRLEALCL
_ DRLEALDP
_ DRLEALDS
_ DRLEALOC
_ DRLEALOG

Command ===> _________________________________________________________

F1=Help F2=Split F5=Enable F7=Bkwd F8=Fwd F9=Swap
F11=Disable F12=Cancel

Command ===> drlestra

F1=Help F2=Split F3=Exit F9=Swap F10=Actions F12=Cancel

Figure 4. Set/Reset Trace Options Window

To enable an EXEC for trace, type any non-blank character in the select row and
press F5. Trace appears in the Option column. To disable the trace for an EXEC,
press F11. Alternatively, you can disable a trace quickly for all EXECs by typing
DRLESTRA OFF on the command line on any Tivoli Decision Support for z/OS or
ISPF command line.

When a trace is in effect, the dialog prompts you for a trace directive—a piece of
information controlling what will be displayed. Refer to TSO/E Version 2 REXX
Reference for information about what these directives look like and what data may
be expected through their use.

To trace a complete session, type TSO EXECUTIL TS on the command line. This
will trace all EXECs that are called during the session until it ends or until you
type TSO EXECUTIL TE on the command line.

Note: Use caution when using this option; it produces a lot of output.

Appendix A. Dump File Content and Trace Options 111

Dialog Trace

112 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix B. Using IBM-supplied Diagnostic and Service Aids
This section describes how to use IBM-supplied diagnostic and service aids.

First Failure Support Technology

First Failure Support Technology (FFST) is an IBM licensed program that improves
availability for IBM and vendor software applications by providing immediate
problem notification and first failure data capture. FFST incorporates several failure
analysis and service support functions to simplify the problem determination
process. The problem symptom strings and data areas that FFST collects are the
keys to a fast and correct problem resolution.

This appendix describes how Tivoli Decision Support for z/OS uses FFST. For
information on FFST operation (beyond what is provided here), refer to the FFST
documentation.

Implementation
As described in “Operator Commands” on page 116, FFST works within its own
address space as a started task. Messages about application-event (problem)
detection are written to the MVS console and to one of the FFST message logs.
They are not written to the detecting program’s JES2 job log.

When an application module detects an error, the module triggers an FFST

software probe—an FFST failure-capture macro. This macro gathers failure
information about the error and calls FFST (through an FFST component executing
as a separate task in the caller’s address space). After recording the error, control
returns to the Tivoli Decision Support for z/OS application, which ends with
abend code U002. (See “User Abend Codes” on page 108.)

Tivoli Decision Support for z/OS distinguishes between these types of errors:
Programmed abends
Programmed abends trigger on should-not-occur points in the code. A literal
that uniquely identifies the point in question follows the abend code. (See
“Data-dump Content” on page 114 for information about PRCS/ST
abends.)
System abends
An ESTAE routine set up during initialization of the Tivoli Decision
Support for z/OS application captures system abends.
Program-exception abends
An ESPIE routine set up during initialization captures program-exception
abends.

Note: Refer to the Administration Guide for information about initialization of Tivoli
Decision Support for z/OS applications.

Because FFST generalizes information capture to support both programmed-exit

errors and system errors, Tivoli Decision Support for z/OS uses only one FFST
type-of-failure code—ABEND—regardless of the type of error.

Two of the three modules containing FFST code form separate load modules:

113
Implementation

v The DRLPXCFF load module contains the FFST Tivoli Decision Support for
z/OS configuration module, which is called when FFST is initialized. If this fails,
no dump is generated, but the DRL0980E message (described in “Log Collector
and Installation Preprocessing Messages” on page 3) is written to the
DRLPDUMP data set.
v The DRLPXTFF load module contains the FFST data-structure table, which
defines the data areas that are to be part of the data dump. The module is
referenced when the software probe is executed.

The third module, DRLPXAFF, contains the software probe. It is linked to the
Tivoli Decision Support for z/OS load modules requesting the dump service.

Note: Information passed to FFST is also written to the DRLDUMP data set.

Data-dump Content
This section describes these elements of an FFST data dump:
v Message
v Symptom string
v Tivoli Decision Support for z/OS data areas

FFST Message
The message part of an FFST data dump contains:
v The name of the detecting operation
v The identifier of the triggered software probe
v The name of the data set and volume that contain the raw customized dump
v The primary symptom string
v Optionally, other messages as a result of the processing
For example, if a generic alert is requested and the NetView receiver is not
active, messages EPW0403E and EPW0412I appear.

Note: Messages beginning with EPW are issued by FFST. Refer to the FFST
documentation.

The message part of the FFST data dump is written to the MVS console and to one
of the FFST message logs.

FFST Symptom String

The FFST dump contains two types of symptom strings:
v Primary symptom string
The primary symptom string contains a set of keywords and values that
summarize the failure. The string might look like this:
PIDS/569510100 LVLS/120 PCSS/DRLCOL01 AB/U002 PRCS/ST RIDS/DRLPCOIT
ADRS/000000A0 FLDS/INVCALL
The first three parameters do not vary. The remaining parameters vary,
depending on the error.
PIDS Product identification
LVLS Level identification (version, release and modification ID)
PCSS The software probe ID
AB Abend code
PRCS Abend type (AB/PC/ST/ER)
RIDS Name of module in error
ADRS Offset within the module in error
FLDS Error literal

114 Tivoli Decision Support for z/OS: Messages and Problem Determination
 FFST Symptom String

v Secondary symptom string

The secondary symptom string, which contains register information about the
error, is only partly valid. Information on a register’s content begins where the
FFST macro is first executed (not the point of failure). You can find complete
register information in one of the data areas—the abend register (as described in
“Tivoli Decision Support for z/OS Data Areas”). Registers 2 through 10 are
restored to the state they were in before the abend, so these may be valid. Check
this before using the information displayed from “Areas around registers” (a
part of the data-dump output described in “Data-dump Formatter”).

Tivoli Decision Support for z/OS Data Areas

An FFST data dump contains these Tivoli Decision Support for z/OS data areas:
v Abends
The abend data area contains information about the module in error:
– Module name
– Storage address of the error
– Corresponding offset in the module
– Optionally, for program checks, 16 bytes of instruction code, beginning at the
error address, are given
The first line is abend-type dependent. The PRCS keyword contains the abend
type:
AB Abnormal termination abend code; Dynamic storage limit exceeded;
Server absent or not initialized
PC Program check check code or code description
ST Program error error reason
ER Program error undefined
v Stacks
The stack data area shows the stack of modules preceding the one in error (their
names and the offset from which control was passed).
v Abend registers
The abend-register data area contains the true content of the registers at the
point of error. As explained in “FFST Symptom String” on page 114, check this
data area, because the content of the secondary symptom string is not
completely valid.
v Last calls
The last-call data area contains the most recent R14 (return address) information
preceding the error.
v Dump-items header
The dump-items header data area is provided only (and optionally) when an
abend of the ST type occurs; this abend type provides a reason for the error. If
the area used to display dump items is too small, you will see Abend items area
shortage.
v Dump items (optional)
Up to 16 dump items are listed for ST-type abends.

Data-dump Formatter
You invoke the FFST data-dump formatter with the FFSTDF command. Because
the command accesses ISPF panels from an FFST panel library, the panels must be

Appendix B. Using IBM-supplied Diagnostic and Service Aids 115

Data-dump Formatter

allocated to ISPPLIB before issuing the command. (Refer to ISPF Dialog

Management Guide and Reference, SC32-4266 for more information about panel
allocation.)

When you invoke the formatter, you are prompted for the name of the data-dump
data set (created when the error occurs). The name of a data-dump data set
contains four qualifiers:
hlq.systemname.dumpqual.DMPxxxxx

where:
hlq the high-level qualifier, is FFST
systemname
is the name of the MVS system specified in SYS1.PARMLIB, member
IEASYS00, operand SYSNAME
dumpqual
is a name specified by the DUMPQUAL macro operand of the FFST
EPWCONFG macro For Tivoli Decision Support for z/OS, the macro
specifies PRFMVS.
xxxxx is a sequence number from 00001 to 99999

Besides the data set name, specify whether the formatted data dump is to go to the
printer (P), the terminal (T), or both (B).

Then specify which output is to be included in the dump:

v Symptom string data: Y
v FFST work area: N
v Data structure table(s): N
v Aread around registers: Y
v Data structures: Y

YNNYY is the default. Area around registers is optional, but, depending on the error
type, the information might be useful.

The next panel (EPWFDFOD) prompts you for information about the output data
set (if output destination is not T), including disposition and size information. Set
the figures for primary and secondary blocks to 2 and 5, respectively.

A third panel (EPWFDFDD) appears the first time you request a formatted data
dump. This panel prompts you for a data set name to be used by Interactive
Problem Control System (IPCS) during data-dump formatting. (The allocated data
set will be a VSAM data set.) Use this panel to set the control-interval size (CI size)
to 4096.

Operator Commands
This MVS START command starts FFST:
START procname

For procname, use the name of the FFST procedure. For ease of use, follow procname
with shortname (to be used in MODIFY commands)—for example, FFSTPROC.FFST.

The MVS STOP command stops FFST.

116 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Operator Commands

Tivoli Decision Support for z/OS application-specific information can be preset in

FFST, through the FFST START-command list allocated to the FFST procedure,
ddname FFSTPARM. Alternatively, you can use the MVS MODIFY command to
introduce Tivoli Decision Support for z/OS application-specific information. The
identifiers are:
PRFMVS
Application identification of Tivoli Decision Support for z/OS, referenced
through the FFST operand APPLID.
DRLCOL01
Software probe identification of Tivoli Decision Support for z/OS,
referenced through the FFST operand PROBEID.
PRFMDUMP
Data-dump qualifier of Tivoli Decision Support for z/OS. The qualifier is
not preset by Tivoli Decision Support for z/OS. Set it using either
parameter input or a MODIFY command, like this:
MVS MODIFY FFST,ACTION=CHANGE,APPLID=PRFMVS,
VENDOR=IBM,DUMPQUAL=PRFMDUMP

Output Options
FFST includes output options that control data dump generation and registration:
v DUMP generates data dumps.
v SYMRC generates symptom records.
v GENAL generates alerts to NetView.
v SYMST generates symptom strings.
v SUPDP suppresses duplicate dumps.

The FFST configuration module uses the default values for DUMP, NOSYMRC,
GENAL, SYMST, and NOSUPDP. All these values can be changed.

Symptom records are written to the SYS1.LOGREC data set and are viewed using
the Environmental Record Editing and Printing (EREP) feature of the MVS
operating system.

Note: Only authorized programs can produce symptom records. Tivoli Decision
Support for z/OS, when run on releases prior to MVS/ESA Version 4 is not
authorized to produce symptom records.

Appendix B. Using IBM-supplied Diagnostic and Service Aids 117

Output Options

118 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix C. Problem Description Worksheet for the Host

Customer number: _______________ Date: _____________________

Problem number: ________________ APAR number: ______________

Program specification—program number 5695-101

Tivoli Decision Support for z/OS
component IDs and release levels: __________________________

PUT levels or CBPDO levels: ___________________________________________________________________

Additional PTF and APAR fixes applied: ________________________________________________________

Problem description

First indication of the problem: ______________________________________________________________

_______________________________________________________________________________________________

What were you trying to do? ___________________________________________________________________

_______________________________________________________________________________________________

What did you expect would happen? _____________________________________________________________

_______________________________________________________________________________________________

What did happen? ______________________________________________________________________________

_______________________________________________________________________________________________

Has the function worked before? _______________________________________________________________

_______________________________________________________________________________________________

Can you recreate the problem? _________________________________________________________________

_______________________________________________________________________________________________

Figure 5. Tivoli Decision Support for z/OS Problem Description Worksheet (Part 1 of 3)

119
Type of failure

Choose one or more of the following problem-type keywords:

__ ABEND code: ____________________

Occurred in module: _________________ Date of the module’s compilation: ____________________

Offset into the module: ____________________

__ MSG. Identifier: _______________ Text: _____________________________________________________

Identifier: _______________ Text: _____________________________________________________

__ LOOP. Description: _________________________________________________________________________

_______________________________________________________________________________________________

__ INCORROUT. Type of incorrect output generated:______________________________________________

_______________________________________________________________________________________________

__ PERFM. Operating environment:

Own or modified update definitions? ____________________

Own exit procedures used? ______________________________

Other licensed programs active? ________________________

User modifications to the program? _____________________

__ DOC. Order or TNL number:_______________ Page(s):_____________ Description:_________________

Figure 6. Tivoli Decision Support for z/OS Problem Description Worksheet (Part 2 of 3)

Software used

Specify the software (version, release, modif. level) used at the time the problem occurred:

MVS __________________________________________

__ TSO/E _____________________________________ __ ISPF ______________________________________

__ QMF _______________________________________ __ DB2 _______________________________________

__ GDDM ______________________________________ __ C _________________________________________

Specify the version, release, and modification level of the systems for which data was
collected (for example, IMS/ESA 3.3 or RMF 4.2):

_______________________________________________________________________________________________

_______________________________________________________________________________________________

_______________________________________________________________________________________________

Are you using your own definitions or have you modified IBM supplied definitions? _____________

Can you remove or bypass these definitions and recreate the problem? __________________________

Are you running any exits of your own with Tivoli Decision Support for z/OS? _______________________

If so, which ones? ____________________________________________________________________________

Can you remove or bypass your own exits and recreate the problem? _____________________________

Is there any other user-written code (EXECs, programs, panel changes ) executing in theTivoli Decision Support for z/OS
environment?

_______________________________________________________________________________________________

Can these be bypassed and the function you were attempting then be successfully executed?

_______________________________________________________________________________________________

Note: You can use information marked with an asterisk(*) to supplement your keyword string.

Figure 7. Tivoli Decision Support for z/OS Problem Description Worksheet (Part 3 of 3)

120 Tivoli Decision Support for z/OS: Messages and Problem Determination
Note: You may copy this problem description sheet without payment or royalty,
provided that each reproduction is done without alteration.

Appendix C. Problem Description Worksheet 121

122 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix D. Problem Description Worksheet for the
Workstation Performance Feature

123
 Customer number: _______________ Date: _____________________

Problem number: ________________ APAR number: ______________

Program specification—program number 5695-101

Tivoli Decision Support for z/OS
Workstation Performance feature release level: ___________________________

Problem description

First indication of the problem: ______________________________________________________________

_______________________________________________________________________________________________

What were you trying to do? ___________________________________________________________________

_______________________________________________________________________________________________

What did you expect would happen? _____________________________________________________________

_______________________________________________________________________________________________

What did happen? ______________________________________________________________________________

_______________________________________________________________________________________________

Has the function worked before? _______________________________________________________________

_______________________________________________________________________________________________

Can you recreate the problem? _________________________________________________________________

_______________________________________________________________________________________________

Type of failure

Choose one or more of the following problem-type keywords:

__ MSG. Identifier: _______________ Text: _____________________________________________________

Identifier: _______________ Text: _____________________________________________________

__ LOOP. Description: _________________________________________________________________________

_______________________________________________________________________________________________

_______________________________________________________________________________________________
__ INCORROUT. Type of incorrect output generated:______________________________________________

_______________________________________________________________________________________________

_______________________________________________________________________________________________

__ PERFM. Operating environment:

Other licensed programs active? ________________________

__ DOC. Order or TNL number:_______________ Page(s):_____________ Description:_________________

Hardware used

Specify the hardware used at the time the problem occurred:

Model ________________________________________

Processor ____________________________________ Screen _______________________________________

Memory _______________________________________

Software used

Specify the software (version, release, modification level) used at the time the problem
occurred:

AIX ________________________________________________

__ TCP/IP __________________________________________

__ Host Support File Transfer Program ______________

__ AIX SNA Services/6000 ___________________________

__ AIX Host Connection Program/6000 ________________

124 Tivoli Decision Support for z/OS: Messages and Problem Determination
Figure 8. Workstation Performance Feature Problem Description Worksheet
Note: You may copy this problem description sheet without payment or royalty,
provided that each reproduction is done without alteration.

Appendix D. Problem Description Worksheet 125

126 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix E. Problem Description Worksheet for the AS/400
System Performance Feature

127
 Customer number: _______________ Date: _____________________

Problem number: ________________ APAR number: ______________

Program specification—program number 5695-101

Tivoli Decision Support for z/OS
AS/400 feature release level: ____________________________________________

Problem description

First indication of the problem: ______________________________________________________________

_______________________________________________________________________________________________

What were you trying to do? ___________________________________________________________________

_______________________________________________________________________________________________

What did you expect would happen? _____________________________________________________________

_______________________________________________________________________________________________

What did happen? ______________________________________________________________________________

_______________________________________________________________________________________________

Has the function worked before? _______________________________________________________________

_______________________________________________________________________________________________

Can you recreate the problem? _________________________________________________________________

_______________________________________________________________________________________________

Type of failure

Choose one or more of the following problem-type keywords:

__ MSG. Identifier: _______________ Text: _____________________________________________________

Identifier: _______________ Text: _____________________________________________________

__ LOOP. Description: _________________________________________________________________________

_______________________________________________________________________________________________

_______________________________________________________________________________________________
__ INCORROUT. Type of incorrect output generated:______________________________________________

_______________________________________________________________________________________________

_______________________________________________________________________________________________

__ PERFM. Operating environment:

Other licensed programs active? ________________________

__ DOC. Order or TNL number:_______________ Page(s):_____________ Description:_________________

Hardware used

Specify the hardware used at the time the problem occurred:

Model ________________________________________

Processor ____________________________________ Screen _______________________________________

Memory _______________________________________

Software used

Specify the software (version, release, modification level) used at the time the problem
occurred:

OS/400 _____________________________________________

__ NetView FTP _____________________________________

__ NetView FTP/400 _________________________________

Figure 9. AS/400 Feature Problem Description Worksheet

128 Tivoli Decision Support for z/OS: Messages and Problem Determination
Note: You may copy this problem description sheet without payment or royalty,
provided that each reproduction is done without alteration.

Appendix E. Problem Description Worksheet 129

130 Tivoli Decision Support for z/OS: Messages and Problem Determination
Appendix F. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This
section describes the following options for obtaining support for IBM software
products:
v “Searching knowledge bases”
v “Obtaining fixes”
v “Receiving weekly support updates” on page 132
v “Contacting IBM Software Support” on page 132

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

IBM provides extensive documentation that can be installed on your local
computer or on an intranet server. You can use the search function of this
information center to query conceptual information, instructions for completing
tasks, and reference information.

Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

To search multiple Internet resources for your product, use the Web search topic in
your information center. In the navigation frame, click Troubleshooting and
support
Searching knowledge bases and select Web search. From this topic, you
can search a variety of resources, including the following:
v IBM technotes
v IBM downloads
v IBM developerWorks®
v Forums and newsgroups
v Google

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support/.
2. Click Downloads and drivers in the Support topics section.
3. Select the Software category.
4. Select a product in the Sub-category list.
5. In the Find downloads and drivers by product section, select one software
category from the Category list.
6. Select one product from the Sub-category list.

131
 7. Type more search terms in the Search within results if you want to refine your
search.
8. Click Search.
9. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

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

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/support/
us/.
2. Click My support in the upper right corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Application servers.
A third list is displayed.
7. In the third list, select a product sub-segment, for example, Distributed
Application & Web Servers. A list of applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
HTTP Server and WebSphere® Application Server.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email
on the Edit profile tab.
11. Select Please send these documents by weekly email.
12. Update your e-mail address as needed.
13. In the Documents list, select Software.
14. Select the types of documents that you want to receive information about.
15. Click Update.

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

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

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

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

To contact IBM Software support, follow these steps:

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

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.

Appendix F. Support information 133

 Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

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

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

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

134 Tivoli Decision Support for z/OS: Messages and Problem Determination
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user'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 this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

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

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

IBM World Trade Asia Corporation

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

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and
changes in the product(s) and/or the program(s) described in this publication at
any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

135
Notices

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

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

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

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

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

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to

136 Tivoli Decision Support for z/OS: Messages and Problem Determination
 Notices

IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM‘s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color
illustrations might not display.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.

Notices 137
138 Tivoli Decision Support for z/OS: Messages and Problem Determination
Bibliography
TDS publications
Administration Guide and Reference, SH19-6816
Resource Accounting for z/OS, SH19-4495
AS/400 System Performance Feature Guide and Reference, SH19-4019
CICS Performance Feature Guide and Reference, SH19-6820
Distributed Systems Performance Feature Guide and Reference, SH19-4018
Guide to Reporting, SH19-6842
IMS Performance Feature Guide and Reference, SH19-6825
Language Guide and Reference, SH19-6817
Messages and Problem Determination, SH19-6902
Network Performance Feature Installation and Administration, SH19-6901
Network Performance Feature Reference, SH19-6822
Network Performance Feature Reports, SH19-6821
System Performance Feature Guide, SH19-6818
System Performance Feature Reference Volume I, SH19-6819
System Performance Feature Reference Volume II, SH19-4494
Usage and Accounting Collector User Guide, SC23-7966

139
140 Tivoli Decision Support for z/OS: Messages and Problem Determination
Glossary

A internal data type
A data type used within Tivoli Decision
administration
Support for z/OS during the processing
A Tivoli Decision Support for z/OS task
of data.
that includes maintaining the database,
updating environment information, and
K
ensuring the accuracy of data collected.
key columns
administration dialog The columns of a DB2 table that together
A set of host windows used to administer constitute the key.
Tivoli Decision Support for z/OS.
key value

C Value that is used to sort records into
groups.
collect A process used by Tivoli Decision
Support for z/OS to read data from input
L
log data sets, interpret records in the data
log collector
set, and store the data in DB2 tables in
A Tivoli Decision Support for z/OS
the Tivoli Decision Support for z/OS
program that processes log data sets and
database.
provides other Tivoli Decision Support for
component z/OS services.
An optionally installable part of a Tivoli
log collector language
Decision Support for z/OS feature.
Tivoli Decision Support for z/OS
Specifically in Tivoli Decision Support for
statements used to supply definitions to
z/OS, a component refers to a logical
and invoke services of the log collector.
group of objects used to collect log data
from a specific source, to update the log data set
Tivoli Decision Support for z/OS Any sequential data set that is used as
database using that data, and to create input to Tivoli Decision Support for z/OS.
reports from data in the database.
log definition
control table The description of a log data set
A predefined Tivoli Decision Support for processed by the log collector.
z/OS table that controls results returned
log procedure
by some log collector functions.
A program module that is used to process

D all record types in certain log data sets.
data table lookup expression
A Tivoli Decision Support for z/OS table An expression that specifies how a value
that contains performance data used to is obtained from a lookup table.
create reports.
lookup table

E A Tivoli Decision Support for z/OS DB2
table that contains grouping, translation,
environment information
or substitution information.
All of the information that is added to the
log data to create reports. This
P
information can include data such as
Tivoli Decision Support for z/OS database
performance groups, shift periods,
A set of DB2 tables that includes data
installation definitions, and so on.
tables, lookup tables, system tables, and
exit A log or record procedure. control tables.

I

141
purge condition system table
Instruction for purging old data from the A DB2 table that stores information that
Tivoli Decision Support for z/OS controls log collector processing, Tivoli
database. Decision Support for z/OS dialogs, and
reporting.

R

T
record definition
The description of a record type contained target In an update definition, the DB2 table in
in the log data sets used by Tivoli which Tivoli Decision Support for z/OS
Decision Support for z/OS, including stores data from the source record or
detailed record layout and data formats. table.
record procedure threshold
A program module that is called to The maximum or minimum acceptable
process some types of log records. level of usage. Usage measurements are
compared with threshold levels.
record type
The classification of records in a log data
U
set.
update definition
repeated section Instructions for entering data into DB2
A section of a record that occurs more tables from records of different types or
than once, with each occurrence adjacent from other DB2 tables.
to the previous one.

V
report definition language
view An alternative representation of data from
Tivoli Decision Support for z/OS
one or more tables. A view can include all
statements used to define reports and
or some of the columns contained in the
report groups.
table on which it is defined.
report group
A collection of Tivoli Decision Support for
z/OS reports that can be referred to by a
single name.
reporting dialog
A set of host or workstation windows
used to request reports.
resource group
A collection of network resources that are
identified as belonging to a particular
department or division. Resources are
organized into groups to reflect the
structure of an organization.
resource information
Environment information that describes
the elements in a network.

S
section
A structure within a record that contains
one or more fields and may contain other
sections.
source In an update definition, the record or DB2
table that contains the data used to
update a Tivoli Decision Support for
z/OS DB2 table.

142 Tivoli Decision Support for z/OS: Messages and Problem Determination
Index
A data-dump formatter, FFST 115
DEFINE/DROP report and report group
First Failure Support Technology (FFST)
(continued)
abend code U002 113 messages 51 implementation 113
abend codes description worksheet, Tivoli Decision load modules 113
user 108 Support for z/OS problem 119 operator commands 116
abend information 107 AS/400 System Performance output options 117
ABEND keyword 92 featureAS/400 System Performance fixes, obtaining 131
abend registers (in FFST data feature 127 formatter, FFST data-dump 115
dump) 115 Workstation Performance
abends (in FFST data dump) 115 featureWorkstation Performance
abends, types of 113
accessibility x
feature 123
dialog messages, help vii
H
analysis using FFST, failure 113 hardware 99
dialog trace 110
APAR (authorized program analysis help for dialog messages vii
DOC (documentation) keyword 95, 102
report) 97 host messages
documentation
areas, Tivoli Decision Support for z/OS from the AS/400 feature 50
TDS 139
data (in FFST dump) 115 from the CICS feature 48
DRL0317I DRL0318I DRL0319I DRL0320I
AS/400 feature messages 50 from the IMS feature 37
DRL0321I DRL0322I 24
AS/400 featureAS/400 feature generated by REXX utilities
DRL0323I DRL0324I DRL0325I DRL0326I
problem description worksheet 127 batch reporting 55
DRL0327I 24
problem determination 99 DEFINE/DROP report and report
DRL0404I DRL0405I DRL0406I 30
AS/400 System Performance group 51
DRL0445I DRL0446I DRL0447I 31
featureAS/400 System Performance generated by the log collector 3
DRL3120I 57
feature generated by the log data
DRLDUMP 107
problem description worksheet 127 manager 64
DROP/DEFINE report and report group
problem determination 99 generated by the REXX-SQL
messages 51
audience for this book, intended vii interface 35
dump content, FFST data- 114
authorized program analysis report Information/Management 63
dump file 107
(APAR) 97 installation preprocessing 3
dump formatter, FFST data- 115
migration 59
dump items (in FFST data dump) 115
host problem determination 89
B how to use this book vii

batch reporting messages 55 E

books viii, ix education x
environment
I
implementation, FFST 113
host
C software 91
IMS feature messages 37
INCORROUT (incorrect output)
calls, last (in FFST data dump) 115 workstation
keyword 95, 102
capture, first failure data 113 hardware 99
information centers, searching for
checklist, Tivoli Decision Support for software 99
problem resolution 131
z/OS problem description 119, 123, error data items 108
Information/Management messages 63
127 error situations recording 110
interface messages, REXX-SQL 35
CICS feature messages 48 exception abends, program- 113
Internet
classifying problems 99 exit messages
searching for problem resolution 131
code U002, abend 113 CICS 48
invoking the FFST data-dump
collecting information IMS 37
formatter 115
about specific problems 92
collector messages, log 3
commands, FFST operator 116 F K
component ID 96, 100 failure analysis using FFST 113
conventions keyword
FFST (First Failure Support
typeface xi ABEND 92
Technology) 113
customer support 132 DOC (documentation) 95, 102
first failure data capture 113
INCORROUT (incorrect output) 95,
First Failure Support Technology (FFST)
102
data-dump content 114
D message 114
LOOP 94, 101
MSG (message) 93, 101
data areas, Tivoli Decision Support for symptom string 114
PERFM (performance) 95, 102
z/OS (in FFST dump) 115 Tivoli Decision Support for z/OS
string 89
data capture, first failure 113 data areas 115
keywords 90
data-dump content, FFST 114 data-dump formatter 115
keywords for problems 89

143
knowledge bases, searching for problem problem description worksheet 123, 127 System Diagnostics 92
resolution 131 host 119
workstation
AS/400 System Performance T
L featureAS/400 System
Performance feature 127
termination cause 107
last calls (in FFST data dump) 115 Tivoli Decision Support for z/OS data
Workstation Performance
load modules for FFST 113 areas (in FFST dump) 115
featureWorkstation Performance
log collector messages 3 Tivoli Decision Support for z/OS
feature 123
log data manager messages 64 problem description worksheet 119,
problem determination
LOOP keyword 94, 101 123, 127
describing problems 134
Tivoli software information center ix
determining business impact 133
Tivoli technical training x
host 89
M submitting problems 134
trace
compiled programs 109
manuals viii, ix workstation 99
dialog 110
TDS 139 problem keywords 89
SQL 108
message failure 93, 101 problems
trace information 108
message, FFST 114 information about 99
training, Tivoli technical x
messages, host program temporary fix (PTF) 97
typeface conventions xi
from the AS/400 feature 50 program-exception abends 113
from the CICS feature 48 programmed abends 113
from the IMS feature 37 PTF (program temporary fix) 97
generated by REXX utilities publications viii U
batch reporting 55 accessing online ix U002, abend code 113
DEFINE/DROP report and report TDS 139 Usage and Accounting Collector
group 51 generated by Usage and Accounting
generated by the log collector 3 Collector 69
generated by the log data
manager 64
R Usage and Accounting Collector
messages 69
register content 108
generated by the REXX-SQL user abend codes 108
registers, abend (in FFST data
interface 35 users of this book, intended vii
dump) 115
Information/Management 63
reject information
migration 59
record or row 109
messages, issued on AS/400 system
generated by the log collector 85
release numbers 90 W
report and report group messages, Web Reporting messages 68
messages, Usage and Accounting
DEFINE/DROP 51 Web Reporting Messages
Collector
reporting messages, batch 55 generated by Web Reporting 68
generated by Usage and Accounting
RETAIN database 90 who should use this book vii
Collector 69
REXX utility messages worksheet
messages, Web Reporting
batch reporting 55 problem description
generated by Web Reporting 68
DEFINE/DROP report and report AS/400 System Performance
messages, workstation vii
group 51 featureAS/400 System
migration messages 59
REXX-SQL interface messages 35 Performance feature 127
module stack 108
host 119
modules for FFST, load 113
Workstation Performance
MSG (message) keyword 93, 101
S featureWorkstation Performance
feature 123
secondary symptom string, FFST 115
workstation messages, help vii
O service support functions of FFST 113
software 91, 99
Workstation Performance
online publications featureWorkstation Performance feature
Software Support
accessing ix problem description worksheet 123
contacting 132
operator commands, FFST 116 problem determination 99
describing problems 134
options, FFST output 117 workstation problem determination 99
determining business impact 133
output options, FFST 117
receiving weekly updates 132
submitting problems 134
SQL trace 108
P stacks (in FFST data dump) 115
PARM field 109 string, FFST symptom 114
PERFM (performance) keyword 95, 102 support, service 113
primary symptom string, FFST 114 supporting materials 98
problem symptom string 89
collecting information about 91 symptom string, FFST 114
documentation about 96, 100 System
information about 92, 101 Diagnostics 92
keywords 90 system abend 92
reporting to IBM 97, 103 system abends 113

144 Tivoli Decision Support for z/OS: Messages and Problem Determination



Printed in USA

SH19-6902-15