DB2 Server for VSE Messages and Codes (Version 7 Release 5)

Contents

About This Manual

Chapter 12. ARI7001-ARI7970 ISQL

Conventions Used in This Manual

Messages

147

Online HELP Text

Components of the Relational Database Management

Chapter 13. ARI0800-ARI0899,

System

ARI8000-ARI8999 DBS Utility

SQL Reserved Words

vii

Messages

191

Common Error Action

191

Summary of Changes

Rerunning DBS Utility

191

Summary of Changes for DB2 Version 7 Release 5

Enhancements, New Functions, and New

Chapter 14. ARI0900-ARI0949

Capabilities

. ix

Database Maintenance and Database

Chapter 1. Introduction

I/O Messages

217

Using This Manual

Message Format and Associated Text

Chapter 15. ARI0950-ARI0974 Trace

Formatter Messages

225

Chapter 2. ARI0001-ARI0199 DB2 Server

for VSE Control Messages

Chapter 16. CICS/VSE Transaction

Abend Codes

229

Chapter 3. ARI0200-ARI0299, ARI2000-

ARI2069 DBSS Messages

Chapter 17. DBSS Return Codes . .

231

Warning Return Codes

231

Chapter 4. ARI2900-ARI2942 Common

Bad Return Codes

231

Messages

Chapter 18. SQLCODEs

237

SQLCODEs 0, and +12 through +863

237

Chapter 5. ARI0400-ARI0498 Resource

SQLCODEs -084 through -30090

248

Adapter Messages

Chapter 19. SQLSTATEs

335

Chapter 6. ARI4000-ARI4599 DB2

Server for VSE Control Messages . . . 93

Chapter 20. DB2 Server for VSE

Reason Codes

355

Chapter 7. ARI0500-ARI0511 SQL

VSE/Advanced Functions System Services Return

Messages

107

Codes

355

VSE/Advanced Functions Abnormal Termination

Chapter 8. ARI0520-ARI0535,

Codes

355

ARI5806-AR5810 Catalog Maintenance

VSE/Advanced Functions Cross-Partition

Messages

111

Communication Codes

356

Other DB2 Server for VSE Abnormal Termination

Codes

357

Chapter 9. ARI0536-ARI0599,

ARISBDID JCL Return Codes

358

ARI5361-ARI5431 Preprocessor

ARISBGUD JCL Return Codes

358

Messages

115

ARISCNVD JCL Return Codes

358

ARISGDEF JCL Return Codes

359

Chapter 10. ARI5500-ARI5593

ARISIQBD/Other bindfile load JCL Return Codes

359

FLAGGER Messages

135

Chapter 21. Sequential File Errors . .

361

Chapter 11. ARI0600-ARI0699,

Chapter 22. Include File Access Errors

365

ARI6000-ARI6299, ARI0700-ARI0799

Problem Determination Notes:

365

EXEC Messages

145

Chapter 23. Limit Errors

367

iii

About This Manual

This manual lists the messages and codes issued by the DB2 Server for VSE

system. This reference manual is for users, operators, programmers, and

maintainers of this product. This manual explains the messages you see on your

display terminal.

The manual contains messages with the prefix ARI and ASN. The Data Propagator

Relational Capture for VSE & VM messages are included in the manual and

contain the ASN prefix.

The messages and codes, where appropriate, consist of:

v An expanded explanation of the message text

v The action taken by the system

v The response required of the user, operator, programmer, database administrator,

and system programmer.

The codes section contains information for:

v CICS/VSE^® Transaction Abend Codes

v DBSS return codes

v SQLCODEs

v SQLSTATEs

v Reason codes, including:

- System service return codes

- System abend codes

- System communication codes

v Sequential file errors

v Include file access errors

v Limit errors

v System errors

v Hardware errors.

The “Summary of Changes” section summarizes the technical and library changes

made for the DB2 Server for VSE Version 7 Release 5 product.

Chapters 15 through 19 explain the various codes and SQLSTATEs that can be

returned to a DB2 Server for VSE user or application program. Most of the codes

and SQLSTATEs report error conditions. The codes are presented in groups,

according to the source of the codes. The codes can come from the DB2 Server for

VSE system itself, or from various other programs with which the DB2 Server for

VSE system works.

If you are the system programmer or the database administrator, see the DB2

Server for VSE & VM Diagnosis Guide and Reference manual for information on

reporting a problem whenever you are asked in System Programmer Response or

Database Administrator Response to contact your designated support group for

your installation.

Throughout this manual, the DB2 Server for VSE Version 7 Release 5 product is

referred to as DB2 Server for VSE, the database system, database manager or

About This Manual

application server, unless otherwise noted. In some cases, the online help may use

different terminology to that found in the manual.

For a list of related publications, see “Bibliography” on page 399.

Conventions Used in This Manual

In this manual, the following terms are used:

Term Meaning

CICS^® Customer Information Control System (CICS/VSE 2.1 and later) The terms

CICS and CICS/VSE are used interchangeably throughout this manual.

DBS utility

Database Services Utility

ISQL Interactive Structured Query Language

LUW Logical unit of work

LUW ID

Logical unit of work identifier

DB2 Server for VSE

DB2 Server for VSE Version 7 Release 5

user ID

User identification

VSE VSE/ESA Release 2.2 and later

Online HELP Text

Most of the information in this manual is also available as online HELP text.

Installation of the online HELP text is optional. To use the online HELP text, when

installed, enter the ISQL command HELP followed by a space and the message

number or SQLCODE, or enter HELP SQLSTATE followed by the 5-digit

SQLSTATE number.

Note: The online HELP text for messages, codes, and SQLSTATE information is

not serviced by the IBM Support Center. The online HELP text is similar to

this manual. You can use the Readers’ Comment Form in the back of this

manual to comment on the online HELP text. If you want to submit an

Authorized Program Analysis Report (APAR) against documentation, it

must be written against this manual, not the online HELP text.

Components of the Relational Database Management System

Figure 1 on page vii depicts a typical configuration with one database, one batch

partition user, and a CICS^® partition with several interactive users.

vi Messages and Codes

About This Manual

Online Resource Adapter

Application Requester

ent

Interactive SQL

ent

CICS Application

Dbextent

Storage

Applications

Pool

CICS Partition

Batch Resource Adapter

Application

Program

Directory

Application Requester

Log

VSE Batch

Partition

Database

Data System Control

VSAM

Relational Data System

Database Storage

DB2

Subsystem

Database

for VSE

Database Manager

Partition

Library

VSE

Application Server

Figure 1. Basic Components of the RDBMS

The database is composed of:

v A collection of data contained in one or more storage pools, each of which in turn

is composed of one or more database extents (dbextents).

v A directory that identifies data locations in the storage pools. There is only one

directory per database.

v A log that contains a record of operations performed on the database. A database

can have either one or two logs.

The database manager is the program that provides access to the data in the

database. It is loaded into the database partition from the DB2 Server for VSE

library.

The application server is the facility that responds to requests for information from

and updates to the database. It is composed of the database and the database

manager.

The application requester is the facility that transforms a request from an

application into a form suitable for communication with an application server.

SQL Reserved Words

The following words are reserved in the SQL language. They cannot be used in

SQL statements except for their defined meaning in the SQL syntax or as host

variables, preceded by a colon.

About This Manual vii

Summary of Changes

This is a summary of the technical changes to the DB2 Server for VSE & VM

database management system for this edition of the book. Several manuals are

affected by some or all of the changes discussed here. For your convenience, the

changes made in this edition are identified in the text by a vertical bar (|) in the

left margin. This edition may also include minor corrections and editorial changes

that are not identified.

This summary does not list incompatibilities between releases of the DB2 Server

for VSE & VM product; see either the DB2 Server for VSE & VM SQL Reference, DB2

Server for VM System Administration, or the DB2 Server for VSE System

Administration manuals for a discussion of incompatibilities.

Summary of Changes for DB2 Version 7 Release 5

Version 7 Release 5 of the DB2 Server for VSE & VM database management

system is intended to run on the Z/VM Version 5 Release 2 or later environment

and on the Z/VSE(^®) Version 3 Release 1 or later environment.

Enhancements, New Functions, and New Capabilities

The following have been added to DB2 Version 7 Release 5:

Explain Option on DBSU REBIND PACKAGE Command

This new functionality allows the EXPLAIN(YES/NO) option on REBIND

PACKAGE command. If EXPLAIN(YES) is issued, then all four update tables

(structure, plan, cost, reference) will be updated. If EXPLAIN(NO) is issued, then

none of the four update tables will be updated.

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VSE & VM Database Services Utility

v DB2 Server for VSE & VM Performance Tuning Handbook

v DB2 Server for VSE & VM Quick Reference

v DB2 Server for VSE & VM SQL Reference

For Fetch only

This new functionality accepts the ″FOR FETCH ONLY″ clause after a cursor select

statement. It causes a cursor to become read-only (no UPDATEs or DELETEs are

permitted using this cursor). If a read-only cursor is referenced in an UPDATE or

DELETE statement, SQLCODE -510 will be issued and the statement is not

processed. In addition, under the SBLOCK preprocessor option, ″FOR FETCH

ONLY″ forces blocking to be used on the read-only cursor regardless of whether

there is a COMMIT. If there is no ″FOR FETCH ONLY″ clause, under SBLOCK,

blocking would only be done if a COMMIT was absent.

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VM Messages and Codes

v DB2 Server for VSE & VM Application Programming

v DB2 Server for VSE & VM Performance Tuning Handbook

v DB2 Server for VSE & VM Quick Reference

v DB2 Server for VSE & VM SQL Reference

Application Message Formatter

This functionality provides an Application Programming Interface (API) that

retrieves the descriptive text for an SQLCODE, given an SQLCA input parameter.

The API will be available for Assembly, COBOL, C, PL/I and FORTRAN.

In DB2 for VM and DB2 for VSE Online, the user may specify the language of the

returned text. The languages supported by DB2 for VSE/VM are American English

(AMENG), uppercase English (UCENG), German (GER), French (FRANC) and

Japanese (KANJI). VSE Batch does not support switching to another language.

Therefore the default will be used regardless of the user’s specification. The values

of SQLCODE, SQLSTATE, SQLERRD1 and SQLERRD2 will be automatically

appended to the returned text. The user may also specify to have the entire

SQLCA included. If the SQLCODE could not be found in the repository, the entire

SQLCA will be returned in the buffer.

If the SQLCA was set by another product (such as DB2 UBD), the descriptive text

is retrieved if the SQLCODE exists in the DB2 for VM/VSE repositories. However,

the token substitutions may not be correct.

For more information, see DB2 Server for VSE & VM Application Programming.

Convert buffer read/write to compiler macro

The DRDA code has over 100 small modules. Each call to an external module has a

certain amount of overhead associated with it. Certain modules are called very

frequently and this can add up to a significant amount of time. This functionality

improves the performance by converting few modules to macros or internal

procedures, to reduce this overhead.

Modify Build Tree Creation

This functionality modifies Build Tree creation used by DRDA parsing and

generation. It is built in such a way that every code point that is used to search

through the tree must be converted to a different format before the search can be

done. If modified build tree was created with the converted point, then the code

point would not have to be converted every time the tree must be searched. This

improves the performance of the DRDA code path length with the minimal search.

Split code point search routines

When parsing a data stream within each parser action routine, a binary search is

done to find the specific code point. Some action specific routines are quite large,

so the binary search can be long. Splitting and spreading the code point evenly

among other modules would reduce the overheads and improves the performance

of the DRDA code path length.

DRDA Multi-Row Insert

Multi Row insert is a means of caching homogenous insert statements and sending

them as a block to the server for processing. This reduces the overhead of sending

a large number of singular inserts and receiving as many responses.

Buffering of homogenous inserts eliminates the need to send an SQL statement to

the DB2 server every time an insert is made, thereby improving performance over

DRDA.

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VSE & VM Application Programming

Messages and Codes

v DB2 Server for VSE & VM Database Administration

v DB2 Server for VM System Administration

v DB2 Server for VSE & VM Performance Tuning Handbook

v DB2 Server for VSE & VM Quick Reference

v DB2 Server for VSE & VM SQL Reference

Connection Pooling for DRDA TCP/IP in Online Resource

Adapter

Connection pooling is a technique that allows multiple users to share a cached set

of pre-established connections that provide access to a database. Establishing a

connection between a user and a server takes a sizeable time. Users who have

validated their entry to a database once need not establish a connection every time

a request is submitted. Instead, they can use a pre-established connection from a

pool of such connections and get their results much faster.

From the user’s point of view, there is a considerable improvement in response

time after this line item is implemented.

For more information, see the following documentation on DB2 Server for VSE &

VM:

v DB2 Server for VSE System Administration

v DB2 Server for VSE & VM Application Programming

v DB2 Server for VSE & VM Operation

v DB2 Server for VSE & VM Performance Tuning Handbook

IBM DB2 Server for VSE, Client Edition

This feature allows the customer the flexibility to install and use only the client

(run-time support) component of DB2 Server for VSE without the requirement to

buy and install the server component during the installation process of DB2 server

for VSE product. The client-only installation enables customers to reduce the total

cost of ownership when they have their databases residing on a non-local platform

(like VM, z/OS, LUW) and have a large number of their DB2 applications on VSE

(like ISQL on CICS, DBSU on VSE, other online/batch applications on VSE).

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VSE System Administration

v DB2 Server for VSE Program Directory

IBM DB2 Server for VM, Client Edition

This feature allows the customer the flexibility to install and use only the client

(run-time support) component of DB2 Server for VM without the requirement to

buy and install the server component during the installation process of DB2 server

for VM product. The client-only installation enables our customers to reduce the

total cost of ownership when they have their databases residing on a non-local

platform (like VM, z/OS, LUW) and have a large number of their DB2 applications

on VM (like ISQL, DBSU, other user applications on VM).

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VM System Administration

v DB2 Server for VM Program Directory

Summary of Changes xi

Handling Commit Responses from DB2 UDB Stored Procedures

This feature will allow DB2 Resource Manager on VSE/VM to accept and process

results of a stored procedure running in a UDB server with a COMMIT statement

in the stored procedure.

Currently, DB2 for VM/VSE client does not handle responses from ’COMMIT’

statements coded in DB2 UDB stored procedures. Implementation of this feature

will enable handling responses of COMMIT statements in DB2 UDB stored

procedures and thus allow users to have COMMIT statements in their stored

procedures, while using DB2 for VM/VSE client.

COMMIT statements, however, are not allowed in stored procedures on the DB2

Server for VM/VSE.

For more information, see DB2 Server for VSE & VM Application Programming.

Make on-line programs AMODE 31 RMODE ANY

This feature converts DB2 server for VSE online program which presently operate

under 24 bit addressing mode from AMODE 24, to AMODE 31 RMODE ANY.

Presently, all the online programs are loaded below 16M line. Implementation of

this line item ensures that all the online program will be loaded above the 16M

line, which results in more virtual storage below the line, which can be utilized by

other applications.

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 Server for VSE System Administration

v DB2 Server for VSE Program Directory

Provide BIND File Support in VM and in VSE Batch Environments

This feature provides the facility of binding packages across servers. The process of

binding is achieved by dividing the program preparation method into two steps.

The first step does the precompilation of the embedded SQL programs with the

prep parameter ’BIND’. Invocation of VSE/VM preprocessor creates a ’bindfile’.

The bindfile can be bound against any DB2 server using VSE/VM binder. During

this process, the access path is generated, SQL statements are verified,

authorization checks are performed, and package on the target server is created.

This line item eliminates the need of re-prepping the source code or porting of

packages across DB2 servers.

For more information, see the following DB2 Server for VSE & VM documentation:

v DB2 REXX SQL for VM/ESA Installation and Reference

v DB2 Server for VM Messages and Codes

v DB2 Server for VSE & VM Application Programming

v DB2 Server for VSE & VM Database Administration

v DB2 Server for VM Program Directory

v DB2 Server for VSE Program Directory

Convert TCP/IP LE/C interface to EZASMI API

The feature of converting TCP/IP LE/C interface to EZASMI API intends to

replace the current LE/C interface and implement the EZA Assembler Interface

(EZASMI)to enhance performance in DB2 Client/Server for VSE over DRDA.

Currently, either LE/C interface or CSI Assembler Interface is used for TCP/IP

functions. The EZASMI interface makes the code all Assembler.

xii Messages and Codes

Chapter 1. Introduction

All DB2 Server for VSE messages have a message

Using This Manual

identifier in the form of XXXnnnnt, where:

If you use this manual regularly, you should read

XXX Identifies the major component generating

this section along with the following section

the message:

“Message Format and Associated Text”. They

provide information that is helpful when you use

ARI shows the message is from the

this manual for reference.

database manager component of

the DB2 Server

All messages have four digits following the ARI

ASN shows the message is from the

or ASN prefix. Old 3-digit messages are now

DPROPR component

preceded by a zero. For example, ARI201E is now

ARI0201E.

DSQ see QMF Messages and Codes

manual

The table of contents can help you in looking up

XTS shows the message is from the

a particular message, code, or error because

Data Restore Feature.

headings are provided to show the numeric

sections and page locations. You can also use the

nnnn Identifies the particular message number.

index at the back of the book to find the page or

Is the action indicator:

pages of any particular message or code.

Action required

D Decision required

Message Format and Associated

Error

Information only

Text

System wait.

In this book, the conventions for showing

messages are:

For messages beginning with:

v All the letters, numbers, and punctuation

XTS See the DB2 Server for VSE & VM Data

marks (periods, commas, underscores, dashes,

Restore manual

and so on) following the message identifier in

SQM See the DB2 for VSE Control Center

bold show the actual message text. The

Operations Guide.

exceptions to this convention are brackets [ ],

braces { }, logical OR symbols |, blank lines,

ELO See the DB2 REXX SQL for VM/ESA

and format numbers.

Installation and Reference manual

v Letters, words, and numbers in the text of the

message that are not bold represent variables.

Explanation contains information about the

Hyphenated words that are not bold also

message. This includes the following:

represent variables. The database manager

v Definitions for variable fields in the message

substitutes specific values for the variables

text

when it displays the message.

v Possible reasons why the message occurred

In the explanation following the message text,

v Additional descriptive information about the

the variables are in bold or italics.

condition that caused the message to occur.

v Brackets [ ] enclose optional message text.

Depending on the circumstances, an item or

System Action describes the resulting action that

group of items in brackets might appear when

was or will be taken by the database manager.

the message is displayed.

v Braces { } enclose alternative items, which are

User Response, Operator Response, Programmer

separated by a logical OR | symbol. Depending

Response, Database Administrator Response,

on the circumstances, one of the alternative

and System Programmer Response describe the

items appears when the message is displayed.

responses that might be required of those persons.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control

Messages

v Catalog the parameter data set in the library as a

ARI0001E An error occurred while attempting to

source member (the A sublibrary), or

obtain storage.

v Correct the PARMID parameter in the job control.

Explanation: Either:

v All available GETVIS storage has been exhausted; the

If the problem persists, for corrective action, look up

reason code, normally displayed at end-of-job, will

the displayed error codes under either Chapter 22,

be 12 (X’0C’)

“Include File Access Errors,” on page 365 or "INCLUDE

v A hardware error occurred while attempting to get

FILE ERRORS" in the HELP text.

storage; the reason code will be 32 (X’20’)

v An internal error occurred while attempting to get

ARI0003E An error occurred reading the xxxxxxxx

storage; the reason code will be 8 (X’08’).

parameter data set. Reason Code = nn

Return Code = nn.

Note: The DB2 Server for VSE reason code is the

Explanation: xxxxxxxx is the name of the parameter

VSE/Advanced Functions GETVIS macro return

data set as specified in the PARMID parameter. This

code. It is displayed in message ARI0042I.

parameter is specified in the job control to identify a

System Action: If SQLCODE -930 accompanies this

library source statement member (in the "A"

message, the database manager continues and

sublibrary).

additional requests to obtain storage may result in the

The REASON value is the Primary Error Code. The

message being issued again. If the message is issued

CODE value is the Secondary Error Code. For further

without SQLCODE -930, the database manager is

explanation, look up the displayed error codes under

ended.

either Chapter 22, “Include File Access Errors,” on page

Operator Response: If GETVIS storage has been

365, or “INCLUDE FILE ERRORS” in the HELP text.

exhausted (reason code = 12), restart the database

System Action: The database manager ends.

manager after allocating a larger partition.

Operator Response: For further explanation, look up

System Programmer Response: You may have to

the displayed error codes under either Chapter 22,

assist the operator in determining what partition size

“Include File Access Errors,” on page 365, or

will be required if storage is exhausted. Contact the

“INCLUDE FILE ERRORS” in the HELP text.

appropriate personnel for hardware service or the

designated support group.

ARI0004I

xxxxxxxx - The database manager

ignores PARMID within a parameter

ARI0002E Unable to open the xxxxxxxx parameter

data set.

data set. Reason Code = nn. Return

Code=nn.

Explanation: xxxxxxxx is the name of the parameter

data set which contains the PARMID initialization

Explanation: xxxxxxxx is the name of the parameter

parameter. The PARMID parameter is ignored in a

data set as specified in the PARMID parameter.

parameter data set.

This parameter is specified in the job control to identify

System Action: Processing continues.

a library source statement member (in the "A"

sublibrary).

Operator Response: Refer this message to your

system programmer.

The Reason Code value is the Primary Error Code. The

Return Code value is the Secondary Error Code. For

System Programmer Response: Correct the parameter

further explanation, look up the displayed error codes

data set specification to eliminate this message.

under either Chapter 22, “Include File Access Errors,”

on page 365, or “INCLUDE FILE ERRORS” in the

ARI0005E

{JCL|xxxxxxxx} - yyyyyyyy parameter is

HELP text.

specified more than once.

System Action: The database manager ends.

Explanation: JCL indicates that the parameter in error

Operator Response: Refer this message to your

was specified in the job control.

system programmer.

xxxxxxxx is the name of the parameter data set which

System Programmer Response: Either:

contains the parameter in error.

DB2 Server for VSE System Control - ARI0001-ARI0199

yyyyyyyy is the parameter keyword that was specified

caused by coding ...,=value,

more than once in the initialization parameter input.

ARI0008E

{JCL|OPER|xxxxxxxx} - yyyyyyyy = c is

Note: The same parameter keyword can be specified

invalid. It must be d.

once in the job control and once in the parameter

data set.

Explanation: JCL indicates that the parameter in error

was specified in the job control.

System Action: If this error occurs in the job control

parameter processing, the database manager ends.

OPER indicates that the parameter in error was

specified during run time using the SET operator

If this error occurs during parameter data set

command.

processing, the database manager ends unless the

yyyyyyyy parameter is correctly specified in the job

xxxxxxxx is the name of the parameter data set which

control. See System Programmer Response.

contains the parameter in error.

Operator Response: Refer this message to your

yyyyyyyy is the initialization parameter keyword which

system programmer.

has the invalid parameter value. It must be one of the

following keywords: ACCOUNT, ALTLOG,

System Programmer Response: Remove the extra

ARCHTAPE, DSPLYDEV, DSPSTATS, DUALLOG,

occurrences of the initialization parameter from either

DUMPTYPE, EXPAND, EXTEND, LOGMODE,

the job control or the parameter data set. If this

STARTUP, SECALVER, SECTYPE, SYNCPNT,

parameter was specified more than once in the

SYSMODE, TAPEMGR or TCPRETRY.

parameter data set, it may be overridden by a correct

specification in the job control. However, the message

c is the first (or only) character of the invalid parameter

will still be issued but may be ignored and the

value. If no value was specified, a comma is substituted

database manager will continue processing.

for the missing value. If more than one character is

given for the parameter value, it will not be accepted

even if the first character is valid.

ARI0006E

{JCL|xxxxxxxx} - yyyyyyyy is an invalid

parameter specification.

d is a character string indicating the correct parameter

value as follows:

Explanation: JCL indicates that the parameter in error

yyyyyyyy

(default)

was specified in the job control.

--------

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

---------

xxxxxxxx is the name of the parameter data set which

ACCOUNT

D, T, E, or N

contains the parameter in error.

ALTLOG

N or Y

ARCHTAPE REW or UNL

REW

yyyyyyyy is the initialization parameter keyword which

DSPLYDEV

L, C, or B

is invalid (or misspelled). If the parameter keyword in

DSPSTATS

0, 1, or 2

error was greater than eight characters, only the first

DUALLOG

N or Y

nine characters are printed.

DUMPTYPE

P, F, or N

EXPAND

DBSPACE or ALL

DBSPACE

System Action: The database manager ends.

EXTEND

Y or N

LOGMODE

Y, A, L, or N

Operator Response: Refer this message to your

SECALVER

N or Y

system programmer.

SECTYPE

DB2 or ESM

DB2

STARTUP

C, E, F, I, L, M,

System Programmer Response: Correct the invalid

P, R, S, U, or W

initialization parameter specification in either the job

control or the parameter data set.

SYNCPNT Y or N

SYSMODE M or S

TAPEMGR Y or N

ARI0007E

{JCL|xxxxxxxx} error. A keyword is

TCPRETRY Y or N

missing.

System Action: If this error occurs in the job control

Explanation: JCL indicates that the parameter in error

parameter processing, the database manager ends.

was specified in the job control.

If this error occurs during parameter data set

xxxxxxxx is the name of the parameter data set which

processing, the database manager ends unless the

contains the parameter in error.

yyyyyyyy parameter is correctly specified in the job

System Action: The database manager is ended.

control. See System Programmer Response.

Operator Response: Refer this message to your

If this error occurs while processing the SET command,

system programmer.

the command is ignored and processing continues.

System Programmer Response: Correct the invalid

Operator Response: Refer this message to your

initialization parameter specification in either the job

system programmer.

control or the parameter data set. This error would be

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

System Programmer Response: Correct the invalid

(2 x NCUSERS)

parameter value in the job control, the parameter data

NLRBU

583233

1000

set, or the operator console. If the invalid parameter

NPACKAGE

32766/NCUSERS

NPACKPCT

100

was specified in the parameter data set, it may be

NPAGBUF

400000

(4 x NCUSERS) + 10

overridden by a correct specification in the job control.

PROCMXAB

255

However, the message will still be issued but may be

PTIMEOUT

99999

180

ignored and the database manager will continue

RMTUSERS

65535

processing.

SLOGCUSH

100

SOSLEVEL

100

TCPDISPB

100

ARI0009E Format 1:

TCPMAXRT

9999

158

{JCL|OPER|xxxxxxxx} - yyyyyyyy = c is

TCPPORT

65535

446

invalid. It must be in the range from n1

TRACEBUF

99999

to n2.

Format 2:

System Action: If this error occurs in the job control

{JCL|OPER|xxxxxxxx} - yyyyyyyy = c is

parameter processing or during parameter data set

invalid. It must be in the range from n1

processing, the database manager ends.

to n2 or d.

If this error occurs while processing the SET operator

Explanation: JCL indicates that the parameter in error

command, the command is ignored and processing

was specified in the job control.

continues.

OPER indicates that the parameter in error was

Operator Response: Refer this message to your

specified during run time using the SET operator

system programmer.

command.

System Programmer Response: Correct the invalid

xxxxxxxx is the name of the parameter data set which

parameter value in the job control, the parameter data

contains the parameter in error.

set, or the operator console. If the invalid parameter

was specified in the parameter data set, it may be

yyyyyyyy is the parameter keyword which has the

overridden by a correct specification in the job control.

invalid parameter value. It must be one of the

However, the message will still be issued but may be

following keywords: ARCHPCT, CHKINTVL,

ignored and the database manager will continue

DBSPNUM, DISPBIAS, LTIMEOUT, NCSCANS,

processing.

NCUSERS, NDIRBUF, NLRBS, NLRBU, NPACKAGE,

NPACKPCT, NPAGBUF, PROCMXAB, PTIMEOUT,

RMTUSERS, SLOGCUSH, SOSLEVEL, TCPDISPB,

ARI0010E

{JCL|xxxxxxxx} -

TCPMAXRT, TCPPORT, or TRACEBUF.

{TRACDBSS|TRACCONV|TRACRDS|

TRACDSC|TRACWUM|TRACDRRM

c is the invalid parameter value. If no value was

|TRACSTG} is invalid. The parameter

specified, a comma is substituted for the missing value.

value must be either {0, 1, or 2 | 0 or 1}.

If the parameter is longer than eight characters, only

the first eight characters are displayed. The parameter

Explanation: JCL indicates that the parameter in error

value can be up to eight characters. Leading zeros are

was specified in the job control.

suppressed.

xxxxxxxx is the name of the parameter data set which

n1 is the lower limit (or minimum) for the correct

contains the parameter in error.

parameter value.

Specifying a parameter value other than 0, 1, or 2 for

n2 is the upper limit (or maximum) for the correct

the TRACDBSS, TRACCONV, TRACRDS, TRACDSC,

parameter value.

TRACWUM, or TRACDRRM initialization parameter is

invalid. Specifying a parameter value other than 0 or 1

d is the non-numeric value that can also be used for the

for the TRACSTG initialization parameter is invalid.

parameter value.

System Action: If this error occurs in the job control

yyyyyyyy

(default)

parameter processing, the database manager ends. If

--------

---------

this error occurs during parameter data set processing,

ARCHPCT

the database manager ends unless the TRACDBSS,

CHKINTVL

99999999

TRACCONV, TRACRDS, TRACDSC, TRACWUM,

DBSPNUM

32000

TRACDRRM, or TRACSTG parameter is correctly

DISPBIAS

specified in the job control. See System Programmer

LTIMEOUT

99999

Response.

NCSCANS

655

NCUSERS

252

Operator Response: Refer this message to your

NDIRBUF

400000

NPAGBUF

system programmer.

NLRBS

Larger

583333

(2 x NCUSERS) +

System Programmer Response: Correct the invalid

of 50 or

(NLRBU x NCUSERS)/2 +10

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

initialization parameter value in either the job control

ARI0012I

The database manager ignores yyyyyyyy

or the parameter data set. If the invalid parameter was

= c when zzzzzzzz = d.

specified in the parameter data set, it may be

overridden by a correct specification in the job control.

Explanation: yyyyyyyy is the initialization parameter

However, the message will still be issued but may be

keyword of the value that is ignored.

ignored and the database manager will continue

c is the parameter value that was specified.

processing.

zzzzzzzz is the initialization parameter keyword that is

used and causes the yyyyyyyy parameter to be ignored.

ARI0011E

{JCL|xxxxxxxx} - yyyyyyyy is invalid.

The parameter string must be from 1 to

d is the parameter value specified for zzzzzzzz.

n characters.

yyyyyyyy

zzzzzzzz

--------

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

--------

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

Explanation: JCL indicates that the parameter in error

ACCOUNT

T, D, or E

STARTUP

C, E, I, L, M,

was specified in the job control.

P, or S

xxxxxxxx is the name of the parameter data set which

ACCOUNT

D, T, or E

PROGNAME

ARISEGB

contains the parameter in error.

ACCOUNT

D, T, or E

PROGNAME

ARISRMG

ALTLOG

N or Y

SYSMODE

yyyyyyyy is the initialization parameter keyword which

ALTLOG

N or Y

STARTUP

E, I, M,

has the invalid parameter string length. It must be one

S, U, or

of the following keywords: CHARNAME, DBNAME,

ARCHPCT

value

LOGMODE

Y or N

DBPSWD, DSPSTATS, PARMID, PROGNAME,

DISPBIAS

value

SYSMODE

DBSPNUM

value

STARTUP

C, E, I,

L, M

TRACCONV, TRACDBSS, TRACRDS, TRACDSC,

S, U, or

TRACWUM, TRACDRRM, or TRACSTG.

DUALLOG

N or Y

SYSMODE

n is the maximum character string length of the value.

DUALLOG

N or Y

STARTUP

E, F, I,

M, P, R,

S, U, or

yyyyyyyy

NCUSERS

value > 1

SYSMODE

---------

-----

PROCMXAB

non-zero value

SYSMODE

CHARNAME

PROGNAME

program-name

SYSMODE

DBNAME

PROGNAME

program-name

STARTUP

C, E, I,

L, M,

DBPSWD

P, or S

DSPSTATS

PTIMEOUT

non-zero value

SYSMODE

PARMID

RMTUSERS

non-zero value

SYSMODE

PROGNAME

TCPDISPB

value > 1

RMTUSERS

TRACCONV

TCPMAXRT

value

TCPPORT

TRACDBSS

TCPPORT

non-zero value

SYSMODE

TRACRDS

TCPRETRY

TCPPORT

TRACDSC

TRACDRRM

non-zero value

RMTUSERS

TRACWUM

1 or 2

RMTUSERS

TRACDRRM

SECALVER

N or Y

SYSMODE

TRACSTG

SECTYPE

DB2 or ESM

SYSMODE

System Action: If this error occurs in the job control

SYNCPNT

RMTUSERS

LTIMEOUT

non-zero value

SYSMODE

parameter processing, the database manager ends.

Notes:

If this error occurs during parameter data set

processing, the database manager ends unless the

1. The database manager ignores the PROCMXAB and

yyyyyyyy parameter is correctly specified in the job

PTIMEOUT parameters when SYSMODE=S because

control. See System Programmer Response.

they have no significance in single user mode. They

are supported only in multiple-user mode.

Operator Response: Refer this message to your

system programmer.

System Action: Processing continues.

System Programmer Response: Correct the invalid

Operator Response: Refer this message to your

initialization parameter value in either the job control

system programmer.

or the parameter data set. If the invalid parameter was

System Programmer Response: Remove the

specified in the parameter data set, it may be

initialization parameter specification causing the

overridden by a correct specification in the job control.

message.

However, the message will still be issued but may be

ignored and the database manager will continue

processing. PARMID is valid only on the job control

ARI0013E yyyyyyyy must be c when zzzzzzzz = d .

and, therefore, must always be corrected.

Explanation: yyyyyyyy is the initialization parameter

keyword of the value that is in conflict.

c is the parameter value that was specified.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

zzzzzzzz is the initialization parameter keyword that is

ARI0015I

yyyyyyyy parameter value is c.

used and causes the yyyyyyyy parameter specification

to be invalid.

Explanation: This message displays the final values

used by the database manager as a result of the

d is the parameter value specified for zzzzzzzz.

merging of job control, default parameter values.

yyyyyyyy c

zzzzzzzz d

--------

-------

--------

yyyyyyyy is the initialization parameter keyword.

c is the parameter value to be used by the database

LOGMODE Y

STARTUP L

manager.

LOGMODE Y, A,

SYSMODE M

or L

yyyyyyyy

STARTUP W, R,

EXTEND

---------

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

U, or F

ACCOUNT

D, T, E, or N

STARTUP W, R,

SYSMODE M

ALTLOG

N or Y

U, or F

ARCHTAPE

REW or UNL

CHARNAME

character-set-name

System Action: If this error occurs in the job control

DBNAME

database name, up to 18 characters

parameter processing, the database manager ends.

DSPLYDEV

L, B, or C

DSPSTATS

0, 1, or 2

If this error occurs during parameter data set

DUALLOG

N or Y

processing, the database manager ends unless the

DUMPTYPE

P, F, or N

yyyyyyyy parameter is correctly specified in the job

EXTEND

Y or N

control. See System Programmer Response.

LOGMODE

Y, A, L, or N

PARMID

parameter-data-set-name

Operator Response: Refer this message to your

PROGNAME

program-name

system programmer.

SECALVER

Y or N

System Programmer Response: Correct the invalid

SECTYPE

DB2 or ESM

initialization parameter value in either the job control

STARTUP

C, E, F, I, L, M, P, R,

or the parameter data set. If the invalid parameter was

S, U, or W

specified in the parameter data set, it may be

SYSMODE

M or S

overridden by a correct specification in the job control.

TAPEMGR

Y or N

However, the message will still be issued but may be

TCPRETRY

Y or N

ignored and the database manager will continue

TRACCONV

0, 1, or 2

processing.

RMTUSERS

0 - 65535

TRACDBSS

0, 1, or 2

TRACRDS

0, 1, or 2

ARI0014E The database manager requires

TRACDSC

0, 1, or 2

PROGNAME when SYSMODE = S

TRACWUM

0, 1, or 2

AND STARTUP = {W|R}.

TRACDRRM

0, 1, or 2

TRACSTG

0 or 1

Explanation: When SYSMODE=S and STARTUP=W

(or STARTUP=R) is specified, the PROGNAME

System Action: Processing continues.

initialization parameter must be specified.

Notes:

System Action: If this error occurs in the job control

1. The DBPSWD parameter value will not be

parameter processing, the database manager ends. If

displayed.

this error occurs during parameter data set processing,

2. DUALLOG and ALTLOG will be displayed only if

the database manager ends unless the PROGNAME or

STARTUP=C or STARTUP=L.

SYSMODE or STARTUP parameter is correctly specified

in the job control. See System Programmer Response.

3. PARMID will be displayed only when specified.

4. PROGNAME will be displayed only when

Operator Response: Refer this message to your

SYSMODE=S and STARTUP=W, R, F, or U.

system programmer.

System Programmer Response: You may want to

System Programmer Response: Either specify the

verify that the initialization parameter values are

PROGNAME initialization parameter or correct the

correct.

invalid parameter value (SYSMODE or STARTUP) in

either the job control or the parameter data set that is

causing this message. If this parameter was specified

ARI0016I

yyyyyyyy parameter value is n.

more than once in the parameter data set, it may be

Explanation: This is an information message that

overridden by a correct specification in the job control.

displays the final values used by the database manager

However, the message will still be issued but may be

as a result of the merging of job control, parameter data

ignored and the database manager will continue

set, and default parameter values.

processing.

yyyyyyyy is the initialization parameter keyword.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

n is the parameter value to be used by the database

Operator Response: Refer this message to your

manager.

system programmer.

yyyyyyyy n

System Programmer Response: Remove the

---------

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

DBNAME specification.

ARCHPCT

10 to 99

CHKINTVL

1 to 99999999

ARI0022E Field procedure fieldproc-name has

DBSPNUM

1 to 32000 or *

abnormally terminated. Please remove it

DISPBIAS

1 to 10

from your installation.

LTIMEOUT

0 to 99999

NCSCANS

1 to 655

Explanation: The field procedure fieldproc-name has

NCUSERS

1 to 252

abended. You must remove the procedure from the

NDIRBUF

10 to 400000

system before restarting the system. Executing field

NLRBS

50 to 583333

procedures that contain errors can affect the security

NLRBU

10 to 583233

and integrity of the database. Thoroughly test the field

NPACKAGE

1 to 32766/NCUSERS

procedure before reinstalling it on your system.

NPACKPCT

0 to 100

NPAGBUF

10 to 400000

System Action: The application server will produce a

PROCMXAB

0 to 255

mini-dump. When possible, processing will continue.

PTIMEOUT

0 to 99999

SLOGCUSH

11 to 100

Operator Response: Save the console output for the

SOSLEVEL

1 to 100

system programmer.

TCPDISPB

1 to 100

TCPMAXRT

1 to 9999

System Programmer Response: Remove the field

TCPPORT

0 to 65535

procedure from your system before restarting the

TRACEBUF

0 to 99999

database manager. Ensure that the field procedure is

thoroughly tested before reinstalling it.

System Action: Processing continues.

Note: The ARCHPCT parameter is displayed only if

ARI0023I

The program-name program will be

LOGMODE=A.

invoked in AMODE amode.

System Programmer Response: You may want to

Explanation: The program-name program will be

verify that the initialization parameter values are

started in the addressing mode amode specified. This

correct.

could be either 24-bit or 31-bit addressing. Note that

this addressing mode corresponds to the addressing

mode of the application program. If the application

ARI0017E An error occurred in the parameter

program is a DBS utility or a DB2 Server for VSE

specification.

preprocessor, the addressing mode will always be

Explanation: One or more errors were found while

AMODE 24. This message is issued before invoking the

processing the initialization parameters. Previous

single-user-mode application program-name.

messages indicate the parameter in error and the

System Action: Processing continues.

correction.

System Programmer Response: If the amode is not

System Action: The database manager ends.

what you want, refer to the appropriate application

Operator Response: Refer this message to your

programming language manual.

system programmer.

System Programmer Response: Correct the invalid

ARI0024E DBCS conversion procedure

initialization parameter value in either the job control

transproc-name has abnormally

or the parameter data set. If the invalid parameter was

terminated. Please remove it from your

specified in the parameter data set, it may be

installation.

overridden by a correct specification in the job control.

Explanation: The DBCS conversion procedure

transproc-name has abended. Thoroughly test the

ARI0018I

{JCL|xxxxxxxx} - DBNAME parameter is

procedure before re-installing it on your system. If you

ignored for VSE/AF.

want to replace or remove this procedure from your

system, contact your system programmer.

Explanation: JCL indicates that the parameter in error

was specified in the job control.

System Action: The application server will produce a

mini-dump. When possible, processing will continue.

xxxxxxxx is the name of the parameter data set which

contains the parameter in error.

Operator Response: Save the console output for the

system programmer.

System Action: Processing continues. The specified

keyword is ignored.

System Programmer Response: Determine the CCSID

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

conversions that use this DBCS conversion procedure

went wrong and contact the designated support group

by checking the TRANSPROC column of the catalog

for your installation.

table SYSTEM.SYSSTRINGS. Refer to the DB2 Server for

VSE System Administration manual for information on

ARI0027E

A communication link error has

updating these CCSID conversions to make use of

occurred.

another DBCS conversion routine.

Explanation: The database manager has violated the

use of the CPC services. The most probable causes may

ARI0025I

The program program-name is loaded at

be:

load-address.

v Control blocks related to the use of communication

Explanation: program-name is the name of the phase

services were damaged.

loaded by the database manager.

v Registers or register save areas used by the database

load-address is the storage address (expressed in

manager in performing communication functions

hexadecimal) where the phase was loaded.

may have had their contents altered.

System Action: Processing continues.

(See Chapter 20, “DB2 Server for VSE Reason Codes,”

System Programmer Response: You may want to note

on page 355.)

the address for use in any potential problem

System Action: The database manager is ended.

determination.

Operator Response: Refer this message to your

system programmer.

ARI0026E An error occurred in the attempt to load

program xxxxxxxx.

System Programmer Response: Perform problem

determination. If a database system error occurred,

Explanation: xxxxxxxx is the name of the phase that

make a record of what went wrong and contact the

the application server attempted to load.

designated support group for your installation.

The reason code is the system return code (from the

CDLOAD macro):

ARI0028I

The database manager is terminating.

v If an internal VSE system error occurred while

attempting to get storage, the reason code is 8

Explanation: This informational message is issued as

(X’08’).

acknowledgment when an SQLEND command (other

than SQLEND QUICK) is first entered.

v If all available GETVIS storage has been exhausted,

the reason code, normally displayed at end-of-job, is

Note: SHUTDOWN is a valid synonym for SQLEND.

(X’0C’).

v If the partition CDLOAD directory (anchor table) is

System Action: The database manager will start

full, the reason code is 16 (X’10’).

termination procedures; all active users (DB2 Server for

VSE agent structures) will be allowed to complete their

v If the phase does not exist in the library core image

processing. No new users will be allowed access to

member, the reason code is 20 (X’14’).

database services. After all active users have completed

v If a hardware error occurred while attempting to get

their processing, the database manager will perform

storage for the phase, the reason code is 32 (X’20’).

any optional functions specified on the SQLEND

command and end.

Note: The reason codes are the VSE/Advanced

Functions CDLOAD return codes.

ARI0029I

n communication links are still

System Action: The database manager is ended.

connected.

Operator Response: If the reason code indicates

Explanation: This informational message tells the

insufficient storage, restart the application server after

operator how many users are active when the SQLEND

allocating a larger partition. For all other reason codes,

command was entered. This number is the number of

notify your system programmer.

agent structures containing connected users.

System Programmer Response: Catalog the phase in

This message is issued when an SQLEND command

the library core image member if not found. You may

(other than SQLEND QUICK) is first issued. It is also

have to assist the operator in determining what

issued with an updated number as each

partition size will be needed if insufficient GETVIS

communication link is disconnected. This may allow

storage is the problem.

the operator to determine how long it might take to

complete the SQLEND process.

If the problem is a hardware error, contact your

installation hardware service representative. If a

database system error occurred, make a record of what

Note: SHUTDOWN is a valid synonym for SQLEND.

System Action: Processing continues.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

make a record of what went wrong and contact the

ARI0030I

Database manager termination is

designated support group for your installation.

already in progress.

Explanation: This informational message is issued in

ARI0034E An error occurred during termination.

response to a subsequent SQLEND command (other

than SQLEND QUICK).

Explanation: This message is issued whenever

database manager termination is in progress and an

System Action: Processing continues and the

error (for example: a program check) occurs which

command is ignored.

causes the termination process to be invoked. This

Operator Response: None unless an immediate

message is also issued if the operator enters a CANCEL

shutdown is required, in which case an SQLEND

command after message ARI0032I has been displayed.

QUICK command can be issued. If that command is

issued, any logical units of work in progress will be

Note: Tape files may not have been closed and may be

resolved (either committed or backed out) the next time

missing the last buffer contents and have no tape

the database manager is brought up.

mark (EOF indicator).

System Action: The database manager ends

Note: SHUTDOWN is a valid synonym for SQLEND.

immediately.

Operator Response: Notify your system programmer.

ARI0031E Invalid SQLEND parameter.

You may wish to write a tapemark on any open tape

Explanation: The SQLEND command was entered

files.

with an invalid parameter. The operator should specify

System Programmer Response: Perform problem

only a valid SQLEND command. For more information,

determination. If a database system error occurred,

refer to the DB2 Server for VSE & VM Operation manual.

make a record of what went wrong and contact the

designated support group for your installation.

Note: SHUTDOWN is a valid synonym for SQLEND.

System Action: Operator command processing ends.

ARI0035I

Application server cancel has been

Operator Response: Reenter the command correctly.

requested.

Explanation: The operator has issued a CANCEL

ARI0032I

The database manager has terminated.

command or an I/O cancel has been issued by another

VSE system component. The operator is allowed to

Explanation: This informational message is issued

request a dump if desired. See message ARI0044D.

prior to closing any data sets and ending.

System Action: The database manager ends.

Note: The operator should not enter a CANCEL

command after this message has been displayed.

ARI0036E No SAVEAREA found for ARIXRDS.

It will cause immediate termination of the

database manager with the message ARI0034E

Explanation: A program check interrupt occurred in

being displayed.

the package. The database manager attempted to

recover, but could not find the save area for the RDS

Note: If the database manager has ended abnormally, a

recovery routine (ARIXEBR).

DB2 Server for VSE mini-dump will be

System Action: The database manager ends.

displayed. These dumps are described in the

DB2 Server for VSE & VM Diagnosis Guide and

Operator Response: Refer this message to your

Reference manual.

system programmer.

System Action: The database manager is ended.

System Programmer Response: Perform problem

determination. If a database system error occurred,

make a record of what went wrong and contact the

ARI0033E An error occurred while attempting to

designated support group for your installation.

close SYSLST.

Explanation: Termination could not properly close the

ARI0037E The entry point for ARIXEBR1 cannot

printer file used for error and informational messages.

be found.

System Action: Database manager termination

Explanation: A program check interrupt occurred in

continues.

the package. The database manager attempted to

Operator Response: Notify your system programmer.

recover, but could not find the entry point to the RDS

recovery routine (ARIXEBR1).

System Programmer Response: Perform problem

determination. If a database system error occurred,

System Action: The database manager is ended.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

Operator Response: Refer this message to your

ARI0040E A database manager system error

system programmer.

occurred - ARIxxxx nn.

System Programmer Response: Perform problem

Explanation: An internal error occurred within the

determination. If a database system error occurred,

database manager system. Usually a "should not occur"

make a record of what went wrong and contact the

condition has occurred. A dump will be taken

designated support group for your installation.

according to the DUMPTYPE initialization parameter.

This is a system error.

ARI0038E Invalid return code from ARIxxxx.

ARIxxxx is the name of the module that detected the

Explanation: An internal error has occurred.

error.

ARIxxxx is the name of the module which returned an

nn is the error detection point within the module. See

unexpected or invalid return code to the caller.

Chapter 24, “System Errors,” on page 371 for a list of

communication link errors.

System Action: The database manager ends.

Notes:

Operator Response: Refer this message to your

1. If the database manager has ended abnormally, a

system programmer.

mini-dump will be displayed. These dumps are

System Programmer Response: Perform problem

described in the DB2 Server for VSE & VM Diagnosis

determination. If a database system error occurred,

Guide and Reference manual. Refer also to message

make a record of what went wrong and contact the

ARI0042I for additional diagnostic information.

designated support group for your installation.

2. If this message is preceded by a VSAM ERROR

display, refer to the topic about VSAM errors in the

ARI0039E Application server limit error occurred -

DB2 Server for VSE & VM Diagnosis Guide and

ARIxxxx nn.

Reference manual.

Explanation: This message is usually due to causes

System Action: The database manager ends.

such as:

Operator Response: Refer this message to your

v Insufficient partition GETVIS storage.

system programmer.

v Phase not found.

System Programmer Response: Perform problem

v Insufficient external storage space for functions such

determination. If a database system error occurred,

as DB2 Server for VSE logging.

make a record of what went wrong and contact the

designated support group for your installation.

Other messages issued prior to this message will

identify the error condition and aid in the corrective

ARI0041E System hardware error occurred -

action to be taken.

ARIxxxx nn.

ARIxxxx is the name of the module which detected the

Explanation: A hardware error was detected during a

limit error.

GETVIS, CDLOAD, I/O, etc. operation.

ARIxxxx is the name of the module that detected the

nn is the error detection point within that module. See

error.

Chapter 23, “Limit Errors,” on page 367 for a list of

critical detection points and their related error

nn is the error detection point in the module.

conditions.

A preceding message describes the cause of the

hardware error. A dump or mini-dump will not be

No DB2 Server for VSE dump or mini-dump will be

taken if a hardware error occurs.

displayed because a limit error occurred.

System Action: The database manager ends.

System Action: The database manager is ended.

Operator Response: Refer this message to your

Operator Response: If the error is due to insufficient

system programmer.

GETVIS storage, restart the database manager after

allocating a larger partition.

System Programmer Response: Perform problem

determination. If a hardware error is indicated, report

System Programmer Response: You may have to

this problem to the hardware service person at your

reallocate external storage space, catalog missing

installation. If a database system error occurred, make a

phases into the library core image member, or assist the

record of what went wrong and contact the designated

operator in allocating a larger partition size.

support group for your installation.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

when a problem such as a trace file close error

ARI0042I

Database manager reason code is n1 -

occurred. The next job step, if processing the

X’n2’.

trace file, probably will not be able to proceed.

Explanation: This code is a VSE system return code

512

The database manager ended, but a limit error

returned to the database manager. It can be used for

occurred (see message ARI0039E). Execution of

problem determination.

any subsequent job steps will probably result

n1 is the decimal representation of the reason code.

in a failure.

n2 is the hexadecimal representation of the reason code.

516

The database manager ended, but an error

occurred. (See message ARI0040E). This code

Note: A previous message should have been displayed

is also returned if the operator enters a

related to the reason code. See Chapter 20, “DB2

CANCEL command. Execution of any

Server for VSE Reason Codes,” on page 355 and

subsequent job steps will probably result in a

Chapter 17, “DBSS Return Codes,” on page 231

failure.

for additional information about the reason

520

The database manager ended but a hardware

codes.

error occurred. (See message ARI0041E).

System Action: The database manager ends.

Execution of any subsequent job steps will

probably result in a failure.

Operator Response: Refer this message to your

system programmer.

For nonzero return codes, see previous database

System Programmer Response: Note the reason code

manager error messages.

for problem determination.

Note: When the database manager is operating in

single user mode: If this message is accompanied

ARI0043I

Database manager return code is n.

by message ARI0046I, the return code passed

Explanation: This return code is for informational

back to the system will be the code from the

purposes. Except for return code 0, it is related to any

database system.

earlier DB2 Server for VSE messages that have been

System Action: Database manager termination

displayed. This return code is also returned to VSE

continues.

upon return by the database manager.

n is one of the following:

ARI0044D If you want a dump, enter 1(Yes).

The database manager ended normally.

Otherwise enter 0(No).

An error exists while processing the JCL job

Explanation: The abnormal termination routine has

that starts the database manager software.

been entered due to an operator or I/O cancel request.

Contact the designated database manager

If a dump is required, the operator must reply with a 1

support group for your installation.

or YES to the message. If 0 or NO is entered, no dump

will be taken. Any other reply will cause message

256

An error exists while processing the JCL job

ARI0052E to be displayed. The dump to be taken is

that starts the database manager software.

determined by the DUMPTYPE initialization parameter

Contact the designated database manager

(DUMPTYPE=P, F, or N). If DUMPTYPE=N was

support group for your installation.

specified, the default DUMPTYPE=F is assumed.

504

The database manager ended, but a problem

System Action: Processing continues as determined by

occurred. Possible problems are a printer close

the operator reply.

error, VSAM close error, etc. The next job step

can usually proceed.

Operator Response: Reply 1 or YES if a dump is

required. Reply 0 or NO if no dump is required.

506

An XPCC IDENT failed. If this message is

preceded by ARI0042I, the reason code 36

(X’24’) displayed in ARI0042I indicates that a

ARI0045I

Ready for operator communications.

duplicate subsystem name already exists. This

Explanation: This informational message is issued

will happen if a DB2 Server for VSE partition

only in multiple user mode. It informs the system

is being brought up while the same default

operator that the database manager is ready to accept

subsystem name has been used to logon for an

DB2 Server for VSE operator commands.

application server under VM in a Guest

Sharing environment, or vice versa.

Operator Response: Enter any operator commands

desired.

508

The database manager ended. This return code

is returned when an SQLEND QUICK

(SHUTDOWN QUICK) has been issued or

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

v File I/O error (on a GET, PUT, OPEN, or

ARI0046I

xxxxxxxx return code is n1 - X’n2’.

CLOSE).

Explanation: This message occurs only when the

v Get/release virtual storage failure.

database manager is operating in single user mode. It

v Preprocessor invocation parameter error.

reports a nonzero application return code (passed back

in register 15) when the application program returns to

v SQL error, such as preprocessor cannot

the database manager.

connect to the database manager using the

user ID or password provided to it (either

xxxxxxxx is the name of the application program

explicitly or implicitly), or preprocessor

(specified in the PROGNAME initialization parameter).

experienced an internal SQL error during

preprocessor initialization or shutdown.

n1 is the decimal representation of the return code.

Severe SQL error. Preprocessor cannot

n2 is the hexadecimal representation of the return code.

continue. Probable causes are:

Some application programs (such as those written in

v Package was not in the catalog or was not

COBOL or FORTRAN) do not pass back a zero return

usable when an attempt was made to use it.

code upon successful completion. If the application

v Communication path to the database

program does not make the return code zero, whatever

manager has been disabled.

value is in register 15 will be displayed as the return

code. This value is normally the entry point address of

v Error occurred while trying to free

the application program; it is typically a large value.

dynamically allocated virtual storage.

v Unrecoverable system error occurred.

IBM-supplied DB2 Server for VSE programs (for

example, a preprocessor or the DBS utility) that run in

v Attempt to process an SQL command before

single user mode will also have their return codes

the database manager was started or ready.

displayed in this message.

v Error during attempt to open or write to a

FORTRAN list file.

If the name of the application program given in the

message is one of the preprocessors:

ARIPRPA

Assembler Preprocessor

Return codes 12 and 16 are called preprocessor

ARIPRPB

C Preprocessor

terminating errors. The preprocessor halts at the point

ARIPRPC

COBOL Preprocessor

of the error and performs its cleanup processing:

ARIPRPF

FORTRAN Preprocessor

v Flushes the input source file.

ARIPRPP

PL/I Preprocessor

v Frees any previously allocated virtual storage.

v Merges workfiles into output files (for COBOL only).

the following return codes apply:

v Closes any open files.

No errors and no warnings.

v Restores the previous state of the package.

The preprocessor BLOCK option was specified

v Handles the preprocessor return code.

and

v One or more cursor operations are ineligible

If the name of the application program given in the

for blocking, or

message is the DBS utility (ARIDBS), the following

v One or more SELECT statements were

return codes apply:

encountered (SELECT statements cannot be

All commands processed successfully.

blocked).

An error occurred during DBS utility

Preprocessor or SQL warning. Either:

termination. However, all requested processing

v A preprocessor warning message was

completed successfully. All changes were

issued.

committed to the database. No SQL or DBS

v An SQL warning message was issued

utility commands need to be reprocessed.

during the processing of an SQL command.

Errors have occurred during ERRORMODE

Preprocessor or SQL error. Either:

CONTINUE processing. Some commands

issued while SET ERRORMODE CONTINUE

v A preprocessor error message was issued.

was in effect were not processed successfully.

v An SQL error message was issued during

the processing of an SQL command; a

DBS utility processing error occurred. From

negative SQLCODE was returned.

the point of the error, no further commands

Preprocessing continues.

were executed, but later DBS utility commands

were checked for syntax errors.

Preprocessor or SQL error. Preprocessor cannot

continue. Probable causes are:

DBS control command file open error

occurred. No commands were processed.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

DBS message file open error occurred. No

when the VSE job accounting support (JA) is provided.

commands were processed.

This means that the JA option is specified on the IPL

SYS command.

Initialization error occurred. Not enough

virtual storage was available for DBS utility

System Action: If this condition occurs, DB2 Server

working storage areas. No commands were

for VSE accounting support is shut off, and the

processed.

database manager is ended.

Operator Response: Refer this message to your

When the database manager is started for database

system programmer.

generation (STARTUP=C is specified), the program

name is always ARIGCAT.

System Programmer Response: Re-IPL the system

with the JA option specified on the IPL SYS command.

When the database manager is started for log

Then restart the database manager.

reconfiguration (STARTUP=L is specified), the program

name is always ARISEGB.

ARI0052E response is incorrect. Please reenter the

correct response.

Unless the return code is 512 or greater, the application

return code is passed back to the system.

Explanation: An incorrect value (response in text) was

entered in response to the previous message. If response

System Action: Database manager termination

is blank, a null response (no response or blanks) was

continues.

entered.

Operator Response: None, unless otherwise requested

System Action: The previous message will be

by the application programmer.

re-displayed.

System Programmer Response: None, unless

Operator Response: Determine the valid response to

otherwise requested by the application programmer or

the previous message, and enter the valid response

by preceding messages if the application program is the

when the prompting message is re-displayed.

DB2 Server for VSE program.

ARI0053E An unexpected error occurred accessing

ARI0047E CDLOAD - Reason Code = nnn.

the application server at initialization.

Explanation: This message only occurs with message

DBSS Return Code = code.

ARI0026E. It is issued when an error other than "not

Explanation: During the database manager startup,

found" or "insufficient storage" occurs while the

the RDS module ARIXERO encountered unexpected

database manager is trying to load the program

problems when attempting to access the application

indicated in message ARI0026E.

server.

CDLOAD is the type of load operation being tried by

code is the DBSS return code from the open. Refer to

the database manager when the error occurred.

Chapter 17, “DBSS Return Codes,” on page 231.

nnn is the return code indicating the cause of the

System Action: The database manager is ended.

failure. Refer to the VSE manual that documents the

load operation in question.

Operator Response: Refer this message to your

system programmer.

This message is accompanied by a DB2 Server for VSE

dump (as specified by the DUMPTYPE initialization

System Programmer Response: Note the DBSS return

parameter) and message ARI0040E, except when the

code, make a record of what went wrong, and contact

program identified is ARICMOD. The return code in

the designated support group for your installation.

message ARI0043I is 516.

System Action: The database manager ends.

ARI0054E Unable to do COMMIT. DBSS Return

Code = return-code.

Operator Response: Notify your system programmer.

Explanation: During the database manager startup,

System Programmer Response: Make a record of

ARIXERO was unable to issue a COMMIT after

what went wrong and contact the designated support

opening the record catalog table RIDs, TIDs, and IIDs.

group for your installation.

return-code is the DBSS return code from the open.

Refer to Chapter 17, “DBSS Return Codes,” on page

ARI0051E Accounting support specified, but VSE

231.

job accounting support is not provided.

System Action: The database manager is ended.

Explanation: The DB2 Server for VSE accounting

support uses the VSE GETFLD macro to collect CPU

Operator Response: Refer this message to your

time on a user basis. This macro is supported only

system programmer.

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

System Programmer Response: Perform problem

information about it so that the problem can be

determination. If a database system error occurred,

recreated if necessary.

make a record of what went wrong and contact the

designated support group for your installation.

ARI0058E Message editing error {MSG ID = nnnn

| SQLCODE = nnnn}. Reason Code =

ARI0056I

Tracing terminates because of operator

nn.

request.

Explanation: This is a system error. A database

Explanation: During database initialization, you

component requested that a message be edited and

specified the parameters TRACCONV, TRACDBSS,

displayed. If SQLCODE appears in the message text,

TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or

the request was for the SQLCODE message associated

TRACSTG (or any combination). The initialization

with SQLCODE nnn. If MSG ID appears in the

dialog prompted the operator for the tape unit cuu or

message text, the request was for the database message

the reply DISK (output to disk) for the trace output file

ARInnnn (nnnn from message text).

(message ARI0092A) and the operator responded with

The exact cause of the message editing error is

CANCEL to the prompting message. This message

identified by the Reason Code=nn value in the message

indicates that database initialization is continuing but

text where:

with trace inactive ("output disabled").

A message number is outside a valid range.

System Action: Database initialization continues, but

with the trace inactive, the TRACCONV, TRACDBSS,

SQL code number is out of range.

TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or

This is an invalid DBCS substitution string.

TRACSTG parameters are overridden.

Message is not found in the repository.

Note: Since trace is "output disabled", the TRACE OFF

The repository is not found.

operator command must be entered before the

TRACE ON operator command can be entered.

Sequence number contains wrong or

non-existing message line number.

ARI0057E Message ARInnnn has formatting error.

Invalid buffer length.

Explanation: This is a database error. The message

You may be able to identify the lost message from the

identified by nnnn (that is, message prefix ARI) either:

displayed message number or SQLCODE and take

v Was too long to fit into the internal message buffer

appropriate action.

(20 lines and 68 bytes per line for the database

manager or 79 bytes per line for ISQL). Part of the

System Action: Processing continues as though the

message was truncated and not displayed.

lost message had been displayed. Subsequent messages

may clarify system activity.

v Had one or more variable substitution requests

which could not be performed. Either the variable

User Response: If the reason code is 04 and the

was not supplied by the requesting module or the

database machine is operating at a later release than

variable had an invalid length. The message line

your user machine, use the message number or

contains &n. or &na. (where n is the variable

SQLCODE in the message text to help you determine

number in the internal structure VARLIST and a is

the release level of the database machine.

an optional conversion alphabetic character). These

values identify the unresolved variables.

Operator Response: Save this message and, if

possible, any additional information about the

application program or the database manager program

For a multi-line message, the error may have occurred

which was running and notify your system

on any (or all) lines. The message in error precedes this

programmer.

message on the display terminal or printer.

Programmer response: See Operator Response.

System Action: Normal processing continues.

System Programmer Response: Save the message

Operator Response: Save the message output (this

output and any other information given to you by the

message and the message identified by nnnn) and

operator or programmer and report this problem to the

notify your system programmer.

designated support group for your installation. If the

Programmer response: Same as Operator Response.

application program using the database manager is

known, save information about it so that the problem

System Programmer Response: Save the message

can be recreated if necessary.

output and report this problem to the designated

support group for your installation. If the application

program using the database manager is known, save

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

ARI0059E Program cancelled due to insufficient

ARI0061E The operator command value value is too

virtual storage.

long.

Explanation: An attempt to acquire partition virtual

Explanation: The system operator or ISQL terminal

storage (using the VSE GETVIS macro) failed.

user has entered a database operator command which

has a command name or parameter which exceeds

System Action: The program will be canceled because

eighteen characters in length. Database operator

of insufficient virtual storage.

command names and parameters may not exceed

Operator Response: If the return code of 32 (X’20’)

eighteen characters. The first eighteen characters of the

from the GETVIS macro is displayed (see Note), a main

invalid value are displayed in the message. This error

storage hardware error was detected. Report this

may be caused by misspelling an operator command

problem to your installation hardware service person.

name or parameter or by omitting the blank required

between the parameters of the command or between

Otherwise, assume that there is not enough virtual

the command name and the first parameter.

storage and proceed as follows. Either run the failing

program in a larger partition or change the program

System Action: Operator command processing ends.

parameters so that it requires less virtual storage. If you

Operator Response: Use the VSE Attention routine to

are running a program with the database manager in

initiate communication with the database manager.

single user mode, you may be able to run it in a

Reenter the command with the correct value. For a

smaller partition while the database manager is

description of the database operator commands, see the

running in multiple user mode. Consult with your

DB2 Server for VSE & VM Operation manual.

database or VSE system programmer to help you.

User Response: Reenter the command with the correct

Note: An attempt is made to provide information

value. See the DB2 Server for VSE & VM Interactive SQL

about:

Guide and Reference manual.

v Calling module name (or address).

v Requested virtual storage size (in bytes).

ARI0062A dbname : Enter a DB2 Server for VSE

operator command.

v Reason code containing the operating system return

code (from the GETVIS macro). (See message

Explanation: The dbname is the name of the

ARI0042I.)

application server started in the partition. The system

v Database return code. (See message ARI0043I.)

operator has requested (using the VSE Attention

facility) communication with the database manager. The

A dump of the partition is issued if this attempt fails

database manager is prompting the operator to enter a

because of a lack of storage. The dump is displayed on

database operator command.

SYSLST.

System Action: The database manager will process the

System Programmer Response: See Operator

database operator command entered in response to this

Response.

prompting message.

Operator Response: Enter the desired database

ARI0060I

Database manager initialization

operator command.

complete.

Note: If you do not wish to enter a command, respond

Explanation: The database manager has completed the

to message ARI0062A by pressing only the Enter

initialization process in multiple user mode. It is ready

key. This will cause the database manager to end

to accept work requests from other partitions.

command processing until you again request

System Action: The database manager enters wait

communication with the database manager.

state, waiting for work requests from other partitions

and for system operator requests to enter operator

ARI0063I

You did not enter an operator command.

commands.

Explanation: The system operator has entered a null

Operator Response: Database application programs

line in response to a request to enter a database

including preprocessors, ISQL, and the Database

operator command, or ISQL has transmitted a blank

Services Utility program may be started in other

line for database operator command processing. This

partitions.

should not occur for ISQL (ISQL internal error).

Database operator commands may be entered from the

System Action: Operator command processing ends.

system operator console.

To enter another database operator command, you

must use the VSE Attention routine to initiate

communication with the database manager.

User Response: You may enter a database operator

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

command or an ISQL or SQL command. If you are in

ARI0066E An error occurred processing the

ISQL, this message indicates an internal error in ISQL.

operator command.

In this case, notify your system programmer.

Explanation: A database operator command was

System Programmer Response: If message ARI0063I

routed to the module which processes the command.

is received by an ISQL terminal user, ISQL is

The module detected an error and ended command

malfunctioning. Determine the service level of the

processing. If the error was an invalid command

database manager and report this problem to the

parameter, the module issued a message identifying the

designated support group for your installation.

error. If the module invoked database services which

detected an error (for example, I/O error), then the

ARI0064E You entered an invalid operator

operator received an error message due to the error.

command.

Note that in the last case, the operator command may

have come from an ISQL terminal but the specific error

Explanation: The operator or the ISQL terminal user

message is displayed to the operator.

has entered an operator command. Either:

System Action: Operator command processing ends.

v The command name is not a valid operator

command, or

Operator Response: Refer to the previous error

v The command name is a name other than COUNTER

message for the cause of the error and for corrective

or SHOW (ISQL command input only), or

action.

v The ARCHIVE operator command was entered with

User Response: If there is a previous error message

operands or LARCHIVE operator command was

indicating the cause of command failure, take the

entered with an operand besides INACTIVE.

corrective action indicated by that message. If there is

no previous error message, the command was not

Notes:

executed due to some error detected by the database

1. ISQL should process only COUNTER and SHOW as

manager (such as an I/O error) and the operator has

operator commands. Therefore, ISQL has an internal

been notified of the error. If the problem persists, you

error.

may wish to notify the system programmer of your

System Action: Operator command processing ends.

problem.

Operator Response: Initiate communication with the

System Programmer Response: Obtain the ISQL

database manager (use the VSE Attention routine) and

terminal user and operator error message output and

reenter the command with the correct name and

take the corrective action recommended or suggested

operands. For the descriptions of the database operator

by the error messages.

commands, see the DB2 Server for VSE & VM Operation

manual.

ARI0067E Invalid SHOW command entered.

User Response: You may enter a database operator

Explanation: This message was caused by the operator

command or an ISQL or SQL command. This message

or ISQL terminal entering:

indicates an internal error in ISQL. Notify your system

v The operator SHOW command with an invalid or

programmer.

omitted first operand

System Programmer Response: If message ARI0064E

v A SHOW command with an incorrect number of

is received by an ISQL terminal user, ISQL is

operands.

malfunctioning. Determine the service level of the

System Action: Operator command processing ends.

database manager and report this problem to the

designated support group for your installation.

Operator Response: Reenter the SHOW command

with the correct operands. For a description of this

command, refer to the DB2 Server for VSE & VM

ARI0065I

Operator command processing is

Operation manual.

complete.

User Response: Reenter the SHOW command with

Explanation: This message notifies the operator or the

the correct operands. For the description of SHOW

ISQL terminal user that a database operator command

commands, refer to the DB2 Server for VSE & VM

has successfully completed processing.

Operation manual. You may alternatively enter an ISQL

System Action: Normal processing continues. You can

or SQL command.

use the VSE Attention routine to start further

communication with the database manager.

ARI0068E Invalid SET command entered.

User Response: You may enter another database

Explanation: The operator SET command operand

operator command or an ISQL or SQL command.

was invalid or omitted.

System Action: Operator command processing ends.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

Operator Response: Reenter the SET command with

Note: The selected tape unit must be currently

the correct operand. For the description of this

unassigned.

command, refer to the DB2 Server for VSE & VM

2. Make the tape unit ready, with a labeled scratch

Operation manual.

tape mounted and properly positioned.

3. Enter the cuu of the selected tape unit.

ARI0069E READ MEMBER

sublibrary.membername FAILED,

Reply CANCEL if no tape is available, or if accounting

REASON=nn CODE=nn

is not desired, or if the ARI0075E error condition

cannot be corrected.

Explanation: During reading of the SYSIPT file, a

READ MEMBER statement was encountered. (The

READ MEMBER statement is described in the

ARI0074E Invalid response {BLANK|value} to

CHANGE TO PROGRAM DIRECTORY OR BOOK INFO

prompt message.

WENT TO.) While attempting to access and read the

Explanation: An incorrect value (value in message

VSE library source statement member specified in that

text) or no value (BLANK in message text) was entered

statement, an error occurred.

in response to message ARI0073A.

sublibrary identifies the sublibrary containing the

System Action: The accounting prompting message

member.

ARI0073A (to which the invalid response was entered)

membername identifies the library source statement

is redisplayed.

member to be read. REASON is the Primary Error

Operator Response: Determine the valid response to

Code, and CODE is the Secondary Error Code.

the accounting prompting message, and enter the valid

For further explanation, look up the displayed error

response when the prompting message is redisplayed.

codes under either Chapter 22, “Include File Access

Errors,” on page 365, or “INCLUDE FILE ERRORS” in

ARI0075E

{OPEN|CLOSE|GENCB} error on

the HELP text.

accounting file filename [cuu].

System Action: See subsequent database messages.

Reason Code = reason-code.

Normally this error condition causes the job to end.

Return Code = return-code.

[Error Code = error-code.]

User Response: Save this error message and give it to

the job submittor or the system programmer for

Explanation: In attempting to open or close the

problem resolution.

database accounting output file, or to generate the

ACB/RPL for a VSAM ESDS accounting file, an error

System Programmer Response: Take action based on

occurred. If accounting data is being written to tape,

the REASON and CODE values.

the cuu of the tape is provided in the message.

The file has the name indicated by filename, which is

ARI0073E Ready filename accounting output

either ARIACC1 or ARIACC2.

volume. Enter CUU or CANCEL.

If an error code is not displayed, the reason-code value is

Explanation: The database manager is requesting the

the primary error code and the return-code value is the

system operator to ready a tape unit for accounting

secondary error code. For further explanation, look up

output and to supply its cuu. The database accounting

the displayed reason code and return code under either

file will have the filename indicated by filename, which

Chapter 21, “Sequential File Errors,” on page 361, or

is either ARIACC1 or ARIACC2.

“SEQ FILE ERRORS” in the HELP text.

If this message is redisplayed after message ARI0075E

If an error code is displayed, the return-code is the

(indicating an accounting file open error), the database

contents of register 15 after VSAM processed the

manager is requesting corrective action for that

request macro. See the VSE/VSAM Messages and Codes

message, plus the operator action for ARI0073E.

manual for the possible cause of this error.

System Action: If the operator enters a cuu, the

System Action: If the error condition is a dynamic

indicated tape unit is dynamically assigned and

assignment error on OPEN, message ARI0073A

opened.

displays to allow the accounting output volume to be

If the operator enters CANCEL, accounting support is

respecified. If the error condition is something other

shut off, and the database manager ends.

than a dynamic assignment error on an OPEN, the

accounting support is shut off and the database

Operator Response: The database manager is

manager ends.

requesting the system operator to:

Operator Response: Report the message to your

1. Select a tape unit for the accounting output.

system programmer. For corrective action, look up the

displayed reason and return codes under either

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

Chapter 21, “Sequential File Errors,” on page 361, or

Save this message and give it to your system

“SEQ FILE ERRORS” in the HELP text. For VSAM

programmer. Do not try to process the output file.

errors, see the VSE/VSAM Messages and Codes manual

If accounting data is being written to tape, you can try

for the possible cause of this error.

to salvage the accounting data on the output tape by

using the VSE job control MTC WTM,cuu statement.

ARI0076D Write error on accounting file filename

System Programmer Response: For corrective action,

[cuu].

see Chapter 21, “Sequential File Errors,” on page 361

for the reason code and return code displayed. For

Reason Code = code Return Code = code

VSAM errors, refer to the VSE/VSAM Messages and

[Error Code = code]

Codes manual for the possible cause of this error.

Do you want to continue?

= terminate,

Note: Although you may have partial accounting

Yes = continue without accounting,

output, it may not be cleanly processed because

Alt = continue but use alternate file.

the file was not closed.

Enter 0(No), 1(Yes), or 2(Alt).

Explanation: In attempting to write database

ARI0077D End of extents encountered on

accounting data to the accounting output file, an access

accounting file filename.

error occurred. All application server activity is halted

until the reply to the prompt is given. If accounting

No = terminate,

data is being written to tape, the cuu is provided in the

Yes = continue without accounting,

message. The database accounting file has the file name

Alt = continue but use alternate file.

indicated by filename. This name will either be

Enter 0(No), 1(Yes), or 2(Alt).

ARIACC1 or ARIACC2. If an error code is not

displayed, the Reason Code value is the primary error

Explanation: In attempting to write database

code and the Return Code value is the secondary error

accounting data to the accounting output DASD file, an

code. See Chapter 21, “Sequential File Errors,” on page

end-of-extents condition occurred. The accounting

361 for reason code and return code displayed. If an

DASD file is now full. Note that some accounting data

error code is displayed, the return code is the contents

has already been lost. All application server activity is

of register 15 after VSAM processed the request macro.

halted until the reply to the prompting message is

See the VSE/VSAM Messages and Codes manual for the

given. The database accounting file has the file name

possible cause of this error.

indicated by filename. This name will either be

ARIACC1 or ARIACC2.

The database manager is now asking whether you wish

to: continue execution with the accounting support

The database manager is now asking whether you wish

disabled, switch to the alternate accounting file, or

to: continue execution with the accounting support

terminate the database manager. The operator can reply

disabled, switch to the alternate accounting file, or

No(0), Yes(1), or Alt(2).

terminate the database manager. The operator can reply

No(0), Yes(1), or Alt(2).

System Action: All application server activity is halted

until the operator replies to the prompt. If the operator

System Action: All application server activity is halted

replies Yes or No, accounting support is immediately

until the operator replies to the prompt. If the response

disabled. This error condition prevents the accounting

is Yes or No, accounting support is immediately

output file from being closed.

disabled.

If the reply is Yes, execution continues with the

If the reply is Yes(1), the database manager execution

accounting support disabled.

continues with accounting support disabled. Eventually,

the actions described under System Programmer

If the response is Alt, the database manager issues an

Response should be done.

OPEN for the alternate accounting file, and continues

executing with accounting support enabled.

If the response is Alt(2), the database manager issues

an OPEN for the alternate accounting file and

If the reply is No, the database manager immediately

continues executing with accounting support enabled.

terminates. The condition is treated as a limit error.

If the response is No(0), the database manager

If accounting is to tape, the tape unit identified in this

terminates immediately. The condition is treated as a

error message will be dynamically unassigned.

limit error.

Therefore the tape unit will be available for any use,

including the alternate accounting file (unless error

Operator Response: Reply Yes(1), Alt(2), or No(0).

message ARI112E is displayed). If this unit is used for

Save this message and give it to your system

the alternate accounting file, a new tape volume must

programmer.

be mounted.

System Programmer Response: You may need to

Operator Response: Reply Yes(1), No(0), or Alt(2).

allocate a larger space for the accounting file. Update

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

the DLBL/EXTENT information accordingly in the job

ARI0081E Write error trace file. Reason Code = nn.

control for the accounting file. Ensure that the full

Error Code = nn.

accounting file is saved for later processing. If you are

using database tables to store the accounting data, the

Explanation: When the system attempted to write

full accounting file should be loaded (using

trace data to the trace output file, an access error

DATALOAD) into the tables at the earliest opportunity.

occurred. Trace status is now "output disabled". The

trace file has the file name ARITRAC. The Reason Code

value is the Primary Error Code. The Error Code value

ARI0078E Invalid response to accounting file error

is the Secondary Error Code. For further explanation,

prompt message.

look up the displayed error codes under either

Explanation: An invalid response was given to

Chapter 21, “Sequential File Errors,” on page 361, or

accounting file error prompt message ARI0076D.

“SEQ FILE ERRORS” in the HELP text.

System Action: Message ARI0076D is redisplayed.

System Action: Any further database trace output is

disabled. This error condition prevents closing the trace

User Response: Determine the valid response to

output file during TRACE OFF command processing,

message ARI0076D, and enter the valid response when

database manager shutdown, or application

the prompting message is redisplayed.

termination.

User Response: Save this message and give it to your

ARI0079I

Accounting file filename

system programmer. If a 0Pnn message was received

{OPENED|CLOSED}.

for the trace tape or disk unit, also give a copy of this

Explanation: The database accounting file has been

message to the system programmer. Do not try to

opened or closed. This file has the name indicated by

process the trace output file.

filename, which is either ARIACC1 or ARIACC2.

See Operator Response for message ARI0097I for

System Action: If the accounting file was opened, the

possible action to salvage the accumulated trace output

system is writing accounting records to the opened file.

data.

If the accounting file was closed, it is available for any

Operator Response: See User Response.

other processing.

System Programmer Response: For corrective action,

User Response: None required.

look up the displayed error codes under either

Chapter 21, “Sequential File Errors,” on page 361, or

ARI0080E Trace file end of extents encountered.

“SEQ FILE ERRORS” in the HELP text. Note that

Trace output is disabled.

although you may have partial trace output, it cannot

be cleanly processed because the trace file has not been

Explanation: In attempting to write database trace

closed.

data to the trace output DASD file, an end-of-extents

condition occurred. The trace DASD file is now full.

Tracing is disabled.

ARI0082E TRACE command parameter n

[parameter] invalid or missing.

System Action: The database manager continues

without any further database trace output. This error

Explanation: The TRACE operator command was

condition prevents closing the trace output file during

entered and is being processed. One of the following

TRACE OFF command processing, database manager

conditions was detected:

shutdown, or application termination.

v A required parameter contains an invalid value.

v A required parameter was omitted.

User Response: Save this message and give it to your

v An optional parameter contains an invalid value.

system programmer. Do not try to process the trace

v An undefined extra parameter was entered.

output file.

See the Operator Response for message ARI0097I for

Parameter n identifies which parameter was omitted or

possible action to take to salvage the accumulated trace

contains the invalid value. parameter, if present in the

output data.

message text, identifies the invalid parameter value. If

not present, it indicates that a required parameter was

Operator Response: See User Response.

omitted.

System Programmer Response: You may need to

System Action: TRACE command processing ends.

allocate a larger space for the trace file. Update the

There is no change in the status of the database trace

DLBL/EXTENT information accordingly in the job

facility.

control for the trace file.

Operator Response: Consult the TRACE command

section of the DB2 Server for VSE & VM Operation

manual, and compare the TRACE command description

with the TRACE command that you entered and the

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

text of this message. Determine which parameter was

v If CANCEL is entered, TRACE command processing

erroneously specified or omitted and reenter the

ends.

TRACE command.

Operator Response: Enter one of the following:

User ID

ARI0083I

Trace command specified {ON|OFF},

Indicates tracing by database user ID.

but trace already {ON|OFF CLOSED}.

Although lower case characters may be

Explanation: One of the following occurred:

entered, they are translated to upper case by

the database manager. Also, imbedded blanks

v The TRACE ON command was specified and the

may not be entered since the blank (space)

database trace facility is already active (ON) or

character is the database parameter delimiter

"output disabled" due to successful processing of a

character. You should attempt to trace by a

previous TRACE ON operator command (and no

user ID only if the user ID consists entirely of

subsequent successful TRACE OFF operator

numeric and uppercase alphabetic characters

command).

with no imbedded blanks (low order blanks

v The TRACE ON command was specified and the

are no problem).

database trace facility is already active (ON) or

"output disabled" due to successful processing of

AGENT n

trace parameters (TRACCONV=, TRACDBSS=,

AGENT indicates trace by agent number; n is

TRACRDS=, TRACDSC=, TRACWUM=,

a valid database Agent number (blank

TRACDRRM=, TRACSTG=) specified with the

between AGENT and n).

initialization parameters (and no subsequent

AGENT 1

Operator Agent.

successful TRACE OFF operator command).

v The TRACE OFF command was specified and the

AGENT 2

Checkpoint/Archive Agent.

database trace facility is already inactive (OFF) and

AGENT 3

In single user mode is

no trace file is open (trace is in OFF CLOSE state).

General Purpose User Agent.

The message text specifies OFF and OFF CLOSED.

In multiple user mode is

TRACE ON cannot be validly specified unless trace is

Ready/Recovery Agent.

inactive (OFF). TRACE OFF cannot be validly specified

AGENTS 4-n In multiple user mode are

unless trace is active (ON) or inactive but with the trace

General Purpose User

file open (OFF NOCLOSE).

Agents.

System Action: TRACE command processing ends.

There is no change in status of the database trace

Note: On SHOW commands, user agents 4

facility.

through n are displayed as agents 1, 2,

..., NCUSERS initialization parameter

Operator Response: None is required since trace is

value.

already in the state specified by the TRACE command.

If you want to specify new tracing (TRACE ON)

Indicates that all database Agents are to be

parameters, you must first successfully enter the

traced.

TRACE OFF command (the NOCLOSE option allows

CANCEL

the trace file to be kept open for further output in the

Ends TRACE command processing.

same trace file).

ARI0085E Agent number [value] invalid or missing.

ARI0084D Enter one of userid, AGENT n, * (for

all), or CANCEL.

Explanation: An incorrect or null (blank) agent

number value was entered in response to TRACE ON

Explanation: The TRACE ON operator command is

command prompting message ARI0084D.

being processed. The database manager is prompting

v If value is missing from the message text, the

the operator to specify which database user ID or agent

keyword AGENT was entered but the agent number

number (or * for all agent numbers) is to be traced.

value was omitted.

System Action:

v If value is present in the message text, an agent

v If a user ID is entered, trace output will occur only

number value was entered which was not an

for the database Agents processing on behalf of the

unsigned number, was a zero, or exceeded the

specified user ID.

number of agents present in the database manager.

v If AGENT n is entered, trace output will occur only

The number of agents can be determined by the

for processing within the specified Agent number.

SHOW ACTIVE operator command.

v If * is entered, trace output will occur for processing

System Action: TRACE ON prompting message

in all DB2 Server for VSE Agents.

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

ARI0084D is re-displayed to allow the correct response

the trace prompting message, and enter the valid

to be entered.

response when the prompting message is re-displayed.

Operator Response: Determine the valid agent

number value you will enter in response to prompting

ARI0087D Enter one or more component names or

message ARI0084D, and enter the valid response when

CANCEL. Valid component names are

the prompting message is re-displayed.

DBSS, RDS, [WUM, DRRM,] DSC,

CONV, and STG.

ARI0086E Invalid response {BLANK|value} to

Explanation: The TRACE ON operator command is

prompt.

being processed. The database manager is prompting

the operator to specify the major components (DBSS,

Explanation: An incorrect value (value in message

RDS, WUM, DRRM, DSC, CONV, or STG) that are to

text) or no value (BLANK in message text) was entered

be traced.

in response to a TRACE ON command or trace

initialization prompting message.

System Action:

v If the operator enters DBSS, message ARI0090D

For message ARI0092A, a blank or null response was

appears and prompts the operator for the functions

entered (BLANK in text), an incorrect cuu value was

of DBSS to trace.

entered (not three characters or not valid hex

v If the operator enters RDS, message ARI0088D

characters), or the response DISK or CANCEL was

appears and prompts the operator for the functions

misspelled.

of RDS to trace.

For message ARI0084D, a blank or null response was

v If the operator enters WUM, message ARI0141D

entered.

appears and prompts the operator for the trace level.

For message ARI0087D, either only a blank or null

v If the operator enters DRRM, message ARI0140D

response was entered (BLANK in text), or a value

appears and prompts the operator for the functions

other than CONV, DBSS, RDS, WUM, DRRM, DSC,

of DRRM to trace.

or STG was entered (value in text).

v If the operator enters DSC, message ARI0142D

For message ARI0088D, either only a blank or null

appears and prompts the operator for the functions

response was entered (BLANK in text), or a value for

of DSC to trace.

function name other than *, EXEC, PA, OPT, AG,

v If the operator enters CONV, message ARI0160D

INT, or AU was entered (value in text).

appears and prompts the operator for the trace level.

v If the operator enters STG, message ARI0162D

For message ARI0090D, either only a blank or null

appears and prompts the operator for the trace level.

response was entered (BLANK in text), or a value for

v If the operator enters CANCEL, TRACE command

function name other than *, ENTRY, EXIT, LOG,

processing ends.

LOCK, LUW, DC, DM, STOR, SORT, INDEX, or

STAT was entered (value in text).

Operator Response:

For message ARI0091D, either only a blank or null

v If you want DBSS tracing, enter DBSS.

response was entered (BLANK in text), or a value

v If you want RDS tracing, enter RDS.

that was not an unsigned numeric, or that was not in

v If you want WUM tracing, enter WUM.

the range 0 to 14999 or 20000 to 24999, was entered

v If you want DRRM tracing, enter DRRM.

(value in text).

v If you want DSC tracing, enter DSC.

v If you want CONV tracing, enter CONV.

For message ARI0140D, a blank or null response was

v If you want STG tracing, enter STG.

entered (BLANK in text), or a value for function

v If you want to end the TRACE command, enter

name other than *, DICT, GEN, PARSE, or RDIIN

CANCEL.

was entered (value in text).

For message ARI0141D, either only a blank or null

Enter any of DBSS, RDS, WUM, DRRM, DSC, CONV,

response was entered (BLANK in text).

or STG (with one or more blanks between them). You

For message ARI0142D, either only a blank or null

can enter them in any order.

response was entered (BLANK in text), or a value for

function name other than *, AGENT, or COM was

Note: You can see this message in all environments. In

entered (value in text).

environments where components are not active,

For message ARI0160D, a blank or null response was

however, the components tracing does not take

entered (BLANK in text).

place, even if the operator specifies them.

For message ARI0162D, a blank or null response was

entered (BLANK in text).

ARI0088D Enter RDS function name and

trace-level pairs.

System Action: The TRACE prompting message (to

which the invalid response was entered) is redisplayed.

Valid function names are *, EXEC,

Operator Response: Determine the valid response to

PA, OPT, AG, INT, AU, SG, and

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

CANCEL.

Your entry was in response to one of the following

Valid trace-level values are

TRACE ON command prompting messages:

and 2.

v ARI0088D (RDS in message text)

v ARI0160D (CONV in message text)

Explanation: The TRACE ON command is being

v ARI0090D (DBSS in message text)

processed. The operator has responded RDS to

v ARI0140D (DRRM in message text)

prompting message ARI0087D. The database manager

v ARI0141D (WUM in message text)

is prompting the operator to specify which functions of

v ARI0142D (DSC in message text)

RDS to be traced and the desired trace level for each

v ARI0162D (STG in message text).

function.

System Action:

{*|function name} in message text identifies the valid

RDS, DBSS, DSC, or DRRM function name that

v If * n is entered, all RDS functions will be traced at

precedes the omitted or incorrect trace-level value.

trace level n.

v If EXEC n, or PA n, or OPT n, or AG n, or INT n, or

System Action: The TRACE ON prompting message

AU n, or SG n are entered, the specified functions of

(to which the incorrect response was entered) is

RDS will be traced at the specified trace level (n).

re-displayed.

v If CANCEL is entered, TRACE command processing

Operator Response: Determine the valid response to

ends.

the trace prompting message (each function name must

be followed by a valid trace-level value of 0, 1, or 2

Note: If trace level 0 is entered for a function, it will

with a blank between them) and enter the valid

not be traced (equivalent to not entering the

response when the prompting message is re-displayed.

function at all). Therefore, if you want to trace

all RDS functions (at level 2, for example) except

ARI0090D Enter DBSS function name and

INT, you can enter * 2 INT 0. Since INT appears

trace-level pairs.

after the * specification, it overrides the implicit

INT 2 implied by * 2. Likewise, entering : * 1

EXEC 2 will cause all RDS functions except

Valid function names are

EXEC to be traced at level 1 and EXEC to be

*, ENTRY, EXIT, LOG, LOCK, LUW,

traced at level 2.

DC, DM, STOR, SORT, INDEX, STAT,

and CANCEL.

Operator Response:

Valid trace-level values are

v If all RDS functions are to be traced, enter * plus 1 or

1, and 2.

2 for desired trace level (with blank between * and

Explanation: The TRACE ON command is being

number).

processed. The operator has responded DBSS to

v If only selected RDS functions are to be traced, enter

prompting message ARI0087D. The database manager

first function name, then its trace level value, then, if

is prompting the operator to specify which functions of

desired, second function name, then its trace level

DBSS are to be traced and the desired trace level for

value, etc. Note that one or more blanks must appear

each function.

between each function name and each trace level

value entered. Note also that if you enter a function

System Action:

name more than once, the last entry is effective.

v If * n is entered, all DBSS functions will be traced at

v If TRACE command termination is desired, enter

trace level n.

CANCEL.

v If ENTRY n, or EXIT n, or LOG n, or LOCK n, or

v See Note in the System Action section of this message

LUW n, or DC n, or DM n, or STOR n, or SORT n, or

for possible use of * in combination with other

INDEX n, or STAT n are entered, the specified

function names.

functions of DBSS will be traced at the specified trace

level (n).

v If CANCEL is entered, TRACE command processing

ARI0089E Trace-level [value] for

ends.

{RDS|CONV|DBSS

|DSC|WUM|DRRM|STG} {*|function

Note: If trace level 0 is entered for a function, it will

name} invalid or missing.

not be traced (equivalent to not entering the

Explanation: You entered one of the following:

function at all). Therefore, if you want to trace

v An incorrect trace-level value ([value] displayed in

all DBSS functions (at level 2, for example)

message text)

except INDEX, you can enter: * 2 INDEX 0. Since

INDEX appears after the * specification, it

v No trace-level value ([value] omitted from message

overrides the implicit INDEX 2 implied by * 2.

text).

Likewise, entering: * 1 ENTRY 2 will cause all

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

DBSS functions except ENTRY to be traced at

TRACSTG. The initialization is requesting the system

level 1 and ENTRY to be traced at level 2.

operator to:

v Ready a tape unit for trace output and supply its

Operator Response:

cuu, or

v If all DBSS functions are to be traced, enter * plus 1

v Reply DISK if the trace output file is a disk file.

or 2 for desired trace level (with blank between * and

number).

If this message is redisplayed after message ARI0094E

v If only selected DBSS functions are to be traced,

(indicating a trace file open error), the database

enter first function name, then its trace level value,

manager is requesting corrective action for that

then, if desired, second function name, then its trace

message plus the operator action indicated above.

level value, etc. Note that one or more blanks must

appear between each function name and each trace

System Action: If the operator enters cuu, the

level value entered. Note also that if you enter a

indicated tape unit is dynamically assigned and

function name more than once, the last entry is

opened. DB2 Server for VSE initialization continues

effective.

with database trace active.

v If TRACE command termination is desired, enter

If the operator enters DISK, the trace disk file is

CANCEL.

opened. DB2 Server for VSE initialization continues

v See the note in the SYSTEM ACTION section of this

with database trace active.

message for possible use of * in combination with

If the operator enters CANCEL, message ARI0056I is

other function names.

displayed. DB2 Server for VSE initialization continues

with database trace inactive ("output disabled").

ARI0091D Enter the dump trace point number, or

Operator Response: Database initialization is

CANCEL to terminate trace command

requesting the system operator to supply one of the

processing.

following:

Explanation: The TRACE ON command is being

v The cuu of a selected tape unit if tracing to tape, or

processed. The operator specified the DUMP parameter

v The reply DISK if tracing is to a disk file.

in the TRACE ON command. The database manager is

prompting the operator to specify the CONV, DBSS,

If trace output is to tape:

RDS, DSC, WUM, DRRM, or STG trace point number

that is to cause a database snap dump to occur when

1. Select a tape unit for trace output.

the trace point is first activated. The snap dump will

dump either all of the database partition (full dump),

Note: The selected tape unit must be currently

or only that part of the partition which does not

unassigned.

contain database load modules (partial dump). The

2. Make the tape unit ready with a labeled scratch

database initialization parameter DUMPTYPE will

tape mounted and properly positioned.

control whether a full dump is given (DUMPTYPE=F)

3. Enter the cuu of the selected tape unit.

or a partial dump is given (DUMPTYPE=P or N).

System Action: The entered trace point number is

You can reply CANCEL if no tape or disk file is

stored. When that trace point is first activated for

available or tracing is not desired.

tracing, a snap dump is produced on SYSLST. After the

first activation, no more snap dumps are produced.

If this message is redisplayed after message ARI0094E

(indicating a trace file open error), the database

If CANCEL is entered, TRACE command processing

manager is requesting corrective action for that

ends.

message plus the operator action indicated above.

Operator Response:

Reply CANCEL if the error condition cannot be

v Enter the CONV, DBSS, RDS, DSC, WUM, DRRM, or

corrected.

STG trace point number that you want. The number

must be unsigned and in the range of 0 to 14999 or

ARI0093I

TRACE command terminated by

20000 to 24999.

request.

v If TRACE command termination is desired, enter

Explanation: The TRACE ON command was being

CANCEL.

processed. The operator responded CANCEL to a

prompting message.

ARI0092A Ready trace output volume. Enter CUU,

System Action: TRACE command processing ends.

DISK, or CANCEL.

There is no change in status to the database trace

Explanation: The operator specified one or more of

facility.

the initialization parameters TRACCONV, TRACDBSS,

TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

Operator Response: The operator may reenter the

or initialization trace initialization is completed. The

TRACE ON command.

TRACCONV, TRACDBSS, TRACRDS, TRACDSC,

TRACWUM, TRACDRRM, or TRACSTG

initialization parameters specify how TRACE is

ARI0094E Trace file {cuu|DISK} assign or open

active.

failed. Reason Code = nn. Return Code

v Trace output is directed to tape unit cuu (cuu is in

= nn.

the message text) or to a disk file (DISK is in the

Explanation: The database manager is processing the

message text).

TRACE ON command or initializing a database trace

during database or Resource Adapter initialization. An

ARI0096I

TRACE now OFF. Trace file remains

error occurred while the Resource Adapter was

open on unit {cuu|DISK}.

attempting to dynamically assign (tape only) and open

the trace output file on tape unit cuu (cuu is in the

Explanation: The TRACE OFF NOCLOSE command

message text) or on a disk file (DISK is in the message

was successfully processed. Trace is inactive and the

text). The Reason Code value is the Primary Error

trace output file remains open for subsequent trace

Code. The Return Code value is the Secondary Error

output (after using a TRACE ON command). If cuu is

Code. For further explanation, look up the displayed

in the message text, it identifies the trace output file

error codes under either Chapter 21, “Sequential File

tape unit. If DISK is in the message text, the trace

Errors,” on page 361, or “SEQ FILE ERRORS” in the

output file is a disk file. This message will occur if

HELP text.

trace was active when the command was entered or if

trace was already inactive but with the trace output file

System Action: If this error occurs in the database

open (due to a prior TRACE OFF NOCLOSE

machine, then either:

command).

v TRACE command processing ends (For TRACE

command processing, the trace facility remains

System Action: TRACE OFF command processing has

inactive.), or

completed. Trace is completely inactive.

v Database initialization reissues message ARI0092A.

Operator Response: None required. A TRACE ON

This allows the system operator to correct the

command may now be entered. Note that a TRACE

problem indicated by this error message, ready the

OFF command with the NOCLOSE parameter omitted

trace output volume, and retry the trace file open

(or database manager termination which closes the tape

processing.

or disk file) must be executed before the trace output

file can be processed.

If this error occurs in a user virtual machine, the

application abends.

ARI0097I

TRACE was output disabled. TRACE is

Note: If output is to tape, the tape volume has not

now OFF. It did not close unit

been accessed.

{cuu|DISK|UA}.

User Response: For corrective action, look up the

Explanation: The database manager is being normally

displayed error codes under either Chapter 21,

or abnormally terminated, or the TRACE OFF

“Sequential File Errors,” on page 361, or “SEQ FILE

command (with or without the CLOSE or NOCLOSE

ERRORS” in the HELP text.

parameters) was processed. Trace was previously ON

(active) due to the TRACE ON operator command or

Operator Response: See User Response.

the initialization parameters TRACCONV, TRACDBSS,

System Programmer Response: See User Response.

TRACRDS, TRACDSC, TRACWUM, TRACDRRM, or

TRACSTG.

ARI0095I

Trace now on with output on unit

Trace became "output disabled" (trace output

{cuu|DISK}.

suppressed) because of either:

Explanation: The TRACE ON command has been

v A failure to assign and open the trace output file

successfully processed, or database initialization has

during database initialization (CANCEL reply to

successfully initialized trace ON. Database trace is now

message ARI0092A); or

active with trace output on tape unit cuu (cuu is in the

v A trace output file write error (message ARI0081E).

message text) or to a disk file (DISK is in the message

text).

The TRACE OFF command or database manager

termination caused trace to be turned off (fully

System Action:

disabled), but the trace output file was not closed due

v Trace is active.

to the previous problem (assign failure, open failure, or

TRACE ON command processing is completed. Trace

write error).

is active as specified by the values entered for the

various TRACE ON command prompting messages,

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

If cuu is in the message text, the trace output tape file

The Reason Code value is the Primary Error Code. The

was assigned and opened and may contain trace output

Return Code value is the Secondary Error Code. For

data, but due to the write error and failure to close the

further explanation, look up the displayed error codes

file, the file may not be usable. Also, tape unit cuu

under either Chapter 21, “Sequential File Errors,” on

remains assigned to the database partition until the

page 361, or “SEQ FILE ERRORS” in the HELP text.

partition goes to end of job step.

System Action: TRACE OFF command processing or

trace shutdown is completed. Trace is in the OFF state.

If DISK is in the message text, one of the following

Assume that the trace tape or disk file was not closed

occurred:

and is not fully processable (see below).

v The disk trace output file was not successfully

opened for Trace output during database

Note: If output was to tape, tape unit cuu remains

initialization (message ARI0094E was displayed).

assigned to the database partition and cannot be

v The disk trace output file was opened successfully,

used until the database manager ends. Therefore,

but an error occurred in writing data to the file

if this condition occurred during the TRACE

(message ARI0081E was displayed). The file may

OFF command, you may have to shut down the

contain trace data, but because of the write error and

database manager to unassign the tape unit.

the failure to close the file, the file may not be

Operator Response: Report the problem (message) to

usable.

your system programmer.

If UA is in the message text, the trace output tape file

You may attempt to run the DB2 Server for VSE Trace

was not successfully assigned and opened during

Formatter Utility Program (ARIMTRA). It will format

database initialization.

and output all trace data up to the point of failure. At

that point it may end due to lack of tape/disk CLOSE

System Action: Trace has been turned off (disabled).

recording or an unreadable record on the tape/disk.

Note: If cuu is in the message text, the tape unit cuu is

Notes:

no longer the trace output file. (A later TRACE

1. If the output was to tape and if the message is in

ON command to another cuu will be accepted).

response to the TRACE OFF command, you can

restart the database trace using the TRACE ON

Operator Response: None required. If the message

command with a different tape unit cuu specified.

was in response to the TRACE OFF command and

output was to tape, a TRACE ON command may be

2. If the output was to tape and you require the use of

entered (with a different cuu). If output was to tape,

the tape unit cuu by this or any other partition

you may attempt to salvage the trace data on the

(before planned shutdown of the database manager

output tape by using the VSE job control MTC

), you must shut down the database manager (and

WTM,cuu statement. In any case, you can attempt to

restart it) to unassign the tape unit.

run the DB2 Server for VSE Trace Formatter Utility

System Programmer Response: For corrective action,

Program (ARIMTRA). It will format and output all

look up the displayed error codes under either

trace data or selected trace data up to the point of

Chapter 21, “Sequential File Errors,” on page 361, or

failure. At that point it will probably end due to invalid

“SEQ FILE ERRORS” in the HELP text.

data or an I/O error on the tape.

Note: If output was to tape, tape unit cuu remains

ARI0099I

TRACE OFF. Output file closed on unit

assigned to the database partition and cannot be

{cuu|DISK}.

used until the database manager ends. Therefore,

Explanation: Database trace has been successfully

if this condition occurred during the TRACE

ended due to entry of the TRACE OFF CLOSE (CLOSE

OFF command, you may have to shut down the

is the default) operator command or due to database

database manager to unassign the tape unit.

manager normal or abnormal termination. Trace is off

and the trace output file has been successfully closed. If

ARI0098E Trace file {cuu|DISK} unassigned or

cuu is in the message text, the trace file is on tape cuu

CLOSE failed. Reason Code = nn.

and the tape unit has been unassigned. If DISK is in

Return Code = nn. TRACE OFF.

the message text, the trace file is a disk file.

Processing completed.

System Action: TRACE OFF command processing or

Explanation: The TRACE OFF command (CLOSE is

trace shutdown is completed. The trace file is closed.

the default) is being processed or the database manager

Operator Response: None required. The trace output

is being normally or abnormally ended. If cuu is in the

file is now available for print display by the DB2 Server

message text, a terminating error occurred while trying

for VSE Trace Formatter Utility Program (ARIMTRA).

to close and unassign the trace output tape file. If

DISK is in the message text, a terminating error

Note for tracing to tape: Because the database manager

occurred while trying to close the trace output disk file.

does not rewind the tape, the operator should manually

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

rewind the tape (unless more files are to be written on

Note: You may get the same result if the requested

the tape) and, if desired, demount it.

agent, user, or DBSPACE has no lock contention

at the time the command is reentered.

ARI0100E Agent/user ID {agent-id | user-id} is not

assigned.

ARI0103E

A column named name1 does not exist in

the system catalog table named name2.

Explanation: A SHOW LOCK operator command

could not be processed. Sources of the problem include:

Explanation: The row for the column name (name1)

was not found in the system table name2. name1 is

v An invalid user ID was entered

either TLABEL or CLABEL. The TLABEL column

v An invalid agent number was entered (not numeric

resides in SYSTEM.SYSCATALOG and contains

or not in the range 1 through NCUSERS)

correlation names. name2 is either

v The user, identified by user-id, was not assigned to

SYSTEM.SYSCATALOG or SYSTEM.SYSCOLUMNS.

an agent at the instant the SHOW command was

The CLABEL column resides in

entered.

SYSTEM.SYSCOLUMNS and contains column labels.

System Action: The SHOW command processing is

The database manager expects there to be a column

ended.

named TLABEL in SYSTEM.SYSCATALOG and

CLABEL in SYSTEM.SYSCOLUMNS when looking for

Operator Response: Be sure that the specified agent-id

a row describing those columns. It could find neither of

or user-id is valid and reenter the SHOW command.

them.

Note: You may get the same result if the requested

System Action: Processing continues.

user-id does not occupy an agent at the time the

Operator Response: Refer this message to your

command is reentered.

database administrator.

Database Administrator Response:

ARI0101E DBSPACE dbspace-number does not exist.

1. Determine why the row was deleted, or why it was

Explanation: The dbspace-number entered on the

updated with invalid values, and what values

SHOW LOCK DBSPACE operator command or used to

should be inserted.

release empty pages (STARTUP=P) was invalid:

2. Insert or update a row for TLABEL or CLABEL in

v Not numeric or

SYSTEM.SYSCOLUMNS with the appropriate

v Not in the range of 1 to n where n is the number of

values.

PUBLIC and PRIVATE DBSPACEs defined in the

3. Restart the database manager.

database (and with rows in catalog table

SYSTEM.SYSDBSPACES).

ARI0104I

The row, where SQLOPTION = option1

System Action: The SHOW command processing or

does not exist, or has incorrect data in

release empty pages processing is ended.

the VALUE column in the catalog table

Operator Response: Correct the DBSPACE number (be

named SYSOPTIONS. The database

sure that the DBSPACE number is between 1 and the

manager will assume a value of option2.

maximum valid value for DBSPACE numbers) and

Explanation: You omitted a data type value or gave

reenter the command.

an incorrect value. The system assumed a value

instead.

ARI0102E There is no lock contention for {any |

The SQLOPTION = option1 possibilities are:

this} {DBSPACE | agent/user}.

SQLOPTION = DBCS

Explanation: The database manager could not find a

The row for DBCS option in

DBSPACE or an agent/user that had locking contention

SYSTEM.SYSOPTIONS (where SQLOPTION =

at the instant the SHOW command was entered. This

DBCS) is missing or contains an invalid value.

message occurred as a result of entering a SHOW

The correct value is either YES or NO.

LOCK DBSPACE, SHOW LOCK USER, SHOW LOCK

WANTLOCK, SHOW LOCK ACTIVE, or SHOW LOCK

SQLOPTION = CHARSUB

GRAPH command.

The row for the CHARSUB option in

SYSTEM.SYSOPTIONS (where SQLOPTION =

System Action: The SHOW command processing is

CHARSUB) is missing or contains an invalid

ended.

value. The correct values are SBCS or MIXED.

Operator Response: Reenter the command.

SQLOPTION = CCSIDSBCS

The row for the CCSIDSBCS option in

SYSTEM.SYSOPTIONS (where SQLOPTION =

CCSIDSBCS) is missing or contains an invalid

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE System Control - ARI0001-ARI0199

CCSID value. The correct values are recorded

v The DBCS option row is missing or contains a value

in the SYSTEM.SYSCCSIDS catalog table.

other than YES or NO. If the row is missing, insert a

row with the correct value. If the row is invalid,

SQLOPTION = CCSIDMIXED

update the row with the appropriate DBCS option.

The row for the CCSIDMIXED option in

v The CHARSUB option row is missing or contains a

SYSTEM.SYSOPTIONS (where SQLOPTION =

value other than SBCS or MIXED. If the row is

CCSIDMIXED) is missing or contains an

missing, insert a row with the correct value. If the

invalid CCSID value. The correct values are

row is invalid, update the row with the appropriate

recorded in the SYSTEM.SYSCCSIDS catalog

CHARSUB option.

table.

v One or more of the CCSID option rows (CCSIDSBCS,

SQLOPTION = CCSIDGRAPHIC

CCSIDMIXED, CCSIDGRAPHIC, MCCSIDSBCS,

The row for the CCSIDGRAPHIC option in

MCCSIDMIXED, or MCCSIDGRAPHIC) is missing

SYSTEM.SYSOPTIONS (where SQLOPTION =

or contains an invalid CCSID value. Insert a row or

CCSIDGRAPHIC is missing or contains an

update the row with the correct CCSID value. The

invalid CCSID value. The correct values are

CCSID values appropriate for this installation should

recorded in the SYSTEM.SYSCCSIDS catalog

be planned and implemented at the time of

table.

installation or migration.

SQLOPTION = MCCSIDSBCS

The row for the MCCSIDSBCS option in

ARI0105I

The row, where column = name, does not

SYSTEM.SYSOPTIONS (where SQLOPTION =

exist in the system catalog table

MCCSIDSBCS) is missing or contains an

table-name. The database manager

invalid CCSID value.

assumes the internal default of charname.

SQLOPTION = MCCSIDMIXED

Explanation: The row for the character set, where

The row for the MCCSIDMIXED option in

column = name does not exist in the catalog table

SYSTEM.SYSOPTIONS (where SQLOPTION =

table-name. The character set specified in the

MCCSIDMIXED) is missing or contains an

CHARNAME parameter on SQLSTART is not correctly

invalid CCSID value.

defined in all catalog tables.

SQLOPTION = MCCSIDGRAPHIC

System Action: Processing continues. The database

The row for the MCCSIDGRAPHIC option in

manager uses the charname character set, which is

SYSTEM.SYSOPTIONS (where SQLOPTION =

usually be the last CHARNAME correctly specified.

MCCSIDGRAPHIC) is missing or contains an

invalid CCSID value.

Operator Response: Refer this message to your

database administrator.

System Action: Processing continues. The implied

value of option2 is:

Database Administrator Response: Determine

v For SQLOPTION = DBCS, DBCS option will be NO.

whether a wrong character set name is specified as the

v For SQLOPTION = CHARSUB, CHARSUB option

CHARNAME initialization parameter.

will be SBCS.

v If the initialization parameter is incorrect, restart the

v For SQLOPTION = CCSIDSBCS, the CCSIDSBCS

database system with a correct initialization

option will be determined from the current

parameter value.

CHARNAME value.

v If the row is missing from the specified catalog table

v For SQLOPTION = CCSIDMIXED, the CCSIDMIXED

table-name, insert a row with the correct values into

option will be determined from the current

the table.

CHARNAME value.

v For SQLOPTION = CCSIDGRAPHIC, the

After inserting the row, restart the database manager,

CCSIDGRAPHIC option will be determined from the

because some application programs may not run

current CHARNAME value.

correctly when using another character set.

v For SQLOPTION = MCCSIDSBCS, the MCCSIDSBCS

For more information, see the DB2 Server for VSE

option will be 37.

System Administration manual.

v For SQLOPTION = MCCSIDMIXED, the

MCCSIDMIXED option will be 0.

ARI0106E The database manager found an

v For SQLOPTION = MCCSIDGRAPHIC, the

incompatibility in the application server

MCCSIDGRAPHIC option will be 0.

at initialization. The expected FORMAT

Operator Response: Refer this message to your

ID is format-id1. The FORMAT ID found

database administrator.

in the application server is format-id2.

Database Administrator Response: Display the

Explanation: The code running on the database

SYSTEM.SYSOPTIONS catalog table and find out

manager is incompatible with the release level of the

whether:

database. format-id1 is the expected format ID, and

Messages and Codes

DB2 Server for VSE System Control - ARI0001-ARI0199

format-id2 is the format ID of the current application

application server default CHARNAME.

server.

Operator Response: Refer this message to your

Level of Code

Application Server

database administrator.

Format ID

Database Administrator Response: Display the row

Version 7 Release 3

for the specified EBCDIC character set in the

SYSTEM.SYSCHARSETS catalog table. Determine the

Version 7 Release 2

correct values and update the row with correct values.

Version 7 Release 1

After correcting the row, restart the database manager

Version 6 Release 1

because some application programs may not run

correctly using another character set.

Version 5 Release 1

Version 3 Release 5

ARI0109E

DB2 Server for VSE accounting is not

Version 3 Release 4

active.

Version 3 Release 3

Explanation: The ALTACCT operator command was

entered, but the database accounting support is not

Version 3 Release 2

active.

Version 3 Release 1

System Action: The ALTACCT operator command

processing ends.

Version 2 Release 2

Operator Response: None is required. Do not enter

System Action: The database manager is terminated.

the ALTACCT operator command when DB2 Server for

Operator Response: Refer this message to your

VSE accounting support is not active. If you were

system programmer.

instructed to enter this command, notify your database

system programmer.

System Programmer Response: The procedures for

installing the database manager code and updating

System Programmer Response: Ensure that the

application servers are described in the DB2 Server for

ACCOUNT initialization parameter is properly

VSE Program Directory. Installations that are

specified and that the system operator is properly

simultaneously using multiple application servers and

instructed when to enter the ALTACCT operator

different database manager releases may accidentally

command.

pair a release of the database manager with an

incompatible application server.

ARI0111I

Accounting disabled.

Explanation: The DB2 Server for VSE accounting

ARI0107E The ROW, where the NAME = name,

support has been disabled. This message is issued

contains incorrect data in the column

whenever the YES response is given in reply to either

column in the system catalog table

message ARI0076D or message ARI0077D.

SYSCHARSETS. Data positions that are

in error are indicated by the letter E in

System Action: Processing continues with accounting

the strings that follow. Either the current

support disabled.

system CHARNAME or

INTERNATIONAL will be used.

ARI0112E Dynamic UNASSIGN of accounting file

Explanation: For the character set specified in the

filename cuu failed. Reason Code =

CHARNAME initialization parameter, the EBCDIC

X'nn'.

character set classification table or the EBCDIC

character set translation table in

Explanation: In attempting to dynamically unassign

SYSTEM.SYSCHARSETS contains invalid values.

the tape unit identified in this error message, an error

occurred. The Reason Code value is the return code (in

In the strings following the message, the positions in

hexadecimal) from the VSE ASSIGN macro. Refer to the

error are marked by an E. These positions are

IBM VSE/ESA System Macros Reference manual for an

represented in hexadecimal numbers.

explanation of this code.

System Action: Processing continues. If the

System Action: Processing continues. The tape unit

application server default CHARNAME is being

identified in this error message remains assigned to the

changed and the new CHARNAME is in error, the

database partition until the database manager

value of the current application server default

terminates and cannot be used until that time.

CHARNAME is used. If the current application server

default CHARNAME is in error, then

Operator Response: Save this message and give it to

INTERNATIONAL will be used as the CHARNAME

your system programmer.

value. Message ARI0143I indicates the value of the

Chapter 2. ARI0001-ARI0199 DB2 Server for VSE Control Messages

DB2 Server for VSE Messages and Codes (Version 7 Release 5) - page 1