Professional Documents
Culture Documents
Messages V9 PDF
Messages V9 PDF
1 for z/OS
Messages
GC18-9849-03
DB2 Version 9.1 for z/OS
Messages
GC18-9849-03
Note
Before using this information and the product it supports, be sure to read the general information under “Notices” at the
end of this information.
Information resources for DB2 for z/OS and related products . . . . . . . . . . . 813
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
iv Messages
About this information
This information helps you to understand the messages you could receive while
working with DB2.
This information assumes that your DB2 subsystem is running in Version 9.1
new-function mode. Generally, new functions that are described, including changes
to existing functions, statements, and limits, are available only in new-function
mode. Two exceptions to this general statement are new and changed utilities and
optimization enhancements, which are also available in conversion mode unless
stated otherwise.
Throughout the messages information, “DB2” means the program product. Other
DB2 products are given their complete names or abbreviations.
The DB2 Utilities Suite is designed to work with the DFSORT™ program, which
you are licensed to use in support of the DB2 utilities even if you do not otherwise
license DFSORT for general use. If your primary sort product is not DFSORT,
consider the following informational APARs mandatory reading:
v II14047/II14213: USE OF DFSORT BY DB2 UTILITIES
v II13495: HOW DFSORT TAKES ADVANTAGE OF 64-BIT REAL
ARCHITECTURE
These informational APARs are periodically updated.
Related information
DB2 utilities packaging (Utility Guide)
Accessibility features
The following list includes the major accessibility features in z/OS products,
including DB2 Version 9.1 for z/OS. These features support:
v Keyboard-only operation.
v Interfaces that are commonly used by screen readers and screen magnifiers.
v Customization of display attributes such as color, contrast, and font size
Keyboard navigation
You can access DB2 Version 9.1 for z/OS ISPF panel functions by using a keyboard
or keyboard shortcut keys.
For information about navigating the DB2 Version 9.1 for z/OS ISPF panels using
TSO/E or ISPF, refer to the z/OS TSO/E Primer, the z/OS TSO/E User’s Guide, and
the z/OS ISPF User’s Guide. These guides describe how to navigate each interface,
including the use of keyboard shortcuts or function keys (PF keys). Each guide
includes the default settings for the PF keys and explains how to modify their
functions.
vi Messages
Related accessibility information
Online documentation for DB2 Version 9.1 for z/OS is available in the Information
Management Software for z/OS Solutions Information Center, which is available at
the following Web site: http://publib.boulder.ibm.com/infocenter/dzichelp
http://www.ibm.com/support/docview.wss?&uid=swg27011656
This Web site has an online reader comment form that you can use to send
comments.
v You can also send comments by using the feedback link at the footer of each
page in the Information Management Software for z/OS Solutions Information
Center at http://publib.boulder.ibm.com/infocenter/db2zhelp.
Messages are identifiable by unique message numbers, which are eight to ten
characters long. Message identifiers have the following format:
DSNB209I
DSN The first three characters are DSN, which is the DB2 component prefix.
B The fourth character is the subcomponent identifier, which identifies the
subcomponent of DB2 that issued the message. Each subcomponent has an
associated hexadecimal identifier (hex ID), which is the hexadecimal
representation of the subcomponent identifier. In this example, B identifies
the DB2 buffer manager.
209 The numeric identifier is three to five characters long and begins at the fifth
character in the message. The numeric identifier is unique within the
subcomponent.
I The last character of the message identifier is the message type code. For DB2
messages in general, the I type code is used to indicate that this message is
for information only. However, some older messages use other type codes.
Messages in some subcomponents are associated with particular return codes. The
return codes can vary by subcomponent. The introduction to each set of messages
describes the return codes used for that subcomponent.
Subcomponent identifiers
The numbers that are assigned to messages and reason codes in DB2 are associated
with certain DB2 subcomponents.
The following table lists the DB2 subcomponents and shows the identifiers
associated with each component.
Table 2. Subcomponent identifiers used in messages and reason codes
Subcomponent Associated subcomponent Associated hexadecimal
identifier (for messages) identifier (for reason codes)
Call attachment facility A X’C1’
Buffer manager B X’C2’
TSO attachment facility E X’C5’
Message generator F X’C6’
Database descriptor manager G n/a
Precompiler, DSNH CLIST H X’C8’
Data manager I X’C9’
Recovery log manager J X’D1’
Distributed data facility L X’D3’
IMS attachment facility M X’D4’
XML manager n/a X’D5’
Data space manager P X’D7’
viii Messages
Table 2. Subcomponent identifiers used in messages and reason codes (continued)
Subcomponent Associated subcomponent Associated hexadecimal
identifier (for messages) identifier (for reason codes)
Recovery manager R X’D9’
Storage manager S X’E2’
Service controller, install T X’E3’
Utilities U X’E4’
Agent services manager V X’E5’
Instrumentation facility W X’E6’
Relational data system X X’E7’
Initialization procedures Y X’E8’
System parameter manager Z X’E9’
Service facilities 1 X’F1’
Subsystem support 3 X’F3’
subcomponent
Group manager 7 X’F7’
Sample applications 8 X’F8’
General command processor 9 X’F9’
Messages with DSNC and DSN2 identifiers and codes in the X’C3’range were
previously used to display CICS messages. For information about CICS messages,
see the information in the CICS Library.
Many IBM message references are also available from the IBM Publications Center
and some IBM product messages, including the DB2 for z/OS messages, are
enabled for the LookAt facility.
DSNA messages use common elements and share the same basic structure:
v Message number (DSNAnnna).
v The name of the CSECT responsible for writing the message.
v TCB address of the task currently executing.
v A series of tokens and token-explanations unique to each message.
The intent of these messages is to aid IBM development and the IBM Support
Center. They contain information that might not be meaningful except to IBM.
Messages in the DSNA8 range are intended for diagnosis and are documented in
Diagnosis Guide and Reference.
2 Messages
DSNA206E • DSNA209E
Control returns to the caller. Your request was not System action:
processed. The DB2 call attachment facility is ready for Control returns to the caller. The request was not
more input. processed. The DB2 call attachment facility is ready for
System programmer response: more input.
Refer the problem to the programmer using the DB2 System programmer response:
call attachment facility. Refer the problem to the programmer using the DB2
Programmer response: call attachment facility.
Correct the logic in your application. Check the spelling Programmer response:
of the action parameter type or keyword on the Remove explicit calls to DSNALI from the application
previous request passed to the DB2 call attachment program.
facility. The action parameter type you passed is listed
in the parm field of the DSNA800I trace message. If the Problem determination:
error is not the action parameter, the parameter in error
See a DSNTRACE trace job stream to understand the non-null value when the CONNECT TYPE parameter is
context of this message. set to SPECIFIC.
System action:
DSNA301I THE VALUE parm-value FOR
The stored procedure DSNACICS terminates without
PARAMETER parm-name IS NOT VALID
calling the CICS transaction.
Explanation:
System programmer response:
The stored procedure DSNACICS could not run
Ensure that the user exit DSNACICX sets the parameter
because one of the input parameters contains an
to a non-null value.
incorrect value.
Programmer response:
System action:
Correct the input parameter value in the SQL CALL
The stored procedure DSNACICS terminates without
statement, or ensure the the user exit DSNACICX sets
calling the CICS transaction.
the parameter to a non-null value.
System programmer response:
Severity:
Ensure that the user exit DSNACICX sets the parameter
12
to a valid value.
Programmer response:
DSNA304I THE USER EXIT DSNACICX
Correct the input parameter value specified on the SQL RETURNED RETURN CODE =
CALL statement. X’hhhhhhhh’ AND THE FOLLOWING
ERROR MESSAGE:
Severity:
Explanation:
12
The user exit DSNACICX returned a non-zero return
code and a message to stored procedure DSNACICS.
DSNA302I THE REQUIRED INPUT PARAMETER
The message that DSNACICX returns immediately
parm-name CONTAINS NULLS
follows message DSNA304I.
Explanation:
System action:
The stored procedure DSNACICS could not run
The stored procedure DSNACICS terminates without
because one or more of the required input parameters
calling the CICS transaction.
contains a null value.
System programmer response:
System action:
Correct the cause of the error message that the user exit
The stored procedure DSNACICS terminates without
generated.
calling the CICS transaction.
Programmer response:
System programmer response:
Contact the system programmer.
Ensure that the user exit DSNACICX sets the parameter
to a non-null value. Severity:
Programmer response: 12
Correct the input parameter value in the SQL CALL
statement, or ensure that the user exit DSNACICX sets DSNA305I THE CICS EXCI func REQUEST
the parameter to a non-null value. FAILED. CICS RESPONSE CODE =
X’hhhh’ CICS REASON CODE =
Severity:
X’hhhhhhhh’
12
Explanation:
DSNACICS uses the CICS EXCI Call interface to
DSNA303I THE PARAMETER NETNAME WAS
request the execution of a CICS server program. CICS
NOT SPECIFIED WHEN THE
EXCI interface call func resulted in an unexpected CICS
CONNECT TYPE OF SPECIFIC WAS
response code and reason code. Possible values of func
SPECIFIED
are:
Explanation:
Initialize_User
The input parameter NETNAME must contain a Initializes the EXCI user environment.
4 Messages
DSNA306I • DSNA307I
Allocate_Pipe
DSNA306I THE CICS SERVER PROGRAM program
Allocates a session to a CICS region.
ABENDED. CICS ABEND
Open_Pipe CODE=C’cccc’
Connects an allocated pipe to a receive session
Explanation:
of the CICS region.
The CICS server program that DSNACICS called
DPL_Request
abnormally terminated. CICS returns a four-character
Issues a request to execute the CICS server
abend code to indicate the error. These error codes are
program.
described in CICS Transaction Server for z/OS Problem
Close_Pipe Determination Guide.
Disconnects an open pipe from a CICS region.
System action:
Deallocate_Pipe
Stored procedure DSNACICS processes the next
Deallocates a pipe from a CICS region.
request. CICS does a backout to the last syncpoint and
forces the SYNCONRETURN option.
The failure can occur because the EXCI interface is not
properly enabled for the CICS subsystem. For System programmer response:
explanations of the CICS response code and reason
Correct the cause of the error in the server program.
code, see CICS Transaction Server for z/OS External
Ensure that the mirror transaction is still enabled after
Interfaces Guide.
this error. The mirror transaction must be enabled so
System action: that subsequent requests to run a server program are
accepted.
The stored procedure DSNACICS terminates without
calling the CICS transaction. Programmer response:
6 Messages
DSNA311I • DSNA314I
Determine why the operator canceled the stored an error in the DB2 stored procedure, refer to Part 3 of
procedure task. Diagnosis Guide and Reference.. Collect the following
diagnostic items:
Programmer response:
v Console output from the system on which the job
Contact the system programmer. was run, and a listing of the SYSLOG data set for the
Severity: period of time spanning the failure.
v Dynamic dump, taken to SYS1.DUMPxx data set, by
12 DB2 (04E and 04F abends).
v CICS trace listing.
DSNA311I DSNACICS ABNORMALLY
TERMINATED Programmer response:
Add a DSNDUMP DD statement to the JCL startup | OTMA Callable Interface API otmaci-api encountered an
procedure for the stored procedure address space in | error.
which DSNACICS runs. Then rerun the application that
| System action:
calls DSNACICS. This causes DB2 to generate an SVC
dump whenever it issues an error message for | The execution of the stored procedure, stored-procedure,
DSNACICS. | terminated before invoking IMS.
If you suspect an error in the DB2 stored procedure, | Programmer response:
refer to Part 3 of Diagnosis Guide and Reference. Collect
the following diagnostic items: | Refer to the IMS OTMA Guide and Reference for
| explanations of the return and reason codes.
v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure. | DSNA318I stored-procedure ERROR IN RRS
v Dynamic dump, taken to SYS1.DUMPxx data set, by | CTXRCC API. RC=return-code
DB2 (04E and 04F abends). | Explanation:
v CICS trace listing.
| An error was encountered in RRS when processing the
Programmer response: | two-phase commit.
Contact the system programmer. | System action:
Severity: | The execution of the stored procedure, stored-procedure,
| terminated before invoking IMS.
12
| Programmer response:
| DSNA315I stored-procedure FUNCTION func-name | Refer to the MVS Programming Resource Recovery
| HAS COMPLETED SUCCESSFULLY. | manual for an explanation of the return code.
| Explanation:
| DSNA319I stored-procedure RECEIVED UNKNOWN
| The stored procedure, stored-procedure, executed | FUNCTION func-name
| successfully.
| Explanation:
| System action:
| The stored procedure, stored-procedure, received an
| None. | unknown function name in parameter 1 of the stored
| Programmer response: | procedure call.
| None. | System action:
| The stored procedure terminated before invoking IMS.
| DSNA316I stored-procedure INPUT PARAMETER | Programmer response:
| ERROR. CALLER MUST PROVIDE
| INPUT FOR PARAMETER parm-name | Specify a function name known to the stored procedure
| WITH FUNCTION func-name. | in parameter 1.
| Explanation:
| DSNA320I DSNAIMS ERROR IN CTXSWCH
| A value for parameter parm-name is required for | DURING THE SWITCH AWAY FROM
| function func-name. | PRIVATE CONTEXT. RC=return-code
| System action: | Explanation:
| The execution of the stored procedure, stored-procedure, | An error was encountered in CTXSWCH API during
| terminated before invoking IMS. | the switch away from private context of DSNAIMS.
| Programmer response: | System action:
| Provide an appropriate value for the parameter, and | DSNAIMS is terminated after executing CTXSWCH.
| re-run the function.
| Programmer response:
| DSNA317I stored-procedure ERROR IN otmaci-api | Contact IBM service for the return code.
| API. RC=return-code, RSN1=reason-code1,
| RSN2=reason-code2, RSN3=reason-code3,
| RSN4=reason-code4.
| Explanation:
8 Messages
DSNA321I • DSNA604I
| System action:
| DSNA603I csect-name THE COLUMN column-name
| DSNAIMS is terminated after executing CTXSWCH. | IN TABLE table-name IS NOT VALID.
| Programmer response: | row-identifier= id. INVALID REASON
| CODE= xx
| Contact IBM service for the return code.
| Explanation:
10 Messages
DSNA611I • DSNA616I
| Contact the system programmer, or system | Correct the invalid data set name.
| administrator to arrange for the required RACF or
| equivalent security authorization. If more information
| Severity:
| is needed, look at the messages in the console log. | 12 (severe)
| Severity:
| 12 (severe) | DSNA614I csect-name UNABLE TO OBTAIN
| storage-usage STORAGE, SIZE = size
| BYTES
| DSNA611I csect-name THE data-set-attribute OF THE
| DATA SET DSNAME=dsname IS NOT
| Explanation:
| yy | An error occurred when the stored procedure
| Explanation: | attempted to obtain size bytes of storage for the
| storage-usage indicated. The csect-name in the message
| The data set indicated in the message cannot be | identifies the CSECT that issued the message.
| processed because the data set attribute is not
| supported. | System action:
| 12 (severe) | Severity:
| 12 (severe)
| DSNA613I csect-name THE DATA SET NAME
| DSNAME=dsname MUST NOT BEGIN | DSNA616I csect-name CATALOG SEARCH
| WITH A PATTERN MATCHING | INTERFACE ERROR, R15=xx, REASON
| CHARACTER | CODE= yy RETURN CODE=zz
| Explanation: | Explanation:
| The specified data set name begins with an ’*’ or ’%’. | An error occurred when the Catalog Search Interface
| This is not allowed for filtering, because it will cause a | (CSI) was called.
| massive search of the catalog and could tie up a lot of
| system resources. | System action:
| information on the interface’s R15, reason code, and | cannot access its DB2 task list table. It is operating only
| return code values. | on a single task list
| Severity: | Programmer response:
| 12 (severe) | Follow the diagnosis approach suggested for the SQL
| return code.
| DSNA617I csect-name IFCA ERROR, IFCARC1=vv,
| IFCARC2=ww, IFCABNM=xx, | DSNA619I csect-name SUBSYSTEM INTERFACE
| IFCAGRSN=yy, IFCAGBNM=zz | ERROR, FUNCTION CODE=n,
| RETURN CODE=xx, SSOBRETN=yy,
| Explanation:
| additional-info
| An error occurred when submitting a DB2 command
| Explanation:
| through the instrumentation facility interface (IFI).
| IFCARC1, IFCARC2, IFCABNM IFCAGRSN, and | An error occurred when a subsystem interface (SSI)
| IFCAGBNM are fields in the IFI Communication Area | function was called. The ’csect-name’ in the message
| (IFCA). | identifies the CSECT that issued the message. The SSI
| function codes are:
| System action:
| v 54 - Request subsystem version information call
| Processing terminates.
| v 79- SYSOUT Application Program Interface
| Programmer response: | v 80 - Extended status function call
| Refer to Codes, section ″X’E6......’ IFI reason codes″ for | System action:
| information on the IFCARC1, IFCARC2, and
| IFCAGRSN values. Consult the ″Instrument facility | Processing terminates.
| communications area (IFCA)″ section of the | Programmer response:
| Administration Guide for information about IFCABNM
| and IFCAGBNM. | Refer to z/OS DFSMS: Macro Instructions for Data Sets
| for more information on the MVS RETURN CODE
| Severity: | associated with the failed MVS non-VSAM macro.
| 12 (severe) | Severity:
| 12 (severe)
| DSNA618I csect-name SQL ERROR DURING SQL
| STATEMENT sql, object-type = object-name
| DSNA620I csect-name ERROR ALLOCATING DATA
| Explanation: | SET DSNAME=dsname, RETURN
| An SQL error resulted when the stored procedure | CODE=xx, ERROR REASON CODE=yy,
| issued an SQL statement sql for the identified DB2 | INFO REASON CODE=zz
| object. | Explanation:
| This message can be followed by a formatted form of | An error occurred when the DYNALLOC macro was
| the SQLCA and a text message based on the SQLCODE | invoked to dynamically allocate the named data set.
| field of the SQLCA, or it can be followed by an
| unformatted form of the SQLCA. | System action:
| csect-name | Processing terminates.
| Identifies the CSECT that issued the message | User response:
| sql The SQL statement encountering the error | Refer to z/OS MVS Programming: Authorized Assembler
| object-type | Services Guide for information on the DYNALLOC
| The type of DB2 object that the failed SQL | RETURN CODE, error reason code, and the
| statement is processing | informational reason code values.
| object-name | Severity:
| The name of the DB2 object that the failed | 12 (severe)
| SQL statement is processing
| System action:
| The stored procedure issuing the SQL statement
| terminates. On the operator’s console, the
| administrative scheduler that issues this message
12 Messages
DSNA621I • DSNA626I
| Severity: | Severity:
| 12 (severe) | 12 (severe)
| DSNA622I csect-name THE func-name FUNCTION | DSNA625I csect-name THE STORED PROCEDURE
| CALL IS UNSUCCESSFUL, reason | TASK WAS TERMINATED BY THE
| OPERATOR
| Explanation:
| Explanation:
| A z/OS C/C++ function func-name returned an
| unexpected error code. reason is the run-time error | The stored procedure did not complete successfully,
| message string that maps to the error code errno, | because it was terminated by the operator.
| followed by the errno2 value. | System action:
| System action: | Processing terminates.
| Processing terminates. | User response:
| User response: | Issue the SQL CALL statement again.
| Refer to C/C++ Run-Time Library Reference manual for | Severity:
| information on the z/OS C/C++ function error codes.
| 12 (severe)
| Severity:
| 12 (severe) | DSNA626I csect-name THE func-name FUNCTION
| CALL IS UNSUCCESSFUL,
| DSNA623I csect-name THE PROCEDURE | parm-name=parm-value, reason
| procedure-name DID NOT COMPLETE | Explanation:
| SUCCESSFULLY, RETURN CODE=xx
| A z/OS C/C++ function func-name returned an
| Explanation: | unexpected error code when the parameter parm-name
| The procedure procedure-name did not complete | was passed to the function with the value parm-value.
| successfully when it was internally invoked, returning | reason is the run-time error message string that maps to
| the indicated return code value. This message is | the error code errno, followed by the errno2 value.
| followed by the error message returned by the named | System action:
| procedure, if applicable.
| Processing terminates.
| System action:
| User response:
| Processing terminates.
| Refer to C/C++ Run-Time Library Reference manual for
| User response: | information on the z/OS C/C++ function error codes.
| Review the error message returned by the named | Severity:
| stored procedure. Refer to the Messages for more
| information about the error message returned. Refer to | 12 (severe)
| the for more information about the error message
| returned.
| DSNA627I csect-name THE funcname FUNCTION | DSNA631I csect-name THE jes-version COMMAND
| CALL IS UNSUCCESSFUL, RETURN | command WAS ISSUED BUT NOT
| CODE= xx, ERROR REASON | ACCEPTED
| CODE=yy, INFO REASON CODE=zz
| Explanation:
| Explanation:
| The command response received does not indicate
| A z/OS C/C++ function returned an unexpected return | whether the command was accepted or completed. The
| code. The ’csect-name’ in the message identifies the | ’csect-name’ in the message identifies the CSECT that
| CSECT that issued the message. The possible names of | issued the message. The possible commands are:
| the z/OS C/C++ function are: | v CANCEL - Cancel a job
| v dynalloc(): Allocate a data set | v PURGE - Purge a job
| v dynfree(): Deallocate a data set
| System action:
| An error occurred when a subsystem interface (SSI) | Processing completes. The RETURN_CODE output
| function was called. The ’csect-name’ in the message | parameter is 8 if the command was issued by a stored
| identifies the CSECT that issued the message. The SSI | procedure.
| function codes are:
| User response:
| v 54 - Request subsystem version information call
| v 79- SYSOUT Application Program Interface
| Issue the JES2 command $D JOB or the JES3 command
| *INQUIRY,J to display the current status of the job.
| v 80 - Extended status function call
| Severity:
| System action:
| 8 (error)
| If the function name is dynalloc(), then processing
| terminates.
| DSNA632I csect-name JOB SUBMISSION FAILED
| Programmer response:
| Explanation:
| Refer to z/OS DFSMS: Macro Instructions for Data Sets
| for information on the DYNALLOC RETURN CODE, | An error occurred while submitting a job for execution.
| ERROR REASON CODE, and INFO REASON CODE | A job identifier was not returned when the ENDREQ
| values. | macro was issued after a complete job was written to
| the internal reader. The ’csect-name’ in the message
| Severity: | identifies the CSECT that issued the message.
| 12 (severe) if the function name is dynalloc(). If the | System action:
| function name is dynfree(), then the Severity is the
| dynfree() return code. | Processing terminates.
| User response:
| DSNA629I csect-name THE PARAMETER parm-name | Review the submitted JCL records to ensure that it has
| RETURNED BY THE STORED | a valid JOB statement.
| PROCEDURE proc-name IS NOT VALID.
| INVALID REASON CODE=xx | Severity:
| Explanation: | 12 (severe)
| An invalid value was returned by the indicated
| procedure for the specified parameter. The cause of the | DSNA634I csect-name THE JES-MANAGED
| invalid error is identified by the invalid reason code | SYSOUT DATA SET IS EMPTY,
| value in the message text. The specified parameter is | JOBID=jobid
| not valid for the indicated reason:
| Explanation:
| 3 Value is null.
| A request was made to process SYSOUT data sets
| System action: | residing on JES spool for the indicated job identifier
| specified. However, the indicated job does not have any
| Processing terminates. | SYSOUT data sets.
| User response: | System action:
| Report the problem to the IBM Support Center. | No action is taken with the specified job identifier.
| Severity: | User response:
| 12 (severe) | If the job action was requested by a stored procedure,
14 Messages
DSNA635I • DSNA640I
| 12 (severe) | Explanation:
| The sequence number of the rows in the indicated table
| DSNA635I csect-name AN INTERNAL ERROR | is not in ascending sequence, or the row sequence
| OCCURRED. additional-info | number does not start with 1.
| Explanation: | System action:
| An error, as indicated in additional-info, occurred. | Processing terminates.
| System action: | User response:
| Processing terminates. | Correct the sequence number of the rows in the
| indicated table.
| User response:
| Severity:
| Report the problem to the IBM Support Center.
| 12 (severe)
| Severity:
| 12 (severe) | DSNA639I csect-name THE NUMBER OF ROWS
| table-size IN THE INPUT TABLE
| DSNA636I csect-name DB2 THREAD WAS | table-name AND THE NUMBER OF
| CANCELED | OBJECTS objnum SPECIFIED IN THE
| PARAMETER parm-name DO NOT
| Explanation: | MATCH
| The thread running the stored procedure was canceled. | Explanation:
| System action: | The number of rows in the indicated table did not
| Processing terminates. | match the number of objects specified in the named
| parameter.
| User response:
| System action:
| If necessary, issue the SQL CALL statement again.
| Processing terminates.
| Severity:
| User response:
| 12 (severe)
| Correct the number of objects specified in the indicated
| parameter, or repopulate the named table with the
| DSNA637I csect-name I/O ERROR ON DATA SET | correct number of rows.
| Explanation: | Severity:
| An I/O error occurred while processing a data set or | 12 (severe)
| library member.
| System action: | DSNA640I csect-name SHUTDOWN DURATION
| Processing terminates. | xxxx REACHED, SHUTDOWN
| INITIATED
| User response:
| Explanation:
| Look at the messages in the console log for more
| information. If necessary, report the problem to the IBM | When the overall execution time reached the indicated
| Support Center. | shutdown duration, shutdown was initiated. When
| shutdown is initiated, current utility executions run to
| Severity: | completion but no new utility will be started.
| 12 (severe) | System action:
| Current utility executions are allowed to run to
| completion, but no new utility will be started.
| User response:
| Determine which objects have not been processed due
| to the shutdown. Call
Chapter 1. DSNA messages 15
DSNA643I • DSNA651I
| SYSPROC.ADMIN_UTL_SCHEDULE again to process | format. The error was detected at position xx in the
| the unprocessed objects. If necessary, increase the | parameter value.
| SHUTDOWN_DURATION input parameter on the SQL
| CALL statement.
| The csect-name in the message identifies the CSECT that
| issued the message.
| Severity:
| System action:
| 4 (warning)
| The stored procedure terminates.
16 Messages
DSNA652I • DSNA657I
18 Messages
DSNA674I • DSNA678I
| System action:
| DSNA680I csect-name THE ADMIN SCHEDULER
| The administrative scheduler continues running, but | proc-name TASK LIST list-name IS
| some scheduled tasks cannot be executed. | CORRUPTED
20 Messages
DSNA683I • DSNA692I
22 Messages
Chapter 2. DSNB messages
Message identifiers that begin with DSNB communicate information about the buffer
manager.
Correct the situation, and then reinvoke the application. DB2 is ready to clean up the associated table space or
index space. However, before any cleanup is initiated,
Problem determination: DB2 requests a drain on the table space or index space.
Collect the following diagnostic items: DB2 waits indefinitely for this lock. Therefore, all
activities against the table space and/or index space
v Console output from the system on which the job
must be quiesced before the cleanup process can
was run, and a listing of the SYSLOG data set for the
proceed. If the associated object is an index space, all
period of time spanning the failure.
activities against the table space for which the index
v Listing of SYS1.LOGREC data set, obtained by space is defined must also be quiesced. After the
executing IFCEREP1. cleanup process completes, the table space or index
v IDCAMS LISTCAT output for the ICF (VSAM) space is automatically made accessible to users.
catalog that contains the DB2 subsystem catalog that
User response:
defined the failing index or table.
v VTOC listing of the disk volume on which the failing If the clean up activity does not appear to be
operation occurred. completed, DB2 might still be waiting for a drain lock
on the table space. Issue a -DISPLAY DATABASE
. CLAIMERS command for the table space in question
(for index spaces, this would be the associated table
DSNB209I csect-name-BUFFER MANAGER space) to determine whether the clean up routine is still
TABLESPACE/INDEXSPACE CLEAN-UP waiting for a lock and if so, to determine the holders of
ROUTINE (DSNB1CFC) HAS BEEN the table space lock. If the jobs are holding the table
SCHEDULED FOR DBNAME = dbn, space lock for a very long duration (for instance,
SPACENAME = spn, PSID = X’psid’ wait-for-input), it might be necessary to cancel those
jobs in order to allow the clean up process to proceed.
Explanation:
DB2 detected an abnormal condition for one of the DSNB212I csect-name-RECOVER PAGE STARTING
following reasons: DBNAME = dbn , SPACENAME = spn ,
v The associated table space or index space contains PAGE NUMBER = X’pno’
modified pages that cannot be written to DASD for a
Explanation:
period of time that is longer than expected. This can
be caused by either an unusually long period of The buffer manager (BM) subcomponent of DB2
contiguous update or by an internal logic error. discovered an inconsistent page with unbalanced write
v This message follows an abnormal termination due intents. DB2 is ready to do online recovery on the page
to inconsistent data or an incomplete update to the using the DB2 log. The dbn indicates the associated
page. database name. The spn indicates the table space name
or index space name. The pno is the page number (in
DB2 scheduled the table space or index space cleanup hexadecimal) within the table space or index space that
routine (DSNB1CFC) for the associated table space or is logically inconsistent.
index space. DSNB1CFC acquires a drain lock to ensure System action:
24 Messages
DSNB215I • DSNB223I
Processing continues. for the associated table space or index space. Refer to
message DSNB209I for the reasons why the buffer
manager schedules the table space or index space
DSNB215I csect-name-ONLINE RECOVERY FOR
cleanup process. The dbn indicates the associated
AN INCONSISTENT PAGE HAS BEEN
database name. The spn indicates the table space name
COMPLETED FOR DBNAME = dbn ,
or index space name.
SPACENAME = spn , PAGE NUMBER =
X’pno’ System action:
Explanation: Processing continues.
The recovery process for an inconsistent page
completed. The dbn indicates the associated database DSNB221I csect-name-BUFFER MANAGER
name. The spn indicates the table space name or index TABLESPACE/INDEXSPACE CLEAN-UP
space name. The pno is the page number (in PROCESS WAS NOT REQUIRED FOR
hexadecimal) within the table space or index space that PSID = X’psid’
was logically inconsistent.
Explanation:
System action:
This message indicates that the buffer manager (BM)
Processing continues. table space or index space cleanup process was
bypassed for the associated table space or index space.
After quiescing all other activities against the table
DSNB217I csect-name-ONLINE RECOVERY FOR
space or index space, the buffer manager discovered
AN INCONSISTENT PAGE WAS
that the table space or index space is no longer in
UNSUCCESSFUL FOR DBNAME = dbn
active mode; that is, it was closed.
, SPACENAME = spn , PAGE NUMBER
= X’pno’ The abnormal condition detected earlier was resolved
by buffer manager close page set processing. Refer to
Explanation:
the corresponding message, DSNB209I, using psid as
The recovery process for an inconsistent page failed. the matching field, for the reasons the buffer manager
The page is written to DASD as logically inconsistent. schedules the table space or index space cleanup
This message is issued in response to message process. The psid is the internal identifier for the
DSNB212I, which was issued to indicate the start of the associated table space or index space.
recovery process. The dbn indicates the associated
System action:
database name. The spn indicates the table space name
or index space name. The pno is the page number (in Processing continues.
hexadecimal) within the table space or index space that
was logically inconsistent.
DSNB223I csect-name-BUFFER MANAGER
System action: TABLESPACE/INDEXSPACE CLEANUP
PROCESS WAS SKIPPED FOR PSID =
The page is marked as logically inconsistent and is
X’psid’
unavailable until it is repaired. The execution unit
driving this function proceeds normally. Explanation:
Problem determination: This message indicates that the table space or index
space cleanup process was bypassed for the associated
A DSNI012I message might be issued before this
table space or index space. During the process of
message to indicate the same failure. If it is, a 00C90102
quiescing all other activities against the table space or
abend dump might help determine the cause of this
index space, an error that is not recoverable was
failure. Otherwise, see SYS1.LOGREC for any abend
detected. The error might be caused by any of the
that occurred between the associated DSNB212I
following conditions:
message and this message. Use the time stamp on the
log records to find this abend. v An out-of-storage condition was detected by IRLM.
v The table space or index space was dropped because
of a backout.
DSNB219I csect-name-BUFFER MANAGER
TABLESPACE/INDEXSPACE CLEAN-UP
It is assumed that the abnormal condition detected
PROCESS HAS BEEN COMPLETED
earlier can later be resolved by the close page set
FOR DBNAME = dbn , SPACENAME =
processing. Refer to the corresponding message
spn
DSNB209I (use psid as the matching field) for the
Explanation: reasons for scheduling the table space or index space
cleanup process. The psid specifies the internal
This message indicates that the buffer manager (BM)
identifier for the associated table space or index space.
table space or index space cleanup process completed
System action: indicating the type of I/O error that occurred. If an IOS
message was issued, follow the problem determination
Processing continues.
directions for that message.
System programmer response:
Collect the following diagnostic items:
The associated table space or index space might contain v Console output from the system on which the job
inconsistent data. Issue the DB2 STOP TABLESPACE or was run, and a listing of the SYSLOG data set for the
INDEXSPACE command to allow close page set period of time spanning the failure.
processing to perform cleanup for the associated table
v Listing of SYS1.LOGREC data set, obtained by
space or index space.
executing IFCEREP1.
.
DSNB224I csect-name- BUFFER MANAGER I/O
ERROR DURING function,
DBNAME=dbn,SPACENAME=snm, DSNB225I csect-name - BUFFER MANAGER I/O
DATA SET NUMBER=dsno, PAGE ERROR DURING function
NUMBER=X’pno’, MM ERROR DBNAME=dbn,SPACENAME=snm,
FLAG=X’aa’, CSW STATUS=X’bbbb’, DATA SET NUMBER=dsno, MM
SENSE BYTES=X’cccc’, SEEK ERROR CODES=X’aaaaaaaa’ DB2
ADDRESS=X’dddddddddddddddd’ REASON CODE=X’bbbbbbbb’
Explanation: Explanation:
An I/O error was encountered by the buffer manager DB2 encountered an I/O error. The function specified
(BM) subcomponent of DB2. The function specified in in the message is READ, WRITE, CASTOUT, or
the message is READ, WRITE, or FORMAT. The FORMAT. The message contains the database name,
message gives the database name, table space name or table space name or index space name, data set
index space name, data set number, and page number number, media manager error information returned at
(in hexadecimal) of the page for which the I/O the time of the failure, and the DB2 reason code
operation was being performed. The remaining associated with this failure.
information is error information returned by the media
System action:
manager and is used for error analysis by IBM support
personnel. Except for a castout error, the application terminates
with abend X’04E’ and reason code 00C200A4 or
System action:
00C200C0. If an error occurs during castout, processing
The system action depends on the function being continues.
performed. If the function is WRITE, or if the function
Operator response:
is READ and the operation was performed during
restart or rollback, the I/O error page range of the data Notify the system programmer and follow the
set is updated and message DSNU086I is issued. In directions given for the reason code described in Codes.
most cases (READ, synchronous WRITE, FORMAT), a
’resource not available’ is returned to the user with a System programmer response:
reason code that identifies the nature of the problem. If you suspect an error in DB2, refer to Part 2 of
After being issued 10 times for a given data set, this Diagnosis Guide and Reference for information on
message is disabled for that data set until it is closed identifying and reporting the problem.
and reopened. Problem determination:
Operator response: This message is issued before the occurrence of abend
Notify the system programmer. X’04E’ and reason code 00C200A4 or 00C200C0 to
provide information related to the media manager
System programmer response: failure.
See documentation in Codes for the reason code Check the MVS console log for an IOS error message
returned to the user in the SQLCA or in utility indicating the type of I/O error that occurred. If an IOS
messages.If you suspect an error in DB2, refer to Part 2 message was issued, follow the problem determination
of Diagnosis Guide and Reference for information on directions for that message.
identifying and reporting the problem.
Collect the following diagnostic items:
Problem determination: v Console output from the system on which the job
See the Problem Determination section of the reason was run, and a listing of the SYSLOG data set for the
code returned to user. period of time spanning the failure.
v Dynamic dump, taken to SYS1.DUMPxx data set, by
Check the MVS console log for an IOS error message
DB2 (04E and 04F abends).
26 Messages
DSNB226I • DSNB228I
v Listing of SYS1.LOGREC data set, obtained by v DSN1COPY-generated copy of the table and index,
executing IFCEREP1. taken before any recovery is performed.
v IDCAMS LISTCAT output for the ICF (VSAM) .
catalog that contains the DB2 subsystem catalog that
defined the failing index or table.
DSNB227I csect-name - DFHSM RECALL FAILED
v VTOC listing of the disk volume on which the failing
FOR DSNAME=dsn HSMRC=aaaaaaaa
operation occurred.
HSMRSN=bbbbbbbb
.
Explanation:
The attempt to recall a migrated data set failed.
DSNB226I csect-name - BUFFER MANAGER PAGE
DSNAME identifies thedata set. HSMRC and HSMRSN
GET ROUTINE DETECTED AN
are the return code and reason code given by DFHSM.
INVALID PAGE IN DBNAME=dbn
SPACENAME=snm DATA SET System action:
NUMBER= dsno PAGE
EXPECTED=X’aaaaaa’ PAGE NUMBER A ’resource not available’ code is returned to the user.
FOUND=X’bbbbbb’ Operator response:
Explanation: Notify the system programmer.
An unexpected page was received during buffer System programmer response:
manager (BM) get page processing. The page set
involved is identified by the database name, space Use the information provided in the message to
name, and data set number. The page in error is determine the reason forthe DFHSM recall failure.
identified by page expected aaaaaa. Page number bbbbbb Problem determination:
was found in the buffer that should contain the
expected page. Refer to Codes for an explanation of the return and
reason codes contained in this message. Refer to the
System action: DFHSM message ARC11nnI, wherenn is the value of
The application is terminated with abend X’04E’ and HSMRC.
reason code 00C200F7.
Operator response: DSNB228I csect-name GROUP BUFFER POOL
gbpname CANNOT BE ACCESSED FOR
Notify the system programmer and follow the function MVS IXLCACHE REASON
directions given for reason code 00C200F7 in Codes. CODE=reason
System programmer response: Explanation:
If you suspect an error in DB2, refer to Part 2 of While accessing group buffer pool gbpname for function
Diagnosis Guide and Reference for information on function DB2 received an error from the MVS
identifying and reporting the problem. IXLCACHE request.
Problem determination: function READ or WRITE
This message is issued before the occurrence of abend reason Reason code from the MVS IXLCACHE
X’04E’ and reason code 00C200F7 to provide request
information about the page set involved.
System action:
Collect the following diagnostic items:
The system action depends on the function being
v Console output from the system on which the job
performed. If the function is a WRITE, or a READ
was run, and a listing of the SYSLOG data set for the
performed during rollback or DB2 restart, the page is
period of time spanning the failure.
added to the logical page list (LPL) for the data set and
v Dynamic dump, taken to SYS1.DUMPxx data set, by message DSNB250E is issued. Otherwise, ’resource
DB2 (04E and 04F abends). unavailable’ is returned to the user with a reason code
v Listing of SYS1.LOGREC data set, obtained by that identifies the specific problem.
executing IFCEREP1.
System programmer response:
v IDCAMS LISTCAT output for the ICF (VSAM)
catalog that contains the DB2 subsystem catalog that See MVS/ESA Programming: Sysplex Services Reference for
defined the failing index or table. an explanation of the MVS IXLCACHE reason code.
v VTOC listing of the disk volume on which the failing
operation occurred.
28 Messages
DSNB301E • DSNB302I
The traceid is for IBM serviceability. The reasontype For DB2 reason code 00C20204, which indicates a
explains why the pages were added into LPL; the problem during MVS IXLCONN processing, this
following list contain the reason types: message is issued once for each DB2 subsystem for
each IXLCONN reason code until the failure condition
DASD DB2 encountered a DASD I/O error when
is corrected. If the DB2 reason code is not 00C20204,
trying to read or write pages on DASD.
then reason2 contains zeros. See MVS/ESA Programming:
LOGAPPLY Sysplex Services Reference for an explanation of MVS
DB2 cannot apply log records to the pages. IXLxxxx reason codes
preference list cannot be found (for example, not v DB2 puts the group buffer pool into ’damage
enough free space), and therefore allocation occurs in a assessment pending’ (DAP) status. Message
different coupling facility. MVS tries to allocate the DSNB304I indicates the DAP status. The group
structure in the facility that best meets the structure buffer pool cannot be accessed until DAP status is
allocation request as follows: cleared.
1st choice: v The DB2 damage assessment process determines
Coupling facility that meets the volatility which table spaces and index spaces are using the
requirement, the space requirement, and the failed group buffer pool and puts those spaces into
exclusion list requirement. ’group buffer pool recovery pending’ (GRECP)
status.
2nd choice:
v After DB2 sets all the necessary spaces to GRECP
Coupling facility that meets the volatility
status, the DAP status for the group buffer pool is
requirement and the storage requirement.
cleared. Message DSNB305I indicates that DAP status
3rd choice: is cleared.
Coupling facility that has the best fit (most
available free space) even though this might
DSNB305I csect-name ’DAMAGE ASSESSMENT
be less than the amount requested.
PENDING’ STATUS WAS CLEARED
4th choice: FOR GROUP BUFFER POOL gbpname
Structure cannot be allocated.
Explanation:
IFCID 0250, if activated, contains a list of the coupling Damage assessment completed and the ’damage
facilities on which allocation was attempted. assessment pending’ (DAP) status is cleared for the
group buffer pool (GBP). At this point, the group buffer
pool status is no longer restricted and DB2 attempts to
DSNB303E csect-name A LOSS OF CONNECTIVITY reconnect to the group buffer pool on the next reference
WAS DETECTED TO GROUP BUFFER to a GBP-dependent page set within the associated
POOL gpbname buffer pool.
Explanation: Message DSNB304I precedes this message.
Connectivity to group buffer pool gpbname was lost.
System action: DSNB306I csect-name THE REQUESTED LENGTH
OF THE LOCAL CACHE VECTOR
DB2 disconnects from the coupling facility structure COULD NOT BE ALLOCATED FOR
with REASON=FAILURE. GROUP BUFFER POOL gbpname
The action taken in response to this problem depends REQUESTED LENGTH = length1
on the attempted function, as follows: ALLOCATED LENGTH = length2
v For a coupling facility read: SQLCODE -904 (resource Explanation:
unavailable) is returned to the SQL user with a
DB2 connected to the group buffer pool indicated by
reason code indicating the specific error.
gbpname, but the MVS Cross-system Extended Services®
v For a coupling facility read during rollback, backout, (XES) component could not allocate the requested size
or restart: The inaccessible page is added to the of the local cache vector (LCV) in the hardware system
logical page list (LPL) for the page set. Message area (HSA). DB2 requires an LCV size that is large
DSNB250E is issued for the first page of each data enough to handle all pages in the member’s buffer
set added to the LPL. pool.
v For a coupling facility read during castout: The
length1 indicates the LCV size (in number of bits) that
castout operation cannot complete.
DB2 requested. length2 indicates the LCV size (in
v For a coupling facility write: The changed page is number of bits) that XES was able to allocate.
added to the LPL for the page set.
To prevent flooding the operator console, this message
is only issued once per DB2 member per group buffer
DSNB304I csect-name GROUP BUFFER POOL pool until the condition is corrected.
gbpname WAS SET TO ’DAMAGE
ASSESSMENT PENDING’ STATUS System action:
30 Messages
DSNB307I • DSNB309I
System programmer response: DB2 successfully connected to the group buffer pool
and allocated the group buffer pool in a coupling
There is not enough HSA storage on the processor to
facility. However, the group buffer pool was allocated
support the size of the local cache vector. The details of
in a coupling facility containing a structure in the
HSA allocation are machine-dependent and are defined
exclusion list.
by the hardware. To correct this problem, take one or
both of the following actions: System programmer response:
v Consult the documentation for your processor If you require that the exclusion list be honored, you
hardware to determine if the HSA storage allocation must ensure that there is sufficient space in the
can be increased, and if so, how to do it. coupling facilities that are not in the exclusion list.
v Modify the software configuration in your parallel IFCID 0250 provides information about which facilities
sysplex to reduce the number or size of the vectors were attempted.
that are in use by other coupling facility structure
users. Consider the following possible solutions:
DSNB308I csect-name GROUP BUFFER POOL
– Use the DB2 ALTER BUFFERPOOL command to gbpname WAS SUCCESSFULLY
reduce the size of this local buffer pool. This ALLOCATED BUT THE ALLOCATED
means that you might have to reduce the size of SIZE OF alloc_size IS LESS THAN THE
the virtual pool. REQUESTED SIZE OF req_size
– Use the DB2 ALTER BUFFERPOOL command to
Explanation:
reduce the size of another local buffer pool that is
already connected to a group buffer pool. This DB2 successfully connected to the group buffer pool
means that you might have to reduce the size of and allocated the group buffer pool in a coupling
the virtual pool. If you make a connected buffer facility. However, the allocated size of the group buffer
pool smaller, DB2 can usually contract the size of pool was less than the requested size in the MVS
the corresponding LCV dynamically, making HSA CFRM administrative policy because there is not
storage available. However, DB2 cannot always do enough space in the preference list facilities. Both
the dynamic LCV contraction. In cases where DB2 alloc_size and req_size are in 4KB blocks.
cannot dynamically contract the LCV size, you can
use the DB2 ALTER BUFFERPOOL command to System programmer response:
either force a deallocation of the LCV or to force a IFCID 0250 provides information about which coupling
contraction of the LCV as follows: facilities were used for attempted allocation.
1. Redefine the virtual pool to be smaller than
the original size.
DSNB309I csect-name GROUP BUFFER POOL
2. Take one of the following actions: gbpname HAS BEEN DISCONNECTED
a. Make the virtual pool very small (perhaps WITH A REASON OF ’reason’
50 pages or less). Making the virtual pool
Explanation:
sufficiently small should let DB2
dynamically contract the LCV, or DB2 disconnected from the named group buffer pool.
b. Delete the virtual pool to let DB2 reason indicates one of the following values:
disconnect from the group buffer pool. This
frees the entire LCV associated with that NORMAL
member’s connection to that group buffer DB2 disconnected the group buffer pool
pool. normally. MVS deletes the connection.
– Consolidate your group buffer pool-dependent FAILURE
page sets into fewer buffer pools to reduce the DB2 disconnected the group buffer pool
number of group buffer pool connections. abnormally. MVS puts the connection into a
– Consult the documentation for the other software ’failed-persistent’ state. DB2 disconnects the
components that might be using a coupling GBP with a reason of FAILURE when some
facility cache or list structure with an associated type of error has been detected, and castout
LCV to determine whether it is possible to either processing cannot proceed. Usually the error
delete the connection or to reduce the size of the involves a connectivity failure to either the
LCV associated with the connection. coupling facility or DASD. This message is
preceded by message DSNB303E, and
probably a series of DSNB311I and DSNB312I
DSNB307I csect-name GROUP BUFFER POOL messages.
gbpname WAS SUCCESSFULLY
ALLOCATED BUT THE EXCLUSION If this message is issued because connectivity was lost
LIST WAS NOT HONORED to the group buffer pool, this message signifies that this
Explanation: DB2 member has completed its processing of the error.
System programmer response: need to be recovered. This message is issued after DB2
has completed its processing for the partition; this is
See the system programmer response for message
the earliest point at which you can recover the LPL
DSNB311I or DSNB312I.
pages for that partition.
System action:
DSNB310I csect-name GROUP BUFFER POOL
gbpname IS ALLOCATED IN A The pages in the LPL are not accessible until they have
NONVOLATILE STRUCTURE been recovered.
Explanation: System programmer response:
The coupling facility storage in which the group buffer Issue the START DATABASE command on the table
pool is allocated was previously volatile, but is now space or index space partition to recover the LPL pages.
nonvolatile. For availability reasons, we recommend The START DATABASE command must be issued from
that DB2 group buffer pools be allocated in nonvolatile a DB2 member that can connect to the group buffer
coupling facility storage. When DB2 connects a group pool. Alternatively, the RECOVER utility or the LOAD
buffer pool, it requests that the backing coupling utility can be used to recover the LPL pages.
facility structure be allocated in nonvolatile storage. If
the request for nonvolatile storage is not honored, DB2
DSNB313I csect-name GROUP BUFFER POOL
issues message DSNB302I.
gpbname TO BE DISCONNECTED
System action: REASON=reason LOSSCONN
PERCENTAGE=percentage
DB2 processing continues.
Explanation:
DSNB311I csect-name DBNAME database SPACE This DB2 member is disconnecting from group buffer
NAME spacename HAS PAGES IN THE pool gpbname because it has lost connectivity to the
LOGICAL PAGE LIST coupling facility in which the group buffer pool is
allocated.
Explanation:
reason is one of the following:
This message is issued after a loss of connectivity to a
group buffer pool was detected. The message indicates NOSFMPOL
that the named table space or index space has one or MVS cannot determine the scope of the loss of
more pages in the logical page list (LPL) that need to connectivity because there is no active SFM
be recovered. This message is issued after DB2 has policy with CONNFAIL(YES).
completed its processing for the table space or index
LOSSCONN
space; this is the earliest point at which you can
MVS determined that the scope of the loss of
recover LPL pages for that table space or index.
connectivity was less than 100%.
System action:
NOXESEVL
The pages in the LPL are not accessible until they have MVS started to try to determine the scope of
been recovered. the loss of connectivity, but some condition
occurred which prevented MVS from being
System programmer response:
able to complete the evaluation. One example
Issue the START DATABASE command with the named of such a condition would be that the SFM
table space or index to recover the LPL pages. The policy became inactive while MVS was trying
START DATABASE command must be issued from a to do the evaluation.
DB2 member that can connect to the group buffer pool.
Alternatively, the RECOVER utility or the LOAD utility If reason is LOSSCONN, then percentage indicates the
can be used to recover the LPL pages. percentage of lost connectivity that was calculated by
MVS. MVS evaluates the scope of the loss of
connectivity in terms of SFM weights associated with
DSNB312I csect-name DBNAME database SPACE
the systems which have lost connectivity and which
NAME spacename PARTITION
have active connectors to the coupling facility structure
part-number HAS PAGES IN THE
(if there are systems that do not have an active
LOGICAL PAGE LIST
connector to the coupling facility structure, then those
Explanation: systems are not factored into the ″percentage loss of
connectivity″ calculation).
This message is issued after a loss of connectivity to a
group buffer pool was detected. The message indicates
If reason is not LOSSCONN, then percentage is not
that a partition of the named table space or index has
applicable (it should appear as zero).
one or more pages in the logical page list (LPL) that
32 Messages
DSNB314I • DSNB315I
CONERROR Explanation:
The named group buffer pool is currently YES The group buffer pool will be used for data
allocated in a coupling facility, but DB2 cannot caching.
connect to the group buffer pool because the
system on which it is running does not NO The group buffer pool will not be used for
currently have connectivity, and MVS has data caching. It will be used for cross
indicated that currently no other member is invalidation only.
actively connected and has connectivity.
One DB2 member issues this message whenever the
DAP The named group buffer pool is in damage structure is allocated. DB2 detects this on the first
assessment pending (DAP) state. connection to the group buffer pool either in the
System action: mainline processing or during group buffer pool
rebuild.
DB2 triggers the damage assessment function to ensure
that any changed pages that might have been cached in System action:
the affected group buffer pool get marked as ″needing DB2 processing continues.
recovery″ (the objects to which the pages belong are
marked in GRECP state). This message should be
immediately followed by a DSNB304I message
indicating that the group buffer pool has been entered
into damage assessment pending (DAP) state.
If there are transactions that are in progress at the time
34 Messages
DSNB322I • DSNB325A
This message reports the group buffer pool recovery You can relieve the GBP storage shortage by taking one
pending (GRECP) status of the table space or index or more of the following actions:
space identified by the internal identifiers DBID and v Use the ALTER GROUPBUFFERPOOL command to
PSID. This message is issued instead of message lower the CLASST and GBPOOLT castout thresholds.
DSNB321I when the name of the table space or index v Use the ALTER GROUPBUFFERPOOL command to
space is not available. The table space or index space lower the GBPCHKPT GBP checkpoint frequency.
cannot be automatically recovered because there are
v Use the MVS SETXCF START,REBUILD command to
retained physical locks (P-locks) on the space.
expand the GBP coupling facility structure. If you
System action: rebuild, you can use the ALTER
GROUPBUFFERPOOL command to lower the RATIO
The table space or index space is not accessible. so that a higher percentage of the GBP storage is
User response: given to data entries over directory entries.
v If you are running on MVS 5.2 or a subsequent
Issue the -DISPLAY DATABASE(*) SPACENAM(*)
release, you can use the MVS SETXCF START,ALTER
RESTRICT command to determine the table spaces or
command to expand the size of the GBP (the
index spaces in GRECP status. First, start the failed
maximum size to which you can expand is
determined by the SIZE parameter in the CFRM If the MVS IXLCONN reason code is xxxx0C08
policy that was used to allocate the GBP). (structure allocation failed because there was no
suitable facility to allocate based on the preference list
If you don’t do anything to relieve the storage in the MVS CFRM administrative policy), or if the MVS
shortage, message DSNB228I appears if a write to the IXLCONN reason code is xxxx084C (user does not have
GBP fails due to a ’GBP full’ condition. If DB2 detects a proper Security Access Facility (SAF) authorization),
’full’ condition, it will suspend the transaction, initiate then IFCID 0250, if active, contains additional
castout activity, and then retry the write to the GBP. If diagnostic information.
the GBP write still fails after several retry attempts,
then DB2 adds the page to LPL.
DSNB331I csect-name REBUILD STARTED FOR
GROUP BUFFER POOL gbpname
Message DSNB327I appears when the GBP storage REASON = reason
shortage is relieved.
Explanation:
You can monitor the amount of GBP storage in use A rebuild has been initiated for the named group buffer
with the DISPLAY GBPOOL command and with the pool. reason indicates the reason why the rebuild was
DB2 statistics trace. Monitor the castout activity to initiated. reason can be one of the following:
ensure that castouts are keeping up with the rate of
GBP-write activity. You can use Performance trace OPERATOR
classes 20 and 21 (specifically, IFCIDs 0261, 0262 and The operator initiated a SETXCF command to
0263) to do more detailed monitoring of the DB2 initiate the rebuild.
castout processing.
LOSSCONN
MVS detected a loss of connectivity to the
DSNB327I csect-name GROUP BUFFER POOL group buffer pool.
gbp-name HAS ADEQUATE FREE
SPACE This message is issued by each DB2 member
participating in the rebuild.
Explanation:
System action:
The group buffer pool (GBP) coupling facility structure
has adequate space available for the writing of new The DB2 members that are actively connected to the
pages to the GBP. named group buffer pool participate in the rebuild.
DB2 accomplishes the group buffer pool rebuild
This message may be issued when either of the
processing in two phases:
following occurs:
1. Quiesce phase. Each member quiesces all local
v Rebuilding of GBP reduces changed page count to
access to the group buffer pool.
60% or less of GBP capacity.
2. Connect phase. Each member connects to the new
v ’changed data.’ entries decrease to 60% or lower
structure. Each page set or partition castout owner
when they were previously 75% GBP capacity or
that has connectivity to original structure is
higher.
responsible for writing pages from the original
System action: structure to the new one. If there are not enough
data entries in the new structure, the page set and
DB2 processing continues. partition owners cast those pages out to DASD
instead. Each member issues message DSNB332I
DSNB330I csect-name GROUP BUFFER POOL after it completes this activity. After all members
gbpname CANNOT BE CONNECTED have completed their castout owner rebuild work,
FOR REBUILD DB2 REASON CODE = the group buffer pool structure owner does the final
reason1 MVS IXLCONN REASON sweep and checks to see if there are any changed
CODE = reason2 pages still remaining in the original structure. If so,
the structure owner reads the changed pages from
Explanation: the original structure and writes them to the new
DB2 was not able to connect to the named group buffer one. The structure owner issues message DSNB333I
pool for rebuild. reason1 is the DB2 reason code. reason2 after it has completed the final sweep.
is the MVS IXLCONN reason code. See MVS/ESA
Programming: Sysplex Services Reference for an After all members have responded to MVS indicating
explanation of MVS IXLxxxx reason codes. that its connect phase processing is complete, MVS then
notifies each member that the rebuild is complete. Each
System action: DB2 member issues message DSNB338I indicating that
DB2 stops the rebuild. the rebuild has completed successfully.
Problem determination:
36 Messages
DSNB332I • DSNB335I
STRFAILOLD connected to the group buffer pool begin using the new
The original group buffer pool structure failed structure.
while the rebuild was in progress.
DB2REASON DSNB339I csect-name THE STOP OF THE
DB2 decided to stop the rebuild. The reason REBUILD FOR GROUP BUFFER POOL
code given in reason2 indicates why DB2 gbpname HAS COMPLETED
stopped the rebuild.
Explanation:
INSUFFCONN
The stop of the rebuild for the named group buffer
New structure does not provide connectivity
pool has completed.
that is better than or equivalent to the current
structure. This message is preceded by message DSNB335I which
indicates the reason why the rebuild was stopped. This
NOBETRCONN
message is issued by each DB2 member participating in
New structure does not provide better
the rebuild.
connectivity than the current structure for a
LossConn rebuild System action:
The new structure is discarded. If the original structure
If reason1 indicates ’DB2REASON’, then reason2
is still usable, then all members that still have
specifies a DB2 reason code that indicates why DB2
connectivity to the original structure resume using it,
stopped the rebuild. If reason1 is not ’DB2REASON’,
and members that do not have connectivity to the
then reason2 is zero.
original structure disconnect and their connection goes
into a failed-persistent state.
This message is normally preceded by message
DSNB331I, which indicates that the rebuild was started If the original structure is not usable, then DB2 initiates
and the reason why the rebuild was started. This damage assessment processing for the group buffer
message is issued by each DB2 member participating in pool.
the rebuild. This message is followed by message
DSNB339I.
DSNB340I csect-name UNEXPECTED ERROR
System action: DURING REBUILD FOR GROUP
BUFFER POOL gbpname MVS
The new structure is discarded. If the original structure
service-name RETURN CODE = rc MVS
is still usable, then all members that still have
service-name REASON CODE = reason
connectivity to the original structure resume using it.
Members that do not have connectivity to the original Explanation:
structure disconnect, and their connections become
DB2 received an unexpected error from MVS during
failed-persistent.
rebuild processing for the named group buffer pool.
If the original structure is not usable, then DB2 initiates
service-name is one of the following:
damage assessment processing for the group buffer
pool. v IXLREBLD
v IXLEERSP
System programmer response:
If the rebuild stopped because of “DB2REASON”, see rc is the return code from the MVS service and reason is
the explanation for the reason code given. the reason code.
System action:
DSNB338I csect-name THE REBUILD FOR GROUP
BUFFER POOL gbpname HAS DB2 stops the rebuild.
COMPLETED SUCCESSFULLY System programmer response:
Explanation: See MVS/ESA Programming: Sysplex Services Reference for
The rebuild for the named group buffer pool has an explanation of the return and reason code for the
successfully completed. named MVS service.
38 Messages
DSNB351I • DSNB354I
bpname
DSNB357I csect-name AUTOMATIC LPL
The buffer pool external name (BP0, BP1,...,
RECOVERY SUPPRESSED FOR
BP49, BP8KB, BP16KB BP32K, BP32K1,...,
OBJECT TYPE object-type OBJECT
BP32K9).
NAME object-name REASON reason-type
bpid The buffer pool internal identifier (0-49, 80-89).
Explanation:
ucount The number of open table spaces or index
One or more pages in the object that is identified in the
spaces that refer to this buffer pool. A zero use
message have been added to the logical page list (LPL).
count means that the buffer pool is inactive.
However, DB2 cannot initiate automatic LPL recovery
due to an environmental condition that prevents System action:
automatic LPL recovery.
Processing continues.
The object could be a table space, an index space, or a
partition within a table space or an index space that is
identified by the object-type. object-name identifies the DSNB402I BUFFER POOL SIZE = vpsize BUFFERS
name. AUTOSIZE = auto ALLOCATED = vpalc
TO BE DELETED = vptbd
If the object is a table space or an index space, the IN-USE/UPDATED = vpcba BUFFERS
format of the name is dbname.spacename. If the object is ACTIVE = vpact
a partition within a table space or an index space, the
format of the name is dbname.spacename.partnumber. Explanation:
dbname is the database name. spacename is the table This message, displayed by the DISPLAY BUFFER
space or the index space name. partnumber is the POOL command, describes the allocation status of a
partition number. buffer pool. This message is always preceded by
reason indicates the condition that prevents DB2 from message DSNB401I, which identifies the associated
being able to initiate automatic LPL recovery. Here is a buffer pool.
list of the potential values for reason: The following list defines the statistics that you can
DASD DB2 encountered a DASD I/O error. receive in this message:
40 Messages
DSNB404I • DSNB409I
42 Messages
DSNB420I • DSNB453I
ree Number of times prefetch was disabled (no This message is issued in response to the DISPLAY
asynchronous read processor available) BUFFERPOOL command with DETAIL specified. It lists
statistics about parallel activities. This message is
System action: always preceded by message DSNB401I identifying the
Processing continues. associated buffer pool.
The variables are:
DSNB420I SYS PAGE UPDATES = sws SYS PAGES tpa Total number of negotiations with the buffer
WRITTEN = pws ASYNC WRITE I/O = pool for getting the requested number of
wio SYNC WRITE I/O = imw PAGE-INS sequential prefetch streams
REQ = pir
dpa Total number of times the negotiation resulted
Explanation: in the degraded mode of parallel operations
This message is displayed by the DISPLAY
BUFFERPOOL command with the DETAIL option DSNB453I VP CACHED PAGES - CURRENT =
specified. It lists page write statistics for the buffer vcount MAX = mvcount CHANGED =
pool. This message is always preceded by message ccount MAX = mccount
DSNB401I identifying the associated buffer pool.
Explanation:
The statistics are:
This message might be displayed for an active buffer
sws Number of system page updates pool by the DISPLAY BUFFERPOOL command with
pws Number of system pages written LSTATS specified. It lists the number of cached pages
and the number of changed pages in the buffer pool for
wio Number of asynchronous write I/O operations a data set. The message is only issued if there are
imw Number of synchronous write I/O operations nonzero values to display. This message is always
preceded by message DSNB401I identifying the
pir Number of page-ins required for write I/O associated buffer pool, DSNB464I or DSNB465I
System action: identifying the table space or index space, and
DSNB466I identifying the data set.
Processing continues.
The statistics are:
DSNB421I DWT HIT= dwt VERTICAL DWT vcount Number of cached pages in VP for the data set
HIT=vdw NO WRITE ENGINE=wee (that is, the number of buffers that contain
pages for the data set in the buffer pool).
Explanation:
mvcount
This message is displayed by the DISPLAY Maximum number of cached pages in VP for
BUFFERPOOL command with the DETAIL option the data set since the last DISPLAY
specified. It lists page-write statistics for the buffer BUFFERPOOL command with the LSTATS
pool. This message is always preceded by message option was issued.
DSNB401I identifying the associated buffer pool.
ccount Number of changed pages in VP for the data
The statistics are: set (that is, the number of buffers that were
changed in the buffer pool for the data set).
dwt Number of times deferred write threshold was
hit mccount
Maximum number of changed pages in VP for
vdw Number of times vertical deferred write
the data set since the last DISPLAY
threshold was hit
BUFFERPOOL command with the LSTATS
wee Number of times write engine (asynchronous option was issued.
write processor) was not available for I/O
System action:
operations
Processing continues.
System action:
Processing continues.
44 Messages
DSNB461I • DSNB464I
that indicate the beginning of a multiple line display with the LSTATS option. It shows statistics for data
generated by a DISPLAY BUFFERPOOL command. The sets.
format of the multiple line display has three parts:
System action:
v Underlined column headings (DSNB464I).
Processing continues.
v Detailed space information for the spaces and
partitions that are requested by the command
(DSNB465I). DSNB467I STATISTICS FOR type dbname.spacenam
v An ending message (DSNB463I) that may be DATA SET #: dsn# USE COUNT:ucount
displayed if no spaces matched the command Explanation:
criteria.
This message might be displayed for an active buffer
The text of message DSNB465I provides the detail lines pool by the DISPLAY BUFFERPOOL command with
that follow the headings generated by this message. If the LSTATS option specified. It identifies the page
the DISPLAY BUFFERPOOL LIST command finds more set/partition type (table space/index space), database
than 255 lines of output to display, the report will be name, space name, number of claimers/drainers and
broken up and new headings (DSNB464I) will be the relative data set number within a table space or
displayed with ’(CONTINUED)’ showing in the index space for the statistics displayed in one or more
heading text. This is needed due to the MVS limitation of the messages that follow this one.
of 255 messages for multi-line WTO messages. type Whether the page set/partition is a table space
System action: (TABLE SPACE) or an index space (INDEX
SPACE).
Processing continues.
dbname Database name
46 Messages
DSNB499I • DSNB506I
48 Messages
DSNB519I • DSNB529I
DSNB519I csect-name PGSTEAL FOR bpname HAS DSNB522I VPSIZE FOR bpname HAS BEEN SET
BEEN SET TO value. TO integer
Explanation: Explanation:
This message is issued in response to an ALTER This message is issued in response to an ALTER
BUFFERPOOL command to indicate that the requested BUFFERPOOL command to indicate that the requested
change to the PGSTEAL parameter was accepted. change to the VPSIZE parameter was accepted. For an
active pool, the actual expansion, contraction, or
bpname is the name of the buffer pool.
deletion does not take place until after this message is
value is one of the following: issued.
LRU The buffer pool buffers are managed using the System action:
least recently used (LRU) algorithm. This is
Processing continues.
the default.
System programmer response:
FIFO The buffer pool buffers are managed using the
first in first out (FIFO) algorithm. Issue the DISPLAY BUFFERPOOL command to
determine the actual virtual storage usage for this pool.
System action:
Processing continues.
DSNB524I VPSEQT FOR bpname HAS BEEN SET
TO integer
DSNB520I READY TO EXPLICITLY DELETE
Explanation:
BUFFER POOL bpname
This message is issued in response to an ALTER
Explanation:
BUFFERPOOL command. It indicates the successful
This message is issued before draining an active buffer modification of the sequential steal threshold of the
pool in response to an ALTER BUFFERPOOL buffer pool.
command, which specified VPSIZE=0 against an active
buffer pool.
DSNB526I DWQT FOR bpname HAS BEEN SET TO
System action: integer
DSNB533I integer IS THE CURRENT VPXPSEQT DSNB538I csect-name THE TOTAL BUFFER POOL
FOR BUFFER POOL bpname STORAGE NO LONGER EXCEEDS
THE REAL STORAGE CAPACITY
Explanation:
Explanation:
An ALTER BUFFERPOOL command specified a
VPXPSEQT equal to the current assisting parallel This message is issued following a previous DSNB536I
sequential threshold of the buffer pool. message to indicate that the total amount of allocated
buffer pool storage for this DB2 subsystem no longer
System action: exceeds the real storage capacity of the z/OS image.
The assisting parallel sequential threshold of the buffer System action:
pool is not changed. Processing for other parameters, if
requested, proceeds normally. Processing continues.
DSNB534I VPXPSEQT FOR bpname MUST BE DSNB539I csect-name AUTOLPL FOR bpname HAS
BETWEEN 0 AND 100 BEEN SET TO value. IT WILL TAKE
EFFECT ON THE NEXT ALLOCATION
Explanation:
Explanation:
An ALTER BUFFERPOOL command was issued to
change a buffer pool’s VPXPSEQT attribute to an DB2 issues this message in response to an ALTER
invalid value. VPXPSEQT is the assisting parallel BUFFERPOOL command to ind that the requested
50 Messages
DSNB540I • DSNB542I
change to the AUTOLPL parameter was accepted. The DB2 detects that the total storage allocated for the
new AUTOLPL value takes effect the next time the PGFIX YES buffer pools will exceed 80% of the real
buffer pool is allocated. storage capacity on this z/OS image. The buffer pool
| name identified on this message (bpname) will be
bpname is the name of the buffer pool.
allocated with the PGFIX NO attribute. The real storage
value is one of the following: | capacity of this z/OS image (rsc) is displayed in this
message in units of megabytes (1 MB = 2**20 bytes).
YES DB2 automatically recovers pages that are in
LPL status. System action:
NO DB2 does not automatically recover pages in The buffer pool is created using the PGFIX NO
LPL status. To recover the LPL page, perform attribute.
one of the following actions:
System programmer response:
v Issue the START DATABASE command with
the SPACENAM option Either allocate more real storage to this z/OS image,
reduce the requested size of the buffer pool or use the
v Run the RECOVER or LOAD utility
PGFIX NO attribute.
System action:
Processing continues DSNB542I csect-name THE TOTAL ACTIVE PGFIX
YES BUFFER POOL STORAGE
EXCEEDS THE DB2 ALLOWED REAL
DSNB540I csect-name INSUFFICIENT LOCAL STORAGE CAPACITY WHEN
CACHE VECTOR STORAGE TO EXPANDING STORAGE FOR BUFFER
EXPAND BUFFER POOL bpname TO POOL bpname CURRENT VPSIZE =
SPECIFIED SIZE size1. BUFFER POOL cbpsize NEW VPSIZE = nbpsize REAL
SIZE IS NOW size2. STORAGE CAPACITY = rsc MB.
Explanation: Explanation:
The specified buffer pool could not be expanded to the When expanding the VPSIZE for an active PGFIX YES
requested size (size1). The associated group buffer pool buffer pool, DB2 detects that the total storage allocated
is connected, and the local cache vector could not be for all active PGFIX YES buffer pools will exceed 80%
expanded to cover the requested buffer pool size. of the real storage capacity on this z/OS image. The
The local cache vector is a bit array which tracks ALTER BUFFERPOOL command fails and the buffer
whether the page in a given buffer was modified by pool will continue to be active with the current VPSIZE
another system (cross-invalidated). There must be one value.
bit in the vector for each buffer in the buffer pool. For The buffer pool attributes and real storage capacity are:
more information on the local cache vector, see
MVS/ESA Programming: Sysplex Services Reference. bpname
The buffer pool name.
System action:
cbpsize
DB2 downgrades the expansion request to the size that The current VPSIZE for the buffer pool.
can be supported by the available local cache vector
storage (size2). nbpsize
The new VPSIZE that was specified on the
System programmer response: ALTER BUFFERPOOL command.
Free local cache vector storage by contracting or rsc The real storage capacity of this z/OS image
deleting other buffer pools that are connected to a in units of megabytes (1 MB = 2**20 bytes).
group buffer pool. Then reattempt the pool expansion
by reissuing the ALTER BUFFERPOOL command. System action:
The ALTER BUFFERPOOL command fails. The buffer
DSNB541I csect-name THE TOTAL ACTIVE PGFIX pool continues to be active with the current VPSIZE.
YES BUFFER POOL STORAGE
System programmer response:
EXCEEDS THE DB2 ALLOWED REAL
STORAGE CAPACITY WHEN Either allocate more real storage to this z/OS image,
ALLOCATING STORAGE FOR reduce the requested size of the buffer pool or use the
BUFFER POOL bpname REAL STORAGE PGFIX NO attribute.
CAPACITY = rsc MB.
Explanation:
When allocating storage for a PGFIX YES buffer pool,
52 Messages
DSNB601I • DSNB605I
Reason code 00C200E0 and the buffer pool external An attempt to create the buffer pool failed at the time
name are recorded in the cursor table (CT), which is that DB2 was performing its startup or restart
available in the SQL communication area (SQLCA) or processing. Insufficient virtual storage exists within the
messages. An SQLCODE -904 (resource not available) is ssnmDBM1 address space for building the buffer pool.
returned to the user. The name of the buffer pool is bpname.
Explanation: | Once the maximum has been reached, buffer pool sizes
| While activating a buffer pool during DB2 startup or
| are not allowed to be increased.
| restart processing, the buffer pool size was zero. A zero | System programmer response:
| value might be caused by an unusable bootstrap data
| set (BSDS) or by a DB2 abnormal termination after | Analyze the buffer pool sizes and determine if any can
| buffer pool size was altered to zero. The name of the | be decreased, or consider adding more memory.
| buffer pool is bpname.
System action: DSNB740I csect-name ATTEMPTING TO
ESTABLISH DUPLEXING FOR GROUP
DB2 creates the buffer pool using the startup restart BUFFER POOL gbpname REASON =
default value. reason
Operator response: Explanation:
Notify the system programmer. This message remains DB2 has been requested to establish duplexing for the
on the console until deleted by the operator. named group buffer pool. reason indicates the reason
why duplexing was initiated. reason can be one of the
System programmer response:
following:
Use the ALTER TABLESPACE or ALTER INDEX
OPERATOR
statement to modify the affected table spaces or indexes
The operator initiated a SETXCF command to
to indicate a usable buffer pool. To determine a usable
initiate duplexing.
buffer pool, use the DISPLAY BUFFERPOOL command.
If necessary, use the ALTER BUFFERPOOL command to POLICY
activate the failing buffer pool by setting the VPSIZE to The currently active CFRM policy indicated
a nonzero value. that duplexing should be automatically
established for the group buffer pool.
| DSNB610I csect-name MAXIMUM ALLOCATABLE
| BUFFER POOL STORAGE OF int1MB This message is issued by each DB2 member
| HAS BEEN REACHED. UNABLE TO participating in establishing duplexing.
| CREATE/EXPAND BUFFER POOL System action:
| bp-name TO SPECIFIED SIZE int2.
| BUFFER POOL IS NOW int3 The DB2 members that are actively connected to the
named group buffer pool participate in establishing
| Explanation: duplexing for the group buffer pool. Access to the
| A buffer pool could not be created or expanded to the
54 Messages
DSNB741I • DSNB744I
The process to establish duplexing for the named group System action:
buffer pool has successfully completed.
The secondary group buffer pool structure is discarded,
This message is preceded by message DSNB740I which and DB2 enters back into simplex mode on the primary
indicates the reason why duplexing was initiated. This group buffer pool structure. If DUPLEX(AUTO) is
message is issued by each DB2 member participating in specified in the active CFRM policy for the group
establishing duplexing. buffer pool, then duplexing will be automatically
reinitiated, if duplexing is still possible.
System action:
System programmer response:
Processing of mainline requests is resumed for the
group buffer pool. Writes of changed pages to the If the rebuild stopped because of “DB2REASON”, see
group buffer pool will be duplexed writes from this the explanation for the reason code given. If duplexing
point forward. is not automatically reinitiated and duplexing is desired
for the group buffer pool, then use the MVS SETXCF
command to reestablish duplexing.
DSNB743I csect-name DUPLEXING IS BEING
STOPPED FOR GROUP BUFFER POOL
gbpname FALLING BACK TO PRIMARY DSNB744I csect-name DUPLEXING IS BEING
REASON = reason1 DB2 REASON STOPPED FOR GROUP BUFFER POOL
CODE = reason2 gbpname, SWITCHING TO
SECONDARY REASON = reason1 DB2
Explanation: REASON CODE = reason2
Duplexing is being stopped for the named group buffer Explanation:
pool. To stop the duplexing, the secondary group buffer
pool will be deallocated, and DB2 will go back to Duplexing is being stopped for the named group buffer
simplex mode on the primary group buffer pool. pool. To stop the duplexing, the primary group buffer
pool will be deallocated, and DB2 will switch to the the
reason1 indicates why duplexing was stopped: secondary group buffer pool to go back to simplex
OPERATOR mode.
The operator initiated an MVS command to reason1 indicates why duplexing was stopped:
stop duplexing.
OPERATOR
POLICY The operator initiated an MVS command to
A new CFRM policy has been activated which stop duplexing.
specifies DUPLEX(DISABLED) for the group
buffer pool.
56 Messages
DSNB751I • DSNB756I
usage. Note that all message numbers in the range retcode Return code from IRLM on the Notify request
might not be used. Message DSNB790I ends the
reason Reason code from IRLM on the Notify request
display.
For an explanation of IRLM return and reason codes,
DSNB751I MVS CFRM POLICY INFORMATION see Codes .
NOT AVAILABLE FOR GROUP
BUFFER POOL gbpname MVS System action:
IXCQUERY RETURN CODE = retcode Processing continues.
MVS IXCQUERY REASON CODE =
reason A PARTIAL DISPLAY FOLLOWS
DSNB755I DB2 GROUP BUFFER POOL STATUS
Explanation: CONNECTED = status1 CURRENT
DB2 could not retrieve group buffer pool policy DIRECTORY TO DATA RATIO = ratio1
information in response to a DISPLAY PENDING DIRECTORY TO DATA
GROUPBUFFERPOOL command. Either the MVS RATIO = ratio2 CURRENT GBPCACHE
query request (IXCQUERY) did not successfully ATTRIBUTE = gcache1 PENDING
complete, or the backing structure for the group buffer GBPCACHE ATTRIBUTE = gcache2
pool is not defined in the MVS CFRM administrative Explanation:
policy. To determine the exact reason, examine return
code retcode and reason code reason returned by MVS In response to a DISPLAY GROUPBUFFERPOOL
on the query request. For an explanation of the command, this is the first of two messages displaying
IXCQUERY codes, see MVS/ESA Programming: Sysplex information about the status of the group buffer pool as
Services Reference. If the IXCQUERY request did not it is known to DB2. This message is followed by
complete successfully, no CONNLIST information, even DSNB756I. A preceding DSNB750I or DSNB751I
if requested, is provided. message identifies the associated group buffer pool.
DSNB752I GROUP DETAIL STATISTICS ARE NO This DB2 is not actively connected to
NOT AVAILABLE FOR THE GROUP the group buffer pool.
BUFFER POOL BECAUSE A REBUILD | ratio1 The ratio of directory entries to data pages, as
IS IN PROGRESS | specified for the current allocation of this
Explanation: | group buffer pool.
Because a rebuild is in progress for the group buffer ratio2 The desired ratio of directory entries to data
pool, DB2 cannot retrieve group buffer pool group pages to take effect at the next reallocation of
(GDETAIL) statistics in response to a DISPLAY the group buffer pool.
GROUPBUFFERPOOL command. A preceding gcache1 The GBPCACHE attribute as specified for the
DSNB750I or DSNB751I message identifies the current allocation of this group buffer pool.
associated group buffer pool.
gcache2 The value for GBPCACHE attribute that will
System action: take effect at the next reallocation of the group
Processing continues. buffer pool.
MVS CFRM policy information for the group buffer message DSNB756I, and if the structure is allocated,
pool, messages DSNB757I through DSNB759I followed by messages DSNB758I and DSNB759I. A
immediately follow this message. A preceding preceding DSNB750I message identifies the associated
DSNB750I or DSNB751I message identifies the group buffer pool.
associated group buffer pool.
structure-name
threshold1 The coupling facility structure name for this
The threshold at which class castouts are to be group buffer pool, such as DSNCAT_GBP0.
initiated. It is expressed as a percentage of the
status2 MVS global status of the backing coupling
group buffer pool size.
facility structure:
threshold2
NORMAL
The threshold at which castout is to be
Structure is defined in the current
initiated at the group buffer pool level. It is
CFRM policy and has no current MVS
expressed as a percentage of the group buffer
restrictions.
pool size.
CHNGP
interval The time, in minutes, between successive
Change pending in the structure
initiations of group buffer pool checkpoint.
policy.
status1 The recovery status for the group buffer pool:
dupstat The duplexing attribute for the coupling
DAP Damage assessment pending. DB2 is facility structure, as indicated by the DUPLEX
in the process of doing damage parameter in the CFRM policy definition.
assessment for the group buffer pool
DISABLED
in response to a coupling facility
DUPLEX(DISABLED) is specified for
structure failure. The group buffer
the coupling facility structure. The
pool is temporarily stopped internally
DUPLEX parameter is not specified.
by DB2 and is unavailable for use
until the damage assessment process ENABLED
completes. DUPLEX(ENABLED) is specified for
the coupling facility structure.
NORMAL
There is no pending recovery action ALLOWED
for this group buffer pool. DUPLEX(ALLOWED) is specified for
the coupling facility structure.
auto-rec-parm
Automatic recovery parameter specification: dupmode
Indication of current status of the group buffer
YES DB2 should automatically initiate
pool in relation to duplexing.
recovery for the objects using this
group buffer pool following a failure SIMPLEX
of the group buffer pool. This is the Group buffer pool is currently in
default. simplex mode.
NO DB2 should not initiate automatic DUPLEX
group buffer pool recovery. If the Group buffer pool is currently in
group buffer pool fails, you must duplex mode.
manually issue DB2 -START
DATABASE commands to do the INTRAN
recovery. Group buffer pool is currently in a
transition state. Either from simplex
mode to duplex mode, or from
DSNB757I MVS CFRM POLICY STATUS FOR duplex mode to simplex mode. The
structure-name = status2 MAX SIZE rebuild status indicator in message
INDICATED IN POLICY = psize KB DSNB758I gives information about
DUPLEX INDICATOR IN POLICY = the transition state.
dupstat CURRENT DUPLEXING MODE
= dupmode ALLOCATED = status1 psize The size (in kilobytes) of the coupling facility
structure as indicated in the CFRM policy
Explanation: definition.
For a DISPLAY GROUPBUFFERPOOL command, this status1 Whether the backing coupling facility structure
message gives the status for the structure associated is currently allocated:
with the group buffer pool. It is displayed only if DB2
was successful in querying the MVS CFRM YES The coupling facility structure is
administrative policy. It is immediately preceded by allocated in a coupling facility.
58 Messages
DSNB758I • DSNB759I
60 Messages
DSNB765I • DSNB771I
62 Messages
DSNB778I • DSNB784I
w5 Coupling facility write requests that were not GROUPBUFFERPOOL command because the statistics
completed because of a lack of storage in the request (IXLCACHE macro) did not successfully
group buffer pool. complete. A preceding DSNB750I or DSNB751I message
identifies the associated group buffer pool.
DSNB778I CASTOUT THRESHOLDS DETECTED retcode Return code from MVS on the statistics request
FOR CLASSES = t1 FOR GROUP
reason Reason code from MVS on the statistics
BUFFER POOL = t2 GBP
request
CHECKPOINTS TRIGGERED = k1
PARTICIPATION IN REBUILD = k2
For an explanation of IXLCACHE return and reason
Explanation: codes, see MVS/ESA Programming: Sysplex Services
Reference.
This is the seventh of eight messages containing local
statistics, displayed as a result of the DISPLAY System action:
GROUPBUFFERPOOL command with the MDETAIL
option. It lists local castout threshold statistics for the Processing continues.
group buffer pool and also group buffer pool
checkpoint and rebuild statistics. A preceding DSNB782I INCREMENTAL GROUP DETAIL
DSNB750I or DSNB751I message identifies the STATISTICS SINCE basetime
associated group buffer pool.
Explanation:
Counters:
This message is displayed by the DISPLAY
t1 Number of times the class castout threshold GROUPBUFFERPOOL command with
was detected GDETAIL(INTERVAL) specified. It indicates the start
t2 Number of times the group buffer pool castout time of the interval for which the statistics were
threshold was detected accumulated. This is the time of the previous GDETAIL
incremental display from this DB2 or the time the
k1 Number of group buffer pool checkpoints that group buffer pool was allocated or reallocated, if there
were triggered. was no previous GDETAIL incremental display.
k2 Number of times that this member System action:
participated in a rebuild of the group buffer
pool structure. Processing continues.
DSNB781I GROUP DETAIL STATISTICS ARE This is the first of five messages containing group
NOT AVAILABLE FOR THE GROUP statistics, displayed as a result of the DISPLAY
BUFFER POOL. MVS IXLCACHE GROUPBUFFERPOOL command with the GDETAIL
RETURN CODE = retcode MVS option. It lists the successful reads for the group buffer
IXLCACHE REASON CODE = reason pool. A preceding DSNB750Ior DSNB751I message
identifies the associated group buffer pool. This
Explanation: message is always followed by messages DSNB785I
DB2 could not retrieve group buffer pool group through DSNB788I.
(GDETAIL) statistics in response to a DISPLAY
r1 ″Read hit″ counter. Number of times that a group buffer pool and the total number of changed
page was returned on a coupling facility read pages forthe group buffer pool. The associated group
request. buffer pool is identified in apreceding DSNB750I or
DSNB751I message. This message is always preceded
For information about the Group Detail Report, see . bymessages DSNB784I and DSNB785I.
w1 ″Changed page write hit″ counter. Number of
DSNB785I DATA NOT RETURNED DIRECTORY changed pages that were successfullywritten.
ENTRY EXISTED = r2
w2 ″Clean page write hit″ counter. Number of
DIRECTORYENTRY CREATED = r3
clean pages thatwere successfully written.
DIRECTORY ENTRY NOT CREATED =
r4, r5 w3 ″Write miss cache full″ counter. Number of
times a coupling facility writerequest was not
Explanation:
completed because of a
This is the second of five messages containing group
lack of storage in the group bufferpool.
statistics, displayed as a result of the DISPLAY
GROUPBUFFERPOOL command with the GDETAIL p1 ″Total changed″ counter. Snapshot value of the
option. It continues the read statistics for the group current number of changedpages. The
buffer pool. The associated group buffer pool is displayed value of this counter is not affected
identified in a preceding DSNB750I or DSNB751I by whether thisis an incremental or
message. This message is always preceded by message cumulative display.
DSNB784I and followed by messages DSNB786I
through DSNB788I. For information about the Group Detail Report, see .
All the ″read counters″ in this message represent cases
where data was not returned on the coupling facility DSNB787I RECLAIMS FOR DIRECTORY
read request. ENTRIES = d1 FOR DATA ENTRIES =
d2 CASTOUTS= c1
r2 ″Read miss directory hit″ counter. Number of
times that a coupling facility read request Explanation:
specified a page for which a directory entry
exists, but no datawas cached for that page. This is the fourth of five messages containing group
statistics, displayed as a result of the DISPLAY
r3 ″Read miss name assigned″ counter. Number GROUPBUFFERPOOL command with the GDETAIL
of times that a coupling facility read request option. It is always preceded by messages DSNB784I
specified a page for which a directory entry through DSNB786I and followed by message
was created. DSNB788I. It lists the statistics on reclaims and castouts
for the group buffer pool. The associated group buffer
r4 ″Read miss assignment suppressed″ counter.
pool is identified in a preceding DSNB750I or
Number of times that a coupling facility read
DSNB751I message.
request specified a page for which no directory
entry exists and no directory entry is created. | d1 ″Directory entry reclaim″ counter. Number of
times a name assignment required that a
r5 ″Read miss cache full″ counter. Number of
directory entry be reclaimed by the coupling
times that a coupling facility read request
facility.
specified a page for which no directory entry
exists and no directory entry is created d2 ″Data entry reclaim″ counter. Number of times
because of a lack of storage in the group a name assignment required that a data page
buffer pool. be reclaimed by the coupling facility.
| c1 ″Castout″ counter. Number of pages for which
For information about the Group Detail Report, see .
| castout occurred.
DSNB786I WRITES CHANGED PAGES= w1 For information about the Group Detail Report, see .
CLEAN PAGES = w2 FAILEDDUE TO
LACK OF STORAGE = w3 CHANGED
PAGES SNAPSHOT VALUE= p1 DSNB788I CROSS INVALIDATIONS DUE TO
DIRECTORY RECLAIMS = x1 DUE TO
Explanation: WRITES = x2 EXPLICIT = x3
This is the third of five messages containing group Explanation:
statistics,displayed as a result of the DISPLAY
GROUPBUFFERPOOL command with the This is the last of five messages containing group
GDETAILoption. It is followed by messages DSNB787I statistics, displayed as a result of the DISPLAY
and DSNB788I. It lists the statisticson writes to the GROUPBUFFERPOOL command with the GDETAIL
64 Messages
DSNB789I • DSNB793I
r7 The number of requests to the coupling facility The display is terminated for this group buffer pool.
to register interest in a list of pages. DB2 does Command processing continues, if there are other
this when prefetch (sequential or list) is used group buffer pool names to process.
when the following conditions are met:
v The DB2 member is running on a particular DSNB793I DELETE NAME LIST = s5 READ
service level of MVS 5.2 or above CASTOUT STATISTICS = s6 DELETE
v The GBP is allocated in a coupling facility NAME = s7 OTHER ASYNCHRONOUS
with CFLEVEL=2 or above. GBP REQUESTS = s8
secondary group buffer pool. The DB2 TYPE(GCONN) option and an asterisk (*) specified as
member that is the group buffer pool structure the selection list. When DB2 successfully determines
owner periodically issues these requests to (that is, no error is encountered during command
determine whether garbage collection is processing) that there are no group buffer pools
necessary to clean up orphaned data entries connected to any DB2 in the data sharing group.
from the secondary. Orphaned data entries are
System action:
″changed″ data entries in the secondary group
buffer pool without a corresponding Command processing is terminated.
″changed″ data entry in the primary.
Orphaned data entries are to be expected from
time to time and do not represent any kind of DSNB796I CASTOUTS PAGES CASTOUT = c1
data inconsistency problem (because the page UNLOCK CASTOUT = c2 READ
has already been cast out from the primary CASTOUT CLASS = c3 READ
and such that the version of the page in the CASTOUT STATISTICS = c4 READ
secondary is the same as the version of the DIRECTORY INFO = c5
page on DASD). Orphaned data entries can be Explanation:
introduced by certain transaction or system
failures, or by new group buffer pool write This is the eighth of ten messages containing local
activity that encounters very unlikely timing statistics, displayed as a result of the DISPLAY
windows when castout is concurrently GROUPBUFFERPOOL command with the MDETAIL
processing. option. It lists local castout statistics for the group
buffer pool. A preceding DSNB750I or DSNB751I
s7 The number of Delete Name requests to delete message identifies the associated group buffer pool.
″orphaned data entries″ from the secondary
group buffer pool. The DB2 member that is the Counters:
group buffer pool structure owner issues these c1 Number of pages cast out.
requests if it determines that garbage
collection is necessary. See the description c2 Number of requests to unlock for castout.
above under s6 for a description of ″orphaned c3 Number of read castout class requests.
data entries″.
c4 Number of read castout statistics requests.
s8 The number of asynchronous CF requests sent
to the secondary group buffer pool. This c5 Number of read directory info requests. These
excludes ASYNCHRONOUS COMPLETION requests are made during group buffer pool
CHECKS as reported on the DSNB764I checkpoint.
message.
DSNB797I OTHER INTERACTIONS REGISTER
For information about the Group Detail Report, see . PAGE = o1 UNREGISTER PAGE = o2
DELETE NAME = o3 READ STORAGE
DSNB794I THIS DB2 IS NOT CONNECTED TO STATISTICS = o4 EXPLICIT CROSS
ANY GROUP BUFFER POOL INVALIDATIONS = o5
ASYNCHRONOUS GBP REQUESTS =
Explanation: o6
This message is issued in response to a DISPLAY Explanation:
GROUPBUFFERPOOL command with the
TYPE(MCONN) option and an asterisk (*) specified as This is the last of ten messages containing local
the selection list. This message is issued when DB2 statistics, displayed as a result of the DISPLAY
determines that there are no group buffer pools having GROUPBUFFERPOOL command with the MDETAIL
″member connectivity″ from the DB2 on which the option. It lists local castout statistics for the group
DISPLAY GROUPBUFFERPOOL command was issued. buffer pool. A preceding DSNB750I or DSNB751I
message identifies the associated group buffer pool.
System action:
Counters:
Command processing is terminated.
o1 Number of requests to the coupling facility to
register interest in a single page.
DSNB795I NO DB2 IN THE GROUP IS
CONNECTED TO ANY GROUP o2 Number of requests to the coupling facility to
BUFFER POOL remove the registered interest in a single page.
66 Messages
DSNB798I • DSNB799I
o4 Number of requests to the coupling facility to detailed monitoring of the group buffer pool
read the statistics counters associated with the checkpoint processing with IFCID 0261.
structure. DB2 generally issues this request
member-name2
once per group buffer pool checkpoint, and
The member name of the group buffer pool
once per GDETAIL request on the DB2
structure owner. The structure owner’s
DISPLAY GROUPBUFFERPOOL command.
responsibilities include the following:
o5 Number of explicit cross-invalidations for v Issue the group buffer pool checkpoint.
pages in the group buffer pool.
v Detect the GBPOOLT castout threshold and
o6 Number of coupling facility requests to the initiate castout if this threshold has been
primary group buffer pool that were converted reached (by notifying the pageset or
from synchronous to asynchronous. partition castout owners).
v Coordinate the damage assessment process
DSNB798I LAST GROUP BUFFER POOL in case the group buffer pool fails.
CHECKPOINTtimestamp MINIMUM v Coordinate the rebuild process for the group
CLEAN-TO-DIRTY LRSN = lrsn1 buffer pool.
MINIMUM MEMBER RESTART/REDO
LRSN = lrsn2, member-name1 ’UNKNOWN’ is displayed if DB2 is not able
STRUCTURE OWNER = member-name2 to determine which member is the structure
owner for the group buffer pool. This should
Explanation:
only happen in an unexpected error situation.
This message is displayed in response to the DISPLAY See the message accompanying that error.
GROUPBUFFERPOOL command. It is issued only if
System action:
DB2 determines, by successfully querying the MVS
CFRM policy, that the group buffer pool is allocated. It Processing continues.
is immediately preceded by message DSNB759I. A
preceding DSNB750I message identifies the associated
group buffer pool. DSNB799I SECONDARY GBP ATTRIBUTES
ALLOCATED SIZE = ssize KB
timestamp VOLATILITY STATUS = svolstat
The date and time of the last group buffer CFNAME = cfname CFLEVEL -
pool checkpoint. OPERATIONAL = cflevel1 CFLEVEL -
ACTUAL = cflevel2 NUMBER OF
lrsn1 The recovery log record sequence number
DIRECTORY ENTRIES = sdir#
(LRSN) that was recorded by the last group
NUMBER OF DATA PAGES = sdata#
buffer pool checkpoint that reflects the oldest
changed page clean-to-dirty LRSN value at the Explanation:
time of the checkpoint. If the group buffer
pool were to fail, lrsn1 is used by DB2 as input For a DISPLAY GROUPBUFFERPOOL command, this
to determine the starting points for the merged message gives the attributes of the secondary group
log scan to recover the page sets and partitions buffer pool if the group buffer pool is duplexed. It is
that are entered into group buffer pool displayed only if the group buffer pool is duplexed and
recovery pending (GRECP) status. You can do if DB2 was successful in querying the MVS CFRM
more detailed monitoring of the group buffer administrative policy. This message is not displayed if
pool checkpoint processing with IFCID 0261. the group buffer pool is in a transition state between
simplexing and duplexing.
lrsn2 The minimum member-level write-pending
(restart/redo) LRSN that was recorded by the ssize The actual allocated size (in kilobytes) of the
last group buffer pool checkpoint. secondary group buffer pool coupling facility
member-name1 is the DB2 member associated structure.
with the minimum restart/redo LRSN. Group svolstat The volatility status of the secondary group
buffer pool checkpoint records a restart/redo buffer pool:
LRSN for each member - lrsn2 reflects only the
single minimum value across all members. If VOLATILE
the group buffer pool were to fail, DB2 uses The structure is volatile.
each member’s restart/redo LRSN in NON-VOLATILE
conjunction with lrsn1 to determine the The structure is non-volatile.
starting points for the merged log scan to
recover the page sets and partitions that are | cfname The name of the coupling facility in which the
entered into group buffer pool recovery | group buffer pool is allocated. If the group
pending (GRECP) status. You can do more
68 Messages
DSNB803I • DSNB809I
System programmer response: any parameters was issued for an existing group buffer
pool. If an ALTER GROUPBUFFERPOOL command
Reissue the -ALTER GROUPBUFFERPOOL command,
without any parameters is issued for a group buffer
specifying an acceptable value for GBPCHKPT.
pool that does not yet exist, a group buffer pool
definition with default parameters values is created.
DSNB812I SIZE ESTIMATES ARE NOT
System action:
AVAILABLE FOR THE GROUP BUFFER
POOL MVS IXCQUERY RETURN The command is successful and processing continues.
CODE = return code MVS IXCQUERY
REASON CODE = reason code
| DSNB815I PAGE P-LOCK LOCK/UNLOCK,
Explanation: | P-LOCK REQUESTS FOR SPACE MAP
| PAGES = nn P-LOCK REQUESTS FOR
The directory entries and data pages estimates for the
| DATA PAGES = nn P-LOCK REQUESTS
group buffer pool, identified on the preceding
| FOR INDEX LEAF PAGES = nn P-LOCK
DSNB800I message, could not be computed because
| UNLOCK REQUESTS = nn
IXCQUERY was unable to obtain the backing
structure’s size information from the MVS CFRM | Explanation:
administrative policy definition. This can happen if an
IXCQUERY processing error occurred, or if the
| This message is issued in response to a DISPLAY
structure was not defined in the CFRM policy. The
| GROUPBUFFERPOOL command. This message reports
backing structure for the group buffer pool must be
| the physical lock (P-lock) status at the Group Buffer
defined in the CFRM policy before the group buffer
| Pool level. The accounting of these P-locks is intended
pool can be allocated. The exact reason can be
| for use in monitoring and tuning database
determined from the return code and the reason code. For
| performance, especially in a data-sharing environment.
an explanation of the IXCQUERY codes, see MVS/ESA
| For more information about the DISPLAY
Programming: Sysplex Services Reference.
| GROUPBUFFERPOOL command, please see the DB2
| Command Reference.
System action:
| System action:
The command completes successfully, but without
giving the estimates.
| Processing Continues.
70 Messages
DSNB890I • DSNB892I
In the TSO attachment facility, the user can control whether message IDs are
displayed. To see them, type PROFILE MSGID. To suppress them, type PROFILE
NOMSGID.
Trace messages associated with the TSO attachment facility (including DSN and
DB2I) are not listed in this documentation. If you suspect an error in DB2, refer to
Part 2 of Diagnosis Guide and Reference for information on identifying and reporting
the problem.
All DSN command processor trace messages have the same message number:
DSNET20I.
74 Messages
DSNE103E • DSNE109E
User response:
DSNE103E MAIN STORAGE REQUEST FROM
csect-id FAILED Notify the system programmer or system administrator
to obtain proper authorization.
Explanation:
A request for main storage failed.
DSNE107E SUBSYSTEM RESOURCE NEEDED
System action: FOR PLAN plan-name, AUTH ID
auth-id, AND SUBSYSTEM subsys IS
The TSO attachment facility is ready for more input.
NOT AVAILABLE
User response:
Explanation:
Increase the address space size. This can be done as
The DB2 subsystem was unable to allocate a necessary
part of the logging on process.
resource for the requested combination of plan-id,
user-id, and subsystem-id. This message is
DSNE104E RETRY COUNT OF number NOT accompanied by DSNE108E. An attempt to establish
VALID, SET TO 120 connection with the DB2 subsystem has failed.
An invalid ’RETRY’ parameter was entered on the DSN The TSO attachment facility is ready for more input.
command. It has been set to 120. Valid retry counts are
User response:
integer numbers from 0 to 120.
Arrange to obtain the needed resource, and resubmit
System action:
the subcommand. See the explanation for message
Retry count is modified, and DSN execution continues. DSNE108E, which accompanies this message.
User response:
DSNE108E FEEDBACK - REASON CODE
The next time you invoke DSN, use a RETRY count of reason-code TYPE= type RESOURCE
0 to 120. NAME - 44 characters
Explanation:
DSNE105E SUBSYSTEM ssid NO LONGER
OPERATIONAL This message accompanies message DSNE107E or
DSNE114E to explain the problem more clearly.
Explanation: RESOURCE NAME is the name of the unavailable
The DB2 subsystem is down. It must be restarted resource. The reason code is in hexadecimal format.
before the user can continue. System action:
System action: The TSO attachment facility is ready for more input.
Control returns to TSO attachment facility. User response:
User response: Arrange for the missing resource to be available, and
Before you can continue, DB2 must be restarted. You resubmit your job.
must also reissue the DSN command. ISPF users Problem determination:
should restart their jobs.
The reason the resource is unavailable is identified by a
reason code. The value and semantics of the code are
DSNE106E PLAN plan-id NOT AUTHORIZED the same as the SQL return codes documented in Codes.
FOR SUBSYSTEM ssid AND AUTH-ID
auth-id TYPE and RESOURCE NAME identify the resource
that is currently unavailable. The TYPE code identifies
Explanation: the type, as well as the format and content, of the
The requested combination of plan-id, subsystem-id, RESOURCE NAME. Refer to Appendix C, “Resource
and user-id is not currently authorized. types,” on page 807 for a table showing all types and
names.
System action:
The TSO attachment facility is ready for more input. DSNE109E NO INPUT TO BIND, SUBCOMMAND
System programmer response: TERMINATED
System action:
DSNE113E NOT ABLE TO LINK TO MODULE
The TSO attachment facility is ready for more input. modname IN DSNAME data-set-name
Specify the LIBRARY parameter, and resubmit the A DB2 subsystem error occurred during an attempt to
BIND subcommand. Alternatively, you could issue an link to module ’modname’ in data set ’data-set-name’.
ALLOCATE command for the DDNAME DBRMLIB
System action:
and then resubmit the BIND subcommand as originally
written. The TSO attachment facility is ready for more input.
User response:
DSNE110E ssid NOT VALID SUBSYSTEM ID,
Check that the module exists and that its name is
COMMAND TERMINATED
spelled correctly. Enter the correct module name.
Explanation:
There is no subsystem id with the name identified in DSNE114E THE COMBINATION OF PLAN planid,
the message as ’ssid’. The subsystem identifier you AUTH ID auth-id, AND SUBSYSTEM
specify (or default to) on the DSN command must ssid IS NOT VALID
exist. This message is the result of specifying (or
Explanation:
defaulting to) a nonexistent subsystem identifier. For
information on the SYSTEM parameter of the DSN The resource in message DSNE108E, which will follow
command, refer to Command Reference.. this message, is not a valid resource name.
System action: System action:
The DSN processor ends, and control returns to TSO. The TSO attachment facility is ready for more input.
User response: User response:
Reissue the command with a valid SYSTEM parameter. Correct the invalid combination, and resubmit the
subcommand. The problem is probably caused by a
user spelling error. If it is not, check with the system
DSNE111E INSTALLATION EXIT REJECTED
administrator to determine the availability of the
DSNAME data-set-name
needed resource. Your program may need to be bound.
Explanation: See the explanation for message DSNE108 (which
accompanies this one) for more information.
A local installation-supplied exit has rejected the data
set name identified in the message as ’data-set-name’.
DSNE117E NOT ABLE TO LOCATE membername
System action:
IN DSNAME data-set-name
The TSO attachment facility is ready for more input.
Explanation:
User response:
The ’data-set-name’ specified does not contain the
Either correct the data set name specified, or arrange to member the user wanted to run.
authorize the original data set name. Resubmit the
System action:
request.
Control remains with the DSN command processor,
and the DSN prompt appears on the terminal. The
DSNE112E userid STILL SIGNED ON TO
DSN command processor is ready for another
SUBSYSTEM ssid
command.
Explanation:
User response:
An attempt was made to sign on to DB2 when the user
Correct the PROGRAM or LIBRARY parameter, and
was already signed on.
resubmit the subcommand.
System action:
Control returns to TSO. DSNE118E invalid-command NOT VALID
COMMAND
User response:
Explanation:
Log off and log on again.
The user entered an invalid command. A typing error
may be responsible. You may be trying to run a
command processor that is either not available on your
76 Messages
DSNE119E • DSNE125E
User response: The DB2 subsystem was unable to open data set
’data-set-name’, because it is not a sequential or
Either correct the spelling error, or rearrange your partitioned data set.
library concatenation so that you can access the
required command processor. Resubmit the command. System action:
The TSO attachment facility is ready for more input.
DSNE119E data-set-name NOT PARTITIONED
User response:
DATA SET
Correct the data-set-name, or change the data set
Explanation:
organization. Resubmit the job.
The user tried to allocate a sequential data set when a
partitioned data set was required.
DSNE123I data-set-name NOT PARTITIONED
System action: DATA SET, IT IS IGNORED
Check the data-set-name. The data set you specified is System action:
partitioned, but you did not specify a member name.
The TSO attachment facility is ready for more input.
Add a member name, and resubmit the job.
User response:
DSNE121E csect-id NOT ABLE TO OPEN DATA Wait until the member is available and reissue your
SET DCLGEN request.
Explanation:
DSNE125E DATA SET data-set-name IN USE, TRY
The DB2 subsystem was unable to open the requested
LATER
data set.
Explanation:
System action:
The sequential data set ’data-set-name’ is currently in
The TSO attachment facility is ready for more input.
use. This message is normally issued when another
User response: user is updating the specified data set.
For information about why the data set could not be System action:
opened, read the explanations of the messages that
The TSO attachment facility is ready for more input.
accompany this message. Correct the condition, and
resubmit the job. User response:
Wait until the data set is available and reissue your
DCLGEN request.
System action:
DSNE131I MAXIMUM NUMBER OF DB2 USERS
No new users will be permitted to initiate DB2 REACHED. WILL RETRY nnn MORE
sessions. Current users will be permitted to work until TIMES
they terminate their connections to DB2.
Explanation:
User response:
The number of concurrent connections to DB2 is
End your DSN session as soon as possible. restricted. The number is specified in the installation
parameters in member DSN6SYSP. For TSO foreground,
see parameter IDFORE. For background jobs, see
DSNE127I THE DB2 OPERATOR IS STOPPING
parameter IDBACK. The DSN request was denied
THE SUBSYSTEM. DSN IS
because the current number of DB2 connections in the
TERMINATING
system reached the installation specified limit.
Explanation:
The DSN connection to DB2 is attempted ’nnn’ more
The operator has requested that DB2 terminate. times. The number of retries is determined by the
RETRY parameter on the DSN command. For more
System action:
information, refer to Command Reference..
DB2 will shut down, interrupting user activities as
This message is issued every 30 seconds (and each time
necessary. DSN will terminate immediately and return
’nnn’ is decreased by 1) until the connection is made or
the user to TSO.
until ’nnn’ is decreased to zero.
User response:
System action:
Reinitiate your session when DB2 returns.
DSN repeats the connection attempt until the
connection is made or the retry count is decreased to 0.
DSNE128I DB2 IS ABNORMALLY ENDING. DSN
User response:
IS TERMINATING
If all retry attempts fail, resubmit the DSN command
Explanation:
when DB2 activity diminishes. If still unsuccessful, see
DB2 has encountered a problem from which it cannot the system programmer about the installation
recover. parameters.
System action:
DSNE132I DB2 IS OPERATING IN RESTRICTED
DB2 is abending. DSN terminates immediately and ACCESS MODE. MAINTENANCE
returns the user to TSO. PERSONNEL ONLY
User response: Explanation:
Reinitiate your session when DB2 returns. DB2 is not available for normal operation. It is only
available to service personnel.
DSNE130I MAXIMUM NUMBER OF DB2 USERS System action:
REACHED. YOUR RETRY COUNT IS
ZERO Control returns to the caller. Your request was not
processed. The DSN command processor was unable to
Explanation: connect to DB2.
The number of concurrent connections to DB2 is User response:
restricted. The number is specified in the installation
parameters in member DSN6SYSP. For TSO foreground, Wait until DB2 is available for general use, then
see parameter IDFORE. For background jobs, see resubmit your request.
parameter IDBACK. The DSN request has been denied,
because the current number of DB2 connections in the
78 Messages
DSNE133E • DSNE232A
Check that your method of invoking DSN or DB2I The user has attempted to use the FREE PLAN or
allocates the correct libraries for DSN. If you used JCL PACKAGE panel without specifying a plan or package
or a TSO logon procedure to execute DSN code, check name.
your JOBLIB and STEPLIB allocations. If you used a System action:
CLIST to execute DSN, insure that you obtained the
correct version of the DSN code.See your system The TSO attachment facility is ready for more input.
programmer if you invoke DSN using procedures
User response:
supplied by your system programmer.
Enter the name of a plan or package, or (*) to indicate
Problem determination:
’all’.
Insure that coexistence is supported on both release
levels (DSN and DB2). If coexistence is supported,
DSNE232A CONNECTION NAME REQUIRES
insure that the lower level release has the correct SPE
ENABLE/DISABLE OF CONNECTION
level code support that is required to coexist with the
TYPE
current higher level release.
Explanation:
For more information about coexistence and SPEs, refer
to the program directory or preventative service The user indicated that specific connection names were
planning (PSP) updates. to be specified for ENABLE or DISABLE, but the
associated connection type field was not updated. The
ENABLE or DISABLE of connection names requires the
| DSNE136I DB2 IS OPERATING IN RESTART
corresponding connection type to also be specified for
| LIGHT MODE. INDOUBT
ENABLE or DISABLE.
| RESOLUTION ONLY
System action:
| Explanation:
The TSO attachment facility is ready for more input.
| The DB2 member is not available for normal operation.
| It is only available to commit coordinators that have User response:
| indoubt units of recovery that need to be resolved with
Enter Y (Yes) on the connection type for the associated
| this member.
connection names.
| System action:
| Control returns to the caller. Your request was not
System action:
DSNE233A MEMBER NAME MUST NOT BE
SPECIFIED MORE THAN ONCE The TSO attachment facility is ready for more input.
Explanation: User response:
The LIBRARY field containing the data set name, also Enter Y (YES) for each individual connection type to
contains a member name. ENABLE, or DISABLE.
System action:
DSNE237A SPECIFY ENABLE ALL OR SPECIFIC
The TSO attachment facility is ready for more input.
CONNECTION TYPES
User response:
Explanation:
The member name must be specified only once, and
In addition to requesting that all connection types be
must be specified on the MEMBER field.
enabled, the user also requested that specific connection
types be enabled. The enable of all connection types
DSNE234A EITHER DBRM MEMBER OR includes the enable of specific connection types.
INCLUDE PACKAGE LIST MUST BE
System action:
SPECIFIED
The TSO attachment facility is ready for more input.
Explanation:
User response:
The BIND PLAN subcommand requires either a DBRM
member name or a package list as input, neither was Specify specific connection types to be enabled, or
specified. specify that all connection types are to be enabled.
System action:
DSNE240A ISPF RETURNED AN UNEXPECTED
The TSO attachment facility is ready for more input.
CODE WHILE CLOSING A TABLE
User response:
Explanation:
Enter a DBRM member name(s), or specify that a
An ISPF error return code was encountered when
package list is to be included. Both options are also
attempting to perform a TBCLOSE for an ISPF table
allowed.
while processing the current subcommand panel.
System action:
DSNE235A plan/package NAME IS A DUPLICATE
OF PRIMARY plan/package NAME TSO processing for the current subcommand is
terminated.
Explanation:
System programmer response:
In addition to the primary ’plan’ or ’package’ name
specified on the REBIND or FREE subcommand panel, Verify that the ISPF table library allocated to the
the user also specified that additional plans or DSNETBLS DD statement has sufficient space or
packages were to be included in the list. The primary directory entries available. Also refer to the ISPF error
’plan’ or ’package’ name was again specified to be log for additional diagnostic information.
included in the list.
User response:
System action:
Notify the system programmer.
The duplicate of the primary ’plan’ or ’package’ name
is automatically deleted from the list to avoid errors
during subcommand processing. The TSO attachment DSNE241A INTERNAL PROCEDURE WAS
facility is ready for more input. PASSED AN INVALID NUMBER OF
ARGUMENTS
User response:
Explanation:
Complete the list of additional plans or packages.
A TSO Interpreter error was encountered while
executing a subroutine during the processing of the
DSNE236A SPECIFY A CONNECTION TYPE TO current subcommand.
ENABLE OR DISABLE
System action:
Explanation:
TSO processing for the current subcommand is
The user indicated that individual connection types terminated.
were to be ENABLED or DISABLED, but no specific
connection types were specified. System programmer response:
80 Messages
DSNE242A • DSNE246A
Notify the IBM support center that an error was Notify the system programmer.
encountered in the TSO SYSCALL instruction.
User response: DSNE244A CANNOT SAVE CREATED TABLE,
VERIFY SPACE IN TABLE LIBRARY
Notify the system programmer.
Explanation:
Problem determination:
An ISPF TBSAVE function returned with a condition
The TSO SYSCALL instruction is not passing all the
code greater than zero.
parameters to a subroutine defined within the CLIST.
System action:
DSNE242A ISPF RETURNED AN UNEXPECTED TSO processing for the current subcommand is
CODE WHILE SETTING SEARCH terminated.
ARGUMENTS
System programmer response:
Explanation:
Verify that the ISPF table library allocated to the
An ISPF table for the current function does not contain DSNETBLS DD statement has sufficient space and
the expected column or table format. directory entries available. Also refer to the ISPF error
log for additional diagnostic information.
System action:
User response:
TSO processing for the current subcommand is
terminated. Notify the system programmer.
System programmer response:
DSNE245A ISPF RETURNED AN UNEXPECTED
Delete the ISPF table in error. The table is recreated
CODE WHILE ADDING A ROW TO A
automatically during the next invocation of the DB2I
TABLE
function.
Explanation:
User response:
An ISPF TBADD function returned with a condition
Notify the system programmer.
code greater than four.
Problem determination:
System action:
The format of the ISPF table was changed since the last
The TSO attachment facility is ready for more input.
successful use of the table. Refer to the DB2I ISPF table
library allocated to the DSNETBLS DD statement, and System programmer response:
examine the ISPF error log for additional diagnostic
Verify that the user has enough memory to perform
information.
ISPF functions. Also refer to the ISPF error log for
additional diagnostic information.
DSNE243A ISPF RETURNED AN UNEXPECTED
User response:
CODE DURING A TABLE DISPLAY
Enter the DB2I CANCEL command, and notify the
Explanation:
system programmer.
An ISPF error was encountered when attempting to
display a DB2I table panel.
DSNE246A ISPF RETURNED AN UNEXPECTED
System action: CODE WHILE DELETING A ROW
TSO processing for the current subcommand is Explanation:
terminated.
An ISPF TBDELETE function returned with a condition
System programmer response: code greater than zero.
Insure that the DB2I panel and panel library are System action:
established correctly. If the format of both is correct,
TSO processing for the current subcommand is
then use ISPF option 7.2 to test the panel for additional
terminated.
errors.
System programmer response:
Examine the ISPF error log for additional error
information and determine the name of the panel to be Verify that the user has enough memory to perform
displayed. ISPF functions. Also refer to the ISPF error log for
additional diagnostic information.
User response:
User response:
The TSO attachment facility is ready for more input. The user tried to select the ’hostlang’ APPLICATION
LANGUAGE and the comma option of the DECIMAL
User response: POINT field on the DB2I defaults panel. This
Correct the invalid command entry. combination is not supported.
System action:
DSNE250A PLEASE ENTER THE COMMAND AT The defaults panel is displayed again.
THE LINE WITH THE
PLAN/PACKAGE NAME User response:
82 Messages
DSNE291A • DSNE297A
A DB2I function has just completed. The return codes The system is waiting for new input to the panel.
for that function are returned in this message. The
User response:
variable ’hex-code’ is a 3-digit hexadecimal number; the
variable ’decimal-code’ is a 3-digit decimal number. Enter a data set name for COPYDSN, and/or
Refer to the appropriate MVS publication for RCPYDSN1.
DSNE298A ERROR DURING EDIT: CLIST data set DSNE345I WARNING: DB2 DATA CORRUPTION
name CAN RESULT FROM THIS SPUFI
SESSION BECAUSE THE CCSID USED
Explanation:
BY THE TERMINAL IS NOT THE
Errors were encountered while attempting to change SAME AS THE CCSID USED BY
the online book data set names in the DB2 CLIST SPUFI. TERMINAL CCSID
member DSNEMC01. No data set names were changed. terminal-ccsid. SPUFI CCSID: spufi-ccsid.
NOTIFY THE DB2 SYSTEM
System action: ADMINISTRATOR.
The system is waiting for new input to the panel. Explanation:
System programmer response: The current SPUFI session was initiated on a TSO
If you are unable to determine the problem, you can terminal that uses a coded character set identifier
trace the DB2 CLIST execution while displaying this (CCSID) of terminal-ccsid. However, SPUFI was bound
panel. on the local DB2 server using a CCSID of spufi-ccsid.
This discrepancy can lead to unexpected data
User response: conversion, affecting any characters that do not map to
Ensure that the CLIST data set name is correct and the same code point in the two CCSIDs.
contains the DSNEMC01 CLIST member to be changed. If terminal-ccsid is blank, then the terminal code page
This CLIST data set must also be available to the TSO and character set cannot be queried or they are not
user ID in WRITE mode. This error will continue to be supported by ISPF. Possible reasons why the terminal
displayed on the panel until the error is resolved or the code page and character set cannot be queried include:
user exits the panel (END).
v Hardware limitation such as use of older terminals
Problem determination: v Improper configuration of the terminal emulator
Examine the CLIST trace output for any TSO/ISPF software
nonzero return codes encountered during CLIST v Improper BTAM or control unit setup
execution.
| A blank spufi-ccsid indicates that SPUFI might have
If you suspect an error in DB2, refer to Part 2 of
| received an unexpected SQLCODE when it attempted
Diagnosis Guide and Reference for information on
identifying and reporting the problem.
| to query the current application encoding scheme.
| Diagnostics for that SQLCODE appear directly after the
| DSNE345I message in the message warning panel.
DSNE340I INTERNAL ERROR - ILLEGAL TYPE
System action:
IN MODULE module-name
SPUFI waits for the user to indicate whether to
Explanation:
continue or quit.
An internal DB2 problem has occurred. The named
System programmer response:
module has detected a nonexistent SQLTYPE.
On the local DB2, SPUFI expects to process only
System programmer response:
EBCDIC character data encoded in the CCSID of
If you suspect an error in DB2, refer to Part 2 of spufi-ccsid. Ensure that the user’s TSO terminal
Diagnosis Guide and Reference for information on configuration is updated to use a CCSID of spufi-ccsid.
identifying and reporting the problem. Verify the data integrity of all tables modified during
the SPUFI session and follow standard recovery
User response:
procedures. Contact IBM for guidance if widespread or
Collect the SPUFI trace and ISPF log, and notify either long term data corruption is evident (for example, if
the system programmer or the database administrator. many users report this message when using SPUFI).
You may have to rerun the failing job after you have Special considerations:
turned on trace. This will enable you to send trace
Blank CCSIDs
messages to the ISPF log.
As noted previously, a blank terminal-ccsid
setting occurs when the terminal code page
and character set cannot be queried or they are
not supported by ISPF. Check for the
following situations:
v If the message occurs when using a terminal
emulator, verify that the emulator software
is configured with a CCSID setting.
84 Messages
DSNE346I • DSNE354A
v Check the VTAM® setup: The VTAM | hexadecimal format, go to the SPUFI defaults panel
logmode entry used to define the session | and change the setting of the FOR BIT DATA field from
characteristics for the terminal must have | ASIS to HEX.
the EDS (extended data stream) bit turned
’on’ in the PSERVIC (that is,
DSNE351A EDIT PROCESSING OPTION MUST
pservic=xx80xx..). For more information,
BE Y (YES) OR N (NO)
consult OS/390 ISPF Planning and
Customization and the z/OS SNA Network Explanation:
Implementation Guide.
The user specified an edit option other than ’YES’,
v Older terminal hardware such as the IBM ’NO’, or the abbreviation ’Y’ or ’N’. A valid user
327x series do not support the EDS, so a response determines whether SPUFI invokes the ISPF
CCSID cannot be determined. You can editor to allow the user to edit the input data set.
instruct end users of such devices to specify
in the SPUFI defaults panel that the System action:
DSNE345I message should be suppressed.
SPUFI will wait until the user enters a valid response.
Note that suppression applies only when
the terminal CCSID is blank. You cannot use User response:
this field to suppress DSNE345I when
Type in a ’Y’ or an ’N’, and press ’ENTER’.
terminal-ccsid is non-blank.
For more information about terminal-ccsid and DSNE352A EXECUTE PROCESSING OPTION
spufi-ccsid, consult the Installation Guide. MUST BE Y (YES) OR N (NO)
Explanation:
| A blank spufi-ccsid indicates that SPUFI probably
| received an unexpected SQLCODE when it attempted The user specified an execute option other than ’YES’,
| to query the current application encoding scheme. ’NO’, or the abbreviation ’Y’ or ’N’. A valid user
| Check the diagnostics for the SQLCODE that is response determines whether SPUFI executes the SQL
| displayed directly after the DSNE345I message, and statements in the user input data set.
| then respond to the diagnostics accordingly.
System action:
User response:
SPUFI waits until the user enters a valid response.
Notify the system programmer. Depress the END key
User response:
to quit or the ENTER key to continue. Important:
Continuing can result in corruption of data stored by Type in a ’Y’ or an ’N’, and press ’ENTER’.
DB2.
DSNE355A CHANGE DEFAULTS PROCESSING The system waits for the next user input.
OPTION MUST BE Y (YES) OR N (NO)
User response:
Explanation:
At this point you can change the SPUFI panel variable
The user specified a change-default option other than settings to initiate a new SPUFI request, or you can exit
’YES’, ’NO’, or the abbreviation ’Y’ or ’N’. A valid user SPUFI.
response determines whether SPUFI displays the
current-session SPUFI defaults and allows the user to
DSNE363A ONLY RR (REPEATABLE READ), CS
change the defaults.
(CURSOR STABILITY), OR UR
System action: (UNCOMMITTED READ) ALLOWED
User response: The user has entered an invalid isolation level. This
value must be one of the following:
Type in a ’Y’ or an ’N’, and press ’ENTER’.
v RR
v CS
DSNE359A OUTPUT DATA SET NAME
REQUIRED FOR EXECUTE OR v UR
BROWSE
’Isolation level’ here refers to the degree to which the
Explanation: SPUFI user wants to isolate SQL execution from the
The user did not specify the name of the output data effects of other concurrently executing DB2
set. applications.
System action: RR
SPUFI waits until the user specifies an output data set. If the repeatable read (RR) level is specified
and the AUTOCOMMIT option is ’YES’, other
User response: applications can modify the selected database
values as soon as the SPUFI EXECUTE phase
Type in the correct entry, and press ’ENTER’.
is completed and as soon as the automatic
COMMIT (or ROLLBACK, if an error was
DSNE360A THE OUTPUT DATA SET MUST encountered) operation is performed.
RESIDE ON DASD Therefore, it is possible that the retrieved data
being browsed by the user has already been
Explanation:
modified by another application.
The user has attempted to send the output of SPUFI to
If the RR level is specified and the
a SYSOUT data set. He must enter a generic device
AUTOCOMMIT option is ’NO’, then no other
class that contains only DASD devices.
DB2 application executing concurrently can
System action: change any of the selected database values
until the SPUFI user issues either a COMMIT
SPUFI waits until the user specifies a valid output or a ROLLBACK. Therefore, other applications
device class. might be in a normal wait state while the
User response: SPUFI user is browsing the output data set.
86 Messages
DSNE364A • DSNE371A
System action:
DSNE367A ACTION MUST BE C (COMMIT) OR R
| SPUFI waits until the user specifies a valid isolation (ROLLBACK) OR D (DEFER)
| level.
Explanation:
User response:
This message requests the user to make a commit
Type in the correct entry, and press ’ENTER’. action decision.
User response:
DSNE364A token IS INVALID AS AN SQL
STATEMENT TERMINATOR To commit all the changes made since the last commit
point, enter a ’C’. To undo all the changes that have
Explanation: been made since the last commit point, enter an ’R’. To
defer the decision, enter a blank.
The user has entered an SQL statement terminator
(token) that is not supported. The following values are
not valid for use as a SQL statement terminator: DSNE368A YES OR NO MUST BE ENTERED FOR
v blank EACH PROCESSING OPTION
v comma Explanation:
v single and double quotes One of the processing options was left blank or set to
v underscore blank by the user.
v left and right parenthesis User response:
System action: Enter ’YES’ or ’NO’ for each processing option.
The statement cannot be executed.
User response: DSNE370A INPUT DATA SET COULD NOT BE
OPENED
Specify a valid SQL statement terminator.
Explanation:
DSNE365A SQL STATEMENT TERMINATOR HAS The input data set could not be opened because of
BEEN CHANGED TO token invalid data set attributes. The logical record length
(LRECL) of the input data set must be 80K. The record
Explanation: format (RECFM) must be either F or FB. The input data
The SPUFI input data set contains a #SET statement set may be either sequential or partitioned.
that changes the SQL statement terminator to token. User response:
System action: Specify an input data set having valid attributes.
token is the SQL statement terminator until another
#SET statement changes it or the end of the input data DSNE371A OUTPUT DATA SET COULD NOT BE
is reached. OPENED
Explanation:
The output data set could not be opened because of
invalid data set attributes. The logical record length
(LRECL) must be at least 80KB and less than 32KB. The
record format (RECFM) must be F, FB, FBA, V, VB, or
Processing does not begin until the panel entries are Remove the forms control characters or machine control
correct and the user presses ’ENTER’. characters from the input data set, and try again.
User response:
DSNE379A text from DYNALLOC
The output data set must be sequential. Enter a
sequential data-set-name (no member) in the output Explanation:
data set field.
An attempt to allocate a data set has failed. This
message contains the secondary explanation for the
DSNE375A ACCESS TO INPUT DATA SET NOT failure.
AUTHORIZED
User response:
Explanation:
Correct the condition, and resubmit the subcommand.
A local installation-supplied exit has rejected access to
the input data set specified by the user.
DSNE381A UNEXPECTED ALLOCATION RETURN
User response: CODE return-code, reason-code
88 Messages
DSNE384A • DSNE390A
Print the ISPF log, and collect a dump of the TSO Specify logical record length (LRECL) and block size
address space. Refer to Part 2 of Application appropriately on the DSNESP02 panel.
90 Messages
DSNE603E • DSNE610I
92 Messages
DSNE617I • DSNE624I
input data set. ’number’ specifies the SQL return code set. The term ’nn’ is a count of the total number of
for the statement. These return codes are listed in records read from the input data set.
Codes.
System action:
System action:
Input data set processing is completed, and this
Input data set processing is completed, and this message is included in the SPUFI output.
message is included in the SPUFI output.
DSNE622I NUMBER OF OUTPUT RECORDS
DSNE617I COMMIT PERFORMED, SQLCODE IS WRITTEN IS nn
number
Explanation:
Explanation:
This message is written to the output data set after
When an input file is executed successfully and the processing all SQL statements in the current input data
user specified an AUTOCOMMIT option of ’YES’, this set. The term ’nn’ is a count of the total number of
message is written to the output data set to indicate the records written to the output data set.
status of the COMMIT that was performed. ’number’
System action:
specifies the SQL return code for the COMMIT. These
return codes are listed in Codes. Input data set processing is completed, and this
message is included in the SPUFI output.
System action:
Input data set processing is completed, and this
DSNE623I SYNTAX ERROR AT RECORD xx,
message is included in the SPUFI output.
OFFSET xx
Explanation:
DSNE618I ROLLBACK PERFORMED, SQLCODE
IS number A syntax error was detected in the SQL statement
preceding this message in the output data set. ’xx’
Explanation:
identifies the erroneous line number in the SQL
When an error is encountered while executing a SPUFI statement, and ’yy’ identifies the offset (in characters)
input file, and the user specified an AUTOCOMMIT of the error within that record.
option of ’YES’, this message will be written to the
System action:
output data set to indicate the status of the ROLLBACK
that was performed. ’number’ specifies the SQL return Input data set processing is completed, and this
code for the statement. These return codes are listed in message is included in the SPUFI output.
Codes.
User response:
System action:
Correct the specified syntax error in the input data set,
Input data set processing is completed, and this and execute the job again.
message is included in the SPUFI output.
DSNE621I NUMBER OF INPUT RECORDS READ Rearrange your library concatenation so that the
IS nn ISPLINK module can be located. This module resides in
the ISPF load library.
Explanation:
This message is written to the output data set after
processing all SQL statements in the current input data
94 Messages
DSNE808A • DSNE910E
System action:
DSNE905I EXECUTION COMPLETE, MEMBER
DB2 waits for the user to specify either the COMMIT member-name ADDED
(C) or the ROLLBACK (R) option.
Explanation:
User response:
A DCLGEN subcommand executed successfully, adding
Enter ’C’ or ’R’ to continue. the ’member-name’ specified in the message to the data
set specified in the DCLGEN subcommand.
DSNE808A EDIT SESSION HAS COMPLETED. System action:
PRESS ENTER TO CONTINUE.
The TSO attachment facility is ready for more input.
Explanation:
The user has exited from the ISPF editor. DSNE908E csect-name INVALID USE OF parameter
IN PARAMETER LIST OF KEYWORD
System action: keyword.
SPUFI waits form the next user input. Explanation:
User response: An invalid parameter was specified in the parameter
Press ’Enter’ if you want to continue. Press ’END’ if list of the specified keyword.
you want to terminate your SPUFI session. The SPUFI System action:
panel variable settings can be changed at this point.
Subcommand processing is terminated. The TSO
attachment facility is ready for more input.
DSNE901I EXECUTION COMPLETE
User response:
Explanation:
Correct the parameter list in error, and resubmit the
Execution of a subcommand has successfully job.
completed.
Severity:
System action:
8
The TSO attachment facility is ready for more input.
Explanation:
DSNE910E csectname WARNING, THE OWNER
A DCLGEN subcommand executed successfully, KEYWORD WAS SPECIFIED WITH A
replacing the ’member-name’ specified in the message. QUALIFIED TABLE NAME. OWNER
System action: KEYWORD IGNORED
96 Messages
DSNE926E • DSNE931E
The TSO attachment facility is ready for more input. Correct the subcommand, and resubmit the job.
System programmer response:
DSNE929E TABLE NAME LOCATION OF
Re-create the problem with DSN tracing turned on.
(location-name) IS TOO LONG.
Collect the trace stream in the DSNTRACE data set. If
CANNOT EXCEED 16 CHARACTERS
you suspect an error in DB2, refer to Part 2 of Diagnosis
IN LENGTH.
Guide and Reference for information on identifying and
reporting the problem. Explanation:
User response: DCLGEN detected an invalid AT(location) keyword
parameter. The specified location name is too long.
Notify the system programmer.
System action:
DSNE926E COMMAND REJECTED - command Your DCLGEN subcommand was not processed. The
NOT SUPPORTED UNDER DSN command processor issues a return code of 8. The
command_processor DSN is ready for more input.
Explanation: User response:
The user entered a TSO TIME or TEST command. Resubmit the DCLGEN subcommand specifying a
These are not supported by DSN or DB2I. location name that does not exceed 16 characters.
System action:
DSNE930E TABLE NAME OF table-name MUST BE
The user should leave DSN or DB2I, return to TSO, and
QUALIFIED WHEN SPECIFIED WITH
retry the command. DSN can be run under TSO TEST.
LOCATION OF location-name
The TSO attachment facility is ready for more input.
Explanation:
User response:
DCLGEN detected an invalid TABLE keyword
Enter the DSN subcommand, or leave DSN to execute
parameter. You must specify a qualified table name
the requested command.
with the AT (location) keyword.
System action:
DSNE927E RUN SUBCOMMANDS REQUIRE
(1)PROGRAM PARM OR (2)PLAN Your DCLGEN subcommand was not processed. The
AND CP PARMS DSN command processor issues a return code of 8.
DSN is ready for more input.
Explanation:
User response:
RUN subcommands may contain (1) the ’PROGRAM’
parameter and, optionally, the ’PLAN’ parameter or (2) Specify a qualified table name and resubmit the
the ’PLAN’ and command processor (’CP’) parameters. DCLGEN command.
Combinations of (1) and (2) are not allowed.
System action: DSNE931E csect-name keyword-name (parameter_value)
CONTAINS AN INVALID SYMBOL
The TSO attachment facility is ready for more input.
(symbol)
User response:
Explanation:
Correct the subcommand, and resubmit the job.
An invalid ’symbol’ (symbol) was specified in the
’parameter_value’ associated with the specified
DSNE928E RUN SUBCOMMANDS CANNOT ’keyword-name’.
HAVE A PROGRAM PARM AND A CP
System action:
PARM
Subcommand processing is terminated. The TSO
Explanation:
attachment facility is ready for more input.
A RUN subcommand cannot contain both the
User response:
’PROGRAM’ and command processor (’CP’)
parameters. The subcommand should be resubmitted Correct the keyword ’parameter_value’ in error, and
with only one of the parameters. resubmit the job.
System action: Severity:
The TSO attachment facility is ready for more input. 8
User response:
DSNE932I WARNING, ONLY IBM SUPPLIED DSNE938I PLI DECLARATION FOR TABLE
names SHOULD BEGIN WITH DSN table-name
Explanation: Explanation:
The user has issued a BIND, REBIND, or FREE This message is a part of normal DCLGEN output. It
subcommand, using a name or id that begins with tells the name of the table for which the declaration
DSN. was created.
System action: System action:
Processing continues. This message is included in the DCLGEN output.
User response:
DSNE939E csect-name THE COMBINATION
In the future, do not use plan-names, collection-ids, or
ACQUIRE(ALLOCATE) AND
package -ids that begin with DSN. It would be a good
RELEASE(COMMIT)IS NOT
idea to FREE the plan or package you just created and
ALLOWED
to BIND again with a new plan-name, collection-id, or
package-id. Explanation:
The BIND or REBIND subcommand was submitted
DSNE935I ... IS THE DCLGEN COMMAND THAT with conflicting parameters.You cannot specify
MADE THE FOLLOWING ACQUIRE(ALLOCATE) and RELEASE(COMMIT) on
STATEMENTS the same subcommand.
Explanation: System action:
This message is a part of normal DCLGEN output. It The subcommand is terminated and the DSN command
identifies the DCLGEN command that produced the processor reissues theDSN prompt to allow another
declaration of which it is a part. subcommand to be entered.
System action: User response:
This message is included in the DCLGEN output. Enter the corrected subcommand. Refer to Command
Reference for additional information about the BIND
and REBIND subcommands.
DSNE936I THE NUMBER OF COLUMNS
DESCRIBED BY THIS DECLARATION
IS nnn DSNE940E DEFER(PREPARE) INVALID WITH
NODEFER(PREPARE)
Explanation:
Explanation:
This message is a part of normal DCLGEN output. It
tells how many columns were in the table that was The BIND or REBIND subcommand was submitted
named in the DCLGEN command. with conflicting parameters.You cannot specify
DEFER(PREPARE) and NODEFER(PREPARE) on the
System action:
same subcommandbecause these actions conflict.
This message is included in the DCLGEN output.
System action:
The subcommand is terminated and the DSN command
DSNE937I COBOL DECLARATION FOR TABLE
processor reissues theDSN prompt to allow another
table-name
subcommand to be entered.
Explanation:
User response:
This message is a part of normal DCLGEN output. It
Enter the corrected subcommand. Refer to Command
tells the name of the table for which the declaration
Reference for additional information about the BIND
was created.
and REBIND subcommands.
System action:
This message is included in the DCLGEN output. DSNE941I DSNBIND IS A RESERVED PLAN
NAME
Explanation:
This message is generated when the plan name is
’DSNBIND’ in a BIND statement.
System action:
98 Messages
DSNE942E • DSNE948I
Explanation: Explanation:
The REMOTE connection name ’parameter_value’ DCLGEN had to wrap your table or column name(s) in
contains a < or> character in the starting or ending quotes so DB2 could process them. Quotes are not
position of the parameter, but the parameter value is recognized by the PL/I compiler. To avoid compilation
not bracketed by both characters. This message is also errors, use the SQL INCLUDE statement (’EXEC SQL
generated if the first character of the connection name INCLUDE membername’) to merge the DCLGEN
is not an alphabetic character. output with your source program.
If the LU name format of the REMOTE keyword is to Refer to chapter 2 of SQL Reference for more
be used, the name must be specified as <LU_name>. information about the SQL INCLUDE statement.
DSNE949E COMMIT PROCESSING ABNORMAL DCLGEN set the return code to 4 and processed the
TERMINATION, REASON CODE rest of the table.
reason_code
User response:
Explanation:
This is a warning. Be aware that the declaration for
The DSN command processor has initiated a ’prepare column ’colname’ causes a compiler error. You must
to commit’ request in DB2. The request is rejected when edit the declaration before including it in an application
DB2 cannot commit the work performed program.
System action:
DSNE954I csect-name USE OF THE DCLGEN
Commit processing is terminated. COLSUFFIX(YES) OPTION WILL
User response: RESULT IN A MIXED FIELD NAME
FOR COLUMN colname. THE lang
Examine the reason code associated with this message, LANGUAGE DOES NOT SUPPORT
and respond as indicated before resubmitting the job. MIXED FIELD NAMES.
Problem determination: Explanation:
Reference the associated reason code to determine why The COLSUFFIX(YES) option and a double-byte
the ’prepare to commit’ was not successful. NAMES prefix were specified in a DCLGEN invocation,
but column colname contains single-byte characters. This
DSNE950E DCLGEN DOES NOT SUPPORT THE combination would result in a generated field name
lang LANGUAGE with a mixture of double-byte and single-byte
characters, but the lang language does not support
Explanation: mixed field names.
A DCLGEN user attempted to specify a LANGUAGE System action:
parameter, ’lang’, that DCLGEN does not support.
DCLGEN set the return code to 4 and generated the
System action: field name as requested.
DCLGEN processing terminates. User response:
User response: This is a warning. Be aware that the declaration for
Correct the LANGUAGE parameter and resubmit the column colname causes a compiler error. You must edit
DCLGEN subcommand. the declaration before including it in an application
program.
100 Messages
DSNE956A • DSNE967E
The PARMS option parameter-string of the RUN Subcommand processing is terminated. DSN command
subcommand cannot exceed 100 (decimal) characters in processor reissues the DSN prompt to allow you to
length. enter another subcommand.
The TSO attachment facility is ready for more input. Enter the corrected subcommand. Refer to Command
Reference for additional information about the
User response: connection type parameter values supported on the
Correct the PARMS option and resubmit the job. ENABLE and DISABLE keywords.
Severity:
DSNE964E csect-name INVALID SYNTAX FOR 8
keyword KEYWORD PARAMETER
parameter
DSNE967E keyword_name KEYWORD CANNOT
Explanation: BE SPECIFIED MORE THAN ONCE
A parameter that does not follow DB2 naming PER RUN
conventions was specified for keyword. Explanation:
System action: Either the BIND PACKAGE MEMBER or LIBRARY
Subcommand processing is terminated. The DSN keywords specified more than one parameter value.
command processor reissues the DSN prompt to allow Only one member or library name is permitted.
you to enter another subcommand. System action:
User response: Subcommand processing is terminated. DSN command
Correct the keyword parameter value in error, and processor will reissue the DSN prompt to allow another
resubmit the command.Refer to Command Reference for subcommand to be entered.
additional information about the specification of a User response:
package name and the REBIND/BIND
PACKAGE/PLAN or FREE PACKAGE subcommand. Enter the corrected subcommand. Refer to Command
102 Messages
DSNE976E • DSNE999
DSNG001I EDM stype CAN NOT BE DECREASED DSNG004I EDM stype HAS A FINAL ALLOCATED
BELOW THE VALUE isize SPECIFIED SIZE asize
AT DB2 STARTUP
Explanation:
Explanation:
This message is issued in response to a request to
The EDM stype storage cannot be decreased below the decrease the EDM stype storage. The message is issued
size that was specified at DB2 startup. when the requested new level is reached.
System action: stype The EDM pool that is being reduced. Possible
values are Pool, DBD Pool, or Statement Pool.
Processing continues.
asize The EDM stype storage that is available.
DSNG002I EDM stype HAS AN INITIAL SIZE isize, System action:
REQUESTED SIZE rsize, AND AN
Processing continues.
ALLOCATED SIZE asize
Explanation:
DSNG005I DBD IS INCONSISTENT WITH THE
This message is issued in response to a request to CATALOG. UNABLE TO FIND A ROW
increase or decrease the EDM stype storage. IN SYSTABLES WITH DBID dbid AND
OBID obid.
isize The EDM stype storage size prior to the
request for a change. Explanation:
rsize The requested EDM stype storage size. This message is issued in response to a request to load
a database with DBID dbid. This message is issued
asize The EDM stype storage size immediately
when the row is not found in SYSTABLES.
available.
v When increasing the EDM Pool, the asize is dbid DBID of the database that is being loaded.
the storage available to satisfy the request. obid OBID of a table in the database.
v When decreasing the EDM Pool, the asize is
System action:
the INITIAL size reduced by the amount
that could be released immediately. DBD could not be loaded.
When the asize is larger than the rsize, the Operator response:
difference is marked to be released when it
is no longer referenced. Based on dbid and obid from the message, verify that
the row does not exist in the Catalog. REPAIR DBD
System action: TEST or DIAGNOSE can be run to gather more
Processing continues. diagnostic information. Once you have determined that
the Catalog contains the correct information, REPAIR
DBD REBUILD can be run to rebuild the DBD.
DSNG003I INSUFFICIENT VIRTUAL STORAGE
TO EXPAND EDM stype STORAGE Severity:
Explanation: 8 (error).
108 Messages
Chapter 6. DSNH messages
Message numbers that begin with DSNH communicate information about the DB2
precompiler or the DB2 coprocessor.
References to the DB2 precompiler will also apply to the DB2 coprocessor, unless
otherwise mentioned. The DB2 coprocessor is invoked through the compiler.
’COL cc’ in the messages identifies the source column in which the condition was
detected. The indicated column, ’cc’, usually specifies the location of the column
containing the first character of the associated source token. However, if the
precompiler cannot determine this location, it is the beginning of the statement.
Because the detected error might be similar to a valid, but different, construction,
the SQL parsing might indicate the wrong location for the error.
I 0 Informational
W 4 Warning
E 8 Error
S 12 Severe error
U 16 Unrecoverable error
The following precompiler messages with severity levels of 8 are not changed from
errors to warnings when SQL(ALL) is in effect:
v DSNH051I
v DSNH080I
v DSNH290I
v DSNH291I
v DSNH292I
v DSNH312I
v DSNH313I
v DSNH314I
v DSNH504I
Source tokens
Tokens from your source program do not always appear in messages exactly as
they appear in your program. For example, leading zeros are removed from integer
tokens.
110 Messages
DSNH008I • DSNH012I
System action:
DSNH010I S csectname LINE nnnn COL cc
The character is ignored. UNTERMINATED STRING
CONSTANT BEGINNING text
User response:
Explanation:
Correct the character. You might need to place the
character within quotation marks or apostrophes. The constant identified in the message as ’text’ is not
Check to ensure that the CCSID in which the source is terminated properly.
written matches the CCSID option for the Precompiler.
System action:
For example, if the CCSID 1047 codepoints for left and
right square brackets (hexadecimal ’AD’ and ’BD’) are The string is treated as if it were terminated by the end
used in a C source program, ensure that the of file.
Precompiler CCSID option is CCSID(1047).
User response:
Severity:
Terminate the string constant. Check for and correct
8 (error) any missing or extra quotation marks and apostrophes.
These errors are likely to cause others. Some statements
were probably missed because of missing or extra
DSNH008I S csectname LINE nnnn COL cc NESTED
string delimiters.
INCLUDE NOT SUPPORTED
Severity:
Explanation:
12 (severe error)
While processing an INCLUDE, another nested
INCLUDE statement was encountered.
DSNH011I S csectname LINE nnnn COL cc
System action:
UNTERMINATED COMMENT
The nested INCLUDE statement is ignored.
Explanation:
User response:
A comment is not terminated properly. This message is
Remove the nested INCLUDE statements; they are not only issued for HOST(PLI) and HOST(C).
allowed in an included file. The DB2 precompiler
System action:
permits only one level of INCLUDE statements.
The string is treated as if it were terminated by the end
Severity:
of file.
12 (severe error)
User response:
Ensure that the comment terminator is typed properly
DSNH009I S csectname LINE nnnn COL cc MEMBER
and that it is within the specified margins. This error is
name COULD NOT BE INCLUDED
likely to cause others. Some statements were probably
Explanation: missed because of the missing comment terminator.
The identified member name was not found or could Severity:
not be read.
12 (severe error)
System action:
Processing continues without the data from that DSNH012I W csectname LINE nnnn COL cc
member. INVALID CONTINUATION
Ensure that the member is in the library and that its The continuation does not follow the host language
name is spelled correctly. Check and correct any JCL rules.
errors. They are likely to cause other errors. Ensure that
System action:
the data set and library parameters are correct.
Processing continues. Additional errors might result.
Severity:
User response:
12 (severe error)
Follow the host language continuation rules and
embedded SQL continuation rules. Check the margin
option. This error is most common in assembler
language in cases where a continuation begins before
the continuation column (the continuation column is
column 16 by default).
112 Messages
DSNH023I • DSNH028I
114 Messages
DSNH034I • DSNH050I
Severity:
DSNH034I W csectname LINE nnnn COL cc
STATEMENT INSERTS MORE OR 4 (warning)
LESS VALUES THAN THE NUMBER
OF COLUMNS DECLARED
DSNH042I W csectname OPTION: option OPTION
| Explanation: INVALID FOR HOST LANGUAGE
| The number of values specified in an INSERT operation Explanation:
| is different from the number of columns specified in
| the DECLARE TABLE statement for the receiving table. The option identified in the message is not valid. The
QUOTE and COMMA options are not permitted with
System action: HOST(ASM), HOST(PLI), or HOST(C). The TWOPASS
option is not permitted with HOST(COBOL).
Processing continues.
System action:
| User response:
The specified option is ignored.
| Insert the correct number of values. If the DECLARE
| TABLE statement is incorrect, this warning might also User response:
| be incorrect. If the INSERT operation is incorrect, you
| must correct it. Remove the invalid option, or correct the host
specification.
Severity:
Severity:
4 (warning)
4 (warning)
because no table declarations were found before the Avoid implicit definitions by inserting (or including)
first SQL statement that referenced a table or column. table declarations before they are referenced.
System action: Severity:
Processing continues. Suppression is discontinued if a 8 (error)
table declaration is found.
User response: DSNH053I W csectname NO SQL STATEMENTS
WERE FOUND
Insert (or INCLUDE) table declarations before they are
referenced in order to permit table and column Explanation:
checking.
No SQL statements were found in the precompiler
Severity: input file. An empty DBRM member was written.
0 System action:
Processing continues.
DSNH051I E csectname LINE nnnn COL cc sqltype
User response:
name PREVIOUSLY DECLARED OR
REFERENCED If you embedded SQL statements in your application
program and none were found, make sure your column
Explanation:
margins are properly defined for your application
The variable sqltype is TABLE, CURSOR, or program.
STATEMENT. The identifier name was already defined
Severity:
with the given sqltype. The definition might have
occurred implicitly. For example, name might have been 4 (warning)
found in the FROM clause of a SELECT, causing it to
be defined as a table.
DSNH060I E csectname LINE nnnn COL cc INVALID
System action: type SPECIFICATION: spec
The name is installed in the symbol table as a Explanation:
duplicate.
The type is either SCALE or LENGTH. The spec is the
User response: given SCALE or LENGTH specification in an SQL
declaration. Length and scale specifications must be
Remove duplicate definitions, or correct the references.
unsigned integers. The scale specification, where
Avoid implicit definitions by inserting (or including)
permitted, cannot exceed the length. The length
table declarations before they are referenced. Check the
specification cannot be 0.
number of passes used. Use the cross-reference and
source listings to help resolve this type of error. System action:
Severity: Processing continues.
8 (error) User response:
Correct the length or scaling.
DSNH052I E csectname LINE nnnn COL cc
COLUMN name IS ALREADY DEFINED Severity:
IN TABLE table-name 8 (error)
Explanation:
The identified name is already defined as a column in DSNH080I E csectname LINE nnnn COL cc usage
the table named table-name. The definition might have VARIABLE name IS NOT type TYPE
occurred implicitly. For example, table-name might have Explanation:
been found in a select-list, causing name to be defined
as a column within table-name if table-name was not The usage is INDICATOR or STRING. The type is
declared as a host variable. SMALLINT, VARCHAR, or CHARACTER. The data
type of the variable name is not acceptable. All indicator
System action: variables must be small integers. PREPARE and
The name is installed in the symbol table as a EXECUTE strings must be variable character strings,
duplicate. except for FORTRAN, which requires character type.
Remove duplicate definitions, or correct the references. If the containing SQL statement is a declaration, it is
116 Messages
DSNH081I • DSNH084I
DSNH090I S csectname LINE nnnn COL cc HOST The statement attempted to use the LONG VARCHAR
VARIABLE NOT PERMITTED HERE: or LONG VARGRAPHIC syntax. This syntax cannot be
name used for the following statements:
118 Messages
DSNH102I • DSNH104I
16
DSNH103I E csectname constant IS AN INVALID
NUMERIC CONSTANT
DSNH102I E csectname STRING CONSTANT IS
Explanation:
TOO LONG. STRING BEGINS string
The token was found. It begins with a digit, but it is not
| Explanation:
a valid integer, decimal, or float literal. Identifiers
| The string constant beginning with string has a length cannot begin with a digit except for the WHENEVER
| greater than the maximum allowed length. Most strings statement with HOST(FORTRAN), and the identifiers
| have these limits: in COBOL.
| v For a hexadecimal constant (X, GX, or UX), the System action:
| number of hexadecimal digits must not exceed 32704.
If the containing SQL statement is a declaration, it is
| v Any other character string constant must be short
discarded. If the containing SQL statement is
| enough so that its UTF-8 representation requires no
executable, it is replaced by host language statements
| more than 32704 bytes.
that will, if executed, set an error code in the SQLCA.
| v Any other graphic string constant must be short
| enough so that its UTF-8 representation requires no User response:
| more than 32704 bytes. Check the indicated token for validity. Use apostrophes
| v The sum of the lengths of the UTF-8 representations or quotation marks if a character literal is desired.
| of the constant values in an ENDING AT clause must Remove the invalid characters if a number is desired.
| not exceed 765 bytes. This clause applies to CREATE
Severity:
| TABLE, ALTER TABLE, CREATE INDEX, or ALTER
| INDEX. 8 (error)
| In some contexts, however, the limit is smaller; see the
| SQL Reference for the specific cases. DSNH104I E csectname LINE nnnn COL cc ILLEGAL
SYMBOL ″token″. SOME SYMBOLS
| For special registers, the allowable length depends on THAT MIGHT BE LEGAL ARE:
| the particular special register. A string that exceeds the token-list
| limit can be specified only through assignment from a
Explanation:
| host variable. If this release of DB2 increases the
| maximum allowed length of a string constant, then an A syntax error was detected where the symbol ″token″
| attempt to exploit the new length before using the New occurs in the SQL statement. The list of symbols that
| Function Mode produces this SQL return code. might be legal shows some alternate symbols that
could possibly be correct at that point, if the preceding
| Two consecutive string delimiters are used to represent part of the statement is entirely correct.
| one string delimiter within the character string, but
However, the preceding part of the statement might be
| these count as 2 bytes when calculating the lengths of
incorrect. For example, if an important keyword is
| character string constants.
omitted, DB2 detects the error later, and not always
System action: immediately after the point where the keyword should
appear. The list of alternate symbols are only
If the SQL statement containing the string is a
suggestions.
declaration, it is discarded. If the SQL statement
containing the string is executable, it is replaced by System action:
host language statements that, if executed, set an error
If the containing SQL statement is a declaration, it is
code in the SQLCA.
discarded. If the containing SQL statement is
User response: executable, it is replaced by host language statements
that will, if executed, set an error code in the SQLCA.
Correct the string. If a shorter string is acceptable,
reduce the length of the string constant. If a long string User response:
is required, a host variable is required.
Correct the statement and precompile the program
Severity: again.
8 (error) Severity:
8 (error)
DSNH109I E csectname LINE nnnn COL cc type | The string constant that begins with the specified string
CLAUSE NOT PERMITTED | is invalid because it has at least one of the following
| errors:
Explanation:
| v the string constant contains one or more characters
The type is INTO, ORDER BY, FOR UPDATE, , USING, | that are not valid hexadecimal digits
LARGE, or CORRELATION NAME. | v the string constant does not have an even number of
| v A SELECT INTO statement cannot include ORDER | digits
| BY, because the result cannot be more than a single | v for a UX or GX string constant, the number of digits
| row. | is not a multiple of 4
| v A SELECT INTO statement cannot include FOR
System action:
| UPDATE OF, because position is not retained.
120 Messages
DSNH111W • DSNH117I
If the containing SQL statement is a declaration, it is 104 There are no characters between the shift-out
discarded. If the containing SQL statement is and the shift-in characters.
executable, it is replaced by host language statements
105 Shift-out cannot be the first byte of the DBCS
that will, if executed, set an error code in the SQLCA.
character between the shift-out and the shift-in
User response: characters.
Correct the string constant. System action:
Severity: Processing is terminated.
8 (error) User response:
Correct the name.
DSNH111W W csectname LINE nnnn COL cc THE
Severity:
SUBPAGES OPTION IS NOT
SUPPORTED FOR TYPE 2 INDEXES 8 (error)
Explanation:
DSNH115I E csectname LINE nnnn COL cc ILLEGAL
You cannot use the SUBPAGES option for type 2
USE OF COMPARISON OPERATOR
indexes.
operator
System action:
Explanation:
The option is ignored; processing continues.
The syntax is not correct for this type of comparison. A
Programmer response: simple comparison such as ’>’ must not be followed by
a list of items. The ANY and ALL comparisons must
Remove the SUBPAGES option to get rid of the
precede a subselect, rather than an expression or a list
warning.
of items.
Severity:
System action:
4 (warning)
If the containing SQL statement is a declaration, it is
discarded. If the containing SQL statement is
DSNH113I E csectname LINE nnnn COL cc INVALID executable, it is replaced by host language statements
CHARACTER FOUND IN string, that will, if executed, set an error code in the SQLCA.
REASON CODE - nnn
User response:
Explanation:
Correct the syntax. If necessary, refer to chapter 2 of
The string contains an invalid character. It can be an SQL Reference for the correct syntax.
SQL ordinary identifier name, a host variable name, or
Severity:
a DBCS comment.
8 (error)
| Certain SQL identifiers (for example names of buffer
| pools, databases, and plans) must contain only
| uppercase alphabetic or national characters and DSNH117I E csectname LINE nnnn COL cc
| numerics; the first character must be alphabetic or STATEMENT INSERTS THE WRONG
| national. NUMBER OF VALUES
The following reason codes apply to SBCS identifiers: Explanation:
000 An invalid character was found in the SBCS The number of entries in a value-list is not the same as
identifier (including the case in which a DBCS the number of columns specified in an INSERT
identifier was used where only an SBCS statement.
identifier is allowed).
System action:
The following reason codes apply to DBCS identifiers Processing continues.
or comments:
User response:
101 An odd number of bytes exists between the
Correct the syntax. If necessary, refer to chapter 2 of
shift-out and the shift-in character.
SQL Reference for the correct syntax.
102 Either a shift-in or shift-out character is
Severity:
missing.
8 (error)
103 DBCS blanks X’4040’ are not allowed.
Explanation:
DSNH130I E csectname LINE nnnn COL cc THE
The identified column number is either less than 1 or ESCAPE CLAUSE ’x’ CONSISTS OF
greater than the number of items in the select-list. MORE THAN ONE CHARACTER
System action: Explanation:
The cursor declaration is discarded. The literal x used in the ESCAPE clause is too long.
Only one SBCS or one DBCS character is allowed.
User response:
System action:
Correct the column number. If necessary, refer to
chapter 4 of SQL Reference for the correct syntax. The corresponding SQL statement is replaced by host
language statements that will, if executed, set an error
Severity:
code in the SQLCA.
8 (error)
User response:
Correct the string. The literal string for the ESCAPE
DSNH126I E csectname LINE nnnn COL cc ORDER
clause can only be one SBCS or DBCS character.
BY CANNOT BE USED WITH A FOR
UPDATE OF CLAUSE Severity:
Explanation: 8 (error)
The ORDER BY clause makes the cursor incapable of
being updated. DSNH131I E csectname LINE nnnn STATEMENT
WITH LIKE PREDICATE HAS
System action:
INCOMPATIBLE DATA TYPES
The cursor declaration is discarded.
Explanation:
User response:
If the column name at the left of LIKE or NOT LIKE is
This is a DB2 restriction. You can have either an a character type, the expression at the right must be a
ordered cursor or a cursor that can be updated. You character type. If the column name is a graphic type,
cannot specify both attributes for the same cursor. You the expression at the right must be a graphic type.
122 Messages
DSNH132I • DSNH182I
System action:
DSNH171I E csectname LINE nnnn COL cc THE
If the containing SQL statement is a declaration, it is DATATYPE, LENGTH, OR VALUE OF
discarded. If thecontaining SQL statement is executable, ARGUMENT nn OF function-name
it is replaced by host language statementsthat will, if ISINVALID
executed, set an error code in the SQLCA.
Explanation:
User response:
Either the data type, the length or the value of
Correct the syntax. If necessary, refer to chapter 2 of argument nn ofscalar function function-name is incorrect.
SQL Reference forthe correct syntax.
System action:
Severity:
If the containing SQL statement is a declaration, it is
8 (error) discarded. If thecontaining SQL statement is executable,
it is replaced by host language statementsthat will, if
DSNH142I E csectname LINE nnnn COL cc THE SQL executed, set an error code in the SQLCA.
STATEMENT IS NOT SUPPORTED User response:
Explanation: Correct the argument. Refer to Chapter 3 of SQL
The token was found. An SQL statement was detected Reference for rules for each argument of the scalar
that is not supported by the database. The statement function function-name.
might be valid for other IBM relational database Severity:
products or it might be valid in another context. For
example, statements such as VALUES and SIGNAL 8 (error)
SQLSTATE can appear only inside a trigger.
System action: DSNH182I E csectname LINE nnnn COL cc AN
ARITHMETICEXPRESSION WITH A
The SQL statement is replaced by host language DATETIME VALUE IS INVALID
statements that will, if executed, set an error code in
the SQLCA. Explanation:
User response: The specified arithmetic expression contains an
improperly used date/timevalue or labeled duration.
Change the syntax of the SQL statement or remove the
statement from the program. System action:
Severity: If the containing SQL statement is a declaration, it is
discarded. If thecontaining SQL statement is executable,
8 (error) it is replaced by host language statementsthat will, if
executed, set an error code in the SQLCA.
DSNH170I E csectname LINE nnnn COL cc NUMBER User response:
OFARGUMENTS SPECIFIED FOR
function-name IS INVALID Correct the indicated expression. Refer to chapter 2 of
SQL Reference forthe rules for date/time arithmetic.
Explanation:
Severity:
124 Messages
DSNH206I • DSNH290I
Processing continues.
DSNH251I E csectname LINE nnnn COL cc TOKEN
User response: name IS NOT VALID
If the table declares are correct and the column name is Explanation:
not in the table, this creates an error in the BIND step.
The location name cannot contain alphabetic extenders
Correct the DECLARE TABLE statement or the column
for national languages (that is, #, @, and $ in the
name.
United States).
Severity:
System action:
4 (warning)
Processing continues.
User response:
DSNH206I W csectname LINE nnnn COL cc
STATEMENT REFERENCES COLUMN Correct the content of the location name.
column name WHICH IS NOT
Severity:
DECLARED IN THE SPECIFIED
TABLE(S) 8 (error)
Explanation:
The column column name is not contained in any
| DSNH270I FUNCTION NOT SUPPORTED
TABLE declaration for the tables specified in the | Explanation:
statement.
| The statement cannot be processed because it violates
System action: | one or more of the following restrictions:
Processing continues. | v DESC is not allowed in CREATE INDEX if the index
| is an XML index or index on expression.
System programmer response:
| v PADDED is not allowed in CREATE INDEX if the
Check the spelling of the column name. Ensure that all | index is an XML index.
the tables needed were specified in the statement. | v DEFINE NO is not allowed in CREATE INDEX if the
User response: | index is an XML index.
| v DEFER YES is not allowed in CREATE INDEX if the
If the table declares are correct and the column name is
| index is a spatial index.
not in the tables, this creates an error in the BIND step.
Correct the DECLARE TABLE statements or the column | v A spatial index can only be created on a
name. | VARBINARY or BLOB column, or distinct type on
| these data types.
Severity:
| v When a spatial index is created on a LOB column,
4 (warning) | the LOB table space which stores the LOB column
| must exist.
DSNH207I E csectname LINE nnnn COL cc ILLEGAL | v The first argument defined must be a VARBINARY
ORDERBY SPECIFICATION | or BLOB column, or distinct type on these data types
| and all other arguments must be constant literals of
Explanation: | numeric values.
If the select expression involves a UNION operator, the | v A table column can have one spatial index only.
ORDER BY list mustuse numeric constants rather than | System action:
variables.
| The statement cannot be processed.
System action:
| User response:
If the containing SQL statement is a declaration, it is
discarded. If thecontaining SQL statement is executable, | Correct the violation and issue the statement again.
it is replaced by host language statementsthat will, if
| Severity:
executed, set an error code in the SQLCA.
| 8 (error)
User response:
Correct the syntax. If necessary, refer to chapter 4 of
DSNH290I E csectname LINE nnnn COL cc NO
SQL Reference for the correct syntax.
VALID ’END DECLARE SECTION’
Severity: FOUND
8 (error) Explanation:
The user’s source program contains a BEGIN
DECLARE SECTION, but no corresponding END The data type of host variable hostvar is not compatible
DECLARE SECTION was found. with the apparent type of the corresponding select
expression. One of them is numeric and the other is
System action:
character, or one of them is character and the other is
Processing continues. graphic. If the select expression is a column reference,
the data type is obtained from its declaration.
User response:
System action:
Check the application program and ensure that a valid
END DECLARE SECTION statement is present. Processing continues.
8 (error) Ensure that the table definitions are current, and that
the host variable has the proper data type.
Check the application program and ensure that a valid Host variable name should not be declared in this
BEGIN DECLARE SECTION is present. location of the source program. This message is issued
only at reference time.
Severity:
System action:
8 (error)
Processing continues.
DSNH292I E csectname LINE nnnn COL cc HOST User response:
NAME name IS TOO LONG;
If this host variable is used, the user assumes
MAXIMUM IS size CHARACTERS
responsibility for possible exposure of incorrect output.
Explanation: Refer to Part 2 of Application Programming and SQL
Guide to determine where host variables can be validly
Fully qualified C host variable names cannot contain declared.
more than 256 characters.
Declaring a COBOL host variable in the File Section
System action: might lead to incorrect output from SQL statements or
If the containing SQL statement is executable, it is abend 04E with RC=00E7000C.
replaced by host language statements that will, if Severity:
executed, set an error code in the SQLCA.
4 (warning)
User response:
Reduce the length of names or the level of qualification DSNH312I E csectname LINE nnnn COL cc
of the host variable name in error. UNDEFINED OR UNUSABLE HOST
Severity: VARIABLE name
8 (error) Explanation:
The name in the message is used in an SQL statement,
DSNH303I W csectname LINE nnnn COL cc but either no declaration was found in the application
STATEMENT SELECTS program so far, or the attributes are improper for this
INCOMPATIBLE DATA TYPE INTO use. Declarations for host variables used in a
hostvar DECLARE CURSOR statement must precede the SQL
statement, regardless of the ONEPASS or TWOPASS
Explanation: option for the precompiler, or a parameter marker was
expected in an EXECUTE IMMEDIATE statement. This
126 Messages
DSNH313I • DSNH314I
Check the declaration and the attributes of the named System action:
host variable. If you intended the name to refer to a
The corresponding SQL statement is replaced by host
column, the colon (:) should not be present. If you
language statements that will, if executed, set an error
intended a literal, you need to enclose the value in
code in the SQLCA.
string delimiters (apostrophes or quotation marks).
User response:
If you intended to use a host variable, only a subset of
the possible variable declarations are valid for use as a Check the declaration and the attributes of the named
DB2 host variable. The rules for host variables are host variable. Refer to Application Programming and SQL
listed in the application programming guides. Use the Guide for the allowable host variable type and length.
cross-reference listing and precompiler source listing to
Severity:
determine the source of the problem.
v If you use the STDSQL(YES) option for the 8 (error)
precompilation, make sure that all of the host
variable declarations are declared within DSNH314I E csectname LINE nnnn COL cc
BEGIN/END DECLARE SECTIONs. REFERENCE TO HOST VARIABLE
v If the cross-reference listing does not contain the host name IS AMBIGUOUS
variable name, the declaration is missing. If the
source for a declaration is present, a missing Explanation:
terminator from a comment or from a string might The host variable name was defined more than once in
cause this type of error. The margins could also this application program. The precompiler cannot
cause this type of error. distinguish which host variable definition should be
v If the name is present, but the data type is not listed, used here. The following table indicates some possible
the host variable is not usable; it does not follow the combinations. DB2 supports only a single adjacent
rules outlined for valid host variable definitions. qualifier for a host variable name.
v If several definitions exist for the name, the first
reference might occur before the definition. The use
Result Suggested
of the TWOPASS option helps by processing
Case Ref Definition Change
DECLARE statements before the other types of
statements. However, host variable declarations and 1 a x.a Valid None
cursor declarations are processed in the same pass. 2 x.a x.a, y.a Valid None
The host variables referenced in cursor declarations
3 a x.a, y.a DSNH314I Reference x.a
must be defined before the cursor is defined in the or y.a
application program.
4 a x.a, a Valid None
v A parameter marker is expected rather than a host 5 x.a q.x.a, v.x.a No Variable name
variable in an EXECUTE IMMEDIATE statement. precompiler changes
v The data type of a host variable passed in a CALL error, but
statement is not character or varying character. host
v The length attribute of a character or varying language
character host variable passed in a CALL statement compiler will
exceeds 255 characters. issue an
error.
Severity: 6 a a, a No Variable name
8 (error) precompiler changes
error, but
host
language
compiler will
issue an
error.
| Explanation:
| During conversion of the source text into UTF-8
| (CCSID1208), a character was encountered that resulted
| in a substitution character of either ’3F’x (in EBCDIC
128 Messages
DSNH350I • DSNH385I
| DSNH350I E csectname column-name WAS | DSNH372I E csectname ONLY ONE ROWID, ROW
| IMPLICITLY OR EXPLICITLY | CHANGE TIMESTAMP, SECURITY
| REFERENCED IN A CONTEXT IN | LABEL OR IDENTITY COLUMN IS
| WHICH IT CANNOT BE USED | ALLOWED IN A TABLE
| Explanation: | Explanation:
| The ALTER, CREATE, or DECLARE TEMPORARY | An attempt was made to do one of the following
| TABLE statement is invalid for one of the following | actions:
| reasons: | v Create a table with more than one ROWID column.
| v A LOB, DECFLOAT, or XML column cannot be | v Add a ROWID column to a table that already has
| specified as a column of the primary key in a | one.
| PRIMARY KEY clause.
| v Create a table with more than one identity column.
| v A LOB, DECFLOAT, or XML column cannot be
| specified as a column of a UNIQUE KEY.
| v Add an identity column to a table that already has
| one.
| v A LOB, DECFLOAT, XML, or security label column
| cannot be specified as a column of a foreign key in a
| v Add a security label column to a table that already
| referential-constraint clause.
| has one.
System action:
| The proper ranges for SQL values are as follows:
| v 5.4E-79 to 7.2E+75 for FLOAT values
Processing continues.
| v -(1031 -1) to +(1031 -1) for DECIMAL values
User response: | v -2147483648 to 2147483647 for INTEGER values
Make both operands compatible character data types. | v -32768 to +32767 for small integer (SMALLINT)
Ensure that the table declaration is correct. | values
Severity: | v -9.999999999999999x10-383 to 9.999999999999999x10384
| for DECFLOAT(16) values
4 (warning)
| v -9.999999999999999999999999999999999x10-6143 to
| 9.999999999999999999999999999999999x106144 for
DSNH402I W csectname LINE nnnn COL cc | DECFLOAT(34) values
STATEMENT APPLIES name TO | v - 9223372036854775808 to +9223372036854775807 for
CHARACTER DATA | big integer (BIGINT) values
Explanation: System action:
The numeric operation or function name is used with a If the containing SQL statement is a declaration, it is
non-numeric operand. discarded. If the containing SQL statement is
System action: executable, it is replaced by host language statements
that will, if executed, set an error code in the SQLCA.
Processing continues.
User response:
User response:
Correct the number.
Make the operand numeric or use a character function.
Ensure that the table declaration is correct. Severity:
Severity: 8 (error)
4 (warning)
130 Messages
DSNH408I • DSNH449I
The corresponding SQL statement is replaced by host The statement cannot be executed.
language statementsthat will, if executed, set an error
User response:
code in the SQLCA.
Select a name for the function or distinct type that is
User response:
not reserved for system use.
Correct the syntax of the SQL statement. Refer to the
Severity:
SQL Reference forinformation on the EXTERNAL NAME
clause. 8 (error)
Severity:
DSNH473I E csectname LINE nnnn COL cc. A USER
8 (error)
DEFINED DATA TYPE CANNOT BE
CALLED THE SAME NAME AS A
| DSNH451I THE data-item DEFINITION IN THE SYSTEM PREDEFINED TYPE
| CREATE OR ALTER STATEMENT FOR (BUILT-IN TYPE).
| routine-name CONTAINS DATA TYPE
Explanation:
| type WHICH IS NOT SUPPORTED FOR
| THE TYPE AND LANGUAGE OF THE The name of a data type to be created has an
| ROUTINE unqualified name that is the same as a
system-predefined data type. This is not allowed.
| Explanation:
Adding delimiters does not make the name valid. The
| An error was found in the data-item part of the following names are restricted:
| CREATE or ALTER statement for routine-name. The
|| BIGINT DECIMAL REF
| statement contained an invalid data type, or it
| contained a distinct type which is based on the invalid | BINARY DECFLOAT ROWID
| data type. | BLOB DOUBLE SMALLINT
| BOOLEAN DOUBLE TIME
| System action:
| PRECISION
| The statement cannot be processed. | CHAR FLOAT TIMESTAMP
| Programmer response: | CHAR VARYING GRAPHIC VARBINARY
| CHARACTER INT VARCHAR
| Correct the specification of the routine and reissue the | CHARACTER INTEGER VARGRAPHIC
| CREATE statement. | VARYING
| Severity: | CLOB LONG XML
| VARCHAR
| 8 (error) | DATALINK LONG
| VARGRAPHIC
DSNH457I E csectname LINE nnnn COL cc. A | DATE NUMERIC
FUNCTION OR DISTINCT TYPE | DBCLOB REAL
CANNOT BE CALLED name SINCE IT | DEC ROWID
IS RESERVED FOR SYSTEM USE. |
Explanation: System action:
The user-defined function or distinct type cannot be The statement cannot be executed.
created or referenced because the name selected is
reserved for use by the system. User response:
A number of names used as keywords are reserved for Correct the statement to use another identifier for the
system use. These names may not be used as name of the new user-defined type.
user-defined functions or distinct-type-names, even if Severity:
they are delimited identifiers. These names are:
8 (error)
= < > >= <=
<> ¬= ¬> ¬>
ALL AND ANY BETWEEN DISTINCT DSNH487I E csectname LINE nnnn COL cc object-type
EXCEPT EXISTS FALSE FOR FROM object-name ATTEMPTED TO EXECUTE
IN IS LIKE MATCH NOT AN SQL STATEMENT WHEN THE
NULL ONLY OR OVERLAPS SIMILAR
DEFINITION OF THE FUNCTION OR
SOME TABLE TRUE TYPE UNIQUE
UNKNOWN PROCEDURE DID NOT SPECIFY THIS
ACTION
System action:
Explanation:
132 Messages
DSNH490I • DSNH520I
System action: The identified keyword is not permitted. The keyword list
is a list of the keywords that are permitted in this
The statement cannot be executed. context. The combinationof privileges requested on a
GRANT or REVOKE statement is not allowed.
User response:
Theauthorities must all be of one type and consistent
Remove the DESCRIBE CURSOR statement. Issue a with the form of GRANTor REVOKE. REVOKE
DESCRIBE of the statement used to define the declared UPDATE(column list) is not allowed; only REVOKE
cursor. UPDATE ispermitted.
Severity: System action:
8 (error). The containing SQL statement is replaced by host
language statements thatwill, if executed, set an error
code in the SQLCA.
| DSNH527I WARNING: THE PRECOMPILER OR
| DB2 COPROCESSOR ATTEMPTED TO User response:
| USE THE DB2-SUPPLIED DSNHDECP
Correct the syntax. If necessary, refer to chapter 2 of
| MODULE.
SQL Reference forthe correct syntax.
| Explanation:
Severity:
| The DSNHDECP module that is supplied by DB2 is
134 Messages
DSNH558I • DSNH585I
DSNH586I E csectname LINE nnnn COL cc. THE DSNH590I E csectname LINE nnnn COL cc NAME
TOTAL LENGTH OF THE CURRENT name IS NOT UNIQUE IN ROUTINE
PATH SPECIAL REGISTER CANNOT routine-name
EXCEED 254 CHARACTERS.
Explanation:
Explanation:
Name name is a parameter, SQL variable, condition
The CURRENT PATH special register is defined as a name, or label in SQL procedure routine-name. name is
VARCHAR(254). The content of the string includes each not unique.
schema name delimited with double quotes and
System action:
separated from the next schema name by a comma. The
total length of the string of all schema names in the The statement cannot be processed.
CURRENT PATH cannot exceed 254 characters. A SET
CURRENT PATH statement causing this message User response:
would exceed this limit. Change the name to make it unique within the routine.
System action: Severity:
The statement cannot be executed. 8 (error)
User response:
Remove schema names to reduce the total length to fit DSNH599I W csectname LINE nnnn COL cc.
the 254 character maximum length. If all the schema COMPARISON FUNCTIONS ARE NOT
names are required, it may be necessary to consolidate CREATED FOR A DISTINCT TYPE
some user-defined functions so that fewer schema BASED ON A LONG STRING DATA
names are required for the CURRENT PATH. TYPE.
Severity: Explanation:
136 Messages
DSNH628I • DSNH630E
trigger definition. A column cannot be specified in v A CREATE FUNCTION statement contains both a
more than one ALTER TABLE clause except if it is SOURCE clause and a RETURNS TABLE clause.
specified in an ALTER COLUMN clause and ADD v A CREATE FUNCTION statement contains both a
CHECK CONSTRAINT clause. SOURCE clause and a clause used to define an
System action: external function (EXTERNAL, LANGUAGE, NO
SQL).
The statement cannot be executed.
| v A CREATE or ALTER FUNCTION statement contains
User response: | a clause other than the CAST FROM clause for
| external scalar functions.
Correct the CREATE statement to specify unique names
for each of the columns of the index, table, view, or the v A CREATE or ALTER PROCEDURE statement
columns in the UPDATE OF clause of a trigger attempts to use the NO WLM ENVIRONMENT and
definition. Correct the ALTER statement to specify PROGRAM TYPE SUB options. When NO WLM
unique names for each of the ALTER COLUMN ENVIRONMENT is used, then PROGRAM TYPE
clauses. MAIN must also be used.
v A CREATE or ALTER PROCEDURE statement
This error can also occur on CREATE TABLE when a attempts to use both NO WLM ENVIRONMENT and
column list of a PRIMARY KEY, FOREIGN KEY, or either USER or DEFINER for EXTERNAL SECURITY.
UNIQUE clause contains two or more occurrences of When NO WLM ENVIRONMENT is used, then
the same column name. PARAMETER STYLE must be either GENERAL or
Severity: SIMPLE CALL WITH NULLS.
v A CREATE or ALTER PROCEDURE statement
8 (error)
contains both a LANGUAGE REXX™ clause, and a
PARAMETER STYLE DB2SQL or PARAMETER
DSNH628I E csectname LINE nnnn COL cc STYLE JAVA clause.
MUTUALLY EXCLUSIVE CLAUSES v An ALTER TABLE statement contains both an
HAVE BEEN SPECIFIED. ALTER COLUMN clause and a VALIDPROC clause.
Explanation: | v A CREATE or ALTER INDEX statement attempted to
| specify either CLUSTEPS, PARTITION BY, or both,
Mutually exclusive clauses were specified in one or
| for an XML index or an extended index.
more of the following ways:
| v A CREATE INDEX statement contains both
v A CREATE TABLESPACE statement contains both
| GENERATE KEY USING and a column specified as
the SEGSIZE and NUMPARTS clauses
| ASC or DESC.
v A CREATE TABLESPACE statement contains both
v An ALTER TABLE statement contains both an
the SEGSIZE and LARGE clauses.
ALTER COLUMN clause and a clause other than the
v A CREATE TABLESPACE statement contains both check constraint clause.
the SEGSIZE and MEMBER CLUSTER clauses.
| v A CREATE or ALTER INDEX statement attempted to
v A CREATE or ALTER TABLESPACE contains both | specify either CLUSTER, PARTITION BY, or both, for
the LOCKPART YES and LOCKSIZE TABLESPACE | an XML index or an extended index.
v A ’column-definition’ contains both NOT NULL and | v A CREATE INDEX statement contains both a
DEFAULT NULL clauses. | GENERATE KEY USING clause, and a column
v A ’column-definition’ contains both FIELDPROC and | specified as ASC or DESC.
DEFAULT clauses.
System action:
v A select-statement contains both the update-clause
and the FOR FETCH ONLY clause. The statement was not executed.
v An ALTER TABLE statement contains both a DROP Programmer response:
CONSTRAINT clause and either a DROP FOREIGN
Change the options specified in the statement and
KEY clause or a DROP CHECK clause.
reissue the statement.
v A CREATE or ALTER TABLESPACE contains both
the LOCKPART YES and LOCKSIZE TABLESPACE Severity:
v A CREATE TRIGGER statement specifies more than 8 (error)
one correlation name for OLD, NEW, OLD_TABLE,
or NEW_TABLE. Each of these correlation specific
can appear no more than once in the CREATE DSNH630E E csectname LINE nnnn COL cc THE
TRIGGER statement. WHERE NOT NULL SPECIFICATION
IS INVALID FOR TYPE 1 INDEXES
v A CREATE FUNCTION statement contains both a
CAST FROM clause and a SOURCE clause. Explanation:
138 Messages
DSNH684I • DSNH741I
The SQL statement cannot be executed. This message is issued by the following CLIST: DSNH
System programmer response: System action:
Correct the SQL statement. Refer to chapter 2 of SQL Processing continues as requested.
Reference fo rinformation about writing literal lists.
User response:
Severity:
This phase is complete. If there are errors, other
8 (error) messages are produced. The next phase requested
begins. The order of the phases is:
DSNH739I E csectname LINE nnnn COL cc. CREATE 1. PLI Macro Pass
FUNCTION function-name FAILED 2. Precompiler
BECAUSE FUNCTIONS CANNOT
3. CICS Command Translator
MODIFY DATA WHEN THEY ARE
PROCESSED IN PARALLEL. 4. Bind Package
5. Bind Plan
Explanation:
6. ASM, ASMH, C (C/370 Compiler), COBOL,
The function cannot be created because ALLOW COBOL2, FORTRAN, PLI
PARALLEL and MODIFIES SQL DATA were both
7. Prelink
specified explicitly or implicitly. A function cannot be
parallelized if it modifies data. 8. Link
9. Run
System action:
Severity:
The statement cannot be executed.
retcode
User response:
Specify DISALLOW PARALLEL or change the
DSNH741I process1(NO) IMPLIES THAT process2
MODIFIES SQL DATA to NO SQL, CONTAINS SQL or
CANNOT BE RUN
READS SQL DATA.
Explanation:
Severity:
An inconsistent processing set was specified. An earlier
8 (error)
phase and a later phase were requested, but not the
intermediate step needed to process data between
DSNH740I xxxxxx phase FINISHED, RC = retcode, them. For example, requesting the precompile and the
LISTING IN data-set link edit without the compile produces this error.
Values for process1 are PRECOMP, CICSXLAT,
Explanation:
COMPILE, LINK, or BIND. Values for process2 are
The DSNH INST phase completed with return code COMPILE, LINK, or RUN.
retcode. The phase is one of the following:
This message is issued by the following CLIST: DSNH
v PLI Macro Pass
System action:
v Precompiler
v CICS Command Translator process2 is not performed, but other processing is done.
v Bind Package User response:
Specify a consistent combination of processing. allowed. If prompting is not allowed, for example in
Application program preparation needs to run all the batch or when PROFILE NOPROMPT was entered, the
steps to provide a correct application program. The CLIST terminates.
process does allow beginning or ending steps to be run
User response:
at a different time. See message DSNH740I for the
required step order. Specify an INPUT name. See message DSNH753I.
Severity: Severity:
4 (warning) 0 (successful)
DSNH750I INVALID DATA SET: clist-keyword DSNH753I ENTER INPUT DATA SET NAME
clist-keyword-parameter
Explanation:
Explanation:
The CLIST is requesting the name of the input data set.
The data set name specified on the
clist-keyword-parameter contains unbalanced parenthesis. This message is issued by the following CLIST: DSNH
System action: The system waits for user to enter data set name or for
the CLIST to be terminated.
The CLIST is terminated.
User response:
User response:
Enter the name of the data set. Do not specify the
If a member name is to be associated with the specified parameter or command, but just enter the name of the
data set, the member name must be enclosed in data set. The standard TSO prefixing will be done if the
parentheses. data set name is not entered within apostrophes.
Severity: Severity:
8 (error) 0 (successful)
DSNH751I clist ERROR IN parameter VALUE value DSNH754I clist OUTNAME PARAMETER name
MUST NOT CONTAIN SPECIAL
Explanation:
CHARACTERS
The specified CLIST keyword parameter does not have
Explanation:
an acceptable value.
The DSNH and DSNHC CLISTs, clist, use the
System action:
OUTNAME parameter to build names for a number of
The CLIST processing is terminated. data sets that are passed from phase to phase. These
names are prefixed by an authorization ID or TSO
User response:
prefix value and have a number of suffixes. For this
Refer to the DSNH (TSO clist) section in Command reason, OUTNAME parameter name must not contain
Reference for a complete list of the supported CLIST special characters. It can contain a period or national
parameters and their associated values. characters. It cannot have apostrophes to specify a
single data set name.
Severity:
System action:
8 (error)
The CLIST is terminated.
140 Messages
DSNH755I • DSNH759I
Severity: 8 (error)
8 (error)
DSNH758I HOST(host-language) IS NOT
PERMITTED WITH RUN(IMS) OR
DSNH756I clist PRINT PARAMETER name MUST RUN(CICS)
NOT CONTAIN SPECIAL
CHARACTERS Explanation:
names assigned during processing. In general, SYS is a reserved prefix for names. The only
exceptions to this rule include the following conditions:
Problem determination:
| v SYSADM and SYSTOOLS are valid schema names.
The location of the messages describing the prior errors
v SYSPROC is a valid schema name for stored
depends upon the values of the TERM and PRINT
procedures.
parameters. The messages can be directed to the
terminal, to preallocated data sets, or to data sets | v SYSIBM is a valid schema name for a stored
dynamically allocated during CLIST processing. | procedure when the current application process has
| the SYSADM or SYSCTRL privilege.
If TERM(NONE) PRINT(NONE) was specified, the
| v SYSTOOLS is a valid schema name when the current
messages are not available. Execute the CLIST again
| application process has the SYSADM or SYSCTRL
and specify a location for the error messages.
| privilege.
To find the documentation, note the immediately
preceding DSNH740I message for the location of the This message is also issued if an attempt is made to
listings. If the ’LISTING IN data-set’ portion of the grant the CREATEIN, ALTERIN or DROPIN privileges
message is missing, specify a PRINT data set, on a schema with the SYS prefix. The same exceptions
SOURCE(YES) and XREF(YES), and execute the CLIST apply to the grant.
again. Use TERM(TERM) to direct error messages to
your terminal. These listings and execution of the This condition is similar to the condition reported in
DSNH CLIST are required for problem diagnosis. SQLCODE -20074.
If the error is in the CLIST or the error location is User response:
CLIST CHECKING, use CONTROL(SYMLIST) to
produce a detailed trace of the CLIST execution and Select a name that does not start with a reserved prefix.
provide the trace listing. Severity:
Check for DSNH751I messages that describe the error. 4
Severity:
retcode DSNH867I E csectname LINE nnnn COL cc.
INVALID SPECIFICATION OF A
ROWID COLUMN
DSNH760I PRELINK OPTION INVALID WITH
HOST LANGUAGE (host-language) Explanation:
142 Messages
DSNH901I • DSNH902I
| 003 Error in a storage suballocation request. | 002 A miscellaneous error occurred on conversion
| v This error might have occurred because of
| from the source CCSID to CCSID 1208.
| storage constraints when building the | 003 No conversion is defined from the source
| DBRM entry for the SQL statement or | CCSID to CCSID 1208.
| because the SQL statement exceeds the DB2
| maximum statement length. | 004 A miscellaneous error occurred on conversion
| from the source CCSID to CCSID 1208.
| 004 Error in pointer structures.
| 005 Substitution occurred on conversion from
| 005 On BIND or REBIND, a host variable was not | CCSID 1208 to the source CCSID.
| found.
| 006 The internal buffer is too small for conversion
| 006 Unexpected value for parser option. | from CCSID 1208 to the source CCSID.
| 007 The size of a DBRM entry exceeds the | 007 An invalid code point was found during
| maximum size. | conversion from CCSID 1208 to the source
| 008 Internal conversion error.
| CCSID.
| v An error occurred when converting a | 008 Another type of invalid input character was
| timestamp version-id. | found during conversion from CCSID 1208 to
| the source CCSID.
| System action:
| 009 A miscellaneous error occurred during
| The precompiler or coprocessor is terminated | conversion from CCSID 1208 to the source
| immediately. | CCSID.
| System programmer response: | 010 No conversion is defined from CCSID 1208 to
| If you suspect an error in DB2, refer to Part 2 of | the source CCSID.
| Diagnosis Guide and Reference for information on | 011 A miscellaneous error occurred during
| identifying and reporting the problem. | conversion from CCSID 1208 to the source
| User response: | CCSID.
| Diagnosis Guide and Reference for information on | more than 1000 source lines and contains a LOB
| identifying and reporting the problem. | variable declaration.
| User response: System action:
| Notify the system programmer. Processing continues.
| Problem determination: User response:
| A copy of the application program source and the Split the DCL statement into two parts.
| print-out is useful (specify SOURCE and XREF).
Severity:
| Severity:
8
| 16 (unrecoverable error)
DSNH4408I E csectname LINE nnnn COL cc THE
DSNH904I csectname U STORAGE OVERFLOW VALUE IS NOT COMPATIBLE WITH
THE DATA TYPE OF ITS TARGET
Explanation:
Explanation:
More storage is needed, but could not be obtained
during precompiler/parser execution. The data type of the value to be assigned to the
parameter or SQL variable is incompatible with the
System action:
declared data type of the assignment target. Both must
The precompiler/parser is terminated immediately. be:
v Numerals
System programmer response: v Characters
The storage required for the current statement could v Graphics
not be acquired or exceeds the maximum for a single v Dates or character
request. If the region size is being used completely, v Times or character
check whether the region can be expanded. If it cannot v Timestamps or character
be expanded, the SQL statement is too large to be v Row ID’s
processed. v The same distinct types
Explanation: 8 (error)
144 Messages
DSNH4701I • DSNH4762I
| If the SQL options are required, upgrade to a newer | which is not taken by the COBOL compiler.
| level of the compiler.
| System action:
| Refer to message DSNH4760I in the output listing and
| the DB2 Program Directory for information on selecting | Processing continues.
| the correct level of the compiler to use. | User response:
| If the SQL options are not required, remove them. | Specify the APOST precompiler options, and
| Severity: | precompile the application again. There is no need to
| modify the COBOL source.
| 4 (warning)
| Severity:
146 Messages
DSNH4780I • DSNH4783I
| DSNH4784I E csectname DSNHDECP IS FOR DB2 DSNH4787I E csectname LINE nnnn COL cc
| VERSION ″dsnhdecp-version″ BUT RESIGNAL STATEMENT NOT
| product-name IS FOR DB2 VERSION WITHIN A HANDLER
| ″dsnhdecp-version″
Explanation:
| Explanation:
The RESIGNAL statement can only be used inside
| The release information from the given DSNHDECP condition handlers.
| does not match the current level of the DB2
System action:
| precompiler or SQL coprocessor.
The statement cannot be processed.
| System action:
User response:
| The precompiler or SQL coprocessor is terminated.
Remove the RESIGNAL statement or use a SIGNAL
| Programmer response:
statement instead.
| Ensure that a DSNHDECP data-only load module for
Severity:
| the correct DB2 version is available to the precompiler
| or SQL coprocessor, and that DSNHDECP load module 8 (error)
| is the one that DB2 finds first. DB2 searches for the
| DSNHDECP module in the following places, and in the
| following order: DSNH4788I csectname CCSID ccsid FOR PROGRAM
SOURCE CODE IS NOT SUPPORTED
| v The STEPLIB concatenation for the precompile or
| compiler step for SQL coprocessor Explanation:
| v The JOBLIB concatenation for the job that includes | The DB2 precompiler or DB2 coprocessor does not
| the precompile step or compiler step for SQL | accept input source code with the specified CCSID. The
| coprocessor | rules for the CCSID are:
| v The system link list | v When source code for an external SQL procedure is
| Severity: | precompiled, the CCSID must be a Latin-1 EBCDIC
| CCSID.
| 12 (severe error) | v For other uses of the DB2 precompiler or DB2
| coprocessor, the CCSID must be an EBCDIC CCSID.
DSNH4785I E csectname LINE nnnn COL cc THE System action:
DECLARATION OR USE OF THE
SQLSTATE OR SQLCODE VARIABLE The precompiler or DB2 coprocessor terminates.
IS NOT VALID
User response:
Explanation:
Specify an EBCDIC CCSID.
The declaration or use of an SQLCODE or SQLSTATE
Severity:
special variable is not valid for one of the following
reasons: 16 (unrecoverable error)
v SQLSTATE is declared with a data type other than
CHAR(5). | DSNH4789I csectname SQL PROCESSING OPTION
v SQLCODE is declared with a data type other than | ″option″ IS IGNORED
INTEGER.
| Explanation:
v NULL is assigned to SQLCODE or SQLSTATE.
| When using the DB2 precompiler or the DB2
System action: | coprocessor, the SQL processing option option is
The statement cannot be processed. | ignored.
User response: | If option is GRAPHIC or NOGRAPHIC, the option has
| no effect. For the DB2 precompiler, these options are
Declare SQLSTATE only as CHAR(5) and SQLCODE | superseded by the CCSID option. For the DB2
only as INTEGER. Do not assign the null value to | coprocessor, these options are superseded by a process
SQLCODE or SQLSTATE. | that the coprocessor uses to determine the CCSID.
Severity: | System action:
8 (error) | Processing continues.
| User response:
148 Messages
DSNH4920I • DSNH5034I
| Make sure the correct CCSID is provided to the v the host-variable-array or host indicator variable
| precompiler or coprocessor. array do not contain structures that are not
permissible. The only structures that may be defined
| If the CCSID provided is a single-byte CCSID, then
in a host-variable-array are those that are used to
| x’0E’ and x’0F’ characters are not interpreted as
define variable length string host variables.
| shift-out and shift-in characters surrounding DBCS
| characters. If the CCSID provided is a mixed CCSID, See the Application Programming and SQL Guide for more
| then x’0E’ and x’0F’ characters are interpreted as language-specific information on how to define the
| shift-out and shift-in characters surrounding DBCS host-variable-arrays in a program.
| characters.
| Options for SQL statement processing (Application DSNH5033I DECLARE VARIABLE NOT VALID
| Programming Guide) FOR variable
Explanation:
DSNH4920I E csectname TOKEN ID ARRAY TOO
SMALL Host variable variable specified in a DECLARE
VARIABLE statement is not valid. The DECLARE
Explanation: VARIABLE statement occurs after any SQL statement
The DB2 coprocessor needs more token identifier array (in a COBOL or FORTRAN application program) or
entries than the coprocessor allocated. after a DECLARE CURSOR statement (in an
application program in any other host language), where
System action: the SQL statement and the DECLARE VARIABLE refer
Control is returned to caller with no other action taken. to the same variable.
Allocate a larger token identifier array and make the The statement cannot be processed.
call to SQLGCMPL again. User response:
Severity: Ensure that the DECLARE VARIABLE occurs before the
8 (error) use of the host variable in an SQL statement in the
application.
The host variable variable was specified in two or more The source program cannot be precompiled.
DECLARE VARIABLE statements, or was specified two User response:
or more times in one DECLARE VARIABLE statement.
A host variable can be specified once at most in a Specify the TWOPASS precompiler option or, for
DECLARE VARIABLE statement. assembler, do not specify the ONEPASS precompiler
option.
System action:
Severity:
The statement cannot be processed.
8 (error)
User response:
Specify the host variable at most once in a DECLARE DSNH20008I UNSUPPORTED OPTION keyword
VARIABLE statement. SPECIFIED
Severity: Explanation:
8 (error) keyword is a deprecated feature that was supported in
releasesprior to DB2 Version 9.1, and is no longer
DSNH5036I CCSID VALUE OUT OF RANGE supported.
150 Messages
DSNH20061I • DSNH20289I
| You can use the same built-in data types for SQL 8 (error)
| procedure parameters or variables that you can use for
| the CREATE TABLE statement, except these:
DSNH20129I E csectname LINE nnnn COL cc LOCAL
| v LONG VARCHAR SPECIAL REGISTER IS NOT VALID
| v LONG VARGRAPHIC AS USED
| v ROWID Explanation:
| v distinct type
| The CURRENT PACKAGE PATH special register and
System action: | local special registers, such as CURRENT SERVER and
| CURRENT PACKAGESET, cannot be used in an
The statement cannot be executed.
| expression that is on the right side of a SET
User response: | host-variable assignment statement.
| Change the syntax to specify one of the supported data The only valid uses of these special registers in a SET
| types. Instead of a LONG VARCHAR data type, use a host-variable assignment statement are:
| VARCHAR data type with an explicit length. Instead of v SET :hv = CURRENT SERVER;
| a LONG VARGRAPHIC data type, use a
v SET :hv = CURRENT PACKAGESET;
| VARGRAPHIC data type with an explicit length.
v SET :hv = CURRENT PACKAGE PATH;
Severity:
System action:
8 (error)
The statement cannot be executed.
1 No PIPI token. return-code is the return code A stacked diagnostics area is only accessible from
from the CEEPIPI(init_sub) call. within a handler in a native SQL routine.
2 CEE could not be loaded. return-code is the This error can occur when the STACKED keyword is
return code from the CEEPIPI(add_entry) call. specified in a GET DIAGNOSTICS statement outside of
an SQL procedure.
3 PIPI would not terminate. return-code is the
return code from the CEEPIPI(term) call. System action:
152 Messages
Chapter 7. DSNI messages
Message identifiers that begin with DSNI communicate information about the data
manager.
User response:
DSNI001I RESTART HAS BEEN DEFERRED
REASON reason TYPE type NAME Correct the resource unavailable problem and reissue
name the -START command.
Explanation:
DSNI003I csect-name UNABLE TO STOP OBJECT
Restart could not be performed for one or more pages
TYPE object-type OBJECT NAME
of the resource identified by type and name. Those
object-name REASON reason TYPE type
pages are placed in the logical page list (LPL) and
NAME name
restart for those pages is deferred. The reason code
explains why restart was not performed. Explanation:
Refer to Appendix C, “Resource types,” on page 807 for The identified object could not be stopped because a
an explanation of resource type codes. resource required to perform the stop was unavailable.
The object could be a database, a table space, an index
System action:
space, or a partition within a table space or an index
DB2 restart continues. Pages for which restart activity space.
was not performed are put into the LPL.
The ’object-type’ identifies the type and ’object-name’
User response: identifies the name. If the DB2 catalog is unavailable,
’object-type’ contains binary zeros and ’object-name’
Correct the problem indicated by the reason code. Then
contains blanks.
use the START DATABASE command or the RECOVER
utility to remove the pages from the LPL. The resource that was unavailable is identified by
’type’ and ’name’. The ’type’ code identifies the type of
the resource as well as the format and content of the
DSNI002I csect-name UNABLE TO START OBJECT
resource, ’name’.
TYPE object-type OBJECT NAME
object-name REASON reason TYPE type Refer to Appendix C, “Resource types,” on page 807 for
NAME name an explanation of resource type codes. The ’reason’
contains the reason code explaining why the resource
Explanation:
was unavailable.
The resource identified could not be started because it
System action:
was unavailable. The resource could be a database, a
table space, an index space, or a partition within a table The specified database, space, or partition is not
space or an index space. The ’object-type’ identifies the stopped and remains in the current state. If there are
type. The ’object-name’ identifies the name. If the DB2 other databases, spaces, or partitions to be stopped,
catalog is unavailable, ’object-type’ contains binary they are processed normally.
zeros and ’object-name’ contains blanks.
User response:
The resource that was unavailable is identified by
Correct the resource unavailable problem and reissue
’type’ and ’name’. The ’type’ code identifies the type of
the -STOP command.
the resource as well as the format and content of the
’name’.
DSNI004I RESOURCE HAS BEEN STOPPED
Refer to Appendix C, “Resource types,” on page 807 for
TYPE type NAME name
an explanation of resource type codes. The ’reason’
contains the reason code explaining why the resource Explanation:
was unavailable.
The resource identified by TYPE and NAME could not
System action: be opened/closed, initialized, or was found to be in an
inconsistent state. The resource has been ’stopped’ by
The specified database, space, or partition is not started
DB2. If an open error occurred during DB2 startup,
and remains in its current state. If there are other
restart processing for the resource was deferred.
databases, spaces, or partitions to be started, they are
processed normally. TYPE and NAME identify the resource that has been
stopped. The TYPE code identifies the type of the Correct the problem that is specified by the reason
resource as well as the format and content of the code, and reissue the -START command.
resource, NAME.
Refer to Appendix C, “Resource types,” on page 807 for DSNI006I csect-name ASYNCHRONOUS GRECP
an explanation of resource type codes. OR LPL RECOVERY IN PROGRESS
FOR function - ID id TYPE type NAME
System action:
name
The database, table space or index space is stopped by
Explanation:
DB2.
This message is issued in response to a START
User response:
DATABASE command, AUTOMATIC GRECP
Previous messages provide information to allow you to RECOVERY, or AUTOMATIC LPL RECOVERY function
determine the cause of the problem and the method of under the following conditions:
correcting it. Refer to them, and correct the problem. v When the object (table space or index space), which
Then restart the database, table space, or index space is identified by type and name, had group buffer pool
using the -START command; and invoke the recovery pending (GRECP) or logical page list (LPL)
application again. status, and
v Recovery was triggered.
DSNI005I csect-name LPL OR GRECP RECOVERY
CANNOT BE DONE FOR function - ID The values for function could be START DATABASE
= id OBJECT TYPE object-type OBJECT COMMAND, AUTOMATIC GRECP RECOVERY, or
NAME object-name REASON reason TYPE AUTOMATIC LPL RECOVERY.
type NAME name
id is a decimal number that represents the recovery
Explanation:
function.
The resource that is identified could not be recovered
during a recovery function that is identified by Refer to Appendix C, “Resource types,” on page 807 for
function_id because of problems during LPL or GRECP an explanation of resource type codes.
recovery. The resource could be a table space, an index
space, or a partition within a table space or index System action:
space. object-type identifies the type of resource. The object is started. Also, GRECP or LPL recovery is
object-name identifies the name of the resource. initiated. During LPL or GRECP recovery process,
The resource that could not be recovered is identified message DSNI022I might be issued periodically to
by type and name. The type code identifies the type of indicate the recovery status. If the recovery completes
the resource, as well as the format and content of name. successfully, message DSNI021I will appear at the end
reason contains the reason code explaining why the of recovery. Otherwise, message DSNI005I will indicate
resource could not be recovered. the error.
154 Messages
DSNI008I • DSNI011I
Notify the system programmer. See the System Programmer Response section of the
abend reason code specified in this message.
156 Messages
DSNI014I • DSNI017I
The job abends with reason code 00C90101 after this 8 (error)
message appears.
Operator response: DSNI017I RESOURCE TYPE type NAME name IS
INCONSISTENT DUE TO ONE OR
Collect the console output from the system on which MORE PENDING STATES
the job was run for the period of time spanning the
failure. Save this output for use in problem Explanation:
determination. There are two possible reasons for this message:
System programmer response: 1. The header page of a table space, index, or partition
belonging to a database defined as ROSHARE
See abend reason code 00C90101 for more information. OWNER could not be marked as consistent during
User response: the processing of the STOP DATABASE command
because one or more of the following was true:
Notify the system programmer.
v The table space, index, or partition is in recovery
Problem determination: pending status.
In general, the data in these pages is fine. However, if v The table space, index, or partition is in check
problems are reported that repeatedly involve the same pending status.
pages or if the same pages are reported by other v The table space, index, or partition has pages in
abends, you might want to analyze the set of pages the logical page list (LPL).
involved. v The table space, index, or partition status has a
If you suspect an error in DB2, refer to Part 2 of utility in progress (UTUT status on the output
Diagnosis Guide and Reference for information on from a DISPLAY DATABASE command).
identifying and reporting the problem. v The table space, index, or partition has a utility in
progress that allows read-only access (UTRO on
the output from a a DISPLAY DATABASE
DSNI015I OBJECT name IS ALREADY STARTED
command).
FOR RW ACCESS. THE OBJECT WILL
REMAIN STARTED FOR RW ACCESS v An I/O error range exists.
2. A retained lock is held on the table space, index, or
Explanation:
partition. The retained lock could be signifying a
The -START DATABASE command with the pending status.
If the STOP DATABASE command was issued without This message is informational only.
specifying the SPACENAM parameter, then one or
System action:
more of the conditions stated above is true for one or
more table spaces, indexes, or partitions in the specified The object is not stopped.
database.
Severity:
System action:
0 (informational)
For case 1, if the STOP DATABASE command was
specified with the SPACENAM parameter, the table
space, index, or partition is stopped. DB2 does not DSNI020I csect-name UNABLE TO DRAIN
allow access to an inconsistent table space, index, or RESOURCE TYPE type NAME name.
partition by any ROSHARE READ system. WILL RETRY DRAINING THE
RESOURCE.
For case 2, no access to an inconsistent table space,
index, or partition is allowed until the retained lock is Explanation:
released by the failed system at completion of its The resource identified by ’type’ and ’name’ could not
restart. be drained. The ’type’ code identifies the type of
User response: resource as well as the format and content of the
resource ’name’. The drain request is made again for
Issue a DISPLAY DATABASE command to display the this resource.
status of the object in question. Resolve the pending
states and then reissue the STOP DATABASE command Refer to Appendix C, “Resource types,” on page 807 for
to ensure that the consistency indicator is reset. an explanation of resource type codes.
158 Messages
DSNI023I • DSNI028I
This informational message is issued during the Fast exceeds a defined threshold (LOCKMAX) for the
Log Apply process. log-records indicates the number of tablespace.
log records that have been applied during the Fast Log
name The name of the escalated resource. The
Apply process. fla-buffers indicates the number of
format of name depends on the type of table
buffers used by the Fast Log Apply process.
space. For simple or partitioned table spaces,
Severity: the format is database-name.tablespace-name. For
a segmented table space, the format is
0 (informational)
creator-name.table-name (or DBID.OBID of the
table).
DSNI029I csect-name THE FAST LOG APPLY
state The lock state (after escalation) of the escalated
PROCESS IS ACTIVE AND THE
resource.
AVAILABLE ssnmDBM1 STORAGE IS
bytes BYTES id1 The name of the executing plan associated
with this thread.
Explanation:
id2 The name of the executing package (if any)
This informational message is issued during the Fast
associated with this thread.
Log Apply process for member ssnm. There is sufficient
storage for the Fast Log Apply process to continue, and id3 The statement number of the executing SQL
the remaining amount of available storage is displayed statement associated with this plan.
in hexadecimal as bytes.
id4 The correlation identifier of the thread
Severity: associated with the escalated resource.
0 (informational) id5 The connection identifier of the thread
associated with the escalated resource.
DSNI030I csect-name BACKOUT PROCESSING IS id6 The logical-unit-of-work identifier of the
CONTINUING BEYOND THE thread associated with the escalated resource.
REQUESTED LIMIT DUE TO
id7 Thread Info - the primary authorization_id
CATALOG OR DIRECTORY ACTIVITY
associated with the thread.
OF UR urid.
id8 Thread Info - Work station name of the end
Explanation:
user’s work station. An asterisk (*) indicates
The number of log records requested to be processed that it is not relevant to the thread or was not
during restart’s backward phase have been processed. provided by the client.
Under other circumstances further backout processing
id9 Thread Info - User-Id of the end user. An
would be postponed. However, because the indicated
asterisk (*) indicates that it is not relevant to
UR has catalog or directory updates that are not backed
the thread or was not provided by the client.
out yet (and because backout against catalog or
directory page sets cannot be postponed), backout id10 Thread Info - Application name of the end
processing is continuing. It will continue until this UR’s user’s application. An asterisk (*) indicates that
backout is complete. it is not relevant to the thread or was not
provided by the client.
System action:
id11 The collection-id of the package (if any).
Backout processing continues.
resource.
System action:
DSNI031I csect-name - LOCK ESCALATION HAS
OCCURRED FOR RESOURCE NAME = Escalation has occurred for the specified object
name, LOCK STATE = state, PLAN
NAME : PACKAGE NAME = id1:id2,
COLLECTION-ID = id11, STATEMENT DSNI032I csect-name CANCEL THREAD
NUMBER = id3, CORRELATION-ID = NOBACKOUT COMMAND FAILED
id4, CONNECTION-ID = id5, LUW-ID = FOR THE THREAD = token REASON =
id6, THREAD-INFO = id7:id8:id9:id10 reason
Explanation: Explanation:
Lock escalation balances concurrence with performance DB2 displays this message when it cannot grant a
by using page locks while a process accesses relatively request to cancel a thread without backing out data
few pages, then changing to table space or table locks changes. The reason code explains why the request was
when the process accesses a number of pages that rejected.
token Identifies a thread whose processing you
160 Messages
DSNI033I • DSNI038I
requested to cancel. The token is a 1- to errors were corrected and to reset the auxiliary warning
15-digit decimal number. state. The auxiliary warning state can also be reset
using the REPAIR utility with SET NOAUXWARN.
reason Indicates the reason why the command failed.
Severity:
System action:
0 (informational)
Processing terminates normally.
User response:
DSNI036I csect-name THE REAL-TIME
The reason code specifies the action to be taken. STATISTICS COLLECTION PROCESS
IS DISABLED
0 (informational) | Explanation:
| The data set for the database name, space name, and
| DSNI040I csect-name RESTORE SYSTEM UTILITY | partition number failed to be physically opened
| PROCESSING LOG RANGE FROM | through an -ACCESS DATABASE command with
| rba/lrsn xxxxxx TO yyyyyy | keyword MODE(OPEN). PART will be unavailable for
| non-partitioned data sets.
| Explanation:
| Operator response:
| This message periodically shows the progress of system
| level recovery made by the RESTORE SYSTEM utility. | Examine the console for other related error messages.
| In non-data sharing, the log range is RBA. In data | Ensure the bufferpool is activated, and then re-issue the
| sharing, the log range represents LRSN value. The | command. If the failure persists, then contact DB2
| value for xxxxxxxx is the RBA or LRSN value of the | Technical Support.
| current log record being processed and the yyyyyyyy
| value is the RBA or LRSN of the last log record to be
| DSNI046I module-name DBET ENTRY IN ERROR
| processed by the RESTORE SYSTEM utility.
| REASON reason-code ERQUAL
| System action: | erqual-value NAME object-name DBID dbid
| OBID obid LRSN lrsn-or-rba
| System Level Point-In-Time recovery continues.
| Explanation:
| Severity:
| An error occurred when DB2 processed a DBET
| 0 (informational) | exception state for a table space, index space, or
| partition of a partitioned object.
DSNI041I csect-name START ACCESS(FORCE) | REASON
CANNOT BE ISSUED AGAINST | Identifies the DB2 reason code that is listed in
TARGET obj-type obj-qual.obj-name part | the dump that accompanies this message.
DUE TO STOPPED UTILITIES ON
VERSION version-number. REQUEST IS | ERQUAL
REJECTED. | Identifies the specific abend in the CSECT that
| caused this message to be issued. This
Explanation: | information, and the reason code, is used by
The object cannot be started due to outstanding utilities | IBM Software Support to identify the cause of
on a different version. The status of the object is | the problem.
unchanged. | NAME Identifies the table space or index space that
version-number is the version on which the utility was | encountered the problem. A partition number
running. | is included where applicable.
obj-type is table space or index space. | LRSN Identifies the LRSN or RBA of the log record
| that was being processed when the error
obj-qual is the database name. | occurred. If no log record was being
obj_name is the table space or index space name. | processed, LRSN will be blank.
162 Messages
DSNI047I • DSNI048I
v If ’01’, this is the first entry of a and thus permit dual logging to proceed. If recovery is
multivolume data set. required, information from this message might be
v If ’11’, this is the middle entry of a required as input to the change log inventory
multivolume data set. (DSNJU003) utility.
v If ’10’, this is the last entry of a multivolume
data set. DSNJ005I ACTIVE LOG COPY n IS ACTIVE,
LOG IN DUAL MODE, STARTRBA=...
CATLG
An indicator to denote one of two conditions: Explanation:
v If ’NO’, the archive log data set is This message is sent when copy ’n’ of the log becomes
uncataloged. active after previously being flagged as inactive.
v If ’YES’, the archive log data set is STARTRBA is the RBA of the first byte of log data
cataloged. written on copy ’n’ after it was activated.
System programmer response:
The BSDS is automatically updated with the
information contained in this message; however, if None required. However, if recovery is required,
recovery is required, information from this message information from this message may be required as
may be required as input to the change log inventory input to the change log inventory (DSNJU003) utility.
(DSNJU003) utility.
DSNJ006I ALLOCATION FOR NEW ARCHIVE
DSNJ004I ACTIVE LOG COPY n INACTIVE, LOG DATA SET HAS BEEN
LOG IN SINGLE MODE, ENDRBA=... CANCELLED BY OPERATOR.
Explanation: Explanation:
This message is sent when the dual active logging This message is sent if the operator answers ’N’ to the
option is selected and copy ’n’ becomes inactive. A log WTOR message DSNJ008E.
copy becomes inactive when the next active log data
System action:
set is not ready when required. ENDRBA is the last
byte of log data written on copy ’n’. This is usually If the allocation is for copy 1 archive log data set,
caused by a delay in off-load. off-load terminates processing until the next time it is
activated. If copy 1 has already been allocated and this
System action:
request is for copy 2, off-load switches to single
The log is switched to single mode until the next data off-load mode for this data set only.
set for copy ’n’ is ready for logging.
If DB2 is shut down or abends while in single mode DSNJ007I csect-name OPERATOR CANCELED
with the ZPARM option still set for dual active data MOUNT OF ARCHIVE VOL SER=
sets, the previous state of the active log data sets volser
determines what happens when DB2 is started, as
Explanation:
follows:
v If fewer than two data sets are available (not flagged If the operator answers ’N’ to the WTOR message
as STOPPED) for each set of active logs, DB2 startup DSNJ009I, this message is issued. The variable ’volser’
terminates and message DSNJ112E is issued. is the volume serial of an archive log volume required
for the read request.
v If an active log data set is in NOTREUSABLE state,
DB2 can be started in single logging mode, but dual System action:
mode takes effect when the other active log data set
becomes available after offloading. The read request for the archive log volume fails. If the
request was issued with the COND=YES parameter,
Operator response: return code 12 and reason code 00D1032B are returned
to the requester. Otherwise, DB2 abends with reason
Execute an MVS Display System Requests command (D
code 00D1032B.
R,L for example) to ensure that there are no
outstanding requests that are related to the log off-load
process. Take the necessary action to satisfy any DSNJ008E nn OF mm ACTIVE LOGS ARE FULL.
requests, and permit off-load to continue. ssname NEEDS ARCHIVE SCRATCH.
REPLY Y WHEN DEVICE READY OR
System programmer response:
N TO CANCEL.
If the switch to single mode was caused by the lack of
Explanation:
a resource required for off-load, the necessary resource
should be made available to allow off-load to complete The installation has requested a WTOR before archive
166 Messages
DSNJ009E • DSNJ011I
log data set allocation. DB2 needs a scratch volume for archive read to reissue the message for the copy ’Z’
offloading an active log data set. ’ssname’ is the name copy 2 archive VOLSER with the same RBA range. A
of the DB2 subsystem. ’nn’ is the number of full active response of ’N’ to this second WTOR, or to the initial
log data sets. ’mm’ is the total number of active log WTOR for single archiving, causes the archive read
data sets. service task to fail with unpredictable results.
System action:
DSNJ010I csect-name INVALID RESPONSE. WTOR
The off-load task waits for the operator’s reply.
WILL BE REPEATED.
Operator response:
Explanation:
The operator has three options:
A WTOR was issued during archive data set allocation.
v Get a scratch volume ready, make sure there is an The user did not respond correctly to the message.
available unit for the volume, and reply ’Y’. DB2 Either ’Y’ or ’N’ must be entered.
then continues with the off-load.
System action:
v Determine from the number of active log data sets
available whether the off-load can be delayed until The original WTOR is repeated.
the next time an active log data set becomes full. If
Operator response:
the process can be delayed, then reply ’N’.
This response has two possible effects. Reply as indicated in the repeated message.
– If dual archive logging is in effect and this
allocation is for a copy 1 archive data set, the ’N’ DSNJ011I CONDITIONAL RESTART RECORD rrr
response delays the off-load process until the next CREATED AT .... WAS FOUND. REPLY
active log data set becomes full. Y TO USE, N TO CANCEL
– However, if the copy 1 archive data set has Explanation:
already been allocated and this request is for copy
2, the ’N’ response causes the off-load to switch to When the log manager was initialized, a conditional
single archive mode (the switch is for this data set restart control record was found in the bootstrap data
only). set. Both the record identifier (a 4 byte hexadecimal
v Defer giving a response. This causes off-load to wait number) and the creation time stamp (yy.ddd hh:mm)
before processing. However, because off-load is a are displayed to help identify the conditional restart
separate service task, the wait does not affect DB2 record which will be used. If you want a conditional
performance. restart using that record, reply ’Y’ to the message.
Otherwise, reply ’N’ and notify the system
programmer.
If offloading to DASD, an error has occurred
attempting to allocate an archive log data set. Reply ’Y’ System action:
to receive the error messages.
If ’Y’ is the response, DB2 is started conditionally, using
the record found. If ’N’ is the response, DB2 startup is
DSNJ009E ssname NEEDS VOL SER=nnnnnn. terminated.
REPLY Y TO CONTINUE OR N TO
CANCEL Operator response:
System action: If a normal restart of DB2 has failed and you have
created a conditional restart control record with the
The archive log read service task waits for the change log inventory (DSNJU003) utility, check whether
operator’s reply. This wait affects the agent for which the time and date in the message agree with when you
the log read was issued and any other agents that created that record. If they do, reply ’Y’ to the
might be waiting on the log read service task queue. outstanding WTOR. If they do not, reply ’N’ and
investigate the discrepancy.
Operator response:
Locate the requested volume, ensure that a device is
available, and reply ’Y’. DB2 continues with dynamic
allocation and then begins reading the log.
If dual archiving is in effect, a response of ’N’ causes
168 Messages
DSNJ015I • DSNJ030I
A ’Y’ reply will continue the conditional restart. A ’N’ DB2 continues processing. If statistics class 3 is active,
reply will terminate DB2 startup. IFCID 0335 is written. This message will be deleted
when the offload task completes the archive process.
Operator response:
System programmer response:
To continue this CSRONLY processing, reply ’Y’ to this
message. If you are not sure, contact the system This may be an indication that there may be an
programmer. outstanding tape mount request or that the offload task
may no longer be functioning. This situation can result
System programmer response: in a log-full situation if DB2 can not archive log data
sets when they fill. You should reply to any tape mount
The conditional restart control record will not be
requests and monitor offload activity very closely. You
deactivated at the end of the CSRONLY processing. To
can issue the -DISPLAY LOG command to display the
deactivate this record, either cancel this record or create
status of the offload task, and the -ARCHIVE LOG
a new record. Refer to part 2 of Diagnosis Guide and
CANCEL OFFLOAD command can be used to
Reference for more information.
terminate and restart the offload process.
Prior to terminating the offload task, obtain a dump of
DSNJ016E csect-name WARNING - SYSTEM
the DB2 MSTR address space for problem
CHECKPOINT PROCESSOR MAY
determination.
HAVE STALLED. LAST CHECKPOINT
WAS TAKEN date-time.
DSNJ020I csect-name RECEIVED REPLY OF N TO
Explanation:
msg-num. SUBSYSTEM STARTUP IS
While switching active log data sets, DB2 found that TERMINATED.
there has not been a system checkpoint taken since the
Explanation:
last time DB2 switched active log data sets. date-time is
the date and time of the last system checkpoint. There The operator chose to terminate DB2 startup by
should be at least one system checkpoint on each log answering ’N’ to ’msg-num’.
data set.
System action:
System action:
DB2 will not restart.
DB2 continues processing. If statistics class 3 is active,
IFCID 0335 is written. This message will be deleted Operator response:
when a system checkpoint is taken. To restart DB2, follow the ’operator response’ of
System programmer response: ’msg-num’.
of these log(s) is STOPPED in the bootstrap data set If the LUWID is an ’*’, it indicates that the thread
(BSDS). originated at this site.
System action: PLAN NAME and AUTHID further identify the thread
associated with the UR.
DB2 terminates with a dump.
If the thread’s creator included End User information,
Operator response:
then DB2 displays the End User’s ID, TRANSACTION
Notify the system programmer. NAME, and WORKSTATION NAME. Otherwise, these
fields will contain an ’*’.
System programmer response:
System action:
The log RBA range must be available for DB2 to be
recoverable. Correct previous errors and restore the DB2 continues processing. If statistics class 3 is active,
active log data set(s) that contain the RBA range IFCID 0313 is written. This message will be repeated
reported in the message. each additional time the threshold is reached.
v If the log data set(s) are recoverable, the active log System programmer response:
data set inventory in the BSDS must be modified to
reset the STOPPED status. Use the print log map Consult with the application programmer to determine
(DSNJU004) utility to obtain a copy of the BSDS log if this is a problem UR. See Part 4 of Administration
inventory. Next, use the change log inventory Guide for more information about problems caused by
(DSNJU003) utility to delete the active log data sets uncommitted URs.
marked STOPPED (use the DELETE statement), and If an application program caused the UR to reach its
then add them again (use the NEWLOG statement). threshold number of log records, you can use CANCEL
The starting and ending RBA for each active log data THREAD to cancel the UR. If you cancel an
set must be specified on the NEWLOG statement uncommitted UR, DB2 will undo the changes. The
when the log(s) are added back to the BSDS using amount of time required for this process depends on
the DSNJU003 utility. the amount of work done by the UR. The amount of
v If the log data set(s) are not recoverable, it is time required for this process depends on the amount
necessary to conditionally restart DB2. See Part 4 of of work done by the UR.
Administration Guide for additional information on
Programmer response:
conditional restart and recovering from log failures.
Ensure that the application commits frequently enough,
Problem determination:
or consult with your DB2 administrator about
Examine previous messages to determine the reason the decreasing the frequency of the check.
active log data set(s) are unavailable to DB2.
| DSNJ032I csect-name alert-lvl- APPROACHING
DSNJ031I csect-name WARNING - | END OF THE LOG RBA RANGE OF
UNCOMMITTED UR HAS WRITTEN | FFFFFFFFFFFF. CURRENT LOG RBA IS
nn LOG RECORDS - CORRELATION | xxxxxxxxxxxx
NAME = xxxxxxxxxxxx CONNECTION
ID = yyyyyyyy LUWID =
| Explanation:
LOGICAL-UNIT-OF-WORK-ID=token | The current log RBA is approaching the end of the log
PLAN NAME = xxxxxxxx AUTHID = | RBA range. xxxxxxxxxxxx is the current log RBA value.
xxxxxxxx END USER ID = xxxxxxxx | The current log RBA should not be allowed to advance
TRANSACTION NAME = xxxxxxxx | to the maximum value of FFFFFFFFFFFF. alert-lvl
WORKSTATION NAME = xxxxxxxx | indicates one of the following:
Explanation: | v WARNING is issued when the current log RBA
| reaches the F80000000000 value. DB2 will continue
This message indicates that a unit of recovery (UR) | processing.
reached the threshold number of log records written
without a COMMIT or ROLLBACK. This threshold was
| v CRITICAL is issued after the log RBA value reaches
defined during installation.
| FFFF00000000. If the message is issued during DB2
| restart, then processing will continue. Otherwise,
The value nn is cumulative, and indicates the number | DB2 will terminate with reason code 00D10251
of log records that were written since the beginning of
the UR.
| System action:
170 Messages
DSNJ050I • DSNJ072E
| after restart completes the recovery of the incomplete requirement is not met, this message is issued just prior
| units-of-recovery. DB2 can then be restarted in to the allocation of the archive log data set specified in
| ACCESS(MAINT) mode, in order to recover any the message.
| indoubt units-of-recovery, to -START any table spaces
System action:
| in a restricted state such as LPL or GRECP, or to
| -TERMINATE any utilities that are in progress. The archive log data set will be allocated using the
archive log prefix. However, the archive log DSN will
| Operator response:
not contain the date and time as the user requested.
| Notify the system programmer.
Operator response:
| System programmer response:
Notify the system programmer.
| Use the instructions in Resetting the log RBA (DB2
System programmer response:
| Administration Guide) to determine when to reset the
| log and how to reset it, depending on your data The ZPARM parameters for the log archive function
| sharing environment. must be changed. Specifically, the TSTAMP and
ARCPFXn fields are not consistent with one another.
For details concerning the course of action required to
DSNJ050I LOAD MODULE DSNJL003 DOES
eliminate this problem, refer to Part 2 of Installation
NOT HAVE RMODE(24) ATTRIBUTE
Guide under the DSNTIPA panel and DSN6ARVP
Explanation: macro subtopics.
The named load module was not link edited with the
required RMODE(24) attribute. DSNJ071I csect-name TIMER FAILURE CAUSED
TIMESTAMPING OF ARCHIVE dsname
System action:
TO BE BYPASSED
DB2 startup is terminated.
Explanation:
Operator response:
By way of a ZPARM parameter, the user has specified
Notify the system programmer of the failure. that the date and time of creation of an archive log data
set be included as part of the archive log data set name
System programmer response: (DSN). However an attempt to get the current date and
Verify that all installation and maintenance activities time from the system failed. This message is issued just
against this module were executed using SMP. Verify prior to the allocation of the archive log data set
that the JCLIN for SMP includes the correct RMODE specified in the message.
control statement, and that the Linkage Editor provided System action:
with the Data Facility Product (DFP) for the version of
MVS being used was invoked by SMP for the link The archive log data set will be allocated using the
edits. Correct the procedure or JCL which caused the archive log prefix. However, the archive log DSN will
error and rerun the necessary SMP jobs. not contain the date and time as the user requested.
Problem determination:
DSNJ072E ARCHIVE LOG DATA SET dsname
The MVS service aid AMBLIST provides Linkage Editor HAS BEEN ALLOCATED TO
module attributes in the summary section of the NON-TAPE DEVICE AND
LISTLOAD function output. CATALOGED. ZPARM CATALOG
OPTION OF ’NO’ HAS BEEN
DSNJ070I csect-name ARCHIVE LOG DSN PREFIX OVERRIDDEN.
NOT IN PROPER FORMAT TO Explanation:
RECEIVE TIMESTAMP DATA.
TIMESTAMPING OF dsnname By way of an archive log DSNZPARM parameter, the
BYPASSED user specified that all archive log data sets should be
uncataloged (CATLG=NO). However, DB2 requires that
Explanation: all archive log data sets allocated to nontape devices
By way of a ZPARM parameter, the user has specified must be cataloged. The archive log data set specified by
that the date and time of creation of an archive log data ’dsname’ has been allocated to a nontape device, and
set be included as part of the archive log data set name has thus been cataloged. The user’s DSNZPARM
(DSN). To accomplish this, the DB2 subsystem requires CATLG setting of ’NO’ has been overridden.
that the length of the archive log data set name prefix System action:
not exceed 19 characters if using the standard DATE
formate (YYDDD), or 17 characters if using the The archive log data set has been allocated to a
extended DATE format (YYYYDDD). If the prefix nontape device, and has been cataloged. The
172 Messages
DSNJ096E • DSNJ099I
174 Messages
DSNJ104I
2-byte error code (S99ERROR) followed by the 2-byte the NEWLOG statement must be the same as the
information code (S99INFO) from the SVC99 request name of the actual DB2 active log data set allocated
block. If the S99ERROR code indicates an SMS on DASD.
allocation error (97XX), then ’ssssssss’ contains
additional SMS reason code information obtained from
DSNJ104I csect-name RECEIVED ERROR STATUS
S99ERSN.Refer to z/OS MVS Programming: Authorized
nnn FROM macro-name FOR DSNAME
Assembler Services Guide for a description of the SVC99
dsname
codes. Additional SMS reason codes can be found in
z/OS DFSMSdfp Diagnosis Reference. Explanation:
For active log data sets, if the problem occurred during DB2 encountered an error while issuing macro
DB2 initialization, you can resolve the problem by ’macro-name’. Error status is the return code from the
either: specified macro.
v Resolving the error associated with the active log v For an OPEN of a VSAM data set, the return code in
data set as indicated by STATUS=keyword the error field of the access method services control
v Using AMS, providing another copy of the active log block is included in this message as the error status
data set value. Refer to the appropriate VSAM publication for
a definition of these values.
v Updating the BSDS with the change log inventory
(DSNJU003) utility v If the OPEN was for a non-VSAM data set, the error
status is zero.
v Restarting DB2.
v For MMSRV errors, error status contains the error
For archive log data sets: information returned by media manager services. If
an MMSRV CATUPDT failure occurs attempting to
v If the problem occurred during allocation with the
truncate an active log data set, the log data set will
intent to write the data set, no immediate action is
be unavailable to DB2 and the status of the log data
required. However, failure to resolve the SVC99 error
set will be flagged as ’STOPPED’ in the BSDS.
(indicated by the STATUS value in the message)
might eventually cause the available space in the v For VSAM OPEN and MMSRV errors, this message
active log to be exhausted (DSNJ111E), since all is preceded by an IEC161I message that defines the
future off-loads might fail due to the same error. error that occurred.
v If the problem occurred during allocation with the v For a PROTECT of an archive log data set, the return
intent to read the data set, determine the problem, code is from DADSM PROTECT. Refer to the
and use the DSNJU003 utility DELETE function to appropriate MVS publication for a description of the
delete the archive log data set from the BSDS archive MMSRV return codes.
log inventory. Then use the NEWLOG function to v For a CLOSE of an archive log data set, the return
add the data set back into the archive log inventory, code is the TCB completion code for an abend
pointing to the correct volume and device. received during CLOSE processing. This abend is
normally preceded by an IEC210I or IEC212I
For additional information about recovery from log message that defines the error.
failures, refer to Part 4 of Administration Guide. v For EDTINFO and UCBLOOK errors, the first 2 bytes
contain the return code and the second 2 bytes
This message can also be issued as the result of a contain the reason code.
possible user error. If the STATUS=keyword displays a
value of ’17080000’, then the site might have one or Refer to part 2 of Diagnosis Guide and Reference for
more active log data sets defined in the BSDS, but not information about recovery from log failures.
allocated on DASD. To correct the situation, print the
contents of the current active log data set inventory System action:
using the print log map (DSNJU004) utility, and then If this condition is encountered during log manager
do one of the following: initialization, DB2 startup is terminated. If the error
v For each active log data set listed in the BSDS, but occurs later and the data set is needed either for
not actually allocated on DASD, allocate the active offload or for input operations, DB2 processing
log data set using access method services. The access continues. If a second copy of the data is available, DB2
method services command syntax for active log data attempts to allocate and open the second data set.
sets can be found in the DSNTIJIN installation job
If the data set is needed as an active log data set, the
stream.
log manager attempts to retry the failing request. If the
v Use the DSNJU003 utility DELETE statement to retry fails, the DB2 subsystem is terminated.
delete the errant active log data set name, and the
NEWLOG statement to add the correct name to the Operator response:
active log data set inventory. The name specified on Notify the system programmer.
If the error was received from EDTINFO or UCBLOOK If another log data set contains the data, the log
and the allocation for the archive log data set fails, manager attempts to read the data from the alternate
verify that the archive UNIT names are correct in source. If an alternate source is not available, the log
ZPARMs. manager returns a read error return code to the
program requesting the log data.
If the dual active logging option is selected, the log For additional information about recovery from log
manager switches to the next data set for this copy. If failures, refer to Part 4 of Administration Guide.
the next data set is not ready, the log manager This message can also be issued as the result of a
temporarily enters single logging mode and allocates a possible user error. If the data set name associated with
replacement data set for the one that encountered the the DSNAME=keyword is missing, and the
error. Dual logging is resumed as soon as possible. STATUS=keyword displays a value of ’00180408’ or
If single active logging option is selected and the next ’00100408’, then the site is using dual logging, but only
data set is not ready, the log manager waits for that one set of active log data sets are defined in the BSDS.
data set to be available. In this case, log writing is To resolve this condition, do one of the following:
inhibited until the replacement is ready for output. v Define a second set of active log data sets using
access method services (if they are not defined
System action:
176 Messages
DSNJ107I • DSNJ110E
already), and update the BSDS log inventory using If dual BSDSs are available, the log manager enters
the DSNJU003 NEWLOG operation. single BSDS mode using the remaining good BSDS.
v Reset the log parameters ZPARM to indicate single Otherwise, an error code is returned to the log request
logging. To do this, set the TWOACTV parameter in that caused access to the BSDS.
the DSN6LOGP ZPARMs to NO. Operator response:
Notify the system programmer.
DSNJ107I READ ERROR ON BSDS
DSNAME=name ERROR STATUS=status System programmer response:
If dual BSDSs are available, the log manager attempts There is no more space in the specified bootstrap data
to read from the other BSDS. If read from the second set. The operation that encountered the out-of-space
BSDS fails or if there is only one BSDS, an error code is condition did not complete properly.
returned to the log request that caused access to the System action:
BSDS.
If dual BSDSs are available, the log manager enters
If read error is detected during start-up, DB2 single BSDS mode using the remaining good BSDS.
initialization process is terminated to prevent users Otherwise, an error code is returned to the log request
from operating in a cripple mode. User should take that caused access to the BSDS.
action to correct the problem.
Operator response:
Operator response:
Notify the system programmer.
Notify the system programmer.
System programmer response:
System programmer response:
If dual BSDS mode is being used, execute an offline
It may be necessary to replace or repair the BSDS, access method services job to rename the full BSDS and
depending on what conditions resulted from the read define a new, larger BSDS with the same name. Enter
error. To replace a BSDS, first delete the bad BSDS, and the DB2 -RECOVER BSDS command to reestablish dual
then define the new BSDS with the same name and BSDS mode.
attributes. If a new name is used for the new BSDS,
change the log startup JCL to specify the new BSDS If dual BSDS mode is not being used, the DB2
name. subsystem must be shut down and the BSDS recovered
offline. In this case, execute the same access method
services job mentioned above to rename the full data
DSNJ108I WRITE ERROR ON BSDS DSNAME=... set and define a larger data set. Next, execute an access
ERROR STATUS=... method services REPRO job to copy the full BSDS into
Explanation: the new BSDS.
Each time the message is issued, the off-load processing Execute an MVS Display System Requests command (D
is retried. If the situation is not corrected, the active log R,L for example) to ensure that there are no
data space fills to capacity, message DSNJ111E is outstanding requests that are related to the log off-load
issued, and the DB2 online processing halts. process. Take the necessary action to satisfy any
requests, and permit off-load to continue.
Operator response:
System programmer response:
To clear this condition, steps must be taken to complete
other waiting off-load tasks. Once an active log data set If the delay was caused by the lack of a resource
is made available (reusable) by completing the off-load required for off-load, the necessary resource must be
process for it, the DB2 logging activity can continue. made available to allow off-load to complete and thus
permit logging to proceed. For additional information
Execute an MVS Display System Requests command (D
on recovery from this condition, refer to the discussion
R,L for example) to determine the outstanding requests
on DB2 system resource failures and active log failures
related to the log off-load process. Take the necessary
in Part 4 of Administration Guide.
action to satisfy any requests, and permit off-load to
continue. If off-load fails to complete normally or
cannot be initiated, notify the system programmer. DSNJ112E csect-name INSUFFICIENT ACTIVE LOG
DATA SETS DEFINED IN BSDS
System programmer response:
Explanation:
Either correct the problem that is causing the off-load
process to fail, or add more active log data sets. Note There are not enough active log data sets defined in the
that the latter action requires DB2 to be down and the BSDS to start DB2. This condition usually exists for one
change log inventory (DSNJU003) utility to be run. of the following reasons.
Possible causes for the shortage of active log data space v Fewer than two data sets are defined for one of the
are: active log copy sets.
v Excessive logging. For example, too many users have v DSN6LOGP specified TWOACTV=YES in DB2
requested logs at the same time or too many utilities initialization parameters, but data sets for two copies
have specified LOG(YES). of active log are not defined in BSDS.
v Delayed or slow off-loading. For example, failure to v Fewer than two data sets are available (not flagged
mount archive volumes, incorrect replies to off-load as STOPPED) for one of the active log copy sets.
messages, or slow device speeds. System action:
v Excessive use of the -ARCHIVE LOG command.
DB2 startup is terminated.
Each invocation of the -ARCHIVE LOG command
causes the DB2 subsystem to switch to a new active Operator response:
log data set and to initiate an off-load of the active
log. Although the -ARCHIVE LOG command will Notify the system programmer.
not be processed when only one active log data set System programmer response:
remains in a copy of the active log (see DSNJ319I),
excessive use of the command could have consumed Use the change log inventory (DSNJU003) utility to
all space in the active log except the current active make the number of active log data sets defined in the
log data sets. BSDS consistent with the parameters specified on
DSN6LOGP. Log data sets that are flagged as
v Off-loads failed. See Operator Response.
’STOPPED’ will not be reused by DB2. These data sets
v Insufficient active log space. See Operator Response. must be recovered (either redefined or recovered from
v Offload task no longer functioning. Issue the the other copy of the log) and the log data sets must be
-ARCHIVE LOG CANCEL OFFLOAD command to deleted and re-added to the BSDS (using DSNJU003)
abnormally terminate and restart the offload process. with the appropriate RBA’s, to clear the STOPPED
status. Restart DB2.
DSNJ111E OUT OF SPACE IN ACTIVE LOG
DATA SETS DSNJ113E csect-name log-type log-value NOT IN
ANY ACTIVE OR ARCHIVE LOG
Explanation: DATA SET. CONNECTION-ID=aaaaaaaa,
Due to delays in off-load processing, all available space CORRELATION-ID=aaaaaaaa,
in all active log data sets has been exhausted. DB2 MEMBER-ID=member-id
recovery logging cannot continue. Explanation:
System action: A request was made to read the log starting at this
The DB2 log manager waits for an available data set. log-value and log-type (RBA or LRSN). However, the log
value cannot be found in any active or archive log data
Operator response: set for the indicated member. The member-id contains
178 Messages
DSNJ114I • DSNJ117I
the ID of the data sharing member whose logs were preceded by message DSNJ103I, the off-load data set
being requested at the time of the failure or zero if data could not be allocated. If this message is not preceded
sharing is not active. The connection and correlation by DSNJ103I, the off-load data set was successfully
IDs identify the user or application that encountered allocated, but could not be opened.
the problem. Correlation IDs beginning with ’0nn’
System action:
where ’nn’ is a number from 01 to 28, identify system
agents. Refer to part 2 of Diagnosis Guide and Reference Off-load will be tried at a later time.
for information about recovery from log failures.
Operator response:
System action:
Notify the system programmer.
Depending upon what log record is being read and
why, this error could result in an abend with a reason | System programmer response:
code of ’00D1032A’. | If the allocation failed with DSNJ103I, review the error
Operator response: | status information of message DSNJ103I. Correct the
| condition that caused the data set allocation to fail so
Notify the system programmer. | that, on retry, the off-load can take place.
System programmer response:
DSNJ116I ERROR ATTEMPTING TO ADD
| This error could be a user error. In most cases, the
ARCHIVE ENTRY TO BSDS
| archive log data set that contained the requested log
| value has been deleted from the bootstrap data set Explanation:
| (BSDS) by the change log inventory (DSNJU003) utility.
| Complete the following steps to correct the error: Off-load could not add an archive entry to the BSDS.
The off-load is considered incomplete. The active log
| v Locate the output from an old print log map run of data set is not marked as reusable for new log data.
| the BSDS for the DB2 member identified by This message is preceded by message DSNJ107I,
| member-id. DSNJ108I, or DSNJ109I.
| v Identify the data set that contains the missing log
| value. If the data set has not been reused, run the System action:
| DSNJU003 utility to add this data set back into the Off-load will be retried at a later time.
| inventory of log data sets.
Operator response:
| v Restart DB2.
Notify the system programmer.
DSNJ114I ERROR ON ARCHIVE DATA SET, System programmer response:
OFFLOAD CONTINUING WITH ONLY
Refer to the specific preceding message for action.
ONE ARCHIVE DATA SET BEING
GENERATED
DSNJ117I INITIALIZATION ERROR READING
Explanation:
BSDS DSNAME=......, ERROR
An error occurred while accessing one of the archive STATUS=...
data sets being created by off-load. Because the dual
Explanation:
archive option is specified, off-load is continuing with
the other archive data set. For the RBA range being The log manager encountered an error during
off-loaded, there is only one copy of archive instead of initialization reading from the specified bootstrap data
the usual two copies. set. Error status contains the VSAM return and
feedback codes. It is a two byte field with the first
System action:
containing the hexadecimal return code and the second
Off-load produces a single archive data set. byte containing the hexadecimal feedback code. Refer
to the appropriate VSAM publication for a description
System programmer response:
of VSAM return and reason codes.
A second copy of this archive log data set can be made,
System action:
and the BSDS(s) can be updated with the change log
inventory (DSNJU003) utility. DB2 startup is terminated.
Operator response:
DSNJ115I OFFLOAD FAILED, COULD NOT
Notify the system programmer.
ALLOCATE AN ARCHIVE DATA SET
System programmer response:
Explanation:
Determine the cause of the read error using the VSAM
Off-load could not allocate or open an archive log data
error status information provided. Restart DB2.
set. The off-load was not performed. If this message is
Operator response:
DSNJ118I LOG INITIALIZATION RECEIVED
RETURN CODE nnn FROM xxxxxxxx If restart fails, notify the system programmer.
MACRO
System programmer response:
Explanation:
If restart fails, run the print log map (DSNJU004) utility
Log manager initialization received a bad return code against each BSDS. From the output, determine which
from the named macro. data set is obsolete, delete it, define a replacement for
it, and copy the remaining BSDS to the replacement.
System action:
If output from the print log map (DSNJU004) utility for
DB2 initialization is terminated.
both data sets is similar, delete the data set with the
Operator response: oldest time stamp, and copy the data set with the most
recent time stamp.
Notify the system programmer.
System programmer response:
DSNJ121I LOG MANAGER ENCOUNTERED AN
Determine the problem from the documentation on the ERROR READING THE JFCB.
named macro and return code. Then take appropriate DDNAME=nnnnnnnn
steps, and restart the DB2 subsystem.
Explanation:
During log manager initialization (if dual BSDS data
DSNJ119I BOOTSTRAP ACCESS
sets are specified), the job file control block (JFCB) in
INITIALIZATION PROCESSING
MVS is read to obtain the data set names associated
FAILED
with DDNAME BSDS1 and BSDS2. This error is caused
Explanation: by a missing DD statement.
180 Messages
DSNJ123I • DSNJ128I
DSNJ123I CHANGE LOG INVENTORY FAILURE DSNJ126I BSDS ERROR FORCED SINGLE BSDS
DETECTED MODE
Explanation: Explanation:
During log manager initialization, the BSDS data set The log manager encountered an I/O error or a VSAM
was found to have been incompletely processed by the logical error on a bootstrap data set. This message is
change log inventory (DSNJU003) utility. preceded by message DSNJ107I or DSNJ108I.
System action: System action:
DB2 startup is terminated. The log manager enters single BSDS mode using the
remaining BSDS.
System programmer response:
Operator response:
Run the print log map (DSNJU004) utility to determine
what operation against the BSDS did not complete. Run Notify the system programmer.
the change log inventory (DSNJU003) utility against the
System programmer response:
BSDS(s) to allow any unfinished processing to be
completed. Execute an offline access method services job to rename
the error BSDS and define a new BSDS with the same
name. Then enter the log manager -RECOVER BSDS
DSNJ124I OFFLOAD OF ACTIVE LOG
command to reestablish dual BSDS mode.
SUSPENDED FROM RBA xxxxxx TO
RBA xxxxxx DUE TO I/O ERROR
DSNJ127I SYSTEM TIMESTAMP FOR BSDS=...
Explanation:
Explanation:
During off-load, an unrecoverable I/O error was
encountered on an active log data set. The data set When the log manager is initialized, the system time
experiencing the error is marked unusable, and no stamp for the bootstrap data sets (BSDS) is displayed.
further logging is done to that data set. The time stamp is of the format yy.ddd hh:mm:ss.th.
This time stamp should be close to the last time at
System action:
which this subsystem was stopped. If not, then it may
Active log data sets continue to be off-loaded as they indicate a restart is being attempted with the wrong
become full. BSDS.
Operator response: System action:
Notify the system programmer to allow recovery DB2 startup continues.
actions to be initiated.
Operator response:
System programmer response:
If the time displayed does not appear to be close to the
Recover the data manually from the data set, copy it to time this subsystem was last stopped, contact the
an archive data set, run the change log inventory system programmer.
(DSNJU003) utility to make the new archive data set
System programmer response:
available to the DB2, and remove the error-prone active
log data set from DB2 by using the change log If you cannot explain the apparent time discrepancy,
inventory utility. cancel the subsystem. From the startup procedure for
the subsystem services address space, determine the
data set names of the bootstrap data sets and run the
DSNJ125I ERROR DUMPING BSDS, OFFLOAD
print log map (DSNJU004) utility. Check whether the
CONTINUING WITHOUT
active and archive log data sets all belong to this
PRODUCING THE BSDS DUMP
subsystem. If not, then change the startup procedure
Explanation: for the subsystem services address space to use the
correct bootstrap data sets.
An error occurred while dumping the BSDS data set
during the off-load process. The data set is not
produced, but the off-load process continues. The DSNJ128I LOG OFFLOAD TASK FAILED FOR
volume containing the off-loaded data set does not ACTIVE LOG nnnnn
contain a BSDS for recovery use.
Explanation:
System action:
The off-load task abended while attempting to offload
The system continues the off-load process without the relative byte address (RBA) range in active log data
producing a dump of the bootstrap data set. set ’nnnnn’.
182 Messages
DSNJ131I • DSNJ140I
Change the ICF catalog name in the BSDS to agree with | program, to restore the data set with the original DCB
the name defined in DSNZPARM during DB2 | information.
initialization. To change the ICF catalog name in the
BSDS, use the BSDS change log inventory (DSNJU003)
DSNJ138I csect-name OFFLOAD COMPLETE FOR
utility with the NEWCAT control statement.
LOG TRUNCATION FROM AN
User response: ARCHIVE LOG COMMAND,
ENDRBA=xxxxxxxxxxxx
Notify the system programmer.
Explanation:
Problem determination:
This message indicates that the offload of the truncated
During log manager initialization, the ICF catalog name
active logs, resulting from an -ARCHIVE LOG
defined in DSNZPARM is compared to the catalog
command, has completed successfully. xxxxxxxxxxxx is
name in the BSDS to ensure that the catalog name used
the ENDRBA of the truncated active logs and the
by the log manager during DB2 processing is correct.
newly created archive log data sets.
These names were found not to be the same.
| DB2 could not successfully complete the read of this System programmer response:
| log-value and log-type (RBA or LRSN) due to reason If the user or application completes successfully, no
| code ’ccc’. The member-id contains the ID of the data further action is necessary. If the user or application
| sharing member whose logs were being requested at does not complete successfully, refer to the messages
| the time of the failure or zero if data sharing is not related to the actual failure to determine the
| active. The user or application that encountered the appropriate corrective actions. For additional
| error is identified by the connection and correlation ID. information about recovery from log failures, refer to
| Messages that have the same connection ID and Part 4 of Administration Guide.
| correlation ID relate to the same application.
| Correlation IDs beginning with ’0nn’, where ’nn’ is a
| number from 01 to 28, identify system agents.
System action:
184 Messages
DSNJ153E • DSNJ157I
186 Messages
DSNJ208E • DSNJ213I
Correct the control statement, and rerun the utility. A VSAM PUT was issued that resulted in a nonzero
return code. ’yy’ contains the error code returned by
VSAM. ’xxxxxxxx’ contains the ddname of the BSDS
DSNJ210I OLD ICF CATALOG NAME=oldname, encountering the error.
NEW CATALOG NAME=newname
System action:
Explanation:
The current utility is terminated. This message is
Change log inventory (DSNJU003) utility processing for written to the SYSPRINT data set, not to a console.
User response:
The action to be taken is dictated by the return code. identifying and reporting the problem.
The BSDS may have to be recovered by use of a
Collect the following diagnostic items:
backup copy.
v SYSABEND, SYSUDUMP, or SYSMDUMP output.
v SYSPRINT output, including JCL, for the application
DSNJ214I SPECIFIED DSNAME ALREADY
program or batch job, and system messages that
EXISTS IN BSDS, DDNAME=xxxxxxxx
were issued. Make sure that MSGLEVEL=(1,1) on the
Explanation: JOB statement so that all diagnostic information is
sent to SYSPRINT.
The user attempted a NEWLOG operation with a data
set name that already exists in the BSDS. An entry is
never made in a BSDS if the specified DSNAME DSNJ216I NO SPACE IN BSDS FOR
currently exists in either the active or archive records of ADDITIONAL ACTIVE LOG ENTRIES,
that BSDS. ’xxxxxxxx’ contains the ddname of the DDNAME=xxxxxxxx
subject BSDS.
Explanation:
System action:
The maximum number of active log data sets is fixed.
The current utility is terminated. This message is No further entries can be inserted after the maximum
written to the SYSPRINT data set, not to a console. has been reached. xxxxxxxx contains the ddname of the
subject BSDS.
User response:
System action:
Either correct the control statement and rerun the
utility, or delete the existing DSNAME from the BSDS The current utility is terminated. This message is
and rerun the utility. written to the SYSPRINT data set, not to a console.
User response:
DSNJ215I csect-name SVC 99 INFORMATION
Run the print log map utility to determine the current
REQUEST FOR DD NAME ’ddname’
status of the BSDS. Subsequent actions can then be
FAILED. RC= rc, RSN= rsncd, AND
formulated, depending upon the status of the BSDS.
INFO CODE infocode.
Explanation:
DSNJ217I SPECIFIED DSNAME DOES NOT
The Print Log Map utility requested information from EXIST IN BSDS, DDNAME=xxxxxxxx
the MVS Dynamic Allocation facility about the DD
Explanation:
name shown in the message, but the system was
unable to provide the information. The return code, The DELETE operation specifies a DSNAME that
reason code, and information code were returned by cannot be found in the BSDS. ’xxxxxxxx’ contains the
the system’s SVC 99 facility. See MVS/ESA ddname of the subject BSDS.
Programming: Authorized Assembler Services Guide for an
explanation of these codes. System action:
188 Messages
DSNJ219I • DSNJ222I
6. Insufficient virtual storage is usually accompanied You specified the parameter ’xxxx’. This parameter is
by a separate error from the MVS operating system. not valid for the argument.
Increase the REGION size on the JCL job step and
System action:
rerun the utility.
7. Contact the system programmer. The current utility is terminated. This message is
written to the SYSPRINT data set, not to a console.
Remove the redundant parameter, and rerun the utility. Operator response:
Notify the system programmer.
DSNJ225I xxxx OPERATION COMPLETED
System programmer response:
SUCCESSFULLY
The error status portion of this message contains the
Explanation:
2-byte error code (S99ERROR) followed by the 2-byte
The change log inventory (DSNJU003) utility operation information code (S99INFO) from the SVC request
named ’xxxx’ completed successfully. block. If the S99ERROR code indicates an SMS
deallocation error (97XX), then ’ssssssss’ contains
System action: additional SMS reason code information obtained from
This message is written to the SYSPRINT data set, not S99ERSN. Refer to the MVS/ESA SPL: Application
to a console. Development Guide for a description of these codes.
DSNJ226I SPECIFIED VOLUME ALREADY DSNJ229I csect-name OPEN FAILED FOR SYSIN
EXISTS IN BSDS, DDNAME=xxxxxxx Explanation:
Explanation: An error occurred when the DB2 Print Log Map utility
The specified volume currently exists in the archive log tried to open the SYSIN data set.
records of the BSDS. ’xxxxxxxx’ specifies the ddname of Possible causes are:
the subject BSDS.
1. The DD name of the SYSIN data set was not
System action: specified in the user’s job control language (JCL).
The current utility is terminated. This message is 2. Insufficient virtual storage is available to perform
written to the SYSPRINT data set, not to a console. the OPEN command.
User response:
190 Messages
DSNJ230I • DSNJ234I
3. The characteristics of the SYSIN data set are System programmer response:
different from those expected by the print log map
One or more error messages describing the specific
(DSNJU004) utility.
error preceded this message. Refer to the specific
System action: message(s) for error analysis and the appropriate action
to take.
DSNJU004 attempts to continue processing without an
input control statement. DB2 writes this message to the This message will be of interest to the IBM support
SYSPRINT data set, not to the system console. center when the problem is described.
User response:
DSNJ232I OUTPUT DATA SET CONTROL
Take one of the following actions based on the cause of
INITIALIZATION PROCESSING
the error.
FAILED
1. Provide the missing DD statement and rerun the
utility. Refer to Utility Guide and Reference for Explanation:
information about required dd statements. During log manager initialization, the output data set
2. Insufficient virtual storage is usually accompanied control function was unable to complete its
by a separate error message from the MVS initialization process.
operating system. Increase the REGION size on the
System action:
JCL job step and rerun the utility.
3. Check that the SYSIN data set is a fixed record DB2 startup is terminated.
format (blocked or unblocked) with an LRECL of System programmer response:
80. You might need to contact the system
programmer for help if this is a JES data set. One or more error messages describing the specific
error preceded this message. Refer to the specific
message for error analysis and the appropriate action to
DSNJ230I LOG OFFLOAD SUBCOMPONENT take.
INITIALIZATION PROCESSING
FAILED This message will be of interest to the IBM support
center when the problem is described.
Explanation:
During log manager initialization, the off-load function DSNJ233I ARCHIVE LOG READ
was unable to complete its initialization process. INITIALIZATION PROCESSING
System action: FAILED
Operator response: During log manager initialization, the archive log read
function was unable to complete its initialization
Notify the system programmer. process.
System programmer response: System action:
One or more error messages describing the specific DB2 startup is terminated.
error preceded this message. Refer to the specific
message(s) for error analysis and the appropriate Operator response:
actions to take. Notify the system programmer.
System programmer response:
DSNJ231I LOG COMMAND INITIALIZATION
PROCESSING FAILED One or more error messages describing the specific
error preceded this message. Refer to the specific
Explanation: message(s) for error analysis and the appropriate action
During log manager initialization, the log command to take.
function was unable to complete its initialization
process. DSNJ234I ARCHIVE LOG COMMAND QUIESCE
System action: INITIALIZATION PROCESSING
FAILED
DB2 startup is terminated.
Explanation:
Operator response:
During log manager initialization, the quiesce function
The rest of subsystem termination will direct the which supports the -ARCHIVE LOG MODE(QUIESCE)
actions you should take.
Operator response: The print log map (DSNJU004) utility read an invalid
control statement from the SYSIN data set.
Notify the system programmer.
System action:
System programmer response:
DSNJU004 ignores the control statement and attempts
One or more error messages describing the specific to continue processing by looking for a SYSUT1 DD
error preceded this message. Refer to the specific statement to describe the BSDS that is to be printed.
message(s) for error analysis and the appropriate action
to take. User response:
Correct or remove the control statement and rerun the
DSNJ235I OUTPUT BUFFER WRITER job.
INITIALIZATION PROCESSING
Refer to Utility Guide and Reference for information on
FAILED
creating a print log map (DSNJU004) utility control
Explanation: statement.
During log manager initialization, the output buffer Problem determination:
writer function was unable to complete its initialization
If you suspect an error in DB2, refer to Part 2 of
process.
Diagnosis Guide and Reference for information on
System action: identifying and reporting the problem.
DB2 startup is terminated. Collect the following diagnostic items:
Operator response: v SYSPRINT output, including JCL, for the application
program or batch job, and system messages that
Notify the system programmer. were issued. Make sure that MSGLEVEL=(1,1) on the
JOB statement so that all diagnostic information is
System programmer response:
sent to SYSPRINT.
One or more error messages describing the specific
error preceded this message. Refer to the specific
DSNJ238I LOG OFFLOAD TERMINATION
message(s) for error analysis and the appropriate action
PROCESSING FAILED
to take.
Explanation:
DSNJ236I BOOTSTRAP ACCESS TERMINATION During log manager termination, the off-load function
PROCESSING FAILED was unable to complete its termination process.
Explanation: System action:
During log manager termination, the bootstrap data set Log manager shutdown continues to the next step.
access function was unable to complete its termination
process. Operator response:
Log manager shutdown continues to the next step. System programmer response:
192 Messages
DSNJ240I • DSNJ244I
The conditional restart control record in use indicates Notify the system programmer.
that the DB2 log should be truncated at the specified System programmer response:
RBA or LRSN.xxx is replaced by either RBA or LRSN,
and rrr is the value specified in the current record. If you suspect an error in DB2, refer to Part 2 of
Diagnosis Guide and Reference for information on
System action: identifying and reporting the problem.
If Y, DB2 startup continues. If N, DB2 startup is For a return code of ’4’, if you suspect an error in DB2,
terminated. refer to Part 2 Diagnosis Guide and Reference of for
Operator response: information on identifying and reporting the problem.
For a return code of ’8’, execute an offline access
Reply N if the truncation is going to occur at an method services job to determine the cause of the
undesirable point. Notify system programmer. Reply Y VSAM error.
to continue the restart.
System programmer response: DSNJ248I ARCHIVE LOG READ
DEALLOCATION INITIALIZATION
Rerun the change log inventory (DSNJU003) utility to
PROCESSING FAILED
modify the conditional restart record.
Explanation:
DSNJ246I CONDITIONAL RESTART RECORD During log initialization, the archive log read
INDICATES COLD START AT RBA rrr. deallocation process was unable to complete its
REPLY Y TO CONTINUE, N TO initialization.
CANCEL
System action:
Explanation:
DB2 startup is terminated.
The conditional restart control record in use indicates
that DB2 is to be cold started and that logging is to be Operator response:
begin at the specified RBA. Notify the system programmer.
System action: System programmer response:
If ’Y’, DB2 startup continues. If ’N’, DB2 startup is One or more error messages describing the specific
terminated. error precede this message. Refer to these messages for
Operator response: error analysis and the appropriate action to take.
194 Messages
DSNJ250E • DSNJ255I
The DB2 subsystem detecting this error is terminated. The current operation is terminated. This message is
written to the SYSPRINT data set, but not written to a
System programmer response: console.
Using IDCAMS LISTCAT or TSO LISTCAT, display the User response:
share options of all of the active log data sets of all of
the members in the data sharing group. For any active Change the number of parameter arguments on the
log data set that is defined with less than control statement, and rerun the utility.
SHAREOPTIONS(2 3), use IDCAMS ALTER or TSO
ALTER to alter the data set definitions to | DSNJ255I csect-name CONDITIONAL RESTART
SHAREOPTIONS(2 3) or higher. | ENDTIME OF end-time WILL RESULT
Problem determination: | IN LOG TRUNCATION AT xxxx
| yyyyyyyyyyyy
If you suspect an error in DB2, refer to Part 2 of
Diagnosis Guide and Reference for information on | Explanation:
identifying and reporting the problem. | The conditional restart control record in use indicates
Collect the following diagnostic items: | that the DB2 log should be truncated with ENDTIME
| end-time. The ENDTIME value translates to truncation
v Console output from the system on which the job
| type xxxx with value yyyyyyyyyyyy. This value is either
was run, and a listing of the SYSLOG data set for the
| an LRSN value (for data sharing) or a STCK (store
period of time spanning the failure.
| clock) value (for non-data sharing).
v Dynamic dump, taken to SYS1.DUMPxx data set, by
DB2 (04E and 04F abends). | System action:
v Listing of SYS1.LOGREC data set, obtained by | Startup continues.
executing IFCEREP1.
If dual BSDS data sets are specified, the SYSUT1 data If this message was received during processing of the
set is converted first. If that conversion is successful, -RECOVER BSDS command, then the DB2 subsystem
the SYSUT2 data set is then converted. A failure at this will continue in single BSDS mode. If this message was
point does not affect the successful SYSUT1 conversion. received during processing of the -ARCHIVE LOG
command, the archive log history record in the BSDS
If conversion fails for the SYSUT1 data set, processing will not be updated to reflect the occurrence of an
is terminated at that point. In this case, any SYSUT2 -ARCHIVE LOG command; logging and the off-load
data set that was specified will not be converted. processing will continue.
User response: Operator response:
196 Messages
DSNJ302I • DSNJ306I
Inform the system programmer of the type of error that Execute an offline access method services job to delete
occurred, and whether the error occurred while or rename the replacement BSDS and define a new
processing a -RECOVER BSDS command or an BSDS with the same name. Reenter the log manager
-ARCHIVE LOG command. -RECOVER BSDS command to reestablish dual BSDS
mode.
System programmer response:
If this message was received during processing of the
DSNJ304I ERROR CLOSING REPLACEMENT
-RECOVER BSDS command, then recovery action must
BSDS DSNAME=... ERROR STATUS=...
be performed on the bootstrap data set before
reentering the command. If this message was received Explanation:
during processing of the -ARCHIVE LOG command, no
The -RECOVER BSDS command encountered an error
action is necessary.
while attempting to close the specified bootstrap data
set. Error Status contains the VSAM return and
DSNJ302I ALLOCATION ERROR ON feedback codes. It is a 2-byte field with the first
REPLACEMENT BSDS DSNAME=... containing the hexadecimal return code and the second
ERROR STATUS=... containing the hexadecimal feedback code.
Explanation: System action:
The RECOVER BSDS command encountered an error Processing of the command is terminated. The system
while trying to dynamically allocate the specified data continues in single BSDS mode.
set. DSNAME is the data set name. Error Status is the
Operator response:
error code and information code returned by MVS
dynamic allocation. Notify the system programmer.
System action: System programmer response:
Processing of the command is terminated. The system Execute an offline access method services job to delete
continues in single BSDS mode. or rename the replacement BSDS and define a new
BSDS with the same name. Reenter the log manager
Operator response:
-RECOVER BSDS command to reestablish dual BSDS
Determine the cause of the error from the error status mode.
contained in the message, and correct the condition.
Then reenter the -RECOVER BSDS command.
DSNJ305I REPLACEMENT BSDS NOT EMPTY
System programmer response: DSNAME=...
The error status portion of this message contains the Explanation:
2-byte error code (S99ERROR) followed by the 2-byte
The -RECOVER BSDS command was issued, but the
information code (S99INFO) from the SVC request
replacement bootstrap data set was not empty; that is,
block. Refer to the appropriate MVS publication for a
it contained data.
description of these codes.
System action:
DSNJ303I WRITE ERROR ON REPLACEMENT Processing of the command is terminated. DB2
BSDS DSNAME=... ERROR STATUS=... continues in single BSDS mode.
Explanation: Operator response:
The -RECOVER BSDS command encountered an error Notify the system programmer.
while attempting to write to the specified bootstrap
data set. Error Status contains the VSAM return and System programmer response:
feedback codes. It is a 2-byte field with the first Execute an offline access method services job to delete
containing the hexadecimal return code and the second or rename the error BSDS and define a new BSDS with
containing the hexadecimal feedback code. the same name. Reenter the log manager -RECOVER
System action: BSDS command to reestablish dual BSDS mode.
198 Messages
DSNJ313I • DSNJ317I
activity for all users and jobs that were blocked during
DSNJ316I SYSTEM QUIESCE ALREADY IN
the quiesce period.
PROGRESS
Explanation:
DSNJ313I PARAMETER SPECIFIED ON THE
keyword KEYWORD (value) IS NOT IN An attempt was made to issue an -ARCHIVE LOG
THE RANGE OF ALLOWABLE command with the MODE(QUIESCE) option when a
VALUES system quiesce was already in progress. The system
quiesce could be the result of processing by another
Explanation:
-ARCHIVE LOG MODE(QUIESCE) command, or by a
This message was generated by an error occurring in -STOP DB2 MODE(QUIESCE) command.
one of the following commands:
System action:
v ARCHIVE LOG command with MODE(QUIESCE)
Command processing will terminate. The system
v SET ARCHIVE
quiesce currently in progress will continue.
v SET LOG
You specified a value for one of the command options DSNJ317I ARCHIVE LOG QUIESCE PERIOD
that was outside of the range of allowed values. EXPIRED. NUMBER OF
OUTSTANDING UR’S = xxxx.
System action: ARCHIVE LOG PROCESSING WILL
BE TERMINATED, AND UPDATE
Processing for the ARCHIVE LOG, SET ARCHIVE, or
ACTIVITY AGAINST DB2
SET LOG command is terminated. This message is
RESOURCES WILL BE RESUMED.
followed by message DSN9023I.
HH:MM:SS
Operator response:
Explanation:
Check Command Reference for the correct syntax.
An -ARCHIVE LOG MODE(QUIESCE) command was
processed by the DB2 subsystem; however, the DB2
DSNJ314I xxxx KEYWORD REQUIRES yyyy subsystem was not able to quiesce all update activity in
KEYWORD TO ALSO BE SPECIFIED the user-specified quiesce time interval.
ON THE COMMAND
System action:
Explanation:
This message is informational only. The DB2 subsystem
A command was entered which specified the ’xxxx’ determined that ’xxxx’ units of recovery (URs) did not
keyword. However, use of the ’xxxx’ keyword requires reach a point of consistency during the quiesce period,
that the ’yyyy’ keyword also be used. and therefore could not be stopped from continuing
their associated update processing.
System action:
Consequently, the -ARCHIVE LOG processing will be
Command processing terminates for the -ARCHIVE
terminated. The current active log data set(s) will not
LOG or -RECOVER BSDS command. This message is
be truncated, and will not be switched to the next
followed by message DSN9023I.
available active log data set(s). The log archive
Operator response: (off-load) task will not be created. All jobs and users
suspended during the quiesce will be resumed, and
Check Command Reference for the correct syntax. normal update activity against DB2 resources will be
commenced.
DSNJ315I -STOP DB2 MODE(FORCE) IN This message will be followed by the DSNJ312I
PROGRESS message.
Explanation: Operator response:
An attempt was made to issue an -ARCHIVE LOG Contact the system programmer.
command when a -STOP DB2 MODE(FORCE)
command was already in progress. System programmer response:
200 Messages
DSNJ320I • DSNJ325I
Notify the system programmer. The message number is not included in this message.
This message, in combination with message DSNJ327I, corr-id An identifier associated with a specified
provides the tape unit information that is part of the thread. In TSO, it is either the authorization ID
-DISPLAY ARCHIVE report. or the job name.
tapeaddr
The physical tape address of the tape unit DSNJ331I avolume, avolume, avolume, avolume ...
allocated to read archive log. Explanation:
status Status of tape address: This message provides the tape volume information for
BUSY Tape address is actively processing an the Archive Log Volumes report output.
archive log data set. avolume
PREM Tape address is active and allocated The name of the archive log volume required
for premount. for this correlation ID. An ’avolume’ prefixed
with an ’*’ signifies that the data on the
AVAIL Tape unit is inactive and waiting for archive log volume is also mapped by an
work. active log data set. As such, the ’avolume’
corr-id The correlation id associated with the user of might not be required for the read process,
the tape being processed. If the status is PREM since the data is read from the active log, if
or AVAIL, this column might contain ’*****’, possible.
indicating no current user is associated with
this tape. DSNJ332I END OF ARCHIVE LOG VOLUMES
vname The name of the tape volume that is mounted REPORT
on the tape address. Explanation:
dsname This message follows messages DSNJ330I and
The data set on the tape volume that is being DSNJ331I and indicates that the ARCHIVE LOG
processed (BUSY and PREM) or was last VOLUMES report was generated successfully. The
processed (AVAIL). message number is not included in this message.
202 Messages
DSNJ334I • DSNJ340I
CANCELED
DSNJ341I csect-name -ARCHIVE LOG COMMAND
ARCHIVE LOG command processing for the
NOT ALLOWED, LOGGING IS
named member was canceled due to a
SUSPENDED
problem encountered elsewhere in the data
Explanation: sharing group. The quiesce operation is
interrupted and terminated and update
An attempt to issue an -ARCHIVE LOG command
activity against DB2 resources is resumed
failed because a -SET LOG SUSPEND command has
before command processing is terminated for
suspended logging.
the member.
System action:
COMMUNICATIONS FAILURE
Command processing terminates for the -ARCHIVE A communications failure occurred between
LOG command. You may reissue the command when the named member and one or more other
logging has been resumed by the -SET LOG RESUME members in the data sharing group. The
command. quiesce operation is interrupted and update
activity against DB2 resources is resumed
before command processing is terminated for
DSNJ350I csect-name (A)SYNCHRONOUS the member. ARCHIVE LOG command
ARCHIVE LOG COMMAND QUIESCE processing for the remainder of the data
PROCESSING STARTED IN DATA sharing group terminates unsuccessfully.
SHARING
FAILED
Explanation: The named member was inactive at the time
The DB2 subsystem of a data sharing group accepted the ARCHIVE LOG command was issued.
an ARCHIVE LOG command with the Termination of the DB2 subsystem for this
MODE(QUIESCE) option. member was abnormal. This status, if
displayed for any member, will cause
Each active DB2 member in the data sharing group ARCHIVE LOG command processing for the
performs the quiesce operation. The member entire data sharing group to terminate
originating the quiesce issues message DSNJ350I; all unsuccessfully.
other members issue DSNJ310I as they start quiescing.
NOT AVAILABLE
Archive command status for the named
DSNJ351I csect-name MEMBER member name member could not be determined. This
STATUS=member status condition typically occurs when the named
Explanation: member fails to respond during ARCHIVE
LOG command processing and is usually
| This message is one of a list of elements that display accompanied by message DSNJ353I and/or
| archive related status of the indicated member of the message DSNJ355I.
| data sharing group. These member status messages are
| preceded by the message DSNJ359I and are followed QUIESCED
| by DSNJ361I. The named member was active at the time the
ARCHIVE LOG command was issued. Update
member name identifies the member of the data sharing activity against DB2 resources had successfully
group. quiesced for that member (no active URs) in
member status indicates archive related status of the response to specifying MODE(QUIESCE).
named member. It appears as one of the following:. QUIESCED/OFFLOADING
ABNORMALLY TERMINATING The named member was active at the time the
The named member was undergoing abnormal ARCHIVE LOG command was issued. Update
subsystem termination at the time ARCHIVE activity against DB2 resources had successfully
LOG processing was active for the data quiesced for that member (no active URs) in
sharing group. ARCHIVE LOG command response to specifying MODE(QUIESCE). The
processing for the remainder of the data active log at the time was truncated and an
sharing group terminates unsuccessfully. offload process was initiated after all members
in the data sharing group had reached a
ARCHIVE ALREADY ACTIVE quiesce point.
ARCHIVE LOG command processing was
running at the named member at the time a STOPPED
succeeding ARCHIVE LOG command was The named member was inactive at the time
issued. The succeeding ARCHIVE LOG the ARCHIVE LOG command was issued.
command terminates unsuccessfully for the Termination of the DB2 subsystem for this
remaining members of the data sharing group. member was normal with no incomplete URs
outstanding. Log truncation and offload
204 Messages
DSNJ352W • DSNJ357E
processing are scheduled to be performed active members in the data sharing group have
automatically the next time the named successfully quiesced their update activity within the
member is started. When the member is allotted time period. For each active member in the
started, it is important to ensure that archive data sharing group, the active log is truncated and
processing occurs automatically. Certain error switched, and an offload task is initiated to begin the
conditions might require entering an offload process. Log truncation, switch and offload
ARCHIVE LOG command via the operator processing for stopped (and quiesced) members is
console to cause log truncation and offload performed the next time they are started.
processing to be performed. This member
status is accompanied by warning message
DSNJ355I csect-name ARCHIVE LOG: ONE OR
DSNJ362A.
MORE ACTIVE MEMBERS FAILED TO
TIME EXCEEDED RESPOND OR START OFFLOAD
The named member could not quiesce its TASKS
update activity within the allotted period of
Explanation:
time. The incomplete quiesce operation is
interrupted and update activity is resumed This message is displayed when MODE(QUIESCE) is
before command processing is terminated for specified with the ARCHIVE LOG command, and one
the member. ARCHIVE LOG command or more active members could not successfully quiesce
processing for the remainder of the data their update activity in the time allotted. Subsystem
sharing group is unsuccessfully terminated. activity already quiesced is resumed, and ARCHIVE
LOG command processing terminates unsuccessfully
for all active members in the data sharing group.
DSNJ352W csect-name MEMBERS WERE NOT
Message DSNJ353I might also appear with this
OFFLOADED
message.
Explanation:
Operator response:
DB2 issues this message during processing of an
See the list of DSNJ351I member status messages
ARCHIVE LOG command with the MODE(QUIESCE)
following message DSNJ359I to determine the reason
option. One or more quiesced members were not
for the archive command failure.
available to receive the archive request. DSNJ351I
messages follow to display the quiesced members.
DSNJ356I csect-name COMMUNICATIONS
At the next start up of the quiesced member, DB2
FAILURE TERMINATED COMMAND
switches (truncates) the current active log and initiates
the archive task. Explanation:
This message appears as a result of the failure of a
DSNJ353I csect-name DSNJ353I MEMBER member communications request by one or more members of
name NOT RESPONDING. the data sharing group. This message is likely to be
accompanied by DSN7xxx or other error messages
Explanation:
and/or an SVC dump.
This message is displayed when a response is needed
System action:
but not received within an expected period of time
during ARCHIVE LOG MODE(QUIESCE) command ARCHIVE LOG command processing terminates
processing. This can occur as a result of abnormal unsuccessfully for all members in the group.
subsystem termination under the named member or,
possibly from communications problems among
members of the data sharing group. DSNJ357E csect-name SYSTEM QUIESCE FAILED
Examine the console log of the named member for This message indicates the unsuccessful outcome of an
operator information messages that might relate to the ARCHIVE LOG MODE(QUIESCE) command. This
problem. message indicates that one or more members were
unable to quiesce their update activity in the time
allowed. It is usually accompanied by one or more
DSNJ354I csect-name DSNJ354I ARCHIVE LOG: related messages (e.g., DSNJ355I), and a list of member
ALL ACTIVE MEMBER(S) STARTED status messages indicating the reason for the failure.
OFFLOAD TASKS
Operator response:
Explanation:
Refer to messages DSNJ359I, DSNJ351I and DSNJ361I
This message is displayed when MODE(QUIESCE) is to determine archive related status of members in the
specified with the ARCHIVE LOG command, after all data sharing group.
206 Messages
DSNJ372I • DSNJ403I
DB2 catalog and directory data sets exceeds the message is written to the SYSPRINT data set, not to a
maximum capacity of the BSDS SYSTEMDB record. console.
This is an internal error.
User response:
System action:
Correct the control statement and rerun the utility.
All subsequent change log inventory (DSNJU003) utility
statements are bypassed, and DSNJU003 processing is
DSNJ407I csect-name NO VALID CHECKPOINT
terminated with a return code of 4. The DB2
RBA FOUND. LOG WILL BE
SYSTEMDB record is not updated.
SCANNED AT RESTART
This message is written to the SYSPRINT data set, not
Explanation:
to a console.
After completing its search through the resource
User response:
manager status table and the checkpoint queue, no
Notify the systems programmer. valid checkpoint RBA was found within the specified
range.
DSNJ404E keyword NOT ALLOWED FOR System action:
operation OPERATION
Utility processing continues, and will set a return code
Explanation: of 4. This message is written to the SYSPRINT data set,
not to a console.
An invalid keyword was used during the operation
named ’operation’. User response:
System action: | The last 100 checkpoints are recorded in the BSDS,
| including the log STARTRBA and log ENDRBA of the
The current utility processing is terminated. This
| checkpoint range. When either STARTRBA or
message is written to the SYSPRINT data set, not to a
| ENDRBA/ENDLRSN are specified, the change log
console.
| inventory (DSNJU003) utility attempts to locate a valid
User response: | checkpoint in the range. In this case, DSNJU003 was
| unsuccessful in finding a valid checkpoint. When DB2
Correct the control statement and rerun the utility. | is restarted, the log will be scanned to locate the
| checkpoint prior to the log truncation point.
DSNJ405E keyword1 KEYWORD MUTUALLY
EXCLUSIVE WITH keyword2 DSNJ408I csect-name CHECKPOINT RBA FOUND,
KEYWORD RBA = rba, TIME = time
Explanation: Explanation:
’keyword1’ and ’keyword2’ are mutually exclusive and After completing its search through the resource
cannot appear on the same control statement. manager status table and the checkpoint queue, ’rba’
System action: was the most recent checkpoint RBA in the specified
range and ’time’ was the time of the checkpoint.
The current utility processing is terminated. This
message is written to the SYSPRINT data set, not to a System action:
console. Utility processing continues.
User response:
Determine the extraneous keyword and remove it from DSNJ409I UNABLE TO WRITE ACTIVE LOG
the control statement. Rerun the utility. RECORD TO THE BSDS DATASET.
DDNAME=xxxxxx
208 Messages
DSNJ410E • DSNJ415E
DSNJ411I csect-name CRESTART nnnn FOR STARTRBA and ENDRBA are equal. A cold start will
CRCRID = yyyy, DDNAME = ddname result if this restart control record is used during DB2
restart. No forward or backout processing will be
Explanation: performed.
A CRESTART request has just completed. ’nnnn’ is System action:
either CREATE or CANCEL. ’yyyy’ is the restart
control record hexadecimal identifier and ’ddname’ is CRESTART processing continues.
the BSDS data set (SYSUT1 or SYSUT2) associated with User response:
the request.
No additional actions are required if a cold start of the
System action: system is desired. If a cold start is not desired, reissue
Current utility processing continues. This message is the CRESTART and either CANCEL the current restart
written to the SYSPRINT data set, not to a console. control record, or CREATE a new restart control record.
User response:
DSNJ415E csect-name ENDRBA = rba IS INVALID,
Note the record identifier for future reference. MUST BE A MULTIPLE OF 4K
Explanation:
DSNJ412E csect-name RESTART CONTROL
RECORD NOT FOUND IN BSDS The specified ENDRBA at ’rba’ is not a multiple of
4KB.
Explanation:
System action:
The CRESTART CANCEL keyword was specified but
the conditional restart control record does not exist in CRESTART processing is terminated.
the BSDS data set. User response:
System action: Correct the ENDRBA value on the CRESTART
statement and rerun the utility.
A required parameter ’xxxxxxxx’ for a Log utility One or more error messages describing the specific
operation was missing from the Log utility control error preceded this message. This error is considered
statement. The attempted operation is ’yyyyyyyy’. unrecoverable and will leave the BSDS data set in an
uncertain state. It will be necessary to either: recreate
System action: the data set using access method service routines and
then use change log inventory (DSNJU003) utility to
The Log utility ’yyyyyyyy’ operation does not perform
make the active and archive log data set(s) known to
its function. All subsequent Log utility control
the BSDS, or recover the BSDS using a backup copy.
statements are processed. A nonzero return code is
issued by the utility.
DSNJ420I UNABLE TO WRITE BCR1 RECORD
DB2 writes this message to the SYSPRINT data set, not
TO BSDS DATASET. DDNAME=xxxxxx
to a console.
Explanation:
User response:
A program encountered an I/O error when attempting
Add the missing parameter to the control statements
to write the BSDS control record to the BSDS data set.
associated with the specified operation and rerun the
’xxxxxx’ is the DDNAME of the BSDS data set being
utility.
accessed.
Operator response:
DSNJ418I WARNING - A NOTREUSEABLE
ACTIVE LOG DATA SET WAS Notify the system programmer.
DELETED FROM BSDS LOG
INVENTORY, System programmer response:
STARTRBA=...,ENDRBA=... One or more error messages describing the specific
Explanation: error preceded this message. Refer to the specific
message(s) for error analysis and the appropriate action
The data set name specified on the DSNAME to take.
parameter of the change log inventory (DSNJU003)
utility DELETE statement was a NOTREUSABLE active
log.
System action:
DSNJU003 processing continues, it will terminate with
210 Messages
DSNJ421I • DSNJ425I
When dropping one of the old active log data sets from
DSNJ421I THE BSDS IS NOT AT THE PROPER
the BSDS, it was found to have been flagged as NOT
RELEASE LEVEL. DDNAME=xxxxx
REUSABLE (i.e., this data set MAY NOT have been
Explanation: archived). ’xxxxxx’ will contain the data set name of the
active log in question.
This message is issued when a program attempting to
access The BSDS data set is not at a compatible release System action:
level. This can be one of the following:
The program will remove this active log data set from
v The program accessing the BSDS data set is at a the BSDS and continue.
NEW release level and the BSDS is at the old level.
System programmer response:
v The program accessing the BSDS data set is at an
OLD release level and the BSDS is at the NEW level. Check to see if this data set had been archived. The
v The program encountered an UNKNOWN release active log data set was not deleted on disk but
level on the BSDS data set. removed only from the BSDS data set, so it may still be
archived, if needed. Use access method service routines
System action: to copy the VSAM active log data set to a sequential
The program will terminate with no action taken. archive log data set.
DSNJ428I CHECKPOINT RECORD DELETED The specified STARTRBA could not be located in the
FROM QUEUE, STARTRBA=startrba, checkpoint queue.
ENDRBA=endrba System action:
Explanation: The current utility is terminated. This message is
The checkpoint record specified has been deleted from written to the SYSPRINT data set, not to a console.
the Checkpoint Queue. ’startrba’ and ’endrba’ was the User response:
RBA range indicated in the deleted checkpoint record.
Run the print log map (DSNJU004) utility against the
System action: SYSUT1 BSDS and SYSUT2 BSDS. Determine the
The BSDS checkpoint queue is modified as stated. This correct STARTRBA value and correct the STARTRBA
message is written to the SYSPRINT data set, not to a parameter and rerun the utility.
console.
DSNJ432I THE OFFLRBA VALUE MUST END
DSNJ429I RBA RANGE CONFLICTS WITH WITH ’FFF’
EXISTING CHECKPOINT RECORD Explanation:
RBA RANGE
The OFFLRBA value is invalid. It must end with ’FFF’.
Explanation:
System action:
The specified RBA range for the new checkpoint record
either exists or overlaps an existing RBA range in the The current utility is terminated. This message is
checkpoint queue. written to the SYSPRINT data set, not to a console.
System action: User response:
212 Messages
DSNJ433I • DSNJ436I
Correct the control statement and rerun the utility. Collect the following diagnostic items:
v SYSPRINT output, including JCL, for the application
DSNJ433I csect-name INVALID CONTROL program or batch job, and system messages that
STATEMENT. A MEMBER LIST MUST were issued. Make sure that MSGLEVEL=(1,1) on the
CONTAIN AT LEAST ONE MEMBER JOB statement so that all diagnostic information is
NAME. sent to SYSPRINT.
Explanation:
DSNJ435I csect-name THE MEMBER LIST OF A
The control statement is invalid. The member list is CONTROL STATEMENT MUST BE
either empty or in the wrong format. TERMINATED WITH A
System action: PARENTHESIS.
If you suspect an error in DB2, refer to Part 2 of The current utility is terminated. This message is
Diagnosis Guide and Reference for information on written to the SYSPRINT data set, not to a console.
identifying and reporting the problem.
User response:
Collect the following diagnostic items:
Correct the control statement and rerun the utility.
v SYSPRINT output, including JCL, for the application
program or batch job, and system messages that
were issued. Make sure that MSGLEVEL=(1,1) on the | DSNJ439I csect_name NEW FUNCTION MODE
JOB statement so that all diagnostic information is | REQUIRED FOR xxxxxx OPERATION
sent to SYSPRINT. | Explanation:
| An attempt was made to run a log utility requiring
DSNJ437I csect-name UNABLE TO ALLOCATE | new-function mode while DB2 was in conversion mode
BSDS dsname. SVC 99 RTN CODE rc, | or enabling-new-function mode.
RSN CODE rsncd, INFO infocd.
| DB2 must be in new-function mode before the utility
Explanation: | program can run successfully. xxxxxx is the name of the
The print log map (DSNJU004) utility attempted to | attempted operation requiring new-function mode.
allocate a BSDS data set using the MVS Dynamic | System action:
Allocation facility, but the system was unable to
complete the allocation. The return code, reason code, | The program will terminate with no action taken.
and information code were returned by the system’s
| System programmer response:
SVC 99 facility. See MVS/ESA Programming: Authorized
Assembler Services Guide for an explanation of these | Convert DB2 to new-function mode and retry the
codes. | program.
System action:
DSNJ440I BSDS HAS ALREADY BEEN
The processing of the BSDS named in the message is
CONVERTED, DDNAME=nnnnnnnn
terminated. If this is the last (or only) BSDS to be
processed by this job, the job is terminated. Explanation:
User response: This message occurs when the BSDS conversion
program DSNJCNVB detects that the BSDS data set
Refer to Utility Guide and Reference for information on
that was specified by DDNAME nnnnnnnn has already
required JCL statements. Correct the JCL and rerun the
been converted.
job.
System action:
Problem determination:
If only SYSUT1 was specified, or both SYSUT1 and
If you suspect an error in DB2, refer to Part 2 of
SYSUT2 data sets have already been converted, the
Diagnosis Guide and Reference for information on
program will terminate with no action taken. In the
identifying and reporting the problem.
case where both are specified, but only SYSUT1 was
Collect the following diagnostic items: previously converted, the program will continue to
v SYSPRINT output, including JCL, for the application process the conversion for SYSUT2.
program or batch job, and system messages that System programmer response:
were issued. Make sure that MSGLEVEL=(1,1) on the
JOB statement so that all diagnostic information is No further action is necessary.
sent to SYSPRINT.
. DSNJ441I INVALID BSDS CONVERSION,
DDNAME=xxxxxx
214 Messages
DSNJ442I • DSNJ702E
The procedure for running program DSNJCNVB with listed DB2 reason code.
includes making a copy of the BSDS prior to
System action:
conversion. Restore the BSDS to the original
pre-conversion copy, and retry the conversion. Once the An execution unit issues this message and then, if this
conversion is successful, retry the program. was an unconditional request, writes a record to
SYS1.LOGREC and requests an SVC dump. The
execution unit then terminates.
| DSNJ442I csect-name RECEIVED ERROR STATUS
| nnn FROM macro-name Operator response:
| Explanation: Collect all relevant diagnostic materials, including
SYS1.LOGREC, SVC dump, and console output of peer
| DB2 encountered an error while issuing macro
and host.
| macro-name. Error status is the return code from the
| specified macro. System programmer response:
| System action: Review the explanation for the associated DB2 reason
code for further action.
| The requested operation fails.
| User response:
DSNJ701E csect-name MEMBER NAME
| If the error is from the CONVTOD macro, ensure that (membername) IN BSDS DOES NOT
| the ENDTIME timestamp value is valid and in the MATCH MEMBER NAME (membername)
| correct format. IN DB2 SYSTEM PARAMETERS
dsnzparm
| DSNJ443I csect-name ENDTIME LOG Explanation:
| TRUNCATION POINT = xxxxxxxxxxxx
During startup, DB2 detected that the member name
| Explanation: listed in its bootstrap data set (BSDS) does not match
the member name in the DB2 system parameters load
| The ENDTIME timestamp value results in a log module.
| truncation at LRSN or STCK value xxxxxxxxxxxx.
Operator response:
| System action:
Notify the system programmer.
| Utility processing continues.
System programmer response:
| DSNJ444I csect-name ENDTIME TIMESTAMP IS Restore the BSDS or specify a different system
| GREATER THAN THE CURRENT parameters load module on the START DB2 command.
| TIMESTAMP
| Explanation: DSNJ702E csect_name GENERIC LU NAME lu-name
IN BSDS DOES NOT MATCH THE
| The ENDTIME timestamp must be a GMT timestamp
GENERIC LU NAME lu-name
| for which there exists a log record with a timestamp
ASSOCIATED WITH THE DATA
| that is greater than, or equal to, the specified
SHARING GROUP.
| timestamp value.
Explanation:
| System action:
DB2 issues this message during startup when it detects
| The utility terminates. that the generic LU name in the bootstrap data set
| User response: (BSDS) does not match the generic LU name in the
shared communications area (SCA) structure.
| Specify an ENDTIME timestamp value that is valid for
| log truncation. System action:
DB2 startup continues.
DSNJ700I csect_name ERROR ATTEMPTING TO
Operator response:
ACCESS BSDS FOR PEER MEMBER
ID= member-id, MEMBER NAME= Notify the system programmer.
member-name, REASON-CODE=
System programmer response:
reason-code.
Depending on the accuracy of the BSDS value, take one
Explanation:
of the following actions:
DB2 issues this message to identify the peer member v BSDS value is correct: DB2 startup will automatically
ID, and if known, the peer member name associated replace the generic LU name in the SCA with the
correct value. The BSDS for each member of this DB2 the required group restart is completed, start the new
data sharing group must specify this same value for member again.
generic LU name.If any member specifies a different
If this is the very first startup of the group, you must
value for generic LU name, use the change log
start the originating member first before starting any
inventory utility (DSNJU003) to change the generic
other member.
LU name, as described in Utility Guide and Reference..
v BSDS value is not correct: DB2 startup will replace
the generic LU name in the SCA. The SCA value will DSNJ705I csect-name THE DB2 SYSTEM
be incorrect when startup is complete. Take the PARAMETERS SPECIFY DATA
following actions to correct this situation: SHARING, BUT THE BSDS SPECIFIES
NON-DATA SHARING.
– Stop this DB2 subsystem.
– Use the change log inventory utility (DSNJU003) Explanation:
to change the generic LU name of this member, as The system parameters passed on the DB2 start
described in Utility Guide and Reference. command specified data sharing, but the bootstrap data
– Issue START DB2 for this member. START DB2 set (BSDS) did not indicate this DB2 is a data sharing
will correct the generic LU name contained in the member.
SCA.
System action:
216 Messages
DSNJ707E • DSNJ712E
inform the system programmer. sharing group when the data sharing group is in
System Recover Pending mode.
System programmer response:
System action:
If this DB2 should be a member of a data sharing
group, reassemble the system parameters load module DB2 startup terminates.
and specify DSHARE=YES. If this DB2 is not a member
Operator response:
of a data sharing group, execute the installation job
DSNTIJGF, which updates the BSDS for non-data When the data sharing group is no longer in System
sharing. Recover Pending mode, start the new member again.
DB2 issues this message during startup when it detects System action:
that the LOCATION name in the bootstrap data set Command processing terminates unsuccessfully.
(BSDS) does not match the LOCATION name in the
system communications area (SCA) structure. System programmer response:
Depending on the accuracy of the BSDS value, take one If you suspect an error in DB2, refer to Part 2 of
of the following actions: Diagnosis Guide and Reference for information on
identifying and reporting the problem.
v BSDS value is correct: DB2 startup will automatically
replace the LOCATION name in the SCA with the
correct value. The BSDS for each member of this DB2 DSNJ712E csect-name SCA READ FAILURE
data sharing group must specify this same value for ENCOUNTERED.
LOCATION. If any member specifies a different
Explanation:
value for LOCATION, use the change log inventory
utility (DSNJU003) to change the LOCATION name, A failure occurred during command processing
as described in Utility Guide and Reference. attempting to read from the SCA.
v BSDS value is not correct: DB2 startup will replace System action:
the LOCATION name in the SCA. The SCA value
will be incorrect when startup is complete. Take the Command processing terminates unsuccessfully.
following actions to correct this situation: System programmer response:
– Stop this DB2 subsystem.
Obtain SYS1.LOGREC and possible SVC dump for
– Use the change log inventory utility (DSNJU003) analysis.
to change the LOCATION name of this member,
as described in Utility Guide and Reference. Problem determination:
– Issue START DB2 for this member. START DB2 Review the DB2 system console for possible DSN7xxxx
will correct the LOCATION name contained in the and/or SVC dump messages that could relate to this
SCA. problem.
If you suspect an error in DB2, refer to Part 2 of
DSNJ708I csect-name NEW MEMBER START-UP IS Diagnosis Guide and Reference for information on
NOT ALLOWED WHEN THE DATA identifying and reporting the problem.
SHARING GROUP IS IN SYSTEM
RECOVER PENDING MODE
Explanation:
A new data sharing member attempted to join the data
DSNJ713E csect-name SCA WRITE FAILURE DSNJ992I csect-name LOG DATA SET NAME =
ENCOUNTERED. data-set-name
Explanation: Explanation:
A failure occurred during command processing The indicated data-set-name is to be preformatted.
attempting to write to the SCA.
Severity:
System action:
0 (informational)
Command processing terminates unsuccessfully.
System programmer response: DSNJ993I csect-name LOG DATA SET IS NOT A
VSAM DATA SET
Obtain SYS1.LOGREC and possible SVC dump for
analysis. Explanation:
Problem determination: The input log dataset is not a VSAM data set.
Review the DB2 system console for possible DSN7xxxx System action:
and/or SVC dump messages that could relate to this
Processing terminates.
problem.
User response:
If you suspect an error in DB2, refer to Part 2 of
Diagnosis Guide and Reference for information on Use the AMS IDCAMS Service to define the active log
identifying and reporting the problem. data set as a VSAM Linear data set.
Severity:
DSNJ990I csect-name SHOWCB ERROR, RETURN
CODE = error-code 8 (error)
Explanation:
DSNJ994I csect-name VSAM OPEN ERROR,
SHOWCB failed with error-code error-code. An ACBERRFLG = error-code
error-code of 4 means that the log data set was
allocated greater than 4 gigabytes in size, which is not Explanation:
supported. VSAM OPEN failed with the indicated ACB error-code.
System action: System action:
Processing terminates. Processing terminates if the error code is greater than
System programmer response: or equal to 128; otherwise, processing continues
normally.
Follow standard VSAM diagnostic procedure. Refer to
z/OS DFSMS: Macro Instructions for Data Sets. If the log System programmer response:
data set was allocated greater than 4 gigabytes in size, Follow standard VSAM diagnostic procedure. Refer to
reallocate the data set less than 4 gigabytes in size. z/OS DFSMS: Macro Instructions for Data Sets. See also
User response: MVS/DFP™ V3R3 Diagnosis Guide for more information
about the VSAM procedures.
Notify the system programmer.
User response:
Severity:
Notify the system programmer.
8 (error).
Severity:
DSNJ991I csect-name START OF LOG DATA SET 8 (error) if error is greater than or equal to 128;
PREFORMAT FOR JOB job-name otherwise, 4 (warning)
step-name
Explanation: DSNJ995I csect-name VSAM PUT
ERROR,RPLERREG = return-code,
The active log data set preformat utility has started. RPLERRCD = reason-code
Severity: Explanation:
0 (informational) VSAM PUT failed with the indicated return-code and
reason-code.
System action:
218 Messages
DSNJ996I • DSNJ998I
Explanation:
DSNL011I VTAM STOPPING DDF
Abnormal termination of the distributed data facility
(DDF) has started. Explanation:
DSNL008I DDF ABNORMAL TERMINATION The distributed data facility (DDF) -STOP command is
COMPLETE initiated.
Explanation:
DSNL012I VTAM TERMINATING DDF
Abnormal termination of the distributed data facility
(DDF) has completed. Explanation:
System action:
The specified thread is not canceled.
222 Messages
DSNL013I • DSNL017I
System action:
DSNL013I VTAM OPEN ACB FAILED
ERROR=error-code Termination of the DDF is started.
Explanation: Operator response:
VTAM returned a nonzero return code after DB2 Notify the system programmer.
invoked the OPEN ACB macro instruction during
termination of the distributed data facility (DDF). System programmer response:
VTAM return codes for OPEN error conditions are Refer to z/OS Communications Server SNA Programming
defined in z/OS Communications Server SNA to determine the cause of the failure. After the error is
Programming. fixed, issue the -START DDF command.
System action:
Termination of the distributed data facility is initiated. DSNL016I DDF RECORD NOT FOUND IN BSDS
Notify the system programmer. DDF cannot find the DDF communication record in the
BSDS.
System programmer response:
System action:
Determine the cause of the OPEN ACB failure, correct
the error, and issue the -START DDF command. DDF termination process is initiated.
Refer to z/OS Communications Server SNA Programming Notify the system programmer.
for failure analysis during an OPEN macro instruction. System programmer response:
Use the change log inventory to add the DDF
DSNL014I VTAM CLOSE ACB FAILED communication record to the BSDS.
ERROR=error-code
Problem determination:
Explanation:
Collect the following diagnostic item:
VTAM returned a nonzero return code after DB2
v Print the contents of the BSDS using the print log
invoked the CLOSE ACB macro instruction during
map utility.
termination of the distributed data facility (DDF).
VTAM return codes for CLOSE error conditions are
defined in z/OS Communications Server SNA DSNL017I INVALID DDF RECORD FOUND IN
Programming. BSDS REASON = reason-code
System action: Explanation:
Termination of DDF continues. An invalid or incomplete DDF communication record
was found in the BSDS.
Operator response:
System action:
Notify the system programmer.
DDF begins to terminate processing.
System programmer response:
Operator response:
Determine the cause of the failure, fix the error
condition, and then issue the -START DDF command. Notify the system programmer.
Problem determination: | System programmer response:
Refer to z/OS Communications Server SNA Programming | See the information for the associated reason-code. Use
for failure analysis during a CLOSE macro instruction. | the change log inventory utility to correct the DDF
| communication record in the BSDS.
DSNL015I VTAM SETLOGON FAILED Problem determination:
RTNCD=error-code FDBK2=open-flags
Collect the following diagnostic item:
Explanation: v Print the contents of the BSDS using the print log
VTAM returned a nonzero return code after DB2 map utility.
invoked the SETLOGON macro during initialization of
the distributed data function (DDF). VTAM return
codes are defined in z/OS Communications Server SNA
Programming.
luname
DSNL018I VSAM ERROR READING DDF
A 1- to 8-character luname.
RECORD IN BSDS RPLERRCD=error-
code luwunique
A 12-character hex number.
Explanation:
A VSAM GET command was issued that resulted in a Luname and luwunique are separated by a ’.’ delimiter.
nonzero return code. RPLERRCD ’error-code’ is the Netid is optional. If netid is specified, then netid and
VSAM return code. luname are separated by a ’.’ delimiter. If netid is not
specified, then the ’.’ delimiter before luname is not
System action:
present.
Termination of the distributed data facility (DDF) is
System action:
initiated.
The specified thread is not canceled.
Operator response:
User response:
Notify the system programmer.
Determine the correct logical-unit-of-work ID of the
System programmer response:
distributed thread that is to be canceled and reissue the
Determine the cause of the failure, fix the error command.
condition, and issue the -START DDF command.
Problem determination:
The cause of the failure is dictated by the VSAM return
Determine the correct value. The -DISPLAY THREAD
code. The BSDS may have to be recovered by using a
command can be used to display all distributed
backup copy.
activity.
Problem determination:
Refer to the appropriate VSAM publications. DSNL021I command ACCEPTED
Explanation:
DSNL019I VTAM DOES NOT SUPPORT APPC
The ’command’ command has been accepted and
FUNCTIONS
asynchronous processing of ’command’ has been
Explanation: initiated. The command can only be -START or -STOP
the distributed data facility.
The installed release of VTAM does not support the
advanced program-to-program communications (APPC) System action:
application program interface (API). The APPC API bit
The command was accepted and asynchronous
is not set in the VTAM function-list vector in the
processing has been initiated.
access-method-support vector list.
System action:
DSNL022I csect-name DDF THREAD
Termination of the distributed data facility (DDF) is logical-unit-of-work-id WAS PREVIOUSLY
initiated. CANCELED
Operator response: Explanation:
Notify the system programmer. A command to cancel the distributed data facility
(DDF) thread logical-unit-of-work-id was previously
System programmer response:
issued. Either the CANCEL DDF THREAD or the
Determine whether the installed release of VTAM CANCEL THREAD command was entered. The thread
supports the APPC API. If VTAM does not support the is currently being canceled. The CANCEL command
APPC API, a VTAM release that supports the APPC terminates a thread only if the thread is processing in
API must be installed before the DDF can be started. DB2 or is currently suspended by DB2. The thread
might not be processing in DB2 in these situations:
DSNL020I KEYWORD ’THREAD’ PARAMETER v The thread is processing in the application and has
parameter FORMAT IN ERROR not made a request to DB2. The DISPLAY THREAD
command indicates this.
Explanation: v The user placed the thread on an MVS resource
The parameter value specified for the using the ENQUE command. The CANCEL
logical-unit-of-work ID on the CANCEL DDF THREAD command has no effect on the thread until ENQUE
has an invalid format. The correct form is completes and the thread returns to DB2.
’netid.luname.luwunique’, where: v The thread is processing in VTAM and is waiting for
a response from a partner. The DISPLAY THREAD
netid A 1- to 8-character network ID.
224 Messages
DSNL023I • DSNL026I
DETAIL command indicates this. In this case the 2. Console dump of DB2 address spaces (ssnmDBM1,
thread does not terminate until VTAM returns to ssnmMSTR, ssnmDIST), and VTAM at the server
DB2. VTAM commands, which will terminate the site.
session or LU, can be used to cause VTAM to return 3. SYSLOG from requesting and server sites.
to DB2.
4. LOGREC from requesting and server sites.
DSNL023I DDF IS ALREADY IN THE PROCESS If an indefinite inconsistency is suspected, use the
OF STARTING CANCEL DDF THREAD command to terminate the
thread. If CANCEL DDF THREAD fails to terminate
Explanation:
the agent, use VTAM commands to terminate the
The distributed data facility (DDF) was starting when thread conversations.
the -START DDF or -STOP DDF command was issued.
Problem determination:
System action:
Use the DB2 DISPLAY THREAD command with
The issued command is not executed. DETAIL option at each DB2 subsystem to display
information about the agent and its conversations. Use
VTAM commands to display additional information
DSNL024I DDF IS ALREADY IN THE PROCESS
about the conversations being used by the thread and
OF STOPPING
also about network conditions.
Explanation:
Collect the following diagnostic items:
The distributed data facility (DDF) was stopping when v Console output from the system on which the job
the -STOP DDF or -START DDF command was issued. was run, and a listing of the SYSLOG data set for the
System action: period of time spanning the failure.
v SVC dump (or system dump), taken to
The -START or -STOP DDF command is not executed. SYS1.DUMPxx data set, as result of an
operator-initiated dump command or SLIP trap exit.
DSNL025I A DISTRIBUTED AGENT FOR v Listing of SYS1.LOGREC data set, obtained by
luw-id=token EXISTS AT THIS executing IFCEREP1.
LOCATION BUT NOT AT SITE WITH
LOCATION location AND LU luname .
Explanation:
DSNL026I LUW-ID luw-id=token APPEARS TO BE
The DDF error monitor has detected that a distributed SUSPENDED PARTNER LOCATION
agent exists at this location but not at the named location PARTNER LU luname
partner location.
Explanation:
Where
The DDF error monitor has detected that a distributed
luw-id=token agent with the specified ’luw-id’ at this location and at
The logical unit of work ID of the thread the named partner ’location’ may be suspended
followed by an ’=’ sign and a token which indefinitely.
may be used in place of ’luw-id’ in any DB2
command that accepts ’luw-id’ as input. Where
location luw-id=token
The location name of the partner site where a The logical unit of work ID of the thread
thread with the same ’luw-id’ does not exist. followed by an ’=’ sign and a token which
may be used in place of ’luw-id’ in any DB2
luname command that accepts ’luw-id’ as input.
The 8-character LUNAME of the partner
location. location
The location name of the partner site where a
Operator response: thread with the same ’luw-id’ exists.
Determine if the inconsistency is due to network luname
conditions or a DB2 error. If a DB2 error is suspected, The 8-character LUNAME of the partner
acquire documentation to diagnose the problem. location.
1. Console dump of DB2 address spaces (ssnmDBM1, Operator response:
ssnmMSTR, ssnmDIST), VTAM, and user’s address
space at the requesting site. Determine if the inconsistency is due to network
conditions or a DB2 error. If a DB2 error is suspected,
acquire documentation to diagnose the problem.
1. Console dump of DB2 address spaces (ssnmDBM1, value which may be used in any DB2
ssnmMSTR, ssnmDIST), VTAM, and hung user’s command that accepts luw-id as input.
address space at the requesting site.
thread-info
2. Console dump of DB2 address spaces (ssnmDBM1, Thread-info contains additional identifiers that
ssnmMSTR, ssnmDIST), and VTAM as the server define more specific information regarding the
site. identity of the thread.
3. SYSLOG from requesting and server sites.
In many distributed configurations, the
4. LOGREC from requesting and server sites. primary authorization-ID used with DB2 is not
necessarily the user-ID of the end user.
If an indefinite inconsistency is suspected, use the
CANCEL DDF THREAD command to terminate the The following identifiers, separated by a
thread. If CANCEL DDF THREAD fails to terminate colon(:), are provided:
the agent, use VTAM commands to terminate the v The primary authorization-ID associated
thread conversations. with the thread.
Problem determination: v Work station name of the end user’s work
station. An asterisk (*) indicates that it is not
Use the DB2 DISPLAY THREAD command with relevant to the thread or was not provided
DETAIL option at each DB2 subsystem to display by the client.
information about the agent and its conversations. Use
v End user’s user-ID. An asterisk (*) indicates
VTAM commands to display additional information
that it is not relevant to the thread or was
about the conversations being used by the thread and
not provided by the client.
also about network conditions.
v Application name of the end user’s
Collect the following diagnostic items: application. An asterisk (*) indicates that it
v Console output from the system on which the job is not relevant to the thread or was not
was run, and a listing of the SYSLOG data set for the provided by the client.
period of time spanning the failure.
abnd The abend code or zeros if the abend code is
v SVC dump (or system dump), taken to indeterminate.
SYS1.DUMPxx data set, as result of an
operator-initiated dump command or SLIP trap exit. reason The DB2 reason code or zeros if the reason
code is indeterminate.
v Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1. Problem determination:
. Gather appropriate diagnostic information (refer to the
System Programmer Response section of the abend
reason code specified in this message if applicable).
DSNL027I dis-agent-type DISTRIBUTED AGENT
Refer to DSNL028I message(s) for the names of the
WITH LUW-ID luw-id=token
other location(s).
THREAD-INFO thread-info RECEIVED
ABEND=abnd REASON=reason
| DSNL028I luw-id=token ACCESSING DATA
Explanation:
| preposition LOCATION location nettype
A distributed agent has abended at this location. This | netvalue
message will be followed by zero or more occurrences
| Explanation:
of DSNL028I, each of which describes a remote location
where the distributed agent also exists and where | This message follows DSNL027I and identifies a remote
diagnostic information might also need to be collected. | location where work might have been occurring for the
This message is informational and with the DSNL028I | distributed thread. This message is informational and
message(s) identifies the remote locations where | with the DSNL027I message identifies a remote location
diagnostic information may have to be collected. | where diagnostic information might have to be
| collected.
Where
| luw-id=token
dis-agent-type
| The logical unit-of-work ID of the thread
’REQUESTING’ if the thread that abended is
| followed by an ’=’ sign and a token which
an allied thread that has distributed activity
| may be used in place of ’luw-id’ in any DB2
and SERVER if the thread that abended is a
| command that accepts ’luw-id’ as input.
database access thread.
luw-id=token
The logical-unit-of-work ID of the thread
followed by an ’=’ sign and a 5 digit token
226 Messages
DSNL029I • DSNL031I
| LU -- indicates that VTAM is used to v Console output from the system on which the job
| connect to the remote site. was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
| IPADDR -- v Dynamic dump, taken to SYS1.DUMPxx data set, by
| indicates that TCP/IP is used to DB2 (04E and 04F abends).
| connect to the remote site.
v Listing of SYS1.LOGREC data set, obtained by
| netvalue executing IFCEREP1.
| The network address of the remote location.
| netvalue can be blank. .
228 Messages
DSNL033I • DSNL034E
destination, then the same message recurs later Determine the cause of the failure. Correct the
(along with trace record) when the statistics condition and restart DDF using the -START DDF
class is directed to the resident table as its command.
permanent destination instead of SMF or GTF.
Problem determination:
System action:
If an abend is associated with the failure, a dump
An alert was generated and the system wrote a trace might have been provided. LOGREC will also contain
record with IFCID=ifcid to statistics class 4 that can be information about the abend.
used to diagnose the problem.
Operator response: DSNL034E DDF CANNOT BE STARTED
BECAUSE OF BSDS
Notify the system programmer for analysis.
INCONSISTENCIES, ORIGINAL
System programmer response: LUNAME=luname1, BSDS
LUNAME=luname2, ORIGINAL
Determine the destination of statistics class 4 and locate LOCATION=location1, BSDS
and print the trace record with SEQUENCE LOCATION=location2
NUMBER=seq-no. The reason code is described in
Codes. The description of the reason code can be used Explanation:
in conjunction with the publication Distributed
The LUNAME or the LOCATION name stored in the
Relational Database Architecture Reference to
bootstrap data set (BSDS) was changed since the
determine the type of DRDA exception that has been
distributed data facility (DDF) was last started, but
detected. Use the procedures described in Diagnosis
DDF still has resynchronization responsibility with one
Guide and Reference to determine the problem and
or more partner logical units using the old LUNAME
which system is responsible.
and LOCATION name. Both the original and current
BSDS values of LUNAME and LOCATION name are
DSNL033I csect-name DDF TERMINATION displayed.
SCHEDULED DUE TO DETECTION
luname1
OF ABEND abend REASON reason
The LUNAME required for resynchronization
Explanation:
luname2
A severe error was detected during DDF processing. The LUNAME currently stored in the BSDS
DDF processing can no longer continue so DDF
location1
termination has been scheduled. ’Csect-name’ is the
The LOCATION name required for
DB2 module that detected the condition and requested
resynchronization
DDF termination.
location2
The abend and reason might also contain additional
The LOCATION name currently stored in the
information about the cause.
BSDS
abend The abend code or zeros if no abend is
System action:
associated with the termination of DDF.
DDF cannot be started until the inconsistencies are
If the abend was a DB2 04E abend, the DB2
corrected.
reason code will contain additional
information about the abend. Operator response:
reason The DB2 reason code or zeros if no DB2 Inform the database administrator.
reason code is associated with the termination
Database Administrator Action: You have the
of DDF.
following options, depending on whether there is a
If no abend is associated with the problem, the requirement to change the LUNAME or LOCATION
reason code describes the cause for the name in the BSDS:
termination. v If the names were changed in error, use the change
System action: log inventory (DSNJU003) utility to change the
LUNAME and/or LOCATION name back to the
Termination of the distributed data facility (DDF) is correct value. Then START DDF.
initiated.
v If the name must be changed, you must first remove
Operator response: all of the resynchronization responsibility that DB2
had using the old names. You can purge this
Notify the system programmer for analysis. information, allow automatic resynchronization to
System programmer response: take place, or use a combination of both.
You can purge resynchronization information by v Issue the STOP DDF MODE(FORCE) command. The
using the RESET INDOUBT command with the indoubt thread remains indoubt and can be resolved
FORCE option. You can purge all information by using automatic resynchronization after DDF is
regardless of partner name (LOCATION (*)), or you started again, or it can be resolved manually as
can selectively purge by specifying a location name. described above.
DDF does not have to be started to use this
command. You can use the DISPLAY THREAD
DSNL036I DDF THREAD logical-unit-of-work-id
command to generate a report of indoubt threads.
SPECIFIED IS INDOUBT
This report indicates all resynchronization
responsibility known by DB2. Explanation:
If you do not purge the resynchronization A database access thread that is indoubt cannot be
information, or only selectively purge, and you want canceled by using the -CANCEL DDF THREAD
automatic resynchronization to occur before changing command.
the names, you must first use the change log
inventory (DSNJU003) utility to change the System action:
LUNAME and/or LOCATION name back to the
The specified thread is not canceled.
correct value. Then START DDF. At this point,
automatic resynchronization begins. You can monitor Operator response:
the progress by periodically using the DISPLAY
Use the -DISPLAY THREAD TYPE(*) command to
THREAD command for TYPE (INDOUBT) threads.
display all distributed activity.
Resynchronization does not complete until all needed
communications paths are available and all needed
partner logical units are available. If you cannot wait DSNL037I csect-name RESET GENERICLU lu
for availability, use the RESET INDOUBT command SUCCESSFUL
with the FORCE option to purge information
associated with unavailable partners. Explanation:
The RESET GENERICLU command successfully purged
DSNL035I DDF CANNOT BE STOPPED the VTAM sysplex information from shared memory.
BECAUSE AN INDOUBT DATA BASE lu The value supplied on the RESET
ACCESS THREAD EXISTS GENERICLU command
Explanation: System action:
DDF is the connection manager for a database access The VTAM information contained in the sysplex shared
thread (DBAT) that is indoubt. A STOP DDF memory for the indicated LU is purged.
MODE(QUIESCE) command is rejected until the
indoubt logical unit of work is resolved.
DSNL038E csect-name RESET GENERICLU lu
System action: FAILED DUE TO VTAM RTNCD=xx
DDF is not stopped. and FDB2=yy
v Use the DISPLAY THREAD TYPE(INDOUBT) yy The hexadecimal value of the VTAM FDB2
command to find the LOCATION that has field
coordinator responsibility for the indoubt LUW.
System action:
Contact that location and determine whether the
LUW committed or aborted. Then use the RECOVER VTAM was not able to purge the sysplex shared
INDOUBT command to cause the indoubt DBAT to memory information for the indicated LU.
be resolved with the same decision.
System programmer response:
After the indoubt thread is resolved, reissue the
STOP DDF command. Refer to z/OS Communications Server SNA Programming
230 Messages
DSNL039E • DSNL043I
for the meaning of the VTAM RTNCD and FDB2 System action:
values.
The DB2 GENERIC LUNAME installation option is
ignored.
DSNL039E csect-name RESET GENERICLU lu
System programmer response:
FAILED DUE TO ACTIVE VTAM
SESSIONS If the DB2 GENERIC LUNAME is required, install
VTAM Version 4 Release 2 or a later release.
Explanation:
The RESET GENERICLU command was not accepted
DSNL042E csect-name DB2 SYSPLEX TP WAS
because one or more active VTAM sessions exist to the
INVOKED BY LU lu, BUT REQUIRED
indicated LU. All VTAM sessions must be terminated
MVS LEVEL IS NOT INSTALLED
before the command is accepted.
Explanation:
lu The value supplied on the RESET
GENERICLU command A request for the DB2 sysplex transaction program (TP)
was received by a DB2 server that is a member of a
System action:
data sharing group. The DB2 sysplex TP is used by the
The command is rejected. requesting systems to determine which DB2 systems
within the group are currently available for DDF
System programmer response:
conversations.
Terminate the VTAM sessions to the remote LU and
The DB2 sysplex TP uses Work Load Manager (WLM)
reissue the -RESET GENERICLU command.
functions in MVS Version 5 Release 2 or a later release
to balance distributed workload among the DB2
DSNL040E csect-name RESET GENERICLU lu systems in the group. Because the required MVS release
FAILED DUE TO INDOUBT is not installed or DB2 is not registered with WLM, the
RESOLUTION INFORMATION DB2 sysplex TP is not able to provide the requested
information.
Explanation:
lu The name of the LU in the network that
The RESET GENERICLU command was not accepted invoked the DB2 sysplex TP
because information is currently being retained for
resolution of indoubt threads for the indicated partner System action:
LU. The DISPLAY THREAD TYPE(INDOUBT)
The DB2 sysplex TP returns the NETID.LUNAME of
command can be used to view this information.
the local DB2 system as the only available DB2 server
lu The value supplied on the RESET in the group. The requester is not provided the names
GENERICLU command of other DB2 systems in the group, so all sessions from
the requester are routed to the local DB2 server.
System action:
System programmer response:
The command is rejected.
Install MVS Version 5 Release 2 or a later release if you
System programmer response: want to have the DB2 sysplex TP return multiple
Make sure that all indoubt threads at the remote site NETID.LUNAME values to the requester or refer to the
are resolved before issuing the RESET GENERICLU DSNL044I on why DB2 could not register with WLM.
command.
When DB2 performs automatic indoubt thread DSNL043I csect-name RESET GENERICLU luname
resolution, the information contained in the DISPLAY INVALID
THREAD TYPE(INDOUBT) display is purged at the Explanation:
end of the resynchronization process.
The luname value specified is invalid. The correct
If required, use the -RESET INDOUBT command to format is either a
manually purge the indoubt resolution information.
v 1 to 8 character luname, or
v 1 to 8 character network ID, a period, and a 1 to 8
DSNL041E csect-name DB2 GENERIC LU NAME character luname.
REQUESTED, BUT REQUIRED VTAM
LEVEL IS NOT INSTALLED System action:
Explanation: The parameter is ignored. Processing continues with
the next luname, if any.
The DB2 GENERIC LUNAME installation option was
specified. This option requires VTAM Version 4 Release User response:
2 or a later release.
Determine the correct luname and reissue the Refer to MVS/ESA Programming: Workload Management
command. Services for the meaning of the MVS RETCODE and
RSNCODE values.
DSNL044I csect-name MVS macname MACRO
FAILED WITH RETCODE=xx AND | DSNL045I csect-name ICSF macname FUNCTION
RSNCODE=yy | FAILED WITH RETCODE=return-code
| AND RSNCODE=reason-code
Explanation:
| Explanation:
An MVS Workload Manager (WLM) macro returned an
unexpected return code, which is described by the | An Integrated Cryptographic Service Facility (ICSF) call
indicated RETCODE and RSNCODE values. DDF uses | returned an unexpected return code, which is described
MVS Workload Manager macros to obtain data sharing | by the indicate RETCODE and RSNCODE values. DDF
sysplex routing information for incoming DDF work | uses ICSF calls to create connection keys, to generate a
requests, and to establish an MVS enclave for the | shared private key, to encrypt data, and to decrypt
execution environment of the distributed thread. | data.
macname | macname
The name of the MVS macro that returned the | The name of the ICSF call that returned the
unexpected return code. The possible values | unexpected return code. The possible values
are: | are:
v IWMSRSRG: Register with WLM for sysplex | v CSNERNG: Random Number Generate
routing. | v CSNECKM: Multiple Clear Key Import
v IWMSRSRS: Request sysplex routing | v CSNFPKB: Key Token Build
information.
| v CSNFPKE: Key Encrypt
v IWMSRDRS: Deregister with WLM for
sysplex routing.
| v CSNEENC: Encipher data.
232 Messages
DSNL047I • DSNL069I
| If the cryptographic service facility is not installed, | return_value, return_code. reason_code, and
| install it before requesting encryption functions. If it is | saf_error_message.
| configured, verify that the ICSF service is available and
| working correctly.
DSNL065I csect-name CURRENT DDF STATE
| ICSF System Programmer’s Guide DOES NOT PERMIT STOP DDF
MODE(SUSPEND)
System action:
DSNL082I LOCATION LUNAME GENERICLU
DDF is attempting to terminate all active database
access threads. Explanation:
This message is issued as a result of the DISPLAY DDF
DSNL080I csect DISPLAY DDF REPORT command. This message displays the column headings
FOLLOWS: for the DSNL083I message that follows
Explanation: System action:
This message is issued as a result of the DISPLAY DDF Processing continues normally.
command. This message is always generated as the title
for the DISPLAY DDF command report output. It
precedes the other messages generated by this
command.
System action:
234 Messages
DSNL083I • DSNL084I
| A value of 0 (zero) indicates that a secure SQL | to use TCP/IP network protocols (see tcpport
| listener port has not been specified and DDF is | in the DSNL084I message), DDF has not yet
| not configured to accept secure inbound | been started, or TCP/IP initialization has
| connections using the SSL protocol through | failed.
| this port number. If the secure port has not
System action:
| been specified, remote connections can still use
| the DRDA PORT, and use SSL on it, but DDF Processing continues normally.
| will not validate if the connection utilizes SSL
| protocol or not.
| DSNL086I domain-type DOMAIN=domain-name
| A value of ’-NONE’ indicates that DB2 will
| not accept connections on this port. The reason | Explanation:
| for not accepting connections for the port | This message is issued as a result of the DISPLAY DDF
| might be due to specifying 0 (zero) for the | command. This message displays a TCP/IP domain
| DSN6SYSP MAXDBAT installation parameter | name associated with DDF.
| defined in DSNZPARM. For more information,
| see the MAX REMOTE ACTIVE specification | domain-type
| in the DSNTIPE installation panel in the DB2 | The type of domain name that is displayed,
| Installation Guide. The current MAX REMOTE | which can be one of the following:
| ACTIVE value can also be seen in the MDBAT | SQL The domain name is used to accept
| value of the DSNL090I message, which is | inbound SQL requests from remote
| included in the DISPLAY DDF DETAIL report. | partners. The tcport value of message
| This information also appears in message | DSNL085I message provides the port
| DSNL004I when DDF is started. See the | number that is used to accept
| DSNL004I message for additional information. | inbound connections.
236 Messages
DSNL087I • DSNL090I
| Database Administrator Action: Inform the database This message is issued as a result of the DISPLAY DDF
| administrator at the coordinator ’location’ and at the DETAIL command. This message displays some of the
| participant ’location’ of the problem. system parameter information associated with DDF.
| Correcting the damage at the participant is not an easy dt DDF thread value. It indicates the ″DDF
| task. Since the time of the heuristic action, the data that THREADS″ value specified in the DSNTIPR
| was committed using manual means might have been installation panel.
v A - DDF is configured with DDF THREADS | throughput may have been affected, in which
ACTIVE | case it might be appropriate to consider
v I - DDF is configured with DDF THREADS | increasing the maxdbat value. See adbat and
INACTIVE | DSNL090I mdbat for additional information.
| Also note that the quedbat counter is only reset
condbat | at restart for this DB2 subsystem.
Maximum number of inbound connections as
determined by the ″MAX REMOTE | inadbat
CONNECTED″ value in the DSNTIPE | Current number of inactive DBATs (previously
installation panel. | called type 1 inactive threads). This value only
| applies if the dt value specified in the
mdbat Maximum number of database access threads | DSNL090I message indicates that DDF
as determined by the ″MAX REMOTE | INACTIVE support is enabled. Any database
ACTIVE″ value in the DSNTIPE installation | access threads reflected here can also be
panel. This effectively determines the | observed in the DISPLAY THREAD
maximum number of active slots. That is, the | TYPE(INACTIVE) command report.
maximum number of concurrent active
database access threads that could potentially conqued
be executing SQL. Current number of connection requests that
have been queued and are waiting to be
System action: serviced. This value only applies if the dt
Processing continues normally. value that is specified in the DSNL090I
message indicates that DDF INACTIVE
support is enabled.
DSNL092I ADBAT=adbat QUEDBAT=quedbat
INADBAT=inadbat CONQUED=conqued These connections can represent newly
attached connections, or inactive connections
Explanation: for which a new request has arrived from the
client (connections that were represented in
This message is issued as a result of the DISPLAY DDF
the inaconn value of the DSNL093I message).
DETAIL command.
| These requests cannot be processed when one
adbat Current number of database access threads
| of the following conditions occur:
(DBATs). This includes DBATs that are actively
associated to work for remote connections and | v The maximum number of database access
″disconnected″ DBATs (see DSNL093I dscdbat | threads has been reached (adbat value is
for more information). This value increases as | equal to or greater than the DSNL090I mdbat
new DBATs get created or when inactive | value) and there are no disconnected
DBATs become active (see inadbat description | database access threads to process the
for more information) . The value decreases as | request (see DSNL093I dscdbat value).
DBATs terminate or become inactive (see | Processing continues for these conqued
inadbat), or as ″disconnected″ DBATs (see | connections when another active database
DSNL093I dscdbat) terminate. When this value | access thread releases its slot by either
reaches or exceeds the DSNL090I mdbat value, | terminating or by moving to the inactive
then newly attached connections, or new work | state (see the inadbat value or the DSNL093I
on existing inactive connections (see DSNL093I | inaconn value).
inaconn for more information) or threads | v The DDF is suspended or suspending (see
(inadbat), might may need to be queued (see | DSNL081I status value). Processing
quedbat for more information) if there are no | continues when the DDF is started
″disconnected″ DBATs (see DSNL093I dscdbat) | (resumed).
available that can be used to service the work.
System action:
quedbat
| This value reflects a cumulative counter that is Processing continues normally.
| always incremented when the DSNL090I mdbat
| limit has been reached. The quedbat value is DSNL093I DSCDBAT=dscdbat INACONN=inaconn
| equal to the cumulative number of newly
| attached connections, or new work on inactive Explanation:
| connections (see DSNL093I inaconn), or new This message is issued as a result of the DISPLAY DDF
| work on inactive DBATs (see inadbat) that had DETAIL command.
| to wait for a DBAT to become available to
| service the new work. This value is identical dscdbat
| to the QDSTQDBT statistical value and a Current number of disconnected database
| non-zero value suggests that performance and access threads. This value only applies if the dt
238 Messages
DSNL099I • DSNL201I
value specified in the DSNL090I message This message indicates that the DISPLAY DDF report
indicates that DDF INACTIVE support is successfully completed.
enabled. This value is effectively the number
System action:
of DBAT pool threads. DBAT pool threads are
the database access threads that are available Processing continues normally.
to service queued connections requests (see
DSNL092I conqued value). Database access
threads reflected here are also accounted for in DSNL200I DISPLAY LOCATION REPORT
the DSNL092I adbat value. FOLLOWS-
DSNL202I location prdid requesters servers convs DSNL203I L203-SYSTASK SESSID A ST TIME
Explanation: Explanation:
This message lists the status of communications This message forms the heading for the listing of DB2
between a remote location and this DB2 subsystem. system threads that communicate with other locations.
Information about the status appears in the following It follows each occurrence of message DSNL202I if the
list: DETAIL keyword of the DISPLAY LOCATION
command is used. This message is followed by one or
Item Description
more occurrences of message DSNL204I, which
LOCATION describe the DB2 system threads communicating with
| A name for the remote site. the remote site and its conversation information. Items
in this part of the heading are:
PRDID Identifies the database product at the location
in the form nnnvvrrm. SYSTASK
v nnn - Identifies the database product (e.g., Heading that describes the DB2 system thread
DSN=DB2). SESSID
v vv - Product version. Heading for the associated conversation
v rr - Product release. identifiers
240 Messages
DSNL205I • DSNL207I
the remote DB2 location. DB2 uses these with the partner (CNOS) prior to
conversations internally. The conversations conversation allocation.
created are one directional. That is, DB2 has
D Conversation in deallocation.
a conversation that it uses to send
information to the remote site, and another R Receiving.
that it uses to receive information from the
remote site. A DB2 system thread is created S Sending.
to manage ’outbound’ (used for sending) Blank otherwise.
conversations and another to manage
’inbound’ (used for receiving) conversations. time The timestamp (yydddhhmmssth) of the last
message sent or received on the conversation.
v RESYNC
A conversation used to resynchronize a unit The message number and subsystem recognition
of work that encountered a previous thread character are not included in this message. However,
or communication error. There can be one L204 is included in the message text to identify the
entry representing each thread needing message.
resynchronization with the remote site.
System action:
sessid Two possible values can appear in this
column: Command processing continues
1. For VTAM network connections, this
column contains the VTAM-defined session DSNL205I DISPLAY LOCATION REPORT
instance identifier of the session on which COMPLETE
the conversation is executing. If the session
identifier is not applicable, this field Explanation:
contains zeros. This message follows messages DSNL200I, DSNL201I,
VTAM does not supply the entire session and DSNL202I and indicates that the -DISPLAY
id to DB2. The first two digits of the LOCATION report successfully completed.
session id are incorrect. Therefore, the
The message number and subsystem recognition
session id, as presented in this message, is
character are not included in this message.
not acceptable in VTAM commands. Use
the VTAM DISPLAY NET,ID=db2- System action:
luname,SCOPE=ACT command to obtain
Processing continues normally.
the full session ID. The DISPLAY NET
command lists all sessions (SID) for the
DB2 logical unit. Scan the DISPLAY NET DSNL206I csect-name named-command COMMAND
output for the complete SID. INVALID, reason
2. For TCP/IP network connections, this | Explanation:
column contains a string of the form
’local:remote’, where: | The named-command could not be processed due to the
| displayed reason.
local -- specifies the local DB2 system’s
TCP/IP port number System action:
remote -- Processing continues normally.
specifies the remote partner’s
TCP/IP port number
DSNL207I DISPLAY LOCATION NO LOCATIONS
active One of the following: FOUND
N The conversation is active in the Explanation:
network.
The -DISPLAY LOCATION command was unable to
W The conversation is suspended in DB2 find any locations associated with the specified list of
waiting for VTAM or TCP/IP locations. If all locations were specified, there is no
notification that the function is distributed activity.
complete.
System action:
Blank, otherwise.
Processing completed normally.
status Status of the conversation:
User response:
A Conversation in allocation.
If a location list was specified, reissue the -DISPLAY
C Session limits are being negotiated LOCATION command using the LOCATION(*)
242 Messages
DSNL401E • DSNL402I
v Any resources updated at the participant were occurred for the logical unit of work with
committed. LUWID=’luwid’. DB2 was the coordinator for the
v Updated resources at this DB2 were rolled back. logical unit of work and made the decision to abort the
database updates made by ’luwid’. At ’location’ a
| location heuristic decision was made to COMMIT the updates
| The field contains one of the following: made by ’luwid’.
| v The requester’s relational database name
Information about the heuristic damage continues to
| (location name)
appear in the DISPLAY THREAD TYPE(INDOUBT)
| v The requester’s VTAM LU name (<luname>) report until it is purged with the RESET INDOUBT
| v The requester’s IP address command.
luwid=token
The global logical unit of work id and the DSNL403I INDOUBT THREAD RESOLUTION
local token that identify the thread. WITH PARTICIPANT location SHOWS
HEURISTIC DAMAGE FOR luwid=token
seq-no The IFCID sequence number associated with - REMOTE ABORT VERSUS LOCAL
the trace record. The sequence number is COMMIT. INFORMATION
printed in hexadecimal format. If the sequence RECORDED IN TRACE RECORD
number is zero, then IFCID 207 was not active WITH IFCID=207 AND IFCID
or it was active with a destination of the SEQUENCE NUMBER=seq-no
resident trace table only. IFCID 207 is a
member of statistics class 4, which has a Explanation:
default destination of SMF.
DB2 has coordinator responsibility for the logical unit
of work identified by ’luwid=token’. Resolution with a
| If the location specified refers to a DB2 Linux®, UNIX®, participant shows heuristic damage occurred. The
| and Windows® system that is running at the Version 9.1 participant identified by ’location’ manually resolved
| level or later, and that server location has enabled the indoubt thread identified by ’luwid=token’. The
| access to non-DB2 databases through the Federated action taken was to abort the thread. This is
| Database or Information Integrator capability, then any inconsistent with the commit decision of the
| updates made to that downstream non-DB2 database coordinator.
| will be processed under the control of the DB2 Version
| 9.1 for Linux, UNIX, and Windows unprotected update v The application was told that commit succeeded.
| capability. This permits changes to be made to this v Any resources updated at the participant were rolled
| downstream non-DB2 database, even when the changes back.
| were being requested through applications running v Updated resources at this DB2 were committed.
| under two-phase commit or protected update control,
| such as CICS and IMS. During phase one of commit | location
| processing, the DB2 V9.1 for Linux, UNIX, and | This field contains one of the following:
| Windows server will have actually committed the | v The requester’s relational database name
| changes to the downstream non-DB2 database by the | (location name)
| time it replies to this DB2 that it is prepared to accept a | v The requester’s VTAM LU name (<luname>)
| commit decision from. However, if during phase one
| commit negotiation with other downstream database
| v The requester’s IP address
| servers and other coordinated resource managers from luwid=token
| CICS or IMS, the decision is made to abort the unit of The global logical unit of work id and the
| work, this will result in heuristic damage to the data at local token that identify the thread.
| the non-DB2 database downstream of the DB2 V9.1 for
| Linux, UNIX, and Windows server. No attempts will be seq-no The IFCID sequence number associated with
| made to resync with the identified remote location the trace record. The sequence number is
| server, and a DB2 indoubt thread will not be left in printed in hexadecimal format. If the sequence
| DB2 to reflect this issue. number is zero, IFCID 207 was not active or it
was active with a destination of the resident
System action: trace table only. IFCID 207 is a member of
statistics class 4, which has a default
Alert A004 is generated. A trace record whose
destination of SMF.
IFCID=207 is written. Indoubt resolution with the
participant completes. System action:
System programmer response: Alert A004 is generated. A trace record with IFCID 207
is written. Indoubt resolution with the participant
Call the database administrator.
completes.
Database Administrator Action: Inform the database
System programmer response:
administrator at ’location’ that heuristic damage
244 Messages
DSNL404E • DSNL405I
Call the database administrator. Database Administrator Action: DB2 does not attempt
to automatically resolve the indoubt thread. The
Database Administrator Action: Inform the database
indoubt thread must be manually resolved. The commit
administrator at ’location’ that heuristic damage
or abort decision made at the coordinator must be
occurred for the logical unit of work with
determined so that the same decision can be made at
LUWID=’luwid’. DB2 was the coordinator for the
this participant DB2.
logical unit of work and made the decision to
COMMIT the database updates made by ’luwid’. At Contact the database administrator at the coordinator
’location’ a heuristic decision was made to back out location to determine whether the thread with
(ABORT) the updates made by ’luwid’. LUWID=luwid committed or aborted.
Information about the heuristic damage continues to If the coordinator system is another DB2, the following
appear in the DISPLAY THREAD TYPE(INDOUBT) steps can be taken at the DB2 coordinator to determine
report until it is purged with the RESET INDOUBT the commit or abort decision.
command. 1. If the coordinator DB2 system is running and a DB2
conditional restart was not performed since the
DSNL404E PROTOCOL ERROR DURING error was detected at this (the participant) location,
INDOUBT THREAD RESOLUTION ask the database administrator at the DB2
WITH COORDINATOR location coordinator location to issue one of the following
LUWID=luwid=token INFORMATION DISPLAY THREAD TYPE(INDOUBT) commands:
RECORDED IN TRACE RECORD v A -DISPLAY THREAD TYPE(INDOUBT), using
WITH IFCID=206 AND IFCID the LOCATION keyword and specifying the
SEQUENCE NUMBER=seq-no location name of the local DB2.
Explanation: v A -DISPLAY THREAD TYPE(INDOUBT)
LUWID(luwid)
DB2 has participant responsibility for the logical unit of
work identified by ’luwid=token’. The DB2 thread If a thread with LUWID=luwid appears in the
associated with the logical unit of work is indoubt. A display, then the display also includes the commit
protocol error occurred during indoubt resolution with or abort decision. If no thread with LUWID=luwid
the coordinator identified by ’location’. appears in the display, the thread was aborted.
2. If the DB2 coordinator is down, or if a conditional
location
restart was performed there, ask the database
Either the relational database name
administrator at the DB2 coordinator to run
(location-name) or the logical unit name
DSN1LOGP, specifying SUMMARY(ONLY) FILTER
(<luname>) of the coordinator.
LUWID(luwid). The output from DSN1LOGP
luwid=token includes the commit or abort decision.
The global logical unit of work id and the
local token that identify the thread. Use the RECOVER INDOUBT command at this (the
participant) location to resolve the indoubt thread.
seq-no The IFCID sequence number associated with
the trace record. The sequence number is
printed in hexadecimal format. If the sequence DSNL405I THREAD luwid=token PLACED IN
number is zero, IFCID 206 was not active or it INDOUBT STATE BECAUSE OF
was active with a destination of the resident COMMUNICATION FAILURE WITH
trace table only. IFCID 206 is a member of COORDINATOR location.
statistics class 4, which has a default INFORMATION RECORDED IN
destination of SMF. TRACE RECORD WITH IFCID=209
AND IFCID SEQUENCE
System action:
NUMBER=seq-no
The indoubt thread remains indoubt. Alert A003 is
Explanation:
generated. A trace record whose IFCID=206 is written.
During execution of the two phase commit protocol
System programmer response:
with the coordinator identified by ’location’,
This is an APARable error, probably at the coordinator, communication failed. Phase 1 of the protocol
but possibly at the DB2 participant. The DB2 completed and the thread is prepared for either commit
documentation required is contained in the statistics or abort.
class 4 trace record that was written. Determine the
The thread is placed in the indoubt state and appears
destination of statistics class 4. Locate and print the
in a DISPLAY THREAD TYPE (INDOUBT) report.
trace record with SEQUENCE NUMBER=’seq-no’.
Periodic attempts are made to reestablish
Call the database administrator. communication with the coordinator for automatic
System programmer response: During execution of the two phase commit protocol
with the participant identified by ’location’,
Determine the cause of the communication failure and communications failed. Phase 1 of the protocol
have the problem fixed. DB2 periodically attempts to completed with the participant, which is prepared to
reestablish communication. If the problem cannot be either commit or abort. The decision to commit the
fixed in a reasonable amount of time, call the database thread was made, but cannot be communicated to the
administrator. Manual resolution of the indoubt thread participant at this time. The participant is indoubt.
might be necessary to release locked resources.
DB2 becomes responsible for indoubt resolution with
Database Administrator Action: Take the following the participant. This responsibility appears in a
actions to resolve this thread using manual means (that DISPLAY THREAD TYPE (INDOUBT) report. Periodic
is, take heuristic action) if it is necessary to release attempts are made to reestablish communication with
locks held by this thread. the participant for automatic indoubt resolution. If
v Determine the proper commit or abort decision by successful, message DSNL423 is written.
contacting the database administrator at the
luwid=token
coordinator ’location’ shown in this message in order
The global logical unit of work id and the
to determine whether the thread with LUWID=luwid
local token that identify the thread.
committed or aborted.
If the coordinator system is another DB2, the | location
following steps can be taken at the DB2 coordinator | This field contains one of the following:
to determine the commit or abort decision. | v The requester’s relational database name
1. If the coordinator DB2 system is running and a | (location name)
DB2 conditional restart was not performed since | v The requester’s VTAM LU name (<luname>)
the error was detected at this (the participant) | v The requester’s IP address
location, ask the database administrator at the
DB2 coordinator location to issue one of the seq-no The IFCID sequence number associated with
following DISPLAY THREAD TYPE(INDOUBT) the trace record. The sequence number is
commands: printed in hexadecimal format. If the sequence
number is zero, IFCID 209 was not active or it
246 Messages
DSNL407I • DSNL408I
248 Messages
DSNL410I • DSNL411E
manually resolved with the RECOVER INDOUBT At this DB2 participant, all indoubt threads coordinated
command. by the cold starting location must be resolved with the
RECOVER INDOUBT command. Locked data remains
| location unavailable until resolution. Threads that were already
| This field contains one of the following:
resolved with this command are discarded. Threads not
| v The requester’s relational database name yet resolved are discarded after resolution with the
| (location name) command.
| v The requester’s VTAM LU name (<luname>)
| v The requester’s IP address The commit or abort decision provided using the
RECOVER INDOUBT command for a logical unit of
seq-no The IFCID sequence number associated with work are propagated to all downstream participants, if
the trace record. The sequence number is any.
printed in hexadecimal format. If the sequence
number is zero, then IFCID 204 was not active
or it was active with a destination of the DSNL412I PROTOCOL ERROR DETECTED IN
resident trace table only. IFCID 204 is a SYNCPOINT REQUEST/RESPONSE
member of statistics class 4, which has a FROM COORDINATOR location
default destination of SMF. LUWID=luwid=token. INFORMATION
RECORDED IN TRACE RECORD
System action: WITH IFCID=208 AND IFCID
The connection with the partner is accepted. Alert A001 SEQUENCE NUMBER=seq-no
is generated. A trace record whose IFCID=204 is Explanation:
written.
DB2 is a participant in the logical unit of work
System programmer response: identified by ’luwid=token’. A protocol error occurred
Call the database administrator. during the SNA sync point exchange with the
coordinator identified by ’location’. The protocol error
Database Administrator Action: DB2 is a participant fits into one of the following categories:
with one or more indoubt threads where the v An unknown SNA PS header was received.
coordinator is ’location’. The DBMS at ’location’
performed a cold start. The DB2 participant assumes v An SNA PS header was received in the wrong
that the coordinator recovery log was lost or damaged sequence.
and indoubt thread resolution cannot be achieved. v An invalid LU6.2 verb sequence was used to deliver
There is probably inconsistent data at the coordinator. the SNA PS header.
A list of indoubt threads involving the coordinator v A DEALLOCATE TYPE(ABEND_SVC) was received
’location’ can be displayed using the DISPLAY from the coordinator, indicating that the coordinator
THREAD command for indoubt type threads by detected a protocol violation in the PS headers
including the LOCATION(’location’) parameter in the transmitted by DB2.
command.
location
The heuristic decision (that is, to commit or abort the Either the relational database name
logical unit of work) should be coordinated with any (location-name) or the logical unit name
other participants. The existence of other participants (<luname>) of the coordinator.
might not be easy to determine. The information might
be available in the coordinators recovery log even luwid=token
though the coordinator performed a cold start. If the The global logical unit of work id and the
coordinator is a DB2, then it might be possible to local token that identify the thread.
execute the DSN1LOGP utility to produce a summary seq-no The IFCID sequence number associated with
report. If this is possible, the following information the trace record. The sequence number is
might be produced: printed in hexadecimal format. If the sequence
v The LUWID of the thread. number is zero, IFCID 208 was not active or it
v The NID used by IMS or CICS to identify the thread. was active with a destination of the resident
trace table only. IFCID 208 is a member of
v The name of all participants.
statistics class 4, which has a default
v The name of an upstream coordinator if the destination of SMF.
coordinator is also a participant. This could happen
when an application requester accesses a DB2 AS If the protocol error was detected before the commit
using application-directed access, which in turn decision, the unit of work at the DB2 system might be
accesses another DB2 server with system-directed indoubt. DB2 does not automatically resolve such an
access. (The local DB2 might be the third system in indoubt thread.
this scenario.)
250 Messages
DSNL413I
statistics class 4. Locate and print the trace record with System programmer response:
SEQUENCE NUMBER=’seq-no’.
This is an APARable error, probably at the participant,
Call the database administrator. The participant might but possibly at the DB2 coordinator. The DB2
need to manually resolve the indoubt thread. documentation required is contained in the statistics
class 4 trace record. Determine the destination of
Database Administrator Action: The DB2 coordinator
statistics class 4. Locate and print the trace record with
does not know the status of the thread at the
SEQUENCE NUMBER=’seq-no’.
participant. The DB2 coordinator assumes that it is
indoubt and maintains knowledge of the indoubt Call the database administrator. The participant might
participant until it is purged with the RESET need to manually resolve the indoubt thread.
INDOUBT command. If the thread is indoubt at the
Database Administrator Action: The DB2 coordinator
participant, it must be resolved using manual
maintains knowledge of the indoubt participant until it
(heuristic) means. The status of the thread at the local
is purged with the RESET INDOUBT command. If the
DB2 (the coordinator) can be determined with the
thread is indoubt at the participant, it must be
DISPLAY THREAD command for type indoubt threads
manually (heuristically) resolved. The status of the
by including the LUWID(’token’) parameter in the
thread at the local DB2 (the coordinator) can be
command.
determined with the DISPLAY THREAD command for
If the ’participant’ location is also a DB2, the RECOVER type indoubt threads by including the LUWID(’token’)
INDOUBT command can be used at the participant to parameter in the command.
resolve the indoubt thread.
If the participant is another DB2, the RECOVER
INDOUBT command can be used to resolve the
DSNL414E PROTOCOL ERROR DURING indoubt thread.
INDOUBT THREAD RESOLUTION
WITH PARTICIPANT location
DSNL415I AUTOMATIC RESOLUTION OF
LUWID=luwid=token INFORMATION
luwid=token WITH COORDINATOR
RECORDED IN TRACE RECORD
location RESULTED IN ABORT
WITH IFCID=206 AND IFCID
SEQUENCE NUMBER=seq-no Explanation:
Explanation: The identified indoubt logical unit of work was
automatically resolved by communication with the
DB2 has coordinator responsibility for the logical unit
coordinator location. After automatic resolution, this
of work identified by ’luwid=token’. The DB2 thread
message is issued if message DSNL405 was previously
associated with the logical unit of work is either
issued to report the thread as indoubt. This message is
committed or aborted. A protocol error occurred during
not issued if message DSNL405 occurs in one restart of
indoubt resolution with the participant identified by
DDF or DB2, and automatic resolution occurs in a
’location’.
different restart of DDF or DB2.
The thread at the participant remains indoubt. DB2
luwid=token
rejects further attempts to automatically resolve the
The global logical unit of work id and the
indoubt thread.
local token that identify the thread
location
The relational database name (location-name)
| location
of the participant.
| This field contains one of the following:
| v The requester’s relational database name
luwid=token | (location name)
The global logical unit of work id and the
local token that identify the thread.
| v The requester’s VTAM LU name (<luname>)
| v The requester’s IP address
seq-no The IFCID sequence number associated with
the trace record. The sequence number is System action:
printed in hexadecimal format. If the sequence Processing continues normally.
number is zero, IFCID 206 was not active or it
was active with a destination of the resident
trace table only. IFCID 206 is a member of DSNL416I COLD START CONNECTION
statistics class 4, which has a default REJECTED BY PARTNER location
destination of SMF.
Explanation:
System action:
DB2 attempted to make a cold-start connection with a
Alert A003 is generated. A trace record whose partner location. The partner rejected this attempted
IFCID=206 is written. connection. DB2 never rejects cold-start connections by
partners.
252 Messages
DSNL417E • DSNL418E
that it had performed a cold start operation and lost all location
knowledge of this indoubt thread. There might be Either the relational database name
damage at the participant. (location-name) or the logical unit name
(<luname>) of the partner
location
This field contains one of the following: System action:
v The requester’s relational database name The connection was successful. Normal processing
(location name) continues.
v The requester’s VTAM LU name (<luname>)
v The requester’s IP address DSNL420I COLD START CONNECTION BY
luwid=token PARTICIPANT location ACCEPTED.
The global logical unit of work id and the POSSIBLE DAMAGE. INFORMATION
local token that identify the thread. RECORDED IN TRACE RECORD
WITH IFCID=204 AND IFCID
seq-no The IFCID sequence number associated with SEQUENCE NUMBER=seq-no
the trace record. The sequence number is
printed in hexadecimal format. If the sequence Explanation:
number is zero, then IFCID 204 was not active DB2 has coordinator responsibility for indoubt threads
or it was active with a destination of the at a participant and just connected with the participant,
resident trace table only. IFCID 204 is a which lost all knowledge of indoubt threads because of
member of statistics class 4, which has a a previous cold start. There might be damage at the
default destination of SMF. participant.
System action: | location
Alert A001 is generated. A trace record whose | This field contains one of the following:
IFCID=204 is written. | v The requester’s relational database name
| (location name)
System programmer response:
| v The requester’s VTAM LU name (<luname>)
Call the database administrator.
| v The requester’s IP address
Database Administrator Action: DB2 is the coordinator
seq-no The IFCID sequence number associated with
with indoubt thread resolution responsibility for one or
the trace record. The sequence number is
more indoubt logical units of work at ’location’. The
printed in hexadecimal format. If the sequence
DBMS at ’location’ performed a cold start. DB2
number is zero, then IFCID 204 was not active
assumes that the participant recovery log was lost or
or it was active with a destination of the
damaged and indoubt thread resolution cannot be
resident trace table only. IFCID 204 is a
achieved. There is probably inconsistent data at the
member of statistics class 4, which has a
participant. Minimally, the participant might not
default destination of SMF.
completely reflect the final outcome of the threads that
were indoubt at the time the failure occurred. A list of System action:
indoubt threads involving the partner ’location’ can be
The connection with the partner is accepted. Alert A001
displayed using the DISPLAY THREAD command for
is generated. A trace record whose IFCID=204 is
type indoubt threads by including the
written.
LOCATION(’location) parameter in the command.
System programmer response:
Information about the indoubt participant continues to
appear in the DISPLAY THREAD TYPE(INDOUBT) Call the database administrator.
report until it is purged with the RESET INDOUBT
command. Database Administrator Action: DB2 is the coordinator
with indoubt thread resolution responsibility for one or
more indoubt logical units of work at ’location’. The
DSNL419I PARTNER location HAS RESOLVED DBMS at ’location’ performed a cold start. DB2
WARM START STATUS AND assumes that the participant recovery log was lost or
CONNECTION IS ACCEPTED damaged and indoubt thread resolution cannot be
achieved. There is probably inconsistent data at the
Explanation:
participant. Minimally, the participant might not
A successful warm start connection was made with a completely reflect the final outcome of the threads that
partner. A previous attempt to make a warm start were indoubt at the time the failure occurred. A list of
connection with the partner was rejected with a indoubt threads involving the partner ’location’ can be
DSNL410I message because the partner specified an displayed using the DISPLAY THREAD command for
incorrect log name. type indoubt threads by including the
LOCATION(’location) parameter in the command.
254 Messages
DSNL421I • DSNL423I
| v The requester’s VTAM LU name (<luname>) Determine the cause of the communication failure and
| v The requester’s IP address have the problem fixed. DB2 periodically attempts to
reestablish communication. If the problem cannot be
System action: fixed in a reasonable amount of time, call the database
administrator. The participant might need to resolve the
Processing continues normally.
indoubt state manually in order to release locked
resources.
DSNL425I THREAD luwid=token AT PARTICIPANT
Database Administrator Action: If the unit of work
location MAY BE INDOUBT BECAUSE
with LUWID=luwid is indoubt at ’location’, inform the
OF A COMMUNICATION FAILURE.
database administrator there that the logical unit of
DB2 ABORTED THE THREAD.
work with LUWID=luwid was aborted to assist in
INFORMATION RECORDED IN
manual resolution of the indoubt thread at ’location’.
TRACE RECORD WITH IFCID=209
AND IFCID SEQUENCE
NUMBER=seq-no DSNL429I INCONSISTENT DDF LOG DATA,
THE FIRST CONNECTION WITH
Explanation:
EACH REMOTE LOCATION WILL BE
During execution of the two phase commit protocol A COLD START CONNECTION
with the participant identified by ’location’,
Explanation:
communications failed. Phase 1 of the protocol
completed with the participant and it is prepared for DB2 detected an inconsistency in the DB2 log during
either commit or abort. The decision to abort the thread restart operations. Since the log is inconsistent and
was made, but cannot be communicated to the cannot be trusted, DB2 performs a cold start connection
participant at this time. The participant is indoubt. with each partner LU the next time a connection with
that LU is attempted. If DB2 has indoubt resolution
DB2 becomes responsible for indoubt resolution with
responsibility either as a coordinator or as a participant,
the participant. This responsibility appears in a
then this information is lost as indicated by messages
DISPLAY THREAD TYPE (INDOUBT) report. Periodic
DSNL438 and/or DSNL439, which might follow this
attempts are made to reestablish communication with
message. This means that:
the participant for automatic indoubt resolution. If
successful, message DSNL424 is written. v All information that DB2 maintained about having
coordinator responsibility for remote participants
luwid=token was purged. These remote participants need manual
The global logical unit of work id and the resolution for any indoubt threads for which DB2
local token that identify the thread. was the coordinator. A DSNL439I message is
| location displayed for each indoubt remote participant.
| This field contains one of the following: v All information that DB2 maintained about having
| v The requester’s relational database name participant responsibility for remote coordinators
| (location name) was purged. A DSNL438I message is displayed for
256 Messages
DSNL432I • DSNL434E
each database access thread that has a remote nnnn The number of indoubt threads for which DB2
coordinator. If a database access thread remains is the participant
indoubt at the end of restart, then the thread must be
mmmm
manually resolved. A -DISPLAY THREAD (*)
The number of remote partners that have
TYPE(INDOUBT) LOCATION (*) command provides
coordinator responsibility
a report that lists the indoubt threads that need
manual resolution. System action:
System action: Processing continues normally.
Processing continues normally. Operator response:
System programmer response: If the message was issued as a result of DDF starting,
no action is necessary. If the message was issued as a
Call the database administrator.
result of DDF stopping, contact the database
Database Administrator Action: See the DSNL438I and administrator.
DSNL439I messages to determine what action to take.
Database Administrator Action: If the message was
issued as a result of stopping DDF, then DB2
DSNL432I DDF IS COORDINATOR FOR nnnn maintained all information necessary to perform
THREADS WITH mmmm INDOUBT automatic resynchronization with partner locations and
REMOTE PARTNERS resolve all indoubt units of work. Issue the START DDF
command to initiate this process.
Explanation:
If you do not want to perform automatic
This message is issued when DDF is started or stopped,
resynchronization, you can still resolve the indoubt
if DDF determines that this DB2 has coordinator
units of work for which DB2 is a participant and which
responsibility for one or more indoubt threads with one
hold database resources locked. Use the DISPLAY
or more partners. This is a summary status message.
THREAD command for type indoubt threads to
nnnn The number of indoubt threads for which DB2 produce a display that lists these threads. Then use the
is the coordinator RECOVER INDOUBT command to either commit or
abort these units of work.
mmmm
The number of remote partners where the To avoid data inconsistency, coordinate this manual
threads are indoubt resolution with the database administrators at the
locations that have coordinator responsibility for each
System action: indoubt unit of work. If any of the indoubt units of
Processing continues normally. work at DB2 also have coordinator responsibility for
participant locations, then you should notify the
Operator response: database administrators at the participant locations of
If the message was issued as a result of DDF starting, the commit or abort decision so they can make the
no action is necessary. If the message was issued as a same decision.
result of DDF stopping, contact the database
administrator. DSNL434E DDF NOT STARTED - INCORRECT
Database Administrator Action: If the message was VTAM RELEASE LEVEL
issued as a result of stopping DDF, then DB2 Explanation:
maintained all information necessary to perform
automatic resynchronization with partner locations and The local VTAM release level is older than the
resolve all indoubt units of work. Issue the START DDF minimum release level required by DB2. When DB2
command to initiate this process. issues the VTAM OPEN macro, the VTAM release level
is returned to DB2. DB2 examines the VTAM release
If the message was issued as a result of starting DDF, level to determine whether the local VTAM system
then DDF started automatic resynchronization. provides the function required by DB2.
System action:
DSNL433I DDF IS PARTICIPANT FOR nnnn
INDOUBT THREADS WITH mmmm The attempt to START DDF fails.
REMOTE PARTNERS Operator response:
Explanation: Call the system programmer.
This message is issued when DDF is started or stopped, System programmer response:
if DDF determines that this DB2 has participant
responsibility for one or more indoubt threads with one Install a release of VTAM that is compatible with the
or more partners. This is a summary status message. DB2 system. The DB2 Program Directory identifies the
required VTAM release level. has not yet completed the first phase
of commit and should be backed out.
DSNL438I RESYNC STATUS PURGED FOR U UNKNOWN: The status of the logical
COORDINATOR location. LUWID=luwid, unit of work is not known to DB2
URID=urid, STATUS=s INFORMATION because of conditional restart.
RECORDED IN TRACE RECORD
seq-no The IFCID sequence number associated with
WITH IFCID=235 and IFCID
the trace record. The trace record is written to
SEQUENCE NUMBER=seq-no
statistics class 4, which is started to SMF as a
Explanation: default during DB2 installation. Statistics class
4 must be started to a permanent destination
The information related to resynchronization with the
(SMF or GTF) for the trace record to be
remote coordinator location for the logical unit of work
accessible. The sequence number is printed in
identified by ’luwid’, which is displayed in this
hexadecimal.
message, is being purged by DB2. Automatic indoubt
resolution responsibility for this distributed logical unit System action:
of work can no longer be performed.
Processing continues normally.
This situation can arise in one of two ways;
System programmer response:
v A DB2 conditional restart (other than a DB2 cold
start; that is, a DB2 conditional restart with Call the database administrator.
STARTRBA=ENDRBA) is being performed. Database Administrator Action: The resynchronization
v An inconsistency in the DB2 log was detected during information that was purged by DB2 is recorded in this
DB2 restart processing (indicated by a DSNL429I message. To determine the proper commit or abort
message). decision made by the coordinator at ’location’, use the
status code as follows:
| location
| This field contains one of the following: A The correct decision is to abort the logical unit
| v The requester’s relational database name of work.
| (location name) C The correct decision is to commit the logical
| v The requester’s VTAM LU name (<luname>) unit of work.
| v The requester’s IP address D Contact the database administrator at
luwid The global logical unit of work id that ’location’ to determine the correct decision.
identifies the logical unit of work. F The correct decision is to abort the logical unit
urid The unit of recovery identifier. This is the RBA of work.
on the DB2 recovery log of the log record that U Contact the database administrator at
marks the beginning of the logical unit of ’location’ to determine the correct decision.
work. This is the earliest RBA required to
process the logical unit of work during restart.
DSNL439I RESYNC STATUS PURGED FOR
s Restart status of the logical unit of work. PARTICIPANT location. LUWID=luwid,
When DB2 came down, the logical unit of URID=urid, STATUS=s INFORMATION
work was in one of these states: RECORDED IN TRACE RECORD
A INABORT: The logical unit of work WITH IFCID=235 and IFCID
was in the “must-complete” phase of SEQUENCE NUMBER=seq-no
abort, but abort has not yet Explanation:
completed.
DB2 is purging the information related to
C INCOMMIT: The logical unit of work resynchronization with the remote participant location
was in the “must-complete” phase of for the logical unit of work identified by ’luwid’, which
commit, but commit has not yet is displayed in this message. Automatic indoubt
completed. resolution responsibility for this distributed logical unit
D INDOUBT: The logical unit of work of work can no longer be performed.
completed the first phase of commit, This situation can arise in one of two ways:
but DB2 has not yet received the
commit or abort decision from the v A DB2 conditional restart (other than a DB2 cold
coordinator. start; that is, a DB2 conditional restart with
STARTRBA=ENDRBA) is being performed.
F INFLIGHT: The logical unit of work
258 Messages
DSNL440I
v An inconsistency in the DB2 log was detected during message. When communicating the proper commit or
DB2 restart processing (indicated by a DSNL429I abort decision to the database administrator at
message). ’location’, use the status code as follows:
| location A Abort the logical unit of work.
| This field contains one of the following:
C Commit the logical unit of work.
| v The requester’s relational database name
| (location name) D See the DSNL438I message produced for the
same ’luwid’ and ’urid’ to determine the
| v The requester’s VTAM LU name (<luname>)
coordinator ’location’. Contact the database
| v The requester’s IP address administrator at ’location’ to determine the
luwid The global logical unit of work id that correct decision.
identifies the logical unit of work. F Abort the logical unit of work.
urid The unit of recovery identifier. This is the RBA U If there is a DSNL438I message for the same
on the DB2 recovery log of the log record that ’luwid’ and ’urid’, proceed as described above
marks the beginning of the logical unit of under ’D’. Otherwise, there might be
work. This is the earliest RBA required to information available on the DB2 log that a
process the logical unit of work during restart. DSN1LOGP summary report can provide. If
s Restart status of the logical unit of work. this is not successful, contact the IBM Support
When DB2 came down, the logical unit of Center.
work was in one of these states:
A INABORT: The logical unit of work DSNL440I csect-name RESET INDOUBT
was in the “must-complete” phase of COMMAND SPECIFICATION IN
abort, but abort has not yet ERROR
completed. Explanation:
C INCOMMIT: The logical unit of work A RESET INDOUBT command was issued, but the
was in the “must-complete” phase of specification of keywords or keyword parameter values
commit, but commit has not yet was in error.
completed.
System action:
D INDOUBT: The logical unit of work
completed the first phase of commit, No indoubt information was purged. System processing
but DB2 has not yet received the continues normally.
commit or abort decision from the User response:
coordinator.
One of the following errors was made in the RESET
F INFLIGHT: The logical unit of work INDOUBT command specification:
has not yet completed the first phase
of commit and should be backed out. v RESET INDOUBT was issued without any other
keywords specified. At least one of the following
U UNKNOWN: The status of the logical keywords must also be specified: LUNAME,
unit of work is not known to DB2 IPADDR, LOCATION, or LUWID.
because of conditional restart. v RESET INDOUBT was issued with both the LUWID
seq-no The IFCID sequence number associated with and LOCATION keywords specified, but a list of
the trace record. The trace record is written to LOCATION keyword parameter values was
statistics class 4, which is started to SMF as a specified. When both the LUWID and LOCATION
default during DB2 installation. Statistics class keywords are specified only one LOCATION
4 must be started to a permanent destination keyword parameter value is allowed.
(SMF or GTF) for the trace record to be v RESET INDOUBT was issued with at least one
accessible. The sequence number is printed in LOCATION keyword parameter value that began
hexadecimal. with a ’<’, but did not end with a ’>’, or the length
of the bracketed value was not 1 to 8 characters.
System action:
When the LOCATION keyword parameter value is
Processing continues normally. specified in the <luname> format, the luname value
must be bracketed with ’<’ and ’>’ and be 1 to 8
System programmer response:
characters long.
Call the database administrator. | v RESET INDOUBT was issued with an invalid
Database Administrator Action: The resynchronization | IPADDR keyword parameter. Verify that the
information that was purged by DB2 is recorded in this | specified IPADDRs are in the proper form, that there
260 Messages
DSNL445I • DSNL447I
| Remember that the FORCE option causes DB2 to System processing continues normally.
| purge all knowledge of indoubt resolution User response:
| responsibility involving the luname or
| ipaddrspecified on the command. For SNA, you can use the VTAM command DISPLAY
NET to determine the existence of sessions between
| Use caution when using the FORCE parameter to two logical units. Terminate the sessions by using the
| purge participant indoubt information when no VTAM command VARY NET,TERM to allow the RESET
| errors are precluding automatic resolution. INDOUBT to occur. For TCP/IP, terminate all
| Normally, after the use of the RECOVER INDOUBT connections to the IP address.Determine the correct
| command, automatic resolution with the luname or ipaddr and reissue the command.
| coordinator determines if heuristic damage
| occurred. This detection is lost if RESET INDOUBT DSNL449I DB2 HAS NO INFORMATION
| is used before automatic resolution with the RELATED TO LUNAME luname
| coordinator can be achieved.
Explanation:
| Use caution when using the FORCE parameter to A -RESET INDOUBT LUNAME(’luname’) FORCE
| purge coordinator indoubt information when no command was issued but DB2 has no knowledge of the
| errors are precluding automatic resolution. Once the specified ’luname’.
| information is purged, any participant that is
| indoubt is forced to use a heuristic decision process luname
| to resolve the indoubt logical unit of work. The logical unit name, as defined to VTAM, of
the coordinator or participant
| 2. Examine the -DISPLAY THREAD output. If the
| value specified in the command (and displayed in System action:
| the DSNL447I message) is incorrect, determine the
| correct value and reissue the command using the No information was purged. System processing
| correct value. continues normally.
User response:
DSNL448I UNABLE TO FORCE COLD START Determine the correct luname as follows:
WITH nettype netvalue, SESSION STILL
v Use the -DISPLAY THREAD(*) TYPE(INDOUBT)
EXISTS
LOCATION(*) command to determine locations for
Explanation: which DB2 has indoubt responsibility.
A -RESET INDOUBT LUNAME(’luname’) FORCE or a v Query the SYSIBM.LOCATIONS table to correlate a
-RESET INDOUBT IPADDR(’ipaddr’) FORCE command location name with an luname. The LINKNAME
was issued to force a cold start, but network column contains the luname associated with the
connections still exist between DB2 and the partner location name in the LOCATION column.
’luname’ or ’ipaddr’. The information related to this Then reissue the command, specifying the correct
partner was not purged, so a cold start is not luname.
performed.
nettype DSNL450I DDF THREAD luwid=token IS
Identifies the type of network used to access BETWEEN PHASE 1 AND PHASE 2 OF
the remote site. There are two possible values: COMMIT. THREAD IS NOW AN
LU -- indicates that VTAM is used to INDOUBT THREAD AS A RESULT OF
connect to the remote site. CANCEL REQUEST.
Explanation:
262 Messages
DSNL451I • DSNL454I
The identified DDF thread was in a prepared state After determining the correct luname, reissue the
waiting for the commit or backout decision of the command.
commit coordinator. The thread cannot be canceled in
this state. However, the thread was removed from the
DSNL452I QUALIFYING INDOUBT
active state and placed into the indoubt state. The
INFORMATION FOR LUNAME luname
conversation with the coordinator was deallocated. The
HAS BEEN PURGED
thread is now indoubt and appears in the display
thread report for indoubt threads. The resources held Explanation:
by the thread continue to be held. Automatic resolution
of the indoubt state is attempted periodically. Resources A -RESET INDOUBT LUNAME(’luname’) command,
held by the thread are released after indoubt resolution which was issued to purge indoubt information about
occurs. the specified luname completed successfully. The
indoubt information was purged.
luwid=token
The global logical unit of work id and the luname
local token that identify the thread The luname specified for the LUNAME
keyword in the -RESET INDOUBT
System action: LUNAME(luname) command being processed.
Processing continues normally. System action:
Operator response: The specified indoubt information was purged. System
processing continues normally.
If the purpose of canceling this thread was to free the
resources held by the thread, call the database
administrator. DSNL453I csect QUALIFYING INDOUBT
INFORMATION FOR IPADDRipaddr
Database Administrator Action: To release the
NOT FOUND
resources held by the indoubt thread before automatic
resolution with the coordinator, a manual commit or Explanation:
abort decision can be made with the RECOVER
INDOUBT command. First, issue the DISPLAY A -RESET INDOUBT IPADDR(’ipaddr’) command was
THREAD command for an indoubt thread report, issued, but DB2 has no indoubt information about the
which includes the subject thread. From this report, specified IP address.
determine the name of the coordinator. Contact the csect The CSECT name of the DB2 module that
coordinator system and find out whether a commit or issued the message
abort decision was made.
| ipaddr The IP address of the coordinator or
| participant.
DSNL451I QUALIFYING INDOUBT
INFORMATION FOR LUNAME luname System action:
NOT FOUND No indoubt information was purged. System processing
Explanation: continues normally.
Explanation: luname
The VTAM LU name associated with the
An advanced program-to-program communications remote location.
(APPC) conversation failed, or could not be allocated,
because a VTAM return code indicates a conversation modename
failure. VTAM return codes are defined in z/OS The logon mode used by DB2 to allocate the
Communications Server SNA Programmer’s LU 6.2 conversation.
Reference. System action:
SNA sense codes that start with 00 represent DB2 All communication to the remote location fails until the
reason codes. Refer to Codes for a description of more limits can be negotiated with the remote location.
common SNA sense codes returned to DB2 by VTAM.
Operator response:
The variables that are not return codes are described as
follows: Notify the system programmer.
264 Messages
DSNL502I • DSNL511I
266 Messages
DSNL512I
| call failed and DB2 is not able to determine the | installation panel. Another way to specify the value
| host name. DB2 retries the socket call periodically. | is through the TCPKPALV value in the DSN6FAC
| – If socket=GETADDRINFO(host-name), then DB2 | macro, used to build the DB2 parameters module.
| invoked a TCP/IP GetAddrInfo socket call to | In this situation, processing continues, and DB2 does
| determine the IP address associated with the | not retry the socket call. Verify that the TCP/IP stack
| specified host name. However, the call failed and | being used by DB2 contains the required companion
| DB2 is not able to determine the IP address. DB2 | support for this function. If not, modify the DB2
| retries the socket call periodically. | parameter module to prevent DB2 from attempting
| There are two options to consider: | to override the TCP/IP stack value.
| 1. If you want a BSDS specified IP address, | v If socket=BSDS_ERROR
| correct the BSDS. This requires you to stop and | (ADDRESS_ON_PORT_STMT), you specified an IP
| restart DB2. | address in both the BSDS and the PORT statement of
| the TCP/ IP profile. An address should be specified
| 2. Otherwise, verify that the provided host-name
| in only one place. That is, DB2 detected that IP
| is correct.
| addresses have been specified in the BSDS (through
| - If the host-name is incorrect, correct the | the IPV4, GRPIPV4, IPV6, and GRPIPV6 keywords of
| host-name in the appropriate resolver | the DSNJU003 Change Log Inventory utility) and
| configuration file, refresh TCP/IP, and then | also in the TCP/IP profile on the PORT statement for
| stop and start DDF so that the new | the port value to be used by this subsystem. Only
| host-name is refreshed for DDF | one of the specifications can now have IP addresses.
| initialization. | The DB2 TCP/IP environment will not initialize, and
| - If the host-name is correct, then TCP/IP is | the error is periodically repeated until the error is
| unable to resolve the host-name to an IP | corrected.
| address. You must make changes in order to | One of the IP address specifications must be
| allow for proper host-name to IP address | removed from the BSDS or from the TCP/IP profile.
| resolution. If the changes have been made to | However, the BSDS specification should be retained
| the name server or local host table, refresh | because the recommendation is to use BSDS
| the resolver. | specifications to define the IP addresses that are to be
| – If socket=GETNAMEINFO(ip-address), then DB2 | associated to DB2, and, because removing the BSDS
| invoked a TCP/IP GetNameInfo socket call to | specifications would require DB2 to be stopped. In
| determine the domain name for the specified IP | this case, to allow the initialization of the DB2
| address. However, the call failed and DB2 is not | TCP/IP environment to continue. The TCP/IP profile
| able to determine the domain name. DB2 retries | PORT statement can be changed to remove the IP
| the socket call periodically. | addresses and then the changed specifications can be
| v If socket=POLL, then the online ZPARM was changed | dynamically brought on-line, which favors the BSDS
| using the SET SYSPARM command, changing the | specifications.
| MAXDBAT from a positive value to zero. In this | v If socket=BSDS_ERROR
| case, the message is informational, indicating that | (IPv6_REQUIRES_DUALMODE_STACK), you
| DB2 terminated its TCP/IP listening capability for | specified a member or subsystem, and possibly
| SQL related work because DB2 can no longer accept | group, IPv6 address, in the BSDS without enabling a
| SQL related connections from remote partners when | TCP/IP dual mode stack. DB2 ignores all IPv6
| MAXDBAT is set to zero. | addresses defined in the BSDS and DDF
| v If socket=SHUTDOWN_REG (USS_UNAVAILABLE), | start-processing continues normally.
| then the UNIX System Services (USS/OMVS) | You should either enable a dual mode stack or delete
| environment is not available. DDF start processing | all of the BSDS-defined IPv6 addresses and use only
| continues and this message is periodically repeated | IPv4 addresses.
| until the Unix System Services environment becomes | v If socket=BINDSPECIFIC NOT SUPPORT WITH
| available or DDF is stopped. You can use the z/OS | SECURE PORT, you specified a secure port in the
| ″F OMVS, RESTART″ command to start the Unix | BSDS but have simultaneously defined an IP address
| System Services environment. | on the PORT statement in the TCP/IP profile
| v If socket=SETRLIMIT and reason code=1148033C, then | (PROFILE.TCPIP).
| you should define DB2 as a superuser. See Installation | DDF only supports secure ports when it is listening
| Guide for instructions on enabling DDF as a | on the INADDR_ANY.
| superuser.
User response:
| v If socket=TCPKEEPALIVE, then DB2 issues this
| socket call as a result of the TCP/IP KeepAlive value Notify the system programmer.
| specified in the DB2 parameters module (usually
Problem determination:
| DSNZPARM). You may specify this value by the
| TCP/IP KEEPALIVE value in the DSNTIP5 See System Programmer Response.
If the trusted context ADDRESS attribute containing the TCP/IP service names are case sensitive, so make sure
specified domain defined in the that the PORT column in SYSIBM.LOCATIONS is an
SYSIBM.SYSTXTTRUSTATTRS is invalid, then exact match for the service name defined to TCP/IP.
v If the error occurs during implicit trusted connection User response:
processing, then the error is ignored and the
Notify the system programmer.
connection is established without any additional
privileges. Problem determination:
v If the error occurs during explicit trusted connection See System Programmer Response.
processing, then the connection processing fails.
Operator response: DSNL515I csect TCP/IP BIND FOR PORT port
Notify the system programmer. FAILED WITH RETURN CODE=’rc’X
AND REASON CODE=’reason’X
System programmer response:
Explanation:
Refer to IBM TCP/IP for MVS: Application Programming
Reference for an explanation of the error. Correct the DB2 encountered an error on the TCP/IP bind socket
IPADDR column value in SYSIBM.IPNAMES or register call while attempting to register a TCP/IP port number
the domain with TCP/IP. Correct the trusted context with the TCP/IP instance.
ADDRESS attribute value using the SQL ALTER Variable
| TRUSTED CONTEXT statement. register the domain Description
| with TCP/IP.
csect The CSECT name of the DB2 module that
User response: issued the message.
268 Messages
DSNL516I • DSNL517I
port The TCP/IP port number DB2 wants to calls, encryption and decryption, and so on. If the
register with the TCP/IP instance. CEEPIPI module is not included in an accessible data
set such as STEPLIB data sets or the LPA library, DDF
| rc The return code reported by TCP/IP. The
is unable to use the Language Environment.
| return code values are documented in z/OS
| UNIX System Services Messages and Codes or in System action:
| z/OS Communications Server: IP and SNA Codes.
DDF startup continues, but DDF users cannot use DB2
| reason The reason code reported by TCP/IP. The functions that require Language Environment services.
| reason code values are documented in z/OS
System programmer response:
| UNIX System Services Messages and Codes or in
| z/OS Communications Server: IP and SNA Codes. Add the Language Environment library to the DDF
STEPLIB concatenation or to the LPA library. The
System action:
Language Environment library must be APF authorized
If this error occurs for the TCP/IP port that is used for when it appears in the DDF STEPLIB concatenation.
incoming DRDA requests, the error is probably caused
Problem determination:
by DB2 restarting on a CEC that already has another
DB2 subsystem using the DRDA port number. DB2 will Collect the following diagnostic item listed in
continue to try to activate the TCP/IP port number v Console output from the system on which the job
periodically. was run, and a listing of the SYSLOG data set for the
If this error occurs for a TCP/IP port that is used for period of time spanning the failure.
incoming DRDA requests to an ALIAS, the error is .
probably caused by some of the reasons that an error
would occur for the normal DRDA request port. Check
to ensure that the port value was also not previously DSNL517I csect-name CEEPIPI func SERVICE
reserved for another application in the system’s TCP/IP FAILED WITH RETURN CODE=rc
profile. DB2 will continue to try to periodically activate
Explanation:
the TCP/IP port number.
DB2 uses the Language Environment CEEPIPI service
If this error occurs for the DRDA resynchronization
to issue certain TCP/IP socket calls. The Language
port, DB2 invokes internal processing that is equivalent
Environment return code rc was not expected for the
to STOP DDF MODE(FORCE).
indicated Language Environment function call.
Operator response:
func The function requested by DB2. Possible
Notify the system programmer. values are:
System programmer response: add_entry(module-name)
Add an entry to the Language
| Refer to z/OS UNIX System Services Messages and Codes Environment PIPI table dynamically.
| or z/OS Communications Server: IP and SNA Codes for an Module-name is the name of the
| explanation of the error. module that failed to be added to the
Define DB2’s TCP/IP port number to the TCP/IP PIPI table.
instance, or use the change log inventory utility to call_sub
correct the TCP/IP port number used by DB2. Run a program that issues a TCP/IP
User response: socket call using an existing
Language Environment run time
Notify the system programmer. environment.
Problem determination: del_sub
See System Programmer Response. Delete an entry from the Language
Environment PIPI table dynamically.
DB2 must load the Language Environment interface rc The return code received from CEEPIPI.
module (CEEPIPI) to process functions requiring System action:
Language Environment services. These Language
Environment services are required for TCP/IP socket
System programmer response: port The TCP/IP port number used by this DB2
subsystem to accept incoming
A description of the Language Environment enclave resynchronization connection requests.
return code and the condition token are documented in
Language Environment for OS/390 & VM Programming System action:
Guide. The DB2 TCP/IP port is available to accept incoming
270 Messages
DSNL521I • DSNL600I
Correlation IDs beginning with ’0nn’ where reason code. The value and semantics of the code are
’nn’ is a number from 01 to 28, identify system the same as the SQL return codes documented in Codes.
agents. Use the table defined for message DSNT500I to find the
TYPE of resource identified in the message.
connection-id
The connection identifier of the requester.
DSNL701I CDB OBJECT object-name DOES NOT
luw-id=token
EXIST
The logical unit of work ID of the thread
followed by an ’=’ sign and a token which Explanation:
may be used in place of luw-id in any DB2
The communications database (CDB) does not contain
command that accepts luw-id as input.
object-name. The incorrect object-name can be the
database name, the table space name, or the table
Refer to message DSNT500I for an explanation of the
name.
resource type and resource name.
System action:
System action:
Termination of the distributed data facility (DDF) is
The SQL statement cannot be executed.
initiated.
Operator response:
Operator response:
See Problem Determination.
Notify the system programmer.
Problem determination:
System programmer response:
The reason the resource is unavailable is identified by
Determine what caused the failure, define the object as
the reason code. The reason code is described in Codes.
required, and issue the -START DDF command.
Collect the information described for the reason code
received. Problem determination:
Collect the following diagnostic items: Print the definition of the communications database
v Console output from the system on which the job (CDB).
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure. DSNL702I CDB TABLE table-name DOES NOT
HAVE PROPER COLUMN
DSNL700I csect-name CDB RESOURCE DEFINITIONS, COLUMN column-name
UNAVAILABLE, DEFAULTS MAY BE IS MISSING OR INCORRECTLY
USED REASON=reason TYPE=type DEFINED
NAME=name Explanation:
Explanation: The communications database (CDB) needs a definition
This message indicates that a requested function for ’column-name’ in ’tablename’. The current
required the CDB which is currently unavailable. definition is missing or incorrect.
Defaults can be used to allocate conversations or set System action:
conversation limits with VTAM and TCP/IP partners.
Termination of the distributed data facility (DDF) is
System action: initiated.
If the SYSIBM.MODESELECT table is unavailable, Operator response:
VTAM defaults are used to allocate conversations. If
the the SYSIBM.LUMODES table is unavailable, VTAM Notify the system programmer.
defaults can be used for conversation limits. If the System programmer response:
SYSIBM.LOCATIONS, SYSIBM.IPNAMES,
SYSIBM.LULIST, or SYSIBM.LUNAMES tables Determine what caused the failure, define the column
areunavailable, conversations can not be allocated to as required, and issue the -START DDF command.
remote LOCATIONs.
Problem determination:
Operator response:
Print the definition of the communications database
Note the REASON code, the TYPE code, and the (CDB).
NAME. See Problem Determination section for an
explanation of the collected data.
Problem determination:
The reason the resource is unavailable is identified by a
272 Messages
DSNL703I • DSNL800I
Operator response:
DSNL703I CDB TABLE table-name DOES NOT
HAVE PROPER INDEX DEFINITIONS, Notify the system programmer.
INDEX index-name IS MISSING OR
INCORRECTLY DEFINED System programmer response:
DSNL704I CDB OBJECT object-name DOES NOT The variable “routine” is the name of the exit routine,
HAVE PROPER REFERENTIAL DSNLHLIx, invoked by DB2.
CONSTRAINT DEFINITIONS System action:
Explanation: The system abends the failing database-access agent.
The communications database (CDB) requires
referential constraint definitions for object-name. The | DSNL800I csect-name EXECUTION FAILED
current definition is missing or incorrect. | BECAUSE THE BIND DEPLOY
System action: | FUNCTION IS NOT SUPPORTED BY
| THE SERVER WHICH CAUSED
Termination of the distributed data facility (DDF) is | TERMINATION OF CONNECTION:
initiated. | LOCATION location, PRODUCT ID
Operator response: | pppvvrrm
System programmer response: | The current bind command failed because the
| command was routed to a server that does not support
Determine what caused the failure, define the missing | the bind deploy function.
referential constraint, and issue the -START DDF
command. For more information, see Installation Guide. | System action:
Problem determination: | The BIND command fails. The package is not deployed.
274 Messages
Chapter 10. DSNM messages
Message identifiers that begin with DSNM communicate information about the IMS
attachment facility.
All of the DSNM messages are sent to the IMS master terminal operator (MTO) and
to the appropriate MVS console.
Problem determination:
DSNM100I SUBSYSTEM xxxx NOT AVAILABLE
Recovery information is available on the DB2 log and
IMS/TM log to assist in the resolution of the work Explanation:
unit(s) indoubt. For each indoubt work unit, an
The IMS/TM command facility which routes
IMS/TM attachment facility snap record (code
commands to the DB2 subsystem cannot perform its
X’5501FE’) is written to the IMS/TM log.
functions because the DB2 subsystem named ’xxxx’ is
considered not operational.
DSNM005I IMS/TM RESOLVE INDOUBT
System action:
PROTOCOL PROBLEM WITH
SUBSYSTEM xxxx The connection to the DB2 subsystem failed for the
command. The command is rejected.
Explanation:
System programmer response:
The DB2 subsystem ID of ’xxxx’ has protocol
incompatibilities with IMS/TM. The DB2 resolve If the DB2 subsystem is operational, and if you suspect
indoubt process received an unknown or invalid an error in DB2, refer to Part 2 of Diagnosis Guide and
recovery request (RRE) from IMS/TM. The request was Reference for information on identifying and reporting
rejected by DB2 and kept by IMS/TM. The message is the problem. The person entering the request may not
sent to the IMS/TM master terminal operator. be authorized to execute the command. If the DB2
subsystem is not operational, DB2 commands from
System action:
IMS/TM cannot be processed.
The connection between the DB2 and IMS/TM
Problem determination:
subsystems remains active, and applications can access
DB2 resources. A snap record (X’5501FF’) is written to the IMS/TM log
if a connection request failed.
Operator response:
Notify the system programmer.
DSNM104I xxxx COMMAND FAILED
System programmer response:
Explanation:
Call the support center after extracting from the
The DB2 command specified by xxxx failed to
IMS/TM log the IMS/TM attachment facility snap
complete.
records (code X’5501FE’) using the IMS/TM utility
DFSERA10. System action:
These records contain the complete request from The command terminated without providing an output
IMS/TM to DB2, the request type is at offset X’01C’, message. Commands will still be allowed by the
276 Messages
IMS/TM attachment facility.
System programmer response:
If you suspect an error in DB2, refer to Part 2 of
Diagnosis Guide and Reference for information on
identifying and reporting the problem.
Problem determination:
If the command failed because of an abend, a snap
record (X’5501FF’) is written to the IMS/TM log and
SYS1.LOGREC information is available.
– The z/OS level is V1.7 or later A LUW-ID of ’*’ indicates that the thread does not have
– The data set is SMS-managed a LUW-ID. If the LUW-ID is not an ’*’, the value is a
logical-unit-of-work-id that is assigned to the thread
– The Extent Constraint Removal option is set to
followed by an ’=’ sign and a token value, which can
YES in the associated SMS data class
be used in place of logical-unit-of-work-id in any DB2
v If any of the conditions outlined in the previous command that accepts logical-unit-of-work-id as input.
bullet are not true, the maximum number of extents
is: Messages that have the same connection ID, correlation
ID, and LUW-ID relate to the same user. This makes it
– 251 to 255 for non-striped data sets
possible to scan a number of DSNP-prefixed messages
– 251 to 255 for each stripe for striped data sets and group activities involving a given user.
Problem determination: System action:
Examine the console messages, SYS1.LOGREC The data space manager (DSM) terminates its actions
information, and SYSLOG to determine the reason for associated with the current SQL request. Higher level
the condition. Try to resolve it by the methods functions might terminate the current SQL request or
described in the Operator Response section of this the unit of recovery that issued the request.
message. If you feel that this message indicates a
problem in an IBM program, you should provide the Operator response:
following sources of information about the problem: This message is directed to either the database
v Console sheet showing the message and related administrator or the system administrator. Bring the
messages that might precede or follow it. message to their attention if it appears on the MVS
v System log printout (obtained via MVS WRITELOG operator’s console. The installation should consider
operator command) showing related VSAM/media directing DB2 messages to a console other than the
manager messages that might appear there (usually operator’s console.
needed only if you have a message or reason code System programmer response:
that indicates a media manager services problem
occurred). Investigate the problem indicated by the reason code
and preceding access method services messages, if any,
v Integrated catalog facility (ICF) catalog listing
and correct it, if possible. If an out-of-space condition
showing characteristics of the data set in question
exists, see the description of message DSNP001I for
and of the ICF catalog itself.
actions to consider.
v VTOC listing of packs associated with the request,
showing space available for data sets, catalogs, Problem determination:
VTOC index, and the VTOC itself, as well as data set See Problem Determination of message DSNP001I for
extent information. this information.
v Any associated dumps.
v SYS1.LOGREC listing showing entries at or near the DSNP003I csect - RESET FAILED FOR data-set-name.
time of the problem (unless these appear in an RC=rrrrrrrr CONNECTION-
associated dump). ID=xxxxxxxx, CORRELATION-
v Depending on the reason code, the results of certain ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
SQL SELECT operations on DB2 catalog tables may work-id=token
be needed. ( See Codes.)
Explanation:
DSNP002I csect - DEFINE FAILED FOR Reset, a data space manager (DSM) function invoked
data-set-name RC=rrrrrrrr by DB2 utilities, failed in CSECT ’DSNPmmmm’ for the
CONNECTION-ID=xxxxxxxx, reason identified by RC. See Codes. The connection ID,
CORRELATION-ID=yyyyyyyy, correlation ID, and logical-unit-of-work ID (LUW-ID)
LUW-ID=logical-unit-of-work-id =token identify the user or application that encountered the
problem. Correlation IDs beginning with ’0nn’, where
Explanation: ’nn’ is a number, identify system agents.
Data set definition failed (in CSECT ’DSNPmmmm’) for A LUW-ID of ’*’ indicates that the thread does not have
the reason identified by RC. (Refer to Codes.) The a LUW-ID. If the LUW-ID is not an ’*’, the value is a
connection ID, correlation ID, and logical-unit-of-work logical-unit-of-work-id that is assigned to the thread
ID (LUW-ID) identify the user or application that followed by an ’=’ sign and a token value, which can
encountered the problem. The connection, correlation, be used in place of logical-unit-of-work-id in any DB2
and logical-unit-of-work IDs identify the user or command that accepts logical-unit-of-work-id as input.
application that encountered the problem. Correlation
IDs beginning with ’0nn’, where ’nn’ is a number, Messages that have the same connection ID, correlation
identify system agents. ID, and LUW-ID relate to the same user. This makes it
280 Messages
DSNP004I • DSNP005I
possible to scan a number of DSNP-prefixed messages This message is directed to the database administrator
and tie together activities involving a given user. or the system administrator. Bring it to that person’s
attention if it appears on the MVS operator’s console.
System action:
The installation should consider directing DB2
DSM terminates its actions associated with the current messages to a console other than the operator’s console.
SQL request. Higher level functions might terminate
System programmer response:
the current SQL request or the unit of recovery that
issued the request. Investigate the problem indicated by the reason code
and preceding access method services messages if any,
Operator response:
and correct it, if possible. Check the data set and delete
This message is directed to the database administrator it by using access method services directly if reasonable
or the system administrator. Bring it to that person’s to do so. Consider making a backup copy before doing
attention if it appears on the MVS operator’s console. this. (Use DB2 utilities to make the copy; in general,
The installation should consider directing DB2 VSAM utilities do not work on DB2 data sets.)
messages to a console other than the operator’s console.
Problem determination:
System programmer response:
See Problem Determination for message DSNP001I for
Investigate the problem indicated by the reason code this information.
and preceding DB2, access method services, or VSAM
Severity:
messages, if any, and correct it, if possible.
8 (error)
It might be necessary to delete and redefine the data
set using access method services. Consider making a
backup copy before doing this. (Use DB2 utilities to DSNP005I csect - COULD NOT REMOVE EXCESS
make the copy; in general, VSAM utilities do not work VOLUMES FROM CANDIDATE LIST
on DB2 database services data sets.) OF data-set-name CONNECTION-
ID=xxxxxxxx, CORRELATION-
Problem determination:
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
See Problem Determination for message DSNP001I for work-id=token
this information.
Explanation:
Volumes from a storage group were entered in the data
DSNP004I csect - DELETE FAILED FOR
set’s candidate list and could not be removed by
data-set-name. RC=rrrrrrrr
CSECT ’DSNPmmmm’ after some data space manager
CONNECTION-ID=xxxxxxxx,
(DSM) operation. The connection ID, correlation ID,
CORRELATION-ID=yyyyyyyyyyyy,
and logical-unit-of-work ID (LUW-ID) identify the user
LUW-ID=logical-unit-of-work-id=token
or application that encountered the problem.
Explanation: Correlation IDs beginning with ’0nn’, where ’nn’ is a
number, identify system agents.
Deletion failed in CSECT ’DSNPmmmm’ for the reason
identified by RC. (Refer to Codes.) The connection ID, A LUW-ID of ’*’ indicates that the thread does not have
correlation ID, and logical-unit-of-work ID (LUW-ID) a LUW-ID. If the LUW-ID is not an ’*’, the value is a
identify the user or application that encountered the logical-unit-of-work-id that is assigned to the thread
problem. Correlation IDs beginning with ’0nn’, where followed by an ’=’ sign and a token value, which can
’nn’ is a number, identify system agents. be used in place of logical-unit-of-work-id in any DB2
command that accepts logical-unit-of-work-id as input.
The value of the LUWID is alogical-unit-of-work-id that
is assigned to the thread followed by an ’=’ sign and a Messages that have the same connection ID, correlation
token value, which can be used in place of ID, and LUW-ID relate to the same user. This makes it
logical-unit-of-work-id in any DB2 command that possible to scan a number of DSNP-prefixed messages
accepts logical-unit-of-work-id as input. and group activities involving a given user.
Messages that have the same connection ID, correlation This is not a major problem. However, the data set will
ID, and LUWID relate to the same user. This makes it not properly reflect subsequent deletions from the
possible to scan a number of DSNP-prefixed messages volume list in its storage group (via ALTER
and group activities involving a given user. STOGROUP command in SQL), because the data set’s
integrated catalog facility (ICF) catalog entry still
System action: contains the volume serial numbers.
DB2 terminates its actions associated with the current If needed, the storage group in question can be
SQL request. DB2 might terminate the current SQL identified by issuing an SQL SELECT to get
request or the unit of recovery that issued the request. information about the table space or index that is
Operator response: identified by the third and fourth qualifiers (database
name, table space name) in the data set name. attention if it appears on the MVS operator’s console.
The installation should consider directing DB2
System action:
messages to a console other than the operator’s console.
Operation continues.
System programmer response:
Operator response:
If you suspect an error in DB2, refer to Part 2 of
This message is directed to the database administrator Diagnosis Guide and Reference for information on
or the system administrator. Bring it to that person’s identifying and reporting the problem.
attention if it appears on the MVS operator’s console.
Problem determination:
The installation should consider directing DB2
messages to a console other than the operator’s console. See Problem Determination for message DSNP001I for
this information.
System programmer response:
Severity:
Look for associated DSM and access method services
messages preceding this one to get additional 8 (error)
information. Attempt an ALTER REMOVEVOLUMES
access method services command, if appropriate, after
DSNP007I csect - EXTEND FAILED FOR
issuing a LISTCAT to see which volumes are recorded
data-set-name. RC=rrrrrrrr
as ’candidate’ in the integrated catalog facility (ICF)
CONNECTION-ID=xxxxxxxx,
catalog.
CORRELATION-ID=yyyyyyyyyyyy,
Problem determination: LUW-ID=logical-unit-of-work-id =token
See Problem Determination for message DSNP001I for Explanation:
this information. (However, there should not be a need
Extension failed in CSECT ’DSNPmmmm’ of the data
for VTOC or SYSLOG information for this case.)
space manager (DSM). The ’data-set-name’ identifies
the data set that is being extended. RC is the reason
DSNP006I csect - REQUIRED STOGROUP code, which indicates why the extend process failed. (
DEFINED DATA SET NOT See Codes.) The ’connection ID’, ’correlation ID’, and
AVAILABLE- data-set-name RC=rrrrrrrr ’logical-unit-of-work-id’ (LUW-ID) identify the user or
CONNECTION-ID=xxxxxxxx, application that encountered the problem. Correlation
CORRELATION-ID=yyyyyyyyyyyy, IDs beginning with ’0nn’, where ’nn’ is a number,
LUW-ID=logical-unit-of-work-id=token identify system agents.
Explanation: A LUW-ID of ’*’ (asterisk) indicates that the thread
does not have a LUW-ID. If the ’LUW-ID’ is not an
An attempt to alter the shareoptions of this data set
asterisk (’*’), the value is a ’logical-unit-of-work-id’ that
failed. The data set could not be accessed for the reason
is assigned to the thread followed by an ’=’ (equal sign)
indicated by RC. ( See Codes.) The connection ID,
and a token value, which can be used in place of
correlation ID, and logical-unit-of-work ID (LUWID)
’logical-unit-of-work-id’ in any DB2 command that
identify the user or application that encountered the
accepts ’logical-unit-of-work-id’ as input.
problem. Correlation IDs beginning with ’0nn’, where
’nn’ is a number, identify system agents. Messages that have the same ’connection ID’,
’correlation ID’, and ’LUW-ID’ relate to the same user.
The value of the LUWIDis a logical-unit-of-work-id that
This situation makes it possible to scan a number of
is assigned to the thread followed by an ’=’ sign and a
DSNP-prefixed messages and group activities involving
token value, which can be used in place of the
a given user.
logical-unit-of-work-id in any DB2 command that
accepts the logical-unit-of-work-id as input. System action:
Messages having the same connection ID, correlation The DSM terminates its actions associated with this
ID, and LUWID relate to the same user. This makes it extend request. Higher level functions might terminate
possible to scan a number of DSNP-prefixed messages if they cannot continue without a successful extend. In
and group activities involving a given user. this case, additional console messages and/or SQL
codes are produced. In other cases, higher level
System action:
functions might be able to resolve the space need
DB2 terminates its actions associated with the current without the extend, so they continue normally.
SQL request. DB2 might terminate the current SQL
Operator response:
request or the unit of recovery that issued the request.
See Operator Response for message DSNP001I for this
Operator response:
information.
This message is directed to the database administrator
System programmer response:
or the system administrator. Bring it to that person’s
282 Messages
DSNP008I • DSNP009I
The following sources of information are available to connection ID, correlation ID, and logical-unit-of-work
help determine the cause of the failure: ID (LUWID) identify the user or application that
v See the Programmer Response for message encountered the problem.
DSNP001I.
The value of the LUWID is alogical-unit-of-work-id that
v Analyze the RC value in conjunction with the
is assigned to the thread followed by an ’=’ sign and a
console messages.
token value, which can be used in place of
v The reason code might apply to the data set logical-unit-of-work-id in any DB2 command that
identified in the message or to another data set that accepts logical-unit-of-work-id as input.
is needed for the extend process. If the reason code
indicates a data set access failure, the console Messages having the same connection ID, correlation
messages indicate the data set name. For example, if ID, and LUWID relate to the same user. This makes it
the RC indicates ’resource unavailable’, console possible to scan a number of DSNP-prefixed messages
messages identify the resource that is unavailable. and group activities involving a given user.
Most likely, the message will be DSNT500I.
v Retrieve diagnostic information from the output of If the name of the data set in the message is different
the DISPLAY DB...RESTRICT or DISPLAY UTIL(*)... from the name of the original data set (for example,
commands. ’....A002’ instead of ’...A001’), a new data set might
v If the extend failed on a result table space, refer to need to be created. A different name indicates that the
“Sort Data Sets” in DB2 Performance Monitoring and original data set exceeded its limit.
Tuning Guide.
System action:
v For information about finding the SDWA refer to
Part 2 of Diagnosis Guide and Reference. DB2 terminates its actions associated with the current
SQL request or utility. DB2 might terminate the current
v See Section 4 (Volume 1) of Administration Guide for
SQL request or utility or the unit of recovery that
more information on recovering the
issued the request.
DSNDB01.DBD01 table space.
v To find out how the extend function operates, refer Operator response:
to “Improving disk utilization: space and device This message is directed to the database administrator
utilization” in DB2 Performance Monitoring and or the system administrator. Bring it to that person’s
Tuning Guide. attention if it appears on the MVS operator’s console.
Problem determination: The installation should consider directing DB2
messages to a console other than the operator’s console.
See Problem Determination for message DSNP001I.
System programmer response:
DSNP008I csect- REQUIRED USER-DEFINED Refer to the reason code in Codes. The return code
DATA SET NOT AVAILABLE-data-set- description might indicate that one of the following
name RC=rrrrrrrr CONNECTION- actions needs to be performed or it indicates the
ID=xxxxxxxx, CORRELATION- necessary steps:
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of- v If the data set does not exist, create it before
work-id=token attempting the create table space/index or extend
data set again.
Explanation:
v If the data set shareoptions are incorrect, modify the
One of the following actions applied against shareoptions with access method services (AMS).
user-defined data sets failed in CSECT ’DSNPmmmm’
v The appropriate AMS command is ALTER
of the data space manager (DSM):
SHAREOPTIONS.
v Create table space or index
Problem determination:
v Extend table space or index
v Process the SQL ALTER DATABASE statement See Problem Determination for message DSNP001I for
this information.
v Process the REORG TABLESPACE utility with
SHRLEVEL REFERENCE or CHANGE Severity:
Correlation IDs beginning with ’0nn’, where ’nn’ is a 8 (error)
number, identify system agents.
DSNP009I THE FOLLOWING ERROR MESSAGES
One or more of the data sets could not be accessed for
WERE RECEIVED FOR operation ON
the reason indicated by RC. (Refer to Codes.) The
data-set-name
Problem determination:
DSNP010I END OF ERROR MESSAGES.
CONNECTION-ID=xxxxxxxx, See Problem Determination for message DSNP001I for
CORRELATION-ID=yyyyyyyyyyyy, this information.
LUW-ID=logical-unit-of-work-id=token
Explanation: DSNP011I csect - MEDIA MANAGER SERVICES
ERROR FOR data-set-name.
Messages DSNP009I and DSNP010I enclose a block of
MMRC=cccccccc DSMRC=ffffffff
messages that are received by the data space manager
CONNECTION-ID=xxxxxxxx,
(DSM) subcomponent of DB2 in response to an access
CORRELATION-ID=yyyyyyyyyyyy,
method services (AMS) operation.
LUW-ID=logical-unit-of-work-id =token
operation
Explanation:
The access method services operation that was
being performed. The MMRC is the return code that DB2 received from
media manager services. Refer to the appropriate MVS
data-set-name
publication for a description of these codes. DSMRC is
The data set on which the operation was being
a DSM reason code that indicates which of the media
performed.
manager services functions, update or extend, failed.
(Refer to Codes.) The message is from CSECT
The prefix of the messages in the block is usually IDC
’DSNPmmmm’ of the data space manager (DSM). The
(access method services messages). However, the prefix
connection ID, correlation ID, and logical-unit-of-work
can also be IKJ (dynamic allocation) or other system
ID (LUW-ID) identify the user or application that
subcomponent IDs. Refer to the appropriate MVS
encountered the problem. Correlation IDs beginning
publication for descriptions of the enclosed messages.
with ’0nn’, where ’nn’ is a number, identify system
agents.
| The operation can be DEFINE CLUSTER, ALTER
| ADDVOLUMES, ALTER REMOVEVOLUMES, ALTER A LUW-ID of ’*’ indicates that the thread does not have
| NEWNAME, or DELETE CLUSTER. One or more other a LUW-ID. If the LUW-ID is not an ’*’, the value is a
| DSM messages follow this message to explain what logical-unit-of-work-id that is assigned to the thread
| happened as a result of the failure of this access followed by an ’=’ sign and a token value, which can
| method services request. The connection ID, correlation be used in place of logical-unit-of-work-id in any DB2
| ID, and logical-unit-of-work ID (LUW-ID) identify the command that accepts logical-unit-of-work-id as input.
| user or application that encountered the problem.
Messages that have the same connection ID, correlation
ID, and LUW-ID relate to the same user. This makes it
A LUW-ID of ’*’ indicates that the thread does not have possible to scan a number of DSNP-prefixed messages
a LUW-ID. If the LUW-ID is not an ’*’, the value is a and group activities involving a given user.
logical-unit-of-work-id that is assigned to the thread
followed by an ’=’ sign and a token value, which can System action:
be used in place of logical-unit-of-work-id in any DB2
The DSM terminates its actions associated with the
command that accepts logical-unit-of-work-id as input.
current SQL request. Higher level functions might
terminate the current SQL request or the unit of
Messages that have the same connection ID, correlation recovery that issued the request.
ID, and LUW-ID relate to the same user. This makes it
possible to scan a number of DSNP-prefixed messages Operator response:
and group activities involving a given user. Correlation
DSM messages are directed to either the database
IDs beginning with ’0nn’, where ’nn’ is a number,
administrator (DBA) or the system administrator.
identify system agents.
However, they can request that the operator issue an
System action: MVS WRITELOG operator command (for example, ’W
A’) to obtain MVS SYSLOG output. The SYSLOG
Operation continues. sometimes contains media manager messages that
Operator response: might be helpful to the DBA or system administrator in
determining why space could not be allocated.
This message is directed to the database administrator
or the system administrator. Bring it to that person’s System programmer response:
attention if it appears on the MVS operator’s console. This message might be preceded by one or more IEC or
The installation should consider directing DB2 ICY messages on the console or in SYSLOG. These
messages to a console other than the operator’s console. messages help to determine what happened and what
System programmer response: action to take.
284 Messages
DSNP012I • DSNP013I
See Problem Determination for message DSNP001I for SQL request. Higher level functions might terminate
this information. the current SQL request or the unit of recovery that
issued the request.
DSNP012I csect - ERROR IN ICF CATALOG System programmer response:
LOCATE FUNCTION FOR data-set-name
Correct the problem indicated by the catalog return and
CTLGRC=cc CTLGRSN=zzzzrrss
reason codes.
CONNECTION-ID=xxxxxxxx,
CORRELATION-ID=yyyyyyyyyyyy, Problem determination:
LUW-ID=logical-unit-of-work-id=token
See Problem Determination for message DSNP001I for
Explanation: this information.
CTLGRC and CTLGRSN are the return and reason
codes that DB2 received from SVC 26 call (ICF catalog DSNP013I INSUFFICIENT PRIMARY
locate function). The reason code is in the same format ALLOCATION SPACE TO FORMAT
as that returned to DB2 by the SVC 26 call. CONTROL PAGES IN DATA SET
data-set-name CONNECTION-
If CLTGRC is 4 or 8, CTLGRSN is associated with
ID=xxxxxxxx, CORRELATION-
access method services message IDC3009I. To
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
determine the name of the CSECT that set CTLGRSN,
work-id =token
convert zzzz from hexadecimal to EBCDIC, and append
the resulting two characters to ’IGG0CL’. For example, Explanation:
suppose that zzzz is C6C6. The EBCDIC equivalent of
X’C6C6’ is ’FF’, so the CSECT that set the reason code Data space manager (DSM) discovered that the primary
is IGG0CLFF. space quantity given in the data set definition was not
large enough. Formatting of required control
rr is the hexadecimal equivalent of the reason code information in the first several pages was not possible.
value that is documented in access method services The connection ID, correlation ID, and
message IDC3009I. ss is the hexadecimal equivalent of logical-unit-of-work ID (LUW-ID) identify the user or
the return code value that is documented in access application that encountered the problem.
method services message IDC3009I (the return code
follows the reason code.) Convert rr and ss to decimal. A LUW-ID of ’*’ indicates that the thread does not have
Then see the description of IDC3009I for explanations a LUW-ID. If the LUW-ID is not an ’*’, the value is a
of the reason code and return code. For example, logical-unit-of-work-id that is assigned to the thread
suppose that rrss is 0532. The decimal equivalent of followed by an ’=’ sign and a token value, which can
X’32’ is 50, and the decimal equivalent of X’05’ is 5. be used in place of logical-unit-of-work-id in any DB2
Therefore, in IDC009I, you need to look up a return command that accepts logical-unit-of-work-id as input.
code of 50 and a reason code of 5. Messages that have the same connection ID, correlation
If CTLGRC=AAAAAA08 and CTLGRSN=AAAAAA08, ID, and LUW-ID relate to the same user. This makes it
CTLGRSN is not associated with access method possible to scan a number of DSNP-prefixed messages
services message IDC3009I. AAAAAA08 indicates that and group activities involving a given user. Correlation
data-set-name is not in the ICF catalog. IDs beginning with ’0nn’, where ’nn’ is a number,
identify system agents.
The connection ID, correlation ID, and LUW-ID identify
the user or application that encountered the problem. System action:
Correlation IDs beginning with ’0nn’, where ’nn’ is a DSM terminates its actions associated with the current
number, identify system agents. SQL request. Higher level functions might terminate
An LUW-ID with an asterisk (*) indicates that the the current SQL request or the unit of recovery that
thread does not have an LUW-ID. If the LUW-ID is not issued the request.
an asterisk (*), the value is a logical-unit-of-work-id that Operator response:
is assigned to the thread followed by an equals sign (=)
and a token value, which can be used in place of This message is directed to the database administrator
logical-unit-of-work-id in any DB2 command that accepts or the system administrator. Bring it to that person’s
logical-unit-of-work-id as input. attention if it appears on the MVS operator’s console.
The installation should consider directing DB2
Messages that have the same connection ID, correlation messages to a console other than the operator’s console.
ID, and LUW-ID relate to the same user. This makes it
possible to scan a number of DSNP-prefixed messages System programmer response:
and group activities involving a given user. This should occur only for table spaces or indexes that
System action: are not storage group defined. (The DB2 interpreter
forces the initial allocation to be large enough if a
DB2 terminates its actions associated with the current storage group is used.) Check both the page size
specification (4KB or 32KB) and the number of control Provide the console sheet and a dump. A GTF trace
pages required (2 for table space, 3 for index space). might also be required. If you suspect an error in DB2,
Specify the primary allocation value again so that at refer to Part 2 of Diagnosis Guide and Reference for
least (pages multiplied by page size) bytes are information on identifying and reporting the problem.
allocated. Refer to the explanation section of this message for
additional problem determination information.
Problem determination:
See Problem Determination for message DSNP001I for
DSNP015I csect - IRLM MANUAL UNLOCK
this information.
REQUEST FAILED FOR data-set-name.
RC=rr,SC=ssssssss, CONNECTION-
DSNP014I IRLM MANUAL LOCK REQUEST ID=xxxxxxxx, CORRELATION-
FAILED FOR data-set-name. ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
RC=rr,SC=ssssssss, CONNECTION- work-id=token
ID=xxxxxxxx, CORRELATION-
Explanation:
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
work-id=token DB2 requested a manual unlock on a data set, but the
unlock could not be performed for reasons specified in
Explanation:
RC and SC. RC and SC are the return code and reason
DB2 requested a manual lock on a data set, but the lock code from IRLM. RC and the first two digits of SC are
could not be obtained for reasons specified in RC and documented in Codes The connection ID, correlation ID,
SC. RC and SC are the return code and reason code and logical-unit-of-work ID (LUW-ID) identify the user
from IRLM. RC and the first two digits of SC are or application that encountered the problem.
documented in Codes. The connection ID, correlation
A LUW-ID of ’*’ indicates that the thread does not have
ID, and logical-unit-of-work ID (LUW-ID) identify the
a LUW-ID. If the LUW-ID is not an ’*’, the value is a
user or application that encountered the problem.
logical-unit-of-work-id that is assigned to the thread
A LUW-ID of ’*’ indicates that the thread does not have followed by an ’=’ sign and a token value, which can
a LUW-ID. If the LUW-ID is not an ’*’, the value is a be used in place of logical-unit-of-work-id in any DB2
logical-unit-of-work-id that is assigned to the thread command that accepts logical-unit-of-work-id as input.
followed by an ’=’ sign and a token value, which can
Messages that have the same connection ID, correlation
be used in place of logical-unit-of-work-id in any DB2
ID, and LUW-ID relate to the same user. This makes it
command that accepts logical-unit-of-work-id as input.
possible to scan a number of DSNP-prefixed messages
Messages that have the same connection ID, correlation and group activities involving a given user. Correlation
ID, and LUW-ID relate to the same user. This makes it IDs beginning with ’0nn’, where ’nn’ is a number,
possible to scan a number of DSNP-prefixed messages identify system agents.
and group activities involving a given user. DSNP001I
System action:
or DSNP007I follow this message. Correlation IDs
beginning with ’0nn’, where ’nn’ is a number, identify The current SQL or the unit of recovery that issued the
system agents. request might be terminated.
If message DSNT376I was received before message Operator response:
DSNP014I, the lock request failed because of a timeout
This message is directed to the database administrator
condition. Otherwise, refer to the IRLM return and
or the system administrator. Bring it to that person’s
reason codes for an explanation of the failure.
attention if it appears on the MVS operator’s console.
System action: The installation should consider directing DB2
messages to a console other than the operator’s console.
The current SQL or the unit of recovery that issued the
request might be terminated. System programmer response:
Operator response: Investigate the problem indicated by the IRLM return
and reason code.
This message is directed to the database administrator
or the system administrator. Bring it to that person’s Problem determination:
attention if it appears on the MVS operator’s console.
Provide the console sheet and a dump. A GTF trace
The installation should consider directing DB2
might also be required. If you suspect an error in DB2,
messages to a console other than the operator’s console.
refer to Part 2 of Diagnosis Guide and Reference for
System programmer response: information on identifying and reporting the problem.
See the explanation section of this message for
Investigate the problem indicated by the IRLM return
additional problem determination information.
and reason code.
Problem determination:
286 Messages
DSNP016I • DSNP018I
Explanation:
DSNP016I CREATE FAILED FOR pageset-name.
RC=rrrrrrrr CONNECTION- Reset failed in the data space manager (DSM)
ID=xxxxxxxx, CORRELATION- subcomponent of DB2 for a table space or index space
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of- for the reason given in RC. (Refer to Codes.) The
work-id =token ’pageset-name format is dbname.tiname, where dbname is
the database name and tiname is the table space or
Explanation:
index space name.
Creation of a table space or index space failed in the
This message identifies the function that was in
data space manager (DSM) for the reason given in RC.
progress at the time of a failure. The specific failure is
(Refer to Codes.) The pageset-name format is
usually identified by a preceding message. The
’dbname.tiname.instance’, where ’dbname’ is the
connection ID, correlation ID, and logical-unit-of-work
database name and ’tiname’ is the table space or index
ID (LUW-ID) identify the user or application that
space name.
encountered the problem.
This message identifies the function that was in
A LUW-ID of ’*’ indicates that the thread does not have
progress at the time of a failure. The specific failure is
a LUW-ID. If the LUW-ID is not an ’*’, the value is a
usually identified by a preceding message. The
logical-unit-of-work-id that is assigned to the thread
connection ID, correlation ID, and logical-unit-of-work
followed by an ’=’ sign and a token value, which can
ID (LUW-ID) identify the user or application that
be used in place of logical-unit-of-work-id in any DB2
encountered the problem.
command that accepts logical-unit-of-work-id as input.
A LUW-ID of ’*’ indicates that the thread does not have
Messages that have the same connection ID, correlation
a LUW-ID. If the LUW-ID is not an ’*’, the value is a
ID, and LUW-ID relate to the same user. This makes it
logical-unit-of-work-id that is assigned to the thread
possible to scan a number of DSNP-prefixed messages
followed by an ’=’ sign and a token value, which can
and group activities involving a given user. Correlation
be used in place of logical-unit-of-work-id in any DB2
IDs beginning with ’0nn’, where ’nn’ is a number,
command that accepts logical-unit-of-work-id as input.
identify system agents.
Messages that have the same connection ID, correlation
System action:
ID, and LUW-ID relate to the same user. This makes it
possible to scan a number of DSNP-prefixed messages DSM terminates its actions associated with the current
and group activities involving a given user. Correlation SQL request. Higher level functions might terminate
IDs beginning with ’0nn’, where ’nn’ is a number, the current SQL request or the unit of recovery that
identify system agents. issued the request.
System action: Operator response:
DSM terminates its actions associated with the current This message is directed to the database administrator
SQL request. Higher level functions might terminate or the system administrator. Bring it to that person’s
the current SQL request or the unit of recovery that attention if it appears on the MVS operator’s console.
issued the request. The installation should consider directing DB2
messages to a console other than the operator’s console.
Operator response:
System programmer response:
This message is directed to the database administrator
or the system administrator. Bring it to that person’s Investigate the problem indicated by the reason code
attention if it appears on the MVS operator’s console. and preceding messages, and correct it, if possible.
The installation should consider directing DB2
messages to a console other than the operator’s console. Problem determination:
System programmer response: See Problem Determination for message DSNP001I for
this information.
Investigate the problem indicated by reason code and
preceding messages, and correct it, if possible.
DSNP018I DROP FAILED FOR pageset-name.
Problem determination: RC=rrrrrrrr CONNECTION-
ID=xxxxxxxx, CORRELATION-
See Problem Determination for message DSNP001I for
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-
this information.
work-id =token
Explanation:
DSNP017I RESET FAILED FOR pageset-name.
RC=rrrrrrrr CONNECTION- Drop failed in the data space manager (DSM)
ID=xxxxxxxx, CORRELATION- subcomponent of DB2 for a table space or index space
ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of- for the reason given in RC. Refer to Codes. The
work-id =token ’pageset-name’ format is ’dbname.tiname’, where
’dbname’ is the database name and ’tiname’ is the table followed by an ’=’ sign and a token value, which can
space or index space name. This message identifies the be used in place of logical-unit-of-work-id in any DB2
function that was in progress at the time of a failure. command that accepts logical-unit-of-work-id as input.
The specific failure is usually identified by a preceding
Messages that have the same connection ID, correlation
message. The connection ID, correlation ID, and
ID, and LUW-ID relate to the same user. This makes it
logical-unit-of-work ID (LUW-ID) identify the user or
possible to scan a number of DSNP-prefixed messages
application that encountered the problem.
and group activities involving a given user. Correlation
A LUW-ID of ’*’ indicates that the thread does not have IDs beginning with ’0nn’, where ’nn’ is a number,
a LUW-ID. If the LUW-ID is not an ’*’, the value is a identify system agents.
logical-unit-of-work-id that is assigned to the thread
System action:
followed by an ’=’ sign and a token value, which can
be used in place of logical-unit-of-work-id in any DB2 Operation continues.
command that accepts logical-unit-of-work-id as input.
Operator response:
Messages that have the same connection ID, correlation
ID, and LUW-ID relate to the same user. This makes it This message is directed to the database administrator
possible to scan a number of DSNP-prefixed messages or the system administrator. Bring it to that person’s
and group activities involving a given user. Correlation attention if it appears on the MVS operator’s console.
IDs beginning with ’0nn’, where ’nn’ is a number, System programmer response:
identify system agents.
The data set and corresponding page set piece or
System action: partition can usually continue to be used by the DB2
DSM terminates its actions associated with the current subsystem. However, they should be stopped and
SQL request. Higher level functions might terminate restarted at the earliest possible time in order to
the current SQL request or the unit of recovery that synchronize the allocation control blocks with the
issued the request. integrated catalog facility (ICF) catalog volume list.
This message is directed to the database administrator See Problem Determination for message DSNP001I for
or the system administrator. Bring it to that person’s this information.
attention if it appears on the MVS operator’s console.
The installation should consider directing DB2 DSNP020I csect-name - USER DEFINED
messages to a console other than the operator’s console. ATTRIBUTES INCORRECT FOR
System programmer response: data-set-name. RC=rrrrrrrr
CONNECTION-ID=xxxxxxxx,
Investigate the problem indicated by the reason code CORRELATION-ID=yyyyyyyy,
and preceding messages, and correct it, if possible. LUW-ID=logical-unit-of-work-id =token
Problem determination: Explanation:
See Problem Determination for message DSNP001I for The specified data set was access method services
this information. user-defined and does not have the required DB2
attributes. The connection ID, correlation ID, and
LUW-ID identify the user or application that
DSNP019I csect - REALLOCATE FAILED FOR
encountered the problem.
data-set-name. RC=rrrrrrrr
CONNECTION-ID=xxxxxxxx, The value of the LUWID is a’logical-unit-of-work-id’
CORRELATION-ID=yyyyyyyyyyyy, that is assigned to the thread, followed by an ’=’ sign
LUW-ID=logical-unit-of-work-id =token and a token value, which can be used in place of
’logical-unit-of-work-id’ in any DB2 command that
Explanation:
accepts ’logical-unit-of-work-id’ as input.
After a successful ALTER REMOVEVOLUMES request,
Messages having the same connection ID, correlation
the data space manager (DSM) subcomponent of DB2
ID, and LUWID relate to the same user. This makes it
was unable to reallocate the data set for the reason
possible to scan a number of DSNP-prefixed messages
indicated by RC. (Refer to Codes.) The connection ID,
and group activities involving a given user. Correlation
correlation ID, and logical-unit-of-work ID (LUW-ID)
IDs beginning with ’0nn’, where ’nn’ is a number,
identify the user or application that encountered the
identify system agents.
problem.
System action:
A LUW-ID of ’*’ indicates that the thread does not have
a LUW-ID. If the LUW-ID is not an ’*’, the value is a No action is taken with the named data set. An error
logical-unit-of-work-id that is assigned to the thread code is returned and a dump is not taken.
288 Messages
DSNP021I • DSNP026I
Operator response:
DSNP022I csect-name EXTEND DBET RECORDING
Notify the system programmer. FAILED FOR data-set-name, RC=rrrrrrrr,
SC=ssssssss, DBETSC=nnnnnnnn,
System programmer response: CONNECTION-ID=xxxxxxxx,
Delete the named data set and define it with the correct CORRELATION-ID=yyyyyyyyyyyy,
attributes. LUW-ID=logical-unit-of-work-id=token
Obtain an access method services LISTCAT for the This is an internal error. The connection ID, correlation
named data set’s attributes. Refer to Part 2 of ID, and logical-unit-of-work ID (LUW-ID) identify the
Administration Guide for the correct data set definition user or application that encountered the problem.
attributes. An LUW-ID of ’*’ indicates that the thread does not
Severity: have an LUW-ID. If the LUW-ID is not an ’*’, the value
is a logical-unit-of-work-id that is assigned to the
8 (error) thread followed by an ’=’ sign and a token value,
which can be used in place of the logical-unit-of-
DSNP021I csect-name EXTEND NOTIFY FAILED work-id in any DB2 command that accepts the
FOR data-set-name, SC=ssssssss, logical-unit-of-work-id as input.
NOTESC=nnnnnnnn, Messages that have the same connection ID, correlation
CONNECTION-ID=xxxxxxxx, ID, and LUW-ID relate to the same user. This makes it
CORRELATION-ID=yyyyyyyyyyyy, possible to scan a number of DSNP-prefixed messages
LUW-ID=logical-unit-of-work-id=token and group activities involving a given user. Correlation
Explanation: IDs beginning with ’0nn’, where ’nn’ is a number,
identify system agents.
This is an internal error. The connection ID, correlation
ID, and logical-unit-of-work ID (LUW-ID) identify the System action:
user or application that encountered the problem. The current SQL statement or the unit of recovery that
An LUW-ID of ’*’ indicates that the thread does not issued the request might be terminated.
have an LUW-ID. If the LUW-ID is not an ’*’, the value Problem determination:
is a logical-unit-of-work-id that is assigned to the
thread followed by an ’=’ sign and a token value, Obtain the console sheet and a dump. A GTF trace
which can be used in place of the logical-unit-of- might also be required.
work-id in any DB2 command that accepts the Refer to part 2 of Diagnosis Guide and Reference for
logical-unit-of-work-id as input. information on identifying and reporting the problem.
Messages that have the same connection ID, correlation
ID, and LUW-ID relate to the same user. This makes it DSNP026I csect-name DATASET IS NOT
possible to scan a number of DSNP-prefixed messages ALLOWED TO BE DELETED
and group activities involving a given user. Correlation data-set-name, RC=rrrrrrrr,
IDs beginning with ’0nn’, where ’nn’ is a number, CONNECTION-ID=xxxxxxxx,
identify system agents. CORRELATION-ID=yyyyyyyyyyyy,
If message DSNT376I was received before message LUW-ID=logical-unit-of-work-id=token
DSNP021I, the notify request failed because of a Explanation:
timeout condition.
During clean up of the shadow data set in the final
System action: step of online REORG, an error is detected due to an
The current SQL statement or the unit of recovery that attempt to delete a regular table or index space data
issued the request might be terminated. set. The formula used internally to calculate the scale of
the result for decimal division is explained in chapter 3
Problem determination: SQL Reference. The connection ID, correlation ID, and
Obtain the console sheet and a dump. A GTF trace logical unit of work ID (LUWID) identify the user or
might also be required. application that encountered the problem. Correlation
IDs beginning with ’0nn’, where ’nn’ is a number,
Refer to Diagnosis Guide and Reference for information identify system agents.
on identifying and reporting the problem.
The value of the LUWID is assigned to the thread
followed by an ’=’ sign and a token value, that can be
used in place of the LUWID in any DB2 command that
accepts it as input.
Messages that have the same connection ID, correlation Diagnosis Guide and Reference for information on
ID, and LUWID relate to the same user. This makes it identifying and reporting the problem.
possible to scan a number of DSNP-prefixed messages
Problem determination:
and group activities involving a given user.
See ’Problem Determination’ for message DSNP001I for
System action:
this information.
No action is taken with the named data set. An error
Severity:
code is returned and a dump is not taken.
8 (error)
Operator response:
Notify the system programmer.
DSNP028I csect-name HSM RECALL FAILED FOR
System programmer response: DSNAME = dsn
HSMRC=rrrrrrrr,HSMRSN=ssssssss
Determine the failing environment. Refer to part 2 of
CONNECTION ID=xxxxxxxx,
Diagnosis Guide and Reference for information on
CORRELATION ID=yyyyyyyyyyyy,
identifying and reporting the problem.
LUW-ID=logical-unit-of-work-id =token
Problem determination:
Explanation:
This is an internal error in the online REORG of utility.
This message indicates that a required data set was
See the ’Problem Determination’ section of message
migrated by HSM and an attempt to recall the data set
DSNP001I for this information.
failed, preventing DB2 from accessing the data set. The
HSMRC and HSMRSN fields can be used to determine
DSNP027I csect-name RENAME FAILED OLD the HSM failure. See Problem Determination below.
DATASET=data-set-name, NEW The connection ID, correlation ID, and
DATASET=data-set-name, RC=rrrrrrrr, ’logical-unit-of-work ID’ (LUW-ID) identify the user or
CONNECTION-ID=xxxxxxxx, application that encountered the problem.
CORRELATION-ID=yyyyyyyyyyyy,
A LUW-ID of ’*’ indicates that the thread does not have
LUW-ID=logical-unit-of-work-id=token
a LUW-ID. If the LUW-ID is not an ’*’, the value is a
Explanation: ’logical-unit-of-work-id’ that is assigned to the thread
followed by an ’=’ sign and a token value, which can
An attempt to alter the data set name failed. The be used in place of ’logical-unit-of-work-id’ in any DB2
connection ID, correlation ID, and logical unit of work command that accepts ’logical-unit-of-work-id’ as
ID (LUWID) identify the user or application that input.
encountered the problem. Correlation IDs beginning
with ’0nn’, where ’nn’ is a number, identify system Messages that have the same connection ID, correlation
agents. ID, and LUW-ID relate to the same user. This makes it
possible to scan a number of DSNP-prefixed messages
The value of the LUWID is assigned to the thread and group activities involving a given user. Correlation
followed by an ’=’ sign and a token value, that can be IDs beginning with ’0nn’, where ’nn’ is a number,
used in place of the LUWID in any DB2 command that identify system agents.
accepts it as input.
System action:
Messages that have the same connection ID, correlation
ID, and LUWID relate to the same user. This makes it DSM terminates its action with the associated data set.
possible to scan a number of DSNP-prefixed messages Higher level functions that issued the recall request
and group activities involving a given user. might terminate.
DB2 terminates its actions associated with the current Notify the system programmer.
SQL request. DB2 might terminate the current SQL
System programmer response:
request or the unit of recovery that issued the request.
Investigate the reason for the HSM recall failure. Use
Operator response:
the information in this message to help resolve this
This message is directed to the database administrator problem. Additional messages on the MVS operator’s
or the system administrator. Bring it to that person’s console might be associated with this message.
attention if it appears on the MVS operator’s console.
Problem determination:
The installation should consider directing DB2
messages to a console other than the operator’s console. If the HSMRSN is 999, refer to the following list for the
explanation:
System programmer response:
If you suspect an error in DB2, refer to Part 2 of
290 Messages
DSNP030I • DSNP031I
292 Messages
Chapter 12. DSNQ messages
Message identifiers that begin with DSN1 communicate information about service
facilities.
DSNQ001I MQListener was invoked with no major DSNQ004I MQListener was invoked with an illegal
function on the command line. value for the parameter name command
line parameter: parameter value.
Explanation:
Explanation:
The MQListener command line failed to specify a major
function, such as help, run, add, remove, or show. The MQListener command line contained an illegal
value for the parameter name parameter. The illegal
User response:
value was parameter value.
Consult MQListener documentation and re-run
User response:
MQListener with the function that was intended. For
more information, run: Consult MQListener documentation and re-run
v db2mqln1/db2mqln2 help MQListener with the desired parameters. For more
information, run
Severity:
v db2mqln1/db2mqln2 help
8 (Error)
Severity:
8 (Error)
DSNQ002I MQListener was invoked with an
unknown command line parameter
parameter name. DSNQ010I MQListener encountered a database
error accessing subsystem subsystem
Explanation:
name during operation operation name:
The MQListener command line contained an unknown sqlstate = sqlstate value (sqlcode = sqlcode
parameter parameter name. value).
Consult MQListener documentation and re-run MQListener encountered a DB2 database error
MQListener with the desired parameters. For more accessing subsystem subsystem name while executing
information, run operation operation name. The resulting sqlstate was
v db2mqln1/db2mqln2 help sqlstate value (sqlcode sqlcode value).
DSNQ020I MQListener encountered a MQ error Ensure that MQSeries is properly installed and
error executing operation operation name running. Consult the MQSeries documentation for more
on object object name in queue manager information, particularly the Application Programming
queue manager name: reason code = reason Reference for more information about the reason code.
code value.
Severity:
Explanation:
4 (Warning)
MQListener encountered a MQ error error while
executing operation operation name on object object name
DSNQ030I MQListener encountered a DB2
in queue manager queue manager name. The resulting
database error attempting to add a new
reason code was reason code value.
task to the MQListener configuration
User response: configuration name in the subsystem
subsystem name. The input queue
Ensure that MQSeries® is properly installed and specified in the task was input queue
configured, and accessible to the user running name and the specified queue manager
MQListener. Consult the MQSeries documentation for was queue manager name. The resulting
more information, particularly the Application sqlstate was sqlstate value ( sqlcode =
Programming Reference for more information about the sqlcode value ).
reason code.
Explanation:
Severity:
MQListener encountered a DB2 database error while
8 (Error) attempting to add a new task to the MQListener
configuration configuration name in the subsystem
subsystem name. The input queue specified in the task
was input queue name and the specified queue manager
was queue manager name. The resulting sqlstate was
sqlstate value ( sqlcode = sqlcode value ).
294 Messages
DSNQ040I • DSNQ071I
Explanation:
DSNQ074I A thread running the task specified in
MQListener encountered an unsupported datatype in the configuration configuration name by
the signature of the stored procedure schema name. the input queue input queue name and
procedure name in the subsystem subsystem name. The queue manager queue manager name has
datatype was datatype value. exited.
Consult the MQListener documentation and ensure that A thread running the task specified in the configuration
the stored procedure has the correct datatype. configuration name by the input queue input queue name
and queue manager queue manager name has exited.
Severity:
User response:
8 (Error)
None. This is the formal notification of a thread exit,
expected during shutdown or restart.
DSNQ072I MQListener was unable to start a thread
running a task specified in the Severity:
configuration configuration name by the
0 (Informational)
input queue input queue name and queue
manager queue manager name. The ECF
error code was error code value. DSNQ075I MQListener encountered a DB2
database error while running the stored
Explanation:
procedure schema name. procedure name in
MQListener was unable to start a thread running a task subsystem subsystem name during
that was specified in the configuration configuration operation operation name. The resulting
name by the input queue input queue name and queue sqlstate was sqlstate value ( sqlcode =
manager queue manager name. The ECF error code was sqlcode value ).
error code value.
Explanation:
User response:
MQListener encountered a DB2 database error while
Ensure that MQListener configuration is correct, running the stored procedure schema name. procedure
especially the -numInstances parameter, and that the name in subsystem subsystem name during operation
MQListener process has sufficient system resources to operation name. The resulting sqlstate was sqlstate value (
execute the required number of simultaneous tasks. sqlcode = sqlcode value ).
Explanation: 8 (Error)
296 Messages
DSNQ081I • DSNQ082I
300 Messages
DSNR010I • DSNR014I
System programmer response: There was an error in processing the RURE display
table. One of these ERROR LOCATION CODES tells
Increase the region size of the ssnmMSTR address space what function the module was attempting to perform:
before restarting DB2 again.
X’0001’ Trace entry to the module
Problem determination:
X’0002’ Build header for the display table
The size requested is approximately 110 bytes for each
unit of recovery (UR). See the message DSNR004I to X’0003’ Build entries for the display table
determine the total number of URs to process. Then get
X’0004’ Call DSNRWTO to display the table
the 00E2xxxx reason code from the DSNR009I header.
Use these two numbers to determine the reason for the X’0005’ Trace exit from the module
shortage.
X’0006’ Get message text
System action:
DSNR010I AN ERROR OCCURRED IN THE RURE
STATUS TABLE SORT/TRANSLATE The system continues to restart but the RESTART...
MODULE (DSNRUSOR), THE ERROR STATUS TABLE is not displayed.
LOCATION CODE = xxxx
Operator response:
Explanation:
Save the console output and inform the system
There was an error in processing the RURE display programmer.
table. One of these ERROR LOCATION CODES tells
what function the module was attempting to perform: System programmer response:
X’0001’ Trace entry to the module Use the error code in the message to fill in the problem
description.
X’0002’ Sort the recoverable UR display table
Problem determination:
X’0003’ Translate the recoverable UR table
The ERROR CODE describes the problem area and
X’0004’ Convert the store clock value for display should be used in the problem description. A record
was added to the SYS1.LOGREC containing the value
X’0005’ Trace exit from the module
DSNRUDIS, and the PSW and CSECT at the time of the
System action: error. This error indicates an application program check
of some type.
The system continues to restart but the RESTART...
STATUS TABLE is not displayed. Error codes other than X’0006’ indicate an application
program check of some type. Code X’0006’ indicates an
Operator response:
error attempting to locate the table text. The trace entry
Save the console output and inform the system for DSNRUDIS contains the return and reason codes
programmer. from the Get Text request. That information should be
used to fill in the problem description.
System programmer response:
Use the error code in the message to fill in the problem DSNR014I EXCLUDED RURE TABLE
description.
Explanation:
Problem determination:
This message contains a list of RUREs which are being
The ERROR CODE tells the problem area and should bypassed because of the conditional restart. Either they
be used in the problem description. A record was were to be processed in a phase that was bypassed or
added to the SYS1.LOGREC that contains the PSW and they were outside the log range.
module at the time of the error. This error indicates an
application program check of some type. The following list describes each column of the table:
T Connection type. The values could be:
B Batch: a batch program or QMF user.
I Internal: a system service being
performed on some user’s behalf.
PLAN Name of the plan allocated to the UR. By specifying the STARTRBA and/or ENDRBA on the
CRESTART control statement, change log inventory
S Restart status of the UR. When DB2 came (DSNJU003) utility selects an appropriate RBA.
down, the UR was in one of these situations:
Problem determination:
A INABORT: The UR was in the
’must-complete’ phase of abort, and is Print the complete checkpoint records queue by using
yet to be completed. the print log map (DSNJU004) utility. Select a
checkpoint RBA from this queue or let the change log
C INCOMMIT: The UR was in the inventory (DSNJU003) utility make the selection.
’must-complete’ phase of commit, and
is yet to be completed.
DSNR016I STARTRBA xxxxxxxxxxxx VALIDATION
D INDOUBT: The UR had completed FAILED
the first phase of commit, but DB2
had not received the second phase Explanation:
instruction. The UR must be A scan from the STARTRBA failed to find a complete
remembered so it can be resolved log record. Either the entire log was scanned and no
when the owning subsystem complete record was found, or the log manager found
reattaches. an invalid log record. The log manager sends the error
F INFLIGHT: The UR had not messages to the console indicating a bad log record.
completed the first phase of commit, System action:
and will be backed out.
Restart abends.
P POSTPONED ABORT: The UR has
not yet completed backout. Backout Operator response:
must be completed outside of DB2 Record the log manager message numbers and inform
restart by means of the -RECOVER the system programmer.
POSTPONED command.
System programmer response:
URID UR identifier, the log RBA of the beginning of
this unit of work. It is the earliest RBA Use DSN1LOGP to determine a STARTRBA to use for
required to process the UR during Restart. restart. The recovery manager uses the STARTRBA as a
starting point for its search of the beginning of a valid
DAY The day the UR was created, in the format log record.
’ddd’. It is approximately the time of the first
SQL statement of the application or the first
SQL statement following a commit point. DSNR017I RESTART IS BEING TERMINATED
BECAUSE OF CSRONLY
TIME The time the UR was created, in the format SPECIFICATION IN CRCR
’hh mm ss ’. It is approximately the time of
the first SQL statement of the application or Explanation:
the first SQL statement following a commit
The restart procedure only completed the first phase of
point.
startup. The status displayed during this partial restart
System action: can be used to build the conditional restart control
record (CRCR).
302 Messages
DSNR018I • DSNR022I
DSNR020I csect-name START MEMBER member, OR This message is issued before this DB2 member enters
REPLY ’NO’ OR ’QUIESCED’ the group restart process. The group restart process is
synchronized among all group members that are
Explanation: starting and therefore participating in this group
During a group restart, the group member issuing this restart. After this DB2 member synchronizes with other
message attempted to access the BSDS for member members, it is possible that no peer processing will be
member, and either was not able to access the BSDS, or necessary; in that case message DSNR022I immediately
discovered that the BSDS was modified by the change follows this message.
log inventory (DSNJU003) utility since that member If it is necessary to recover both the SCA and retained
was last started. In either case, this DB2 is not able to locks, this message is issued twice; once for SCA
perform peer restart for member member. recovery and again for the recovery of the retained
For group restart to continue, the identified member locks.
must be started. System action:
If it is not possible to start the other member and you The subsystem begins group restart processing.
want to terminate this group restart, you can reply
’NO’ to this message. Replying ’NO’ to this message
causes this DB2 to terminate with a reason code of DSNR022I csect-name DB2 SUBSYSTEM HAS
00D900E1. You then have to reply ’NO’ to this message COMPLETED GROUP RESTART FOR
for all remaining members participating in this group PEER MEMBERS
restart. Explanation:
If you are sure that the identified member was This DB2 subsystem, which previously issued message
quiesced the last time it was started, that is, it was DSNR021I, completed the group restart phase to
stopped with a -STOP DB2 MODE(QUIESCE) recover the shared communications area (SCA) or
This message is issued only if messages DSNR021I and This group member waits for a valid reply to this
DSNR023I were issued. message.
304 Messages
DSNR034E • DSNR037I
processed. rba2 is the RBA of the last log record that DB2 continues processing. If statistics class 3 is turned
will be read in this phase of restart. on, IFCID 0313 is written.
System action: System programmer response:
DB2 restart continues. Consult with the application programmer to determine
if this is a problem UR. See Part 4 of Administration
User response:
Guide for more information about problems caused by
This is an information only message. uncommitted URs. If the UR is caused by an
application program, you can use CANCEL THREAD
to delete the UR, if necessary. If an uncommitted UR is
DSNR034E csect-name THERE CANNOT BE MORE deleted, DB2 will undo the changes. The amount of
THAN TWO RELEASE LEVELS OF time required for this process depends on the amount
DB2 RUNNING IN THE GROUP of work done by the UR.
Explanation: Programmer response:
You attempted to start a DB2 that was at a release level Ensure that the application commits frequently enough,
that cannot coexist in the data sharing group. There are or consult with your DB2 administrator about
already two different releases of DB2 currently running decreasing the frequency of the check.
in the data sharing group.
System action: DSNR036I csect-name UNRESOLVED UR
DB2 terminates. ENCOUNTERED DURING
CHECKPOINT - CORRELATION
System programmer response: NAME = xxxxxxxxxxx CONNECTION
If you are sure that the startup procedure is pointing to ID = yyyyyyyy LUWID =
the correct set of load libraries, you must stop any DB2 logical-unit-of-work-id PLAN NAME =
subsystems that cannot coexist with the one you are xxxxxxxx AUTHID = xxxxxxxx
attempting to start. Explanation:
See for more information about release coexistence in a DB2 has detected an INDOUBT unit of recovery (UR)
data sharing group. during a checkpoint. The purpose of this message is to
remind the operator that an INDOUBT UR or
DSNR035I csect-name WARNING - POSTPONED ABORT UR exists.
UNCOMMITTED UR AFTER nn CORRELATION name, CONNECTION ID, and LUWID
CHECKPOINTS - CORRELATION together identify a thread associated with the UR. If the
NAME = xxxxxxxxxxxx CONNECTION LUWID is an ’*’, it indicates that the thread originated
ID = yyyyyyyy LUWID = at this site. PLAN NAME and AUTHID further identify
logical-unit-of-work-id=token PLAN NAME the thread associated with the indoubt UR.
= xxxxxxxx AUTHID = xxxxxxx END
USER ID = xxxxxxxx TRANSACTION System action:
NAME = xxxxxxxx WORKSTATION DB2 continues processing. If statistics class 3 is turned
NAME = xxxxxxxx on, IFCID 0313 is written.
Explanation: System programmer response:
This message indicates that during checkpoint, DB2 Consult with the application programmer to determine
encountered an uncommitted UR that has an whether this is a problem UR. See Part 4 of
INFLIGHT status. Administration Guide for more information about
The value nn is cumulative, and it indicates the number resolving INDOUBT URs.
of checkpoints taken since the beginning of the UR.
CORRELATION name, CONNECTION ID, and LUWID DSNR037I csect-name WARNING - THE TCP/IP
together identify a thread associated with the UR. If the DRDA PORT NUMBER IS CHANGED
LUWID is an ’*’, it indicates that the thread originated FROM port_1 TO port_2
at this site. token is a unique token number associated
with the LUWID. PLAN NAME and AUTHID further Explanation:
identify the thread associated with the UR. If the thread
The TCP/IP DRDA port number specified in the DB2
was created with client End User information, the End
BSDS is different from the value used the last time a
User’s ID, TRANSACTION NAME, and
member of the DB2 data sharing group started. All
WORKSTATION NAME will be displayed. Otherwise,
members of a DB2 data sharing group must use the
these fields will contain an ’*’.
same TCP/IP DRDA port number.
System action:
port_1 The TCP/IP DRDA port number that was number, and DB2 startup continues.
obtained from the DB2 BSDS during DB2
Operator response:
startup.
Contact the system programmer.
port_2 The TCP/IP DRDA port number that was
obtained from the coupling facility during DB2 System programmer response:
startup. This is the TCP/IP DRDA port
number that was used the last time a member If the DB2 resynchronization port number was changed
of the data sharing group was started. inadvertently, stop DB2 immediately. Use the change
log inventory utility (DSNJU003) to correct the
System action: RESPORT value, and restart DB2.
DB2 accepts the new TCP/IP DRDA port number, and If this message reflects a change that you want to make
DB2 startup continues. to DB2’s resynchronization port number, no action is
required. The resynchronization port number stored in
Operator response:
the coupling facility for this member is updated, and
Contact the system programmer. this new port number will be used when DB2 validates
the resynchronization port number for other DB2
System programmer response:
members.
If the TCP/IP DRDA port number was changed
inadvertently, stop DB2 immediately. Use the change
DSNR039I csect-name WARNING - TCP/IP
log inventory utility (DSNJU003) to correct the PORT
RESYNCHRONIZATION PORT
value, and restart DB2.
NUMBER port_1 IS THE SAME AS
If this message reflects a change that you want to make MEMBER member_name
to DB2’s DRDA port number, no action is required. The
Explanation:
DRDA port number stored in the coupling facility is
updated, and this new port number will be used when The TCP/IP resynchronization port of the starting DB2
DB2 validates each member’s DRDA port number. is the same as the member indicated by member_name.
port_1 The TCP/IP resynchronization port number
DSNR038I csect-name WARNING - THE TCP/IP that was obtained from the DB2 BSDS during
RESYNCHRONIZATION PORT DB2 startup.
NUMBER IS CHANGED FROM port_1
member_name
TO port_2
The member name of the DB2 data sharing
Explanation: member that used the same resynchronization
port number.
The TCP/IP resynchronization port number obtained
from the DDF record of the BSDS is different than the System action:
value specified the last time DB2 started.
The TCP/IP port number specified in the BSDS is
Changing the TCP/IP resynchronization port number accepted, and DB2 startup continues.
can cause problems during distributed 2-phase commit
Operator response:
processing. Remote DRDA partners record DB2’s
resynchronization port number in their recovery logs. Contact the system programmer.
The resynchronization port number is used to reconnect
to the appropriate DB2 member when communication System programmer response:
failures occur during 2-phase commit processing. If a Each member of the DB2 data sharing group should
DB2 member changes its resynchronization port have a unique TCP/IP resynchronization port number.
number, the remote DRDA partners may be unable to Use the change log inventory utility (DSNJU003) to
resolve indoubt units of work. specify a unique RESPORT value for this DB2 member
port_1 The TCP/IP resynchronization port number and the DB2 member identified by member_name.
that was obtained from the DB2 BSDS during
DB2 startup. DSNR040I csect-name TRACKER RESTART
port_2 The TCP/IP resynchronization port number ENDLRSN lrsn DOES NOT MATCH
that was obtained from the coupling facility ENDLRSN lrsn ASSOCIATED WITH
during DB2 startup. This is the TCP/IP THE DATA SHARING GROUP
resynchronization port number that was used Explanation:
the last time this member was started.
In a data sharing environment, a TRKRSITE DB2 will
System action: not restart if it detects inconsistencies in the reported
DB2 accepts the new TCP/IP resynchronization port values for ENDLRSN. The ENDLRSN specified on the
Conditional Restart Control Record does not match the
306 Messages
DSNR042I • DSNR044E
ENDLRSN in the system communications area (SCA) This message can occur in the following situations:
structure for the data sharing group. v The DB2 that is starting has completed a fallback
System action: from a later release and does not have the proper
fallback SPE applied.
DB2 startup terminates.
v The DB2 that is starting does not have the proper
Operator response: coexistence SPE to start in a data sharing group,
which is at a later release level.
Collect the SYS1.LOGREC and SVC dump, and contact
the system programmer. v The DB2 that is starting is not at a release level that
supports coexistence with the data sharing group.
System programmer response:
System action:
If the ENDLRSN value for this member is incorrect,
take the following actions: DB2 terminates with reason code 00D900FA.
v Restore the BSDS and Logs for his Tracker DB2 from Operator response:
the primary DB2
Save the console output and inform the system
v Ensure the Conditional Restart Control Record is programmer.
correct
System programmer response:
v Restart DB2
Check the DB2 Program Directory and Preventive
If the ENDLRSN value in the SCA is incorrect, delete
Service Planning updates (PSP) to determine what SPE
the SCA structure and restart all members of the
you need.
TRKRSITE data sharing group with the same
ENDLRSN. Verify that:
v Coexistence is supported between the releases you
DSNR042I csect-name WARNING - UR ROLLBACK are trying to run.
HAS BEEN CANCELED AND IS v The DB2 startup procedure points to the correct set
INCOMPLETE FOR CORRELATION of load libraries.
NAME = corrid CONNECTION ID = v The correct SPE has been applied.
connid AUTHID = authid PLAN NAME =
plan-name URID = urid Problem determination:
The level information is different for each SPE level release level
and each release. This information is for the use of The release and level are different for each
your IBM service representative. release, and are for the use of the IBM service
representative.
This message occurs when a starting DB2 member is at
a later release level that cannot coexist with an existing apar-number
DB2 member. The apar-number is the FALLBACK SPE that
is missing.
System action:
System action:
After detecting the first member with which it cannot
coexist, DB2 terminates with reason code 00D900FA. DB2 terminates with reason code 00D96001.
Operator response: User response:
Save the console output and inform the system Ensure that the FALLBACK SPE is applied, and DB2 is
programmer. started before starting DB2 in a new release.
System programmer response:
DSNR046I csect-name INCOMPLETE UNITS OF
Check the Program Directory and Preventive Service
RECOVERY EXIST FOR subsys
Planning updates (PSP) to ensure that all active
members in the group have the proper SPE applied. Explanation:
Verify that: This message is issued during DB2 shutdown if any
v Coexistence is supported between the releases you incomplete units of recovery exist for the referenced
are trying to run. member of a data sharing group. The message indicates
that retained locks will be held by subsystem subsys.
v The DB2 startup procedure points to the correct set
of load libraries. System action:
v The correct SPE has been applied. DB2 shutdown continues normally.
Problem determination: User response:
Collect the following diagnostic items: Restart DB2 and resolve the incomplete units of
v Console output from the system on which the job recovery to release the retained locks held by
was run, and a listing of the SYSLOG data set for the subsystem subsys.
period of time spanning the failure.
v Dynamic dump, taken to SYS1.DUMPxx data set, by DSNR047I csect-name POSTPONED ABORT
DB2 (04E and 04F abends). BACKOUT PROCESSING LOG
v Contents of the BSDS (both copies if dual BSDS in RECORD AT RBA rba1 TO RBA rba2
use) obtained by using the DB2 print log map
Explanation:
(DSNJU004) utility.
v Unformatted DSN1PRNT output of the This message is produced periodically during the
DSNDB01.DBD01 page set. Use the method backout processing of postponed abort units of
described in Part 5 of Diagnosis Guide and Reference to recovery, initiated by the -RECOVER POSTPONED
locate the inconsistent DBD in the DSNDB01.DBD01 command. The RBAs in this message can be used to
page set. monitor the backout progress.
During the backout process, DB2 reads the log in a
DSNR045I csect-name DB2 SUBSYSTEM IS backward direction and stops reading the log at the
STARTING AND IT WAS NOT RBA matching the URID of the oldest postponed-abort
STARTED IN A PREVIOUS RELEASE UR rba2. rba1 is the RBA of the log record currently
WITH THE FALLBACK SPE APPLIED. being processed.
FALLBACK SPE APAR: apar-number System action:
NEW RELEASE LEVEL: release KNOWN
LEVEL(S): level Backout processing continues.
Explanation: System programmer response:
DB2 was not started with the FALLBACK SPE active This is an information-only message. If the message
before an attempt was made to start DB2 in a new continues to be issued and rba1 remains the same,
release. The FALLBACK SPE must be applied, and the make sure there are no outstanding archive tape
system must be started before DB2 can be started in a mounts that may be delaying the log read process.
new release. Otherwise, obtain a dump of the DB2 address spaces
for problem determination.
308 Messages
DSNR048I • DSNR052I
310 Messages
DSNR058I • DSNR059I
Problem determination:
Collect the following diagnostic items:
Abend X’04E’ with reason code X’00E30010’ is also
produced. However, the error results in a retry. DB2 v Console output from the system on which the job
does not terminate, but a dump is produced. was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
Operator response:
v Dynamic dump, taken to SYS1.DUMPxx data set, by
Notify the system programmer. DB2 (04E and 04F abends).
316 Messages
DSNT105I • DSNT107I
System action:
DSNT105I THE LOADED DSN6SPRM CSECT IS
OBSOLETE. PLEASE REASSEMBLE The message DSNV086E is generated with a reason
THE DSN6SPRM CSECT AND code of X’00E30008’. DB2 is terminated with abend
RELINKEDIT THE DSNZPARM LOAD code X’04F’.
MODULE.
Operator response:
Explanation:
Notify the system programmer.
DSNTSTR2 loaded an out-of-date system parameter
CSECT DSN6SPRM. This error can only occur if code System programmer response:
maintenance has been applied and CSECT DSN6SPRM Reassemble DSN6SYSP, and relink-edit the DSNZPARM
has not been reassembled. This CSECT is contained in load module. This is done by resubmitting the install
the load module specified in the ’PARM=’ parameter of job stream, DSNTIJUZ, that built the load module that
the -START DB2 command. is named following the ’PARM=’ parameter of the
System action: -START DB2 command.
invoked by SMP for the link edits. Correct the Operator response:
procedure or JCL which caused the error and rerun the
Notify the system programmer.
necessary SMP jobs.
System programmer response:
Problem determination:
Appendix A of Installation Guide specifies valid CCSIDs
A DB2 dump was requested to an MVS/XA
for ASCII, EBCDIC, and Unicode. DB2 sets the
SYS1.DUMP data set.
encoding-scheme keyword to ASCII, EBCDIC, or Unicode
The MVS service aid AMBLIST provides linkage editor to identify the source of the error.
module attributes in the summary section of the
If the DSNHDECP value for MIXED is NO, the
LISTLOAD function output.
specified CCSIDs must be SBCS CCSIDs. You can find
these CCSIDs in the table entitled ″Single-byte coded
DSNT108I DB2 HAS DETECTED A DIFFERENCE character set identifiers (CCSIDs)″.
BETWEEN THE RECORDED SYSTEM
If the DSNDECP value for MIXED is YES, then you
CCSIDS AND THE CCSIDS SPECIFIED
must select ASCII MIXED from the table entitled
BY DSNHDECP
″ASCII double-byte coded character set identifiers
Explanation: (CCSIDs)″, and you must select EBCDIC MIXED
CCSIDs from the table entitled ″EBCDIC double-byte
During DB2 startup, DB2 detected a difference between
coded character set identifiers (CCSIDs)″.
the CCSIDs recorded in the BSDS and the CCSIDs
specified by the version of DSNHDECP that was Unicode CCSID values are pre-filled and you should
loaded during startup. DB2 startup terminated to avoid not change them.
potential data corruption issues.
System action: DSNT110I mod-name UNEXPECTED ERROR FROM
IXLMG SERVICE. IXLMG RETURN
DB2 startup is terminated.
CODE = rc. IXLMG REASON CODE =
Operator response: rsncode.
System programmer response: The z/OS IXLMG data collection service issued an
error while collecting DB2 statistics. The rc and rsncode
Determine the reason for the mismatch between the variables indicate the return and reason code. Refer to
CCSIDs in the BSDS and the CCSIDs specified by the ″z/OS MVS Sysplex Services Reference″ for a
DSNHDECP module that was loaded during startup. description of the IXLMG return and reason codes.
Possible reasons for a mismatch include that the
procedure used to start DB2 might have incorrect System action:
library concatenations, or, the copy of DSNHDECP that
DB2 inserts a value of x’FFFFFFFF’ into the
was loaded was incorrectly copied to the libraries
QTGSFLMG field of the DB2 Statistics record.
specified by the DB2 startup procedure.
Correct the mismatch. If IBM support directs you, you
DSNT200I type bind-type FOR PLAN plan-id
can use the change log inventory (DSNJU003) utility
SUCCESSFUL
with the DELETE CCSIDS clause to delete the CCSIDs
that are specified in the in the BSDS. Important: Do not Explanation:
attempt to delete the CCSIDs in the BSDS unless IBM
A BIND, REBIND or FREE PLAN subcommand has
support instructs you.
completed successfully.
type Indicates that a test bind was in progress. A
DSNT109I DB2 HAS DETECTED AN INVALID
test bind means that no plan name was
CCSID IN THE CCSID(S) SPECIFIED
specified. The token is omitted if a normal
FOR ENCODING SCHEME
BIND PLAN was processed.
encoding-scheme BY DSNHDECP
bind-type
Explanation:
Type of bind subcommand: BIND, REBIND, or
The version of DSNHDECP that was loaded during FREE.
DB2 startup has invalid CCSIDs for the encoding-scheme
plan-id Name of application plan specified in the
encoding scheme. DB2 startup terminated to avoid
subcommand.
potential data corruption issues.
System action:
System action:
The plan was successfully bound, rebound, or freed.
DB2 startup is terminated.
318 Messages
DSNT201I • DSNT208I
name-type
DSNT201I type bind-type FOR PLAN plan-id NOT
Indicates the type of list in which the name
SUCCESSFUL
was duplicated.
Explanation: v MEMBER NAME - List of DBRM Members
Errors have been detected during the processing of the v PLAN-ID - List of plan IDs
indicated BIND, REBIND, or FREE PLAN v SYSTEM NAME - List of system connection
subcommand. names on a DISABLE or ENABLE list.
type Indicates that a test bind was in progress. A v PACKAGE NAME - List of package IDs
test bind means that no plan name was
System action:
specified. The token is omitted if a normal
BIND PLAN was processed. Duplicates are removed from ’name-type’ list and the
bind process continues.
bind-type
Type of bind subcommand: BIND, REBIND, or System programmer response:
FREE.
Verify the list that contains the duplicate. If the error is
plan-id Name of application plan specified in the only in entering a name incorrectly, which happens to
subcommand. duplicate another entry, enter the name correctly and
reissue the bind statement. If the entry is really a
System action:
duplicate, no action is required.
The BIND, REBIND, or FREE PLAN was not
performed.
DSNT207I PROGRAM program-name WITH MARK
System programmer response: release-dependency-mark FAILED
BECAUSE IT DEPENDS ON
See other messages issued to determine the error that
FUNCTIONS OF THE RELEASE FROM
caused the bind subcommand to terminate
WHICH FALL BACK HAS OCCURRED
unsuccessfully.
Explanation:
DSNT202I MESSAGE LIMIT EXCEEDED Program ’program-name’ depends on a function of DB2
that is not supported by the current active release.
Explanation:
program-name
A fixed amount of space exists in which to generate
Name of the application program.
bind subcommand messages. This message says that
the bind subcommand generated more messages than release-dependency-mark
will fit in that space. A one-character mark showing the oldest DB2
release supporting this program.
System action:
System action:
For bind subcommands that affect a single plan, the
bind subcommand process continues. However, no The bind operation for this plan or package is not
other messages are generated except for message performed.
DSNT200I or DSNT201I. For bind subcommands that
System programmer response:
affect more than one plan, the bind subcommand
process terminates and no other messages are Warn users not to use plans or packages containing this
generated. program until the DB2 subsystem has been remigrated
to the newer release.
System programmer response:
User response:
The ’FLAG’ parameter of the bind subcommand can be
used to limit the types of messages that are generated. The program cannot be used until the DB2 subsystem
is remigrated to the newer release. Notify the system
programmer.
DSNT205I name IS A DUPLICATE name-type, IT
WILL BE USED ONLY ONCE
DSNT208I PROGRAM program-name
Explanation:
PRECOMPILED WITH INCORRECT
Name ’name’ has been specified more than once in a LEVEL FOR THIS RELEASE
list of names.
Explanation:
name Name that was specified more than once.
Program ’program-name’ was precompiled under a
release not supported by the current level of DB2, or
320 Messages
DSNT212I • DSNT216I
dbrm-name
DSNT212I bind-type AUTHORIZATION ID auth-id
Name of the DBRM associated with the error.
IN THE OWNER KEYWORD IS
INVALID dbrm-pds-name
Partitioned data set associated with the error.
Explanation:
System action:
The authorization ID specified in the OWNER keyword
of the BIND or REBIND subcommand is invalid. To No application plan is created.
specify an OWNER that is not the primary
authorization ID, or one of the secondary IDs of the System programmer response:
process requires additional authority.See Command Determine if an incorrect dbrm-pds-name was specified
Reference for the authority required. in the LIBRARY parameter of the BIND subcommand,
bind-type or an incorrect data set name was specified for the
Type of bind subcommand: BIND or REBIND DBRMLIB DD statement. Check correctly specified data
sets for I/O errors or modified DCB attributes.
| auth-id The authorization ID specified as owner.
| Attention: If you are using a trusted context,
| the token auth-id might return a role instead of | DSNT215I csect-name bind-type bind-subtype FOR
| an authorization ID. A role is returned, if a | PACKAGE = package-name FAILED
| role was in effect and the authorization | BECAUSE AT LEAST ONE BIND
| checking is performed against the role rather | OPTION IS NOT ALLOWED FOR A
| than the authorization ID of the session, when | package-type PACKAGE
| the condition was encountered. The role is | Explanation:
| returned in the following format as a single
| token: ROLE: role-name. | The BIND or REBIND subcommand has been
| submitted with an invalid combination of bind options.
System action: | The message tokens provides the following
The BIND or REBIND subcommand is not executed. | information:
Explanation: | package-type
| Type of package: PROCEDURE.
An invalid DCB block size is specified for the DBRM
library of the BIND subcommand. | System action:
Correct the DCB block size of the DBRM library, and | User response:
reissue the BIND subcommand. | Refer to Command Reference for valid combinations of
| bind options and reissue the BIND or REBIND
DSNT214I I/O ERROR ON DBRM LIBRARY | subcommand with a valid combination.
DBRM MEMBER= dbrm-name DBRM
LIBRARY= dbrm-pds-name xxxxxx DSNT216I REBIND FOR PACKAGE = package_name
Explanation: FAILED BECAUSE AT LEAST ONE
BIND OPTION SPECIFIED CANNOT
An I/O error was encountered attempting to read BE CHANGED IN CONJUNCTION
database request module (DBRM) during a BIND WITH PLANMGMT.
subcommand. ’xxxxxx’ is a portion of the message text
generated by the SYNADAF macro instruction to Explanation:
describe the permanent I/O error This text may contain When attempting to REBIND a package using the
information such as jobname, stepname, unit address, PLANMGMT bind option, at least one of the following
device type, ddname, operation attempted, and error bind options was given a value that’s different from it’s
description. previous value:
| When a REBIND PACKAGE command is invoked on Check the SYSPLAN catalog table for the correct
’plan-id’ to use.
322 Messages
DSNT222I • DSNT224I
| Explanation: | object-name
| If object-type is PLAN, object-name is the name
| The OPTHINT option of Bind or Rebind was specified. | of the plan.
| This message gives counts of the number of statements
| where a hint was fully applied, not fully applied, or | If object-type is PACKAGE, object-name is the
| not found. | name of the package in the format
| ’location-id.collection-id.package-id’.
| csect-name
| The name of the csect from which the message | System action:
| was issued. | Processing continues normally using the default
| bind-type | OPTHINT value.
| Type of BIND subcommand: BIND or | System programmer response:
| REBIND.
| Enable the use of OPTHINT by changing the value of
| object-type | OPTIMIZATION HINTS on the DB2 Installation panel,
| PLAN or PACKAGE | DSNTIP8.
| object-name | If, after further consideration, you do not want to use
| If object-type is PLAN, object-name is the name | OPTHINT, remove OPTHINT from the bind-type
| of the plan. | subcommand or set the value to all blanks.
| If object-type is PACKAGE, object-name is the
| name of the package in the format DSNT224I csect-name bind-type ERROR FOR
| ’location-id.collection-id.package-id’. object-type object-name CCSID = ccsid IS
| count 1 The number of statements where hints were INVALID FOR ENCODING SCHEME =
| found, and all hints found were successfully scheme
| applied. Explanation:
| count 2 The number of statements where hints were The system does not have a valid CCSID defined for
| found and at least one of those hints could not the specified encoding scheme, or the specified CCSID
| be successfully applied. is not defined on the system.
| count 3 The number of statements where there were bind-type
| no matching optimization hints found. Type of bind subcommand: BIND or REBIND.
| System action: object-type
| Processing continues normally. PLAN or PACKAGE.
ccsid The numeric CCSID corresponding to the | the bind-option that is not recommended, then DB2
specified ccsid-type. | will issue a warning during the bind-type operation on
| object-type. To avoid this warning, rerun the bind-type
System action:
| operation on object-type specifying
The bind-type operation is not performed | DBPROTOCOL(DRDA) or allow the bind-type
| operation to default.
System programmer response:
If the bind option ENCODING was not specified, and DSNT228I BIND ERROR, ATTEMPTING TO
instead the value for ENCODING was defaulted from REPLACE PACKAGE = package_name
the system default Application Encoding Scheme, verify WITH VERSION = (version2) BUT THIS
the Application Encoding Scheme is set to a defined VERSION ALREADY EXISTS
CCSID.
Explanation:
If the value specified for the ENCODING option was
ASCII, EBCDIC or UNICODE, verify the corresponding An attempt is made to create a version of a package
CODED CHAR SET subsystem parameter on the that already exists. The version specified in the
installation panel DSNTIPF has been set to a defined REPLVER keyword is different from the version
CCSID. Otherwise, inform the user of the correct specified for the precompile. The version specified for
CCSID. the precompile already exists in the catalog. The
combination of ’location.collection.package.version’
Refer to the section entitled ″Character conversion″ of must be unique in the SYSIBM.SYSPACKAGE catalog
Installation Guide for more information regarding table. A common mistake is that the user may believe
CCSIDs and character sets. that the version he is creating is the one specified in the
User response: REPLVER keyword. This is not the case. The version
specified in the REPLVER keyword is the name of the
Verify that the correct encoding scheme was specified version being replaced. The version that will be created
in the ENCODING bind option on the bind-type is the version that was given to the program when it
subcommand. If correct, see System Programmer was precompiled.
Response and contact the System Programmer. If
incorrect, specify the correct scheme in the ENCODING package_name
option and reissue the bind-type subcommand. Fully qualified package name
Severity: version2
Version-id of package that is to be created
8 (error)
System action:
324 Messages
DSNT230I • DSNT233I
The authorization ID given does not have the privilege System action:
indicated and cannot invoke the bind subcommand on
The indicated package is not bound, rebound, or freed.
the named package.
System programmer response:
bind-type
Type of bind subcommand: BIND, REBIND, or You must grant the indicated privilege to the
FREE authorization ID of the package owner.
auth-id Authorization ID of the invoker of the BIND
subcommand. Attention: If you are using a DSNT236I REBIND FOR PACKAGE package-name
trusted context, the token auth-id might return FAILED BECAUSE IBMREQD OF
a role instead of an authorization ID. A role is ibmreqd IS INVALID
returned, if a role was in effect and the
Explanation:
authorization checking is performed against
the role rather than the authorization ID of the The IBMREQD column of the SYSIBM.SYSPACKAGE
session, when the condition was encountered. catalog table for the named package contains an
The role is returned in the following format as unrecognizable character. This usually means that the
a single token: ROLE: role-name. package depends on a function of DB2 which is not
supported by the currently active release.
package-name
Name of the package in the following format: package-name
’location.collection.package.(version)’ Name of the package in the following format:
’location.collection.package.(version)’
privilege
Name of the privilege not held: System action:
326 Messages
DSNT237I • DSNT240I
The package was not rebound. If BIND or REBIND PLAN is specified, the
package-name refers to a package on the
System programmer response:
PKLIST for the plan.
Warn users not to use the package until the DB2
error-type
subsystem is remigrated to the newer release.
Type of error: WARNING or ERROR.
auth-id Authorization ID of the invoker of the BIND
DSNT237I csect-name BIND sub-type ERROR USING
subcommand.
auth-id AUTHORITY PACKAGE =
package-name ALREADY EXISTS package-name
Name of the package in the following format
Explanation:
’location.collection.package.(version)’.
An attempt is made to add a package that already
System action:
exists. The combination of
’location.collection.package.version’ must be unique in Package not rebound or freed.
the SYSIBM.SYSPACKAGE table. In addition, the
System programmer response:
combination of ’location.collection.package.consistency-
token’ must be unique. Check the SYSPACKAGE catalog table for the correct
’location.collection.package.version’ to use.
sub-type
The sub-type can have the values: COPY, ADD
or REPLACE. DSNT239I PLAN plan-id CONTAINS NO DBRMS
AND NO PACKAGES
auth-id Authorization ID of the owner of the package.
Attention: If you are using a trusted context, Explanation:
the token auth-id might return a role instead of
an authorization ID. A role is returned, if a A plan with no DBRMs was rebound with the
role was in effect and the authorization NOPKLIST option specified. This creates an empty
checking is performed against the role rather plan. No SQL can be executed. The individual variable
than the authorization ID of the session, when fields contain:
the condition was encountered. The role is plan-id Plan name specified on the REBIND
returned in the following format as a single command.
token: ROLE: role-name.
System action:
package-name
Name of the package in the following format: This is a warning message. The REBIND process will
’location.collection.package.(version)’ continue.
328 Messages
DSNT245I • DSNT248I
package-name
CLUSTERED = clustered Name of the package in the following format:
CLUSTERRATIO = clusterratio ’location.collection.package.(version)’
CLUSTERRATIOF = clusterratio release-dependency-mark
FIRSTKEYCARD = firstkeycard A one-character mark showing the oldest
FIRSTKEYCARDF = firstkeycard release of the DB2 which can support this
NLEAF = nleaf package. The release dependency mark for the
NLEVELS = nlevels package is kept in the IBMREQD column in
SPACEF = space the DB2 catalog in SYSIBM.SYSPACKAGE.
DATAREPREATFACTORF =datarepeatfactor
System action:
Programmer response: The package cannot be bound until the DB2 subsystem
is remigrated to the newer release.
Check Command Reference for the correct syntax.
object-type Explanation:
PLAN or PACKAGE
A ’location-id’ was specified on the PKLIST or
object-name CURRENTSERVER keyword on a bind subcommand.
If object-type is PLAN, object-name is the name That location is not defined in the
of the application. Otherwise, it is the name of SYSIBM.LOCATIONS table.
the PACKAGE in ’location.collection.package’
bind-type
format.
Type of bind subcommand: BIND or REBIND
scheme This field displays the encoding scheme
plan-name
specified in the ENCODING bind option on
Name of the plan
the bind-type subcommand or defaulted from
the system default Application Encoding keyword
Scheme. If scheme is UNKNOWN, then the The bind subcommand containing the
CCSID value has not been defined in the nonexistent location: PKLIST or
ENCODING bind option or by the system CURRENTSERVER
default Application Encoding Scheme, and
location-id
therefore the encoding scheme is not known.
The nonexistent location
ccsid This field displays the numeric CCSID
System action:
specified in the ENCODING bind option or
the numeric CCSID corresponding to the The bind process will continue.
scheme specified in the ENCODING bind
option. Otherwise, ccsid displays the numeric System programmer response:
CCSID corresponding to the specified Define the appropriate ’location-ids’ in the
ccsid-type. SYSIBM.LOCATION catalog table prior to executing the
System action: plan.
Verify that the correct encoding scheme was specified System programmer response:
in the ENCODING bind option on the bind-type Determine why the BIND subcommand was unable to
subcommand. If correct, see System Programmer open the DBRM library, and correct the problem.
Response and contact the system programmer. If
incorrect, specify the correct scheme in the ENCODING User response:
option and reissue the bind-type subcommand. Contact the system programmer, providing all material
Severity: associated with the error.
330 Messages
DSNT251I • DSNT254I
Explanation:
DSNT253I csect-name bind-type OPTIONS FOR
The BIND subcommand received an I/O error while PLAN plan-name
attempting to locate the specified DBRM library
member(s). (DEFER | NODEFER) PREPARE
authorization-id CACHESIZE bind-option1
Authorization ID of the invoker of the BIND QUALIFIER bind-option2
subcommand. CURRENTSERVER bind-option3
CURRENTDATA bind-option4
object-type
DEGREE bind-option5
PLAN | PACKAGE
SQLRULES bind-option6
object-name DISCONNECT bind-option7
If object-type is PLAN, object-name is the REOPT bind-option8
name of the application plan. Otherwise, it is KEEPDYNAMIC bind-option9
the name of the package in
IMMEDWRITE bind-option10
’location.collection.package’ format.
DBPROTOCOL bind-option11
System programmer response: OPTHINT bind-option12
Correct the reason for the I/O error, and reissue the ENCODING bind-option13(bind-option14)
BIND subcommand. PATH bind-option15
Problem determination:
Explanation:
Collect the following diagnostic items:
This message shows the BIND or REBIND options that
v Console output from the system on which the job
were used for the plan specified by plan-name during
was run, and a listing of the SYSLOG data set for the
bind or rebind processing.
period of time spanning the failure.
v Dynamic dump, taken to SYS1.DUMPxx data set, by Severity:
DB2 (04E and 04F abends). 0 (informational)
v Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
DSNT254I csect-name bind-type OPTIONS FOR
v SYSPRINT output, including JCL, for the application
program or batch job, and system messages that PACKAGE =package-name
were issued. Make sure that MSGLEVEL=(1,1) on the ACTION (ADD | REP)
JOB statement so that all diagnostic information is OWNER owner
sent to SYSPRINT. QUALIFIER qualifier
. VALIDATE (BIND | RUN)
EXPLAIN (NO | YES)
ISOLATION (RR | CS | RS | UP | blank) collection-id specified with the COPY keyword. You
RELEASE (COMMIT | DEALLOCATE | blank) cannot create a package that is the same name as the
package being copied.
COPY package-name
package-name
Name of the package
Explanation:
(location.collection.package.(version))
This message shows the BIND or REBIND options that
System action:
were used for the local package specified by
package-name during bind or rebind processing. The package is not bound.
Severity: System programmer response:
0 (informational) Choose a different collection id for the package you are
creating and resubmit the subcommand.
DSNT255I csect-name bind-type OPTIONS FOR
DSNT258I bind-type WARNING FOR PLAN
plan-name THE LOCATION-ID location-id
SQLERROR bind-option1 SPECIFIED IN CURRENTSERVER MAY
CURRENTDATA bind-option2 NEED A PACKAGE LIST
DEGREE bind-option3
DYNAMICRULES bind-option4 Explanation:
(DEFER | NODEFER) If binding a PLAN with a nonlocal location specified in
PREPARE the CURRENTSERVER, a package list is required using
REOPT bind-option5 the PKLIST keyword to access any packages at the
KEEPDYNAMIC bind-option6 location specified.
IMMEDWRITE bind-option7
DBPROTOCOL bind-option8 bind-type
OPTHINT bind-option9 Type of bind subcommand: BIND or REBIND
ENCODING bind-option10(bind-option11) plan-name
PATH bind-option12 Name of plan
location-id
Explanation: Location of CURRENTSERVER
This message shows the BIND or REBIND options that System action:
were used for the local package specified by
package-name during bind or rebind processing. The bind process will continue.
Severity: System programmer response:
0 (informational) Add a package list with package(s) that reference the
location specified in the CURRENTSERVER or delete
the CURRENTSERVER from the BIND or REBIND
DSNT256I DBRM MEMBER member-name IS subcommand.
EMPTY, A PACKAGE CANNOT BE
BOUND
DSNT259I bind-type WARNING FOR PLAN
Explanation: plan-name NO PACKAGES IN THE
The named DBRM member is empty, a package cannot PACKAGE LIST REFERENCE THE
be created. LOCATION-ID location-id SPECIFIED IN
CURRENTSERVER
System action:
Explanation:
No package is created.
There are no packages in the package list that reference
the location specified in the CURRENTSERVER
DSNT257I BIND ERROR, PACKAGE package-name keyword.
CANNOT BE CREATED BECAUSE IT
HAS THE SAME NAME AS THE bind-type
PACKAGE BEING COPIED Type of bind subcommand: BIND or REBIND
Explanation: plan-name
Name of plan
The location and collection-id of the package being
created are the same as the local location and the location-id
Location of CURRENTSERVER
332 Messages
DSNT260I • DSNT262I
release-dependency-mark
| bind-subtype
A one-character mark indicating the oldest
| Subtype of bind subcommand: TRIGGER or
DB2 release that can support the bind
| DEPLOY
subcommand. | auth-id Authorization ID attempting the prohibited
| action
This message can be issued in one of the following
situations:
| package-name
| Name of the package in the following format:
v When the DSN command explicitly or implicitly uses
the name of a DB2 subsystem that does not support
| 'collection.package'
a bind option or feature used in the DSN bind | package-type
subcommand bind-type. | Type of package: TRIGGER, NATIVE SQL PL
v When the DSN command uses a group attachment | PROCEDURE.
name for a DB2 data sharing group and the receiving | System action:
DB2 data sharing member does not support a bind
option or feature used in the DSN bind subcommand | The package is not copied, rebound, or freed.
bind-type.
| System programmer response:
v When attempting to use new function before new
function mode has been enabled. | Check the SYSIBM.SYSPACKAGE catalog table for
| names of existing trigger packages or native SQL PL
System action: | procedure packages. Call the bind subcommand again,
The bind-type operation is not performed. | with a ’collection.package’ that is not a trigger or native
| SQL PL procedure package.
System programmer response:
See the ’User Response’ section of this message. | DSNT265I csect-name bind-type bind-subtype ERROR
User response:
| USING auth-id AUTHORITY PACKAGE
| package-name IS NOT A package-type
In the DSN command, specify the name of a DB2 | PACKAGE
subsystem having release dependency mark
release-dependency-mark or higher that supports all of the
| Explanation:
bind options or features used in the bind-type | The subcommand REBIND TRIGGER PACKAGE can
subcommand. | be used only for trigger packages. The subcommand
For a list of the DB2 release dependency marks and
| BIND PACKAGE DEPLOY can be used only for native
334 Messages
DSNT266I • DSNT268I
| SQL PL procedure packages. The subcommand FREE If object-type is PACKAGE, object-name is the
| PACKAGE can be used only for non-trigger and name of the package in the format
| non-native SQL PL procedure packages. ’location-id.collection-id.package-id.(version-
id)’.
| The message tokens are as follows:
schema-name
| bind-type The schema name specified in the bind option
| Type of bind subcommand: REBIND, FREE
PATH causing the SQL Path to exceed 254
| bind-subtype characters.
| Subtype of bind subcommand: TRIGGER,
System action:
| DEPLOY
The bind-type operation is not performed.
| auth-id Authorization ID attempting the prohibited
| action System programmer response:
| package-name See the ’User Response’ section of this message.
| Name of the package in the following format:
User response:
| 'collection.package'
In the bind option PATH, specify a schema name list
| package-type that does not cause the SQL Path to exceed 254
| Type of package: TRIGGER, NATIVE SQL PL characters.
| PROCEDURE
For more information about the bind option PATH and
| System action: the schema name list, please see: Command Reference.
| The package specified is not rebound, deployed, or
| freed. DSNT267I csect-name A TRIGGER PACKAGE
| System programmer response: CANNOT BE FREED USING THE FREE
PACKAGE COMMAND
| For a package that is not a trigger package, rebind
| using the subcommand REBIND PACKAGE. Re-invoke Explanation:
| the bind subcommand with a ’collection.package’ that A FREE PACKAGE command was received that
| is an accepted package. identified the trigger package to be freed. Trigger
packages can only be deleted using the DROP
DSNT266I csect-name bind-type FOR object-type = TRIGGER SQL statement.
object-name FAILED. THE TOTAL System action:
LENGTH OF THE PATH SCHEMA
NAME LIST EXCEEDS 254 The TSO Attachment Facility is ready for more input.
CHARACTERS WITH SCHEMA NAME User response:
schema-name
Use the SQL statement DROP TRIGGER to delete the
Explanation: trigger package.
DB2 uses the schema name list you specified in the
bind option PATH to set the DB2 SQL Path that will be DSNT268I csect-name A BIND COMMAND USING
used for the bind process. The SQL Path is a THE COPY OPTION NAMED A
VARCHAR(254) string containing the list of schema TRIGGER PACKAGE AS THE SOURCE
names you specified, where each schema name is FOR THE BIND
delimited with double quotes and separated from the
next schema name by a comma. The total length of this Explanation:
SQL Path string, including the delimiters and commas,
A trigger package cannot be used as the source for a
cannot exceed 254 characters. The indicated schema
BIND COPY command.
name schema-name in the bind option PATH causes the
SQL Path string to exceed 254 characters. System action:
bind-type The TSO Attachment Facility is ready for more input.
Type of bind subcommand: BIND or REBIND
User response:
object-type
Correct the BIND command and resubmit.
PLAN or PACKAGE
object-name
If object-type is PLAN, object-name is the name
of the plan.
v SQLERRMT = tokens
DSNT270I THE FOLLOWING SQLCA
INFORMATION WAS RETURNED v SQLWARN warn_fields
FROM subsystem v STATEMENT = stmt_num
v SQLCODE = sqlcode Explanation:
v SQLSTATE = sqlstate
A warning or error has been received from a database
v SQLERRMT = tokens server using Distributed Relational Database
v SQLWARN warn_fields Architecture (DRDA) during remote program BIND
processing. The tokens of the message are:
Explanation:
1. subsystem - database server,
A warning or error has been received from a database
2. sqlcode - SQL return code,
server using Distributed Relational Database
Architecture (DRDA) during remote program BIND 3. sqlstate - additional set of return codes common to
processing. The tokens of the message are: the four relational products,
1. subsystem - the database server, 4. tokens - specific tokens passed in the message
portion of the SQLCA for problem determination,
2. sqlcode - SQL return code,
5. warn_fields - the warning information indicators,
3. sqlstate - additional set of return codes common to
and
the four relational products,
6. stmt_num - the statement number of the failing
4. tokens - specific tokens passed in the message
statement.
portion of the SQLCA for problem determination,
and System action:
5. warn_fields - the warning information indicators. See the System Action associated with the indicated
System action: SQLCODE.
See the System Action associated with the indicated System programmer response:
SQL return code. Take note of the warning or error (as indicated in the
System programmer response: SQLCODE, SQLSTATE, or one or more of the
SQLWARN fields), and determine if a program change
See the Programmer Response associated with the is necessary. SQLWARNx fields are described in
indicated SQLCODE and/or SQLSTATE. Take note of Appendix D of SQL Reference. A change to the
the warning or error (as indicated in the SQLCODE, application may be necessary or the system
SQLSTATE, or one or more of the SQLWARN fields), programmer may have to be consulted depending on
and determine if a program change is necessary. the situation.
SQLWARNx fields are described in Appendix D of SQL
Reference.. A change to the application might be If you suspect an error in DB2, refer to Part 2 of
necessary or the system programmer might have to be Diagnosis Guide and Reference for information on
consulted depending on the situation. identifying and reporting the problem.
336 Messages
DSNT301I • DSNT305I
-DISPLAY. The name of the database is ’dbname’. status in this database. INSTALL SYSOPR can use the
START DATABASE command only to recover LPL
| If the operation involves an implicit database or an
pages or GRECP objects. The name of the database is
| object in an implicit database, then the applicable
dbname.
| privilege is not held on the implicit database, on
| database DSNDB04. In this case, the owner of the System action:
| object is not involved in performing the operation.
The request is rejected.
System action:
Operator response:
The request is rejected.
Reissue the -START DATABASE command using the
System programmer response: correct access mode or contact your system
programmer.
The privilege to issue the command must be granted to
the indicated ’authorization-id’.
DSNT305I SUBSYSTEM FAILURE DURING
User response:
command-name DATABASE COMMAND
Notify the system programmer. PROCESSING. RC = yy, REASON = zz
338 Messages
DSNT310I • DSNT314I
v The ’state’ is either: v A list of table space and/or index space names
appears after the keyword SPACENAM in a START
– START RW if the specified table space is currently DATABASE command.
started read/write
– START RO if the specified table space is currently Operator response:
started read only Specify the command correctly.
– START UT if the specified table space is currently
started for utility processing
DSNT314I csect_name INVALID PARTITION
– STOPPED if the specified table space is currently SPECIFICATION FOR OBJECT
stopped, has a stop pending against it, or is object-name
stopping.
Explanation:
If there are pages in the logical page list (LPL) for the The PART keyword is invalidly specified in a START
object, or if the object is in group buffer pool recovery DATABASE, STOP DATABASE, or DISPLAY
pending (GRECP) status, a START DATABASE DATABASE command.
ACCESS(RO) or START DATABASE ACCESS(RW)
command triggers a recovery of that object even if this The PART keyword is invalid if it is specified for:
message is issued for that object. For each object that v A nonpartitioned table space
has LPL or GRECP recovery that is initiated, DB2 issues v A nonpartitioned type 1 index
a DSNI006 message followed by either a DSNI021
v A type 2 index not defined on a partitioned table
message (when the recovery completes successfully) or
space
a DSNI005 message (when the recovery is
unsuccessful).
The object object-name can be either a table space or an
User response: index space.
No response is necessary. This message is informational
only. No action for this table space or index space is
performed by the START DATABASE, STOP
DATABASE or DISPLAY DATABASE command.Any
DSNT311I MESSAGE LIMIT EXCEEDED. other valid table space or index space specified is
DISPLAY IS TERMINATED. processed by the command.
Explanation: System action:
The number of messages generated exceeds the The desired command is not processed for the table
maximum number of messages specified in the LIMIT space or index space in question. All other valid table
keyword or exceeds the system default.
spaces or index spaces specified in the command are The START DATABASE command was specified for a
processed. logical partition of a nonpartitioned index which has
pages in the logical page list (LPL) or is marked group
User response:
buffer pool recovery pending (GRECP). To start a
Resubmit the command for the nonpartitioned table nonpartitioned index with one of these exception
space or index space without using the PART keyword. conditions, the START DB command must be specified
without the PART keyword.
Problem determination:
System action:
SYSIBM.SYSTABLESPACE in the DB2 catalog indicates
whether a table space is partitioned. The command is not processed for the index space. All
SYSIBM.SYSINDEXSPACE in the DB2 catalog indicates other valid table spaces or index spaces specified in the
whether an index space is partitioned and whether the command are processed.
index space is a type 1 or a type 2 index. Type 2
User response:
nonpartitioned indexes can be started, stopped, or
displayedat the logical partition level; type 1 cannot. Submit the command for the nonpartitioned index
space without using the PART keyword.
Severity:
Problem determination:
8 (error)
If more information on the status of the index space is
required, use the -DISPLAY DATABASE command.
DSNT315I csect_name INVALID PARTITION
NUMBER OR RANGE SPECIFIED - Severity:
part-numFOR OBJECT object-name
8 (error)
Explanation:
An invalid partition number or rangewas specified in DSNT317I csect-name ANY USER-DEFINED
the PART keyword for a START DATABASE, STOP INDEXES ON DSNDB06 COULD NOT
DATABASE or DISPLAY DATABASE command. BE cmd-type DUE TO A RESOURCE
UNAVAILABLE ON THE CATALOG
Partition number or range part-numis invalid for the
OR DIRECTORY.
object object-name.
Explanation:
System action:
If user-defined indexes exist on DSNDB06, they could
The part number or rangeis ignored. All other valid
not be displayed, started or stopped (depending on
partitions specified are processed if PART was specified
cmd-type) because the catalog or directory was not
as list.
available. DB2-defined indexes and table spaces are not
User response: affected by this unavailability.
340 Messages
DSNT331I • DSNT350I
342 Messages
DSNT362I • DSNT365I
GLOBAL
DSNT363I PHYSICAL ERROR PAGE RANGE FOR
All requested database information is listed.
DATA SET data-set-name LOW=lowphy,
This title is produced if ACTIVE, DISABLED,
HIGH=hiphy
and RESTRICT are omitted.
Explanation:
LOCKS
The connection identifiers and correlation This message is the response to a -DISPLAY
identifiers of all applications holding, DATABASE command when the SPACENAM keyword
retaining, or waiting for locks on the specified is specified in order to notify the user of any physical
table spaces or index spaces are displayed. I/O errors encountered on a data set.
RESTRICT In the message, ’data-set-name’ is the name of the data
All databases with restricted usage (that is, set with errors. The variables ’lowphy’ and ’hiphy’
RO, started UT) are listed. identify the range of physical pages, within the data
set, that were being read when the I/O errors occurred.
USE The connection identifiers and correlation
Physical page numbers are assigned in relationship to
identifiers of all allocated applications are
the beginning of the data set in which the pages reside.
listed.
This message is always preceded by messages
CLAIMERS
DSNT360I and DSNT361I, which identify the name of
The connection identifiers and correlation
the database and page set that the specified data set
identifiers of all applications holding claims on
supports.
the specified database are displayed.
Page sets (table spaces or index spaces) are made up of
LPL The page number ranges of the pages that are
supporting data sets. Physical pages are pages in
included in the logical page list for the table
supporting data sets that are numbered from the
space or index space.
beginning of the particular data set in which they
OVERVIEW reside. This message refers to physical pages in a data
All table spaces and index spaces that are set that support (are part of) some page set.
contained within the databased that are
System action:
specified.
See the Explanation section for this message.
DSNT362I DATABASE = data-base-name STATUS =
status DBD LENGTH = dbd-length DSNT364I csect-name KEYWORD ONLY IS USED
INCORRECTLY
Explanation:
Explanation:
This message signals the beginning of display
information from the DISPLAY DATABASE command. Keyword ONLY is used incorrectly in the DISPLAY
It lists the name, status, and DBD length of the DATABASE command. When the SPACENAM
database. All table space and index space names listed keyword is specified, keyword ONLY is valid only if
in the following DSNT392I, DSNT394I, or DSNT396I one of the following keywords is also used:
messages are contained within this database. v LOCKS
data-base-name v LPL
The database name. v CLAIMERS
status A combination of one or more of the following v WEPR
strings delimited by a comma. The maximum v USE
length of the string is 18 characters.
System action:
RO The database is started for read
activity only. The DISPLAY DATABASE command is not processed.
is entered and no databases were found to satisfy the command until only one of these mutually exclusive
request. keywords is specified.
System action:
DSNT375I PLAN=plan-id1 WITH
The process continues normally.
CORRELATION-ID=id1
CONNECTION-ID=id2 LUW-ID=id3
DSNT366I DATABASE name NOT type THREAD-INFO=id4 IS DEADLOCKED
WITH PLAN=plan-id2 WITH
Explanation: CORRELATION-ID=id5
A database listed in the DISPLAY DB(...) is not of the CONNECTION-ID=id6 LUW-ID=id7
correct type. The variables are as follows: THREAD-INFO= id8 ON MEMBER id9
type The type of request specified: ACTIVE, This message is issued whenever plan plan-id1 with
RESTRICTED, ACTIVE OR RESTRICTED correlation id1, connection id2, and LUW id3 is denied
an IRLM lock because of a detected deadlock. Plan
Note that either DSNT301I or DSNT302I is produced if plan-id2 identifies one of the members of the deadlock.
no object is found and the keywords ACTIVE and DB2 does not attempt to identify all survivors of a
RESTRICT are omitted. deadlock or all participants in a deadlock in the
System action: DSNT375I message. Plan plan-id2 in message DSNT375I
might be just one of several plans holding locks on the
Processing continues normally. desired resource.
If multiple deadlocks are detected during the same
DSNT367I NO INFORMATION AVAILABLE deadlock-detection interval, the lock holder identified
Explanation: by plan-id2 in one DSNT375I message might be selected
to break a deadlock identified by a different DSNT375I
This message indicated there is no LOCK, USE, LPL, message. The lock holder identified by plan-id2 is not
WEPR or CLAIMER information available when guaranteed to be a winner in all deadlocks in which it
DISPLAY DB(...) SPACENAM(...) ONLY is entered with participates.
the keywords LOCKS, USE, LPL, WEPR or CLAIMERS.
A DB2 IFCID 172 trace record contains the information
System action: needed to determine all participants in, and survivors
of, a given deadlock.
The process continues normally.
plan-id1, plan-id2
The names of the executing plans.
DSNT368I csect-name MORE THAN ONE
MUTUALLY EXCLUSIVE KEYWORD id1 The correlation identifier of the thread
WAS SPECIFIED IN THE DISPLAY associated with plan-id1. Correlation IDs
DATABASE COMMAND. beginning with ’0nn’, where ’nn’ is a number
from 01 to 28, identify a system agent.
Explanation:
id2 The connection identifier of the thread
The keywords, LOCKS, LPL, CLAIMERS, WEPR and
associated with plan-id1.
USE are mutually exclusive. Only one should be
specified in a DISPLAY DATABASE command. The id3 The logical-unit-of-work identifier of the
precedence order for which keyword takes precedence thread associated with plan-id1. An asterisk (*)
over the others is: indicates that the thread does not have an
1. LPL LUW-ID. If the LUW-ID is not an asterisk, the
value is a logical-unit-of-work identifier that is
2. CLAIMERS
assigned to the thread. It is followed by an
3. LOCKS equal (=) sign and a token value, which can be
4. USE used in place of the logical-unit-of-work
5. WEPR identifier in any DB2 command that accepts a
logical-unit-of-work identifier as input.
System action:
id4 This ID contains additional identifiers that
The DISPLAY DATABASE command is processed with define more specific information regarding the
this warning message. identity of the agent.
User response: In many distributed configurations, the
Remove keywords from DISPLAY DATABASE primary authorization-ID used with DB2 is not
necessarily the user-ID of the end-user. If
344 Messages
DSNT376I
provided by the client, the additional tokens subsystem on which the thread associated
further assist in identifying the client end-user. with plan-id2 is executing.
The following identifiers, separated by a colon
DB2 can recover from a lock denial in some cases and
(:), are provided:
can complete successfully. In such a case, the SQLCA is
v The primary authorization-ID associated not filled in. One example is during setup of
with the thread. performance enhancements during bind time for
v Workstation name of the end-user’s execution time.
workstation. An asterisk (*) indicates it is
not relevant to the thread or was not The SQLCA corresponding to correlation id id1,
provided by the client. connection id id2, and LUW-ID id3 contains an
v End-user’s user-ID. An asterisk (*) indicates SQLCODE of -904, -911, -913, or -923 and the name of
it is not relevant to the thread or was not the resource involved in the deadlock.
provided by the client.
v Application name of the end-user’s If you receive a system plan in this message, see the
application. An asterisk (*) indicates that is information about system plans in message DSNT376I.
not relevant to the thread or was not Problem determination:
provided by the client.
Collect the following diagnostic items:
id5 The correlation identifier of the thread
v Console output from the system on which the job
associated with plan-id2.
was run, and a listing of the SYSLOG data set for the
id6 The connection identifier of the thread period of time spanning the failure.
associated with plan-id2. v Dynamic dump, taken to SYS1.DUMPxx data set, by
id7 The logical-unit-of-work identifier of the DB2 (04E and 04F abends).
thread associated with plan-id2. An asterisk (*) v Listing of SYS1.LOGREC data set, obtained by
indicates that the thread does not have an executing IFCEREP1.
LUW-ID. If the LUW-ID is not an asterisk, the v IRLM trace output.
value is a logical-unit-of-work-identifier that is
assigned to the thread followed by an equal .
(=) sign and a token value, which can be used
in place of logical-unit-of-work identifier in DSNT376I PLAN=plan-id1 WITH
any DB2 command that accepts CORRELATION-ID=id1
logical-unit-of-work identifier as input. CONNECTION-ID=id2 LUW-ID=id3
id8 This ID contains additional identifiers that THREAD-INFO=id4 IS TIMED OUT.
define more specific information regarding the ONE HOLDER OF THE RESOURCE IS
identity of the agent. PLAN=plan-id2 WITH
CORRELATION-ID=id5
In many distributed configurations, the CONNECTION-ID=id6 LUW-ID=id7
primary authorization-ID used with DB2 is not THREAD-INFO= id8 ON MEMBER id9
necessarily the user-ID of the end-user. If
provided by the client, the additional tokens Explanation:
further assist in identifying the client end-user. This message is issued whenever plan plan-id1 with
The following identifiers, separated by a colon correlation id1, connection id2, and LUW id3 is denied a
(:), are provided: lock by IRLM, because the amount of time to wait for a
locked resource was exceeded. Plan plan-id2 identifies
v The primary authorization-ID associated
one of the plans holding a lock on the desired resource.
with the thread.
The listed plan is not necessarily responsible for the
v Workstation name of the end-user’s time-out condition.
workstation. An asterisk (*) indicates it is
not relevant to the thread or was not plan-id1, plan-id2
provided by the client. The names of the executing plans.
v End-user’s user-ID. An asterisk (*) indicates id1 The correlation identifier of the thread
it is not relevant to the thread or was not associated with plan-id1. If the execution of the
provided by the client. plan was switched by DB2 to a system agent,
v Application name of the end-user’s the correlation identifier identifies the system
application. An asterisk (*) indicates that is agent. Correlation IDs beginning with ’0nn’,
not relevant to the thread or was not where ’nn’ is a number from 01 to 28, identify
provided by the client. system agents.
id9 Identifies the member name of the DB2 id2 The connection identifier of the thread
associated with plan-id1. If the execution of the logical-unit-of-work-ID in any DB2 command
plan was switched by DB2 to a system agent, that accepts logical-unit-of-work-ID as input.
the connection identifier is the DB2 subsystem
id8 This ID contains additional identifiers that
name.
define more specific information regarding the
id3 The logical-unit-of-work identifier of the identity of the agent.
thread associated with plan-id1. An ’*’ indicates
In many distributed configurations, the
that the thread does not have a LUW-ID. If the
primary authorization-ID used with DB2 is not
LUW-ID is not an ’*’, the value is a
necessarily the user-ID of the end-user. If
logical-unit-of-work-ID that is assigned to the
provided by the client, the additional tokens
thread followed by an ″=″ sign and a token
further assist in identifying the client end-user.
value, which can be used in place of
logical-unit-of-work-ID in any DB2 command The following identifiers, separated by a colon
that accepts logical-unit-of-work-ID as input. (:), are provided:
id4 This ID contains additional identifiers that v The primary authorization-ID associated
define more specific information regarding the with the thread.
identity of the agent. v Workstation name of the end-user’s
workstation. An asterisk (*) indicates it is
In many distributed configurations, the
not relevant to the thread or was not
primary authorization-ID used with DB2 is not
provided by the client.
necessarily the user-ID of the end-user. If
provided by the client, the additional tokens v End-user’s user-ID. An asterisk (*) indicates
further assist in identifying the client end-user. it is not relevant to the thread or was not
provided by the client.
The following identifiers, separated by a colon
v Application name of the end-user’s
(:), are provided:
application. An asterisk (*) indicates that is
v The primary authorization-ID associated not relevant to the thread or was not
with the thread. provided by the client.
v Workstation name of the end-user’s
id9 Identifies the member name of the DB2
workstation. An asterisk (*) indicates it is
subsystem on which the thread associated
not relevant to the thread or was not
with plan-id2 is executing.
provided by the client.
v End-user’s user-ID. An asterisk (*) indicates DB2 can recover from a lock denial in some cases and
it is not relevant to the thread or was not can complete successfully. In such a case, the SQLCA is
provided by the client. not filled in. One example is during setup of
v Application name of the end-user’s performance enhancements during bind time for
application. An asterisk (*) indicates that is execution time.
not relevant to the thread or was not
provided by the client. The SQLCA corresponding to correlation-ID id1,
id5 The correlation identifier of the thread connection-ID id2, and LUW-ID id3 contains an
associated with plan-id2. If the execution of the SQLCODE of -904 or -923 and the name of the resource
plan was switched by DB2 to a system agent, involved in the timeout.
the correlation identifier identifies the system
agent. Correlation IDs beginning with ’0nn’, Several different system plans can appear in plan-id1
where ’nn’ is a number from 01 to 28, identify and plan-id2. These system plans are not documented in
system agents. SYSIBM.SYSPLAN. If you receive a system plan in this
message, you are in contention with another user. If
id6 The connection identifier of the thread you are not doing an automatic rebind, message
associated with plan-id2. If the execution of the DSNT500I or DSNT501I might accompany this message
plan was switched by DB2 to a system agent, and identify that resource. If you need additional
the connection identifier is the DB2 subsystem information, refer to the SQLCA and any additional
name. bind messages. If you are doing an auto rebind, the
id7 The logical-unit-of-work identifier of the SQLCA is not available. Refer to Part 5 of Application
thread associated with plan-id2. An ’*’ indicates Programming and SQL Guide for more information about
that the thread does not have a LUW-ID. If the automatic rebinding. The system plans are:
LUW-ID is not an ’*’, the value is a v ACT
logical-unit-of-work-ID that is assigned to the v BCT
thread followed by an ″=″ sign and a token
v DISTSERV
value, which can be used in place of
v DSNBIND
346 Messages
DSNT376I
v IRLM trace output. id5 Identifies the member name of the DB2
subsystem on which the indoubt thread is
.
executing.
348 Messages
DSNT379I • DSNT380I
DSNT381I IRLM QUIT REQUEST FAILED, RC = DSNT383I csect-name IRLM AUTO-STOP FAILED
xx , SC = yy
Explanation:
Explanation:
During a sign off from IRLM caused by either DB2
During the QUIT (or signoff) request to the IMS/VS normal shutdown (CSECT DSNTLQUI) or DB2
Resource Lock Manager, a return code and subcode subsystem termination (CSECT DSNTLCLE), an
were returned indicating an unsuccessful completion of AUTO-STOP of IRLM using SVC 34 failed. If this
the request. Refer to Codes, for IRLM return codes and occurred during normal sign off, this message
subcode meanings. accompanies abend reason code X’00E30075’.
System action: System action:
This message indicates that the DB2 subsystem DB2 abends.
shutdown could not be completed normally.
Operator response:
Operator response:
Notify the system programmer.
Notify the system programmer.
System programmer response:
System programmer response:
Manually stop IRLM.
Determine the cause of the failure from the return code
Problem determination:
and subcode, and correct the error. Refer to Codes, for
IRLM return codes and subcode meanings. DB2 has Determine the cause of failure from the SVC return
terminated but has not signed off from IRLM. It will be code preserved in register 2.
necessary to issue the ’F irlmproc, ABDUMP’ command
to stop the IRLM. This must be done before issuing Collect the following diagnostic items:
another -START DB2 command. v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
Problem determination: period of time spanning the failure.
Collect the following diagnostic items: v Dynamic dump, taken to SYS1.DUMPxx data set, by
v Console output from the system on which the job DB2 (04E and 04F abends).
was run, and a listing of the SYSLOG data set for the v Listing of SYS1.LOGREC data set, obtained by
period of time spanning the failure. executing IFCEREP1.
v Dynamic dump, taken to SYS1.DUMPxx data set, by v Listing of DSNZPARM module used.
DB2 (04E and 04F abends).
.
v Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
v Listing of DSNZPARM module used. DSNT384I IRLM AUTO-START WAIT TIME
EXCEEDED
v IRLM trace output.
Explanation:
DSNT382I IRLM AUTO-START FAILED An attempt was made to automatically start IRLM.
However, the wait time specified was exceeded.
Explanation:
System action:
During the IDENTIFY to IRLM, the AUTO-START of
IRLM using SVC 34 failed. This message accompanies DB2 is abended.
abend code X’00E30080’.
Operator response:
System action:
Notify the system programmer.
DB2 is terminated with an abend code of X’04E’.
System programmer response:
Operator response:
Either manually start IRLM or modify the
Notify the system programmer. installation-defined auto-start wait time. Restart DB2.
System programmer response: Problem determination:
Determine the cause of failure from the SVC 34 return Collect the following diagnostic items:
code preserved in register 2. v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
350 Messages
DSNT386I • DSNT389I
v Dynamic dump, taken to SYS1.DUMPxx data set, by multiple DSNT389I messages containing the column
DB2 (04E and 04F abends). data. Refer to message DSNT389I for a description of
v Listing of SYS1.LOGREC data set, obtained by the data these headings identify.
executing IFCEREP1.
v Listing of DSNZPARM module used. DSNT389I space type part status conn-id corr-id claims
. Explanation:
This message contains the display information that
Check the IRLMID given in the IRLM procedure
results from a -DISPLAY DATABASE command when
against the IRLMSID in macro DSN6SPRM which was
the keyword CLAIMERS is specified. This message
in the DSNZPARM used at startup.
contains the column data describing the status of a
table space or index space in the database listed in
DSNT386I NAME TYPE PARTS message DSNT362I.
This message forms the headings of a display for a set type TS for a table space, IX for an index space, LS
of messages. This message is always followed by for a LOB table space.
multiple DSNT387I messages. These DSNT387I
| If the object is involved in cloning then the
messages are used to display information that is
| object type will be appended with a ’B’ (base
received as a result of a DISPLAY DATABASE
| object) or a ’C’ (clone object) along with a data
command when the keyword OVERVIEW is specified.
| set instance number. A base object no longer
Refer to message DSNT387I for a description of the
| involved with cloning will have a ’B2’
data these headings identify.
| appended to it’s type if it’s currently
| represented by an instance number 2 data set.
DSNT387I space type parts | A base object no longer involved with cloning,
| that is represented by instance number 1 data
Explanation: | sets, will not have the ’B’ and instance number
This message contains the results from a DISPLAY | suffix.
DATABASE command when the keyword OVERVIEW | Refer to the SYSIBM.SYSTABLESPACE catalog
is specified. This message contains data that describes | table CLONE column to determine if a table
the status of a tablespace or index space in the database | space, and therefore it’s objects, are involved
that is listed in the preceding DSNT362I message. The | with cloning. A CLONE=’Y’ value indicates
data in this message is always preceded by the column | that cloning is active. The INSTANCE column
headings in message DSNT386I. The message number | value indicates the data set instance number
for this message is not displayed. However, messages | for the current base objects.
DSNT386I, DSNT387I, and DSNT390I are always
produced with a multiple line WTO and are never part The partition number. For a nonpartitioned
interrupted. table space or an index on a nonpartitioned
table space, it is blank. For nonpartitioned
space Table space name, index space name, or table indexes on a partitioned table space, it is the
OBID. logical partition number preceded by the
| type TS for a table space, IX for an index space, LS character L (for example, L0001). For
| for a LOB tablespace, TB for a table, or XS for data-partitioned secondary indexes, the prefix
| XML table space for this value will be the character D (for
example, D0001).
| parts Indicates the number of partitions in the table
| space, index space, LOB table space, or XML status Blank, or one or more of the following,
| table space. It is blank for a simple table space, delimited by commas. The maximum length of
| simple index space, or segmented table space. the string is 17 characters.
ACHKP
DSNT388I NAME TYPE PART STATUS CONNID The table space is in aux check
CORRID CLAIMINFO pending state. ACHKP on a table
space indicates that CHECK DATA
Explanation: detected an orphan or missing LOB
This message is the heading for a set of messages that or an out-of-sync condition between
display information as a result of a -DISPLAY the row in the base table and the LOB
DATABASE command when the keyword CLAIMERS in the LOB table space.
is specified. The message number for this message is ARBDP
not displayed. This message is always followed by Advisory Rebuild Pending status is
set when indexes with varying length apply to databases. See for
columns are changed from VARYING information about resolving this
NO to VARYING YES. restricted status.
AREO* The table space is placed in Advisory ICOPY The object (an index space or index
Reorg status. This may be because of partition) is in informational copy
a change in the table or index pending status.
information. It also occurs because the
LPL The object has pages or ranges of
table space, index, or partition
pages that are unavailable because of
identified in this status should be
logical or physical damage.
reorganized for optimal performance.
LSTOP The logical partition is stopped.
AREST The object (a table space, index space,
or a physical partition of a table space PSRBD
or index space) is in an Advisory The index space is in page set rebuild
Restart Pending state. If backout pending status.
activity against the object is not
already underway, it should be RBDP The object (an index space, index
initiated either by issuing the partition or logical index partition) is
RECOVER POSTPONED command or in rebuild pending status. For logical
by recycling the system with the partitions, the RBDP status can
system parameter appear as RBDP*.
LBACKOUT=AUTO. RBDP Indicates that the entire index is
AUXW The table space is in aux warning inaccessible to SQL applications,
state. AUXW on a LOB table space however only the logical partition
indicates that one or more LOBs in needs to be recovered.
the LOB table space is invalid. AUXW RECP The object (a table space, table space
on a base table space indicates that partition, index space, index partition
CHECK DATA detected an orphan or or logical index partition) is in
missing LOB or an out-of-sync recovery pending status.
condition between the row in the base
table and the LOB in the LOB table REFP The object (a table space, a table
space. space partition, index space, or index
space partition) is in refresh pending
CHKP The object (a table space or a partition status. For a table space, run LOAD
within a table space) is in check REPLACE or the RECOVER utility to
pending status. resolve this restricted status, or use
COPY The object (a table space or a partition the REBUILD INDEX utility to
within a table space) is in copy rebuild the index from the data.
pending status. An image copy is REORP
required for this object. The object (a table space or table
| DBETE The DBET status for the object (a space partition) is in recovery
| table space, a partition within a table pending status.
| space, an index space, an index RESTP The object is in the Restart Pending
| partition, or a logical index partition) state. Backout activity against the
| is in error. The error occurred when object must be completed by using
| the DBET states were being modified the -RECOVER POSTPONED
| during log apply or must-complete command, or by recycling the system
| processing. This prohibited DB2 from with system parameter
| successfully updating the DBET LBACKOUT=AUTO.
| states.
RO The table space, table space partition,
GRECP index space or index space partition
The object (a table space, a table is started for read-only activity.
space partition, index space, or index
space partition) is marked recovery RW The table space, table space partition,
pending because of the failure of a a index space or index space partition
group buffer pool. This status value is started for read and write activity.
appears only on spaces. It does not STOP The table space, table space partition,
index space or index space partition
is stopped.
352 Messages
DSNT390I • DSNT392I
STOPE The table space or index space was H The claim is held across commit.
implicitly stopped because there is a
problem with the log RBA in a page.
DSNT390I * DISPLAY OF DATABASE name
Message DSNT500I or DSNT501I is
action*
issued when the error is detected to
indicate the inconsistency. Explanation:
STOPP A stop is pending for the database, This message indicates the end of a set of DSNT391I
table space, table space partition, and DSNT392I messages, a set of DSNT393I and
index space or index space partition. DSNT394I messages, or a set of DSNT395I and
DSNT396I messages.
UT The table space, table space partition,
index space or index space partition In this message:
is started for utility processing only. v The ’name’ is the name of the database.
UTRO A utility is in process on the table v The ’action’ is one of the following:
space, table space partition, index
space, or index space partition that CONTINUES
allows only RO access. The remaining table space and index space
names within this database are continued to
UTRW A utility is in process on the table a new display.
space, table space partition, index
space or index space partition that TERMINATED
allows RW access. The remaining table space and index space
names within this database are terminated.
UTUT A utility is in process on the table
space, table space partition, index ENDS The display for this database is complete.
space or index space partition that
allows only UT access. DSNT391I NAME TYPE STATUS PHYERRLOW
WEPR This object has pages or ranges of PHYERRHI CATALOG PIECE
pages that are unavailable because of Explanation:
physical damage. To reset this flag,
you can use either the RECOVER This message indicates the beginning of a set of
utility with the option as ERROR messages used to display information as a result of a
RANGE or the LOAD utility with the DISPLAY DATABASE command when the keywords
option as REPLACE. WEPR, LOCKS, LPL, CLAIMERS and USE are omitted.
(The message appears in one continuous line across the
If the status for a nonpartitioned index is screen, not as shown above.) This message forms the
blank, then the status information is displayed headings of the display and is always followed by
at the logical partition level. If the type is TB, multiple DSNT392I messages containing the column
the status is blank. data. Refer to message DSNT392I for a description of
the data these headings identify.
conn-id A connection identifier for the thread.
corr-id A correlation identifier of the thread associated DSNT392I space type part status lo-page hi-page
with the space name. cat-name piece
claims The type and duration of currently held Explanation:
claims. The claim is composed of a claim class
descriptor and a claim duration descriptor. This message contains the display information as a
result of a DISPLAY DATABASE command when the
The claim class descriptor has one of the keywords LOCK, CLAIMERS, LPL and USE are
following values: omitted. This message contains the column data
describing the status of a table space or index space in
CS Cursor stability claim class
the database listed in the preceding DSNT362I message.
RR Repeatable-read claim class This message is always preceded by its column
headings in message DSNT391I. The message number
WR Write claim class
for this message is not displayed. However, messages
DSNT391I, DSNT392I, and DSNT390I are always
The claim duration descriptor describes the produced with a multiple line WTO and are never
duration of the claims as follows: interrupted.
A The claim is held until deallocation. In this message:
C The claim is held until the next v The space is the table space name or index space
commit point. name.
354 Messages
DSNT395I • DSNT396I
v The conn-id is a connection identifier for the thread. – ’sign-on id’ or the LTERM if the thread is from an
It is one of the following: IMS message-drive region.
– BATCH if the thread is from a batch region. – AXBUSER if the thread is from an IMS
– TSO if the thread is from a TSO terminal. message-driven region and RACF is used.
– UTILITY if the thread is from a utility. – ’PSB name’ if the thread is from an IMS
nonmessage-driven region and RACF is not used.
– ’IMS identifier’ if the thread is from an IMS
terminal. – ’user-id’, ’term id’, ’tran id’ or other, as specified
in the resource control table (RCT), if the thread is
– ’CICS identifier’ if the thread is from a CICS
from CICS.
terminal.
– CONSOLE if the thread is from the console.
DSNT395I NAME TYPE PART STATUS CONNID
v The corr-id is a correlation identifier of the thread
CORRID LOCKINFO
associated with the space name. It is one of the
following: Explanation:
– ’job name’ if the thread is from a batch region. This message indicates the beginning of a set of
– ’TSO logon identifier’ if the thread is from a TSO messages used to display information as a result of a
terminal. DISPLAY DATABASE command when the keyword
– PST#.PSBNAME if the thread is from an IMS LOCKS is specified. This message forms the headings
terminal. of the display. (The message appears in one continuous
line across the screen, not as shown above.) This
– ’entry ID.thread number.tran id’ if the thread is
message is always followed by multiple DSNT396I
from a CICS terminal.
messages containing the column data. Refer to message
– CONSOLE if the thread is from the console. DSNT396I for a description of the data these headings
– ’0nn’, where ’nn’ is a number , if the thread is for identify.
a system agent.
– For distributed database access threads, this field DSNT396I space type part status conn-id corr-id lock
contains the following:
Explanation:
- While the thread is being created:
1. ’028.DBAA nn’, where nn ranges from 01 to This message contains the display information that
99. This indicates that the database access results from a DISPLAY DATABASE command when
agent (DBAA) is in its connection the keyword LOCKS is specified. This message contains
processing, which consists of establishing the column data describing the status of a table space
the DBAA thread, and validating and or index space in the database listed in the preceding
verifying the user’s ID. Refer to ″Controlling DSNT362I message. This message is always preceded
Access to a DB2 Subsystem″ in by its column headings in message DSNT395I. The
Administration Guide for descriptions of the message number for this message is not displayed.
authorization checks that might be However, the messages DSNT395I, DSNT396I, and
performed. DSNT390I are always produced with a multiple line
WTO and are never interrupted.
All RACF requests are serialized on a single
DB2 RACF service task, which might In this message:
increase the validation time when multiple v The space is the table space name, index space name,
DBAAs are being created concurr or table OBID.
- After the thread is created: v The type is TS for a table space, IX for an index
1. For threads using system-directed access space, LS for a LOB table space or TB for a table.
and threads using application-direct access | If the object is involved in cloning then the object
from a DB2 requester, this variable displays | type will be appended with a ’B’ (base object) or a ’C’
the correlation ID of the thread at the | (clone object) along with a data set instance number.
requesting location. | A base object no longer involved with cloning will
2. For threads using application-directed access | have a ’B2’ appended to it’s type if it’s currently
from a non-DB2 requester, this variable | represented by an instance number 2 data set. A base
displays the first twelve characters in the | object no longer involved with cloning, that is
DDM external name (EXTNAM) parameter | represented by instance number 1 data sets, will not
of the DDM EXCSAT command received as | have the ’B’ and instance number suffix.
part of the SQL CONNECT | Refer to the SYSIBM.SYSTABLESPACE catalog table
v The user-id is one of the following: | CLONE column to determine if a table space, and
– ’TSO logon identifier’ if the thread is from a TSO | therefore it’s objects, are involved with cloning. A
terminal. | CLONE=’Y’ value indicates that cloning is active.
| The INSTANCE column value indicates the data set from a DB2 requester, this variable displays
| instance number for the current base objects. the correlation ID of the thread at the
v The part is the partition number. It is blank for a requesting location.
simple table space, simple index space, or segmented 2. For threads using application-directed access
table space. For nonpartitioned secondary indexes, it from a non-DB2 requester, this variable
is the logical partition number preceded by the displays the first twelve characters in the
character L (for example, L0001). For data-partitioned DDM external name (EXTNAM) parameter
secondary indexes, the prefix for this value will be of the DDM EXCSAT command received as
the character D (for example, D0001). part of the SQL CONNECT
v See DSNT389I for a list of the possible status display
strings. If the type is TB, the status field is blank. corr-id is not specified when the displayed lock is a
P-lock or a retained lock.
v The conn-id is a connection identifier for the thread.
It is one of the following: v The lock describes the type and duration of locks:
– BATCH if the thread is from a batch region. – Transaction locks (also called L-locks) are
identified by their correspondin agents’ connection
– TSO if the thread is from a TSO terminal.
and correlation IDs
– UTILITY if the thread is from a utility.
Multiple locks held by an agent are listed on
– ’IMS identifier’ if the thread is from an IMS multiple lines of the report followed by any locks
terminal. the agent is currently awaiting.
– ’CICS identifier’ if the thread is from a CICS – Physical locks (P-locks) and retained locks are
terminal. identified by their DB2 data sharing member
– CONSOLE if the thread is from the console. names.
Multiple P-locks or retained locks held by a DB2
When the displayed lock is a P-lock or a retained data sharing member are listed on multiple lines
lock, conn-id is not specified. of the report followed by any locks the member is
v The corr-id is a correlation identifier of the thread currently awaiting.
associated with the space name. It is one of the
The lock is composed of a ’lock status’ and followed
following:
by a dash ’-’, a ’lock state’ followed by a ’lock type’,
– ’job-name’ if the thread is from a batch region. and a ’lock duration’ delimited by commas.
– ’TSO logon identifier’ if the thread is from a TSO – The ’lock status’ is a value of:
terminal.
H The lock is held by the agent or the DB2
– PST#.PSBNAME if the thread is from an IMS
member.
terminal.
– ’entry ID.thread number.tran id’ if the thread is W The agent or the member is awaiting the
from a CICS terminal. lock.
– CONSOLE if the thread is from the console. R The lock is retained.
– For distributed database access threads, this field – The ’lock state’ describes themode of the lock as
contains the following: follows:
- While the thread is being created: - For L-locks and drain locks,
1. ’028.DBAA nn’, where nn ranges from 01 to IS A lock with read intentions.
99. This indicates that the database access
agent (DBAA) is in its connection IX A lock with update intentions.
processing, which consists of establishing S A lock with read-only capability.
the DBAA thread, and validating and
verifying the user’s ID. Refer to ″Controlling U A lock with update capability.
Access to a DB2 Subsystem″ in
SIX A table space or table lock with a
Administration Guide for descriptions of the
protocol that does not lock a page
authorization checks that might be
while reading, but locks the page with
performed.
update intention while updating.
All RACF requests are serialized on a single
DB2 RACF service task, which might X An exclusive lock.
increase the validation time when multiple - For L-locks on LOB table spaces,
DBAAs are being created concurr
IS A lock with intent to reserve space
- After the thread is created: within the LOB table space
1. For threads using system-directed access
IX A lock with intent to insert LOBs in the
and threads using application-direc access
LOB table space.
356 Messages
DSNT397I
S A lock which reserves space within the the local DB2 system’s lock waiting queue. When
LOB table space. this lock is acquired, its duration is the same as all
locks held by the user.
SIX A lock which allows the owner to read
and update LOBs. – For a P-lock, the lock is owned by the system, not
the user, and its duratio is not related to the
X An exclusive lock. duration of the locks that are owned by the user.
- For P-locks, – Retained locks do not have a lock duration.
IS This DB2 member has R/O interest.
The page set or partition is group All index spaces on tables are implicitly locked with
buffer pool (GBP) dependent. transaction locks at the same level as the table spaces
containing those tables. P-locks are acquired by DB2 on
IX This DB2 member has R/W interest. index spaces as well as on table spaces.
The page set or partition is
GBP-depende
DSNT397I
S This DB2 member has R/O interest.
The page set or partition is not Explanation:
GBP-dep This message indicates the beginning of a multiple line
SIX This DB2 member has R/W interest. display generated as a result of a DISPLAY DATABASE
The page set or partition is command. The format of this multiple line display has
GBP-depende three parts:
v The column headers, which are dependent on the
NSU This DB2 member has R/W interest.
keywords issued. The headers are underlined.
The page set or partition is
GBP-depende v The space information for all spaces and partitions
requested by the command
X This DB2 member has R/W interest.
v An ending message to state whether the spaces were
The page set or partition is not
displayed or not.
GBP-dep
– The ’lock type’ describes the type of locking as There are six different headers for the DISPLAY
follows: DATABASE commands. The headers are dependent on
S A table space L-lock the presence of the keywords: CLAIMERS, LOCKS,
USE, LPL, OVERVIEW, or no keyword. These five
T A table L-lock different DISPLAY DATABASE command formats are
C A cursor-stability read drain lock described below.
v DISPLAY DATABASE CLAIMERS
R A repeatable-read drain lock
This DISPLAY DATABASE command displays the
W A write drain lock claims that are on certain table spaces, index spaces,
and partitions.
P A partition L-lock
The column headers in this command are as follows:
PP A page set or partition P-lock
NAME TYPE PART STATUS CONNID CORRID
– If the ’lock status’ is H, the ’lock duration’ CLAIMINFO
describes the duration of the lock:
– NAME is the table space name or index space
A The lock is freed at deallocation. name.
C The lock is freed at commit. – TYPE is TS for a table space, IX for an index
space, LS for a LOB table space.
H The lock is freed when all cursors are
| If the object is involved in cloning then the object
closed.
| type will be appended with a ’B’ (base object) or a
M The lock is freed by the system. | ’C’ (clone object) along with a data set instance
| number. A base object no longer involved with
P The lock is freed when the plan is | cloning will have a ’B2’ appended to it’s type if it’s
complete. | currently represented by an instance number 2
I The lock is a page set or partition P-lock. | data set. A base object no longer involved with
It is released when the pageset or | cloning, that is represented by instance number 1
partition data set is closed. | data sets, will not have the ’B’ and instance
| number suffix.
– If the ’lock status’ is W, the ’lock duration’ is a
2-digit number indicating the waiter’s position in | Refer to the SYSIBM.SYSTABLESPACE catalog
| table CLONE column to determine if a table
| space, and therefore it’s objects, are involved with
| cloning. A CLONE=’Y’ value indicates that - ’job name’ if the thread is from a batch region.
| cloning is active. The INSTANCE column value - ’TSO logon identifier’ if the thread is from a
| indicates the data set instance number for the TSO terminal.
| current base objects.
- PST#.PSBNAME if the thread is from an IMS
– PART is the partition number. It is blank for a terminal.
simple table space or simple index space. For
- ’entry ID.thread number.tran id’ if the thread is
nonpartitioned indexes on a partitioned table
from a CICS terminal.
space, it is the logical partition number preceded
by the character L (for example, L0001). For - CONSOLE if the thread is from the console.
data-partitioned secondary indexes, the prefix for - ’0nn’, where ’nn’ is a number, if the thread is
this value will be the character D (for example, for a system agent.
D0001). - For distributed database access threads, this
– See DSNT389I for a list of the possible status field contains the following:
display strings. v While the thread is being created:
– For L-locks on LOB table spaces, 1. ’028.DBAA nn’, where nn ranges from 01
IS A lock with intent to reserve space within to 99. This indicates that the database
the LOB table space access agent (DBAA) is in its connection
processing, which consists of establishing
IX A lock with intent to insert LOBs in the the DBAA thread, and validating and
LOB table space. verifying the user’s ID. Refer to
S A lock which reserves space within the ″Controlling Access to a DB2 Subsystem″
LOB table space. in Administration Guide for descriptions of
the authorization checks that might be
SIX A lock which allows the owner to read performed.
and update LOBs.
All RACF requests are serialized on a
X An exclusive lock. single DB2 RACF service task, which
might increase the validation time when
If the type is TB, the status field is blank. multiple DBAAs are being created concurr
v After the thread is created:
If the status for an index is blank, then the status 1. For threads using system-directed access
information is displayed at the logical partition and threads using application-direct
level. access from a DB2 requester, this variable
– The CONNID is a connection identifier for the displays the correlation ID of the thread
thread. It is one of the following: at the requesting location.
- BATCH if the thread is from a batch region. 2. For threads using application-directed
- TSO if the thread is from a TSO terminal. access from a non-DB2 requester, this
variable displays the first twelve
- UTILITY if the thread is from a utility.
characters in the DDM external name
- ’IMS identifier’ if the thread is from an IMS (EXTNAM) parameter of the DDM
terminal. EXCSAT command received as part of the
- ’CICS identifier’ if the thread is from a CICS SQL CONNECT
terminal. – CLAIMINFO is the type and duration of currently
- CONSOLE if the thread is from the console. held claims. The claim is composed of a claim
- For distributed database access threads, this class descriptor and a claim duration descriptor.
field contains the following: The claim class descriptor has one of the following
v For threads using system-directed access and values:
for threads using application-directed access CS Cursor stability claim class
from a DB2 Version 3 or later requester, this
variable displays the connection name of the RR Repeatable-read claim class
thread at the requesting location. WR Write claim class
v For threads using application-directed access
from a non-DB2 requester or from a DB2 The claim duration descriptor describes the
Version 2 Release 3 requester, this field duration of the claims as follows:
displays the constant SERVER.
A The claim is held until deallocation.
– CORRID is a correlation identifier of the thread
associated with the space name. It is one of the C The claim is held until the next commit
following: point.
358 Messages
DSNT397I
W The agent or the member is awaiting H The lock is freed when all cursors are
the lock. closed.
- For a P-lock, the lock is owned by the system, NAME TYPE PART STATUS PHYERRLO PHYERRHI
not the user, and its duratio is not related to the CATALOG PIECE
duration of the locks that are owned by the In this message:
user.
– The NAME, TYPE, PART, and STATUS columns
- Retained locks do not have a lock duration. are described in the DISPLAY DATABASE
CLAIMERS section.
There are no explicit index space locks. However, all
– When a data set supporting the specified table
index spaces on tables are implicitly locked at the
space or index space has physical I/O errors,
same level as the table spaces containing those
PHYERRLO is a hexadecimal number identifying
tables. P-locks are acquired by DB2 on index spaces
the lowest page number containing an I/O error.
as well as on table spaces.
This column is blank if there are no physical
v DISPLAY DATABASE USE errors.
This DISPLAY DATABASE command displays the – When a data set supporting the specified table
user IDs that are accessing certain table spaces, index space or index space has physical I/O errors,
spaces, and partitions. PHYERRHI is a hexadecimal number identifying
The column headers in this command are as follows: the highest page number containing an I/O error.
NAME TYPE PART STATUS CONNID CORRID This column is blank if there are no physical
USERID errors.
– The NAME, TYPE, PART, STATUS, CONNID, and – When a data set supporting the specified table
CORRID columns are described in the DISPLAY space or index space has physical I/O errors,
DATABASE CLAIMERS section. CATALOG identifies the catalog owning the data
set with the I/O errors. This column is blank if
– The USERID is one of the following: there are no physical errors.
- ’TSO logon identifier’ if the thread is from a – When a data set supporting the specified table
TSO terminal. space or index space has physical I/O errors,
- ’sign-on id’ or the LTERM if the thread is from PIECE is an integer number identifying the piece
an IMS message-drive region. within the table space or index space having the
- AXBUSER if the thread is from an IMS error. This column is blank if there are no physical
message-driven region and RACF is used. errors.
- ’PSB name’ if the thread is from an IMS The piece number can be used to construct the
nonmessage-driven region and RACF is not name of the data set supporting the space
used. containing the physical error as follows:
- ’userid’, ’term id’, ’tran id’ or other, as specifie cat-name.DSNDBC.database-
in the resource control table (RCT), if the thread name.space-name.I0001.Axxxx
is from CICS.
The value xxxx is the piece number plus one and
v DISPLAY DATABASE LPL
database-name is the name displayed in the
NAME TYPE PART STATUS LPL PAGES preceding DSNT362I message. Note that if the
This message contains the display information table space or index space is partitioned, the
resulting from a DISPLAY DATABASE command partiti number should equal the piece number
when the keyword LPL is specified. It contains the plus one.
column data describin the status of a table space or
index space in the database listed in the precedi There are other informational messages that can be
DSNT362I message. This message is always preceded displayed that are not related to one specific keyword.
by its column headings message DSNT805I. The They are listed below:
message number for this message is not displayed. v -luw-id ACCESSING DATA FOR location
In this message: This message is issued for each thread reported that
– The LPL PAGES column lists the pages in the is participating in distributed data access (database
specified space that are unavailable because of access thread). The thread that corresponds to this
logical or physical damage. message is the thread named by the correlation id
v DISPLAY DATABASE (with no LOCKS, USE, LPL or and connection id of the data line preceding this
CLAIMERS keyword). message. This additional line reports the distributed
identification as follows:
This DISPLAY DATABASE command displays the
error page range information for certain table spaces, luw-id=token
index spaces, and partitions. The logical-unit-of-work identifier (LUW-ID)
The column headers in this command are as follows: is a unique identifier that is assigned to the
thread followed by an ’=’ sign and a token.
360 Messages
DSNT398I • DSNT402I
The token can be used in place of luw-id in invoker has authority to display, have LOCK or USE
any DB2 command that accepts luw-id as information available. This message is produced only
input. when the keywords USE and LOCKS are specified.
location
The ending message looks like this:
The LOCATION name assigned to the
requesting site.
* DISPLAY OF DATABASE name action *
v -MEMBER NAME member-name
This message is issued with messages DSNT389I, In this message:
DSNT394I or DSNT396I for each thread in a data
sharing environment. This additional line reports the name The name of the database
member name of the DB2 subsystem accessing this action One of the following:
object.
CONTINUES
If the characters ’(CO)’ follow the member name,
The remaining table space and index
then this member is the castout owner for the page
space names within this database are
set or partition. The castout owner for a page set or
continued to a new display.
partition is the DB2 member responsible for doing all
of the castout I/O for that page set or partition. TERMINATED
The message number and subsystem recognition The remaining table space and index
character are not included in this message. space names within this database are
terminated.
v INVALID space-name
The space-name specified in the SPACENAM ENDS The display for this database is
keyword on the -DISPLAY DATABASE command complete.
does not exist. The name of the table space or index
space is ’space-name’. The request is rejected. DSNT398I
v NO SPACES FOUND
Explanation:
This message is produced when a DISPLAY
DB(name) SPACENAM is entered and no spaces This message appears within a multiple line WTO
were found to satisfy the request. SPACENAM(...) message set and precedes DSNT391I, DSNT393I, and
might have been entered as a range, a subset, or a DSNT395I. It is used to underscore the column
list of spaces. headings.
v spacetype name NOT type This message is issued by CSECT: DSNTDMUL
This message is produced when no table space or
index space listed in the DISPLAY DB(...)
DSNT399I INVALID space-name
SPACENAM(...) satisfies your request.
Explanation:
spacetype
TABLESPACE if the space is a table space or The space-name specified in the SPACENAM keyword
INDEXSPACE if the space is an index space. on the -DISPLAY DATABASE command does not exist.
The name of the table space or index space is
name The name of the space.
’space-name’. The request is rejected.
type A character string that indicates the type of
request specified. The string is a list of the
DSNT400I SQLCODE = 0, SUCCESSFUL
following, delimited by ’OR’:
EXECUTION
– ACTIVE if the keyword ACTIVE is
specified Explanation:
– RESTRICTED if the keyword RESTRICT The SQLCODE was 0, indicating successful execution
is specified. of the function. SQLWARN indicators may note some
v NO INFORMATION AVAILABLE warnings. SQLWARNx fields are described in Appendix
D of SQL Reference..
This message is produced when there is no LOCK or
USE information available. When DISPLAY DB(...) is
entered, and DB(...) is a list of databases or a list of DSNT402I ONLINE BOOK DATA SET NAMES
names, this message indicates that no listed database MUST END IN ’.BOOK’
has LOCK or USE information available.
Explanation:
If DISPLAY DB(...) or DISPLAY DB(...)
SPACENAM(*) is entered, and DB(...) is a range or All book names entered on this panel must end in
subset of databases, or all databases (’*’), this ″.BOOK″.
message indicates that no databases, for which the
Explanation:
DSNT409I BUFFERPOOL SIZES SHOWN MAY BE
You specified the percent sign (%) or the underscore OBSOLETE
character (_) as the application registration table/object
registration table (ART/ORT) escape character. The Explanation:
ART/ORT escape character can be any other character. The buffer pool sizes shown here were set at
System action: installation or migration time and might not be the
most current. Updates might have occurred using the
The panel is redisplayed and the cursor is placed on ALTER BUFFERPOOL command.
the field that produced the error.
System action:
362 Messages
DSNT410I • DSNT414I
Processing continues.
DSNT411I SQLCAID = xxxx, SQLCA IDENTIFIER
Explanation:
DSNT410I THE SUBSYSTEM COMMAND PREFIX
ENTERED IS INCORRECT The SQLCA ID field (SQLCAID) is not the expected
value, C’SQLCA’.
Explanation:
System programmer response:
An incorrect command prefix was entered. The first
character of the command prefix must be one of the The SQLCA area is invalid. This type of error is usually
following characters: the result of one of the following:
v Calling the DSNTIAR formatting routine before an
Character Description SQL statement initializes the area
@ at sign v Overlaying the SQLCA area
$ dollar sign v Passing the wrong address to the DSNTIAR routine.
# number sign Correct the error, and rerun the application program.
. period
/ forward slash DSNT412I SQLCABC = xxxx, SQLCA BYTE
COUNT
’ apostrophe
Explanation:
? question mark
The size of the SQLCA is not the expected value (136
″ quotation mark
bytes).
% percent sign
System programmer response:
! exclamation point
The SQLCA area is invalid. Correct the error. It is
< less than symbol probably an overlay or an incorrect SQLCA address.
) closing parenthesis Rerun the application program.
* asterisk
DSNT413I SQLCODE = xxxx, INVALID SQLCODE
+ plus sign
Explanation:
- minus sign
The SQL return code is not a valid value.
= equal sign
¢ cent sign System programmer response:
For the other characters in the command prefix, you v Calling the DSNTIAR formatting routine before an
can use any character from the preceding set, uppercase SQL statement initializes the area
letters (A-Z), and digits (0-9). v Overlaying the SQLCA area
This message is issued by the following panel: v Passing the wrong address to the DSNTIAR routine.
DSNTIPM
If the maintenance was not coordinated correctly, the
System action: DSNTIAR and DSNTIAM CSECTs were probably not
The panel is redisplayed and the cursor is placed on replaced in the code that is now running. Link-edit the
the field in error load module, and replace DSNTIAR and DSNTIAM.
Correct the error, and rerun the application program.
User response:
Enter a valid command prefix DSNT414I SQLERRM = xxxx, SQLCA ERROR
MESSAGE INSERTION TEXT
Explanation:
This message results from an SQL return code that is
not recognized by DSNTIAR. SQLERRM contains error | performed, wherein DB2 does not access nor
message text. | count individual rows.
System programmer response: v For SQLCODE -911 or -913, a reason code
that indicates whether a deadlock or
Either the SQLCA area is invalid or the maintenance timeout occurred. Tip: The most common
was not coordinated correctly. As a result, the SQL reason codes are:
return code was added to the DB2 subsystem but not
– 00C90088 - deadlock
to the formatting routine.
– 00C9009E - timeout
An invalid SQLCA area is usually the result of one of
the following: 4 Reserved
v Calling the DSNTIAR formatting routine before an 5 Position or column of a syntax error for
SQL statement initializes the area PREPARE or EXECUTE IMMEDIATE
v Overlaying the SQLCA area 6 DB2 internal buffer manager error code
v Passing the wrong address to the DSNTIAR routine.
System programmer response:
If the maintenance was not coordinated correctly, the Refer to Appendix D of SQL Reference for further
DSNTIAR and DSNTIAM CSECTs were probably not information on the contents of the SQLERRD fields.
replaced in the code that is now running. Link-edit the The SQL diagnostic information might help in
load module, and replace DSNTIAR and DSNTIAM. diagnosing an error or in indicating the results of
Correct the error, and rerun the application program. successful execution. If this error or warning should not
occur, correct the error. Rerun the program or SQL
statement.
DSNT415I SQLERRP = xxxx, SQL PROCEDURE
DETECTING ERROR
DSNT417I SQLWARNn-n SQL WARNINGS
Explanation:
Explanation:
The name of the procedure detecting the error is
provided in the SQLERRP. At least one of the 11 warning values is not the
expected value (a blank). A nonblank value in one of
System programmer response:
the 11 warning fields has the following meaning:
(The SQL procedure detecting the error may be of help
SQLWARN0
in diagnosing an error or warning.) Correct the error if
Any other warning code is set.
there is one noted in other messages. Rerun the
program or SQL statement. SQLWARN1
String truncation.
DSNT416I SQLERRD = xx,xx,xx,xx,xx,xx SQL SQLWARN2
DIAGNOSTIC INFORMATION Null value(s) eliminated.
Explanation: SQLWARN3
Number of host variables provided did not
One or more of the six diagnostic fields do not have
equal degree of the table.
the expected value. Check that all of the diagnostic
fields contain one of the following expected values: SQLWARN4
v 00, 00, 00, 00, 00, 00 or No WHERE clause on UPDATE or DELETE.
v 00, 00, 00, -1, 00, 00 SQLWARN5
Not a DB2 SQL statement.
The SQL diagnostic information for each of the six
SQLWARN6
values is as follows:
Date or timestamp value adjusted.
1 DB2 unique internal relational data system
SQLWARN7
code
Conversion of decimal number from precision
2 DB2 internal data manager error code 31 to precision 15 caused truncation of
fractional digits.
3 One of the following conditions:
| v Number of rows inserted, updated, or | SQLWARN8
| deleted following an INSERT, UPDATE, | Character that does not exist on the target
| MERGE or DELETE statement. Attention: A | code page was replaced with a substitution
| ’-1’ in this field indicates that a mass delete | character.
| of a table in a segmented table space was
364 Messages
DSNT418I • DSNT425I
SQLWARN9
DSNT422I THE ART TABLE NAME MUST BE
Arithmetic exceptions have been ignored
DIFFERENT FROM THE CRT TABLE
during processing of COUNT DISTINCT.
NAME
SQLWARNA
Explanation:
| At least one character field of the SQLCA is
| invalid due to a string conversion error. You entered the same name for the Application
Registration Table and the Object Registration Table on
User response:
the Data Definition Control Support panel.
The SQL warning information may be of help in
This message is issued by the following panel:
diagnosing an error or in indicating the results of
DSNTIPZ
successful execution. If this warning should occur,
correct the error and rerun the program or SQL System action:
statement.
The panel is redisplayed and the cursor is placed on
the field in error.
DSNT418I SQLSTATE = sqlstate, SQLSTATE
User response:
RETURN CODE
Change either the APPL REGISTRATION TABLE field
Explanation:
or the OBJT REGISTRATION TABLE field to make
The SQLSTATE is a return code that indicates the these two fields unique with respect to each other.
outcome of the most recently executed SQL statement.
The execution of every SQL statement sets SQLSTATE
DSNT424I OUTPUT DATA SETS MUST BE
to a five-digit code in the range of 00000 to 65535. This
DIFFERENT FROM THE INPUT DATA
has no effect on the existing use of any other field in
SETS
the SQLCA.
Explanation:
User response:
You specified an output data set name that is the same
The reason the build phase failed is identified by the
as one of the input data set names built from the
reason code, which is described in Codes.
PREFIX and SUFFIX fields on the main panel
DSNTIPA1.
DSNT419I WARNING - MAX REMOTE ACTIVE
This message is issued by the following panel:
PREVIOUSLY SPECIFIED AS 0.
DSNTIPT
Explanation:
System action:
You specified a value of 0 for the number of active
The panel is redisplayed and the cursor is placed on
database access threads on a previous panel. This value
the field in error.
might be inconsistent with a DDF STARTUP OPTION
of AUTO or COMMAND. User response:
This message is issued by the following panel: Either change the data set name under the cursor or
DSNTIPR change the PREFIX or SUFFIX fields on panel
DSNTIPA1.
System action:
The panel is redisplayed and the cursor is placed on
DSNT425I ALL THREE OUTPUT DATA SETS
the DDF STARTUP OPTION field.
MUST BE UNIQUE
User response:
Explanation:
No response is necessary if your intent is to have DDF
You specified the same name for two or more of the
started with no active database access threads allocated
output data sets.
and DDF is used as a requester only. Press ENTER to
continue. Otherwise, either change the DDF STARTUP This message is issued by the following panel:
OPTION to NO or MAX REMOTE ACTIVE to the DSNTIPV
number of threads you want.
System action:
Severity:
The panel is redisplayed and the cursor is placed on
4 (warning) the field in error.
User response:
Change the data set name under the cursor or the data
set field(s) that are the same as the one under the The panel is redisplayed and the cursor is placed on
cursor. the field in error.
User response:
DSNT426I ALL THREE DATA SETS ARE
Reduce the length of the prefix or change the
REQUIRED FOR OUTPUT
TIMESTAMP ARCHIVES value to NO.
Explanation:
You specified one or more output data sets and left one DSNT429I THE SUM OF MAX USERS AND MAX
or more output data set fields blank. REMOTE ACTIVE MUST BE <= TO
2000
This message is issued by the following panel:
DSNTIPT Explanation:
System action: The total number of threads determined by MAX
USERS and MAX REMOTE fields is too large.
The panel is redisplayed and the cursor is placed on
the field in error. System action:
User response: The panel is redisplayed and the cursor is placed on
the field in error.
You must specify all or none of the output data set
fields. Leave blank all output data set fields if you do User response:
not want the installation CLIST to edit any CLISTs or
Reduce the MAX USERS field, or the MAX REMOTE
JCL.
field, or both.
366 Messages
DSNT433I • DSNT436I
v With a DDF value of ’AUTO’ or ’COMMAND’, you 1. Press ENTER to continue; the data set(s) will be
must choose a non-zero value for the EBCDIC deleted and reallocated OR
CODED CHAR SET. 2. Press RETURN to leave the installation process; the
v With a DEF ENCODING SCHEME value of ’ASCII’, data set(s) will not be deleted OR
you must choose non-zero values for EBCDIC and 3. Change the data set name(s); the new name will be
ASCII CODED CHAR SETs. checked for existence.
CONTROL(CONLIST) and invoke the CLIST. This Choose one of the following responses:
produces tracing for error documentation. v Ensure that you can run with the overcommitment of
Severity: lock address space, or
v Lower the value(s) of the MAX USERS, MAX
4 (warning)
REMOTE ACTIVE, or LOCKS PER USER fields, or
v Increase the value of the MAX STORAGE FOR
DSNT437I REGION SIZE IS TOO LARGE LOCKS field.
Explanation: Severity:
The numbers you specified produced a region size 4 (warning)
estimate of more than 8000KB. This estimate does not
include the storage required for SWA, because it is
assumed that you placed SWA above the 16MB line. DSNT439I IRLM NO LOCK ESCALATION OR NO
The region size calculation is discussed in Part 2 of USER MAXIMUM
Installation Guide. Explanation:
This message is issued by the following installation You specified the number 0 for:
CLIST: DSNTINST
v The number of table or table space locks that will
System action: cause lock escalation, or
The CLIST continues, but does not produce edited jobs. v The number of locks that will terminate a DB2 user.
368 Messages
DSNT442E • DSNT448I
This message is issued by the following CLIST: DSNTIJMV that was produced and correct the
DSNTINST IEBUPDTE CHANGE statement.
System action: Severity:
The CLIST continues. 8 (error)
User response:
DSNT451I WARNING-THE LOCAL DATE
Compare this recommended value with the actual
LENGTH OR LOCAL TIME LENGTH
available real storage.
HAS BEEN INCREASED
Severity:
Explanation:
0 (successful execution)
The LOCAL DATE LENGTH or LOCAL TIME
LENGTH has been increased and a REBIND command
DSNT449I NUMBER OF LOGS REDUCED FROM must be issued for any dependent plans.
old-num TO MAXIMUM OF 31
This message is issued by the following installation
Explanation: CLIST: DSNTINST
The number of active log data sets used in the DB2 System action:
release you are migrating from is greater than the new
Processing continues.
maximum number of data sets allowed for the current
release of DB2. Installation job DSNTIJUZ will update User response:
your bootstrap data sets to contain only the last 31 data
Rebind all application plans that depend upon the
sets.
length of the local format that was changed.
This message is issued by the following panel:
Severity:
DSNITPL
4 (warning)
System action:
The value is reduced to the maximum of 31 and the
DSNT454I ERROR CODE = errcode, CNT = count
panel is displayed.
Explanation:
User response:
An error was encountered during CLIST processing for
Update any other fields on the panel and continue.
reading the parameter member. Most of these errors are
caused by having a mismatch between the level of the
DSNT450I type ENTRY MUST BE EXACTLY TWO CLIST and that of the parameter member being read.
CHARACTERS
The ’errcode’ is an error code defined for the CLIST.
Explanation: The error code values and associated meanings are
found in TSO/E CLISTS.
These entries are used to complete SYS1.PARMLIB
member names and must be exactly two characters. The ’count’ value is the number of parameter values
The type is: already read.
APF AUTH This message is issued by the following installation
For the APF-authorized library list IEAAPFxx CLIST: DSNTINST
LINK LIST System action:
For the link list library concatenation
The CLIST will terminate.
LNKLSTxx
User response:
MVS SUBSYS
For the MVS subsystem list IEFSSNxx Be sure the parameter member and the CLIST are at
the same level.
This message is issued by the following installation
Problem determination:
CLIST: DSNTINST
If you suspect an error in the process, set
System action:
CONTROL(CONLIST) and invoke the CLIST in batch,
The CLIST will continue. so that the tracing can be sent with the error
documentation. You will also need the listing of the
User response:
CLIST and the parameter member being read.
Check your entries for these fields on the MVS panel
and make them exactly two characters. See job
370 Messages
DSNT456I • DSNT460I
The CLIST will continue, but will not produce edited User response:
jobs. The CLIST resets the incorrect value to ’max’.
Replace the value with a blank.
User response:
See message DSNT465I for the CLIST action. DSNT464I VALUES PERMITTED ARE values
Severity: Explanation:
8 (error) The variable named in message DSNT456I must be one
of the ’values’ listed.
DSNT461I THE BUFFER POOL MAXIMUM IS This message is issued by the following installation
LESS THAN THE MINIMUM VALUE CLIST: DSNTINST
ENTERED
System action:
Explanation:
The CLIST will continue, but will not produce edited
Buffer pool maximums must be greater than or equal to jobs.
the minimum value for the same buffer pool.
User response:
This message is issued by the following panel:
See message DSNT465I for the CLIST action.
DSNTIPE
Severity:
System action:
8 (error)
The panel is redisplayed and the cursor is placed on
the field in error.
DSNT465I VARIABLE varname SET TO value
User response:
Explanation:
Either reduce the minimum value or increase the
maximum value for the indicated buffer pool buffer. The variable, ’varname’, named in message DSNT456I
is in error. Possible reasons for the error are listed in
messages: DSNT458I, DSNT459I, DSNT460I, DSNT462I,
DSNT462I VALUE IS TOO LONG, MAXIMUM IS
DSNT463I, DSNT464I.
length CHARACTERS
This message is issued by the following installation
Explanation:
CLIST: DSNTINST
The variable named in message DSNT456I must be
System action:
shorter than its current value. The maximum length
allowed is ’length’. The CLIST will continue, but will not produce edited
jobs. The value has been set to the value shown.
This message is issued by the following installation
CLIST: DSNTINST User response:
System action: Specify the output data again on the primary install
panel. You will be able to see and change the value. If
The CLIST will continue, but will not produce edited
this value is not acceptable, change it, noting the limits.
jobs. The CLIST resets the value to the default value.
User response:
DSNT466I Output member cannot be DSNTIDSA,
See message DSNT465I for the CLIST action. DSNTIDVB or DSNTIDXA.
Severity: Explanation:
8 (error) | The OUTPUT MEMBER NAME field value must not be
| DSNTIDSA, DSNTIDVB, or DSNTIDXA. Members with
| these names are shipped with DB2 and must not be
DSNT463I DATA SHARING FIELD MUST BE
| overwritten.
BLANK IN UPDATE MODE.
This message is issued by the following panel:
Explanation:
DSNTIPA1
This field is not relevant in Update mode and must be
System action:
blank This message is issued by panel: DSNTIPA1
The panel is re-displayed and the cursor is placed on
System action:
the field in error.
The panel is redisplayed and the cursor is placed on t
User response:
field in error.
372 Messages
DSNT467I • DSNT471I
Change the value of the field under the cursor. System action:
The CLIST will return to the main install panel,
Important: If the member with the name that you
DSNTIPA1.
specify already exists, it is overwritten.
User response:
DSNT467I OUTPUT MEMBER SHOULD BEGIN Specify DSNTIDXA as the INPUT MEMBER NAME
WITH DSNTID and specify the current value for the migration
member.
Explanation:
Severity:
The output parameter member will be placed into
prefix.SDSNSAMP. This data set already has a large 8 (error)
number of members. To avoid replacing a member that
you need, a naming convention with prefix ’DSNTID’
DSNT470I WARNING, ONLY ONE VOLUME WAS
is strongly suggested. The suffixes ’VB’ and ’XA’ are
SPECIFIED
not allowed (see message DSNT466I).
Explanation:
This message is issued by the following installation
CLIST: DSNTINST Only one volume serial number was specified on the
install panel or CLIST invocation. This does not allow
System action:
adequate recovery or performance unless it is intended
The CLIST will continue. to be a single volume test system.
User response: This message is issued by the following installation
CLIST: DSNTINST
Specify a different name for the output member.
System action:
Severity:
The CLIST will continue.
4 (warning)
User response:
DSNT468I ERROR(S) ENCOUNTERED, OUTPUT If this subsystem is intended to be recoverable, more
IS BYPASSED than one volume is needed. Rerun the installation
tailoring process, specifying at least one more volume
Explanation:
on the DSNTIPA2 panel. If this is just a single volume
An error was detected earlier in this run. Because of test system, be sure that you specify a single copy of
the error, data set editing was not performed. the log data sets. The boot strap data sets are small and
not active, so that two are recommended even on a
This message is issued by the following installation single volume system.
CLIST: DSNTINST
Severity:
System action:
4 (warning)
The CLIST will continue, but will not produce edited
jobs.
DSNT471I BEGINNING PARAMETER INPUT
User response: MEMBER inmem
Correct the errors noted earlier, and specify the output Explanation:
prefix name again to produce the edited data.
The input parameter member, ’inmem’, is being read.
Severity: This data includes values for all of the installation
8 (error) parameters.
This message is issued by the following installation
DSNT469I INPUT PARAMETERS MUST BE READ CLIST: DSNTINST
BEFORE MIGRATION System action:
Explanation: The CLIST will continue.
The INPUT MEMBER NAME on panel DSNTIPA1 Severity:
must have a value to allow migration values to be read.
This is to permit the new values to be initialized. 0 (successful execution)
This message is issued by the following installation
CLIST: DSNTINST
DSNT472I WORK FILE DATABASE NAME DSNT475I CHECK count, varname, type, minval,
CANNOT START WITH DSNDB maxval, currentval
EXCEPT FOR DSNDB07
Explanation:
Explanation:
This message indicates the following:
The work file database name cannot start with the v The values read in or entered on the panels are being
characters DSNDB unless the name is DSNDB07. checked.
This message is issued by the following panel: v Values which use the K or M suffix are being
DSNTIPK translated to numbers.
System action: The count, the variable name, the data type, the
minimum value, the maximum value, and the current
The panel is redisplayed and the cursor is placed on
value are shown. This message occurs when the
the field in error.
CONTROL keyword requests a trace.
User response:
This message is issued by the following installation
Change the name so that it does not start with DSNDB.
CLIST: DSNTINST
System action:
DSNT473I BEGINNING CHECK PHASE
The CLIST will continue.
Explanation:
Severity:
This message indicates the following:
v The values entered on the panels are being checked. 0 (successful execution)
v Values which use the K or M suffix are being
translated to numbers. DSNT476I BEGINNING PARAMETER OUTPUT
MEMBER outmem
This message is issued by the following installation
Explanation:
CLIST: DSNTINST
The output parameter member named ’outmem’ is
System action:
being written. This data includes values for all the
The CLIST will continue. install parameters.
374 Messages
DSNT478I • DSNT482I
DSNT478I BEGINNING EDITED DATA SET DSNT481I DSNTINST data set DATA SET SIZE
OUTPUT MAY BE TOO SMALL
Explanation: Explanation:
The output jobs and data are being edited to tailor The DSNTINST CLIST encountered an arithmetic
them. Edited JCL output was requested and no severe overflow during calculation of this data set’s size.
errors were encountered.
System action:
This message is issued by the following installation
DSNTINST continues processing and uses 2147483647
CLIST: DSNTINST
for the result of the calculation that caused the
System action: overflow. Thus, the size of the data set might be too
small.
The CLIST will continue.
User response:
Severity:
Check the data set size in installation job DSNTIJIN. If
0 (successful execution)
it is too small, increase it.
User response:
This message is issued by the following installation
Change the location name to meet the allowable CLIST: DSNTINST
criteria.
System action:
The CLIST reduces the value of NUMCONDB so that
the calculated value for OPNDS is within the allowed
range. CLIST processing continues.
User response:
376 Messages
DSNT489I • DSNT492I
3330 57 3
DSNT490I SAMPLE DATA UNLOAD PROGRAM
3340 24 2
3350 120 4 Explanation:
3375 96 8
This is the header, indicating a normal start for the
3380 150 10 application program.
These size estimates are for system data only. They do DSNT491I TOO MANY TABLES ENTERED
not include: user data, archive logs, image copies, or (MAXIMUM OF 100 TABLES)
temporary work data sets other than the temporary
database. Explanation:
The CLIST is editing the data set and member Split the run into multiple runs, none with more than
dsname(member). The explanation is the type of data 100 tables.
being edited and has one of these values:
Problem determination:
INSTALL JCL
Check the application program input. Make sure there
Jobs that are edited and run as directed during
are no more than 100 tables.
the installation process.
MIGRATE JCL
DSNT492I SQL WARNING DURING SQL
Jobs that are edited and run as directed only
STATEMENT func, TABLE tttttttt
during the migration process.
Explanation:
FALL BACK JCL
A job that is only run as directed when falling The SQL statement may not be executed correctly. The
back to the previous release. function ’func’ may be PREPARE, OPEN, FETCH, or
CLOSE, indicating the type of SQL statement
RECOVERY JCL
encountering the error. Table ’tttttttt’ is the name of the
A job that is only run as directed during a
table or view being unloaded.
recovery process. It deletes the DB2 data sets.
System action:
SAMPLE JCL
Jobs that are edited and run during installation The request may not be executed correctly.
verification to add the sample application.
User response:
378 Messages
DSNT499I • DSNT501I
Check that the DSNTIAUL input statement is a The SELECT statement used to request a table unload
complete SQL statement, ending with a semicolon. contained one of the following:
v A SELECT clause other than ″SELECT * FROM″
User response:
v A FROM clause that does not contain exactly one
Notify the system programmer. table name
380 Messages
DSNT507I • DSNT511I
System action:
DSNT509I WARNING - MIGRATION INPUT
DSNTIAUL generates a LOAD statement containing the MEMBER LEVEL IS rel_ind. LEVEL
string ’TBLNAME’ for the table name. Some column prev_rel IS REQUIRED. RETURN TO
names may be blank. PANEL DSNTIPA1 TO CHANGE
MIGRATION INPUT MEMBER
User response:
Explanation:
Change the LOAD statement table name to the name of
a table with the indicated column descriptions. The migration input member you entered on panel
DSNTIPA1 contains incorrect release indicator ’rel_ind’.
Severity: It should contain the indicator for the prior release
4 (warning) (’prev_rel’). If your input member does not contain a
release indicator, ’rel_ind’ will be <null>. This probably
indicates that you are using a down-level member.
DSNT507I csect-name RECORD LENGTH NEEDED
IS GREATER THAN MAXIMUM This message is issued by the following installation
ALLOWED FOR TABLE table-name CLIST: DSNTINST
In order to unload table table-name, DB2 needs an The message is written to the screen, after display of
output data set with a record length greater than the panel DSNTIPA1.
system maximum of 32760 bytes. This occurs when the User response:
table to be unloaded is in a 32KB page table space and
contains a combination of long columns and a number Press ENTER to proceed to the next panel, and then
of date, time, or timestamp columns. PF3 to return to panel DSNTIPA1 in order to enter an
input member with the correct release indicator.
System action:
The application program is terminated. DSNT510I WARNING - INPUT MEMBER inmem
Severity: LEVEL IS rel_ind. LEVEL curr_rel IS
REQUIRED. RETURN TO PANEL
8 (error) DSNTIPA1 TO CHANGE INPUT
MEMBER
DSNT508I WARNING - NONSTANDARD JOB Explanation:
CARD (cardstat), NO JOB CARDS WILL
BE ADDED TO THE EDITED JOBS The input member ’inmem’ you entered in field 6 on
panel DSNTIPA1 contains incorrect release indicator
Explanation: ’rel_ind’. It should contain the indicator for the current
The job card you entered in field 3 of panel DSNTIPY release (’curr_rel’). If your input member does not
contains one or more of the following errors: contain a release indicator, ’rel_ind’ will be <null>. This
probably indicates that you are using a down-level
v Less than 7 characters (’cardstat’ = TOO SHORT)
member.
v ″//″ missing as the first 2 characters (’cardstat’ =
MISSING //) This message is issued by the following installation
CLIST: DSNTINST
v Missing the word ″JOB″ (’cardstat’ = MISSING
″JOB″TOKEN) System action:
The message is written to the screen, after display of
This message is issued by the following installation
panel DSNTIPA1.
CLIST: DSNTINST
User response:
System action:
Press ENTER to proceed to the next panel, and then
The message is written to the screen, after all panels are
PF3 to return to panel DSNTIPA1 in order to enter an
displayed and before any job editing. No JCL is added
input member with the correct release indicator.
to the edited jobs.
User response:
DSNT511I FIELDS 2 AND 5 MUST BE UNIQUE
You can continue with job editing and manually add FOR EACH NEW MEMBER
JCL to the edited jobs. Alternatively, you can repeat the INSTALLED
installation process and make corrections to the job
Explanation:
card entered on panel DSNTIPY.
This warning message is issued to remind you that the
IRLM SUBSYSTEM and IRLM PROC names must be
unique for each new member installed within a DB2 MEMBER NAME and WORK FILE DB NAME must be
data sharing group. The installation process does not unique for each new member installed within a DB2
check for uniqueness of these names within a group. data sharing group. The installation process does not
check for uniqueness of these names within a group.
This message is issued by the following panel:
DSNTIPI This message is issued by the following panel:
DSNTIPK
User response:
User response:
Enter unique names in these fields for each member of
a DB2 data sharing group. Enter unique names in these fields for each member of
a DB2 data sharing group.
DSNT512I DSNT512I WARNING: ENTER
UNIQUE NAMES FOR LUNAME AND DSNT515I FIELD 7 MUST BE UNIQUE FOR
LOCATION NAME EACH NEW MEMBER INSTALLED
Explanation: Explanation:
This warning message is issued to remind you that you This warning message is issued to remind you that the
must enter values for DB2 LOCATION NAME and DB2 MEMBER IDENTIFIER field on panel DSNTIPJ or the
NETWORK LUNAME fields. DSNZPARM NAME field on panel DSNTIPO must be
unique for each new member installed within a DB2
LUNAME is used to uniquely identify this DB2
data sharing group. The installation process does not
subsystem within the network and to uniquely identify
check for uniqueness of these values within a group.
trace records for correlation of accounting records. The
NETWORK LUNAME must be unique within the This message is issued by the following panels:
network. The installation process does not check for DSNTIPJ and DSNTIPO
uniqueness of this name within a data sharing group.
User response:
The LOCATION NAME must be unique within the
Enter unique values in these fields for each member of
network, but must be the same on all members within
a DB2 data sharing group.
a DB2 data sharing group.
This message is issued by the following panel:
DSNT516I FIELDS 1, 2, AND 4 MUST BE UNIQUE
DSNTIPR
FOR EACH NEW MEMBER
User response: INSTALLED
Enter unique names in these fields. Explanation:
This warning message is issued to remind you that the
DSNT513I FIELD 2 MUST BE UNIQUE FOR SUBSYSTEM NAME, COMMAND PREFIX, and
EACH NEW MEMBER INSTALLED SUBSYSTEM SEQUENCE fields must be unique for
each new member installed within a DB2 data sharing
Explanation:
group. The installation process does not check for
This warning message is issued to remind you that the uniqueness of these values within a group.
DB2 PROC NAME field on panel DSNTIPX or the
This message is issued by the following panel:
RESYNC PORT fieldon panel DSNTIP5 must be unique
DSNTIPM
for each new member installed within a DB2 data
sharing group. The installation process does not check User response:
for uniqueness of these values within a group.
Enter unique values in these fields for each member of
This message is issued by the following panels: a DB2 data sharing group.
DSNTIPX and DSNTIP5
User response: DSNT517I CHARACTERS 2-18 MUST BE A-Z, 0-9,
#, @, $, OR UNDERSCORE
Enter unique values in these fields for each member of
a DB2 data sharing group. Explanation:
WLM environment names that do not meet the
DSNT514I FIELDS 2 AND 3 MUST BE UNIQUE following criteria are not allowed. A WLM environment
FOR EACH NEW MEMBER name may contain up to eighteen characters. The first
INSTALLED character of a WLM environment name must either be
an alphabetic character (A-Z) or a standard alphabetic
Explanation:
extender (in the United States, the standard alphabetic
This warning message is issued to remind you that the extenders are ’#’, ’@’, ’$’). For characters two through
382 Messages
DSNT518I • DSNT527I
The panel is redisplayed, and the cursor is placed on The DSNHDECP module that is used by the DB2
the field with the error. precompiler contains an undefined (0) value for the
CCSID parameter that is indicated by ccsid-parm. The
User response: use of CCSIDs that are undefined will be disallowed by
Change the WLM environment name to meet the DB2 in the near future.
criteria described above. System action:
Processing continues.
DSNT518I THE VALUES FOR DRDA PORT,
SECURE PORT AND RESYNC PORT System programmer response:
CANNOT BE THE SAME
DSNHDECP needs to specify a valid, non-zero default
| Explanation: CCSID (Coded Character Set Identifier) for each of the
three encoding schemes that are supported: ASCII,
| You entered the same value for DRDA PORT, SECURE EBCDIC, and UNICODE. Processing character data
| PORT, and RESYNC PORT. The values for these fields with an undefined CCSID can lead to unpredictable
| must be different. results, including loss or corruption of the data. A
| This message is issued by the following panel: default CCSID must be defined even for encoding
| DSNTIP5 schemes not used on your DB2 system.
| Change either the DRDA PORT, SECURE PORT, or the Using the undefined CCSID for EBCDIC will be
| RESYNC PORT value so that they are different. disallowed in the near future by APAR PQ71079. Using
the undefined CCSID for ASCII will be disallowed in a
future release of DB2.
DSNT519I TO SPECIFY A DRDA PORT OR A
SECURE PORT (OR BOTH) YOU You need to take steps now to select an appropriate
MUST ALSO SPECIFY A RESYNC CCSID for each undefined CCSID, and to plan for and
PORT. schedule deployment of the updated DSNHDECPs on
your DB2 subsystem or data sharing system. See the
| Explanation: documentation provided with the PTF for APAR
| You entered a value for DRDA PORT or SECURE PORT PQ56697 for further guidance.
| but not for RESYNC PORT, or, you entered a value for Do not attempt to choose or change a CCSID without
| RESYNC PORT but did not enter a value for either guidance from IBM. Using the wrong CCSID can
| DRDA PORT or SECURE PORT. corrupt your data and render it unrecoverable.
| When DRDA PORT, SECURE PORT, or both contain a User response:
| non-blank, RESYNC PORT must also contain a
| non-blank. Notify the System Programmer.
installation module typically is located in the that all libraries in the STEPLIB and JOBLIB
SDSNEXIT library. concatenation for the job that invokes program-name are
APF authorized. If program-name is an external module
System action:
for a DB2 stored procedure or user-defined function,
DB2 startup is discontinued. ensure that the corresponding SYSIBM.SYSROUTINES
entry specifies a WLM-established address space.
System programmer response:
User response:
Check the STEPLIB, JOBLIB, or system linbklist
concatenation used in the DB2 address spaces. To Notify the system programmer.
ensure that the proper DSNHDECP module is used,
verify that the library that contains the DSNHDECP
DSNT531I schema.routine-name RECEIVED
module that is generated during installation precedes
SQLCODE sqlcode FROM SQL
the SDSNLOAD library that contains the DSNHDECP
STATEMENT sql-statement
module that was supplied by DB2.
Explanation:
User response:
When schema.routine-name executed sql-statement, DB2
Notify the System Programmer.
returned the SQL warning or error sql-code.
System action:
| DSNT528I USE PROTECTION MUST BE YES
| WHEN CACHE DYNAMIC SQL IS YES schema.routine-name terminates.
| Explanation: System programmer response:
| You entered NO for USE PROTECTION on panel Check the messages in the SYSPRINT data set for the
| DSNTIPP and YES for CACHE DYNAMIC SQL on stored procedures address space where routine
| panel DSNTIP8. You must enter YES for USE schema.routine-name runs. Message DSNT408I provides
| PROTECTION if CACHE DYNAMIC SQL is YES. specific information about the SQL warning or error.
Refer to Messages for more information on the SQL
| System action: error.
| The panel is redisplayed, and the cursor is placed on User response:
| the field that is in error.
Notify the system programmer.
| User response:
| If you see this message on panel DSNTIPP, enter a
DSNT532I schema.routine-name RECEIVED SAF
| value of YES for USE PROTECTION, or return to panel
RETURN CODE return-code FROM
| DSNTIP8 and enter NO for CACHE DYNAMIC SQL. If
RACROUTE COMMAND command.
| you see this message on panel DSNTIP8, enter a value
| of NO for CACHE DYNAMIC SQL, or go to panel Explanation:
| DSNTIPP and enter YES for USE PROTECTION.
When schema.routine-name executed RACROUTE
command command, the OS/390 System Authorization
DSNT530I program-name COULD NOT RUN Facility (SAF) returned an unexpected code return-code.
BECAUSE IT WAS NOT INVOKED
System action:
FROM AN APF-AUTHORIZED
LIBRARY schema.routine-name terminates.
Explanation: System programmer response:
program-name could not run for one of the following Refer to the z/OS Security Server RACROUTE Macro
reasons: Reference for more information about the SAF error.
v program-name was not invoked from an User response:
APF-authorized library.
v One or more libraries in the STEPLIB or JOBLIB Notify the system programmer.
concatenation the job that invokes program-name is
not APF-authorized. | DSNT533I schema.routine-name RECEIVED RETURN
System action: | CODE return-code FROM MVS SERVICE
| service-name, FUNCTION function-name.
The program terminates.
| Explanation:
System programmer response:
| schema.routine-name executed MVS service service-name
Ensure that program-name is link-edited with option | for function function-name and received an unexpected
AC(1) and resides in an APF-authorized library. Ensure | code return-code.
384 Messages
DSNT534I • DSNT543I
| System action:
DSNT541I WLM REFRESH REQUEST FAILED.
| schema.routine-name terminates. RESOURCE PROFILE
subsystem-name.WLM_REFRESH.wlm-
| System programmer response: environment-name IS UNDEFINED
| Refer to the discussion of service service-name in the Explanation:
| z/OS MVS Programming: Authorized Assembler Services
| Reference Volumes 1-4 for assistance with diagnosing the DB2 stored procedure WLM_REFRESH rejected a
| error. request to refresh WLM environment
wlm-environment-name because SAF resource profile
| User response: subsystem-name.WLM_REFRESH.wlm-environment-name
| Notify the system programmer. does not exist. WLM_REFRESH uses the resource
profile to verify whether the requestor is authorized to
refresh the WLM environment. The requestor was
| DSNT534I schema.routine-name RECEIVED AN connected to DB2 subsystem subsystem-name.
| ALERT FROM THE EXTENDED MCS
| CONSOLE: alert-type. System action:
v It contains characters that are not allowed for a SAF | System programmer response:
resource profile or for a DB2 subsystem name
| Examine the system log in the vicinity of the failed
System action: | refresh request and locate message identifier
| message-identifier. Use this message and related
The program terminates.
| messages to diagnose and correct the problem that is
System programmer response: | preventing the WLM refresh request.
v For the WLM_ENV_NAME parameter, specify a | User response:
non-null, non-blank argument. That argument must
conform to the rules for a SAF resource profile. See | Notify the system programmer.
Appendix A of z/OS Security Server RACF Auditor’s
Guide for more information. DSNT546I WLM REFRESH REQUEST
v For the SSID parameter, specify a null or blank CANCELLED BECAUSE AN
argument, or a value that conforms to the rules for a EXTENDED MCS CONSOLE COULD
DB2 subsystem name, as documented in the NOT BE ACTIVATED WITHIN n
Installation Guide. If you specify a null or blank value, SECONDS
DB2 determines the subsystem name.
Explanation:
User response:
DB2 stored procedure WLM_REFRESH rejected a
Notify the system programmer. request because it was unable to activate an extended
MCS console within the allowed period of n seconds.
The extended MCS console serializes the
DSNT544I SQLID sqlid IS UNDEFINED OR user IS
WLM_REFRESH requests and verifies that z/OS
NOT PERMITTED TO USE IT TO
completed the refresh request.
REFRESH wlm-environment-name
System action:
Explanation:
WLM_REFRESH rejects the refresh request.
DB2 stored procedure WLM_REFRESH rejected a
request by user id user to refresh WLM environment System programmer response:
wlm-environment-name using authorization id sqlid. The
This message indicates that WLM_REFRESH is busy
request was denied either because sqlid does not exist
processing one or more previous requests. Issue the
or because user is not permitted to use it.
DB2 command -DIS PROC(SYSPROC.WLM_REFRESH) and
System action: examine the ACTIVE, QUEUED, and MAXQUE values
to analyze whether or not a large backlog of calls to
WLM_REFRESH rejects the refresh request.
WLM_REFRESH currently exists. To give
System programmer response: WLM_REFRESH more time to respond to these
requests, you can increase the wait time by updating
If sqlid exists, permit user to use it. Otherwise, create the setting of the WAITLMT constant in the source
sqlid, give it READ access or higher on the appropriate code of the external module for WLM_REFRESH,
SAF resource profile (which resides in SAF resource DSNTWR. You need to prepare and bind DSNTWR
class DSNR and has the format again for the change to take effect.
ssid.WLM_REFRESH.wlm-environment-name), and permit
user to use it. User response:
386 Messages
DSNT550I • DSNT551I
System programmer response: Take one of the following actions according to reason:
This message indicates that your system is suppressing v For errors allocating, opening, or processing
one or more of the messages that can be generated in data-set-name, specific diagnostic messages are
response to the VARY WLM command. DSNTWR, the displayed by TSO. If you are not seeing these
external module for WLM_REFRESH, uses an extended messages, enter the command TSO PROFILE
MCS console (also named DSNTWR) to monitor WTPMSG in the command line of the current DB2
whether or not the VARY WLM command succeeded or install panel. Consult the appropriate MVS system
failed. Messages with the IDs IWM032I (refresh messages and codes manual for further information
complete) and IWM031I (refresh in progress) indicate about these messages.
that the refresh request processed successfully. So, for v If data-set-name is indicated as a non-partitioned data
WLM_REFRESH to function correctly, you need to set, verify that you have entered the intended data
ensure that the system does not suppress messages set name for CLIST output. If so, rename or delete
IWM031I and IWM032I. the existing data set.
This error can also occur if the specified WLM v Consult your system security administrator to obtain
environment requires more than n seconds to refresh. access to a protected data set.
In this case, you need to increase the wait time allowed v In the event of an unavailable data set, ask the
for the reply by updating the setting of the WAITLMT current user(s) to release it. Ask your system
constant in the source code of the external module for programmer to identify the user(s) if you are unable
WLM_REFRESH, DSNTWR. You need to prepare and to do so. Otherwise, try later when the data set has
bind DSNTWR again for the change to take effect. been freed.
User response:
DSNT551I csect-name bind-type FOR object-type =
Notify the system programmer.
object-name FAILED BECAUSE
CHARACTER CONVERSION FROM
DSNT550I ’data-set-name’ IS UNAVAILABLE FOR CCSID from-ccsid TO CCSID to-ccsid
CLIST OUTPUT BECAUSE reason FAILED WITH ERROR CODE error-code
FOR TABLE dbid.obid COLUMN
Explanation: column-number.
Data set data-set-name is required for output by the DB2 Explanation:
Install CLIST, but cannot be allocated for the reason
that is indicated by reason. Possible reasons are: A conversion error occurred during the conversion of a
v IT CANNOT BE ALLOCATED OR OPENED FOR string to a different coded character set.
OUTPUT bind-type
An error occurred during an allocate, open, or close identifies the type of bind subcommand:
operation on data-set-name. BIND, REBIND or FREE.
v ERROR PROCESSING REQUESTED DATA SET object-type
The request for data-set-name could not be processed. identifies the type of the object being bound:
v MEMBER SPECIFIED, BUT DATASET IS NOT PLAN or PACKAGE.
PARTITIONED object-name
data-set-name already exists, but is not a partitioned if ’object-type’ is PLAN, ’object-name’ is the
data set as required by the CLIST. name of the plan; otherwise, it is the name of
v PROTECTED DATASET the package in ’location.collection.package’
format
Your userid is not authorized to use data-set-name.
v VOLUME NOT ON SYSTEM from-ccsid
identifies the coded character set of the string
data-set-name is registered in the system catalog on a to be converted.
DASD or tape volume which is currently unmounted
or unavailable. to-ccsid
v UNAVAILABLE DATASET identifies the coded character set to which it
must be converted.
data-set-name is currently allocated by another user.
error-code
System action: indicates the type of error as defined as
The Install panel for specifying data-set-name is follows:
redisplayed. You cannot proceed to the next DB2 Install 8 Length exception (for example,
panel until the problem is resolved. expansion required for PC MIXED
User response: data exceeds the maximum length of
the string).
388 Messages
DSNT556I • DSNT570I
| This message may appear twice if specified-space must | v If page-type is 4K, then this message means that you
| be adjusted for both work file page types. | entered a non-zero value in the TEMP 4K SPACES
| field on DSNTIP9, the WORK FILE DATABASE
| panel, but entered a zero in the TEMP 4K TBL
| DSNT556I THE SUM OF TEMP 4K TBL SPACES
| SPACES field.
| AND TEMP 32K TBL SPACES
| CANNOT EXCEED 500 | v If page-type is 32K, then this message means that you
| entered a non-zero value in the TEMP 32K TBL
| Explanation: | SPACES field on DSNTIP9, but entered a zero in the
| This message appears on installation panel DSNTIP9 | TEMP 32K TBL SPACES field.
| when the sum of the values entered in the fields TEMP | System action:
| 4K TBL SPACES and TEMP 32K TBL SPACES exceeds
| 500. 500 is the maximum number of table spaces | Panel DSNTIP9 is displayed again, and the cursor is
| permitted in the work file database. | placed in the field in error.
| System action: | Programmer response:
| Panel DSNTIP9 is displayed again, and the cursor is | Enter a value of one or greater in the TEMP page-type
| placed in the TEMP 4K TBL SPACES field. | TBL SPACE field. If you do not want to create
| additional page-type work file table spaces as part of the
| User response: | migration process, then change the TEMP page-type
| Reduce the total number of table spaces specified in the | SPACES field value to zero.
| TEMP 4K TBL SPACES and TEMP 32K TBL SPACES
| field to 500 or less. DSNT570I WARNING: THIS APPLICATION HAS
SELECTED DSNTIAR TO PERFORM
| DSNT557I TEMP page-type TBL SPACES MUST BE SQL MESSAGE FORMATTING
| GREATER THAN 0 WHEN TEMP BECAUSE THE GET DIAGNOSTICS
| page-type SPACE IS GREATER THAN 0 SERVICE RETURNED AN
UNEXPECTED SQLCODE WHILE
| Explanation: FORMATTING MESSAGES FOR ONE
OR MORE SQL WARNING OR ERROR
| This message is issued for the reasons:
CONDITIONS. A DUMP OF THE
| v If page-type is 4K, then this message means that you SQLCA FOR THE GET DIAGNOSTICS
| entered a non-zero value in the TEMP 4K SPACE REQUEST FOLLOWS:
| field on DSNTIP9, the WORK FILE DATABASE
SQLCODE: sqlcode
| panel, but entered a zero in the TEMP 4K TBL
SQLSTATE: sqlstate
| SPACES field. SQLERRP: sqlerrp
| v If page-type is 32K, then this message means that you
| entered a non-zero value in the TEMP 32K SPACE SQLERRMC: sqlerrmc
| field on DSNTIP9, but entered a zero in the TEMP
| 32K TBL SPACES field. SQLERRD1: sqlerrd1
SQLERRD2: sqlerrd2
| System action: SQLERRD3: sqlerrd3
| Panel DSNTIP9 is displayed again, and the cursor is SQLERRD4: sqlerrd4
| placed in the field in error. SQLERRD5: sqlerrd5
SQLERRD6: sqlerrd6
| Programmer response:
| Enter a value of one or greater in the TEMP page-type SQLWARN0: w0 1: w1 2: w2
| TBL SPACES. If you do not want to create additional 3: w3 4: w4
| page-type work file table spaces as part of the migration 5: w5 6: w6
7: w7 8: w8
| process, then change the TEMP page-type SPACE value
9: w9 A:wA
| to zero.
The dump of the SQLCA is shown here on multiple
| DSNT558I TEMP page-type SPACE MUST BE lines because of space limitations. The empty lines here
| GREATER THAN 0 WHEN TEMP indicate the correct line breaks.
| page-type TBL SPACE IS GREATER
Explanation:
| THAN 0
The application program called the GET
| Explanation:
DIAGNOSTICS service to format one or more of the
| This message is issued for the reasons: warning or error conditions that occurred during the
processing of the current SQL statement that was input
into the system. However, the GET DIAGNOSTICS DIAGNOSTICS service to format one or more of the
service also returned warnings or errors, as indicated warning or error conditions that occurred during the
by the SQLCA dump. The application therefore will use processing of a ROWSET FETCH statement or a
the DSNTIAR message formatting service instead of non-atomic statement. However, the GET
GET DIAGNOSTICS. Attention: Messages formatted by DIAGNOSTICS request failed. Since the severity of the
DSNTIAR might contain truncated tokens. Also, when original warning or error conditions cannot be
multiple unexpected SQLCODEs were returned for the determined, the application terminates after reporting
current inputted SQL statement, DSNTIAR reports on this error.
the first one.
System action:
System action:
The application program is terminated.
The application program continues.
User response:
System programmer response:
Notify the system programmer.
See the problem determination section of this message.
Problem determination:
User response:
Use the SQLCA dump provided by DSNT571I to
Notify the system programmer. determine the cause of the problem. After the problem
is resolved, run the application again.
Problem determination:
Use the SQLCA dump provided by DSNT570I to
DSNT601I THE DESCRIPTOR FOR type name
determine the cause of the problem. After the problem
DOES NOT EXIST IN DBD01
is resolved, run the application again.
Explanation:
DSNT571I ERROR: THIS APPLICATION IS This message is issued for multiple-line WTO. The
TERMINATING BECAUSE THE GET database, table space, or index space ’name’ is in the
DIAGNOSTICS SERVICE RETURNED DB2 catalog but a descriptor for the object does not
AN UNEXPECTED SQLCODE WHILE exist in the DBD01 table space of database DSNDB01.
FORMATTING MESSAGES FOR ONE This error can be produced when one of the following
OR MORE SQL WARNING OR ERROR is true:
CONDITIONS FROM A ROWSET v The Version 9.1 catalog has been migrated into
FETCH STATEMENT OR A Version 8. There is an object in the Version 8 catalog
NON-ATOMIC STATEMENT. A DUMP but there is not a descriptor for the object in the
OF THE SQLCA FOR THE GET Version 8 directory (DBD01).
DIAGNOSTICS REQUEST FOLLOWS:
v The user did not completely restore the DBD01 table
SQLCODE: sqlcode space during a recovery process.
SQLSTATE: sqlstate
SQLERRP: sqlerrp v There is a DB2 logic error.
390 Messages
DSNT603I • DSNT700I
The database specified in the message is not stopped. System programmer response:
392 Messages
DSNT707I • DSNT710I
| SELECT CREATOR,NAME FROM SYSIBM.SYSTABLES WHERE | The START RLIMIT command was unable to use the
| NAME LIKE 'DSNRLMT | resource limit specification table DSNRLSTxx or
| DSNRLMTxx because index DSNARLxx or index
| If the query returns a row that matches | DSNMRLxx is not defined on that table.
| qualifier.table-name, refer to Part 2 of Diagnosis Guide and
| Reference for information on identifying and reporting
| System action:
| the problem. | The START RLIMIT command will not use the resource
| User response: | limit specification table that is associated with index
| index-name.
| See Operator Response.
| Operator response:
| Problem determination:
| Contact the system programmer.
| Collect the following diagnostic items:
| System programmer response:
| v Console output showing the failing START command
| v The output of the SELECT command. | Create the required index and reissue the START
| RLIMIT command.
User response:
| DSNT707I COLUMN column-name IN TABLE
| table-name IS INCORRECTLY DEFINED. See Operator Response.
| THE COLUMN DEFINITION IS
| attribute WITH LENGTH length AND | Problem determination:
| NULL ATTRIBUTE null-attribute. THE | Collect the console output showing the failing START
| COLUMN DEFINITION SHOULD BE | command messages.
| attribute WITH LENGTH length AND
| NULL ATTRIBUTE null-attribute. THE
| START RLIMIT COMMAND WILL DSNT709I new-table-name NOW ACTIVE.
| NOT USE THIS TABLE. old-table-name WAS OLD RESOURCE
LIMIT SPECIFICATION TABLE
| Explanation:
Explanation:
| The START RLIMIT command could not use table
| table-name because table table-name does not have the A START RLIMIT command was entered while the
| proper column definition for a resource limit facility was already active. The facility remains active
| specification table. and switches from using the old table name to the new
one.
| System action:
Operator response:
| The START RLIMIT command will not use table
| table-name for governing. Notify the system programmer.
governor is already active utilizing the specified table. Collect the console output showing the failing START
The command is ignored. command.
System action:
DSNT712I INDEX index-name IS NOT FOR TABLE
The governor continues to use table ’table-name’.
table-name. THE START RLIMIT
Operator response: COMMAND WILL NOT USE THIS
TABLE
Verify that the ID specified on the START RLIMIT
command was the one desired. If not, reenter the | Explanation:
command specifying the correct ID. If it is correct, no
| The START RLIMIT command was unable to use table
action is needed since the facility is already active and
| table-name because index index-name is not defined for
is using the desired table.
| the resource limit specification table table-name.
System programmer response:
| System action:
If you suspect an error in DB2, refer to Part 2 of
| The START RLIMIT command will not use table
Diagnosis Guide and Reference for information on
| table-name for governing.
identifying and reporting the problem.
| Operator response:
User response:
| Contact the system programmer.
See Operator Response.
| System programmer response:
Problem determination:
| Drop the existing DSNARLxx or DSNRLMTxx index
Collect the following diagnostic items:
| and create the correct index on the resource limit
v Console output from the system on which the job | specification table table-name.
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure. User response:
v Listing of SYS1.LOGREC data set, obtained by See Operator Response.
executing IFCEREP1.
Problem determination:
Collect the console output showing the failing START
DSNT711I COLUMN column-name IS MISSING
command messages.
IN TABLE table-name. SHOULD BE
DEFINED AS attribute WITH LENGTH
length AND NULL INDICATOR OF | DSNT713I INDEX index-name IS NOT UNIQUE.
null-attribute | THE START RLIMIT COMMAND
Explanation:
| WILL NOT USE THE ASSOCIATED
| TABLE
The START RLIMIT command has been entered but
failed because COLUMN ’column-name’ in resource
| Explanation:
limit specification table ’table-name’ is not defined. The | The START RLIMIT command has been entered but
proper column definition is given in the message. | failed because INDEX index-name in the resource limit
System action:
| specification table is not defined as a UNIQUE index.
Operator response:
| The START RLIMIT command will not use the resource
| limit specification table associated with index
Verify that the 1 or 2 characters following DSNRLST | index-name for governing.
are what was intended to be entered as the ID on the
START RLIMIT command. If not, reenter the command
| Operator response:
specifying the proper ID. If the ID appears to be | Contact the system programmer.
correct, contact the system programmer.
| System programmer response:
System programmer response:
| Drop INDEXindex-name and create it as a unique index.
TABLE ’table-name’ does not have COLUMN
’column-name’ defined. Use ALTER TABLE to define | User response:
the column as specified in the message. | See Operator Response.
User response: | Problem determination:
See Operator Response. | Collect the console output showing the failing START
Problem determination: | command.
394 Messages
DSNT714I • DSNT716E
| The START RLIMIT command will not use the resource This is an I/O error. Investigate the problem indicated
| limit specification table associated with index by the reason code and preceding messages. If you
| index-name for governing. suspect an error in DB2, refer to Part 2 of Diagnosis
Guide and Reference for information on identifying and
| Operator response: reporting the problem.
| Contact the system programmer. Problem determination:
| System programmer response: Collect the following diagnostic items:
| Drop index index-name and create it with the correct v Console output from the system on which the job
| definition. Refer to Part 5 (Volume 2) of Administration was run, and a listing of the SYSLOG data set for the
| Guide for an example of how to define an index on a period of time spanning the failure.
| resource limit specification table. v Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
| User response:
| Contact the system programmer.
DSNT716E AN ERROR OCCURRED
| Problem determination: ESTABLISHING A RESOURCE LIMIT
FOR CORRELATION-ID correlation-id,
| Collect the console output showing the START
CONNECTION-ID connection-id,
| command messages.
LUW-ID luw-id =token. limit WILL BE
USED AS THE LIMIT
DSNT715E ERROR reason-code READING
Explanation:
table-name. default WILL BE
RESOURCE LIMIT FOR An internal error occurred while the resource limit for
CORRELATION-ID correlation-id, the specified requester was being established. The
CONNECTION-ID connection-id, ’limit’ is determined from the default specified in the
LUW-ID luw-id =token system parameters. This default can be:
Explanation: NOLIMIT
No limit applies.
An error occurred while the resource limit specification
table ’table-name’ was being read. The limit is NORUN
determined from the default specified in the system Zero time limit.
parameters. This default can be:
integer The limit to be used.
NOLIMIT
No limit applies. A logical-unit-of-work identifier (LUW-ID) of ’*’
indicates that the thread does not have a LUW-ID. If
NORUN
the LUW-ID is not an ’*’, the value is a
Zero time limit.
logical-unit-of-work-id that is assigned to the thread
integer The limit to be used. followed by an ’=’ sign and a token value, which can
be used in place of logical-unit-of-work-id in any DB2
The reason code that defines the read error is included command that accepts logical-unit-of-work-id as input.
in the message text, as are the ’connection-ID’, Correlation IDs beginning with ’0nn’, where ’nn’ is a
’correlation-ID’, and the logical-unit-of-work identifier number from 01 to 28, identify system agents.
(LUW-ID) of the thread. An LUW-ID of an ’*’ indicates
System action:
that the thread does not have a LUW-ID. If the LUW-ID
is not an ’*’, the value is a logical-unit-of-work-id that Processing continues using the system-defined default.
is assigned to the thread followed by an ’=’ sign and a
Operator response:
token value, which can be used in place of
logical-unit-of-work-id in any DB2 command that Notify the system programmer.
396 Messages
DSNT722I • DSNT724E
because it contains an active resource limit specification (START RLIMIT,ID=xx). In a DB2 data sharing
table. environment, you must either stop the resource limit
facility on all members of the DB2 data sharing group
System action:
or switch it to use a resource limit specification table
The START DATABASE command is ignored. that does not have an index in the index space.
Operator response:
DSNT724E csect-name ERROR reason-code IN
If the database must be started with access (UT), either READING RESOURCE LIMIT
stop the resource limit facility (STOP RLIMIT), or SPECIFICATION TABLE table-name.
switch it to use a resource limit specification table that FOR AUTHORIZATION ID auth-id
is not in the database (START RLIMIT,ID=xx). In a DB2 RUNNING THREAD WITH
data sharing environment, you must either stop the CORRELATION ID correlation-id,
resource limit facility on all members of the DB2 data CONNECTION ID connection-id, AND
sharing group or switch it to use a resource limit LUWID luw-id, USE OF operation-name IS
specification table that is not in the database. NOT GOVERNED.
Explanation:
DSNT722I csect-name TABLE SPACE name
CANNOT BE STARTED WITH ACCESS An error occurred reading resource limit specification
(UT). IT CONTAINS AN ACTIVE table table-name. auth-id is assumed to be allowed to
RESOURCE LIMIT SPECIFICATION perform operation-name. operation-name is BIND or
TABLE PARALLEL PROCESSING.
If the table space must be started with access (UT), System action:
either stop the resource limit facility (STOP RLIMIT), or If the operation-name is BIND, processing continues if
switch it to use a resource limit specification table that the auth-id is authorized to perform the BIND. If the
is not in the table space (START RLIMIT,ID=xx). In a operation-name is PARALLEL PROCESSING, query
DB2 data sharing environment, you must either stop parallelism is not disabled and can be used if the value
the resource limit facility on all members of the DB2 of the CURRENT DEGREE special register is ’ANY’. If
data sharing group or switch it to use a resource limit the operation-name is PREDGOV, the active RLF
specification table that is not in the table space. (Resource Limit Facility) assumes that the RLST table
does not contain a row for user-predicted ASUTIME,
DSNT723I csect-name INDEX SPACE name and the execution of the SQL statement continues as
CANNOT BE STARTED WITH ACCESS normal.
(UT). IT IS DEFINED ON AN ACTIVE Operator response:
RESOURCE LIMIT SPECIFICATION
TABLE Notify the system programmer.
Index space name cannot be started with access (UT) Investigate the problem indicated by the reason code
because it contains an index on an active resource limit and preceding messages. If you suspect an error in
specification table. DB2, refer to Part 2 of Diagnosis Guide and Reference for
information on identifying and reporting the problem.
System action:
User response:
The START DATABASE command is ignored.
Notify the system programmer.
Operator response:
Problem determination:
If the index space must be started with access (UT),
either stop the resource limit facility (STOP RLIMIT), or Collect the following diagnostic items:
switch it to use a different resource limit specification
table that does not have an index in the index space
Operator response:
| The START RLIMIT command will use the existing
| resource limit specification table. The name of that table
Notify the system programmer. | is in a DSNT704I message.
System programmer response: | System programmer response:
If you suspect an error in DB2, refer to Part 2 of | To use table-name to determine resource limits, create
Diagnosis Guide and Reference for information on | table-name, and issue the -START RLIMIT command
identifying and reporting the problem. | again.
User response:
DSNT735I object name CANNOT BE STARTED. IT
Notify the system programmer.
CONTAINS OR IS DEFINED ON THE
Problem determination: DDL REGISTRATION TABLE(S)
398 Messages
DSNT736I • DSNT744I
400 Messages
DSNT750I • DSNT753I
| You have issued a START PROFILE command to | Investigate the problem indicated by the reason code. If
| activate the profile function, but the column | you suspect an error in DB2, refer to Part 2 of Diagnosis
| column-name in the table creator-name.table-name is | Guide and Reference for information on identifying and
| missing. The reported table is an optional table, and | reporting the problem.
| will not be used by the START PROFILE command.
| The information that was intended to be reported in | DSNT753I csect-name DISPLAY PROFILE REPORT
| this table will not be available. | FOLLOWS: STATUS=status
| System action: | TIMESTAMP=YYYY-MM-DD-
| HH.MN.SS.NNNNNN PUSHOUT=current
| The START PROFILE command continues and the | OUT OF max DISPLAY PROFILE
| offending table will not be used. | REPORT COMPLETE
| System programmer response: | Explanation:
| Make sure the table is created correctly with the proper | You have issued a DISPLAY PROFILE command, which
| columns. Then, run the command again. You can | produced an informational message. This message
| ignore this message if the table is an optional table and | indicates the profiling status, the timestamp when it
| continue the profile function. | started, and the status of push-out limits.
| status The profiling status that’s value can be either
| DSNT751I csect-name THE COLUMN column-name | one of ON, OFF, SUSPENDED, STARTING, or
| IS MISSING IN TABLE | STOPPING.
| creator-name.table-name. IT SHOULD BE
| DEFINED AS data-type WITH LENGTH | ON Profiling is active.
| length AND NULL ATTRIBUTE OF attr. | OFF Profiling is inactive.
| THE START PROFILE COMMAND
| FAILED | SUSPENDED
| Profiling was active, but is suspended
| Explanation: | now due to some error conditions.
| You have issued a START PROFILE command to | Some error conditions might be the
| activate the profile function, but the column | maximum push-out limit has been
| column-name in the table creator-name.table-name is | reached, the table space is full, and
| missing. The START PROFILE command failed. | other similar conditions.
| If the status is either OFF, STARTING, or STOPPING IRLM failed to connect to the IRLM data sharing
| then the TIMESTAMP and PUSHOUT lines will not be group. This message accompanies abend reason code
| reported 00E30806.
| System action: System action:
| The system issues the message above. No other actions DB2 terminates abnormally with reason code 00E30806.
| are taken.
System programmer response:
| System programmer response:
Some possible reasons why IRLM could not connect to
| Take the appropriate action for your system based on its data sharing group are:
| the options below: v The lock structure is not properly defined in the
| ON Issue STOP PROFILE or no do not take any active MVS CFRM administrative policy. The lock
| action. structure name is a concatenation of the DB2 data
sharing group name and the string ’LOCK1’
| OFF Issue START PROFILE or do not take any separated by an underscore (_). For example, if the
| action. DB2 data sharing group name is DSNCAT,
| STARTING or STOPPING DSNCAT_LOCK1 is the lock structure name.
| Wait until the command execution is complete. Ensure that the lock structure is properly defined in
the active CFRM policy. The name of the lock
| SUSPENDED structure that IRLM attempted to access is given in
| Investigate and correct the problem causing this message. IRLM issues message DXR138E to
| the suspension of profiling activities. indicate that the lock structure definition could not
| Stop or restart profiling again when be accessed in the active CFRM policy.
| appropriate. v IRLM could not connect the lock structure. The
reason for the connect failure is given in IRLM
message DXR135E.
| DSNT758I csect-name ATTEMPT TO USE NEW
| COMMAND OR OPTION new-command v IRLM could not join its data sharing group. The
| BEFORE NEW FUNCTION MODE reason for the join failure is given in IRLM message
DXR134E.
| Explanation:
v IRLM joined the wrong group. The set of IRLMs that
| This message is issued when you use a new command are connected to a given lock structure must all be
| or command option new-command that is introduced in members of the same group. Ensure that the GROUP
| DB2 for z/OS Version 9.1 before enabling new-function parameter is correctly specified in the IRLM startup
| mode. You cannot use this command before enabling procedure. If you give an incorrect group name,
| new-function mode. IRLM connects the lock structure, and then times out
waiting for responses from other connectors. IRLM
| new-command
issues message DXR133I for the timeout.
| The new command or command-option that
| can only be used after new-function mode had
| been enabled. DSNT801I ACTION A (ADD) DOES NOT ALLOW
GENERIC DISPLAY (% IN DATA
| System action:
FIELD).
| This message is issued after you attempt to use a new
Explanation:
| command or command-option new command before
| new-function mode has been enabled. You have to specify a specific data item in the DATA
field.
| System programmer response:
This message is issued by the following panel:
| To use the new commands or command option
DSN8SSH
| new-command introduced in this release of DB2, then
| enable new-function mode. System action:
The panel is redisplayed, and the cursor is placed on
DSNT800I csect-name DB2 CANNOT IDENTIFY TO the field in error.
IRLM. IRLM CANNOT CONNECT TO
User response:
ITS DATA SHARING GROUP. THE
LOCK STRUCTURE THAT IRLM Enter specific data in the DATA field.
ATTEMPTED TO ACCESS WAS
strname.
Explanation:
402 Messages
DSNT802I • DSNT806I
DSNT802I ONLY ACTION D (DISPLAY) IS DSNT805I NAME TYPE PART STATUS LPL
ALLOWED FOR DEPARTMENT PAGES
STRUCTURE.
Explanation:
Explanation:
This message indicates the beginning of a set of
You cannot add, update, or erase a department messages used to display information as a result of a
structure. You can only display it. DISPLAY DATABASE command when the keyword
LPL is specified. This message contains the headings of
This message is issued by the following panel:
the display. (The message appears in one continuous
DSN8SSH
line across the screen, not as shown above.) This
System action: message is always followed by one or more DSNT806I
messages containing the column data. Refer to message
The panel is redisplayed, and the cursor is placed on DSNT806I for a description of the data these headings
the field in error. identify.
User response:
Change the ACTION field to D, or change the OBJECT DSNT806I space type part status LPL pages
field to DE or EM. Explanation:
This message contains the display information resulting
DSNT803I csect-name DB2 CANNOT IDENTIFY TO from a DISPLAY DATABASE command when the
IRLM. THE REQUESTED FUNCTION keyword LPL is specified. It contains the column data
LEVEL IS NOT SUPPORTED. describing the status of a table space or index space in
Explanation: the database listed in the preceding DSNT362I message.
This message is always preceded by its column
An attempt was made to identify to an IRLM that does headings message DSNT805I. The message number for
not support the level of function DB2 needs. This this message is not displayed.
message accompanies abend reason code 00E30800.
The message fields have the following meanings:
System action:
space The table space name or index space name.
DB2 terminates abnormally with reason code 00E30800.
type TS for a table space, IX for an index space, LS
System programmer response: for a LOB table space.
Ensure that the STEPLIB statement in your IRLM part The partition number. It is blank for a
startup procedure is referencing the correct IRLM code nonpartitioned table space or index space. For
library and that IRLM is at the appropriate level of nonpartitioned secondary indexes, it is the
maintenance. logical partition number preceded by the
character L (for example, L0001). For
DSNT804I csect-name THERE ARE MODIFY data-partitioned secondary indexes, the prefix
LOCKS OWNED BY THIS DB2 THAT for this value will be the character D (for
HAVE BEEN RETAINED example, D0001).
condition between the row in the base UTRO Although the table space or index
table and the LOB in the LOB table space is started as RW, a utility is in
space. process and only RO access is
allowed.
CHKP The table space is in check pending
status. UTRW The table space or index space is
started as RW and a utility is in
COPY An image copy is required for this
process.
object (table space or data set within
this table space). STOP is also UTUT Although the table space or index
displayed. If the image copy is space is started as RW, a utility is in
required because DB2 encountered a process and only UT access is
problem during RESTART, STOPE is allowed.
displayed instead of STOP.
LPL pages
GRECP The pages in the specified space that are
The object (a table space, a table unavailable because of logical or physical
space partition, index space, or index damage.
space partition) is marked recovery
pending because of the failure of a
DSNT807I csect-name IRLM PURGE OF RETAINED
group buffer pool. This status value
LOCKS FAILED. RETURN CODE =
appears only on spaces. It does not
retcode SUB-CODE = subcode
apply to databases. See for
information about resolving this Explanation:
restricted status.
DB2 issued a PURGE request to IRLM to purge
LPL The object has pages or ranges of retained locks for this DB2. The PURGE request did not
pages that are unavailable because of complete successfully. This message shows the return
logical or physical damage. code and subcode from IRLM.
LSTOP The logical partition is stopped. System action:
RECP The table space or index space is in DB2 abends with reason code 00E30808. Restart
recovery pending status. The member processing is terminated.
must be restarted to restore full access
to the data. For logical partitions, the System programmer response:
RECP status can appear as RBDP*. Refer to the IRLM codes.
RBDP* indicates that the entire index is
inaccessible to SQL applications, DSNT809E csect-name FEEDBACK FROM IRLM
however only the logical partition IDENTIFY INDICATED IRLM DID
needs to be recovered. NOT CONNECT TO THE LOCK
RO The database, table space, or index STRUCTURE
space is started for read activity only. Explanation:
RW The database, table space, or index DB2 identified to IRLM, but cannot continue because
space is started for read and write IRLM did not connect to the lock structure. Global
activity. locking is ignored. This message accompanies abend
STOP The database, table space, or index reason code 00E30809.
space is stopped. System action:
STOPE DB2 implicitly stopped the table DB2 abnormally terminates with reason code 00E30809.
space or index space because of an
internal inconsistency. A DSNT500I or System programmer response:
DSNT501I message is issued at time This condition happens if you are running DB2 in data
of error detection to indicate the sharing mode, but the associated IRLM is running with
inconsistency. local scope (SCOPE=LOCAL in the IRLM startup
STOPP A stop is pending or is in process for procedure). If you are running DB2 in data sharing
this database, table space, or index mode, ensure that the associated IRLM startup
space. procedure specifies SCOPE=GLOBAL. Conversely, if
you are not running DB2 in data sharing mode, ensure
UT The database, table space, or index that the associated IRLM startup procedure specifies
space is started for utility processing SCOPE=LOCAL.
only.
404 Messages
DSNT810E • DSNT815I
406 Messages
Chapter 16. DSNU messages
Message identifiers that begin with DSNU communicate information about utilities.
The severity values shown for the utility messages that follow are returned as the
job-step condition code from the job step during which the message is issued. If
additional messages having higher severity values are issued during the same job
step, the higher value is reflected as the job-step condition code.
| The output of DSNU messages that are sent to SYSPRINT will have a timestamp
| after the message number. This timestamp uses the Julian date format of
| HH:MM:SS:TT.
408 Messages
DSNU007I • DSNU012I
Severity: 8 (error)
8 (error)
DSNU016I csect-name UTILITY BATCH MEMORY
EXECUTION ABENDED,
DSNU013I csect-name JOB WITH DUPLICATE
REASON=X0rrr cause
UTILID FOUND IN SYSUTIL
Explanation:
Explanation:
The utility batch address space has abended. If X’0rrr’
| An entry with the same qualifier was found in the is four characters in length (that is, X’00C1’), the abend
| SYSIBM.SYSUTIL table for a job that was previously was a system X’rrr’ abend. If X’0rrr’ is four characters
| terminated. in length and system abend X’000’ was indicated, a
System action: user abend was issued. If X’0rrr’ is eight characters in
length, the abend was a system X’04E’ abend, and
The utility job is abended with reason code X’0rrr’ is an abend reason code.
X’00E40018’.
If the value of general register 2 is not zero, then cause
User response: will contain CAUSE=X’cccccccc’ where X’cccccccc’ is the
| If you issued the job in order to re-run the utility, then value of general register 2. This information is for
| use the -TERM utility command to delete the entry that service purposes only.
| has the same qualifier from the SYSIBM.SYSUTIL table. System action:
| If the job has no relation to the SYSIBM.SYSUTIL entry
| job, then use a new qualifier. The utility job is abended. The SYSIBM.SYSUTIL entry
for the job is retained in the SYSUTIL table.
410 Messages
DSNU018I • DSNU021I
User response: The utility proceeds along one or the following paths:
Correct the indicated parameter on the EXEC DD If the data set was an incremental image copy data set,
statement, and resubmit the job. the utility proceeds as if it and any later incremental
image copies did not exist.
Problem determination:
If the data set was a full image copy data set, the utility
Refer to Utility Guide and Reference for the parameter attempts to use the most recent prior full image copy
specifications. data set.
Severity: If the data set is used by the COPYTOCOPY utility, and
8 (error) the utility job step includes an OPTIONS control
statement with the EVENT(ITEMERROR,SKIP) option,
COPYTOCOPY processes the next item in the list.
DSNU025I csect-name INVALID RESTART
PARAMETER (restart) The allocation failure may create other problems that
will cause the utility to fail. This is indicated by other
Explanation: messages.
Only the following values may be specified for the System programmer response:
restart parameter: NO or null, CURRENT, or PHASE.
If the utility fails because of the allocation error (as
System action: shown by a subsequent message), correct the error, then
The utility is not run by the stored procedure. resubmit the job.
Correct and re-run. If the job fails, contact the system programmer.
Correct the job control language and resubmit the job. X’00E40070’. The utility job step is left in the stopped
state.
User response:
Operator response:
If the ddname is one you submitted, review and correct
it. If the ddname was not provided by you but by the Notify the user or system programmer.
system, consult the system programmer.
System programmer response:
Correct the data set definition, or add DCB information
DSNU037I csect-name - RECFM=U FOR DDNAME
to the JCL. Do a RESTART(PHASE) of the stopped
dddddddd
utility, or resubmit the job after issuing a -TERM
Explanation: UTILITY command for the stopped utility.
A data set to be used by the utility has an undefined User response:
record format RECFM=U. All data sets must be fixed or
If the DDNAME is for a data set that you submitted,
variable, blocked or unblocked.
review and correct it. It might be necessary to provide
System action: a valid LRECL in the DCB parameter in the JCL. If the
DDNAME was not provided by you but by the system,
The utility job is abended with a reason code of
consult the system programmer.
X’00E40070’. The utility job step is in the stopped state.
Operator response:
DSNU040I csect-name ERROR ACCESSING
Notify the system programmer. DDNAME ddname, DECB=Xhex string
Ensure that no data sets involved in the utility job have An error has occurred during BSAM access of a utility
RECFM=U. Resubmit the job after ending the stopped temporary file identified by ’ddname’. The DECB
utility by the TERM UTILITY command, or do a indicating the error is given as a hexadecimal string.
RESTART(PHASE) of the stopped utility.
System action:
The executing utility issues an X’04E’ abend with abend
DSNU038I csect-name BLOCK SIZE FOR DCB,
reason code ’00E40071’ following this message.
DDNAME dddddddd, IS TOO SMALL,
MUST BE AT LEAST bbbbb BYTES Operator response:
Explanation: An operator with SYSOPR authority can issue the
-TERM UTILITY command to release the resources
The data set with DDNAME ’dddddddd’ has a block
claimed by the stopped utility (this may not be
size that is too small to accommodate a record that
necessary).
needs to be written.
User response:
System action:
Refer to the information given in the Problem
The utility job is abended with a reason code of
Determination section of this message. Correct the
X’00E40079’. The utility job step is left in the stopped
problem. Either issue the -TERM command to
state.
terminate the utility job and resubmit it, or specify the
User response: RESTART parameter and resubmit it.
Delete the data set in error. Change the JCL so that the Problem determination:
block size for the data set with DDNAME ’dddddddd’
The DECB provided contains the ECB in the first four
is at least ’bbbbb’ bytes. Resubmit the utility job with
bytes. The first byte of the ECB contains status bits that
the RESTART(PHASE) option.
indicate the cause of the error. Refer to the appropriate
MVS publication for the meaning of the status bits.
DSNU039I csect-name - LRECL=0 FOR DDNAME
dddddddd
DSNU041I csect-name INVALID CONCATENATED
Explanation: DATA SET FOR DDNAME dddddddd
414 Messages
DSNU042I • DSNU047I
The utility job step is in the stopped state. cases, error messages from MVS sort identify the
problem and the dump is not needed. If sort is unable
Operator response:
to open the UTPRINT data set, only the message and
Notify the system programmer. the abend are provided. For example, if the UTPRINT
DD statement is omitted, correct the problem with
System programmer response: UTPRINT, and resubmit the job.
Remove the concatenated data sets from the data set
with DDNAME ’dddddddd’. Resubmit the job after DSNU046I csect-name UTILITY STATEMENT IS
ending the stopped utility with the TERM UTILITY TOO LONG OR TOO COMPLEX
command, or restart the utility at the beginning of the
stopped phase by using RESTART(PHASE). Explanation:
The utility command and associated control statements
DSNU042I csect-name SORT PHASE STATISTICS. have caused internal fields to exceed DB2 subsystem
NUMBER OF RECORDS=n ELAPSED limits.
TIME=hh/mm/ss
System action:
Explanation:
Utility processing is not initiated.
This message provides statistics on the SORT phase of
User response:
a utility. The number of records sorted, ’n’, and the
duration of the SORT phase in hours, minutes, and Reduce the size or complexity of the utility statement
seconds are provided. where possible. For example, a LOAD into several
tables may be broken up into a separate load statement
System action:
for each table or the size of comparison fields for
The system continues to process normally. ’when’, ’continueif’, and ’nullif’ operands may be
reduced in size.
Severity:
Problem determination:
0 (informational)
Refer to Utility Guide and Reference for correct operand
definitions.
DSNU044I csect-name ERROR FROM SORT
COMPONENT RC=n, UTILITY Severity:
STOPPED
8 (error)
Explanation:
A nonzero return code ’n’ was returned from an MVS DSNU047I csect-name A REQUIRED DD CARD OR
sort. Error messages from sort are printed on the TEMPLATE IS MISSING.
UTPRINT data set. NAME=missing-dd
The executing utility job is placed in the stopped state. The DB2 utility being executed requires a data set to
continue processing. The DDNAME or TEMPLATE
Operator response: name for the missing data set is provided.
An operator with SYSOPR authority can issue the System action:
-TERM UTILITY command to release the resources
claimed by the stopped utility (this may not be Utility processing terminates.
necessary).
Operator response:
User response:
Notify the system programmer.
Determine the cause of the error. If the error can be
System programmer response:
corrected, the utility may be restarted from the
beginning of the sort phase by using the Correct the JCL to include the indicated DD statement
RESTART(PHASE) option. If the error is such that the or add a TEMPLATE control statement. Refer to Utility
utility cannot complete, the -TERM command should Guide and Reference for information about required dd
be issued to remove the stopped utility from the statements.
system. The -TERM utility option should rarely be
Severity:
exercised when the stopped utility is REORG.
8 (error)
Problem determination:
This abend is accompanied by abend reason code
X’00E40005’, and an SVC dump is requested. In most
416 Messages
DSNU054I • DSNU058I
The error is sufficient to terminate further processing of Remove the object from the RECOVERY PENDING
the utility job step. The utility job step is terminated, STATE by using either LOAD REPLACE, RECOVER, or
and resources are released to their prior state. REPAIR against the object. Resubmit the job.
DSNU059I csect-name utility-name UTILITY NOT DSNU061I csect-name USER userid NOT
ALLOWED TO RUN ON A ROSHARE AUTHORIZED, UTILID=utilid
READ DATABASE
Explanation:
Explanation:
The named user issued a utility command and was not
An attempt was made to execute a utility on a authorized to do so.
ROSHARE READ database. Only the RUNSTATS,
The -TERM UTILITY command can only be issued by:
DIAGNOSE, and REPAIR DBD utilities are allowed to
run on read-only shared databases. v The submitter of the utility job.
v Users with SYSOPR, SYSADM, or SYSCTRL
System action:
authority.
Utility processing is not initiated. v Users with DBADM, DBCTRL, or DBMAINT
User response: authority over every database used by the utility.
Even for users with sufficient database authority, the
Resubmit the utility job on the owning system, if
TERM UTILITY command will fail in these
necessary.
situations:
Severity: – The user issued the command before the utility
8 (error) determined what databases it would access.
– The utility job included the DIAGNOSE, REPORT,
or STOSPACE utility. Those utilities must be
DSNU060I csect-name USER userid NOT terminated by the submitter of the job or by a
AUTHORIZED FOR util-name UTILITY holder of SYSOPR, SYSCTRL, or SYSADM
ON DATABASE dbase-name authority.
Explanation:
Any user can issue a -DISPLAY UTILITY command.
User userid attempted to execute a utility util-name
against an object in database dbase-name. The user was System action:
not authorized to execute utilities for database
The -TERM UTILITY request for utility identifier utilid
dbase-name, the user’s authorization did not include this
is rejected.
utility, or the user’s authorization did not have a valid
seclabel. User response:
System action: Take the appropriate action:
Utility processing is not initiated. v Wait to allow the utility to identify the databases it
will access; then reissue the command.
System programmer response:
v Obtain the required authorization and reissue the
Determine why the user was denied access. Either the command.
authorization should be corrected, or another v Have another user with proper authorization issue
authorized user should invoke the utility. When the command.
LISTDEF was used, it can be ignored if the user wanted
to execute utility on the object(s) he or she owns in
implicit database with owner privilege. DSNU062I csect-name util-name UTILITY MAY NOT
BE RUN ON OBJECT qualifier.object-name
User response:
Explanation:
| Ensure that the correct database was specified. If this
| operation involves a table with multilevel security with An attempt was made to execute utility ’util-name’
| row granularity, then you need to have a valid security against object ’qualifier.object-name’. This is not
| label to execute this utility. allowed. The named object cannot be processed by the
named DB2 utility.
Problem determination:
System action:
The following catalog tables can be examined to
determine who has proper authority: The utility job is terminated.
SYSIBM.SYSUSERAUTH, SYSIBM.SYSDBAUTH, User response:
SYSIBM.SYSRESAUTH, SYSIBM.SYSINDEXES
(ownership), or SYSIBM.SYSTABLESPACE (ownership). Remove the invalid utility control statements and
resubmit the job.
Severity:
Severity:
12 (severe error)
8 (error)
418 Messages
DSNU063I • DSNU068I
DSNU063I csect-name utility-name UTILITY NOT DSNU065I csect-name UTILITY NOT ALLOWED
ALLOWED AGAINST AN OBJECT IN AGAINST A WORK FILE
REBUILD PENDING STATE
Explanation:
Explanation:
An attempt has been made to execute a utility against
An attempt has been made to execute a utility against database DSNDB07. Utilities are not allowed against
an object that is in REBUILD PENDING STATE. work files.
CHECK, COPY, MODIFY, LOAD, QUIESCE, REORG,
System action:
and RUNSTAT are not allowed.
Execution of the utility job is stopped.
System action:
User response:
Utility processing is not initiated.
Remove the invalid utility control statement(s) and
System programmer response:
resubmit the job.
Rebuild the index with the REBUILD utility to remove
Severity:
the object from REBUILD PENDING state.
8 (error)
User response:
Remove the object from the REBUILD PENDING
DSNU066I csect-name OPERAND oooooo NOT
STATE by using either LOAD REPLACE, RECOVER, or
ALLOWED FOR uuuuuu UTILITY
REPAIR against the object. Resubmit the job.
against tttttt TABLE
Severity:
Explanation:
8 (error)
An attempt was made to specify the REPLACE option
when executing the LOAD utility on a DB2 catalog
DSNU064I csect-name UTILITY NOT ALLOWED table. It is not permissible to replace existing rows in a
AGAINST SYSTEM DATABASE DB2 catalog table. Rows can only be added to the
existing rows in a DB2 catalog table.
Explanation:
System action:
An attempt was made to execute a utility against
database DSNDB01 or DSNDB06. The following Utility processing is not initiated.
utilities are not allowed against DSNDB01:
User response:
v LOAD
Correct the operand, and resubmit the job.
v REORG TABLESPACE against SYSUTILX (allowed
against other DSNDB01 table spaces) Severity:
v CHECK DATA 8 (error)
v REPAIR DBD
v RUNSTATS DSNU067I csect-name - TABLE SPACE
v MODIFY STATISTICS table-space-name IS NOT A LOB TABLE
SPACE
The following utilities are not allowed against
Explanation:
DSNDB06:
v LOAD (except SYSIBM.SYSSTRINGS) The table space specified, table-space-name, is not a LOB
table space. The object of the utility must be LOB table
v CHECK DATA
space.
v REPAIR DBD
System action:
System action:
Utility returns completion code=8.
Execution of the utility job is stopped.
Programmer response:
User response:
Correct the utility statement.
Remove the invalid utility control statements and
resubmit the job.
| DSNU068I KEYWORD NOT SUPPORTED FOR
Severity: | lob-or-xml TABLESPACE
8 (error) | Explanation:
| The keyword specified in the utility statement is not
| supported for the XML or LOB table space indicated by Correct the control statement in error, and resubmit the
| the lob-or-xml variable. Also, the lob-or-xml reported by job.
| the message cannot be explicitly named in the utility
Severity:
| statement.
8 (error)
| System action:
| Utility execution is terminated.
DSNU072I csect-name INVALID KEYWORD(S)
| User response: SPECIFIED FOR TABLESPACE LIST
| Correct the utility statement. Explanation:
| Severity: The specified keyword cannot be included in a list of
table spaces.
| 8 (error)
System action:
DSNU069I csect-name - AUXILIARY TABLE Processing terminates.
table-name NOT PERMITTED AS
User response:
EXCEPTION TABLE
Remove the specified keyword from the list of table
Explanation:
spaces.
A auxiliary table was specified as an exception table.
Severity:
System action:
8 (error)
Utility returns completion code=8.
Programmer response: DSNU073I csect-name - KEYWORD ’wwwww’
IGNORED
Specify an exception table that is not an auxiliary table.
Explanation:
DSNU070I csect-name KEYWORD OR OPERAND x The keyword, ’wwwww’ is no longer supported.
INVALID WITH y
System action:
Explanation:
Utility processing proceeds.
The use of KEYWORD or OPERAND ’x’ is inconsistent
Problem determination:
with KEYWORD or OPERAND ’y’.
Refer to Utility Guide and Reference for the correct
System action:
syntax.
The control statement in error is rejected and
Severity:
processing is halted.
0 (informational)
User response:
Correct the control statement in error and resubmit the
job.
| DSNU074I UTILITY NOT SUPPORTED FOR
| object-type TABLE SPACE
Severity:
| Explanation:
8 (error)
| The utility statement failed because the table space
| specified was a LOB or XML table space, and the utility
DSNU071I csect-name KEYWORD x REQUIRES | does not support they type of table space indicated.
KEYWORD y
| System action:
Explanation:
| The statement cannot be executed.
When keyword ’x’ is specified, keyword ’y’ must also
be specified.
| Programmer response:
System action:
| Correct the utility statement.
420 Messages
DSNU075I • DSNU080I
DSNU078I csect-name INVALID DBCS IDENTIFIER The data set identified by dd-name did not contain any
iiii text. The system might have processed the end of file
prematurely, or this job requires that the utility
Explanation: statements be skipped.
The DBCS identifier iiii is invalid. Reason codes are: System action:
Processing continues.
422 Messages
DSNU087I • DSNU090I
DB2 detected an error. This message is issued for, but Problem determination:
not limited to the following reasons:
Refer to Utility Guide and Reference to determine valid
v I/O errors were detected on the named object. ttttt is operand types for the designated keyword.
either ’READ’ or ’WRITE’. nnn; is the data set
number. aaaaaa is the first damaged page and bbbbbb Severity:
is the last damaged page of the data set. 8 (error)
v A broken page was detected.
v A page parity error was detected for a ’must DSNU088I csect-name INVALID CHARACTER
complete’ agent. OPERAND cccccccc
v A read or write I/O error was detected. A LPL
recovery might be in progress so the page is added Explanation:
to the WEPR instead of the LPL. The utility parser has determined that the operand
System action: ’cccccccc’ is invalid as a character operand.
Processing continues, but the pages within the error System action:
range are no longer accessible. Utility processing is not initiated.
System programmer response: User response:
Determine the appropriate level of recovery, and invoke Correct the keyword, and resubmit the job.
the recovery utility. If user-defined data sets are being
used and full data set or table space RECOVER is to be Problem determination:
used, then, prior to invoking the RECOVER utility, the Refer to Utility Guide and Reference for correct
table space must be stopped, new data set(s) defined, specification of the character operand.
and the table space restarted. If the data set is part of a
ROSHARE READ database, determine whether it was a Severity:
link or DASD failure. It there was a link failure, then 8 (error)
fix the link, and issue a -START DATABASE with the
ACCESS(FORCE) parameter. If the error was caused by
a DASD failure, then correct the problem from the DSNU089I csect-name OPERAND oooooooo IS TOO
system on which the database was defined as LONG
ROSHARE OWNER.
Explanation:
Problem determination:
The utility parser has determined that the operand
Refer to part 2 of Diagnosis Guide and Reference for a ’oooooooo’ is too long for the keyword specified.
discussion of database recovery procedures.
System action:
There may be an IOS message on the MVS console
Utility processing is not initiated.
SYSLOG indicating the type of I/O error that occurred.
If an IOS message was issued, follow the Problem User response:
Determination directions for the message.
Correct the keyword, and resubmit the job.
Severity:
Problem determination:
0 (informational)
Refer to Utility Guide and Reference for correct operand
length specification.
DSNU087I csect-name INVALID OPERAND TYPE
Severity:
FOR KEYWORD kkkkkkkk - oooooooo
8 (error)
Explanation:
The utility parser has determined that the operand
DSNU090I csect-name DD OR TEMPLATE NAME
’oooooooo’ is the wrong type for the keyword
nnn IS INVALID FOR KEYWORD kkk
’kkkkkkkk’. An example of such an error would be a
decimal operand where only a hexadecimal operand is Explanation:
allowed.
The DDNAME or TEMPLATE nnn was used as an
System action: improper input of the specified keyword kkk or from
one of the reserved ddnames: SYSIN, SYSPRINT,
Utility processing is not initiated.
UTPRINT, SORTWKnn, SORTLIB.
User response:
System action:
Correct the keyword, and resubmit the job.
Processing terminates.
424 Messages
DSNU097I • DSNU100I
utility that is beyond the UNLOAD phase should rarely was received during the -DIS UTIL, -TERM UTIL, or
be terminated. -START DATABASE ACCESS(FORCE) command, then
the command can be reissued.
User response:
Problem determination:
To restart, restore the operand to its prior definition. If
this is not acceptable, terminate the utility job step, take Obtain the system console log output, dump, and
corrective action, and resubmit the job. SYS1.LOGREC information. If you suspect an error in
DB2, refer to Part 2 of Diagnosis Guide and Reference for
Problem determination:
information on identifying and reporting the problem.
Refer to Utility Guide and Reference for correct operand
definitions.Refer to part 2 of Diagnosis Guide and
DSNU100I csect-name USERID = userid MEMBER =
Reference for a discussion of utility restart constraints.
member-name UTILID = utilid
PROCESSING UTILITY STATEMENT
DSNU097I csect-name - input WILL BE REQUIRED statement-number UTILITY = utility-name
SYNTAX IN FUTURE RELEASES PHASE = utility-phase COUNT =
object-count NUMBER OF OBJECTS IN
Explanation: LIST = list-size LAST OBJECT STARTED
The identified ’input’ is not required in this release, but = last-started STATUS = STOPPED
it will be part of the required syntax in future releases. | Explanation:
System action: | This message is issued in response to a DISPLAY
Utility processing continues. | UTILITY command. The utility job with identifier utilid
| stopped during processing. The utility stopped for one
Programmer response: | of these reasons:
Refer to Utility Guide and Reference for the correct | v The REORG utility stopped in response to its
syntax. | UNLOAD(PAUSE) option. The utility is stopped in
| the RELOAD phase.
Severity:
| v The utility is stopped because of a DB2 subsystem
4 (warning) | failure or cancellation (for example, a STOP DB2
| command).
DSNU099I csect-name - IRLM ’req-type’ REQUEST
FAILED, IRLM RETURN CODE = | In a data sharing environment, member-name identifies
X’return-code’ IRLM REASON CODE = | the DB2 member. In a non data-sharing environment,
X’reason-code’ | member-name is blank. At the time of the request,
| object-count records or pages were processed.
Explanation:
The request to the IRLM to obtain or release a lock | If the utility job step is restarted with the
failed for the reasons specified in return-code and | RESTART(PHASE) option, it begins with PHASE
reason-code. In a non data-sharing environment, the | utility-phase. However, not all utilities have phases.
requested lock is the utility serialization lock. In a data | Those that do have phases restart from the beginning
sharing environment, the requested lock is the utility | of that phase.
serialization lock, the utility identifier lock, or the
utility execution lock. For an explanation of IRLM | COUNT indicates the number of pages or records
return and reason codes, see Codes . The type of request | processed in a utility phase. COUNT has different
is indicated by req-type. | meanings for different utilities. For utilities not
| mentioned below, ignore this field.
System action:
| v For CHECK INDEX, LOAD, REBUILD INDEX, and
Utility and command processing terminates. | REORG: number of records processed (log records
| for the LOG phase of REORG), or 0 (for the SWITCH
System programmer response:
| or BUILD2 phase of REORG).
Determine the cause of the IRLM error and take | v For COPY, MERGECOPY, RECOVER (restore phase),
appropriate action. | and RUNSTATS: number of pages processed.
User response: | v For STOSPACE: number of table spaces or indexes
| processed.
Refer to the IRLM messages and codes section for
problem determination and the appropriate action. | If the utility is processing a list of objects, list-size gives
Restart the utility by specifying the RESTART | the total number of objects in the list and last-started
parameter, or terminate the utility with the -TERM | gives the item number of the last object for which
command and then resubmit the job. If this message
| processing was started. These values may not be Command processing is terminated.
| accurate in the UTILINIT before the list size has been
System programmer response:
| determined.
Issue a -DISPLAY DATABASE command to determine
System action:
the state of the DSNDB01.SYSUTILX table space. If the
DB2 waits for directions to either restart or terminate state is copy pending, do a full image copy. If the state
the utility. is recovery pending, use the RECOVER utility to
recover DSNDB01.SYSUTILX. If you suspect an error in
Operator response:
DB2, refer to Part 2 of Diagnosis Guide and Reference for
If necessary, and if you have SYSOPR authority, you information on identifying and reporting the problem.
can issue the -TERM UTILITY command to release the
User response:
resources claimed by the stopped utility.
Notify the system programmer so that the pending
User response:
condition can be resolved.
If you have the required authority, restart or terminate
Severity:
the utility job step.
0 (informational)
To restart the job step, you must have authority to run
the indicated utility and to complete any other utility
functions in the utility job step. DSNU105I csect-name - USERID=userid
MEMBER=member-name UTILID=utilid
To terminate the utility with the -TERM UTILITY
PROCESSING UTILITY STATEMENT n
command, you must be the originator or have SYSOPR
UTILITY=utility-name PHASE=phase-name
or SYSADM authority.
COUNT=n NUMBER OF OBJECTS IN
Severity: LIST=list-size LAST OBJECT
STARTED=last-started STATUS=ACTIVE
0 (informational)
Explanation:
426 Messages
DSNU106I • DSNU110I
UTILID is a 1- to 16-byte alphanumeric token that can altered, displayed, or terminated was correctly
contain any number of periods. entered.To view all currently valid identifiers, issue the
-DISPLAY UTILITY (*) or (partial-utility-id*) command.
System action:
| Severity:
The -ALTER UTILITY, -DISPLAY UTILITY, or -TERM
UTILITY command is rejected. Further processing of | 0 (informational)
the command is ended.
User response: DSNU113I csect-name DISPLAY OR TERM UTILITY
MESSAGE LIMIT HAS BEEN
Review the UTILID provided in the message to
REACHED
determine why it does not conform to the syntax rules
of a utility identifier token, and reissue the request. Explanation:
Severity: This message indicates that the DISPLAY or TERM
utility command that was specified generated more
8 (error)
messages than will fit in the amount of storage that is
available.
DSNU111I csect-name - SUBPHASE=subphase-name
System action:
COUNT=n
The DISPLAY or TERM UTILITY command terminates.
Explanation:
User response:
This message is issued only in response to a -DISPLAY
UTILITY command that is entered on the same member Specify a set of utility jobs using a partial-utility-id to
where the utility is executing. It immediately follows a limit the number of utilities being displayed or
prior DSNU105I message if the utility is using subtasks terminated. See the DB2 Command Reference for more
to perform processing in parallel. One of these information.
messages exists for each subtask.
Severity:
This message gives the user an estimate of how much
0
processing the utility subtask has completed.
SUBPHASE subphase-name identifies the activity that the
DSNU114I csect-name UTILITY COMMANDS
subtask was performing at the time the -DISPLAY
SUBSYSTEM FAILURE, REASON=Xcode
UTILITY command was issued.
Explanation:
COUNT n is the number of records processed by the
utility subtask. This message indicates an abend has occurred in the
utility commands subsystem.
System action:
System action:
The system continues processing.
The command abends. In the case of the -TERM
Severity:
command, termination actions taken previously under
0 (informational) this command are backed out.
User response:
DSNU112I csect-name - NO AUTHORIZED
Prior messages and/or the SVC dump identify the
UTILITY FOUND FOR UTILID = utilid
failure. If the condition can be corrected, the command
Explanation: may be reissued.
This message is issued in response to an -ALTER Problem determination:
UTILITY, -DISPLAY UTILITY, or -TERM UTILITY
In most cases, the failure is not user related. In some
command. DB2 has no record of the utility job
cases, prior messages indicate a user error that may be
identified by the utility identifier utilid. The utilid might
corrected. The problem may be as simple as
not be correct, or the utility might have already
SYSIBM.SYSUTIL being temporarily locked by another
terminated.
command or a utility job. If you suspect an error in
System action: DB2, refer to Part 2 of Diagnosis Guide and Reference for
information on identifying and reporting the problem.
The system rejects the -ALTER UTILITY, -DISPLAY
UTILITY, or -TERM UTILITY request for the indicated
utility job.
User response:
Verify that the utility identifier of the utility job to be
428 Messages
DSNU115I • DSNU120I
| 0 (informational)
DSNU115I csect-name utility-name UTILITY WITH
UTILID = utilid CAN ONLY BE
TERMINATED BY A MEMBER WITH DSNU118I csect-name MAXIMUM NUMBER OF
THE SAME RELEASE = release ERROR MESSAGES ISSUED
Explanation: Explanation:
Command TERM UTILITY cannot terminate the utility The utility issued the maximum number of messages
job with identifier utilid because it belongs to a member that can be generated with the available memory for
with a release level identified in the message. Some message buffers. DB2 suppresses any additional error
utilities can be terminated only from a member of the messages.
DB2 data sharing group with the same release level.
System action:
System action:
Utility processing continues.
Command TERM UTILITY is rejected for the indicated
utility job. User response:
User response: Refer to the message information for any other error
messages that are issued by the utility and take the
Make sure the utilid identifies the utility you want to specified action to resolve the problems. Then rerun the
terminate. If it does, issue command TERM UTILITY utility to ensure that all errors are resolved.
from a member with a release level identified in the
message in the DB2 data sharing group. Severity:
Severity: 0 (informational)
0 (informational)
| DSNU119I csect-name- NUMBER OF OBJECTS
| PROCESSED BY THE UTILITY
| DSNU116I csect-name RECOVER LOGAPPLY | EXCEEDED THE MAXIMUM
| PHASE DETAILS: STARTING TIME = | ALLOWED
| timestamp START RBA = ss START
| LRSN =rr END RBA = ee END LRSN = | Explanation:
| nn LAST COMMITTED RBA = cc LAST | The number of objects being processed by the utility
| COMMITTED LRSN = ll ELAPSED | has exceeded the maximum allowed, which includes
| TIME = hh:mm:ss | tables, tablespace partitions, indexes, index space
| Explanation: | partitions and other database objects modified or
| referenced by the utility. This generally happens when
| This message is only issued during RECOVER | a utility is run on a partitioned tablespace with many
| LOGAPPLY phase in response to a DISPLAY UTILITY | partitions and indexes defined.
| command.
| System action:
| Use the information from this message to estimate how
| much processing RECOVER has completed in the | The utility job is abended with reason code
| LOGAPPLY phase. The starting and ending RBA/LRSN | X’00E400A1’.
| information shows the range of log records that will be | User response:
| applied. The range covers all objects in the list. The last
| committed RBA/LRSN shows the RBA/LRSN of the | Reduce the number of partitions and/or indexes being
| last log record applied at the last commit point in the | processed by the utility. If the utility must be run
| LOGAPPLY phase. If fast log apply is active, then the | against the entire tablespace, you can try dropping one
| last committed RBA/LRSN values might not always | or more indexes to bypass this problem.
| increase if multiple DISPLAY UTILITY commands are
| issued consecutively, because the log records have been | DSNU120I csect-name DEADLOCK
| sorted by object and page number. The elapsed time is | INFORMATION: INTERVAL COUNT=
| based on the starting time of the LOGAPPLY phase. | n, NUMBER OF WAITERS = m. LOCK
| System action: | NAME = lcknum TYPE = type
| FUNC/STATE/DURATION = fst dur
| This message reflects the state of RECOVER log apply | HOLDER/WAITER = h/w PLAN-ID =
| at the time that the DISPLAY UTILITY command is | planid CORR-ID = corrid MEMBER NM
| issued. The system continues processing. A subsequent | = mbrum
| DISPLAY UTILITY command reflects the continued
| processing. | Explanation:
| Severity: | Utility processing encountered a resource that is
| currently unavailable because the resource is involved
430 Messages
DSNU160I • DSNU166I
Severity: Severity:
8 (error) 8 (error)
DSNU172I csect-name UTILITY JOB STOPPED BY DSNU181I csect-name RESTART NOT ALLOWED
STOP DB2 COMMAND FOR utility-name UTILITY
Explanation: Explanation:
A -STOP DB2 command was issued during execution of An attempt was made to restart the named utility. DB2
the utility job step. does not allow this utility to be restarted.
The executing utility stops processing but continues to Utility processing is abended. Abend reason code
hold resources. Subsequent utilities in the same job step 00E40018 might be issued.
are not executed. The storage of the utility job is System programmer response:
retained. Therefore, the utility job step is restartable.
If necessary, take actions to prevent access to the table
User response: space before terminating the utility.
Following a -START DB2 command, the utility job step User response:
may be restarted. Alternatively, the utility may be
terminated using the -TERM UTILITY command and Issue the -TERM UTIL command to terminate the
resubmitted as a new job. A REORG utility that has utility job and then rerun the job without the RESTART
passed the UNLOAD phase should rarely be parameter.
terminated.
Severity:
8 (error)
432 Messages
DSNU182I • DSNU186I
8 (error)
DSNU182I csect-name utility-name MUST BE THE
ONLY UTILITY IN SYSIN
DSNU184I csect-name - DO NOT RECOVER
Explanation:
OBJECT qual.obj-nm UNTIL THE
The submitted utility control statements contain a NEXT TRACKER SITE RECOVERY
utility on the table space DSNDB01.SYSUTILX. This CYCLE
table space is integral to controlling the execution of
Explanation:
utilities. Control over previous or subsequent utilities in
the job step would be lost if the utility were allowed to If DB2 detects an inconsistency relating to a utility’s
execute. Therefore, the identified utility must be the status on object ’qual.obj-nm’ at the tracker site, DB2
only utility in a job step. issues this message. This event can occur if the
SYSUTIL record for the utility either does not exist, or
This message is also issued if you recover the
reflects incorrect information about hte status of the
SYSUTILX indexes, DSNLUX01 and DSNLUX02, or
utility.
table space DSNDB01.DBD01 and include other utility
control statements in the same job step. System action:
Additionally, this message will be issued if you invoke The utility issues ABEND04E with return code
either the BACKUP SYSTEM or RESTORE SYSTEM 00E40009.
utilities and include additional commands.
System programmer response:
System action:
Wait for the next recovery cycle to recover the object
Work performed by utilities in the same utility job step named in this message. If the object named in this
prior to the starting utility persist. The utility identified message is a catalog or directory object, you cannot
and subsequent utilities are not allowed to execute, and recover this object, or any other objects in the list of
the utility job step is placed in the stopped state. catalog and directory objects, or any user data or
indexes. Wait until the next recovery cycle to recover
User response:
the object.
Terminate the utility execution that received this
User response:
message using the -TERM UTILITY command. Submit
a subsequent job step containing only the identified Contact the system programmer.
utility. Execute additional utilities, if any, in a separate
job step. Severity:
Severity: 8 (error)
8 (error)
DSNU185I csect-name THE VSAM DATA SET DOES
NOT EXIST FOR obj-type
DSNU183I csect-name - utility-name UTILITY NOT obj-qual.obj-name part part-number
COMPATIBLE WITH OTHER ACTIVE
UTILITIES Explanation:
Explanation: The VSAM data set(s) for the specified object has not
been defined yet because the object was created with
The utility identified by ’utility-name’ is executing DEFINE NO.
against table space DSNDB01.SYSUTILX. This table
space is integral to controlling the execution of utilities. System action:
Control over other utilities running at the same time The utility skips the object that was created with
would be lost if the utility were allowed to execute. DEFINE NO, and processing continues.
Therefore, the identified utility must be executed alone.
There must be no other active DB2 utilities in the Severity:
system. 0 (informational)
System action:
Utility execution is terminated. DSNU186I csect-name- A SPATIAL INDEX
CANNOT BE PROCESSED BY THIS
User response: UTILITY
Rerun the utility when there are no other utilities Explanation:
executing. Use the -DISPLAY UTILITY command to see
what utilities are ACTIVE. Utilities in the STOPPED | The target objects specified for the utility include one
state are allowed. | or more spatial indexes, which are not supported by
| this utility. If the utility specifies a table space, then you
Severity:
| can drop the spatial indexes, run the utility, and then System action:
| recreate the indexes.
Utility processing is not initiated.
System action:
System programmer response:
The utility does not execute.
Determine which of the three utilities, LOAD
Severity: REPLACE, RECOVER, or REPAIR, should be used to
remove the object from the recover pending state.
8
User response:
DSNU200I csect-name - ERROR RANGE ON TABLE Remove the table space from the recover pending state
SPACE database.tablespace-name by using either LOAD REPLACE, RECOVER, or
PROHIBITS PROCESSING REPAIR against the object. LOAD REPLACE with
KEEPDICTIONARY is not allowed on a table space
Explanation:
(with compression active) in the recover pending state.
The utility encountered an error range on the identified Resubmit the job.
table space or partition, which prohibits it from
Severity:
continuing.
8 (error)
System action:
The utility fails serialization and terminates.
DSNU203I csect-name - RECOVER PENDING ON
User response: INDEX creator.index-name PROHIBITS
PROCESSING
Correct the error range for the table space by running
RECOVER ERROR RANGE. Then resubmit the original Explanation:
failing utility.
An attempt was made to execute a utility against an
Severity: index that is in a rebuild pending state.
434 Messages
DSNU205I • DSNU210I
System action:
DSNU208I csect-name - GROUP BUFFER POOL
The utility terminates. RECOVERY PENDING ON INDEX
creator.index-name PROHIBITS
User response:
PROCESSING
Use the -START DATABASE command to correct the
Explanation:
logical error range (LPL) for the table space. Then
resubmit the original failing utility. You cannot execute a utility on an index that is in a
group buffer pool recovery pending (GRECP) status.
Severity:
System action:
8 (error)
Utility processing does not start.
DSNU206I csect-name - LOGICAL ERROR RANGE User response:
(LOGICAL PAGE LIST) ON INDEX
creator.index-name PROHIBITS Run the REBUILD INDEX utility on the index to
PROCESSING remove the table space from the group buffer pool
recovery pending status. Then resubmit the job.
Explanation:
Severity:
The utility cannot continue because it encountered a
logical error range (logical page list) on the identified 8 (error)
index space or partition.
System action: DSNU209I csect-name - RESTART PENDING ON
obj-type database.tablespace-name
The utility terminates. PROHIBITS PROCESSING
User response: Explanation:
Issue the -DISPLAY command for the index to identify An attempt was made to execute a utility against a
the logical error range (LPL). There are two ways to table space or index space that is in a restart pending
restore the index or index partition that has the LPL state.
before resubmitting the original failed utility.
System action:
v Issue the START DATABASE command to clear the
LPL status, then run the RECOVER or REBUILD Utility processing is not initiated.
INDEX utility.
System programmer response:
v Run the RECOVER or REBUILD INDEX utility to
restore the entire nonpartitioning index (NPI). Use the DISPLAY THREAD TYPE(POSTPONED) to
determine the status of the resource. Use the RECOVER
Severity: POSTPONED command if recover has not already been
8 (error) started. Resubmit the job.
Severity:
DSNU207I csect-name - GROUP BUFFER POOL 8 (error)
RECOVERY PENDING ON TABLE
SPACE database.tablespace-name
PROHIBITS PROCESSING DSNU210I csect-name - INFORMATIONAL COPY
PENDING ON obj-type obj-qual.obj-name
Explanation: PROHIBITS PROCESSING
You cannot execute a utility on a table space that is in a Explanation:
group buffer pool recovery pending status.
An attempt was made to execute the RECOVER utility
System action: with the ERROR RANGE or PAGE options against an
436 Messages
DSNU231I • DSNU234I
0 (informational) cmpbytes
The total number of compressed KB for the
loaded or reorganized data rows (including
DSNU232I csect-name KEEPDICTIONARY the row prefix). This number was rounded to
REQUESTED BUT COMPRESS the nearest KB.
ATTRIBUTE NOT DEFINED FOR
TABLE SPACE table-space-name percsave
The percentage of bytes saved from the loaded
Explanation: or reorganized data rows as a result of
The KEEPDICTIONARY option was specified in the compression.
LOAD or REORG TABLESPACE utility statement. This
keyword should only be used with table spaces that The values above reflect only the number of bytes for
have the COMPRESS YES attribute. Otherwise, it is the data row and the respective row prefix (6 bytes).
ignored. The COMPRESS column of DB2 page and dictionary page overhead is not
SYSIBM.SYSTABLEPART contains the current included.
compression status.
pctrowcomp
System action: The percentage of the rows that were
compressed within the total number of rows
Processing continues. If the dictionary exists, it is that were loaded or reorganized. The stored
erased if LOAD REPLACE or REORG is specified. length and the external length of a row was
Severity: compared to determine if the row was
compressed. If an EDITPROC is involved, its
4 (warning) effect on the length of the row is considered in
the calculation.
DSNU233I csect-name COMPRESSION noncmppages
DICTIONARY DOES NOT EXIST FOR The estimated number of DB2 pages required
TABLE SPACE table-space-name by the uncompressed data rows that were
Explanation: loaded or reorganized. Space required for
PCTFREE and FREEPAGE is included. This
The KEEPDICTIONARY option was specified in the number was rounded up to the next integer.
LOAD or REORG TABLESPACE utility statement for a
table space that does not have a compression cmppages
dictionary. The estimated number of DB2 pages required
by the compressed data rows that were loaded
System action: or reorganized. Space required for PCTFREE
and FREEPAGE is included. Dictionary pages empty. The data was not compressed.
are also included unless a LOAD
System action:
RESUME(YES) was run. This number was
rounded up to the next integer. Processing continues.
auncmprowlen User response:
Average uncompressed row length.
The input data set must contain data in order to build
avgcmprowlen a compression dictionary while running the LOAD
Average compressed row length. utility. Ensure that the input records are not discarded
by the WHEN clause or conversion errors. For the
pagesave
REORG TABLESPACE utility, the table space must be
An estimate of the percentage of DB2 pages
populated with data in order to build a compression
saved by compressing the loaded or
dictionary.
reorganized data rows.
Severity:
System action:
Processing continues.
| 0 (informational)
Module:
DSNU236I csect-name DICTIONARY FOR TABLE
noncmpbytes SPACE table-space-name HAS BEEN
KB WITHOUT COMPRESSION ERASED.
cmpbytes Explanation:
KB WITH COMPRESSION
The compression dictionary of the specified table space
percsave was erased.
PERCENT OF THE BYTES SAVED FROM
The COMPRESS attribute of the table space is NO, and
COMPRESSED DATA ROWS
there are no active rows in this table space. In this case,
pctrowcomp the LOAD RESUME NO utility erases the dictionary.
PERCENT OF THE LOADED ROWS WERE
System action:
COMPRESSED
Processing continues.
noncmppages
PAGES REQUIRED WITHOUT Severity:
COMPRESSION
0 (informational)
cmppages
PAGES REQUIRED WITH COMPRESSION
DSNU237I TABLE table2 IS NOT IN SAME
auncmprowlen TABLESPACE AS TABLE table1
BYTES FOR AVERAGE UNCOMPRESSED
ROW LENGTH Explanation:
438 Messages
DSNU241I • DSNU244I
| System action:
DSNU241I csect-name DICTIONARY WITH n
ENTRIES HAS BEEN SUCCESSFULLY | Processing continues. If KEEPDICTIONARY was
BUILT FROM m ROWS FOR TABLE | specified, a dictionary is built for the table space
SPACE table-space-name, PARTITION | partition. If COPYDICTIONARY was specified, no
part-num | dictionaries are copied.
Explanation: | Severity:
A compression dictionary was built for the specified | 4 (warning)
partition of the table space. This message is issued
during the RELOAD phase of the LOAD utility and at
the end of the UNLOAD phase of the REORG utility. DSNU244I csect-name COMPRESSION REPORT
FOR TABLE SPACE table-space-name,
The variable n is the number of dictionary entries: 512, PARTITION part-num
1024, 2048, 4096, or 8192. n depends on the number of
rows being loaded or reorganized. Explanation:
m is the number of rows used to build the dictionary. The data in the table space partition was compressed.
This message is issued at the end of the RELOAD
System action: phase for the LOAD and REORG utility. The statistics
that follow apply only to the data that was loaded or
Processing continues.
reorganized. For example, RESUME(YES) reports
Severity: statistics only on the additional rows that were loaded,
not what was previously in the table space.
0 (informational)
The compression statistics follow:
| DSNU242I csect-name KEEPDICTIONARY noncmpbytes
| REQUESTED BUT COMPRESS The total number of uncompressed KB (where
| ATTRIBUTE NOT DEFINED ON KB = 1024 bytes) for the loaded or reorganized
| TABLE SPACE table-space-name, data rows (including the row prefix). This
| PARTITION part-num number was rounded to the nearest KB.
| Explanation: cmpbytes
The total number of compressed KB for the
| Either the KEEPDICTIONARY option was specified in
loaded or reorganized data rows (including
| the LOAD or REORG TABLESPACE utility statement or
the row prefix). This number was rounded to
| the COPYDICTIONARY option was specified in a
the nearest KB.
| LOAD utility statement. These keywords should be
| used only with table space partitions that have the percsave
| COMPRESS YES attribute. Otherwise, it is ignored. The The percentage of bytes saved from the loaded
| COMPRESS column of SYSIBM.SYSTABLEPART or reorganized data rows as a result of
| contains the current compression status. compression.
| System action:
The values above reflect only the number of bytes for
| Processing continues. If the dictionary exists, it is the data row and the respective row prefix (6 bytes).
| erased if either LOAD REPLACE or REORG is DB2 page and dictionary page overhead is not
| specified. included.
| Severity: pctrowcomp
The percentage of the rows that were
| 4 (warning) compressed within the total number of rows
that were loaded or reorganized. The stored
| DSNU243I csect-name COMPRESSION length and the external length of a row was
| DICTIONARY DOES NOT EXIST FOR compared to determine if the row was
| TABLE SPACE table-space-name, compressed. If an EDITPROC is involved, its
| PARTITION part-num effect on the length of the row is considered in
the calculation.
| Explanation:
noncmppages
| Either the KEEPDICTIONARY option was specified in The estimated number of DB2 pages required
| the LOAD or REORG TABLESPACE utility statement or by the uncompressed data rows that were
| the COPYDICTIONARY option was specified in a loaded or reorganized. Space required for
| LOAD utility statement for a table space partition that PCTFREE and FREEPAGE is included. This
| does not have a compression dictionary. number was rounded up to the next integer.
Module:
DSNU246I csect-name DICTIONARY FOR TABLE
noncmpbytes SPACE table-space-name, PARTITION
KB WITHOUT COMPRESSION part-num HAS BEEN ERASED.
cmpbytes Explanation:
KB WITH COMPRESSION
The compression dictionary of the specified partition of
percsave the table space was erased.
PERCENT OF THE BYTES SAVED FROM
The COMPRESS attribute of the table space partition is
COMPRESSED DATA ROWS
NO, and there are no active rows in this partition. In
pctrowcomp this case, the LOAD RESUME NO utility erases the
PERCENT OF THE LOADED ROWS WERE dictionary.
COMPRESSED
System action:
noncmppages
Processing continues.
PAGES REQUIRED WITHOUT
COMPRESSION Severity:
cmppages 0 (informational)
PAGES REQUIRED WITH COMPRESSION
auncmprowlen | DSNU247I csect-name FROM TABLE SPACE
BYTES FOR AVERAGE UNCOMPRESSED | table-space-name, PARTITION part-num1
ROW LENGTH | COPIED to PARTITION part-num2
avgcmprowlen | Explanation:
BYTES FOR AVERAGE COMPRESSED ROW
LENGTH | A compression dictionary from partition part-num1 was
| successfully copied to part-num2 for the specified table
pagesave | space.
PERCENT OF THE DB2 DATA PAGES SAVED
USING COMPRESSED DATA | System action:
0 (informational) | Severity:
| 0 (informational)
DSNU245I csect-name THE COMPRESSION
DICTIONARY WAS NOT BUILT FOR
TABLE SPACE table-space-name,
PARTITION part-num
Explanation:
440 Messages
DSNU250I • DSNU252I
Severity:
DSNU250I csect-name UNLOAD PHASE
COMPLETE, ELAPSED TIME = 0 (informational)
hh/mm/ss
Explanation: DSNU251I csect-name UNLOAD PHASE
STATISTICS. NUMBER OF RECORDS
The UNLOAD phase of the REORG utility completed
UNLOADED= mmmmmm FOR obj-type
normally. The time that elapsed between the beginning
obj-qual.obj-name PART nn
of the REORG utility and the completion of the
UNLOAD phase was hh/mm/ss, hours, minutes, and Explanation:
seconds, respectively.
This message is issued at the completion of the
System action: UNLOAD phase of the REORG utility. It gives the
number of records that were unloaded mmmmmm for
Action subsequent to this message depends on the
partition nn of the tablespace, index, or indexspace that
UNLOAD option of the REORG utility statement:
was specified. The count can indicate the amount of
v If the UNLOAD option is CONTINUE, execution of processing.
the utility continues into the RELOAD phase.
System action:
v If the UNLOAD option is PAUSE, execution of the
utility is stopped at the beginning of the RELOAD Only valid table records are unloaded. Dropped table
phase. record counts are not reported.
v If the UNLOAD option is ONLY or EXTERNAL, the Operator response:
REORG utility is finished. Processing continues to
the next utility in the utility job step, or, if there are Count can be indicative of the amount of processing
no more utility statements, the utility job step that remains.
terminates normally.
User response:
Operator response:
The record count represents the current cardinality of
The operator’s response depends on the UNLOAD the table or index that was indicated in the erro
option of the REORG statement: message. Consider invoking the RUNSTATS utility and
v If the UNLOAD option is CONTINUE, no operator then rebinding the involved PLANs if this value differs
response is required. The execution of the REORG greatly from the SYSTABLE.CARD value so that the
utility is proceeding. SQL optimizer can bring the PLANs up to date.
rebinding of the involved PLANs should be considered you suspect an error in DB2, refer to Part 2 of Diagnosis
if this value differs greatly from the SYSTABLE.CARD Guide and Reference for information on identifying and
value, so that the SQL optimizer can bring the PLANs reporting the problem.
up to date.
Collect the following diagnostic items:
Severity: v Console output from the system on which the job
0 (informational) was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
v Dynamic dump, taken to SYS1.DUMPxx data set, by
DSNU253I csect-name UNLOAD PHASE
DB2 (04E and 04F abends).
STATISTICS. NUMBER OF RECORDS
action= mmmmmm FOR TABLE table-name v Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Explanation:
Severity:
This message is issued at the completion of the
UNLOAD phase of the REORG utility. If action is 4 (warning)
″UNLOADED″, it gives the number of records
mmmmmm that were unloaded for the specified table DSNU255I csect-name - KEY COUNT
name. If action is ″DISCARDED″, it gives the number of INCONSISTENT FOR pppppppp PHASE,
records mmmmmm that were discarded for the specified NUMBER OF KEYS EXPECTED =
table name. nnnnnnnn, NUMBER OF KEYS
System action: PROCESSED = aaaaaaaa.
Processing continues if UNLOAD PAUSE option was TERM the utility and re-access the indexes by running
used. REPAIR utility to reset the rebuild-pending states on
indexes. Run the CHECK INDEX utility to determine if
System programmer response: any of the affected indexes are inconsistent.
Determine the failing environment. If you suspect an Inconsistent indexes can be rebuilt by the REBUILD
error in DB2, refer to Part 2 of Diagnosis Guide and INDEX utility.
Reference for information on identifying and reporting Problem determination:
the problem.
If the working data set was manipulated by the user
User response: during the restart process, make sure it was handled
Check if unload data set was altered by user. properly. Refer to Utility Guide and Reference for detailed
Determine if the inconsistent record counts between the information.
unload and reload phases is a potential problem. If it is If you suspect an error in DB2, refer to Part 2 of
an internal DB2 problem, report to system programmer. Diagnosis Guide and Reference for information on
Problem determination: identifying and reporting the problem.
442 Messages
DSNU256I • DSNU260I
If the return code is 8, the table space, indexspace, or can be determined and corrected.
partition being copied should be recovered with the
Severity:
RECOVER utility.
8 (error)
User response:
Notify the system programmer if the return code is 8. If
DSNU271I csect-name - REORG PENDING ON FOR
the return code is 4, no action is required.
TABLE SPACE database.index-name PART
Severity: part number PROHIBITS PROCESSING
4 (warning) or 8 (error) Explanation:
An attempt was made to execute a REORG utility to
| DSNU269I csect-name FIELD field-name IS NOT redistribute data in a partitioned table space. The
| ALLOWED partition number stated in this message was found to
have the REORP state on, but was not specified on the
| Explanation:
PART n1:n2 parameter of the REORG utility.
| You have specified a GENERATED ALWAYS column in
If you are running REORG to materialize identity
| the field specification list. Only a column defined as
column values, you must reorganize the entire table
| GENERATED BY DEFAULT is allowed to be specified
space.
| in the field specification list.
System action:
| Identity columns or row change timestamp columns
| that were defined as GENERATED ALWAYS cannot be Utility processing is not initiated.
| specified in a LOAD field specification list. Also, they
System programmer response:
| cannot be implied in LOAD FORMAT UNLOAD or
| LOAD with no field specification list. Identify the correct partition range specification for the
REORG utility by issuing the DISPLAY command for
| System action:
the table space, and resubmit the utility job step.
| The LOAD utility is terminated
Severity:
| User response:
8 (error)
| Omit the GENERATED ALWAYS column or identity
| column from the LOAD field specification list and
DSNU272I csect-name - FIELD PROCEDURE
| rerun the job.
procedure-name COULD NOT BE
| Severity: LOADED
| 8 (error) Explanation:
An installation supplied field procedure could not be
DSNU270I csect-name - table-name, column-name IN loaded during encoding for LOAD or decoding for
VIOLATION OF INSTALLATION REORG. See SQLCODE -682 for more detail.
DEFINED FIELD PROCEDURE
System action:
procedure-name. function-code, return-code,
reason-code, message-token The utility will terminate with a return code of 8.
Explanation: System programmer response:
An installation-supplied field procedure has returned Determine why the field procedure could not be
an error during encoding for LOAD or decoding for loaded.
REORG. See SQLCODE -681 for more detail.
User response:
System action:
Take the job output to the system programmer.
The utility will issue a system ’04E’ abend with a
reason code of ’00E40336’. Severity:
444 Messages
DSNU280I • DSNU283I
REORG with SHRLEVEL REFERENCE or CHANGE Check the error input records against the error reason
cannot be used on table space partitions with REORG code returned from the validation procedure. Refer to
PENDING restrictive state. Utility Guide and Reference for a definition of LOAD
input field column specifications.
System action:
Severity:
The REORG utility job is terminated.
4 (warning)
User response:
Execute REORG with SHRLEVEL NONE against the
DSNU282I csect-name UNABLE TO RESTART AT
partitions in REORG PENDING state to rebalance the
LAST CHECKPOINT WITH DDNAME
partitions and remove the REORG PENDING state.
’dddddddd’
Severity:
Explanation:
8 (error)
The data set with DDNAME dddddddd is a concatenated
data set and the utility can be restarted only at the
DSNU280I csect-name - ERROR=X’reason-code’ beginning of the phase (RESTART PHASE), not at the
FROM EDIT ROUTINE procedure-name last checkpoint (RESTART CURRENT).
FOR table-name
System action:
Explanation:
The utility will issue a system ’04E’ abend with a
The edit routine provided by your installation has reason code of ’00E40323’.
returned an error during the load of a record into the
User response:
table indicated. The reason code is set by the edit
routine. Change the RESTART option to RESTART PHASE and
resubmit the job step.
System action:
Collect the following diagnostic items:
The LOAD or REORG utility will receive ABEND04E
RC00E40323. v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
System programmer response: period of time spanning the failure.
Verify that the edit routine is correct. v Dynamic dump, taken to SYS1.DUMPxx data set, by
DB2 (04E and 04F abends).
User response:
v Listing of SYS1.LOGREC data set, obtained by
Correct any errors in the input data. Ensure that the executing IFCEREP1.
edit routine provided is correct. The utility can be
restarted or terminated. Severity:
Severity: 8
8 (error)
| DSNU283I csect-name type-of-error SQLCODE =
| sqlcode, SQLERRM = sqlerrm, SQLSTATE
DSNU281I csect-name RECORD (n) OF TABLE | = sqlstate, SQLERRP = sqlerrp, SQLERRD
table-name VIOLATING VALID | = sqlerrd1 sqlerrd2 sqlerrd3 sqlerrd4 sqlerrd5
ROUTINE validproc-name, ERROR | sqlerrd6
CODE=X’reason-code’
| Explanation:
Explanation:
| An error occurred, that returned SQLCA error
The validation exit routine provided by your | information to the utility. This message contains
installation blocked the load of record ’n’ into TABLE | multiple components.
’table-name’. The reason-code was set by the exit
routine. | The SQL diagnostic information can be found in the
| SQLERRD1, SQLERRD2, SQLERRD3, SQLERRD4,
System action: | SQLERRD5, and SQLERRD6 fields.
The LOAD utility continues to process the following | TYPE-OF-ERROR
input record. | Indicates a trigger error, a LOB error, an XML
System programmer response:
| error, or a key evaluation error.
| negative, this indicates that an error has v Use the REFRESH TABLE SQL statement to insert
| occurred. For more information about this SQL data into the system-maintained materialized query
| return code, see Codes. table.
| SQLERRP v Use the ALTER statement to change the materialized
| The name of the procedure that detected the query table to a user-maintained materialized query
| error. table or a base table, and resubmit the utility job
step.
| SQLERRM
| A length indicator and one or more tokens, Severity:
| separated by X’FF’, that are substituted for 8
| variables in the descriptions of error
| conditions. It may contain truncated tokens. A
| length of 70 bytes might indicate a possible DSNU286I csect-name REORG TABLESPACE
| truncation. dbname.tsname OFFPOSLIMIT
SYSINDEXPART ROWS
| SQLSTATE
| A return code for the outcome of the most Explanation:
| recent execution of an SQL statement This is the header message for the SYSINDEXPART
| SQLERRD section of the REORG TABLESPACE OFFPOSLIMIT
| Each field contains a value that indicates the output. This section lists the SYSINDEXPART rows for
| number of rows that qualified for the SQL the table space or table space partition as specified in
| statement, the number of rows in the result the REORG TABLESPACE input statement. The fields
| table, a rough estimate of required resources, from SYSINDEXPART are:
| or an internal error code. CREATOR
Index creator name
| For a complete description of sqlerrp, sqlerrm, and the
| sqlerrd fields, see the description of SQLCA fields in IXNAME
| SQL Reference. Index name
446 Messages
DSNU287I • DSNU290I
LEAFDIST
DSNU287I csect-name REORG TABLESPACE
Number of pages between leaf pages
dbname.tsname INDREFLIMIT
multiplied by 100
SYSTABLEPART ROWS
STATSTIME
Explanation:
TIMESTAMP of RUNSTATS update
This is the header message for the SYSTABLEPART
section of the REORG TABLESPACE INDREFLIMIT Rows which meet the LEAFDISTLIMIT criteria are
output. This section lists the SYSTABLEPART rows for prefaced with ’*’.
the table space or table space partition as specified in
the REORG TABLESPACE input statement. The fields System action:
from SYSTABLEPART are: Processing continues normally
DBNAME User response:
Database name
If the TIMESTAMP reported in the STATSTIME column
TSNAME is not recent, the LEAFDISTLIMIT criteria might be
Table space name evaluated with obsolete statistics.
PART Partition number Severity:
CARD Number of rows in table space 0 (informational)
FARINDREF
Number of rows relocated afar DSNU289I csect-name type REORG LIMITS HAVE
NEARINDREF BEEN MET
Number of rows relocated nearby Explanation:
STATSTIME The REORG utility is indicating whether any specified
TIMESTAMP of RUNSTATS update limits have been met. For REORG TABLESPACE, this
might be the OFFPOSLIMIT or the INDREFLIMIT. For
Rows which meet the INDREFLIMIT criteria are REORG INDEX, this is the LEAFDISTLIMIT. type
prefaced with ’*’. values:
System action: NO If no limits are met.
Processing continues normally blank If at least one limit is met.
User response: System action:
If the TIMESTAMP reported in the STATSTIME column Utility processing continues.
is not recent, the INDREFLIMIT criteria might be
evaluated with obsolete statistics. User response:
the OFFPOSLIMIT or the INDREFLIMIT. For REORG The reason code indicates the specific type of error:
INDEX, this is the LEAFDISTLIMIT. type values:
| 1 The job to which the -ALTER UTILITY
NO If no limits are met. | command applies is not executing REBUILD
| with SHRLEVEL CHANGE, REORG with
blank If at least one limit is met.
| SHRLEVEL REFERENCE, or REORG with
System action: | SHRLEVEL CHANGE.
Utility processing continues. A REORG is performed if | 2 The job to which the -ALTER UTILITY
any limits are met. | command applies is executing REORG with
| SHRLEVEL REFERENCE, but the -ALTER
Severity: | UTILITY command specifies MAXRO,
0 (informational) | LONGLOG, or DELAY.
| 3 The job to which the -ALTER UTILITY
DSNU291I MAXIMUM COMPOSITE UNLOAD | command applies is executing REBUILD with
RECORD SIZE TOO LARGE FOR | SHRLEVEL change, but the -ALTER UTILITY
SORT. SORTDATA KEYWORD IS | command specifies DEADLINE.
IGNORED. System action:
Explanation: -ALTER UTILITY does not execute.
The SORTDATA keyword was specified for a REORG User response:
utility job. However, the largest possible record in the
table space, prefixed by the largest key, produces a Apply -ALTER UTILITY to a job that is executing the
composite record that is too large to be processed by proper utility.
the SORT component. The SORTDATA keyword is
Severity:
ignored.
8 (error)
System action:
Processing continues normally.
DSNU293I csect-name - REORG WITH SHRLEVEL
User response: REFERENCE OR CHANGE CANNOT
APPLY TO THE name TABLE SPACE
If you must use SORTDATA for the table space, try
reducing the size of either the largest record or key Explanation:
field by redefining the table. In some cases, changing a
REORG with SHRLEVEL REFERENCE or CHANGE
field from LONG VARCHAR to VARCHAR with a
cannot operate on the following catalog and directory
specified maximum length might help.
table spaces: DSNDB06.SYSDBASE,
Problem determination: DSNDB06.SYSDBAUT, DSNDB06.SYSGROUP,
DSNDB06.SYSPLAN, DSNDB06.SYSVIEWS, and
This problem should only occur on a table space with a DSNDB01.DBD01.
32KB page size. Analyze the requirement for maximum
data length in VARCHAR and LONG VARCHAR System action:
columns to see if a shorter length can be specified. It
REORG does not execute.
might be necessary to remove the SORTDATA keyword
from the utility statement. User response:
Severity: Execute REORG with SHRLEVEL NONE.
0 Severity:
8 (error)
DSNU292I csect-name - -ALTER UTILITY CANNOT
APPLY TO THIS UTILITY, REASON=c
DSNU294I csect-name - LARGEST COMPOSITE
Explanation: RECORD IS TOO BIG FOR REORG
WITH SHRLEVEL CHANGE
| The -ALTER UTILITY command applies only to a job
| that is executing REBUILD with SHRLEVEL CHANGE, Explanation:
| REORG with SHRLEVEL REFERENCE, or REORG with
SHRLEVEL CHANGE was specified for a REORG
| SHRLEVEL CHANGE. In addition, if the -ALTER
utility job, and the table has a clustering index.
| UTILITY command specifies MAXRO, LONGLOG, or
However, the largest possible record in the table space,
| DELAY, the job must be executing REBUILD with
prefixed by the largest key, produces a composite
| SHRLEVEL CHANGE, or, REORG with SHRLEVEL
record that is too large to be processed by the SORT
| CHANGE.
component. See the computation of the length under
448 Messages
DSNU295I • DSNU296I
original name does not exist. This error For context code 7, define all shadow objects prior to
condition can arise for a DB2-managed or running REORG.
user-managed data set.
Severity:
2
4 (warning) or 8 (error)
During the switch phase of REORG, on
rename 2, REORG detected that a data set
DSNU297I csect-name COMPOSITE RECORD SIZE
with a shadow name does not exist. This error
TOO LARGE FOR table-name
condition can arise for a DB2-managed or
user-managed data set. Explanation:
During the switch phase restart or a -TERM The size of the record that would be unloaded for
UTILITY during the switch phase, on rename REORG DISCARD or REORG UNLOAD EXTERNAL is
5, REORG detected that a data set with a greater than the largest allowed data set logical record
shadow name does not exist. This error length (32760 bytes).
condition can arise for a DB2-managed or
user-managed data set. System action:
3 During the utilterm phase of REORG, on The utility will terminate with a return code of 8.
rename 3, REORG detected that a data set User response:
with a temporary name does not exist. This
error condition can arise for a user-managed If you are attempting to discard records during
data set. REORG, you will have to use SQL to DELETE the
records prior to the REORG. If you are attempting to
7 During initialization of REORG, REORG unload records in an external format, you must use an
detected that the shadow data set did not application instead. If you are using the SORTDATA
exist. This error can only occur with a table option with REORG UNLOAD EXTERNAL or REORG
space, index, or partition that is stored in DISCARD, try removing the SORTDATA keyword.
user-managed data sets.
Problem determination:
System action:
This problem will most likely occur only on a table
For context codes 1 or 2, utility processing is abended. with BLOB, CLOB, or DBCLOB columns.
ABEND reason code 00E4031B is issued. The object is
left in a recovery pending state. Severity:
For context code 3, the utility job step that caused the 8 (error)
function to be requested continues with no renaming.
The utility job is placed in the stopped state. The object DSNU298I csect-name - RESTART NOT ALLOWED
is left in a recovery pending state, and a message will IN phase-name PHASE OF REORG
be issued. WITH SHRLEVEL REFERENCE OR
For context code 7, REORG does not execute. CHANGE
450 Messages
DSNU299I • DSNU302I
452 Messages
DSNU306I • DSNU309I
Explanation: Severity:
The ’table-name’ identifies the target table of the job for 8 (error)
the LOAD utility or the dependent table to be checked
by the CHECK DATA utility. The ’parent-table-name’
DSNU309I csect-name NOT ALL REQUIRED
identifies the parent table of the target table for the
UNIQUE INDEXES HAVE BEEN
LOAD utility or the dependent table for the CHECK
DEFINED FOR TABLE table-name
DATA utility in RELATIONSHIP ’relationship-name’.
The primary index of PARENT TABLE Explanation:
’parent-table-name’ has been dropped.
The table ’table-name’ was created with unique index
This message is repeated for each incompletely defined requirements. Not all of these indexes have been
parent table in each relationship where the target table defined.
is a child.
System action:
System action:
Processing stops. No table in the table space is loaded.
The LOAD and CHECK DATA utilities stop further
User response:
processing. No data is loaded by the LOAD utility and
no relationships are checked by the CHECK DATA The user may resubmit the LOAD job after either:
utility. v Creating all the required unique indexes, or
User response: v Dropping the table and re-creating it without the
unique index requirements.
Check the existence of the primary index and its parent
tables identified by RELATIONSHIP Problem determination:
’relationship-name’.
Determine which unique indexes need to be created.
Determine if the uniqueness requirement for the table Following the completion of the current LOAD utility
is valid. invocation, examine the record in the DISCARDS data
set. Correct the error in the discarded input data, if one
Severity:
exists. Otherwise, correct the input field specification.
8 Submit a RESUME(YES) LOAD invocation, which uses
the DISCARDS data set and the verified LOAD utility
statement and field specifications. Refer to Utility Guide
DSNU310I csect-name RECORD ’n’ WILL BE and Reference for a definition of LOAD input field
DISCARDED DUE TO field-name column specifications.
CONVERSION ERROR FOR table-name
ERROR CODE cc Severity:
Explanation: 4 (warning)
454 Messages
DSNU314I • DSNU317I
The DISCARDS limit specified on the LOAD utility option. The RESUME(YES) option implies that the
statement was reached. specified partition ’nn’ is populated, but in this case it
was not. The message alerts the invoker to this fact,
System action:
and continues as if RESUME(YES) was not specified.
Processing abends to allow users to increase the discard
System action:
limit and restart the utility.
The LOAD utility, in attempting to honor the
User response:
RESUME(YES), found the partition was empty, ignored
Increase the discard limit and restart the utility. the option, and continued as if RESUME(NO) was
Otherwise -TERM the utility. Review the file of input specified.
records provided to LOAD and review table definitions
User response:
to determine why the number of records discarded
exceeds expectations. The user is alerted to the fact that the requested
partition was empty rather than populated as the
Problem determination:
RESUME LOAD option implied.
See user response.
Severity:
Severity:
4 (warning)
8 (error)
DSNU320I csect-name RESUME(YES) WAS
DSNU318I csect-name RECORD ’n’ WILL BE SPECIFIED FOR AN EMPTY
DISCARDED DUE TO INVALID TABLESPACE
field-name COLUMN SPECIFICATION
Explanation:
FOR table-name
RESUME(YES) was specified within the LOAD utility
Explanation:
statement. However, the RESUME(YES) option implies
The load utility calculated the location of an input data that the specified table space is populated.
value using the field specifications supplied and
System action:
VARCHAR length fields present within the input data
set record ’n’. The calculated position for the field was | Processing continues. The LOAD utility, in attempting
determined to be incorrect. | to honor the RESUME(YES), found the table space
| empty, so ignored the option, and proceeded as if
System action:
| RESUME(NO) was specified. If this table is currently
The input data set record number is noted and will be | defined as COMPRESS YES, a dictionary is not built,
discarded in the DISCARD phase. The LOAD utility | unless the tablespace is empty, in which case a
continues to process additional records in the input | compression dictionary will be built.
data set.
User response:
User response:
The user is alerted to the fact that the requested table
Following the completion of the current LOAD utility space was empty rather than populated as the
invocation, examine the record in the DISCARDS data RESUME LOAD option implied. Use the RESUME(NO)
set. Correct the error in the discarded input data, if one option if you want a compression dictionary built.
exists. Otherwise, correct the input field specification.
Severity:
Submit a RESUME(YES) LOAD invocation, which uses
the DISCARDS data set and the verified LOAD utility 4 (warning)
statement and field specifications. Refer to Utility Guide
and Reference for a definition of LOAD input field
DSNU321I csect-name CHECK PENDING ON
column specifications.
TABLESPACE tablespace-name
Severity: PROHIBITS PROCESSING
4 (warning) Explanation:
The requested utility cannot be run against a tablespace
DSNU319I csect-name RESUME(YES) WAS or tablespace partition in a check pending state.
SPECIFIED FOR EMPTY PARTITION
System action:
nn. RESUME(NO) IS ASSUMED
Processing terminates after the check pending states of
Explanation:
all target tablespaces or partitions of the utility are
This message is issued in response to a LOAD utility analyzed.
request containing a partition level RESUME(YES)
User response:
456 Messages
DSNU322I • DSNU325I
Remove the named tablespace or partition from its Resubmit the job if that is still appropriate.
check pending state by using the CHECK DATA or
Severity:
REPAIR utility. If you want more information on the
extent of questionable data in the table space, query the 8 (error)
SYSTABLES and SYSTABLEPART catalog tables.
Severity: DSNU324I csect-name DEFERRED STATUS OF
INDEX SPACE creator-name.index-name
8 (error)
PROHIBITS PROCESSING
Explanation:
DSNU322I csect-name DEFERRED STATUS OF
TABLE SPACE database-name.table-space- The requested utility cannot be run against an index
name PROHIBITS PROCESSING space or index space partition in a deferred state.
Explanation: System action:
The requested utility cannot be run against a table Processing terminates after the deferred state of all
space or table space partition in a deferred state. target index spaces or index partitions of the utility are
analyzed.
System action:
User response:
Processing terminates after the deferred state of all
target table spaces or table space partitions of the The deferred state can be removed through recovery or
utility are analyzed. rebuild of the index space or the physical index
partition. It can also be removed by the -START
User response:
DATABASE command with ACCESS(RW) or
To remove the deferred state, use the RECOVER ACCESS(RO). The RECOVER or REBUILD INDEX
TABLESPACE, LOAD REPLACE utility, or -START utility can be run at either the index space or index
DATABASE command with ACCESS(RW) or partition level. If more information on the status of the
ACCESS(RO). If you want more information on the index space is required, use the -DISPLAY DATABASE
status of the table space, use the -DISPLAY DATABASE command.
command.
Severity:
Severity:
8 (error)
8 (error)
DSNU325I csect-name - AN INVALID SQL/DS
DSNU323I csect-name COLUMN ccc IS OMITTED FORMAT RECORD WAS
ENCOUNTERED
Explanation:
Explanation:
The column ’ccc’ is a nonnullable column and is not
being loaded. Field specifications must include all The LOAD utility detected an invalid SQL/DS format
nonnullable columns. The identified column name was record type.
missing from the field specification.
System action:
System action:
Utility execution is terminated.
Further utility processing is terminated.
User response:
System programmer response:
Correct the input data and resubmit the job. Data that
Corrective procedures may require that a table be has been transmitted from an SQL/DS unload disk
dropped and created again. Refer to Part 2 of the data set in a VM/370 system may have extra block
Administration Guide for a discussion of how this can be descriptors and record descriptors at the beginning of
accomplished. Refer to Utility Guide and Reference for a each record. Ensure that this situation does not exist.
discussion of field specification constraints with regard
Problem determination:
to nonnullable columns.
Refer to Part 2 of the Administration Guide for
User response:
additional information regarding loading data from
Determine if the input data contains the nonnullable SQL/DS and resubmitting a partially completed load
column as a field. If it does, change the field step.
specification to include it. If the input data does not
Severity:
contain the nonnullable column as a field, determine
which is in error, the input data or the column 8 (error)
specification. Make the corresponding correction.
DSNU326I csect-name - USER NOT AUTHORIZED DSNU328I csect-name CANNOT PROCESS THE
FOR LOAD REPLACE ON NON-EMPTY PARTITION nn WITH
TABLESPACE RESUME(NO). PROCESSING
TERMINATES
Explanation:
Explanation:
The user attempted to use the REPLACE option of
LOAD, and it will reset to empty all tables in the table The partition level RESUME keyword either specified
space before loading data. This option requires load or defaulted to a value of NO, which requires the
authorization on each table in the table space, but the partition to be empty. However, the LOAD command
user did not have authority for one or more tables. In named partition ’nn’, which was not empty.
addition, if a table in the table space has a security
System action:
label column, the user must have the write-down
privilege when write-down is in effect. Further utility processing is terminated.
System action: System programmer response:
When LOAD REPLACE validation encounters the first Determine whether the partition should be empty. If it
non-authorized table in the table space, the job step is should, use SQL DELETE to empty it. Otherwise,
terminated. instruct the user to use the RESUME(YES) option for
that partition.
User response:
User response:
| Obtaining the LOAD on DATABASE privilege for the
| database will allow you to proceed using the REPLACE Determine why the assumption of an empty partition
| option. If the table space is an implicit database, then was wrong. This may require consultation with the
| obtain the appropriate authorization privileges on the system programmer. Either remove the current
| implicit database or DSNDB04. If a table in the table partition’s rows using an SQL DELETE, or change the
| space has a security label column, ensure that the user LOAD option to RESUME YES. Resubmit the job. Refer
| has write-down privilege when write-down is in effect to Utility Guide and Reference for a description of the
| before using the REPLACE option. The other partition-level RESUME option of LOAD.
| alternative is to first delete all rows from the tables
| which are to be loaded, and then use the RESUME Severity:
| option instead of the REPLACE option. 8 (error)
Severity:
12 (severe error) DSNU329I csect-name - FIELD field-name IS NOT
DEFAULTABLE
458 Messages
DSNU330I • DSNU333I
20 Input contained an invalid code point for a The LOAD utility found that the input field ’ffffffff’
required CCSID conversion. extends beyond the end of the input record.
21 Input does not conform to the rules for valid If DISCARDS processing is active, the message severity
data for a required CCSID conversion. is 4 (warning).
460 Messages
DSNU336I • DSNU339I
DSNU340I csect-name - ERROR LOADING INDEX, The DB2 catalog or directory table space being
DUPLICATE KEY, INDEX=index-name, reorganized does not have an image copy that the
TABLE=table-name, RID OF INDEXED RECOVER utility can use to recover the table space to
ROW=rid-of-indexed-row, RID OF currency. Before running the REORG utility, you must
NON-INDEXED ROW=rid-of-non-indexed- run the COPY utility to create an image copy. This
row prevents having to recover the DB2 catalog or directory
table space to a prior point in time if a problem occurs
Explanation: during REORG processing.
A duplicate key was found while building the indicated System action:
index during the BUILD phase of the REORG or
REBUILD INDEX utility. This violates the uniqueness Processing terminates
rule for that index.
User response:
System action:
Run the COPY utility to create an image copy of the
All duplicate index entries of the indicated index are DB2 catalog or directory table space. If more than one
reported and the index is in RECOVERY PENDING catalog or directory table space is to be reorganized,
status. Duplicate rows are present in the indexed table. consider using the QUIESCE and COPY utilities for the
set of table spaces to be reorganized.
Utility processing continues with any other utility
functions within the utility job step. Use the REPORT utility to view the recovery
information related to the table space. The output from
Operator response: the REPORT utility should indicate either the absence
Notify the system programmer. of an image copy, or the presence of a REORG LOG
NO SYSCOPY record.
System programmer response:
Severity:
Steps should be taken to inhibit any further processing
until the index is repaired. If the nonunique keys are 8
correct, DROP and recreate the index as nonunique. If
the records with duplicate keys should not be in the DSNU342I csect-name ERROR LOADING INDEX,
table, use REPAIR DELETE to remove the erroneous ERROR = Xreason-code, INDEX =
rows. Use the RID values provided in this message as index-name
input to the REPAIR utility. After the duplicate data
rows are removed or the unique index has been Explanation:
dropped, issue the -DISPLAY DATABASE command
The LOAD, REORG or REBUILD INDEX utility
with RESTRICT against the target database. Use the
encountered a processing error, which it could not
REBUILD INDEX utility to recover any indexes that are
correct, while extending the index identified by
in the REBUILD pending state. CHECK INDEX can be
’index-name’. The reason code is described in Codes.
run to verify that the data and indexes are consistent.
System action:
User response:
The building of index entries for the indicated index is
Duplicate rows are present in the indexed table. The
not completed. An SVC dump of the database services
system programmer should be informed, so that any
address space is requested for diagnostic purposes. The
applications that are dependent upon the uniqueness of
extension of other indexes associated with the tables
the table rows are not initiated until corrective action
being loaded is attempted. Any subsequent attempt to
has been taken.
use the index directly or indirectly will cause the
Problem determination: invoker to abend.
Use REPAIR LOCATE RID DUMP to view the records Operator response:
with duplicate keys. SQLSELECT may fail due to the
The table space in question might need to be stopped
inconsistent index. Use CHECK INDEX to check the
and started for utility-only processing to inhibit
validity of the index.
attempted application use of the defective index.
Severity:
System programmer response:
8 (error)
If the index is used by more than one application,
462 Messages
DSNU343I • DSNU346I
User response: UTILITY command would reflect the results (if any) of
the -ALTER UTILITY command.
When discard processing is specified, examine the
records in the DISCARDS data set after the LOAD Severity:
utility completes. Correct the error in the discarded
0 (informational)
input data. Then run the LOAD utility with the
RESUME YES option using the DISCARDS data set as
input. When discard processing is not specified, correct DSNU348I csect-name BUILD PHASE STATISTICS.
the error in the input data set and rerun the job. NUMBER OF KEYS = nnnnnnnn FOR
INDEX index-name PART part-num
Problem determination:
Explanation:
Collect the following diagnostic items:
v Console output from the system on which the job This message is issued by the BUILD phase of the
was run, and a listing of the SYSLOG data set for the REBUILD INDEX utility to report the total number of
period of time spanning the failure. index key entries used to build the indicated index
partition.
v Dynamic dump, taken to SYS1.DUMPxx data set, by
DB2 (04E and 04F abends). System action:
v Listing of SYS1.LOGREC data set, obtained by This message indicates the number of index key entries
executing IFCEREP1. submitted to the DB2 data manager to build the
Severity: indicated index partition. Both unique and nonunique
key entries are counted. Rejected key entries are not
4 or 8 counted.
User response:
DSNU347I csect-name DEADLINE =
yyyy-mm-dd-hh.mm.ss.mmmmmm The user can verify that the number reported is
consistent with expectations.
Explanation:
Severity:
This message applies only to REORG with SHRLEVEL
REFERENCE or CHANGE. It supplements message 0 (informational)
DSNU105I, which can appear for any utility (including
REORG). DSNU349I csect-name BUILD PHASE STATISTICS.
This message is issued in response to a -DISPLAY NUMBER OF KEYS = nnnnnnnn FOR
UTILITY command. index-name
464 Messages
DSNU350I • DSNU355I
466 Messages
DSNU360I
and processing continues normally. shadow name (for user-managed data sets). It
deletes the temporary for DB2-managed data
System action:
sets.
Processing continues normally.
If a -TERM UTILITY command is issued after any
User response:
renaming, or a restart of the REORG switch phase
If an index or foreign keys were expected to be found occurs after any renaming, the data set names revert
for the table or tables being loaded or reorganized, back to their original form prior to the renaming:
determine the reason the index or foreign keys could
4 The original data set from the shadow name to
not be found.
the temporary name
Problem determination:
5 The shadow data set from the original name to
Probably a user error. Determine if an index should be the shadow name
defined on any of the tables in the table space, or if
6 The original data set from the temporary name
foreign keys should be defined. If so, define the index
to the original name
or foreign keys; otherwise, remove the ’SORTKEYS’
keyword from the utility statement if necessary.
The context code indicates the specific type of error:
Severity:
1 During the switch phase of REORG, on
0 (informational) rename 1, REORG detected that a data set
with a temporary name already exists. This
error condition can arise for a DB2-managed
DSNU360I csect-name - IN REORG WITH
or user-managed data set.
SHRLEVEL REFERENCE OR CHANGE,
DATA SET name EXISTS, CONTEXT=c 2 During the switch phase of REORG, on
rename 2, REORG detected that a data set
Explanation:
with a original name already exists. This error
For the area (table space or partition) being condition can arise for a DB2-managed or
reorganized, REORG with SHRLEVEL REFERENCE or user-managed data set.
CHANGE unloads data from the original data sets and
3 During the utilterm phase of REORG, on
reloads data into shadow data sets. REORG then
rename 3, REORG detected that a data set
exchanges the names of the original and shadow data
with a shadow name already exists. This error
sets, using temporary names during the renaming. The
condition can arise for a user-managed data
original name of a data set is in the form
set.
“catname.DSNDBx.dbname.psname.I0001.Annn”. The
shadow name of a data set is in the form 4 During switch phase restart or a -TERM
“catname.DSNDBx.dbname.psname.J0001.Annn”. The UTILITY during the switch phase, on rename
temporary name of a data set is in the form 4 (while reverting back to the original name),
“catname.DSNDBx.dbname.psname.T0001.Annn”. REORG -TERM UTILITY detected that a data set with
uses such data sets for indexes as well as data. a temporary name already exists. This error
condition can arise for a DB2-managed or
During its initialization, REORG cannot execute if:
user-managed data set.
v Data sets with the temporary names already exist.
5 During switch phase restart or a -TERM
v DB2-managed data sets with the shadow names
UTILITY during the switch phase, on rename
already exist.
5 (while reverting back to the original name),
v User-managed data sets with the shadow names do -TERM UTILITY detected that a data set with
not already exist. a shadow name already exists. This error
condition can arise for a DB2-managed or
To exchange the names of the original and shadow data user-managed data set.
sets, REORG performs the following renaming:
6 During switch phase restart or a -TERM
1 In the switch phase, it renames the original UTILITY during the switch phase, on rename
data set from the original name to the 6 (while reverting back to the original name),
temporary name -TERM UTILITY detected that a data set with
a original name already exists. This error
2 In the switch phase, it renames the shadow
condition can arise for a DB2-managed or
data set from the shadow name to the original
user-managed data set.
name
8 During initialization of REORG, REORG
3 In the utilterm phase, it renames the original
detected that a data set with a temporary
data set from the temporary name to the
name already exists. This error condition can Input record nnnn caused a row to be loaded into table
arise for a DB2-managed or user-managed table at RID rrrr with no primary key for the
data set. relationship with the name r1.
System action: System action:
For context code 1, or 2, the utility job step that caused Processing continues.
the function to be requested abends with code
User response:
00E4031B. The utility job is placed in the stopped state.
None required. The constraint violation described will
For context code 3, the utility job step that caused the
be rectified later in processing.
function to be requested continues without performing
this renaming. Severity:
For context code 4, 5, or 6, the object is left in a 4 (warning)
recovery pending state, -TERM UTILITY continues to
undo renaming, and a message is issued. The objects
and messages are as follows: DSNU362I csect-name - IN utility WITH SHRLEVEL
CHANGE, LOG HAS BECOME SHORT,
v If the data set is part of a nonpartitioned table space, BUT MAXRO IS DEFER,
the object is the table space, and the message is MEMBER=member-name, UTILID=utilid
DSNU562I.
v If the data set is part of a partition of a table space, Explanation:
the object is the partition, and the message is | When you execute utility with SHRLEVEL CHANGE,
DSNU560I. | DB2 will add a five second pause to the next iteration,
v If the data set is part of a nonpartitioned index, the | if the value of MAXRO is DEFER, and the actual time
object is the index, and the message is DSNU557I. | for an iteration and the estimated time for the next
v If the data set is part of a partition of a partitioned | iteration are both less than five seconds. This pause
index, the object is the partition of the index, and the | limits the utility’s consumption of processor time.
message is DSNU559I. | Within an execution of the utility, the first time that this
| situation occurs, DB2 produces this message, which
For context code 8, REORG does not execute. | announces the pause. On all later occurrences of this
| situation, DB2 still adds the pause, but DB2 sends the
User response:
| message only if DB2 has not sent the message (for this
For context code 1 or 2, you can choose between these | execution of the utility) within the past 30 minutes.
actions:
| WTO This message is sent to the console, but it is
v Delete the data set; then RESTART the utility. | not an action message. It is not sent to
v TERM the utility. Delete the data set before trying to | SYSPRINT.
execute REORG again with SHRLEVEL REFERENCE
| member-name
or CHANGE.
| In a data sharing environment, member-name
| identifies the DB2 member. In a non-sharing
For context code 3, if you want to perform the
| environment, member-name is blank. The
renaming, delete the data set with the shadow name
| variable of utilid identifies the utility job step.
and then perform the renaming.
System action:
For context code 4, 5, or 6, execute the RECOVER or
| The utility continues execution, with a five second
REBUILD INDEX utility; then delete the shadow and
| pause. If the conditions in the explanation above
temporary data sets (if they still exist).
| continue to be true, DB2 continues to add five second
| pauses.
For context code 8, delete the data set and then execute
REORG. Operator response:
Severity: You are not required to take any action at this time, but
if you were planning to wait for an appropriate time to
8 (error) execute the -ALTER UTILITY command to increase the
value of MAXRO and thus cause the utility to finish,
DSNU361I csect-name FOREIGN KEY HAS NO now might be an appropriate time to execute.
PRIMARY KEY FOR User response:
RELATIONSHIP=r1 INPUT RECORD
NUMBER=nnnn, RID=Xrrrr | You are not required to take any action at this time, but
| if you were planning to wait for an appropriate time to
Explanation: | execute the -ALTER UTILITY command to choose the
468 Messages
DSNU363I • DSNU367I
report phase will report all secondary errors and System action:
indicate the primary error record which caused this
The statement cannot be executed.
record to be deleted.
System programmer response:
The relevant parent table can be found by querying the
SYSIBM.SYSRELS catalog table. The relevant columns To replace the DB2-supplied exit routine, an SMP
can be found by querying the USERMOD must be applied. If an SMP USERMOD is
SYSIBM.SYSFOREIGNKEYS catalog table. undesirable, the replacement module may be linked
into a user library either included in the MVS
Severity:
LINKLIST or concatenated to the STEPLIB in the
4 (warning) started task JCL for ssnmDBM1 (ssnm is the subsystem
name).
DSNU368I csect-name - REORG MAPPING TABLE User response:
HAS WRONG INDEX
Contact the system programmer about installation of
Explanation: the date or time exit.
A mapping table was specified for a utility job Severity:
executing REORG with SHRLEVEL CHANGE.
8 (error)
However, the table has the wrong index. This message
can arise for any parameters of CREATE INDEX that
are missing from, added to, or different from the DSNU371I csect-name - REORG MAPPING TABLE’S
CREATE INDEX statement that appears for the TABLE SPACE MUST BE SEGMENTED
mapping table in the REORG section of Utility Guide
and Reference. It can also arise for the existence of any Explanation:
other indexes on the mapping table. REORG with SHRLEVEL CHANGE specified a
System action: mapping table for a table space that is not segmented.
The table space that contains the mapping table must
REORG does not execute. be segmented.
User response: System action:
Create a mapping table with the correct index, and no REORG does not execute.
other indexes, as specified under REORG in Utility
Guide and Reference. Execute REORG. User response:
470 Messages
DSNU373I • DSNU377I
| 2
DSNU373I csect-name - IN -ALTER UTILITY OR
REORG WITH SHRLEVEL REFERENCE | v On SHRLEVEL CHANGE, attempt a new
OR CHANGE, DEADLINE HAS | invocation of reorganization later, perhaps
ALREADY OCCURRED, CONTEXT=c | when you expect to have a longer time
| available, you expect that the application
Explanation: | workload is lower, or you expect that the
If a deadline is specified in the -ALTER UTILITY | maximum needed amount of time for
command or the REORG utility with SHRLEVEL | applications to have read-only access is
REFERENCE or CHANGE, the deadline cannot occur | longer.
before the time of execution of the -ALTER UTILITY or | v On SHRLEVEL REFERENCE, attempt a new
REORG that specified the deadline. Context codes are: | invocation of reorganization later, perhaps
| when you expect to have more time
1 The error occurred on -ALTER UTILITY.
| available.
2 The error occurred on REORG.
Severity:
System action:
8 (error)
-ALTER UTILITY or REORG does not execute.
User response: DSNU375I csect-name DISCARD PHASE
STATISTICS - nnn INPUT DATA SET
Execute -ALTER UTILITY or REORG with no deadline RECORDS DISCARDED
or with a deadline that has not already occurred. If you
want to terminate an execution of REORG, use the Explanation:
-TERM UTILITY command.
Input data set records were rejected by the LOAD
Severity: utility for one or several reasons. The rejected records
have been placed in a discards data set. The number of
8 (error) records rejected is ’nnn’. Message DSNU399I
summarizes the errors causing the records to be
DSNU374I csect-name - utility WITH SHRLEVEL rejected.
REFERENCE or CHANGE HAS BEEN System action:
TERMINATED, REASON=c
Processing continues.
| Explanation:
User response:
| The utility with SHRLEVEL REFERENCE or CHANGE
| has been terminated. Examine the LOAD error summary and decide which
of the discarded records, if any, should be corrected
| The reason code indicates the specific type of error: and reapplied to the table space.
| 1 The utility with SHRLEVEL CHANGE Severity:
| specified LONGLOG TERM, and at the end of
| an iteration of log processing, the number of 4 (warning)
| log records that the next iteration would
| process is not sufficiently lower than the
DSNU376I csect-name DISCARD PHASE
| number that the previous iterations processed.
COMPLETE, ELAPSED TIME =
| 2 DB2 estimated that the switch phase of hh/mm/ss
| REORG with SHRLEVEL REFERENCE or
Explanation:
| CHANGE would not start by the deadline
| specified in the DEADLINE phrase. The DISCARD phase of the LOAD utility has
completed normally. The elapsed time for the execution
| System action: was ’hh’ hours, ’mm’ minutes, and ’ss’ seconds.
| The utility terminates. Severity:
| User response: 0 (informational)
| The user can proceed with the following actions, based
| on the reason code received: DSNU377I csect-name - IN utility WITH SHRLEVEL
| 1 Attempt a new invocation of the utility later, CHANGE, THE LOG IS BECOMING
| perhaps when you expect that the application LONG, MEMBER=member-name,
| workload is lower or the maximum needed UTILID=utilid
| amount of time for applications to have
Explanation:
| read-only access is longer.
| During log processing for utility with SHRLEVEL REORG with SHRLEVEL NONE allows the following
| CHANGE, the number of log records that the next combinations of the SORTDATA and NOSYSREC
| iteration is to process is not sufficiently lower than the keywords:
| number that the previous iterations processed. When v Neither keyword
| you executed the utility, the log was not read quickly v SORTDATA alone (without NOSYSREC)
| enough to catch up to the application that is writing
v SORTDATA NOSYSREC
| the log. This is a WTO message; it is sent to the
| console, but it is does not require any user action. The These combinations do not trigger this message.
| message is also sent to SYSPRINT. However, NOSYSREC alone (without SORTDATA) is
inappropriate and triggers this message with a reason
DB2 refrains from taking the specified action in the
code of 1.
LONGLOG phrase if any one of the following events
occur for this execution of the utility before the delay
Also, for REORG with SHRLEVEL NONE, if you
expires:
specify UNLOAD PAUSE, UNLOAD ONLY, or
v You issue an -ALTER UTILITY command. UNLOAD EXTERNAL, NOSYSREC is inappropriate
v You issue a -TERM UTILITY command. and triggers this message with a reason code of 2. If
v DB2 estimates that the time to perform the next the two conditions (omission of SORTDATA and
iteration is less than or equal to the time specified in inclusion of UNLOAD PAUSE, ONLY, or EXTERNAL)
the MAXRO phrase. are both true, NOSYSREC triggers this message with a
reason code of 2.
v The utility terminates for any reason (including the
deadline). System action:
member-name REORG does not execute.
| Identifies the DB2 member in a data sharing
User response:
| environment. It is blank in a non-data-sharing
| environment. Specify an invocation of REORG with appropriate
parameters. Specifically, for reason code 1, if you want
utilid Identifies the utility job step.
to execute REORG with SHRLEVEL NONE, add
System action: SORTDATA and/or remove NOSYSREC. For reason
code 2, if you want to execute REORG with SHRLEVEL
| After a delay (specified by the DELAY phrase of the
NONE, remove NOSYSREC, UNLOAD PAUSE,
| utility or the -ALTER UTILITY command), the REORG
UNLOAD ONLY, or UNLOAD EXTERNAL .
| utility performs the action specified by the LONGLOG
| phrase of the REORG utility or the -ALTER UTILITY Severity:
| command.
8 (error)
Operator response:
No action is required. However, if the action specified DSNU379I csect-name - ALTER UTILITY, UTILID =
by the LONGLOG phrase is not what you wanted, the utilid: SWITCH PHASE IN REORG HAS
operator (or a user-written program that is triggered by ALREADY STARTED, NO ALTER IS
the message) can take an action. For a list of possible PERFORMED
actions, see the description of LONGLOG in the
Explanation:
REORG section of Utility Guide and Reference.
The -ALTER UTILITY command was applied to a job
User response:
that is executing REORG with SHRLEVEL REFERENCE
No action is required. However, if the action that is or CHANGE. However, nothing was altered, because
specified by the LONGLOG phrase is not what you REORG had already started its switch phase.
want, the operator (or a user-written program that the
System action:
message triggers) can take an action.For a list of
possible actions, see the description of LONGLOG in ALTER UTILITY has no effect.
the REORG section of Utility Guide and Reference.
Severity:
472 Messages
DSNU380I • DSNU383I
An image copy is required to establish a new base from This message applies only during the LOG phase of
which the table space can be recovered. Otherwise, the REORG with SHRLEVEL CHANGE. It supplements
results of running the RECOVER utility on that table message DSNU105I which can appear in any phase
space are unpredictable. (including the LOG phase).
The message reflects the state of DB2 at the time of the Severity:
-DISPLAY UTILITY command or the time when DB2
0 (informational)
estimated that the switch phase would not start by the
deadline specified by the DEADLINE phrase.
DSNU385I csect-name - LOG PHASE COMPLETE,
If this message was issued for -DISPLAY UTILITY, the
ELAPSED TIME = hh/mm/ss
system continues processing. A subsequent -DISPLAY
UTILITY command reflects that processing. | Explanation:
Severity: | This message is issued at the normal completion of the
| LOG phase of the utility. The time that has elapsed
474 Messages
DSNU386I • DSNU392I
476 Messages
DSNU398I
VIRTUAL STORAGE The utility step is abended with a system X’04E’ with
Increase the amount of virtual storage an abend reason code of ’00E40318’. If a DSNT500I
available to the utility job by specifying a message is not issued, an SVC dump is requested. A
larger region size in the job JCL, altering the SYSABEND dump of batch storage is also requested.
JES defaults for region size, or changing the The utility step is left in the stopped state.
system IEFUSI exit to allow a larger virtual
region. Operator response:
If the utility is using BSAM data sets for An operator with SYSOPR authority can issue a TERM
which the number of buffers have been UTIL to free any held resources (this may not be
specified (BUFNO specified in the DCB field necessary).
of the DD statement for the data set), consider System programmer response:
reducing the number of buffers.
If you suspect an error in DB2, refer to Diagnosis Guide
VIRTUAL STORAGE BELOW and Reference for information on identifying and
If possible, increase the amount of virtual reporting the problem.
storage below the line available to the utility
job by specifying a larger region size in the job User response:
JCL or reducing the number of data sets If a DSNT500I message was issued, refer to its
allocated in the job step. It might not be description under that message number in this manual.
possible to relieve this constraint. If the unavailable resource becomes available, the
DD STATEMENTS utility step is restartable.
Define additional groups of sort work data If a DSNT500I message is not issued, the error is an
sets, or eliminate the SWnnWKmm DD internal error. Notify the system programmer.
statements and specify the SORTDEVT
keyword (and, optionally, the SORTNUM Severity:
keyword) to allow SORT to use dynamic
8 (error)
allocation of its work data sets.
If the limitation is due to sort message data
sets rather than sort work data sets, define
additional sort message DD statements or
eliminate the UTPRINnn DD statements and
v Check constraint
DSNU399I csect-name - LOAD UTILITY ERROR
SUMMARY REPORT name2 The name of the field or fanset involved in the
error reported on this line, if this information
Explanation:
is pertinent for the type of error reported.
| This message summarizes errors detected during the Otherwise, name2 is blank. This field contains
| load job. The report contains one line for each error. a field name for the following types of errors:
| The errors are listed first by error severity and within v Conversion
| that by idsrn.
v Field specification
The report fields have the following meanings: v Column specification.
sev
For primary referential integrity errors, name2
The severity of the error reported on this line: is a relationship name. For check constraint
errors, name2 is a check constraint name.
Severity Type of Explanation
error idsrn2 The input data set record number of a related
1 Primary Primary referential integrity error. For duplicate key errors, it gives the
errors and all nonreferential input data set record number of the record
integrity errors. whose key is duplicated. For secondary
2 Secondary Secondary referential referential integrity errors, it gives the input
integrity errors (that is, data set record number of the record whose
errors that result from a primary referential integrity error cascaded to
primary referential integrity cause this secondary error. For other types of
error in an ancestor). errors, this field is unused.
System action:
idsrn The relative record number in the input data Processing continues.
set of the record causing the error reported on
this line. Severity:
ddsrn The relative record number in the input data 4 (warning)
set of the record causing the error reported on
this line, if discard processing is in effect.
DSNU400I csect-name COPY PROCESSED FOR
Otherwise, ddsrn is blank.
obj-type obj-qual.obj-name NUMBER OF
type A description of the type of error reported on PAGES=nnnnnn AVERAGE PERCENT
this line, as follows: FREE SPACE PER PAGE = ff.ff
v Conversion PERCENT OF CHANGED PAGES =
pp.pp ELAPSED TIME= hh/mm/ss
v Field specification
v Validation Explanation:
v Part Specification This is an informational message to report the copy
v Unexpected statistics. This message is issued by the COPY utility,
and it can also be issued from LOAD or REORG if a
v Column specification full image copy has been requested during a table
v Referential integrity space load or reorganization. The statistics apply to
v Check constraint pages included in the scope of the COPY request. This
can either be a full table space, full index space
v Duplicate key
(DSNUM(ALL)) or a partition (DSNUM(integer)). All
| v Key evaluation error the pages in the table space, index space, or partition
| v XML document error can be copied (FULL(YES)), or only the changed pages
can be copied (FULL(NO)). The message variables are:
name1 The name of the table for which the record
causing the error was targeted, if this ff.ff The average percentage of free space within
information is pertinent for the type of error the copied pages. This indicates the amount of
reported on this line. Otherwise, name1 is change activity that can occur without
blank. This field has nonblank values for the significant impairment of reference
following error types: performance.
v Conversion nnnnnn The number of pages written out.
v Validation
Image copies produced during LOAD or
v Column specification REORG will have more pages written than a
v Referential integrity (primary). full image copy produced by running the
478 Messages
DSNU401I • DSNU403I
COPY utility on the same table space, because An incremental image copy for a table space or data set
some pages will be written more than once. was requested. However, a full image copy is required.
Possible reasons include:
pp.pp The percentage of changed pages. This
indicates the amount of change activity that v The request was for one of the DB2-maintained table
occurred since the last image copy or spaces DSNDB01.DBD01, DSNDB06.SYSCOPY, or
reorganization. The percentage of changed DSNDB01.SYSUTILX.
pages is obtained by dividing the number of v A LOAD or REORG utility was run on the table
changed pages by the number of pages in the space or data set with no subsequent full image copy.
object. Preformatted pages consisting of all v No full image copy was found for the requested
zeros are included in the count of pages sites.
scanned. Since these preformatted pages are
v Copy pending status was set for the requested table
not copied to the output data set, the number
space or data set.
of pages scanned is usually larger than the
number of pages copied. v The request was for an entire table space, but the
most recent image copy for the table space is on the
When this message is issued for image copies data set level.
produced during LOAD or REORG, this
v The previous image copy is a DFSMS concurrent
percentage will always be reported as 100%,
copy.
because the utility is resetting and
reformatting the entire table space.
The request for an incremental image copy is ignored,
System action: and a full image copy is taken.
The COPY, LOAD or REORG utility continues System action:
processing this message is for information only.
Message DSNU428I will be issued when the copy The request to take an incremental image copy is
processing is complete. treated as a request to take a full image copy.
Reported statistics could suggest that either a The capacity of the target image copy data set might
RUNSTATS or REORG utility should be run on the not be sufficient if its size was established assuming an
table space. incremental image copy. If this condition occurs,
terminate and then resubmit the job step.
Use the SQL SELECT command to look at the 1. If the requested copy is made for current site, then
SYSIBM.SYSCOPY table. If the conflicting image copy the other site can only do point in time recovery.
data sets on the output tape are no longer needed, use 2. If the requested copy is for the site other than the
MODIFY RECOVERY to eliminate the related current site, then the TABLESPACE will be in the
SYSIBM.SYSCOPY records. If the data sets are still same state as before COPY has been made.
needed, you must place the new image copy on a
different tape or you must take a FULL image copy. System action:
DSNU404I csect-name LOCAL SITE AND Take another full image copy of the TABLESPACE for
RECOVERY SITE INCREMENTAL both LOCAL site and RECOVERY site to guarantee the
IMAGE COPIES ARE NOT correct recovery on both sites or check DSNZPARM to
SYNCHRONIZED FOR obj-type ensure that the current site is the site at which the
obj-qual.obj-name image copy is being taken.
Explanation: Severity:
480 Messages
DSNU409I • DSNU412I
For copies to DASD or MSS, fseq is 0; for copies of becomes available for reuse.
cataloged data sets, vol is (CATG).
Because no output was produced, the
System action: SYSIBM.SYSCOPY catalog table remains unchanged.
The utility terminates with return code 8 and does not The requester may want to determine why the
take the image copy or update the SYSCOPY table. apparent assumption that a change occurred was not
true.
User response:
Operator response:
Use the information provided to change the name of
the data set or to locate the duplicate SYSCOPY record The target copy data set identified by the DD statement
for deletion with the MODIFY RECOVERY utility. nominated by the COPY COPYDDN option was not
required. It was not tracked in the DB2 catalog table
Severity:
SYSIBM.SYSCOPY. It need not be kept for subsequent
8 (error) re-call.
Severity:
DSNU409I csect-name NO hardware-or-software
4 (warning)
SUPPORT FOR obj-type obj-qual.obj-name
This message reflects a warning condition that did not
Explanation:
prevent subsequent processing.
This message is issued by the COPY or RECOVER
utility for one of the following reasons.
DSNU411I csect-name UNABLE TO LOGICALLY
v The COPY utility was invoked to take a DFSMS COMPLETE obj-type obj-qual.obj-name
concurrent copy of a table space or index space that RETURN CODE return-code REASON
resides on a device with no hardware or software CODE reason-code
support for the DFSMSdss™ DUMP command with
the CONCURRENT option. Explanation:
v The RECOVER utility invoked the DFSMSdss The DFSMSdss DUMP command with the
RESTORE command without the supporting CONCURRENT option encountered an error during the
software. initialization of the target object being copied. The
return code and reason code are from the DFSMSdss
System action:
DUMP command.
The RECOVER utility falls back to the previous image
System action:
copy data set and continues. The COPY utility job
terminates. The utility job terminates.
User response: User response:
If a list of objects is specified in the COPY job, remove See the return code and reason code in z/OS DFSMSdss
the object that has no hardware or software support Storage Administration Reference to determine the
from the list. Resubmit the job or use the DB2 COPY problem. Resubmit the job after resolving the problem.
utility instead of the DFSMS Concurrent Copy utility.
Severity:
Severity:
8
4 (for RECOVER) or 8 (for COPY)
DSNU412I csect-name UNABLE TO PHYSICALLY
DSNU410I csect-name obj-type obj-qual.obj-name COMPLETE obj-type obj-qual.obj-name
CONTAINED NO CHANGED PAGES RETURN CODE return-code
Explanation: Explanation:
An incremental image copy (COPY option FULL(NO)), The DFSMSdss DUMP command with the
which copies only changed pages, was requested. CONCURRENT option encountered an error during the
However, no changed pages were found. backup process. The return code is from the DFSMSdss
DUMP command.
System action:
System action:
This message indicates normal completion of the image
copy utility. Processing continues to the next utility The utility job terminates.
statement in the utility job step, if any. If there are no
User response:
more utility statements, the utility job step is normally
terminated, and the resources are released to their prior See the return code description in z/OS DFSMSdss
availability state. The UTILID of the utility job step Storage Administration Reference to determine the
482 Messages
DSNU418I • DSNU423I
System action:
DSNU423I csect name CANNOT TAKE
The COPY utility completes unsuccessfully with return CONCURRENT COPY WITH
code 8. SHRLEVEL CHANGE OPTION FOR
obj-type obj-qual.obj-name WITH
System programmer response:
GREATER THAN 4KB PAGE SIZE
You must take a full image copy of the entire table
Explanation:
space by specifying the DSNUM ALL option with the
COPY utility. The DFSMS Concurrent Copy utility is serialized at the
extent level. The greater than 4KB page size condition
Severity:
might span more than one extent. This might cause the
8 (error) output data set to contain inconsistent data.
System action:
DSNU420I csect-name INCORRECT SHARE LEVEL
The COPY utility completes unsuccessfully with return
SPECIFIED FOR TABLE SPACE
code 8.
database-name.tablespace-name DSNUM
dsnum System programmer response:
Explanation: You must take a concurrent copy with the SHRLEVEL
REFERENCE option or a DB2 image copy if you prefer
When copying a table space that is not recoverable, the
the SHRLEVEL CHANGE option.
share level (SHRLEVEL) must be REFERENCE.
Convert the data set attribute Control Interval size of
If the object is an entire table space, ’DSNUM dsnum’ is
the associated tablespace from the 4K Control Interval
not displayed.
into the one that matches the page size. DB2 Utilities
System action: REORG Tablespace, LOAD with REPLACE, and
RECOVER can be used to convert the table space.
Utility processing is terminated.
Severity:
User response:
8 (error)
Correct the SHRLEVEL to REFERENCE, and resubmit
the COPY utility in a new utility job step. Refer to
Utility Guide and Reference for a discussion of COPY
utility constraints.
Severity:
Explanation: | Explanation:
| You must recover the partitioned object at the partition
| level. You may receive this message if you are using
484 Messages
DSNU430I • DSNU434I
| COPY with the CONCURRENT option. The use of | the number of data sets to be processed exceeds the
| online REORG (SHRLEVEL REFERENCE or CHANGE) | DFSMSdss RESTORE command limitation of 255. DB2
| has created a mixture of ’I0001’ and ’J0001’ instance | dynamically allocates a temporary filter data set for the
| nodes (fifth qualifier) for the underlying LDS’s for the | object and generates a DFSMSdss RESTORE command
| partitions of this object. | with the FILT option.
System action: | System action:
Utility processing continues. | If the utility job step includes an OPTIONS control
| statement with the EVENT(ITEMERROR,SKIP) option,
Severity:
| the utility processes the next item in the list. Otherwise,
0 (informational) | utility processing stops with return code of 8.
| User response:
| DSNU430I csect-name - ERROR ALLOCATING
| Correct the error that prevents dynamic allocation and
| TEMPORARY FILTER FOR obj-type
| resubmit the utility job. If dynamic allocation is not
| obj-qual.obj-name DSN=name
| possible, remove be possible, remove the
| CODE=X’reason-code’
| CURRENTCOPYONLY option on the RECOVER utility
| Explanation: | statement.
| Severity: | 4 (warning)
| 8 (error)
DSNU434I csect-name - TEMPLATE template-name
HAS THE STACK YES OPTION ON
| DSNU431I csect-name - ERROR ALLOCATING dd-name DATA SET WHICH IS NOT
| TEMPORARY FILTER FOR obj-type SUPPORTED FOR utility-name.
| obj-qual.obj-name DSNUM=name
Explanation:
| CODE=X’reason-code’
Template processing has detected tape stacking on an
| Explanation:
output data set which is not supported.
| An error returned during the dynamic allocation of a
System action:
| temporary filter data set. This message is followed by
| text that explains reason-code. If the utility job step includes an OPTIONS control
statement with the EVENT(ITEMERROR,SKIP) option,
| The RECOVER utility was run with the
the utility processes the next item in the list. The utility
| CURRENTCOPYONLY option and has detected that
will end with RC8 and subsequent utility statements in
the job step are not executed. Otherwise, if | If the phase-name is DUMPCOPY, then all of the dump
EVENT(ITEMERROR,HALT) is specified or defaulted | format copies for the objects were generated from the
to, the utility processing stops immediately with a | fast replication copies that were created in the
return code of 8 and subsequent utility statements in | FASTCOPY phase (fff).
the job step are not executed.
| If the phase-name is COPY, then one or more of the
User response: | fast replication copies was not successful. The dump
| format copies for those objects were generated from the
Remove the STACK YES option from the TEMPLATE
| DB2 data sets (dddd). The dump format copies for the
statement, then resubmit the job.
| objects that were successfully fast replicated were
Severity: | generated from the fast replication copies (fff). If
| SHRLEVEL(REFERENCE) was specified, then the total
8 (error) | time that the objects copied from DB2 data sets (dddd)
| were not available for application updates, is given in
| DSNU435I csect-name FASTCOPY PHASE | ’hh/mm/ss’ format.
| STATISTICS: TOTAL NUMBER OF | System action:
| OBJECTS PROCESSED = nnnn
| NUMBER OF OBJECTS THAT WERE | The COPY utility continues processing.
| FAST REPLICATED = ssss NUMBER OF
| Programmer response:
| OBJECTS THAT COULD NOT BE FAST
| REPLICATED = ffff ELAPSED TIME = | If phase-name is COPY, then examine the DSNU435I
| hh/mm/ss | message.
| Explanation: | Severity:
| This message is issued at the completion of the | 0 (informational)
| FASTCOPY phase for the COPY utility. The message
| indicates to the user the total number of objects that
DSNU440I csect-name IMAGE COPY
| were requested to be fast replicated (nnnn), the number
INFORMATION
| of objects that were successful (ssss), and the number of
| objects that failed fast replication (ffff). Explanation:
| System action: This message gives statistical information about the
results of running the COPY utility. It applies to a table
| The COPY utility continues processing.
space, partition, or data set, and is based on the
| Programmer response: information in the space page map at the time the
utility is executed. The output contains the following
| If any of the objects could not be fast replicated,
information:
| examine the DFSMSdss error or warning messages in
| the COPY utility job output. Fast replication is DBNAME
| supported for SMS managed data sets on storage The name of the database to which the table
| devices with a fast replication feature. space belongs.
| Severity: TSNAME
The table space specified in the utility
| 0 (informational) statement.
DSNUM
| DSNU436I csect-name phase-name PHASE
The partition or data set number of the table
| STATISTICS: TOTAL NUMBER OF
space. The value is ALL if information is about
| OBJECTS PROCESSED = nnnn
the entire table space.
| NUMBER OF OBJECTS COPIED FROM
| FAST REPLICATION COPY = ffff nnKB PAGES
| NUMBER OF OBJECTS COPIED FROM The total number of nnKB pages in the
| DB2 DATA SETS = dddd TOTAL TIME partition, data set, or entire table space. This
| FOR APPLICATION OUTAGE = value includes preformatted pages that contain
| hh/mm/ss all zeroes.
| Explanation: EMPTY PAGES
The total number of empty pages in the data
| This message is issued at the completion of the
set of the segmented table space, or entire
| DUMPCOPY or the COPY phase for the COPY utility,
segmented table space. Empty pages can result
| if DFSMSdss dump format copies were requested. For
from deletes, or are pages that are not yet
| example, if COPYDDN or RECOVERYDDN was
formatted. They are not copied by the utility.
| specified.
486 Messages
DSNU441I • DSNU442I
System action:
DSNU443I csect-name type CHANGE LIMIT MET
FOR obj-type obj-qual.obj-name Utility processing continues. An image copy is taken if
a change limit is met. If the low CHANGELIMIT value
Explanation:
is met, then an incremental copy is taken. If the high
The COPY utility is indicating whether the percent of CHANGELIMIT value is met, then a full image copy is
changed pages in the specified table space, partition, or taken.
data set meets the CHANGELIMIT values. type values:
Severity:
NO If no CHANGELIMIT met.
0 (informational)
INCREMENTAL
If the percent of changed pages is greater than
DSNU446I csect-name - CHANGELIMIT REPORT
the low CHANGELIMIT value and less than
INFORMATION UNAVAILABLE FOR
the high CHANGELIMIT value.
obj-type obj-qual.obj-name, A FULL IMAGE
FULL If the percent of changed pages is greater than COPY MUST BE TAKEN
or equal to the the high CHANGELIMIT
Explanation:
value.
The changelimit dataset statistical information was
System action:
requested, but is unavailable. A full image copy is
Utility processing continues. required. Possible reasons are as follows:
User response: v The request was for one of the DB2-maintained table
spaces: DSNDB01.DBD01, DSNDB06.SYSCOPY, or
If the REPORTONLY option is specified and the result DSNDB01.SYSUTILX.
of this job step is not used to conditionally execute
v A LOAD or REORG utility was run on the table
other job steps, examine the utility messages for this
space or data set with no subsequent full image copy.
table space, partition, or data set to determine if it has
changed to such a degree that an image copy or other v No full image copy was found for the requested
step should be performed. sites.
v Copy pending status was set for the requested table
Severity:
space or data set.
The return codes are: v The request was for an entire table space, but the
1 (informational) most recent image copy for the table space is on the
If no CHANGELIMIT was met. data set level.
v The previous image copy is a DFSMS concurrent
2 (informational) copy.
If the percent of changed pages is greater than
the low CHANGELIMIT and less than the
The statistical information report will not be generated.
high CHANGELIMIT value.
If REPORTONLY was omitted, then a FULL image copy
3 (informational) is taken.
If the percent of changed pages is greater than
System action:
or equal to the high CHANGELIMIT value.
The request for CHANGELIMIT without
REPORTONLY is treated as a request to take a full
DSNU445I csect-name ictype IMAGE COPY WILL
image copy. The request for CHANGELIMIT with
BE TAKEN FOR obj-type obj-qual.obj-name
REPORTONLY will not generate the report.
Explanation:
User response:
The COPY utility is indicating whether the percent of
If REPORTONLY is specified, then submit a job to take
changed pages in the table space meets the change
a full image copy.
limit value, and whether an image copy will be taken.
ictype values: Severity:
NO If no CHANGELIMIT value met. 4 (warning)
INCREMENTAL
If the percent of changed pages is greater than | DSNU447I csect-name - COPY SHRLEVEL CHANGE
the low CHANGELIMIT value and less than | OF obj-type obj-qual.obj-name IS NOT
the high CHANGELIMIT value. | ALLOWED BECAUSE IT HAS A
| LOGGING ATTRIBUTE OF NOT
FULL If the percent of changed pages is greater than
| LOGGED
or equal to the high CHANGELIMIT value.
| Explanation:
488 Messages
DSNU448I • DSNU454I
| COPY with SHRLEVEL CHANGE was specified for a | Include the index’s table space in the COPY list.
| COPY utility job that refers to an object with a NOT
| LOGGED logging attribute. This situation is not
| Severity:
| supported. | 8 (error)
| System action:
DSNU454I csect-name COPY MERGE COMPLETE.
| Utility processing halts for this object. The utility job
NUMBER OF COPIES = iiiii, NUMBER
| completes with a return code of 8.
OF COPIES MERGED = cccccc, TOTAL
| If the utility job step include an OPTIONS control NUMBER OF PAGES MERGED = ttttt,
| statement with the EVENT(ITEMERROR,SKIP) option, ELAPSED TIME = hh/mm/ss
| the utility will process the next item in the list.
Explanation:
| User response:
This message marks the normal completion of the
| Remove the SHRLEVEL CHANGE option from the MERGECOPY utility. The variables are:
| utility control statement.
iiiii The number of copies found.
| Severity:
cccccc The number of image copies that were
| 8 (error) merged. The number merged can be less than
the number found if a work data set was not
specified using the MERGECOPY WORKDDN
| DSNU448I csect-name - SCOPE PENDING WAS
option.
| SPECIFIED, BUT NO OBJECT WITH
| PENDING STATUS WAS FOUND ttttt The total number of pages that were merged.
| Explanation:
The merged incremental copies were consolidated
| SCOPE PENDING was specified for the utility job, either into a single new incremental image copy or into
| however no objects existed in the list with a pending a new full image copy, depending upon the
| status. MERGECOPY NEWCOPY option. The DB2 catalog
table SYSIBM.SYSCOPY was updated to reflect the
| System action: results.
| Utility processing continues.
This message may indicate that prior data set entries
| Severity: were deleted and, consequently, that backup data set
| 0 (informational) resources were freed.
System action:
| DSNU449I csect-name - THE NOT LOGGED INDEX
Processing continues to the next utility statement in the
| obj-qual.obj-name IN ICOPY PENDING
utility job step, if any. If there are no more utility
| STATE MUST BE COPIED WITH ITS
statements, the utility job step is normally terminated,
| TABLE SPACE IN THE SAME COPY
and the resources are released to their prior availability
| INVOCATION
state. The UTILID of the utility job step becomes
| Explanation: available for reuse.
The target copy data set identified by the DD statement No output was produced and the SYSIBM.SYSCOPY
nominated by the MERGECOPY COPYDDN option catalog table remains unchanged.
was not required. It was not tracked in the DB2 catalog
User response:
table SYSIBM.SYSCOPY. It need not be kept for
subsequent re-call. A full image copy of the associated table space should
be taken. However, if it is preferred that a recovery be
Severity:
done on the data set level, a MERGECOPY job should
4 (warning) be submitted by specifying ’DSNUM(data set number)’
for each data set for which MERGECOPY is required.
A severity 4 condition is given to alert the invoker that
processing did not proceed as defined. However, Severity:
processing is proceeding; nothing was encountered that
4 (warning)
would invalidate further processing.
A severity 4 condition is given to alert the user that
processing did not proceed as defined. However,
DSNU459I SYSCOPY P RECORD ENCOUNTERED
processing is proceeding; nothing was encountered that
FOR obj-type obj-qual.obj-name, PIT RBA =
would invalidate further processing.
xxxxxx
Explanation:
DSNU461I csect-name PRIMARY FULL COPY DATA
The utility encountered a SYSCOPY P record which SET NOT FOUND, BACKUP WILL BE
requires that the SYSCOPY record at the given RBA or USED INSTEAD
LRSN be used. The utility properly traverses the
Explanation:
SYSCOPY records following this SYSCOPY P record.
The primary full image copy cannot be found. The
User response:
backup full image copy will be located and used for
For further information on how the SYSCOPY records the merge process.
are traversed, see Part 4 of Administration Guide.
User response:
Severity:
If the MERGECOPY utility can use the backup full
0 (informational) image copy, the utility continues to process. If no
backup full image copy can be used, the utility
terminates.
Severity:
0 (informational)
490 Messages
DSNU462I • DSNU471I
492 Messages
DSNU478I • DSNU481I
the quiesced table space. This message will be repeated The problem may be an I/O error.
for every quiesced table space in list.
Severity:
System action:
4 (warning)
All data held in the DB2 buffer pool(s) for the table
space and its indexes have been written out to the
DSNU480I csect-name - UNABLE TO
media if no message DSNU473 or DSNU479 were
EXTERNALIZE TABLESPACE
issued earlier. A SYSCOPY record of ICTYPE ’Q’ has
tablespace-name PARTITION
been recorded in the SYSCOPY catalog table for the
partition-number PAGES
table space and for each of its indexes with the COPY
YES attribute. The START-RBA value in the SYSCOPY Explanation:
record(s) is the same for all objects quiesced during this
invocation of the utility. This RBA/LRSN value will be The attempt to externalize TABLESPACE
printed in the message DSNU474 following this ’tablespace-name’ PARTITION ’partition-number’ pages
message. Processing continues to the next table space in to the media failed.
the table space list, if any. System action:
Severity: QUIESCE still continues, but the table space cannot be
0 (informational) volume-dumped.
Problem determination:
DSNU478I csect-name - INDEX index-name HAS The problem might be an I/O error.
PENDING STATE
Severity:
Explanation:
4 (warning)
Index ’index-name’ has a PENDING state.This message
is repeated for all PENDING stated indexes in a table
space. DSNU481I csect-name - QUIESCE SUCCESSFUL
FOR obj-type obj-qual.obj-name
System action: PARTITION partition
QUIESCE stops processing but continues to check all Explanation:
table spaces and indexes for any additional table space
or index that has a PENDING state. There is no update The QUIESCE for PARTITION ’partition-number’ of
in SYSCOPY table for any table space in the list. this object was successful. If the object is a table space
partition, then the quiesce for all of its indexes was
User response: successful. This message will also be issued for each
Issue the DISPLAY DATABASE command to look at the index with the COPY YES attribute over the quiesced
utility status byte in the DBA table for a specified table space. This message is repeated for every
PENDING state. quiesced table space in the list.
Refer to Part 4 of the Administration Guide for a All data held in the DB2 buffer pool(s) for the table
discussion of the database recovery function. space and its indexes have been written out to the
media if message DSNU480 or DSNU482 was not
Severity: issued earlier. A SYSCOPY record of ICTYPE ’Q’ was
recorded in the SYSCOPY catalog table for the table
8 (error)
space and for each of its indexes with the COPY YES
attribute. The START-RBA value in this SYSCOPY
DSNU479I csect-name - UNABLE TO record is the same for all objects quiesced during this
EXTERNALIZE INDEX index-name invocation of the utility. This RBA value is printed in
PAGES message DSNU474 following this message. Processing
continues to the next table space in the table space list,
Explanation:
if any.
The attempt to externalize index ’index-name’ pages to
Severity:
the media has failed.
0 (informational)
System action:
QUIESCE still continues but the table space cannot be
volume-dumped.
Problem determination:
User response:
DSNU482I csect-name - UNABLE TO
EXTERNALIZE INDEX index-name Issue DISPLAY DATABASE to determine the exception
PARTITION partition-number PAGES state.
Explanation: Problem determination:
The attempt to externalize index ’index-name’ Refer to part 2 of Diagnosis Guide and Reference for a
’partition-number’ pages to the media failed. discussion of the database recovery function.
System action: Severity:
QUIESCE still continues, but the table space cannot be 4 (warning)
volume-dumped.
Problem determination: | DSNU485I csect-name QUIESCE WRITE(NO)
| REQUESTED ON obj-type
The problem might be an I/O error.
| obj-qual.obj-name WHICH HAS THE NOT
Severity: | LOGGED ATTRIBUTE
4 (warning) | Explanation:
| QUIESCE with the WRITE(NO) option was requested
DSNU483I csect-name - TABLESPACE tablespace-name | on an object with the NOT LOGGED attribute.
PARTITION partition-number HAS | Invoking QUIESCE WRITE(NO) on an object with the
WRITE ERROR RANGE OR IS IN | NOT LOGGED attribute does not create a recoverable
DEFERRED RESTART. | point and does not write the pages from the buffer pool
| to DASD.
Explanation:
| System action:
The attempt to externalize table space
’tablespace-name’ partition ’partition-number’ pages to | The object will be skipped by QUIESCE, and the other
the media failed. | objects in the list are processed.
System action: | User response:
QUIESCE still continues, but you cannot make an | If you want a quiesced point for the object, complete
image copy of the table space or partition. Processing | the following steps:
continues for the index partition and all nonpartitioned | v Alter the table space to have the LOGGED attribute.
indexes within the table space, and then proceeds to
the next table space in the table space list, if any.
| v Take a full image copy.
| v Rerun QUIESCE.
User response:
| Severity:
Issue DISPLAY DATABASE to determine what
exception state, if any, would prevent image copy on | 0 (informational)
the table space or partition.
Problem determination: DSNU500I csect-name RECOVERY COMPLETE,
ELAPSED TIME = hh/mm/ss
Refer to Part 4 of the Administration Guide for a
discussion of the database recovery function. Explanation:
494 Messages
DSNU501I • DSNU504I
496 Messages
DSNU510I • DSNU511I
DSNU510I NO RECOVERY BASE AVAILABLE The requested recovery of an object would result in
FOR RECOVERY OF obj-type recovery entirely from the log. Because the object is
obj-qual.obj-name also in copy pending status, recovery might fail in log
apply in these situations:
Explanation:
v A previous MODIFY utility job deleted the last
| It is not possible to locate a good recovery base. A recoverable point indicated in the SYSCOPY catalog
| recovery base could be either a full image copy or a table.
| system-level backup. If you only take image copies, the v A previous MODIFY utility job deleted all SYSCOPY
| following conditions are possible: entries.
| v No back level image copy exists, or
In either case, the MODIFY utility leaves the object in
| v An I/O error occurred while reading the back level copy pending status and the RECOVER utility is
| image copies, or unable to determine the reliability of recovery from the
| v DB2 was unable to locate a suitable image copy log.
| The return code that accompanies this message is 0 System action:
| (informational) or 8 (error) under the following
| conditions: The RECOVER utility terminates with return code 8.
System action:
DSNU512I csect-name DATA SET LEVEL
RECOVERY IS REQUIRED FOR obj-type RECOVER completes unsuccessfully with a return code
obj-qual.obj-name of 8.
Explanation: User response:
Recovery was requested for an entire object. However, Submit a recover job by specifying DSNUM (data set
there is an image copy made for a specific data set number) for each data set requiring recovery. If the
associated with the object. Hence, the object must be object is an index space, then the REBUILD INDEX
recovered by data set. utility may be used to rebuild the index. Refer to Utility
Guide and Reference for a discussion of RECOVERY
System action:
utility constraints.
RECOVER completes unsuccessfully with a return code
Severity:
of 8.
8 (error)
User response:
Terminate the current RECOVER job. Then, submit a
DSNU515I csect-name THE IMAGE COPY DATA
RECOVER job by specifying ’DSNUM(data set
SET dsn WITH DATE=date AND
number)’ for each data set for which recovery is
TIME=time IS PARTICIPATING IN
required. Refer to Utility Guide and Reference for a
RECOVERY OF obj-type obj-qual.obj-name
discussion of RECOVERY utility constraints.
Explanation:
Severity:
This message is issued by the RECOVER utility for
8 (error)
each participating image copy data set before it opens
the data set and begins the restore process. If an error
DSNU513I csect-name RECOVER UTILITY LOG occurs while processing, the utility searches for a new
APPLY RANGE IS RBA xxx LRSN xxx recoverable base.
TO RBA yyy LRSN yyy
This message is routed to SYSOUT.
Explanation:
System action:
The RECOVER utility issues this message one or more
RECOVER processing continues.
times to display the entire log range before applying
updates. The RBA and LRSN values are equal in a User response:
non-data sharing environment. The RBA values will be
zero in a data sharing environment for the catalog and Refer to Utility Guide and Reference for a discussion of
directory objects that do not have RECOVERY utility constraints.
DSNDB01.SYSLGRNX entries. This includes catalog Severity:
table spaces DSNDB06.SYSCOPY and
DSNDB06.SYSGROUP and all of their indexes, and all 0 (informational)
of the directory objects.
System action: DSNU516I NO BACKUP WAS TAKEN AFTER
LOAD, REORG OR CHECK DATA
The RECOVER utility continues processing. LOG(NO) OF obj-type obj-qual.obj-name
Severity: Explanation:
0 (informational) | RECOVERY was requested for a data set of an object. If
| the object is a table space, then a system-level backup
DSNU514I csect-name RECOVERY DATA DOES | or full image copy was not taken after or during a
NOT PERMIT DSNUM(ALL) | LOAD, REORG, or CHECK DATA without logging.
RECOVERY OF obj-type obj-qual.obj-name | The table space is in an unrecoverable state. If the
| object is an index space, then a full image copy or
Explanation: | system-level backupwas not taken after a REORG
Recovery was requested for an entire object. If the
| INDEX or REBUILD INDEX.
object is a table space, then the latest activity on the System action:
entire table space was a REORG LOG (NO) or a LOAD
LOG (NO). If the object is an index space, then the RECOVER completes unsuccessfully with a return code
latest activity on the entire index space was a REORG of 8.
INDEX or REBUILD INDEX. If full image copies have | System programmer response:
been taken at the data set level since then, recover the
object on the data set level. | The data should be repaired before a full image copy or
498 Messages
DSNU517I • DSNU520I
| system-level backup is taken. utility to correct the broken page. Refer to Part 4 of
Administration Guide for more information.If you
User response:
suspect an error in DB2, refer to Part 2 of Utility Guide
If the object is a table space, the data set is in an and Reference for information on identifying and
unrecoverable state. If the object is an index space, then reporting the problem.
the REBUILD INDEX utility may be used to rebuild the
User response:
index. Notify the system programmer for corrective
action. The associated data set has not been copied. If the
object is in the COPY-pending status, it is in an
Severity:
unrecoverable state. Notify the system programmer for
8 (error) corrective action.
Severity:
DSNU517I csect-name - SYSCOPY RECORD
8 (error)
DELETED BY MODIFY UTILITY.
DSN=dsn, VOL=SER=nnn,
FILESEQNO=fff DSNU519I csect-name TOCOPY DATA SET NOT
FOUND
Explanation:
Explanation:
This message is repeated for each volume of a
multivolume data set that is deleted. The data set specified with the keywords TOCOPY,
TOVOLUME, or TOSEQNO cannot be found in the
The variables have the following meanings:
SYSCOPY table for the object to be recovered.
dsn The name of the image copy data set whose
This may be caused by a mismatch in granularities. If
record was removed from the SYSCOPY table
the RECOVER specifies a particular DSNUM, the data
by the MODIFY utility.
set specified with the TOCOPY keyword may be for an
nnn The serial number of the volume containing image copy of this DSNUM or of the entire table space
the data set. or index space. However, if the RECOVER is for the
entire table space or index space, the specified data set
fff The tape file sequence number. It will be zero must be for an image copy of the entire table space or
for DASD data sets. index space.
System action: This message may also be issued if TOVOLUME is
The MODIFY utility continues its termination specified for a cataloged data set.
processing. RECOVER TOCOPY can issue DSNU519I even if the
System programmer response: data set information was correct but the data set was
not for this site. For example, if the DB2 subsystem is
Because DB2 no longer has any knowledge of the specified as LOCALSITE, but the TOCOPY data set
image copy data set, you may delete it and reuse the information is for a RECOVERYSITE data set, this
space. If the last full image copy was deleted, ensure message will be issued.
that another one is taken as soon as possible.
System action:
Severity:
RECOVER processing is terminated.
0 (informational)
User response:
DSNU518I csect-name object-type object-qualifier.object- Correct the input and resubmit the RECOVER job.
name CONTAINS BROKEN PAGE Severity:
page-number, ERROR CODE error
8 (error)
Explanation:
A broken page, page number, was detected during DSNU520I csect-name RECOVER TO A PRIOR
execution of an image copy utility job. The copy step is POINT IN TIME MIGHT LEAVE
terminated and the broken page is not copied to the TABLE SPACE table-space-name
output data set. INCONSISTENT
System action: Explanation:
COPY utility ends with a return code of 8. RECOVER DSNUM to a previous point in time (for
System programmer response: example, using the TOLOGPOINT option) was
specified for a nonpartitioned table space. You might
Use either the RECOVER, RECOVER PAGE, or REPAIR have recovered a data set that has different
compression characteristics than the replaced data set. set. Run the change log inventory (DSNJU003) tility
For example, the data set to which you recovered to supply changes that occurred during and after the
might have been compressed with a different last offload operation. Changes can be determined
dictionary. from the operator’s console listing.
System action:
If a listed log data set contains the required RBA or
Processing continues. LRSN, this message is preceded by one or more
DSNJxxx error messages. See the explanation of those
User response:
messages for the appropriate action.
The table space might be in an inconsistent state. If the
Severity:
dictionary was not built with the data set that was just
recovered, the results are unpredictable and might 8 (error)
jeopardize all the data in the entire table space.
Recover all of the data sets in the table space to the DSNU522I csect-name RECOVER CANNOT
same point in time. Do not ignore this message unless PROCEED FOR obj-type obj-qual.obj-name
all data sets in this table space were recovered to the BECAUSE A NON-RECOVERABLE
same point in time. Otherwise, the state of this EVENT HAS BEEN ENCOUNTERED
nonpartitioned table space is inconsistent and FROM SYSIBM.SYSCOPY WHICH
unpredictable. HAS DBNAME=dbname
TSNAME=tsname DSNUM=dsnum
Severity:
ICTYPE=ictype START_RBA=X’rba’
4 (warning)
Explanation:
Recovery was requested for an index, but activity on its
DSNU521I csect-name - RECOVER UTILITY
table space (identified by the SYSIBM.SYSCOPY
FAILED. UNABLE TO READ
columns) prohibits recovery. The use of an index’s full
REQUIRED LOG RECORDS.
image copy by recovery is prohibited by a REORG or
Explanation: LOAD on its underlying table space.
Recovery was requested for a table space, index space, System action:
or data set. An attempt was made to apply changes
Utility processing is terminated. All objects in the
from the DB2 log, but the necessary log records could
RECOVER statement are left in the same state as before
not be read from the log data set. This message is
the RECOVER utility was invoked.
accompanied by message DSNI007I.
User response:
System action:
Use the REBUILD INDEX utility to rebuild the index
The RECOVER utility completes unsuccessfully with
from the table space. For more information about the
return code 8.
recoverability of this index, run the REPORT
Operator response: RECOVERY utility on both the index and its table
space.
Provide the console listing of the DSNI007I message for
the system programmer. Severity:
If no listed data set contains the required RBA or | RECOVER was requested for a table space or a data set
LRSN, one of the following might have occurred: | of a table space and no image copy or system-level
| backup was available. Recovery was attempted from
v The data set was deleted from the bootstrap data set
| the log and failed due to missing data set initialization
(BSDS) by the change log inventory (DSNJU003)
| records. Specifically, the log records which format space
utility. Rerun the utility to insert the missing data set
| map and header pages were missing.
name. DB2 must be stopped to run this utility.
v The BSDS was damaged. The BSDS can be restored System action:
using the dump and the most recent archive log data
500 Messages
DSNU524I • DSNU527I
RECOVER completes unsuccessfully with a return code v The object was recovered to a point in time (for
of 8. example, TOLOGPOINT was specified), which
required fall back processing. However, no
System programmer response:
subsequent image copy was taken to establish a base
Use the problem determination information given for recovery.
below to determine if a user error has occurred. If v A partition of the object was recovered to a point in
possible, correct the error and resubmit the RECOVER time after the last full image copy of the object was
utility job for this table space or data set. Refer to part taken.
2 of Diagnosis Guide and Reference for a discussion of
possible recovery procedures. System action:
Problem determination: Submit the RECOVER job with DSNUM specified for
each data set for which recovery is required. Refer to
This message was preceded by message DSNU513I Utility Guide and Reference for information about the
which identifies the log RBA range being applied. Run RECOVER utility.
the print log map (DSNJU004) utility for the table space
in question over the indicated log RBA range. Severity:
This will show what log records are present and may 8 (error)
assist in determining if a log data set has been
damaged or deleted, or if the BSDS has been damaged. DSNU526I NO BACKUP WAS TAKEN AFTER
If damage to table space DSNDB01.SYSLGRNX is PARTIAL RECOVERY OF obj-type
suspected, recover it and attempt the earlier failing objqual. obj-name
recovery again.
Explanation:
Severity:
| Recovery was requested for a data set of an object.
8 (error) | However, an earlier point-in-time recovery (for
| example, using the TOLOGPOINT option) was
DSNU524I csect-name INVALID DATA SET OR | specified and no subsequent image copy or
PARTITION NUMBER num SPECIFIED | system-level backup was taken to establish a base for
FOR obj-type obj-qual.obj-name | recovery.
An invalid number was specified for the data set or The RECOVER utility completes unsuccessfully with
partition of the object named in the utility statement. return code 8.
Further utility processing terminates. You can use the RECOVER utility with the TOCOPY,
TORBA, or TOLOGPOINT option to force recovery to
User response: an earlier point in time. You can use the DSN1COPY
Correct the data set/partition number, or verify that the utility to restore the data set to an earlier image copy.
object name is specified correctly. Then resubmit the Refer to part 2 of Diagnosis Guide and Reference for a
utility statement in a new utility job step. Refer to discussion of database recovery procedures.
Utility Guide and Reference for a description of the User response:
particular utility options.
The associated data set is in a nonrecoverable state.
Severity: Consult the system programmer for corrective action.
8 (error) Severity:
8 (error)
DSNU525I csect-name RECOVERY DATA DOES
NOT PERMIT DSNUM(ALL)
RECOVERY OF obj-type obj-qual.obj-name DSNU527I csect-name DB2 OBJECT RECOVERED
TO AN INDETERMINATE POINT
Explanation:
Explanation:
Recovery was requested for an entire object. However,
the object is not recoverable at that level for one of the The image copy data set specified with the TOCOPY
following reasons:
keyword of the RECOVER utility was one of the The associated data set was reset to an empty state and
following: the data set was placed in REBUILD PENDING status.
v An image copy dataset made with the SHRLEVEL If REBUILD was processing a TABLESPACE list, only
CHANGE option. In this mode, changes might have the associated data set was reset to an empty state but
been made to the object while image copy was in all data sets in the list were placed in REBUILD
progress. If a change was made to a page before PENDING status.
image copy processed the page, the update will be in System programmer response:
the copy data set. If a change was made to a page
after image copy processed it, the change will not Use the information in the problem determination
appear in the copy data set. The data set may section to determine if a user error occurred. Correct
contain partial updates from some transactions. the error and resubmit the REBUILD utility for the
table space. Also refer to Part 4 of Administration Guide
v An image copy dataset made during the LOAD
for a discussion of possible recovery procedures.
REPLACE utility. An image copy produced during
LOAD REPLACE will not contain updates made to User response:
the table space to correct unique index violations
during the INDEXVAL phase or referential constraint If the TORBA or TOLOGPOINT option was specified,
violations during the ENFORCE phase. Therefore, it use the information in the problem determination
is not recommended as a recovery point. section to verify that it is a valid RBA or LRSN. Correct
the error and resubmit the REBUILD utility for the
table space.
If the object recovered is a table space, then indexes on
the table space are placed in rebuild pending status and Problem determination:
dependent table spaces, if any, are placed in check
pending status. The indexes placed in rebuild pending Execute the REPORT RECOVERY utility for the table
are identified by message DSNU831I, and the space at the appropriate table space or data set level
dependent table spaces placed in check pending are (DSNUM). The output shows the recovery points
identified by message DSNU563I. (SYSCOPY records) and the update log ranges
(SYSLGRNX records) that exist for the table space.
System action:
| If you take system-level backups with the BACKUP
The utility terminates normally. | SYSTEM utility, then run the Print Log Map Utility
User response:
| (DSNJU004) to print the system-level backup
| information. If data sharing, ensure that the
Based on the explanation above, determine if the | system-level backup information from all members is
recovery is satisfactory. Rebuild the indexes identified | gathered. Locate the system-level backup information
by message DSNU557I in the job output. Run CHECK | in the DSNJU004 output and compare it with the
DATA on the table spaces identified by message | output from the REPORT RECOVERY utility output.
DSNU563I to correct any referential constraint
Severity:
violations.
8 (error)
Refer to part 2 of Diagnosis Guide and Reference for a
discussion of database recovery procedures.
DSNU529I csect-name INVALID SPECIFICATION
Severity:
OF TORBA = xxx
4 (warning)
Explanation:
’xxx’ is the log RBA specified for the RECOVER utility
DSNU528I NO FULL IMAGE COPY WAS
TORBA keyword. The RBA is not within the scope of
AVAILABLE AND THERE ARE NO
the log.
UPDATES TO APPLY FROM THE DB2
LOG FOR TABLESPACE tablespace-name System action:
DSNUM dsnum
The RECOVER utility terminates with a return code of
Explanation: 8 without making any changes to the object to be
recovered.
Recovery was requested for a table space or a data set
of a table space and no image copy or system-level User response:
backup was available. If dsnum is 0, then recovery was
requested at the table space level. Recovery was Correct the input and resubmit the job. Refer to part 2
attempted from the log, but no log records were of Diagnosis Guide and Reference for a discussion of
applied because no SYSLGRNX records corresponding database recovery procedures.
to the recovery scope were found. Problem determination:
System action: The listing produced by the print log map (DSNJU004)
502 Messages
DSNU530I • DSNU533I
utility will show the current extent of the DB2 log. EVENT(ITEMERROR,SKIP) option, the next item in the
list will be processed.
Severity:
User response:
8 (error)
Use the information provided in all of the DSNU531I
messages to determine the correct data set for this
DSNU530I csect-name - MULTIPLE DATA SETS
recovery. ’rba’, ’date’ and ’time’ are provided for each
FOUND FOR THE COPY DATA SET
data set to assist in the selection. The DSNU531I
SPECIFICATION
message for the data set you select will provide the
Explanation: correct ’vol’ and ’fseq’ values to be specified on the
TOVOLUME and TOSEQNO keywords respectively.
DB2 issues this message during the RECOVER or
COPYTOCOPY utility when the specification of the Rerun the RECOVER job specifying TOCOPY and
input image copy dataset is ambiguous and does not TOVOLUME(vol-ser). Include the TOSEQNO(fseq)
uniquely identify an image copy. Multiple image copies keyword if it is necessary to distinguish an unique data
were found in SYSIBM.SYSCOPY for the object with set.
the same data set name.
Rerun the COPYTOCOPY job specifying FROMCOPY
System action: and FROMVOLUME(vol-ser). Include the
FROMSEQNO(fseq) keyword if it is necessary to
Processing halts for this object. distinguish a unique data set.
RECOVER completes unsuccessfully with a return code Severity:
of 8.
8 (error)
For the COPYTOCOPY utility, if the utility job step
includes an OPTIONS control statement with the
EVENT(ITEMERROR,SKIP) option, the utility will DSNU532I csect-name - RECOVER obj-type
process the next item in the list. obj-qual.obj-name START
User response: Explanation:
Two or more DSNU531I messages will follow this This message is issued when there is more than one
message providing more information about each object in the list. It indicates that the recover of a
duplicate data set. Select the correct data set from the particular object is starting. If the PARALLEL keyword
DSNU531I messages. has been specified, then the restore phase messages for
different objects in the list may be intermingled.
Rerun the RECOVER job, specifying a unique
combination of TOVOLUME and TOSEQNO. This message is routed to SYSPRINT.
Rerun the COPYTOCOPY job, specifying an unique System action:
combination of FROMVOLUME and FROMSEQ.
RECOVER processing continues.
Severity:
Severity:
8 (error)
0 (informational)
504 Messages
DSNU539I • DSNU544I
Explanation: 0 (informational)
Explanation: 0 (informational)
Processing continues after a unit becomes available and RECOVER was unable to open the data set
is allocated. ’dataset-name’. because of ’reason-code’ from the open
abend. The ’reason-code’ is taken from field
Severity: SDWAABCC in the SDWA.
0 (informational) System action:
The RECOVER utility continues processing, searching
for the prior image copy or applying log records.
Severity:
0 (informational) Explanation:
One of the following results occurred:
DSNU545I csect-name - I/O ERROR READING v The data set was restored from an earlier release
PAGE page-number IN THE COPY backup that does not have a starting RBA or LRSN
DATASET dataset-name DURING in the header page.
RECOVERY OF obj-type obj-qual.obj-name
v The TORBA or TOLOGPOINT option is specified to
Explanation: an RBA or LRSN that is lower than the starting RBA
or LRSN in the header page.
An I/O error was detected while reading page
’page-number’ from copy dataset ’dataset-name’. The System action:
message is issued when 1) The data set is the primary
The RECOVER or RESTORE utility job terminates with
copy data set and there is no backup data set. 2) Open
return code 8.
error is from the backup copy data set.
System programmer response:
System action:
Use the RECOVER or RESTORE utility without the
The RECOVER utility continues processing, searching
LOGONLY option, if possible, or change the RBA or
for the prior image copy or applying log records.
LRSN of the TORBA or TOLOGPOINT option to a
Severity: valid RBA or LRSN value.
0 (informational) Severity:
8 (error)
DSNU546I LOGONLY RECOVER CANNOT
PROCEED BETWEEN BEGINNING
DSNU548I DBID=X’xxxx’ and PSID=X’xxxx’ IN
RBA ’xxxxxxxxxxxx’ AND ENDING RBA
THE HEADER PAGE OF obj-type
’yyyyyyyyyyyy’ ON DSNUM dsnum
obj-qual.obj-name DO NOT MATCH THE
BECAUSE A NON-RECOVERABLE
DB2 CATALOG.
EVENT HAS BEEN ENCOUNTERED
FROM SYSIBM.SYSCOPY WHICH Explanation:
HAS DBNAME=database-name
TSNAME=space-name DSNUM=dsnum The DBID and PSID in the header page do not match
ICTYPE=x the DB2 catalog. It is likely that the wrong data sets
START_RBA=X’zzzzzzzzzzzz’. were restored.
A nonrecoverable event (for example, LOAD LOG(NO), The RECOVER utility job terminates with return code
REORG LOG(NO)) occurred within the log range 8.
between the beginning log RBA or LRSN and ending System programmer response:
log RBA or LRSN for the RECOVER LOGONLY utility.
Find the correct data sets and rerun the job.
System action:
Severity:
The RECOVER utility completes unsuccessfully with
return code 8. 8 (error)
Severity: The RECOVER utility issues one message for each DB2
object that uses only DB2 logs to recover. In a non
8 (error) data-sharing environment, the LOGPOINT value is
specified by an RBA; in a data sharing environment it
DSNU547I LOGONLY action CANNOT PROCEED is specified by an LRSN.
BECAUSE THE STARTING System action:
RBA=X’xxxxxxxxxxxx’ IN THE HEADER
PAGE PGNO=X’xxxxxx’ FOR obj-type RECOVER utility processing continues.
obj-qual.obj-name IS INVALID. Severity:
506 Messages
DSNU550I • DSNU555I
0 (informational)
DSNU553I csect-name INVALID PARTITION
NUMBER=nnnn SPECIFIED FOR
DSNU550I csect-name INDEX NAME= index-name IS INDEX NAME=iiii
EMPTY
Explanation:
Explanation:
An invalid partition number nnnn was specified for
While attempting to REBUILD the indicated index, it index iiii in the utility statement.
was determined that the table upon which the index is
System action:
based is empty.
Further utility processing is terminated.
System action:
User response:
Utility processing proceeds to the next utility request, if
any. Correct the partition number or verify that the index
name is specified correctly, and resubmit the utility
Severity:
statement in a new utility job step. Refer to Utility
4 (warning) Guide and Reference for a description of the particular
utility options.
DSNU551I csect-name INDEX NAME= index-name Severity:
PART=part-num IS EMPTY
8 (error)
Explanation:
While attempting to REBUILD the indicated index DSNU554I csect-name - DUPLICATE INDEX
partition, it was determined that the partition upon NAMES EXIST IN THE SPECIFIED
which the specified index partition is based is empty. INDEX NAME LIST
Utility processing proceeds to the next utility request, if When attempting to CHECK or REBUILD the indicated
any. indexes, it was determined that duplicate index names
were specified in the index name list.
Severity:
System action:
4 (warning)
The utility job terminated.
DSNU552I csect-name RECOVER CANNOT User response:
PROCEED BECAUSE THE
Correct the index-name(s) in the index name list and
starting/ending LOGPOINT xxx IS NOT
resubmit the job.
WITHIN THE RECOVERY RANGE OF
xxx AND xxx FOR obj-type Severity:
obj-qual.obj-name
8 (error)
Explanation:
The starting or ending LOGPOINT found for this DSNU555I csect-name UNLOAD PHASE
recovery job is outside the available recovery STATISTICS, NUMBER OF
information. A LOGPOINT value is an RBA or LRSN. RECORDS=xxxx
The RECOVER utility cannot process this request.
Explanation:
System action:
This message is issued at the normal completion of the
The RECOVER utility terminates. UNLOAD phase of the REBUILD INDEX utility. It
gives the number of records that were unloaded (xxxx)
User response:
for the specified table space.
Use the recovery information that is available from the
Severity:
REPORT utility. Execute the RECOVER utility within
the available recovery range. 0 (informational)
Severity:
8
508 Messages
DSNU557I • DSNU559I
| If a SYSCOPY record for a REORG or LOAD REPLACE The REBUILD TORBA, TOLOGPOINT, or TOCOPY
| that redistributed partition data was encountered, then utility issues this message to inform the user of the
| add the missing partitions to the recover list using the state of all indexes belonging to the REBUILDed table
| LOWDSNUM and HIGHDSNUM values as a guide. space. All indexes were put in REBUILD pending status
to prevent data and index inconsistency. All indexes
| If the object is an index, then use the REBUILD INDEX should be REBUILDed before they are used.
| utility to rebuild the index.
System action:
| Severity:
The REBUILD utility completed successfully.
| 8 (error)
User response:
DSNU557I csect-name - obj-type obj-qual.obj-name IS REBUILD or rebuild all indexes of the REBUILD table
IN RECOVER PENDING space.
Explanation: Severity:
If the REBUILD utility issued this message, the 4 (warning)
corresponding table space to this index was rebuilt to a
point in time with keyword TOCOPY, TOLOGPOINT,
DSNU559I csect-name - obj-type obj-qual.obj-name
or TORBA. Thus, the index was placed in REBUILD
PARTITION partition-number IS IN
pending status.
RECOVER PENDING STATE
If the REBUILD INDEX utility issued this message, the
Explanation:
index is in REBUILD pending status. Either duplicate
index entries existed during the BUILD phase of the If the REBUILD utility issued this message, one
REBUILD INDEX, or invalid KEY/RIDs, which do not partition of a partitioned table space is being rebuilt to
belong to the partition of the cluster index, were a point in time with keyword TOCOPY, TOLOGPOINT,
detected. The duplicate index entries or invalid or TORBA. The corresponding index for that partition
KEY/RID entries must be resolved before starting the was placed in rebuild pending status.
REBUILD INDEX utility again to REBUILD the index
If the REBUILD INDEX utility issued this message, the
and remove the index from REBUILD pending status.
index or the partition of a cluster index is in rebuild
If the REORG utility with SHRLEVEL REFERENCE or pending status. Either duplicate index entries existed
CHANGE (or -TERM UTILITY) issued this message, during the BUILD phase of the REBUILD INDEX or
the index is in REBUILD pending status. During the INDEX PART, or invalid KEY/RIDs, which do not
renaming of a data set during REORG, either a data set belong to the partition of the cluster index, were
with the source name did not yet exist or a data set detected. The duplicate index entries or invalid
with the target name already existed. KEY/RID entries must be resolved before starting the
REBUILD INDEX utility again to rebuild the index and
User response:
remove the index from rebuild pending status.
If the REBUILD or REORG utility (or -TERM UTILITY)
If the REORG utility with SHRLEVEL REFERENCE or
issued this message, use the REBUILD INDEX utility to
CHANGE (or -TERM UTILITY) issued this message,
REBUILD this index.
one partition of a partitioned index was placed in
If the REBUILD INDEX utility issued this message, take rebuild pending status. During the renaming of a data
one of the following actions: set during REORG, either a data set with the source
v Resolve the duplicate index entries or invalid keys name did not yet exist or a data set with the target
and rerun the REBUILD INDEX utility. name already existed.
510 Messages
DSNU564I • DSNU567I
User response:
DSNU564I csect - RESTART NOT ALLOWED FOR
obj-type obj-qual.obj-name Refer to Part 2 of the Administration Guide for
information about resolving the check pending status.
Explanation:
Severity:
Restart of the RECOVER utility is not allowed for one
of the following reasons: 4 (warning)
1. During the RESTORE phase, access to image copies
failed. Therefore, RECOVER determined an earlier DSNU566I csect-name RESTORE OF obj-type
point of recovery to search for available image obj-qual.obj-name FROM DATA SET
copies. RECOVER might not be able to recreate the data-set-name COMPLETED, ELAPSED
original failures for restart. TIME = hh:mm:ss
2. The utility uses the LOGONLY option and was
previously restarted with RESTART(CURRENT). It Explanation:
cannot now be started with RESTART(PHASE). This message is issued at the successful completion of
System action: the RESTORE phase of the RECOVER utility when the
DFSMSdss RESTORE command is issued. The
The utility job terminates. If RECOVER acts on a list of data-set-name identifies the DFSMS concurrent copy that
objects, the restarted job terminates with the first object was being restored. The elapsed time of the RESTORE
for which restart is not allowed. is shown in hours, minutes, and seconds.
User response: System action:
For case 1, execute REPORT RECOVERY on the object RECOVER utility processing continues.
and also collect the output from the previous execution
of RECOVER TABLESPACE. Using those two outputs User response:
and the console log, determine the reason for the No action is required.
failure during the RESTORE phase. Correct the reason
for the failure, if necessary. Terminate the outstanding
utility then rerun the RECOVER TABLESPACE without DSNU567I csect-name TABLESPACE= dbname.tsname
RESTART. PART NUMBER = partition number IS IN
REORG PENDING STATE
For case 2, restart the utility with RESTART(CURRENT)
or restore the data sets and rerun the RECOVER job Explanation:
from the beginning. A SYSCOPY record for a range of partitions has be
Collect the following diagnostic items: encountered. The RECOVER TABLESPACE utility was
executed against an object which was the target of a
v Console output from the system on which the job
partition rebalancing. The RECOVER utility will set all
was run, and a listing of the SYSLOG data set for the
of the partitions involved in the partition rebalancing to
period of time spanning the failure.
REORG PENDING for one of the following reasons:
Severity: v Recovery of a table space to a point in time prior to
8 (error) the resetting of the REORG PENDING state by the
REORG utility.
v Recovery of a table space to currency, when the table
DSNU565I csect-name CHECK CONSTRAINT space is in REORG PENDING state.
constraint-name ON TABLE table-name
WAS CREATED AFTER THE TARGET System action:
RECOVERY POINT
The RECOVER utility completed successfully.
Explanation:
User response:
The check constraint constraint-name was created on
Execute REORG with SHRLEVEL NONE on the
table table-name after the target recovery point. The
partitions in REORG PENDING status to rebalance the
target recovery point is the specified time or RBA in the
partitions and to remove the REORG PENDING state.
point-in-time recovery. The associated table space was
placed in check pending status because the RECOVER Severity:
utility cannot determine whether check integrity was
4 (warning)
maintained. Data in the table might have constraint
violations.
System action:
RECOVER processing continues.
Severity:
| DSNU568I csect-name obj-type obj-qual.obj-name IS IN
| INFORMATIONAL COPY-PENDING 4 (warning)
| STATE
| Explanation: DSNU570I csect-name obj-type obj-qual.obj-name
PARTITION part-num IS IN
| This message reports that the state of a table space or
INFORMATIONAL COPY PENDING
| index has informational COPY- pending status. This
| state is an advisory state, so the object is available for Explanation:
| read and write access. The Informational Copy Pending
| state is set for table spaces with the NOT LOGGED An image copy of the index partition is required to
| attribute when the table space is opened for update. establish a new base from which the index partition can
| The Informational Copy Pending state is set for indexes be recovered. This is an advisory state, so the index is
| when a new recovery base needs to be established due available for read or write access.
| to a non-recoverable event (such as a REORG or LOAD User response:
| utility).
Take an image copy of the index partition or of the
| System action: entire index, depending on your backup and recovery
| None. procedures.
Problem determination:
DSNU572I csect-name ALL site SYSCOPY RECORDS
If you suspect an error in DB2, refer to Part 2 of FOR obj-type= obj-qual.obj-name HAVE
Diagnosis Guide and Reference for information on BEEN DELETED
identifying and reporting the problem.
Explanation:
Collect the following diagnostic items:
The MODIFY RECOVERY utility deleted all of the
v Console output from the system on which the job SYSCOPY table records for the specified table space or
was run, and a listing of the SYSLOG data set for the index space. Any related SYSLGRNX rows are deleted
period of time spanning the failure. if DSNUM ALL is specified. The table space or index
v Job output. space is no longer recoverable at the ’site’. The ’site’
512 Messages
DSNU573I • DSNU581I
Severity:
DSNU585I csect-name REPORT RECOVERY obj-type
0 (informational) obj-qual.obj-name CURRENT
Explanation:
DSNU583I csect-name SYSLGRNX ROWS FROM
REPORT RECOVERY FOR obj-type The message is issued in response to the CURRENT
obj-qual.obj-name option of REPORT RECOVERY utility. It indicates that
only the information since the last recoverable point for
Explanation: the specified table space or index space is reported.
This is the header message for the SYSLGRNX section System action:
of the REPORT RECOVERY output. This section
displays the SYSLGRNX rows for the table space, index Normal utility processing continues.
space, or partition as specified in the REPORT Severity:
514 Messages
DSNU586I • DSNU591I
0 (informational) the next utility statement in the utility job step, if any.
If not, the utility job step is normally terminated, and
the resources held become available for further
DSNU586I csect-name REPORT RECOVERY obj-type
processing. The UTILID of the utility job step becomes
obj-qual.obj-name SUMMARY:
available for reuse. The output from REPORT
Explanation: RECOVERY is now available for RECOVER utility use.
Header message for the REPORT TABLESPACESET v If the return code is 8, utility processing is
output. The output contains all table spaces, tables, and terminated.
dependent tables associated with the table space v If the return code is 4, utility processing continues to
specified in the REPORT TABLESPACESET input the next request.
statement.
User response:
System action:
Determine the cause for unavailability. The -DISPLAY
Utility processing continues normally. DATABASE command can be used to determine the
status. After ensuring the object is available, resubmit
Severity: the job.
0 (informational) Severity:
8 (error) or 4 (warning)
DSNU588I csect-name NO DATA TO BE REPORTED
Explanation: DSNU591I csectname AN UNSUCCESSFUL
The message is issued when no data can be found for a COMPLETION OF A LOG READ,
section of the REPORT output. REASON=X’reason-code’
516 Messages
DSNU599I • DSNU602I
Severity:
DSNU601I csect-name INDEX creator.index-name
0 (Informational) POINTS TO A DIFFERENT
TABLESPACE.
Ensure that all indexes in the list point to the same System action:
database and resubmit the RUNSTATS job.
This message will be issued for each nonpartitioned
Problem determination: index, when INDEX ALL is specified.
518 Messages
DSNU608I • DSNU612I
the system; therefore, it cannot be restarted. flushed. No record of the utility job step is retained by
the system; therefore it cannot be restarted.
User response:
User response:
Examine prior error messages for error identification. If
the error can be corrected, resubmit the RUNSTATS Ensure that all tables in the list are in the specified
utility in a new utility job step. table space and resubmit the utility.
Problem determination: Problem determination:
Prior messages identify this error. See the Refer to the catalog table SYSIBM.SYSTABLES to
documentation for these messages in this manual for determine the table space in which the table is located.
additional problem determination. If you suspect an
Severity:
error in DB2, refer to Part 2 of Diagnosis Guide and
Reference for information on identifying and reporting 8 (error)
the problem.
Severity: DSNU610I csect-name catalog-table-name CATALOG
UPDATE FOR object-name SUCCESSFUL
8 (error)
Explanation:
DSNU608I csect-name USER NOT AUTHORIZED This message indicates that the updating of the
TO ACCESS obj-type obj-qual.obj-name. statistics columns in the CATALOG TABLE
’catalog-table-name’ was successful.
Explanation:
System action:
This user is not authorized to execute the RUNSTATS
utility against obj-type obj-qual.obj-name. Processing continues with the next catalog table.
obj-type INDEX or INDEXSPACE that was specified Severity:
obj-qual creator of the index or database-name of the 0 (informational)
index-space that was specified
obj-name DSNU611I csect-name COLUMN column-name NOT
index-name or index-space-name that was FOUND FOR TABLE creator.table-name
specified.
Explanation:
System action:
A column name, given as an operand of the COLUMN
The executing utility job step terminates. Work keyword, was not found in the specified table.
performed by previous utilities in the job step remains
in effect. Subsequent utility control statements are System action:
flushed. No record of the utility job step is retained in Validation of the utility invocation statement is
the system. Therefore it cannot be restarted. completed and the executing utility job step is
User response: terminated.
Explanation: Severity:
System action: pqty The primary space allocation for the dataset in
4K blocks.
RUNSTATS processing continues.
sqty The secondary space allocation for the dataset
User response: in 4K blocks.
Refer to Utility Guide and Reference for a description of dsnum The number of data sets.
RUNSTATS statistics.
extents The number of extents for the last data set of
Severity: the object.
0 (informational)
This message is routed to SYSPRINT.
520 Messages
DSNU615I • DSNU616I
avgrowlen
DSNU616I csect-name SYSCOLDIST CATALOG
The total number of bytes divided by the
STATISTICS FOR column-name,
number of rows.
column-name, column-name ...
space The space currently allocated for all extents,
CARDINALITY = cardinality
measured in kilobytes.
FREQUENCY COLVALUE
RUNSTATS uses floating point fields to report these
statistics. frequency X “hex_string”
frequency X “hex_string”
This message is routed to SYSPRINT.
... ...
System action: frequency X “hex_string”
RUNSTATS processing continues.
User response: Explanation:
Refer to Utility Guide and Reference for a description of The RUNSTATS utility issues this message to report the
RUNSTATS statistics. statistics collected for the indexed column
’column-name’. If more than one column is listed, then
Severity: the statistics collected and the column values reported
0 (informational) represent the concatenation of those columns.
The value for CARDINALITY is the number of distinct
DSNU615I csect-name SYSCOLUMNS CATALOG values for the listed columns. This statistic appears
STATISTICS FOR column-name only if the KEYCARD option was specified.
The values under FREQUENCY are the same as those
that are inserted into the DB2 catalog. Consider each
COLCARD = cardinality ’frequency’ as a four-digit number with an implied
COLCARDF = cardinality decimal point two places to the left of the final digit.
HIGH2KEY = high2key The resulting number is the percentage of total rows in
LOW2KEY = low2key the table that contain a particular value for the named
index columns.
Explanation: Frequency is associated with the occurrence of a single
The RUNSTATS utility issues this message to report the value which is listed under COLVALUE.
statistics collected for column column-name. Message Frequencies for the most frequent values are collected
DSNU619I is issued to identify the table. by default, or if the FREQVAL option is specified and
cardinality given a COUNT value greater than zero. If the default
The number of distinct values in the column is taken, then the ten most frequently occurring values
are reported in descending order of frequency.
high2key
v If fewer than ten values appear, then there are fewer
The second highest value of the column
than ten distinct values in the index.
low2key v If no values appear, then the values are uniformly
The second lowest value of the column distributed.
v If frequencies appear but column values do not, then
| For empty partitions, RUNSTATS sets the values for the invoker of RUNSTATS is not authorized to read
| HIGH2KEY and LOW2KEY to null (’’X). For a LARGE the table. Message DSNU619I is issued to identify
| table space, the value of COLCARD is set to -1. the table.
0 (informational)
DSNU617I csect-name SYSINDEXES CATALOG
STATISTICS FOR index-name
DSNU618I csect-name SYSINDEXPART CATALOG
CLUSTERED = clustered STATISTICS FOR index-name
CLUSTERRATIO = clusterratio PARTITION part-num
CLUSTERRATIOF = clusterratio
FIRSTKEYCARD = firstkeycard
FIRSTKEYCARDF = firstkeycard CARD = cardinality
NLEAF = nleaf CARDF = cardinality
NLEVELS = nlevels NEAROFFPOS = near-off
SPACEF = space NEAROFFPOSF = near-off
DATAREPREATFACTORF =datarepeatfactor FAROFFPOS = far-off
FAROFFPOSF = far-off
Explanation: LEAFDIST = leafdist
SPACEF = space
The RUNSTATS utility issues this message to report the DSNUM = dsnum
statistics collected for index ’index-name’. EXTENTS = extents
LEAFNEAR = leafnear
clustered
LEAFFAR = leaffar
Whether the table is actually clustered by this
PSEUDO_DEL_ENTRIES = pseudo_del_entries
index (YES or NO)
cluster-ratio
Explanation:
The percentage of data rows that are in
clustering order for this index The RUNSTATS utility issues this message to report the
statistics collected for index ’index-name’. If ’part-num’
datarepeatfactorf
equals 0, the statistics apply to the entire index. If
The anticipated number of data pages
’part-num’ is not 0, the statistics apply to the specified
repeatedly scanned, following index key order
partition of the index.
float-cluster-ratio
cardinality
A number between 0 and 1 that when
The number of rows in the partition or index.
multiplied by 100 gives the percentage of data
rows in the partition that are in clustering near-off
order for this index The number of rows pointed to that are near
but not at their optimal positions.
first-key
The number of distinct values of the first key far-off The number of rows pointed to that are far
column from their optimal positions.
full-key leafdist
The number of distinct values of the key 100 times the average distance in page IDs
between successive leaf pages during a
nleaf The number of active leaf pages in the index
sequential access of the index.
nlevels The number of levels in the index tree
space The space currently allocated for all extents,
space The space currently allocated for all extents, measured in kilobytes.
measured in kilobytes.
dsnum The number of data sets.
For a LARGE table space, the values of extents The number of extents for the last data set of
FIRSTKEYCARD and FULLKEYCARD are set to -1. the object.
RUNSTATS uses floating point fields to report these
leafnear
statistics.
The number of leaf pages physically near the
previous leaf page for successive active leaf
This message is routed to SYSPRINT.
pages.
System action:
leaffar The number of leaf pages located physically
Processing continues. far away from the previous leaf pages for
successive active leaf pages accessed in an
User response: index scan.
Refer to Utility Guide and Reference for a description of pseudo_del_entries
RUNSTATS statistics. The number of entries that are logically
Severity: deleted.
522 Messages
DSNU619I • DSNU623I
Explanation:
| For empty partitions, RUNSTATS set the values for
The RUNSTATS utility issues this message to report the | highkey, high2key, low2key, and lowkey to null (″X).
statistics collected for the specified partition of the table
space containing the table. The statistics follow: This message is routed to SYSPRINT.
cardinality User response:
The number of rows in the table space
Refer to Utility Guide and Reference for a description of
partition
RUNSTATS statistics.
npages The number of pages on which rows of the
Severity:
table space partition appear
0 (informational)
pctpages
The percentage of total pages of the table
space partition that contain rows from this DSNU626I csect-name SYSCOLDISTSTATS
table CATALOG STATISTICS FOR
column-name, column-name, column-name ...
nactive The number of active pages in the table space
PARTITION part-num
partition
CARDINALITY = cardinality
pctrowcomp
The percentage of rows compressed within the FREQUENCY COLVALUE
total number of active rows in the partition
frequency X “hex_string”
This message is routed to SYSPRINT. frequency X “hex_string”
User response: ... ...
Refer to Utility Guide and Reference for a description of frequency X “hex_string”
RUNSTATS statistics.
Explanation:
DSNU625I csect-name SYSCOLSTATS CATALOG
The RUNSTATS utility issues this message to report the
STATISTICS FOR column-name
statistics collected for the indexed column
PARTITION part-num
’column-name’ partition ’part-num’. If more than one
column is listed, then the statistics collected and the
COLCARD = cardinality
column values reported represent the concatenation of
HIGHKEY = highkey
those columns.
HIGH2KEY = high2key
LOW2KEY = low2key The value for CARDINALITY is the number of distinct
LOWKEY = lowkey values for the listed columns. This statistic appears
only if the KEYCARD option was specified.
Explanation:
The values under FREQUENCY are the same as those
The RUNSTATS utility issues this message to report the
that are inserted into the DB2 catalog. Consider each
statistics collected for column column-name partition
524 Messages
DSNU627I • DSNU629I
526 Messages
DSNU633I • DSNU638I
DSNU639I csect - UTILITY NOT ALLOWED TO The STOSPACE utility has found that a DB2 data set
RUN ON INDEX SPACE = iiiiiiii IN has been migrated by the Data Facility Hierarchical
ROSHARE READ DATABASE = Storage Manager. The amount of storage space used
dddddddd cannot be determined for DATA SET ’nnn’ of
INDEXSPACE ’iiiiiiii’ in DATABASE ’dddddddd’. The
Explanation: space allocation information in the catalog will not
An attempt to execute the STOSPACE utility on an include the storage used by the migrated data set.
index space defined in a ROSHARE READ database System action:
failed. The STOSPACE utility is only allowed to execute
in a ROSHARE OWNER or nonshared database. Processing continues to the next data set in the storage
group, if any.
System action:
System programmer response:
Processing continues to the next table space or index
space in the storage group, if any. If required, the data set may be recalled using HSM,
and the STOSPACE utility may be run again.
User response:
Severity:
Resubmit the utility job on the system in which the
database was defined with the ROSHARE OWNER 0 (informational)
attribute.
Severity: DSNU642I csect-name UNABLE TO ACCESS DBD
FOR DATABASE = dddddddd,
4 (warning) TABLESPACE = tttttttt
Explanation:
DSNU640I csect-name DATA SET= nnn OF
TABLESPACE= tttttttt IN DATABASE= A database descriptor control block could not be
dddddddd HAS BEEN MIGRATED BY accessed by the STOSPACE utility. Information in the
HSM DBD is required before space allocation data can be
obtained from the appropriate ICF catalog. Storage
Explanation: space used by table space ’tttttttt’ in database
The STOSPACE utility has found that a DB2 data set ’dddddddd’ cannot be determined.
has been migrated by the Data Facility Hierarchical System action:
Storage Manager. The amount of storage space used
cannot be determined for DATA SET ’nnn’ of Processing continues with the next storage group.
TABLESPACE ’tttttttt’ in DATABASE ’dddddddd’. The
System programmer response:
space allocation information in the catalog will not
include the storage used by the migrated data set. Determine if the reason for the DBD unavailability may
require system corrective action.
System action:
User response:
Processing continues to the next data set in the storage
group, if any. Determine the cause for unavailability. The database
may be stopped or the DBD may be marked as invalid.
System programmer response:
The -DISPLAY DATABASE command can be used to
If required, the data set may be recalled using HSM, determine the status.
and the STOSPACE utility may be run again.
Problem determination:
Severity:
A DSNT501I message may have been sent to the
0 (informational) operator console. If so, see the problem determination
section for message DSNT501I.
Severity:
4 (warning)
528 Messages
DSNU643I • DSNU646I
8 (error)
DSNU643I csect-name UNABLE TO ACCESS DBD
FOR DATABASE = dddddddd,
INDEXSPACE = tttttttt DSNU645I csect-name NO STORAGE GROUPS
NAME FOUND
Explanation:
Explanation:
A database descriptor control block could not be
accessed by the STOSPACE utility. Information in the You requested the STOSPACE utility to report on all
DBD is required before space allocation data can be storage groups, but no storage group was found.
obtained from the appropriate ICF catalog. Storage
space used by index space ’tttttttt’ in database System action:
’dddddddd’ cannot be determined. This message indicates completion of the STOSPACE
System action: utility. Processing continues to the next utility statement
in the utility job step, if any. If not, the utility job step
Processing continues with the next storage group. is normally terminated. Resources are released to their
prior availability state. The UTILID of the utility job
System programmer response:
step becomes available for reuse.
Determine if the reason for the DBD unavailability may
System programmer response:
require system corrective action.
This message indicates either that no storage groups
User response:
were defined by the installation process (or by
Determine the cause for unavailability. The database subsequent SQL procedures) or they have all been
may be stopped or the DBD may be marked as invalid. dropped. If this is an error, the required storage groups
The -DISPLAY DATABASE command can be used to must be re-created with the CREATE STOGROUP SQL
determine the status. statement.
Problem determination: User response:
A DSNT501I message may have been sent to the This message indicates that there are no storage groups
operator console. If so, see the problem determination defined. Consult the system programmer to determine
section for message DSNT501. the reason for this condition.
Severity: Severity:
4 (warning) 4 (warning)
This condition does not prevent subsequent processing.
DSNU644I csect-name USER user-name NOT
AUTHORIZED FOR STOSPACE
DSNU646I csect-name STORAGE GROUP NAME
UTILITY
nnnnnnnn NOT FOUND
Explanation:
Explanation:
Utility processing for the user indicated on the job
This message is issued by STOSPACE when one of the
statement failed, because the user is not authorized to
requested storage groups is not found.
execute the STOSPACE utility.
The following circumstances may exist:
System action:
1. When an inconsistency occurs between
Utility processing is terminated without invoking the SYSIBM.SYSSTOGROUP at the beginning of
requested utility or utilities. STOSPACE execution and SYSIBM.SYSSTOGROUP
System programmer response: during or at the end of processing. The
inconsistency may be due to a storage group being
If the USER specified on the job statement is incorrect, dropped during the processing of STOSPACE utility.
correct it, and resubmit the job. To run the STOSPACE
2. The storage group name is misspelled.
utility, the user must either have SYSADM authority or
have been granted the STOSPACE privilege. Use the System action:
SQL GRANT command to give the user the desired
Processing proceeds normally to the next storage group
authority.
if any.
User response:
User response:
Contact the systems programmer for assistance with
Verify the existence or spelling of the storage group
your security classification.
names by referring to SYSIBM.SYSSTOGROUP. Submit
Severity: another request with the correct storage group
designated.
Severity: Explanation:
530 Messages
DSNU653I • DSNU656I
532 Messages
DSNU662I • DSNU668I
534 Messages
DSNU678I • DSNU683I
System action:
DSNU680I csect-name PAGE hex-page-number
Utility returns completion code=8.
Explanation:
Programmer response:
This message is issued as an identifier at the top of
Correct the ROWID or VERSION. Only ROWID and each page dumped by the REPAIR DUMP PAGES
VERSION values previously generated by DB2 can be facility. ’hex-page-number’ identifies the page which is
used. The most likely source values of a ROWID and about to be dumped.
VERSION are messages DSNU743I, DSNU805I, and
System action:
DSNU806I from the CHECK DATA or CHECK LOB
utilities. Processing continues.
Severity:
DSNU678I csect-name VERIFY, REPLACE, DUMP,
0 (informational)
OR DELETE BEFORE LOCATE
Explanation:
DSNU681I csect-name SET NOCHECKPEND
The REPAIR utility was requested to VERIFY, OPERATION SUCCESSFUL
REPLACE, or DUMP or DELETE a page or record and
Explanation:
that page of record could not be located.
This message reports the successful completion of the
System action:
REPAIR SET TABLESPACE NOCHECKPEND utility
Processing begins at the next LOCATE statement, if operation. The check pending restriction has been
there is one. Subsequent utilities in the same job step removed from the specified table space.
will not be executed.
System action:
User response:
The REPAIR SET statement has completed normally.
Correct the REPAIR control statements, and resubmit
Severity:
the request in a new utility job step. If you suspect an
error in DB2, refer to Part 2 of Utility Guide and 0(informational)
Reference for information on identifying and reporting
the problem.
DSNU682I csect-name SET NORCVRPEND
Severity: OPERATION SUCCESSFUL
8 (error) Explanation:
This message reports the successful completion of the
DSNU679I csect-name MULTIPLE ’DELETE’S PER REPAIR SET NORCVRPEND utility operation. The
’LOCATE’ NOT ALLOWED RECOVERY PENDING restriction has been removed
from the specified table space, from the specified index,
Explanation:
or from all indexes of the specified table space.
The REPAIR utility was requested to DELETE the same
System action:
record more than once. Only one DELETE is allowed
per LOCATE RID or LOCATE KEY. The REPAIR SET statement has completed normally.
System action: Severity:
Processing begins at the next LOCATE scope, if any. 0 (informational)
Subsequent utilities in the same job step are not
executed.
DSNU683I csect-name REPAIR LEVELID
User response: OPERATION SUCCESSFUL.
Remove all but one DELETE control statement from Explanation:
each LOCATE scope which is intended to delete a
record. If you suspect an error in DB2, refer to Part 2 of The REPAIR utility with the LEVELID clause
Utility Guide and Reference for information on completed successfully.
identifying and reporting the problem. System action:
Severity: Processing completed successfully.
8 (error) User response:
Submit any other REPAIR control statements in a
different job step.
Explanation: | Severity:
536 Messages
DSNU692I • DSNU700I
| This message is issued for the following reasons: | System programmer response:
Problem determination: The values for DBNAME and TSNAME must be the
same for all indexes specified in the index name list
To CHECK or REBUILD ALL INDEXES in a table and must be the same as the table space name specified
space, use the TABLESPACE keyword, but do not use on the TABLESPACE keyword if provided.
the list option. This is one way to correct this error. If
you want to correct the list of indexes specified in the Severity:
index name list, the following procedure will locate the 8 (error)
table space name related to the index ’iiii’.
The index name ’iiii’ reported in the message is of the DSNU705I csect-name UNLOAD PHASE
form ’creator.name’. Obtain the TBCREATOR and COMPLETE, ELAPSED TIME=tttt
TBNAME columns from the DB2 catalog table
SYSIBM.SYSINDEXES where columns CREATOR and Explanation:
NAME have the values reported in the message. Obtain The unload phase of the CHECK or REBUILD INDEX
the DBNAME and TSNAME columns from the DB2 utility is complete.
catalog table SYSIBM.SYSTABLES, where columns
CREATOR and NAME have the values obtained from System action:
TBCREATOR and TBNAME of SYSIBM.SYSINDEXES.
Processing continues.
The values for DBNAME and TSNAME must be the
Severity:
same for all indexes specified in the index name list
and must be the same as the table space name specified 0 (informational)
on the TABLESPACE keyword (if provided).
538 Messages
DSNU706I • DSNU711I
System action:
DSNU706I csect-name ROW IS IN WRONG
PARTITION RID=rrrr, INDEX=iiii, CHECK utility processing continues.
KEY=kkkk, CORRECT PART=pppp,
WRONG PART=wwww User response:
Explanation: Drop the unique index, and delete the duplicate rows.
Re-create the index.
The row at RID ’rrrr’ resides in the wrong partition.
The partitioning KEY ’kkkk’ for partitioning INDEX Severity:
’iiii’ indicates that the row at RID ’rrrr’ should reside in 4 (warning)
partition ’pppp’, however the rid indicates that the row
contains partition ’wwww’.
DSNU709I csect-name NO INDEX ENTRY FOR
System action: ROW. RID=rrrr, INDEX=iiii, KEY=kkkk
Utility processing continues. Explanation:
User response: The CHECK utility CHECKIDX phase found that index
Run RECOVER TABLESPACE utility to recover the iiii is missing an entry for the row at RID rrrr with key
data or run REPAIR DELETE utility to delete the row kkkk.
’rrrr’ followed by CHECK INDEX and CHECK DATA System action:
utility if referential constraints are involved.
| CHECK utility processing continues. The utility will
Problem determination: | complete with return code 4.
The inconsistency between the table space partition User response:
number of a row and the index space partition number
of the row’s clustering key may be due to a DB2 Run the REBUILD INDEX utility for index iiii.
internal error, but is most likely due to a user using the Severity:
DSN1COPY service aid to populate a target table space
with data from a source table space when the clustering 4 (warning)
key values on the source and target table spaces are not
identical. DSNU710I csect-name INDEX ENTRY CONTAINS
Severity: INVALID ZERO REPRESENTATION.
RID=rrrr, INDEX=iiii, KEY=kkkk
4 (warning)
Explanation:
DSNU707I csect-name INDEX ENTRY POINTS TO The CHECK utility CHECKIDX phase found that index
WRONG TABLE. OBID=oooo, RID=rrrr, ’iiii’ has an entry that contains a negative zero. The
INDEX= index entry is for the row at RID ’rrrr’ with key ’kkkk’.
The CHECK utility CHECKIDX phase found that index CHECK utility processing continues.
’iiii’ contains an entry for key ’kkkk’ that points to User response:
record at RID ’rrrr’, but the record belongs to the table
with OBID ’oooo’. Run the REBUILD INDEX utility for index ’iiii’.
System action: Severity:
CHECK utility processing continues. 4 (warning)
User response:
DSNU711I csect-name NO ROW FOR INDEX
Run the REBUILD INDEX utility for index ’iiii’. ENTRY. RID=rrrr, INDEX=iiii, KEY=kkkk
Severity: Explanation:
4 (warning) The CHECK utility CHECKIDX phase found that the
index ’iiii’ contains an entry that has no row. The index
DSNU708I csect-name INDEX IS NOT UNIQUE. entry contained RID ’rrrr’ and key ’kkkk’, but RID ’rrrr’
INDEX=iiii, KEY=kkkk is not a valid record.
The CHECK utility CHECKIDX phase found that CHECK utility processing continues.
unique index ’iiii’ contains a nonunique key, ’kkkk’.
User response:
DSNU717I csect-name nnnn ENTRIES CHECKED
Run the REBUILD INDEX utility for index ’iiii’. FOR INDEX=iiii PARTITION=pppp
Severity: Explanation:
DSNU715I csect-name MULTIPLE INDEX ENTRIES DSNU719I csect-name nnnn ENTRIES CHECKED
FOR ROW. RID=rrrr, INDEX=iiii, FOR INDEX iiii
KEY=kkkk
Explanation:
Explanation:
The CHECK utility has completed checking index ’iiii’
The CHECK utility CHECKIDX phase found that index and has processed ’nnnn’ index entries. This message
’iiii’ has multiple index entries for the row at RID ’rrrr’ will be issued once for each index checked.
with key ’kkkk’.
System action:
System action:
Processing continues.
CHECK utility processing continues.
Severity:
User response:
0 (informational)
Run the REBUILD INDEX utility for index ’iiii’.
Severity:
4 (warning)
540 Messages
DSNU720I • DSNU728I
Severity: 4 (warning)
8 (error)
DSNU727I csect-name TABLESPACE tsp IS NOT
CHECK PENDING
DSNU722I csect-name - USER userid DOES NOT
HAVE INSERT AUTHORITY ON Explanation:
EXCEPTION TABLE
This message is issued when ’CHECK DATA
Explanation: TABLESPACE tsp SCOPE PENDING’ is specified and
the CHECK DATA utility finds that the table space is
The CHECK DATA utility was run with FOR not in a check pending state. The CHECK DATA utility
EXCEPTION specified but user ’userid’ does not have skips table space ’tsp’ and will continue with any other
authority to insert into an exception table specified in table space specified. The catalog fields that reflect the
the utility statement. extent of a check pending state are updated to ensure
System action: that they indicate that no check is required.
User response:
DSNU733I csect-name ROW (RID=rrrrrr) HAS NO
Examine the utility input statement to determine the PARENT FOR rel
reason for the missing table named in the message.
Correct the input statement to include the missing table Explanation:
and resubmit the job. Refer to Utility Guide and This message is issued when the CHECK DATA utility
Reference for information about the FOR EXCEPTION finds a row in a dependent table without a parent. The
clause of the CHECK DATA utility and use of row with RID, ’rrrrrr’, has no parent for the
exception tables. relationship named ’rel’. This message is always
Severity: proceeded by a DSNU730I message that identifies the
table in error.
8 (error)
System action:
This message is issued when the CHECK DATA utility Refer to Part 2 of the Administration Guide for a
begins to process a table. The name of table being discussion of the check pending operation.
checked is ’tab’. Severity:
System action: 4 (warning)
Processing continues.
Severity: DSNU735I csect-name DUPLICATE TABLESPACE
tsp PARTITION part NAMES EXIST IN
0 (informational) THE TABLESPACE LIST
Explanation:
This message is issued by the CHECK DATA utility
542 Messages
DSNU736I • DSNU742I
Refer to Part 2 of the Administration Guide for a Utility returns completion code=4. The index is set
discussion of the check pending operation and recovery Recover Pending.
procedures.
Programmer response:
Severity:
Use REBUILD INDEX to correct the index on the
4 (warning) auxiliary table.
544 Messages
DSNU756I • DSNU764I
DSNU765I csect-name THE DB2 CATALOG IS NOT 5. Name cannot be the qualifier of an existing
AT THE REQUIRED LEVEL. CATALOG object that is referenced by a view,
NOT UPDATED function, materialized query table, or
trigger.
Explanation: 6. OWNER and SCHEMA clauses are
The DB2 catalog is not at the proper catalog level to mutually exclusive, and cannot be specified
migrate the catalog. This error can occur due to the in the same CATMAINT UPDATE
following reasons: statement.
v Attempting to migrate the catalog from a DB2 release 7. OWNER is specified, but role is not
that does not support migration present. The user has to run under a
trusted context.
v Attempting to migrate DB2 Stored Procedures prior
to a catalog migration 8. Name cannot be referenced in check
conditions.
System action:
9. Name is too long to fit in PATHSCHEMA.
Utility processing terminates PATHSCHEMA cannot exceed 2048 bytes.
User response: System action:
Fall back to the previous release if the catalog is not at Utility terminates with return code 8.
the correct level for a migration. Migrate only from
User response:
DB2 releases that support migration.
Remove or modify the invalid name, and then rerun
Severity:
the utility.
8 (error)
Severity:
8 (error)
DSNU766I csect-name THE CATALOG HAS
ALREADY BEEN MIGRATED. NO
ACTION WILL BE TAKEN DSNU768I csect-name CATMAINT CONVERT
COMPLETE FOR INDEX index-name
Explanation:
Explanation:
The catalog was already successfully migrated. There is
no reason to rerun the catalog migration job. Therefore, The conversion is complete for index index-name.
no action is taken to update the DB2 catalog.
System action:
System action:
Processing continues with the next index.
Processing ends.
Severity:
Severity:
0 (informational)
0 (informational)
DSNU769I csect-name THE BUILD PHASE FAILED
DSNU767I INVALID name IS SPECIFIED, REASON FOR INDEX index-name REASON reason
reason-code
Explanation:
Explanation:
The CATMAINT CONVERT build phase failed for
This message is issued during CATMAINT UPDATE index index-name. This message and others identify the
SCHEMA, CATMAINT UPDATE VCAT, or CATMAINT actions that should be taken.
UPDATE OWNER processing if an invalid name is
specified. System action:
name Identifies the invalid name. Utility processing continues with the next index and
will terminate with return code 8.
546 Messages
DSNU770I • DSNU775I
8 (error) Severity:
0 (informational)
DSNU776I csect-name CATMAINT operation ERROR
- error-text
DSNU780I csect-name DSNUTILB LEVEL rel1
Explanation: INVALID WITH SUBSYSTEM LEVEL
rel2
The CATMAINT utility halted because the catalog
contains view(s) on the SYSCOLDIST and/or Explanation:
SYSCOLDISTSTATS catalog tables.
JCL has been submitted which executes level ’rel1’ of
System action: DSNUTILB against a level ’rel2’ DB2 subsystem. The
levels must match.
Utility processing halts.
System action:
User response:
The utility terminates with a return code of 8.
Remove the views on these catalog tables. Then retry
the failing CATMAINT operation. This message is User response:
followed by an abend04E RC00E40601. See the problem
Determine the DB2 subsystem against which you wish
determination text of RC00E40601 for additional
to execute. Determine which STEPLIB data set contains
information.
the corresponding DSNUTILB load module. Correct the
Severity: JCL to specify the correct data set on the STEPLIB DD
statement and the correct DB2 subsystem on the EXEC
0 (informational) statement and resubmit the job.
Severity:
DSNU777I csect-name CATMAINT operation STATUS
status-msg 8 (error)
Explanation:
DSNU781I csect-name RESTART OF LEVEL rel1
The CATMAINT utility is processing CATMAINT UTILITY AT LEVEL rel2 INVALID
operation. status-msg indicates where CATMAINT is in
the operation process. Explanation:
548 Messages
DSNU783I • DSNU795I
table space. Activity at another system level has left all v CATALOG CONTAINS TYPE 1 INDEXES
image copies for this table space inconsistent with the
System action:
DB2 LOG.
Utility processing halts. No SYSABEND dump or SVC
System action:
dump is requested.
The utility terminates with a return code of 8.
User response:
User response:
Any unsupported objects/items should be removed
The table space, in its entirety can not be recovered. from the DB2 catalog in the previous release. The
Individual data sets may be recoverable using the DSNTIJPM and DSNTESQ jobs can be used to identify
DSNUM() keyword. any unsupported objects that are found in a subsystem.
Remove any unsupported objects in the DB2 catalog
Severity:
and retry the failing CATMAINT operation. This
8 (error) message is followed by an abend 04E RC 00E40601.
Severity:
DSNU783I csect-name INDEXES DSNSCT02,
8 (error)
DSNLUX01, DSNLUX02 and DSNLLX02
HAVE SUBPAGES VALUE GREATER
THAN 1 AND CANNOT BECOME DSNU790I csect-name utility-name option IS NOT
GROUP BUFFER POOL DEPENDENT. ALLOWED WHEN THERE ARE
OUTSTANDING UTILITIES STARTED
Explanation:
FROM PRIOR RELEASES.
CATMAINT CONVERT TO TYPE 1 DIRECTORY alters
Explanation:
the indexes DSNSCT02, DSNLUX01, DSNLUX02, and
DSNLLX02 to type 1 with more than one subpage. In a The utility to be executed may have conflicts with other
data sharing environment, there cannot be inter-DB2 outstanding utilities started from prior releases.
R/W interest on type 1 indexes with more than one
utility-name is the name of the utility that detected the
subpage (they cannot become group buffer pool
conflict.
dependent). This means that any read or update request
that causes inter-DB2 R/W interest on these directory option is the option specified to the utility that detected
indexes is denied with a ’resource unavailable’ the conflict.
condition.
System action:
For directory indexes, only type 2 indexes can have full
R/W sharing among data sharing members. The request is rejected.
550 Messages
DSNU811I • DSNU814I
The column named column-name did not have an index If AUXERROR INVALIDATE was specified, use SQL
entry in the on the auxiliary index named index-name. to update the LOB column or delete the base table row.
The version for the LOB column was version. Rerun the CHECK DATA utility with AUXERROR
INVALIDATE specified. If all Auxiliary Column Check
| The state changes take place if SHRLEVEL
errors were corrected, Aux Warning will be reset.
| REFERENCE is specified or defaulted. If SHRLEVEL
| CHANGE is specified, the state of the table space The REPAIR utility can be used to reset the Aux
| remains unchanged. Warning state.
System action:
DSNU813I csect-name - LOB IN TABLE
If AUXERROR REPORT was specified, this error is
SPACE=lob_table_space_name WITH
reported only. The base table space is set to an Aux
ROWID=rowid AND VERSION=version
Check Pending state.
HAS NO BASE TABLE ROW
If AUXERROR INVALIDATE was specified, the LOB
Explanation:
column is set invalid. The base table space is set to an
Aux Warning state. The CHECK DATA utility found a LOB in the LOB
table space named lob_table_space_name but did not find
Utility returns completion code=4.
a row in the base table for this LOB. The LOB has a
Programmer response: ROWID of rowid and version of version.
CHECK DATA relies on information in LOB table space | The state changes take place if SHRLEVEL
and in the auxiliary index being correct. Before running | REFERENCE is specified or defaulted. If SHRLEVEL
CHECK DATA to check auxiliary columns, first run | CHANGE is specified, the state of the table space
CHECK LOB and then run REBUILD INDEX or | remains unchanged.
CHECK INDEX. CHECK LOB ensures the validity of
System action:
the LOB table space. REBUILD INDEX or CHECK
INDEX ensures the validity of the auxiliary index. Utility returns completion code=4.
If AUXERROR REPORT was specified, run the Programmer response:
CHECK DATA utility with AUXERROR INVALIDATE
CHECK DATA relies on information in the index on the
to set the base table column invalid.
auxiliary table and LOB table space being correct.
If AUXERROR INVALIDATE was specified, use SQL Before running CHECK DATA to check auxiliary
to update the LOB column or delete the base table row. columns, first run CHECK LOB and then run REBUILD
Rerun the CHECK DATA utility with AUXERROR INDEX or CHECK INDEX. CHECK LOB ensures the
INVALIDATE specified. If all Auxiliary Column Check validity of the LOB table space. REBUILD INDEX or
errors were corrected, Aux Warning will be reset. CHECK INDEX ensures the validity of the auxiliary
index.
The REPAIR utility can be used to reset the Aux
Warning state. The LOB can be deleted using the REPAIR utility.
Specify LOCATE ROWID VERSION DELETE.
DSNU811I csect-name - TABLE=table_name
COLUMN=column_name IS INVALID DSNU814I csect-name - TABLE=table_name
ROWID=rowid VERSION=version COLUMN=column_name IS ZERO OR
NULL BUT ENTRY IN INDEX
Explanation:
index-name FOUND ROWID=rowid
The CHECK DATA utility found a record in the table VERSION=version
named table-name in the row with ROWID rowid. The
Explanation:
column named column-name was marked invalid by a
prior execution of the CHECK DATA utility with The CHECK DATA utility found a record in the table
AUXERROR INVALIDATE specified. The version for named table-name in the row with a ROWID of rowid.
the LOB column was version. The column named column-name was indicated null or
zero length, but an index entry with the same ROWID
| The state changes take place if SHRLEVEL
was found in the index on the auxiliary table named
| REFERENCE is specified or defaulted. If SHRLEVEL
index-name. The version for the LOB column was
| CHANGE is specified, the state of the table space
version.
| remains unchanged.
| The state changes take place if SHRLEVEL
System action:
| REFERENCE is specified or defaulted. If SHRLEVEL
Utility returns completion code=4. The base table space | CHANGE is specified, the state of the table space
is set to a Aux Warning state. | remains unchanged.
552 Messages
DSNU821I • DSNU824I
| nodeid-key-hex-string
| If all auxiliary column check errors were corrected,
| Indicates if the NODEID index key is in
| auxiliary warning will be reset.
| hexadecimal format. | Severity:
| rid-hex-string | 4 (warning)
| Indicates if the RID referenced by this index
| entry is in hexadecimal format.
| DSNU823I XML COLUMN column-name IN XML
| crname.ixname | TABLE SPACE dbname, tsname HAS NO
| The CREATOR NAME and INDEX name that | BASE TABLE ROW. DOCID
| are specified. | DocId-hex-string
| dbname.tsname | Explanation:
| The DATABASE NAME and TABLESPACE
| NAME that are specified. | The CHECK DATA utility found an XML column in the
| XML table space, but did not find a row in the base
| System action: | table for this XML. The XML column has the document
| The index is set RECOVER PENDING.
| identifier that is specified.
| Programmer response:
| The state changes take place if SHRLEVEL
| REFERENCE is specified or defaulted. If SHRLEVEL
| Use REBUILD INDEX or RECOVER to correct the | CHANGE is specified, the state of the table space
| index on the XML table. | remains unchanged.
| Severity: | System action:
| 4 (warning) | Processing continues until you receive completion code
| 4. This is an informational message. XML processing is
| not hindered because an XML column entry exists in
| DSNU822I XML COLUMN column-name IN TABLE
| the auxiliary index, but not in the base table.
| tbcreator, tbname IS MISSING IN INDEX
| ixcreator, ixname DOCID DocId-hex-string | Programmer response:
| Explanation: | Before running CHECK DATA to check the auxiliary
| columns, run REBUILD INDEX or CHECK INDEX.
| This message is issued when a base table row contains
| REBUILD INDEX or CHECK INDEX ensures the
| an XML column value, but no index entry is found for
| validity of the auxiliary index.
| the XML column value in the NODEID index.
| Severity:
| The state changes take place if SHRLEVEL
| REFERENCE is specified or defaulted. If SHRLEVEL | 4 (warning)
| CHANGE is specified, the state of the table space
| remains unchanged.
| DSNU824I XML COLUMN column-name IN TABLE
| System action: | crname, tbname IS NULL BUT ENTRY IN
| INDEX crname, ixname FOUND. DOCID
| If you specified AUXERROR REPORT, then only this
| DocId-hex-string
| error is reported. The base table space is set to an
| auxiliary check pending state. If you specified | Explanation:
| AUXERROR INVALIDATE, then the XML column is
| set to invalid. The base table space is set to an auxiliary
| This message is issued when a row in an XML table
| warning state.
| exists, but it is not referenced by a base table row.
| System action:
DSNU830I csect-name - INDEX= index-name IS IN
| Processing continues. This is an informational message. REBUILD PENDING STATE
| XML processing is not hindered because an XML
Explanation:
| column entry exists in the auxiliary index, but the XML
| column in the base table is marked null or has a null If the RECOVER utility issued this message, the
| length. corresponding table space to this index was recovered
to a point in time with keyword TOCOPY,
| Programmer response: TOLOGPOINT, or TORBA. Thus, the index was placed
| Before running CHECK DATA to check the auxiliary in rebuild pending status.
| columns, run REBUILD INDEX or CHECK INDEX.
If the REBUILD INDEX utility issued this message, the
| REBUILD INDEX or CHECK INDEX ensures the
index is in rebuild pending status. Either duplicate
| validity of the auxiliary index.
index entries existed during the BUILD phase of the
| Severity: REBUILD INDEX, or invalid KEY/RIDs, which do not
belong to the partition of the cluster index, were
| 4 (warning) detected. The duplicate index entries or invalid
KEY/RID entries must be resolved before starting the
| DSNU826I XML COLUMN column name IN TABLE REBUILD INDEX utility again to rebuild the index and
| tbcreator, tbname HAS BEEN MARKED remove the index from rebuild pending status.
| INVALID BY THE CHECK UTILITY. If the REORG utility with SHRLEVEL REFERENCE or
| DOCID DocId hex string CHANGE (or -TERM UTILITY) issued this message,
| Explanation: the index is in rebuild pending status. During the
renaming of a data set during REORG, either a data set
| This message is issued when an XML column value is with the source name did not yet exist or a data set
| marked invalid during CHECK DATA processing for with the target name already existed.
| AUXERROR INVALIDATE or XMLERROR
| INVALIDATE. User response:
| auxiliary warning will be reset if no invalid columns The RECOVER utility completed successfully.
| remain. User response:
| Severity: Use the REBUILD utility with the ALL option to
| 0 (informational) rebuild all indexes over the recovered table space.
Severity:
4 (warning)
554 Messages
DSNU832I • DSNU862I
Severity: Explanation:
RECOVER utility is unable to recover the index or This message indicates the beginning of DIAGNOSE
index space as requested because an ALTER COLUMN DISPLAY MEPL processing.
VARCHAR has been performed. The current column Severity:
definition is no longer consistent with the image copy
and log records which would be used to perform the 0 (informational)
requested recovery.
User response: DSNU862I DISPLAY AVAILABLE UTILITIES.
MAP: bit-map
Use the REBUILD INDEX utility to rebuild the index
from the tablespace. Explanation:
Severity: This message is the end-result of a DIAGNOSE
DISPLAY AVAILABLE control statement. It displays the
8 (error) utilities that are available on this subsystem. The
message contains a machine-readable bit-map, and
556 Messages
DSNU868I • DSNU874I
System action:
DSNU871I csectname DISPLAY DBET DATABASE
This message identifies the SYSUTIL UTILITY dbname
CHECKPOINT/RESTART INFORMATION section of
Explanation:
the DIAGNOSE DISPLAY SYSUTIL output.
This message is the heading for display output of the
Severity:
database exception table (DBET) entry associated with
0 (informational) database dbname.
System action:
DSNU868I csect-name DISPLAY SYSUTIL UTILITY
DIAGNOSE DISPLAY DBET processing started for the
DEPENDENT AREA
named database.
Explanation:
Severity:
This message is the header message for the SYSUTIL
0 (informational)
UTILITY DEPENDENT INFORMATION section of the
DIAGNOSE DISPLAY SYSUTIL output. This section
displays the utility dependent area of the SYSUTIL DSNU872I csectname DISPLAY DBET TABLE
record and contains information particular to the utility SPACE tsname
which the SYSUTIL record is referencing.
Explanation:
System action:
This message is the heading for display output of the
This message identifies the SYSUTIL UTILITY database exception table (DBET) entry associated with
DEPENDENT INFORMATION section of the table space tsname.
DIAGNOSE DISPLAY SYSUTIL output.
System action:
Severity:
DIAGNOSE DISPLAY DBET processing started for the
0 (informational) named table space.
Severity:
DSNU869I csect-name DISPLAY SYSUTIL
0 (informational)
COMPLETE
Explanation:
DSNU873I csectname DISPLAY DBET INDEX
This message is issued in response to normal index-name
completion of DISPLAY SYSUTIL processing.
Explanation:
System action:
This message is the heading for display output of the
This message indicates the end of DISPLAY SYSUTIL database exception table (DBET) entry associated with
processing. index index-name.
Severity: System action:
0 (informational) DIAGNOSE DISPLAY DBET processing started for the
named index.
DSNU870I csect-name NO SYSUTIL RECORD Severity:
FOUND
0 (informational)
Explanation:
This message is issued if no SYSUTIL records are found DSNU874I csectname NO DBET ENTRY FOUND
when DISPLAY SYSUTIL is specified. FOR THE SPECIFIED OBJECT
System action: Explanation:
This message indicates the end of DISPLAY SYSUTIL There is no database exception table (DBET) entry
processing. associated with the specified object.
Severity: System action:
4 (warning) Processing continues normally.
Severity:
4 (warning)
After diagnosis procedure in progress is completed, This message marks the start of a DBD comparison for
reply to this message to continue execution. Any reply the REPAIR DBD TEST or REPAIR DBD DIAGNOSE
is valid. utility. The DBID of the DBD being compared against
the DB2 Catalog is ’xxxx’.
User response:
System action:
See operator response.
DBD checking continues normally.
Severity:
Severity:
4 (warning)
0 (informational)
558 Messages
DSNU903I • DSNU911I
Severity: 0 (informational)
0 (informational)
DSNU907I csect-name - REBUILT VALUE ’cc..cc’
DSNU903I csect-name - REBUILT OBD AT OFFSET Explanation:
X’xxxxxxxx’ IN REBUILT DBD
This message shows a character string which is the
Explanation: value of a field in the OBD which was rebuilt from the
DB2 catalog. The character string is ’cc..cc’.
Following this message is a hexadecimal dump of the
OBD that was rebuilt from the DB2 Catalog. In the System action:
message, ’xxxxxxxx’ is the hexadecimal offset from the
DBD checking continues normally.
beginning of the rebuilt DBD as it appears later in the
REPAIR DBD DIAGNOSE output. Severity:
System action: 0 (informational)
DBD checking continues normally.
DSNU908I csect-name - EXISTING OBD IS obd-type
Severity:
Explanation:
0 (informational)
This message shows the OBD type of the OBD which
exists on the DSNDB01.DBD01 page set.
DSNU904I csect-name - EXISTING VALUE X’xx..xx’
System action:
Explanation:
DBD checking continues normally.
This message shows a hexadecimal string which is the
value of a field in the OBD as it exists on the Severity:
DSNDB01.DBD01 page set. The hexadecimal string is
’xx..xx’. 0 (informational)
System action:
DSNU909I csect-name - REBUILT OBD IS obd-type
DBD checking continues normally.
Explanation:
Severity:
This message shows the OBD type of the OBD which
0 (informational) was rebuilt from the DB2 catalog.
System action:
DSNU905I csect-name - REBUILT VALUE X’xx..xx’
DBD checking continues normally.
Explanation:
Severity:
This message shows a hexadecimal string which is the
value of a field in the OBD which was rebuilt from the 0 (informational)
DB2 catalog. The hexadecimal string is ’xx..xx’.
System action: DSNU910I csect-name - EXISTING DBD
Explanation: Severity:
0 (informational) Explanation:
This message is used when listing the OBDs in the
DSNU912I csect-name - phase-completion-message -- nn REPAIR DBD DIAGNOSE utility. The OBID of the OBD
ERRORS WERE FOUND being listed is ’obid’. The offset to the OBD within the
EXISTING DBD which is displayed later in the output
Explanation: is ’xxxxxxxx’. The offset to the OBD within the
This message marks the end of a processing phase in REBUILT DBD which is displayed later in the output is
the DBD comparison for a REPAIR DBD TEST or ’yyyyyyyy’. A short description of the state of the OBD
REPAIR DBD DIAGNOSE utility. In the message, ’nn’ is ’obd-description’.
indicates the number of errors detected while System action:
processing. Informational and warning messages are
not added into the error count. DBD checking completed.
System action: Severity:
DBD checking continues normally. 0 (informational)
Severity:
DSNU916I csect-name - OBDS DIFFER AT OFFSET
0 (informational) X’xxxxxxxx’ field-name - INFORMATION
NOT IN DB2 CATALOG
DSNU913I csect-name - OBD X’xxxx’ COMPARISON Explanation:
COMPLETE -- nn ERRORS WERE
FOUND This message indicates the value of a field in the OBD
differs from the DBD which exists on the
Explanation: DSNDB01.DBD01 page set and the DBD rebuilt from
This message marks the end of an OBD comparison for the DB2 catalog. This is information which is not kept
the REPAIR DBD TEST or REPAIR DBD DIAGNOSE in the DB2 catalog. This is an acceptable difference and
utility. This message is displayed only when a does not indicate that the OBD is damaged. The
difference has been detected. If there is no difference, hexadecimal offset from the beginning of the OBD is
this message will not be displayed. The OBID of the ’xxxxxxxx’. The name of the field is ’field-name’.
OBD being compared against the DB2 catalog is ’xxxx’. System action:
The number of errors in this OBD is ’nn’. Informational
and warning messages are not added into the error DBD checking continues normally.
count.
Severity:
System action:
0 (informational)
DBD checking continues normally.
Severity: DSNU917I csect-name - DBDS DIFFER AT OFFSET
X’xxxxxxxx’ field-name - INFORMATION
0 (informational) NOT IN DB2 CATALOG
Explanation:
DSNU914I csect-name - DBD X’xxxx’ COMPARISON
COMPLETE -- nn ERRORS WERE This message indicates that the value of a field in the
FOUND DBD differs from the DBD which exists on the
DSNDB01.DBD01 page set and the DBD rebuilt from
Explanation: the DB2 Catalog. This is information which is not kept
This message marks the end of a DBD comparison for in the DB2 catalog. This is an acceptable difference and
the REPAIR DBD TEST or REPAIR DBD DIAGNOSE does not indicate that the DBD is damaged. The
utility. The DBID of the DBD being compared against hexadecimal offset from the beginning of the DBD is
the DB2 catalog is ’xxxx’. The total number of errors ’xxxxxxxx’. The name of the field is ’field-name’.
found in this DBD is ’nn’. System action:
System action: DBD checking continues normally.
DBD checking completed. Severity:
Severity: 0 (informational)
0 (informational)
560 Messages
DSNU919I • DSNU925I
4 (warning) Severity:
4 (warning)
DSNU926I csect-name-OBDDFILE AT OFFSET
X’xxxxxxxx’ IN REBUILT DBD HAS
DSNU929I csect-name-OBD FIELD field-name HAS
OBID X’nnnn’ WHICH IS NOT A FILE
VALUE OUT OF RANGE AT OFFSET
OBD
X’xxxxxxxx’ IN OBD X’nnnn’
Explanation:
Explanation:
The field that points to the first FILE OBD (OBDDFILE)
The object descriptor (OBD) field ’field-name’ has an
in the database descriptor (DBD) that was rebuilt from
unexpected value. The DB2 catalog and database
the DB2 catalog does not point to a FILE OBD. The
descriptor (DBD)/OBD are inconsistent.
DB2 catalog and DBD/OBD (object descriptor) are
inconsistent. field-name
The name of the field in the OBD.
xxxxxxxx
The hex offset from the beginning of the xxxxxxxx
rebuilt DBD. The hex offset from the beginning of the OBD.
nnnn The object identifier (OBID) of the OBD that nnnn The object identifier (OBID) of the OBD.
should be a FILE OBD.
System action:
System action:
Checking of the DBD continues normally.
Checking of the DBD continues normally.
Severity:
Severity:
4 (warning)
4 (warning)
DSNU930I csect-name- INDEX index-name (OBD
DSNU927I csect-name-OBD X’xxxx’ IS A HOLE IN X’xxxx’) MUST BE REBUILT
EXISTING DBD
Explanation:
Explanation:
The index ’index-name’ must be either recovered or
The object descriptor (OBD) that exists on the dropped and recreated to ensure that the index is
DSNDB01.DBD01 page set has been logically deleted, consistent with the description in the INDEX FANSET
OBDHOLE = ’1’B. The DB2 catalog and database OBD. The object descriptor (OBD) is not damaged.
descriptor (DBD)/OBD are inconsistent. The object However, if the index is not either recovered or
identifier (OBID) of the OBD that is a hole is ’xxxx’. dropped and recreated, incorrect output can be
produced when the index is used as an access path.
System action:
index-name
Checking of the DBD continues normally.
The name of the index found in
Severity: SYSIBM.SYSINDEXES.
562 Messages
DSNU931I • DSNU971I
Explanation: Explanation:
This message is issued when the REPAIR utility with This message is sent to the console when TABLESPACE
the DBD option is run on a database that is in use by tsname is set to CHECK pending or auxiliary CHECK
others. pending state. The CORRELATION-ID id1 is the
correlation identifier of the thread requesting CHECK and CHECKRID columns of SYSTABLES and
pending or auxiliary CHECK pending status. SYSTABLEPART are set to ’C’ and binary zeros.)
Correlation IDs beginning with ’0nn’, where nn is a v If the table space is set to not check pending and the
number from 01 to 28, identify system agents. The catalog fields are in error, the scope of check pending
CONNECTION-ID id2 is the correlation identifier of the is set off in the catalog. (The STATUS column of
thread. The LUW-ID id3 is the logical-unit-of-work SYSTABLESPACE is set to an ’A’, and the
identifier of the thread. If the LUW-ID is an ’*’, the CHECKFLAG and CHECKRID columns of
thread has no LUW-ID. If it is not an ’*’, the value is a SYSTABLES and SYSTABLEPART are set to blanks.)
logical-unit-of-work-id that is assigned to the thread
followed by an ’=’ sign and a token value, which can After the catalog fields are corrected, the setting or
be used in place of logical-unit-of-work-id in any DB2 resetting of check pending continues as specified.
command that accepts logical-unit-of-work-id as input.
System action: Usually message DSNT500I or DSNT501I is also issued,
because the probable cause of the error is RESOURCE
Processing continues. UNAVAILABLE. If the reason for the failure was not
User response: RESOURCE UNAVAILABLE, an SVC dump is
requested and processing continues normally. To
Refer to Part 2 of the Administration Guide for a determine the cause of the failure, refer to the dump
discussion of the CHECK pending operation. listing.
Severity:
Collect the following diagnostic items:
4 (warning)
v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
DSNU972I csect-name CATALOG UPDATING period of time spanning the failure.
FAILURE WHILE SETTING OR v Listing of SYS1.LOGREC data set, obtained by
RESETTING CHECK PENDING executing IFCEREP1.
CORRELATION-ID id1
v SYSPRINT output, including JCL, for the application
CONNECTION-ID id2 LUW ID=luw-id
program or batch job, and system messages that
Explanation: were issued. Make sure that MSGLEVEL=(1,1) on the
JOB statement so that all diagnostic information is
When the check pending state is set on or off, the
sent to SYSPRINT.
updating of the catalog tables (SYSTABLESPACE,
SYSTABLES, and SYSTABLEPART) fails. The Severity:
CORRELATION-ID, id1, is the correlation identifier of
0 (informational) or 4 (warning)
the thread associated with the application requesting
that the check pending state be set on or off. The
CONNECTION-ID, id2, is the correlation identifier of DSNU973I csect-name CHECK PENDING, AUX
the application. Correlation IDs beginning with ’0nn’, CHECK PENDING OR BOTH HAS
where ’nn’ is a number from 01 to 28, identify system BEEN RESET FOR TABLESPACE
agents. dbname.tsname CORRELATION-ID id1
CONNECTION-ID id2 LUW-ID id3
System action:
Explanation:
Processing continues.
This message is sent to the console when CHECK
Problem determination:
pending, auxiliary CHECK pending or both states were
The utility being processed requested the setting of reset for TABLESPACE tsname. The CORRELATION-ID
check pending either on or off. The updating of the id1 is the correlation identifier of the thread requesting
STATUS column of SYSTABLESPACE, and of the that the CHECK pending state, the auxiliary CHECK
CHECKFLAG and CHECKRID columns of SYSTABLES pending state or both states be reset. Correlation IDs
and SYSTABLEPART failed. Processing continues beginning with ’0nn’, where nn is a number from 01 to
normally. However, those columns for the rows being 28, identify system agents. The CONNECTION-ID id2
updated now contain invalid values. Subsequent utility is the correlation identifier of the thread. The LUW-ID
processing ignores these values, and the next setting or id3 is the logical-unit-of-work identifier of the thread. If
resetting of check pending for that table space corrects the LUW-ID is an ’*’, the thread has no LUW-ID. If it is
the error in one of the following ways: not an ’*’, the value is a logical-unit-of-work-id that is
v If the table space is set to check pending and the assigned to the thread followed by an ’=’ sign and a
catalog fields are in error, the scope of check pending token value, which can be used in place of the
is escalated in the catalog. (The STATUS column of logical-unit-of-work-id in any DB2 command that
SYSTABLESPACE is set to ’P’, and the CHECKFLAG accepts a logical-unit-of-work-id as input.
564 Messages
DSNU993I • DSNU999I
System action:
DSNU996I csect-name VSAM OPEN ERROR,
Processing continues. ACBERRFLG = error-code
Refer to Part 2 of the Administration Guide for a VSAM OPEN failed with the indicated ACB error-code.
discussion about clearing the CHECK pending status.
System action:
Severity:
Processing terminates if the error code is greater than
0 (informational) or equal to 128; otherwise, processing continues
normally.
DSNU993I csect-name IMAGE COPY RESTORE System programmer response:
TERMINATED
Follow standard VSAM diagnostic procedure. Refer to
Explanation: z/OS DFSMS: Macro Instructions for Data Sets. See also
MVS/DFP V3R3 Diagnosis Guide for more information
Catalog and directory initialization (image copy restore) about the VSAM procedures.
did not complete successfully.
User response:
System action:
Notify the system programmer.
Processing terminates.
Severity:
User response:
8 (error) if error is greater than or equal to 128;
Examine other error messages associated with this job. otherwise, 4 (warning)
Severity:
8 (error) DSNU997I csect-name OUTPUT DATA SET NAME =
data-set-name
User response:
Notify system programmer.
Severity:
8 (error)
Severity: Explanation:
Correcting the clause in error will eliminate this Duplicate LISTDEF or TEMPLATE statements
message in the future. (duplicate names) were detected in the SYSIN, listdef,
or template dataset.
Severity:
System action:
4 (warning)
Utility processing is not initiated.
User response:
566 Messages
DSNU1005I • DSNU1010I
Severity:
DSNU1010I csect-name - LISTDEF name EXPANDS
8 (error) TO THE FOLLOWING OBJECTS:
Explanation:
DSNU1007I csect-name - DATE/TIME VALUES MAY
CHANGE BEFORE EXECUTION This message is followed by an equivalent LISTDEF
control statement with all pattern matching characters
Explanation: removed and all INCLUDE and EXCLUDE clauses
evaluated. For static applications, this expanded
PREVIEW processing has detected DSN date/time
LISTDEF may be saved to a dataset and reused to
variables on a TEMPLATE control statement being
avoid list expansion overhead.
used. These values may change before the actual utility
execution, resulting in different data set names. System action:
Utility processing is not initiated. A utility has attempted to build a data set name based
on a TEMPLATE that specifies DSN variables. The
User response: variable shown has no value in this particular use. For
example, PART when the object is not partitioned or
568 Messages
DSNU1017I • DSNU1022I
Severity: Explanation:
Severity: Explanation:
570 Messages
DSNU1028I • DSNU1032I
is QUIESCE and a single quiesce point is required for ITEMERROR control statement. By default execution
the entire list, the entire list must be resubmitted. will HALT.
Severity: User response:
8 (error) Correct the TEMPLATE DSN expression and resubmit
the utility job. Refer to Installation Guide for the correct
option specifications.
DSNU1028I csect-name - INVALID KEYWORD
kkkkkkkk FOR DASD TEMPLATE Severity:
Explanation: 8 (error)
A DASD TEMPLATE control statement cannot include
the tape TEMPLATE keyword kkkkkkkk. DSNU1031I csect-name - DSN name TOO LONG
System action: Explanation:
Utility processing does not initiate. The TEMPLATE DSN operand results in a data set
name ’name’ that is too long for the type of data set
User response:
being allocated.
DB2 uses the UNIT operand to determine the data set
System action:
type. Either remove the tape keyword from the
TEMPLATE control statement, or correct the UNIT Utility processing for the current object halts. If a list is
operand to refer to a tape unit. Refer to Installation being processed, utility processing of the next object
Guide for the correct option specifications. will proceed or halt based on the OPTIONS
ITEMERROR control statement. By default execution
Severity:
will HALT.
8 (error)
User response:
Correct the TEMPLATE DSN operand in error, and
DSNU1029I csect-name - INVALID KEYWORD
resubmit the utility job. Refer to Installation Guide for
kkkkkkkk FOR TAPE TEMPLATE
the correct option specifications.
Explanation:
Severity:
A tape TEMPLATE control statement cannot include
8 (error)
the DASD TEMPLATE keyword kkkkkkkk.
System action:
DSNU1032I csect-name - INVALID QUALIFIER
Utility processing does not initiate. qualifier IN TEMPLATE name
DB2 uses the UNIT operand to determine the data set The TEMPLATE DSN qualifier either contains invalid
type. Either remove the DASD keyword from the characters or does not start with an alpha character.
TEMPLATE control statement, or correct the UNIT
System action:
operand to refer to a DASD unit. Refer to Installation
Guide for the correct option specifications. Utility processing for the current object halts. If a list is
being processed, utility processing of the next object
Severity:
will proceed or halt based on the OPTIONS
8 (error) ITEMERROR control statement. By default, execution
will HALT.
DSNU1030I csect-name - QUALIFIER qqqqqqqq TOO User response:
LONG
Correct the TEMPLATE DSN operand in error, and
Explanation: resubmit the utility job. Common causes of this error
message are:
The TEMPLATE DSN qualifier ’qqqqqqqq’ is greater than
eight characters. v Omission of the trailing period from a TEMPLATE
DSN variable name. All TEMPLATE DSN variable
System action: names are of the form &xyz. and must contain the
trailing period.
Utility processing for the current object halts. If a list is
being processed, utility processing of the next object v Invalid use of a partitioned data set.
will proceed or halt based on the OPTIONS Refer to Utility Guide and Reference for a description of
the particular utility options.
572 Messages
DSNU1038I • DSNU1043I
If PREVIEW processing must be turned off in the Refer to the DB2 abend code x’00E400C3’ for more
middle of a utility job step, remove the PREVIEW JCL information.
parameter. Activate or deactivate PREVIEW processing
by using the OPTIONS utility control statement, not the
DSNU1041I csect-name - UNABLE TO CREATE GDG
PREVIEW JCL parameter.
BASE name reason
Severity:
Explanation:
0 (informational)
A TEMPLATE could not allocate a generation data
group (GDG) data set, but the base GDG did not exist.
DSNU1038I csect-name - DATASET ALLOCATED. The utility was unable to define the GDG base.
TEMPLATE=template-name
System action:
DDNAME=dd-name FILE
SEQUENCE=file-sequence DSN=ds-name Utility processing halts for the current object. If a list is
in process, utility processing of the next object will
Explanation:
proceed or halt based on the OPTIONS ITEMERROR
| The dataset that was indicated in the message has been control statement. By default, execution will HALT.
| successfully allocated based on a TEMPLATE control
User response:
| statement. file-sequence will only be shown for tape
| datasets. Review the reason value to determine why the GDG
base could not be defined. The possible reasons and
System action:
suggested responses include:
Processing continues. v UNABLE TO LOAD IDCAMS PROGRAM. Ensure
| User response: that the utility can invoke the IDCAMS program.
Ensure that the utility can invoke the IDCAMS
| Refer to Part 4 of Administration Guide for more program.
| information. v IDCAMS ABEND xxx. Use xxx, the abend code from
Severity: the IDCAMS program, to determine why the
IDCAMS program abended.
0 (informational)
v ERROR IN IDCAMS. Review the IDCAMS message
output that is listed between messages DSNU1042I
DSNU1039I csect-name - PROCESSING LIST ITEM: and DSNU1043I to determine why the GDG base
object-type qualifier.name PARTITION could not be defined.
partnum
Severity:
Explanation:
8 (error)
While processing a LISTDEF list, utility processing has
begun on the indicated object.
DSNU1042I csect-name - START OF IDCAMS
System action: MESSAGES
Utility processing continues. Explanation:
Severity: This message indicates the beginning of the IDCAMS
messages or other related non-DB2 messages.
0 (informational)
DSNU1043I indicates the end.
User response:
DSNU1040I csect-name - UNABLE TO LOCATE DSN
dsname ON RESTART No action is required, but subsequent IDCAMS
messages may require some action. See the z/OS MVS
Explanation:
System Messages Volumes 1-10 or other appropriate
DB2 could not find data set dsname when the utility documentation for more information.
was restarted. The data set is required for restart to
continue.
DSNU1043I csect-name - END OF IDCAMS
System action: MESSAGES
The utility step abends. The utility job step is in the Explanation:
stopped state.
This message indicates the end of the IDCAMS or other
User response: related non-DB2 messages. DSNU1042I indicates the
beginning.
User response:
| DSNU1046I csect-name - SWITCH-TO-TEMPLATE
No action is required, but preceding messages may | template-name NOT FOUND
require some action. See the z/OS MVS System Messages
| Explanation:
Volumes 1-10 for more information.
| The LIMIT option of a TEMPLATE utility control
| statement refers to a switch-to-template name that was
DSNU1044I csect-name - PROCESSING ddname AS
| not found in SYSIN or SYSTEMP data set.
EBCDIC
| System action:
Explanation:
| Utility processing continues with original template.
The utility control statement input data set begins with
an EBCDIC character and is assumed for the duration | User response:
of this job step to contain only EBCDIC characters.
| Provide the missing TEMPLATE definition in SYSIN
System action: | prior to its use and resubmit the utility job. If the
| TEMPLATE definition exists in another dataset, provide
Processing of EBCDIC utility control statements
| the SYSTEMPL DD card for the dataset. Refer to
continues.
| Installation Guide for the correct option specifications.
User response:
| Severity:
If processing of utility control statements as EBCDIC is
| 4 (warning)
incorrect make sure the first character in the input data
set is UNICODE, specifically UTF-8 CCSID 1208. This
will cause the entire input data set to be processed as DSNU1047I csect-name - PROCESSING SKIPPED
UNICODE. FOR object-type object-name REASON
CODE=code
Severity:
Explanation:
0 (informational)
The utility has skipped processing of the indicated
object. The reason code shown indicates why
DSNU1045I csect-name - PROCESSING ddname AS
processing was skipped.
UNICODE
1 - CLONE was specified and this object has no
Explanation:
CLONE.
The utility control statement input data set begins with
2 - This object was created with DEFINE NO and this
a UNICODE character, specifically UTF-8 CCSID 1208,
utility does not process DEFINE NO objects.
and is assumed for the duration of this job step to
contain only UNICODE characters. System action:
System action: Processing continues for the remaining objects.
Processing of UNICODE utility control statements Severity:
continues.
0 (informational)
| Attention: UTF-8 quoted strings may not print correctly
| in utility error messages. All messages are printed in
DSNU1048I csect-name - PROCESSING SKIPPED
| EBCDIC, and the quoted strings remain in UTF-8,
FOR n OF m OBJECTS
| causing the output to display poorly in EBCDIC.
Explanation:
User response:
This message summarizes DSNU1047I messages issued
If processing of utility control statements as UNICODE
earlier during the execution of this utility control
is incorrect make sure the first character in the input
statement. It indicates how many objects were skipped
data set is EBCDIC. This will cause the entire input
for the list being processed.
data set to be processed as EBCDIC.
System action:
Severity:
Processing continues for the remaining objects.
0 (informational)
Severity:
0 (informational)
574 Messages
DSNU1050I • DSNU1101I
System action:
DSNU1100I csect-name RECORD ’n’ FOR
Utility processing is terminated. PARTITION m WILL BE DISCARDED
DUE TO field-name CONVERSION
User response:
ERROR FOR table-name ERROR CODE
Correct the TEMPLATE control statement which is in cc
error. Common causes of this error are incorrect syntax
Explanation:
of the (s,l) clause and values of ″s″ or ″l″ which fall
outside of the variable value at the time of execution. The load utility found the input data provided for a
field to be incorrect. The corresponding input data set
Severity:
record ’n’ from the input data set specified for partition
8 (error) m will be placed in the DISCARDS data set.
The error code, cc, identifies the problem. See
| DSNU1051I csect-name TEMPLATE SUBSYS IS NOT DSNU334I for the list of error codes and their meaning.
| SUPPORTED TO ALLOCATE FILE FOR
System action:
| util-name UTILITY
The input data set record is noted and will be
| Explanation:
discarded in the DISCARD phase. The LOAD utility
| Dynamically allocating a BatchPipes® file is not continues to process additional records in the input
| supported for util-name UTILITY. data set.
| User response: User response:
| Remove TEMPLATE keyword, SUBSYS, and resubmit Following the completion of the current LOAD utility
| the job. invocation, examine the record in the DISCARDS data
set for partition m. Correct the error in the discarded
| Severity: input data. Submit a RESUME(YES) LOAD invocation
| 8 (error) with the DISCARDS data set as the input data set.
Refer to Utility Guide and Reference for a definition of
LOAD input field column specifications.
| DSNU1052I csect-name util-name UTILITY DOES
| NOT SUPPORT RESTART WHEN Severity:
| TEMPLATE SUBSYS IS USED
4 (warning)
| Explanation:
| The utility that uses the BatchPipes file cannot be DSNU1101I csect-name RECORD ’n’ FOR
| restarted. PARTITION m WILL BE DISCARDED
DUE TO INVALID field-name COLUMN
| User response: SPECIFICATION
| Use the DB2 command TERM UTILITY to terminate Explanation:
| the stopped utility, and then rerun the job.
The load utility calculated the location of an input data
| Severity: value using the field specifications supplied and
| 8 (error) VARCHAR length fields present within the input data
set record. The calculated position for the field was
determined to be incorrect.
| DSNU1053I csect-name KEYWORD k1 INVALID
| WITH KEYWORD k2 ON utility-name System action:
| Explanation: The input data set record number is noted and will be
discarded in the DISCARD phase. The LOAD utility
| The use of KEYWORD k1 is not allowed due to a continues to process additional records in the input
| conflicting keyword k2 on another utility control data set.
System programmer response: The input data set record is noted and will be
discarded in the DISCARD phase. The LOAD utility
Verify that the validation routine is correct. continues to process additional records in the input
data set.
User response:
User response:
Following the completion of the current LOAD utility
invocation, examine the record in the DISCARDS data Following the completion of the current LOAD utility
set for partition m. Correct the error in the discarded invocation, examine the record in the DISCARDS data
input data, if one exists. Ensure that the exit routine set for partition m. Correct the error in the discarded
provided is correct. Submit a RESUME(YES) LOAD input data, if one exists. Submit a RESUME(YES)
invocation, which uses the DISCARDS data set and the LOAD invocation with the DISCARDS data set as the
verified LOAD utility statement and field specifications. input data set. Refer to Utility Guide and Reference for a
Refer to Utility Guide and Reference for a definition of definition of LOAD input field column specifications. If
LOAD input field column specifications. FORMAT UNLOAD was specified on the load
statement, the WHEN specifications are built internally.
Severity:
This ensures that the rows are loaded back into the
4 (warning) same object from which they were unloaded. Refer to
Utility Guide and Reference for a description of the
FORMAT UNLOAD option of LOAD.
DSNU1103I csect-name RECORD ’n’ FOR
PARTITION m WILL BE DISCARDED Severity:
DUE TO PART OR HIGH KEY
4 (warning)
VALUESPECIFICATION(S)
Explanation:
The discarded record does not belong to the partition m
being loaded. For a LARGE table space, this might be
because the key is higher than the high key value
specified for the last partition.
576 Messages
DSNU1105I • DSNU1108I
System programmer response: The input data set record indicated was loaded into
table ’table-name’, partition m, at RID ’duprid’, but it
Refer to Command Reference for information about the causes a unique index violation for index ’index-name’.
TERM UTIL command.If you suspect an error in DB2, It duplicates the key value of a record already in the
refer to Part 2 of Utility Guide and Reference for table at RID ’rrrr’.
information on identifying and reporting the problem.
System action:
User response:
Processing continues. No index entry is created for the
If a DSNT500I message was issued, refer to the record at RID ’duprid’. The record will be deleted in a
description under that message number. If the subsequent phase of processing.
unavailable resource becomes available, the utility step
is restartable. Severity:
System action:
DSNU1109I csect-name RECORD ’n’ FOR
PARTITION m WILL BE DISCARDED Processing continues.
DUE TO CHECK CONSTRAINT
constraint-name VIOLATION ON TABLE User response:
table-name None required. The constraint violation described will
Explanation: be rectified later in processing.
After the LOAD utility completes, examine the record Input data set records were rejected by the LOAD
in the DISCARDS data set for partition m. Correct the utility for one or several reasons. The rejected records
error in the discarded input data. Submit a have been placed in a discards data set. The number of
RESUME(YES) LOAD job with the DISCARDS data set records rejected for partition m is ’nnn’. Message
as the input data set. DSNU399I summarizes the errors causing the records
to be rejected.
Severity:
System action:
4 (warning)
Processing continues.
578 Messages
DSNU1114I • DSNU1115I
| System action:
DSNU1116I csect-name FOREIGN KEY HAS NO
PRIMARY KEY FOR | Utility operation is terminated with return code 8.
RELATIONSHIP=r1 INPUT RECORD
NUMBER=nnnn | User response:
Processing continues.
DSNU1121I csect-name (RE)LOAD PHASE
User response: STATISTICS - NUMBER OF RECORDS
LOADED = nnnn FOR TABLE table-name
None required.
PART m
Severity:
Explanation:
4 (warning)
When the SHRLEVEL CHANGE option is selected, DB2
issues this message upon normal completion of the
DSNU1117I csect-name - UNIQUE INDEX KEY (RE)LOAD phase of the LOAD utility. It indicates the
DUPLICATES KEY OF INDEXED number of records that were loaded into part m of table
RECORD AT RID rrrr INDEX = table-name from the source record data set. The message
index-name TABLE = table-name RECNO = repeats for each INTO TABLE PART clause in the
input-dataset-record-number LOAD utility statement.
Explanation: System action:
The input data set record was loaded into table Processing continues.
table-name at RID duprid, but it causes a unique index
User response:
violation for index index-name. It duplicates the key
value of a record already in the table at RID rrrr. Verify that the number of records loaded reported is
consistent with expectations.
System action:
Severity:
Processing continues. No index entry is created for the
record at RID duprid. 0 (informational)
Severity:
DSNU1122I csect-name JOB job-name PERFORMING
4 (warning)
util-type WITH UTILID util-id UNABLE
TO DRAIN object-name. RETRY n OF m
DSNU1118I csect-name (RE)LOAD PHASE WILL BE ATTEMPTED IN s SECONDS
STATISTICS - nnnn DUPLICATE KEY
Explanation:
ERRORS ENCOUNTERED
A utility with the RETRY option specified has been
Explanation:
unable to drain a table space, table space part, or index.
This message is issued by the (RE)LOAD phase of the The utility will make another attempt to acquire the
LOAD utility when the SHRLEVEL CHANGE option is drain after a delay.
used. The number of duplicate key errors that were
System action:
encountered during processing is nnnn.
The utility job continues.
System action:
User response:
Processing continues.
The utility job attempts to acquire a restrictive access to
Severity:
the referenced object, and will retry if unsuccessful.
0 (informational) Optionally, the user can determine who has claims on
the object using the -DIS DATABASE command with
CLAIMERS option, and cancel or end those threads.
| DSNU1120I lob-or-xml TABLE NOT DEFINED
Severity:
| Explanation:
0 (informational)
| The LOB or XML table space dbname.tsname has been
| created, but no auxiliary table has been created in it.
580 Messages
DSNU1124I • DSNU1129I
physical partitions 1 and 2 might represent logical loaded correctly; there was not enough data to fill out
partitions 2 and 4. all of the columns. This error can occur when
DSN1COPY is used to copy one table to another table
System action:
that was not defined correctly. To correct this error:
The REORG terminates with return code 8. 1. Define a new table with the same column
User response: definitions as the original table.
2. Use ALTER TABLE ADD COLUMN to add any
Use the DISPLAY DATABASE command to identify a additional columns to the new table.
range of physical partition numbers that represent a
contiguous set of logical partitions, and resubmit the 3. Run the REORG utility on the table space
REORG REBALANCE while specifying that physical containing the new table so the data matches the
partition range. Alternatively, omit the partition range column definitions.
on the REORG REBALANCE so that the entire table 4. Run DSN1COPY to populate the new table.
space is reorganized.
If the previously listed steps do not correct the error,
Severity:
collect the following diagnostic items:
8 (error)
Severity:
8 (error)
DSNU1130I csect-name - NOT ALL PARTITIONS
POPULATED BY REBALANCE -
PROCESSING TERMINATES | DSNU1132I csect-name COPYDICTIONARY
| OPERAND CANNOT BE A
Explanation:
| PARTITION THAT IS BEING
The table space that is being reorganized has many | REPLACED
rows with duplicate partitioning key values, and there
| Explanation:
were insufficient unique values to allow distributing
rows across all partitions during a rebalance. | LOAD COPYDICTIONARY was specified on a
| partition that was also being replaced.
System action:
| COPYDICTIONARY is not supported for this case.
The utility is terminated with return code 8. For
| System action:
REORG SHRLEVEL NONE, the table space is left in the
recover pending restricted state. | Utility operation is terminated with return code 8.
User response: | User response:
If the REORG was REORG SHRLEVEL NONE, recover | Correct the LOAD statement in one of the following
the table space to the point in time before the REORG. | ways:
Severity: | v Specify a different partition number on the INTO
| TABLE PART clause.
8 (error)
| v Specify a different partition number on the
| COPYDICTIONARY option.
DSNU1131I csect-name NOT ENOUGH DATA FOR
| Severity:
REMAINING COLUMNS STARTING
WITH COLUMN colno IN | 8(error)
creator.tablename
Explanation: DSNU1141I csect-name INVALID DELIMITER
CHARACTER x
The REORG utility has discovered that there is not
enough data to fill out the remaining column or Explanation:
columns in a row.
The delimiter character x, which was specified as the
System action: operand of a COLDEL, CHARDEL, or DECPT
keyword, is not a valid delimiter.
The REORG utility is abended with RC00E40349. An
SDUMP might be taken. System action:
User response: Utility processing is not initiated.
Notify the system programmer. User response:
Problem determination: Review the rules for valid delimiters as stated in the
Utility Guide and Reference. Correct the keyword and
The probable cause is that the table was not originally
resubmit the job.
582 Messages
DSNU1142I • DSNU1148I
The message is issued from the LOAD utility when v They were being loaded into a specific partition with
LOAD partition parallelism is being used and the INTO TABLE PART but their partitioning key did
loading of partition n has been completed. The message not match that partition
indicates the total number of records that were v There was an error processing the record
processed from the input file for the partition. The
message is issued for each partition being loaded. The message is not issued if nnnn is zero, or if the job
System action: was restarted from the last commit point.
The user can verify that the number of records matches User response:
expectations. The user can verify that the number of records matches
Severity: expectations. For example, when loading into a single
partition, if this message appears it might be an
0 indication that some rows in the input file belong in
other partitions, and should have been loaded into
DSNU1149I csect - (RE)LOAD PHASE STATISTICS - those partitions.
NUMBER OF INPUT RECORDS NOT Severity:
LOADED=nnnn FOR PART n
0
Explanation:
The message is issued from the LOAD utility when | DSNU1151I csect-name REORGLOB PHASE
LOAD partition parallelism is being used and the | COMPLETE - NUMBER OF RECORDS
loading of partition n has been completed. It indicates | PROCESSED = nnnnnnnn
the total number of records from the input file for
partition n that were not loaded. The records might not | Explanation:
have been loaded because they were excluded by a | This message is issued at the normal completion of the
WHEN clause, because their partitioning key did not | REORGLOB phase of the REORG utility. It indicates the
match partition n, or because there was an error | number of records processed by the utility.
processing the record.
| User response:
The message is not issued if nnnn is zero, or if the job
was restarted from the last commit point. | Verify the number of records loaded into the LOB table
| space.
System action:
| Severity:
The utility continues.
| 0 (informational)
User response:
The user can verify that the number of records matches | DSNU1152I csect-name utility SHRLEVEL option OF
expectations. For example, if this message appears it | obj-type obj-qual.obj-name IS NOT
might be an indication that some rows in the input file | ALLOWED BECAUSE IT HAS A
belong in other partitions, and should have been | LOGGING ATTRIBUTE OF NOT
loaded into those partitions. | LOGGED
Severity: | Explanation:
0 | The SHRLEVEL option was specified incorrectly for a
| utility. One of the following situations occurred:
DSNU1150I csect - (RE)LOAD PHASE STATISTICS - | v option is CHANGE and utility is REORG
NUMBER OF INPUT RECORDS NOT | TABLESPACE: SHRLEVEL CHANGE was specified
LOADED=nnnn | when REORG TABLESPACE was run on a NOT
Explanation:
| LOGGED table space.
| v option is CHANGE and utility is REBUILD INDEX or
The message is issued at the normal completion of the | REORG INDEX: SHRLEVEL CHANGE was specified
RELOAD phase of the LOAD utility. It indicates the | when REBUILD INDEX or REORG INDEX was run
total number of records from the input file or files that | on an index that is defined on a NOT LOGGED table
were not loaded. The records might not have been | space.
loaded for one of the following reasons:
| v option is REFERENCE and utility is REORG
v They were excluded by a WHEN clause | TABLESPACE: SHRLEVEL REFERENCE was
584 Messages
DSNU1153I • DSNU1162I
| System action:
| DSNU1160I csect-name - PARTITIONS WILL BE
| If the REORG, REBUILD INDEX, or REORG INDEX | UNLOADED/RELOADED IN
| was operating on a list of objects and OPTIONS | PARALLEL, NUMBER OF TASKS=n
| EVENT(ITEMERROR,SKIP) was specified, then
| processing continues to the next object in the list.
| Explanation:
| Otherwise, processing terminates. | The REORG TABLESPACE utility is able to unload and
| Operator response: | reload partitions in parallel. The number of tasks
| started is n.
| Remove the SHRLEVEL (CHANGE) or SHRLEVEL(
| REFERENCE) option from the utility statement. | System action:
| 8 (error) | Severity:
| 0 (informational)
| DSNU1153I csect-name LOG YES SPECIFIED FOR
| THE NOT LOGGED obj-type | DSNU1161I csect-name - NON-PARTITIONED
| objqual.obj-name WILL BE IGNORED | INDEXES WILL BE UNLOADED IN
| Explanation: | PARALLEL, NUMBER OF TASKS=n
| DSNU1170I csect-name UNABLE TO EXTEND | index was built. The record was not loaded.
| PARTITION-BY-GROWTH | System action:
| TABLESPACE dbname.tsname BECAUSE
| OF reason | Processing terminates. An abend is requested so that
| the LOAD can be restarted after the error condition is
| Explanation: | corrected.
| One of the following errors occurred: | User response:
| PARTITION RANGE | Find the failing record in the input data set, correct the
| The space that exists in the current range of | condition that caused the key evaluation error, and
| the partition is not big enough to hold all the | restart the LOAD utility. You can optionally include a
| data. | SYSDISC DD statement in the JCL input to hold copies
| LOB COLUMNS
| of records that are not loaded.
| Rows with LOB columns changed partitions | Severity:
| during REORG. This is not allowed. A change
| has been made to the attributes of the table | 8 (error)
| space so that a row with LOB columns cannot
| be reloaded to the partition to which it DSNU1175I csect-name INPUT FIELD(S) - CONTAIN
| belongs. ONE OR MORE INSTANCES WHICH
| MAXPARTITIONS LIMIT WHEN CONVERTED TO DECFLOAT
| The partition was not able to be extended RESULTED IN ONE OF THESE
| because the number of partitions has reached CONDITIONS (OVERFLOW,
| the maximum partitions limit. UNDERFLOW, SUBNORMAL,
INEXACT), AND THE RESULT VALUE
| System action: MAY BE ROUNDED
| Utility processing is discontinued. Explanation:
| User response: The utility for LOAD or UNLOAD converts the input
value, but the converted value is out of the normal
| Correct the space attributes of the partition in order to
range, and it has possibly been rounded.
| fit all the data you need into the partition. Run the
| utility job again. System action:
The utility for LOAD or UNLOAD continues
| DSNU1171I csect-name- KEY EVALUATION ERROR processing.
| OCCURRED DURING PROCESSING
| AT RID rid INDEX = index-name TABLE Severity:
| = table-name RECNO= 4 (warning)
| input-dataset-record-number for-part =
| part-num
DSNU1176I csect-name - FUNCTION function IS NOT
| Explanation: SUPPORTED FOR LOB OR XML
| A key evaluation error occurred when the extended TABLE SPACES
| index was built. The record was not loaded. Explanation:
| System action: The function specified, function, is not supported for
| Processing continues. LOB/XML table spaces.
586 Messages
DSNU1178I • DSNU1188I
Severity:
DSNU1180I csect-name SQLCODE=0, SUCCESSFUL
0 (informational) EXECUTION
Explanation:
DSNU1178I csect-name - SUM OF INPUT COLUMN
The SQLCODE was zero (0), indicating successful
LENGTHS FOR CURSOR cursor-name IS
execution of the function. SQLWARN indicators might
TOO LARGE
note some warnings. SQLWARNx fields are described
Explanation: in Appendix D of SQL Reference.
v Listing of the results produced by the SQL 2 DB2 internal data manager error code
statements.
3 One of the following conditions:
v Source listing of the failing application program.
v Number of rows inserted, updated, or
Severity: deleted following an INSERT, UPDATE, or
DELETE statement. Attention: A ’-1’ in this
8 (error)
field indicates that a mass delete of a table
in a segmented table space was performed,
DSNU1189I csect-name - CURSOR cursor-name wherein DB2 does not access nor count
ALREADY DECLARED individual rows.
588 Messages
DSNU1198I • DSNU1203I
Explanation: 0 (informational)
| DSNU1204I DUPLICATE ROWS MIGHT HAVE DSNU1213I csect-name - INVALID FIELD TYPE FOR
| BEEN UNLOADED FIELD field-name FOR TABLE table-name
| Explanation: Explanation:
| The image copy contains duplicate pages. All rows The specified field type in the field specification list of
| from the duplicate pages are unloaded the UNLOAD utility is incompatible with the base type
of the corresponding column of the table.
| System action:
System action:
| Processing continues.
The utility job terminates.
| Severity:
User response:
| 4 (warning)
Specify only a compatible type allowed for the unload
operation in the field specification list.
DSNU1211I csect-name - INPUT DATA SET IS NOT
AN IMAGE COPY Severity:
Explanation: 8 (error)
The input data set specified by the FROMCOPY or
FROMCOPYDDN option of the UNLOAD utility was DSNU1214I csect-name - INVALID FIELD POSITION
not identified as an image copy data set. SPECIFICATION FOR FIELD field-name,
TABLE table-name
System action:
Explanation:
The utility job terminates.
For a UNLOAD statement, specified field positions are
User response:
not in ascending order in the field specification list of
Specify the correct image copy data set name to the the indicated table.
FROMCOPY option, or to the DD-name that is referred
System action:
to by the FROMCOPYDDN option.
The utility job terminates.
Severity:
User response:
8 (error)
Specify the field positions in the ascending order in the
field specification list. If a certain order of the output
DSNU1212I csect-name - INVALID FIELD NAME
fields is desired, change the order of the field in the list
field-name FOR TABLE table-name
so that the field positions are in the ascending order.
Explanation:
Severity:
The specified field name in the field specification list of
8 (error)
the UNLOAD utility is:
v Not a column name of the specified table, or
DSNU1217I csect-name - CONFLICTING FIELD
v An existing column name for the CONSTANT
POSITION AND/OR LENGTH
option.
SPECIFICATION FOR FIELD field-name,
The field name is not valid. TABLE table-name
The utility job terminates. For a UNLOAD statement, the specified field position
for the indicated field caused a conflict with the
User response: previous field. This is caused either by
For a CONSTANT field, specify a non-existing field v The position value specified for the field is too small.
name. Otherwise, specify the field name as a column v The length specification for the previous field is too
name of the indicated table. large.
Severity: System action:
8 (error) The utility job terminates.
User response:
Specify the correct position or length parameters in the
590 Messages
DSNU1218I • DSNU1221I
field specification list so that there are enough space for This problem will occur when the number of errors in
the output fields. the output record formatting, including data conversion
errors, detected by the UNLOAD utility reached the
Severity:
limit specified by the MAXERR option. For each record
8 (error) in error, the corresponding message has been issued.
The records in error will not be unloaded to the output
data set. This message is issued only once, even though
DSNU1218I csect-name - LOGICAL RECORD there can be a situation in which the number of
LENGTH OF OUTPUT RECORD individual error messages exceeds the specified
EXCEEDED THE LIMIT FOR TABLE MAXERR value. This situation occurs only when the
table-name UNLOAD utility is running in the partition parallel
Explanation: mode and the multiple tasks have reached the
MAXERR value concurrently.
The maximum length of the output records exceeded
the physical limit for the UNLOAD utility. Severity:
Problem determination:
DSNU1225I csect-name - TABLESPACE KEYWORD
When the source objects of the UNLOAD utility consist IS NOT SPECIFIED. AT LEAST ONE
of multiple table spaces, an output data set FROM TABLE SPECIFICATION IS
corresponding to each table space is required. REQUIRED.
Severity: Explanation:
8 (error) There is no TABLESPACE nor FROM TABLE
specification in a UNLOAD statement. The source
object for unloading can not be identified.
DSNU1223I csect-name - TABLESPACE
SPECIFICATION IS MISSING FOR System action:
FROMCOPY OR FROMCOPYDDN
The utility job terminates.
Explanation:
User response:
For the UNLOAD utility, the FROMCOPY or
FROMCOPYDDN option is used but the TEMPLATE If the TABLESPACE specification is omitted, specify at
specification is missing. least one FROM TABLE option to identify the source
object. Instead of a TABLESPACE specification, the
System action: LIST option can be used, if a LISTDEF statement
defines a list of objects. When the LIST option is used,
The utility job terminates.
the FROM TABLE option can not be specified.
User response:
Severity:
Add the TABLESPACE option in the UNLOAD
8 (error)
statement to specify the table space name of the image
copy.
592 Messages
DSNU1226I • DSNU1230I
System action:
DSNU1226I csect-name - THE NUMBER OF
OBJECTS IS TOO LARGE The utility job terminates.
Explanation: User response:
The number of source objects for the UNLOAD utility Use the FROMCOPYDDN, instead of FROMCOPY, to
is too large. Overflow in some of the internal data specify a DD name where the first piece of copy that
structures occurred. contain the page set header page is concatenated to the
source image copy data set.
System action:
Problem determination:
The utility job terminates.
The problem will most likely occur when a piece of
User response:
copy data set, not the first one, is specified to the
Divide the UNLOAD job step into two or more job FROMCOPY option.
steps and, in each job step, use a LISTDEF that expands
Severity:
to less number of objects.
8 (error)
Problem determination:
This problem will most likely occur when the LIST
DSNU1229I csect-name - ERROR IN LOADING
option is used and the corresponding LISTDEF
DICTIONARY FOR TABLE SPACE
definition is expanded to a large number of objects.
table-space
Severity:
Explanation:
8 (error)
For the UNLOAD utility, an error was detected in
loading the dictionary for decompression while reading
DSNU1227I csect-name - THE CONTENT OF THE an image copy data set.
IMAGE COPY DATA SET IS
System action:
INCONSISTENT WITH TABLE SPACE
table-space The utility job terminates.
Explanation: User response:
For the UNLOAD utility, the data set specified by the If the right image copy data set is specified to the
FROMCOPY or the FROMCOPYDDN option is not FROMCOPY or FROMCOPYDDN, it will be required to
corresponding to the table space. take a new image copy for the table space by running
the COPY utility or using other alternative methods.
System action:
Problem determination:
The utility job terminates.
Possibly the image copy data set is corrupted.
User response:
Severity:
Specify a correct image copy data set name for the
table space, or specify the correct table space name for 8 (error)
the image copy.
Severity: DSNU1230I csect-name - INCONSISTENT STRIP
CHAR LENGTH FOR FIELD field-name,
8 (error)
TABLE table-name
Explanation:
DSNU1228I csect-name - A ROWID COLUMN
column-name, TABLE table-name IS An invalid strip character was specified for the
SELECTED FOR UNLOAD BUT THE indicated field of the table.
PAGE SET HEADER PAGE IS
MISSING IN THE SPECIFIED IMAGE System action:
COPY DATA SET The utility job terminates.
Explanation: User response:
For the UNLOAD utility, a ROWID column is selected Specify the correct strip character applicable to the
for unloading from an image copy, but the required field.
information to form the ROWID can not be retrieved
because the page set header page is not included in the Problem determination:
specified image copy data set. For an SBCS or MIXED character field, the strip
character, if specified, must be an SBCS character; for a data set. The UNLOAD utility continues until the total
DBCS field, it must be a DBCS character. number of records in error reaches the value specified
by the MAXERR option (the default is 1). If the total
Severity:
number of records reaches the MAXERR value, the
8 (error) UNLOAD utility issues the DSNU1219I message and
terminates with the return code 8.
System action: This message is issued when a copy of pieces (not the
first piece) of a compressed table space is specified in
The record in error will not be unloaded to the output the FROMCOPY or FROMCOPYDDN option of the
data set. The UNLOAD utility continues until the total UNLOAD utility.
number of records in error reaches the value specified
by the MAXERR option (the default is 1). Severity:
This message is issued only when the NOPAD option is If the total number of records reaches the MAXERR
specified in the UNLOAD statement and most likely value, the UNLOAD utility issues the DSNU1219I
when BLOB, CLOB, or DBCLOB columns are selected message and terminates with the return code 8.
for unload from the table. It is also possible that, if the
User response:
expansion of output strings occurs due to the encoding
scheme specified for the output, the total length of Apply appropriate values to the LENGTH and/or
some output records becomes longer than expected. POSITION parameters in the field specification list to
accommodate the data in the output records.
Severity:
Alternatively, specify TRUNCATE option to the field, if
4 (warning) applicable. Specifying the STRIP option, if applicable,
can also reduce the length of data if the data contains
leading or trailing blanks.
DSNU1232I csect-name - COMPRESSED ROW IS
IGNORED BECAUSE THE Problem determination:
DICTIONARY IS NOT AVAILABLE
This message is issued when the space of a field in an
FOR TABLE table-name
output record is limited by the LENGTH specification
Explanation: for the field or the POSITION specification for the next
field.
The UNLOAD utility encountered a compressed row
when unloading the data from an image copy data set Severity:
but the dictionary for decompression has not been
4 (warning)
loaded for the table space.
System action:
The record in error will not be unloaded to the output
594 Messages
DSNU1234I • DSNU1237I
Severity:
DSNU1234I csect-name - NUMERIC CONVERSION
ERROR OCCURRED FOR FIELD 4 (warning)
field-name, TABLE table-name
Explanation: DSNU1236I csect-name - POSITION SPECIFICATION
CAUSES FIELD OVERLAP FOR FIELD
The UNLOAD utility encountered an error when it
field-name, TABLE table-name
tried to convert a data of one numeric type to another.
Explanation:
System action:
For the UNLOAD utility, the space for an output field
The record in error will not be unloaded to the output
was overlapped by the indicated field to which the
data set. The UNLOAD utility continues until the total
POSITION parameter is specified.
number of records in error reaches the value specified
by the MAXERR option (the default is 1). System action:
If the total number of records reaches the MAXERR The record in error will not be unloaded to the output
value, the UNLOAD utility issues the DSNU1219I data set. The UNLOAD utility continues until the total
message and terminates with the return code 8. number of records in error reaches the value specified
by the MAXERR option (the default is 1). If the total
User response:
number of records reaches the MAXERR value, the
To eliminate any numeric overflow error, specify the UNLOAD utility issues the DSNU1219I message and
same numeric data type for the output as the base type terminates with the return code 8.
of the columns in the table. Convert numeric types only
User response:
when it is known that the range of the source data fits
in the allowable range of the specified numeric type for Consider the following options to eliminate this
the output. situation:
Problem determination: v Remove the POSITION specifications from the field
specification list.
This message is issued most likely when an overflow
v Adjust the POSITION parameter for the field to
occurs in converting a data of one numeric type to
preserve enough space for the previous fields.
another. For example, an attempt to convert an
INTEGER 32768 to a SMALL INT causes an overflow. v Adjust the LENGTH, possibly with the TRUNCATE
option, of the previous fields, if applicable.
Severity:
Problem determination:
4 (warning)
This message will be issued only when the NOPAD
option is specified in the UNLOAD statement. The
DSNU1235I csect-name - CCSID SUBSTITUTION IS POSITION specification for the field caused a conflict
ATTEMPTED WITH NOSUBS OPTION with the positioning and/or the length of a previous
FOR FIELD field-name, TABLE table-name field.
Explanation: Severity:
While the UNLOAD utility is running with the 4 (warning)
NOSUBS option, a CCSID substitution is attempted in
the CCSID conversion process for the indicated field.
DSNU1237I csect-name - ERROR IN CCSID
System action: CONVERSION FOR FIELD field-name,
The record in error will not be unloaded to the output TABLE table-name
data set. The UNLOAD utility continues until the total Explanation:
number of records in error reaches the value specified
by the MAXERR option (the default is 1). If the total The CCSID conversion process detected a code point or
number of records reaches the MAXERR value, the form exception while the UNLOAD utility was
UNLOAD utility issues the DSNU1219I message and running.
terminates with the return code 8. System action:
User response: The record in error will not be unloaded to the output
If it is desired to eliminate any CCSID substitution, data set. The UNLOAD utility continues until the total
specify an appropriate CCSID that has the number of records in error reaches the value specified
corresponding entries to the original CCSID, if by the MAXERR option (the default is 1). If the total
available. To allow the default CCSID substitution, number of records reaches the MAXERR value, the
remove the NOSUBS option. UNLOAD utility issues the DSNU1219I message and
terminates with the return code 8.
System programmer response: | table. Group all WHEN control statements for the same
| table into a single WHEN control statement by using
Verify the contents of SYSSTRINGS. If necessary, insert
| the OR keyword. Resubmit the job.
a row into SYSSTRINGS for the conversion. For an
SBCS translation, the row must contain a translate table | Severity:
or the name of a user-provided translate procedure. For
| 4 (warning)
a DBCS translation, the row must contain the name of a
user-provided translate procedure.
| DSNU1241I csect-name -utility-name UTILITY
User response:
| CANNOT PROCEED BECAUSE TABLE
If the specified CCSID for output is incorrect, correct | table-name IS SPECIFIED IN MORE
the CCSID specification. If a valid CCSID is specified, | THAN ONE FROM TABLE
notify the system programmer. | SPECIFICATION
Severity: | Explanation:
4 (warning) | The table table-name cannot be specified in multiple
| FROM TABLE specifications.
DSNU1238I TABLE table2 IS NOT IN SAME | System action:
TABLESPACE AS TABLE table1
| Utility processing terminates.
Explanation:
| User response:
All source tables for a single UNLOAD utility
| Remove the FROM TABLE specifications for the same
statement must be in the same table space.
| table. Group all WHEN control statements for the same
System action: | table into a single WHEN control statement by using
| the OR keyword. Resubmit the job.
Utility processing terminates.
| Severity:
User response:
| 8 (error)
Remove the FROM TABLE control statement that
specifies table2 from the current UNLOAD request.
Create another UNLOAD utility statement that contains DSNU1250I csect-name - ERROR IN CCSID
the FROM TABLE control statement for table2 so that CONVERSION FOR object-type.
all source tables in a single UNLOAD request are from SOURCE CCSID=ccsid, TARGET
the same table space. Resubmit the job. CCSID=ccsid
Severity: Explanation:
8 (error) The CCSID conversion process failed for object-type. The
values of object-type and the cause of the error for each
type are:
| DSNU1240I csect-name TABLE table-name WAS
| SPECIFIED IN MORE THAN ONE v SBCS PAD CHAR
| FROM TABLE SPECIFICATION, ONLY v DBCS PAD CHAR
| THE FIRST INSTANCE OF FROM v VERIFICATION
| table-name WILL BE PROCESSED
v HEADER CONST
| Explanation: v field-name
| The table table-name was specified in multiple FROM System action:
| TABLE specifications. UNLOAD will only process one
| instance of a table-name per UNLOAD statement. The The utility terminates.
| UNLOAD utility will process the first instance of System programmer response:
| FROM TABLE table- name and discard subsequent
| FROM TABLE specifications containing the same name. Check the SYSSTRINGS catalog table to determine
whether a row exists for the CCSID conversion. If a
| System action: row does not exist, and OS/390 V2R9 is installed, refer
| UNLOAD processing continues. For table table-name, to z/OS C/C++ Programming Guide for additional
| only the first instance of the FROM TABLE table-name conversions that are supported. If no conversions are
| specification will be unloaded and subsequent instances available, contact your IBM service representative to
| will be discarded. request support for the conversion.
| Remove the FROM TABLE specifications for the same If the CCSID that is specified in the utility control
596 Messages
DSNU1251I • DSNU1255I
| Programmer response:
DSNU1304I csect-name n
| Use an image copy data set that contains the header SYSIBM.SYSINDEXPART_HIST ROWS
| page. WERE DELETED
| Severity: Explanation:
Severity: 0 (informational)
0 (informational)
DSNU1306I csect-name n
SYSIBM.SYSLOBSTATS_HIST ROWS
DSNU1302I csect-name n WERE DELETED
SYSIBM.SYSCOLUMNS_HIST ROWS
WERE DELETED Explanation:
Severity: 0 (informational)
0 (informational)
DSNU1307I csect-name n
SYSIBM.SYSTABLEPARTS_HIST
DSNU1303I csect-name n ROWS WERE DELETED
SYSIBM.SYSINDEXES_HIST ROWS
WERE DELETED Explanation:
Severity: 0 (informational)
0 (informational)
598 Messages
DSNU1308I • DSNU1350I
| low2key=
| DSNU1352I csect-name SYSKEYTGTDISTSTATS
| The second lowest value of the key-target
| CATALOG STATISTICS FOR
| index-nameKEYSEQ keyseq-num,
| If the value for the highkey, high2key, low2key, and | keyseq-num, ...PARTITION
| lowkey are null, then the invoker of RUNSTATS is not | part-numCARDINALITY = cardinality
| authorized to read the table. | FREQUENCY KEYVALUE frequency
| X’hex_string’ frequency X’hex_string’ ... ... =
| The message is routed to SYSPRINT. | frequency X’hex_string’
| System action: | Explanation:
| Processing continues. | The RUNSTATS utility issues this message to report the
| User response: | statistics collected for the key column keyseq-num
| partition part-num. If more than one keyseq-num are
| Refer to Utility Guide and Reference for a description of | listed, then the statistics collected and the expression
| RUNSTATS statistics. | values reported represent the concatenation of those
| Severity: | key columns.
| low2key=
| Frequencies for the LEAST frequent values are
| The second lowest value of the key-target
| collected, if the FREQVAL ... LEAST options are
| specified and given a COUNT value greater than zero.
| If the values for high2key and low2key are null, then | Frequencies for the MOST and LEAST frequent values
| the invoker of RUNSTATS is not authorized to read the | are collected, if the FREQVAL ... BOTH options are
| table. | specified and given a COUNT value greater than zero.
| If the default is taken, then the ten most frequently
| The message is routed to SYSPRINT.
| occurring values, plus the lowest and highest values in
| System action: | the partition (if not already included in the ten greatest
| frequencies), are reported in descending order of
| Processing continues. | frequency.
| User response: | If fewer than ten values appear, then there are fewer
| Refer to Utility Guide and Reference for a description of | than ten distinct values in the index.
| RUNSTATS statistics. | If no values appear, then the values are uniformly
| Severity: | distributed.
| 0 (informational) | If frequencies appear but key column values do not,
| then the invoker of RUNSTATS is not authorized to
| read the table. Message DSNU619I is issued to identify
| the table.
| The message is routed to SYSPRINT.
| System action:
| Processing continues.
600 Messages
DSNU1353I • DSNU1355I
602 Messages
DSNU1402I • DSNU1407I
DSNU1402I csect-name - copy-type FOR obj-type DSNU1405I csect-name - site-type SITE PRIMARY
obj-qual.obj-name DSNUM n WITH IMAGE COPY DOES NOT EXIST FOR
START_RBA rba ALREADY EXISTS obj-type obj-qual.obj-name DSNUM n
Explanation: Explanation:
COPYTOCOPY attempted to make an image copy that The COPYTOCOPY utility attempted to make a backup
already exists. image copy for the site, but the primary image copy
does not exist.
System action:
System action:
The utility does not make the image copy for the
specified object type. COPYTOCOPY makes the The utility cannot make the site backup copy. If the
remaining types of image copies. If there is a list of utility job includes an OPTIONS control statement with
objects to be copied, COPYTOCOPY processes the next the EVENT(ITEMERROR,SKIP) option, COPYTOCOPY
object in the list. processes the next item on the list.
User response: User response:
Run the REPORT utility to determine the image copy Modify your COPYTOCOPY job, COPYDDN or
types that you need. Modify your COPYTOCOPY job, RECOVERYDDN option, to include the ddname for the
and rerun it as needed. primary copy.
Severity: Severity:
| 4 (warning) or 8 (error) 8 (error)
604 Messages
DSNU1411I • DSNU1458I
incremental image copy. If this condition occurs, halt problem. The The user may generate a dump by
the utility and resubmit the job step with the adding the DIAGNOSE ABEND statement in the utility
appropriate size. job and re-running the utility. If the error can be fixed,
correct the error and resubmit the utility, else issue the
Severity:
TERM utility command to terminate the utility.
4 (warning)
Severity:
8 (error)
DSNU1411I csect-name - ut_name DOES NOT
SUPPORT RESTART(PHASE). PHASE
CHANGED TO CURRENT. | DSNU1455I csect-name obj-type obj-qual.obj-name NOT
| CLONED
Explanation:
| Explanation:
This utility does not support the RESTART(PHASE).
| You specified an object-name along with the CLONE
System action:
| keyword, but the object is not involved with cloning.
The utility overrides RESTART(PHASE) with | This message will also be issued if you specified an
RESTART(CURRENT). | invalid clone object-name.
| System action: | The object has the NOT LOGGED logging attribute. For
| not logged objects, the recovery point must match a
| The utility job is terminated.
| recoverable point. A recoverable point is established
| User response: | when one of the following circumstances are true:
| Remove the invalid utility control statements, or refer | v When a table space is altered from LOGGED to NOT
| to a base object, and resubmit the job. | LOGGED, which alters all of the index spaces for
| indexes on all of the tables in the table space
| Severity: | v When an image copy is taken against a not logged
| 8 (error) | table space or a not logged index space
| System action:
| DSNU1459I csect-name KEYWORD OR OPERAND | Utility processing halts for this object. The utility job
| oooooo INVALID WITH AN OBJECT | completes with a return code of 8. If the utility job step
| INVOLVED IN CLONING | includes an OPTIONS control statement with the
| qualifier.object-name FOR THE uuuuuu | EVENT(ITEMERROR,SKIP) option, the utility will
| UTILITY | process the next item in the list.
| Explanation: | User response:
| The use of KEYWORD or OPERAND oooooo of the | Resubmit the RECOVER job with TOLASTCOPY or
| uuuuuu utility is invalid when specified for an object | TOLOGPOINT that matches a recoverable point.
| involved in cloning.
| Severity:
| System action:
| 8 (error)
| The utility job is terminated.
| User response: | DSNU1505I csect-name RECOVERY OF THE NOT
| Remove the invalid utility control statements and | LOGGED obj-type obj-qual.obj-name WAS
| resubmit the job. | TO THE LAST RECOVERABLE POINT:
| RBA/LRSN rba/lrsn. THE OBJECT HAS
| Severity: | BEEN CHANGED SINCE THAT POINT
| 8 (error) | Explanation:
| A full recovery was requested, but because the object is
DSNU1502I csect-name - RECOVER OF obj-type | not a logged object, it was recovered to its last
obj-qual.objname dsnum n WILL | recoverable point, which means that any changes made
PROCEED TO LOG POINT X’rba/lrsn’ | to the object after the recoverable point are lost. This
Explanation: | message warns that the object has been modified since
| the last recoverable point.
DB2 issues this message if the RECOVER utility
statement includes the TOLASTCOPY or | A recoverable point is established when one of the
TOLASTFULLCOPY keyword. The message provides | following circumstances is true:
information on the point in time that the object was | v When a table space is altered from LOGGED to NOT
recovered to. In a data sharing environment, the log | LOGGED, which alters all of the index spaces for
point identified is an LRSN. Otherwise, the log point | indexes on all of the tables in the table space
identified is an RBA. | v When an image copy is taken against a not logged
System action: | table space or a not logged index space
606 Messages
DSNU1506I • DSNU1510I
| DSNU1506I csect-name: RECOVER LOGONLY OF | If the utility job step includes an OPTIONS control
| obj-type obj-qual.obj-name IS NOT
| statement with the EVENT(ITEMERROR,SKIP) option,
| ALLOWED BECAUSE THE LOGGING
| the utility will process the next item in the list.
| ATTRIBUTE OF THE OBJECT IS NOT | User response:
| LOGGED
| Check the utility job output for prior messages
| Explanation: | indicating an allocation, open, or read error on the
| The object to be recovered has a NOT LOGGED
| image copy data set identified by the DSNU515I
| logging attribute. This means there are no log records
| message. Correct the situation if possible. If the
| available for the LOGONLY RECOVER job. The object
| problem cannot be corrected, then run the REPORT
| should be recovered to a previous point in time that is
| RECOVERY utility for the object to determine the
| a recoverable point. A recoverable point is:
| options that are available for recovery.
| 8 (error) | Severity:
| 8 (error)
| DSNU1507I csect-name: THE IMAGE COPY FOR
| obj-type obj-qual.obj-name IS NOT | DSNU1510I csect-name - LOG APPLY PHASE
| USABLE. RECOVERY BY FALLBACK | COMPLETE, ELAPSED TIME:
| TO THE PREVIOUS IMAGE COPY IS | HH.MM.SS
| NOT POSSIBLE BECAUSE REQUIRED
| LOG RECORDS WERE NOT WRITTEN | Explanation:
| Explanation: | Severity:
| You cannot recover an object that requires the recovery | 8 (error)
608 Messages
DSNU1520I • DSNU1523I
| DSNU1520I THE RECOVERY BASE FOR obj-type | Review the RECOVER Utility job output and, in
| obj-qual.obj-name dsnum n IS THE
| particular, the DFSMShsm messages in the HSM job log
| SYSTEM-LEVEL BACKUP WITH DATE
| to determine the cause of the failure. If the restore of
| = yyyymmdd, TIME = hhmmss, AND
| the data sets failed due to target volume connectivity
| TOKEN = X byte-string
| problems or hardware failures, the system storage
| administrator should be contacted to resolve the
| Explanation: | problem. Once the problem has been resolved, you may
| run the RECOVER Utility job again.
| This message is issued by the RECOVER Utility in the
| RESTORE phase when a system-level backup has been | If the problem with the system-level backup cannot be
| chosen as the recovery base for the identified object. | resolved, you can consider these recovery options to
| bypass the problem:
| System programmer response:
| v RECOVER with the RESTOREBEFORE option to
| Recovery processing continues. | direct the recovery to find a recovery base prior to
| Severity: | the system-level backup that has the problem. Note
| that more log apply processing will be needed
| 0 (informational) | during the recovery of the object.
| v RECOVER with the FROMDUMP option (or specify
| DSNU1521I csect-name A LOGONLY RECOVERY | YES for the RESTORE/RECOVER FROM DUMP
| CANNOT BE DONE BECAUSE THE | install option on installation panel DSNTIP6) to
| HEADER PAGE CANNOT BE | direct the recovery to use a copy of the system-level
| ACCESSED FOR obj-type | backup that had been dumped to tape.
| obj-qual.obj-name dsnum n | v SYSTEM-LEVEL BACKUPS => NO can be specified
| Explanation: | on install panel DSNTIP6 to avoid choosing
| system-level backups as a recovery base.
| The header page could not be read. DB2 stops the
| RECOVER utility from proceeding with a LOGONLY | Problem determination:
| recovery because the starting point is unavailable. | The DFSMShsm message(s) appearing in the HSM job
| System programmer response: | log will indicate the cause of the failure.
| DSNU1524I obj-type obj-qual.obj-name dsnum n | Issue the DFSMShsm LIST COPYPOOL command with
| CANNOT BE RESTORED FROM THE
| the ALLVOLS option for the DB2 database copy pool.
| SYSTEM LEVEL BACKUP WITH DATE
| Analyze the output from the LIST COPYPOOL
| = yyyymmdd, TIME = hhmmss, AND
| command to see whether the system-level backup
| TOKEN = X ’byte-string’ BECAUSE
| identified by the token is recoverable. If the
| THE SPECIFIED DUMPCLASS
| system-level backup no longer resides on DASD and
| hsm-dumpclass-nm IS NOT KNOWN TO
| has been dumped to tape, then rerun the RECOVER
| DFSMSHSM
| specifying the FROMDUMP option.
| Explanation:
| Severity:
610 Messages
DSNU1528I • DSNU1552I
| system-level backup that was dumped to tape. slb-type | point-in-time with consistency, only when the objects at
| will be FLASHCOPY for the former and DUMP COPY | the recovery point on the specified member have active
| for the latter. | units of recovery. This message identifies the RBA of
| the checkpoint from which the RECOVER utility will
| System action:
| process the log records during the LOGCSR phase for
| Recovery processing continues. | this DB2 member.
| This message is issued at the completion of the | The following list contains the column names and the
| LOGCSR phase by the RECOVER utility for recover to | description of their contents:
| point-in-time with consistency. The LOGCSR phase can
| be skipped if the RECOVER utility determines that no | MEM The name of the DB2 member to which this
| active units of recovery (URs) at the recovery point | UR belongs. In a data sharing environment,
| exist. The counts indicate the number of units of work | this field identifies the DB2 member. In a
| that have execution states that require rollback action to | non-data sharing environment, this field is
| be performed during this recovery process. This is in | blank.
| order to ensure recovery consistency. | T The connection type. The values can be one of
| The INFLIGHT count specifies the number of URs that | the following types:
| neither completed phase one of the commit process nor | v B Batch: a batch program or QMF user.
| began the process of backing out during the recovery | v I Internal: a system service being performed
| point. The RECOVER utility will roll back the changes | on a user’s behalf.
| during the LOGUNDO phase.
| v S Subsystem: work that originated from an
| The INABORT count specifies the number of URs that | attached subsystem, either CICS or IMS/VS.
| were in the process of being backed out during
| CONID
| recovery point. The RECOVER utility will roll back the
| Connection identifier for related URs. Batch
| changes during the LOGUNDO phase.
| connections are not related to any other
| The POSTPONED ABORT count specifies the number | connection. Subsystem connections with the
| of URs that’s backout was postponed in an earlier | same identifier indicate URs that originated
| restart process, and not attended to prior to the | from the same subsystem.
| recovery point. The RECOVER utility will roll back the
| CORRID
| changes during the LOGUNDO phase.
| Correlation identifier. Unique within a
| The INDOUBT count specifies the number of URs that | subsystem connection, it relates a UR to a
| were interrupted between phase one and phase two of | particular CICS or IMS/VS transaction.
| the commit process. The URs are treated as INABORT
| AUTHORIZATION ID
| URs and the RECOVER utility will roll back the
| Authorization identifier of the user for whom
| changes during the LOGUNDO phase.
| this UR was created.
| This message precedes a table showing the status of
| PLAN Name of the plan allocated to the UR.
| URs that were active during the recover to
| point-in-time on the objects being recovered. This table | S UR status. The UR was in one of these
| will only exist if an active UR exists during the | situations during the recovery point:
| recovery point. This table helps to identify the | v A INABORT: The UR was in the ’must
| following conditions: | complete’ phase of abort. Its change on the
| v URs that have changes on the recovered objects | objects being recovered must be rolled back.
| which need to be rolled back during the LOGUNDO | v D INDOUBT: The UR had completed the
| phase. | first phase of commit, but DB2 had not
| v The scope of log records that require processing in | received the second phase instruction. Its
| order to roll back the changes. | change on the objects being recovered must
| be rolled back.
| For each active UR in the table, you will see one line | v F INFLIGHT: The UR had not completed
| with the following format showing the UR information: | the first phase of commit. Its change on the
| objects being recovered must be rolled back.
| MEM T CONID CORRID AUTHORIZATION ID | v P POSTPONED ABORT: The UR has not yet
| PLAN S URID DAY TIME | completed backout after DB2 was last
612 Messages
DSNU1554I • DSNU1556I
| Severity:
DSNU1602I csect-name - BACKUP SYSTEM UTILITY
| 0 (informational) COMPLETED, ELAPSED TIME =
hh:mm:ss
System action: The RESTORE SYSTEM utility has begun applying logs
beginning at the log-point-value in order to arrive at
The restart is ignored, and a new BACKUP SYSTEM the point in time indicated by the log point at which
request is initiated. the logs were truncated via the SYSPITR parameter on
System programmer response: the conditional restart command, CRESTART CREATE.
Severity: None.
0 (informational) Severity:
0 (informational)
614 Messages
DSNU1606I • DSNU1611I
8 (error)
DSNU1606I csect-name - RESTORE SYSTEM
UTILITY STARTING, COPY POOL =
copy-pool-name, TOKEN = X’token’ DSNU1609I csect-name - BACKUP SYSTEM UTILITY
REQUIRES SYSADM OR SYSCTRL
Explanation:
AUTHORITY TO RUN. THE CALLER
Restore of the indicated copy pool with the indicated HAS INSUFFICIENT AUTHORITY
token is starting.
Explanation:
System action:
The invoker of the BACKUP SYSTEM utility lacks the
None. SYSADM or SYSCTRL authority required to run the
utility.
System programmer response:
System action:
None.
The utility is terminated.
Severity:
System programmer response:
0 (informational)
Ensure that the BACKUP SYSTEM utility is run by an
administrator with SYSADM or SYSCTRL authority.
DSNU1607I csect-name - RESTORE SYSTEM
UTILITY REQUIRES INSTALL Severity:
SYSADM AUTHORITY TO RUN. THE
8 (error)
CALLER HAS INSUFFICIENT
AUTHORITY
DSNU1610I csect-name - AN INCOMPLETE BACKUP
Explanation:
SYSTEM HISTORY ENTRY HAS BEEN
The invoker of the RESTORE SYSTEM utility lacks the FOUND IN THE BSDS, INDICATING
install SYSADM authority required to run the utility. THERE MAY BE AN INVALID DATA
AND LOG VERSION IN COPYPOOL =
System action:
copy-pool-name FOR TOKEN = X’token’.
The utility is terminated. DFSMSHSM WILL BE CALLED TO
DELETE THE VERSION
System programmer response:
Explanation:
Ensure that the RESTORE SYSTEM utility is run by an
administrator with install SYSADM authority. During Backup System processing, an incomplete
backup history entry was found in the BSDS. For
Severity: example, an incomplete entry can exist if DB2 or z/OS
8 (error) goes down before backup processing can complete.
Such an entry indicates that a data and log version may
exist in the indicated copy pool for the indicated token.
DSNU1608I csect-name - system-utility SYSTEM
UTILITY FAILED. REQUIRED System action:
DFSMSHSM SERVICES NOT Backup System will invoke DFSMShsm to delete the
AVAILABLE. version of the data and logs before proceeding with the
Explanation: current backup.
The system that attempted to run the BACKUP System programmer response:
SYSTEM or RESTORE SYSTEM utility does not have None.
the version of z/OS that contains the version of
DFSMSHSM that is required by those utilities. Severity:
616 Messages
DSNU1618I • DSNU1624I
System programmer response: Restoration of the data from the indicated copy pool
with the indicated token has completed successfully.
Determine why these systems are in a problem state,
and whether they can be moved out of this state. Once System action:
all members have been returned to either the active or
Continue with log apply phase.
normally quiesced state, resubmit the job.
System programmer response:
Severity:
None.
8 (error)
Severity:
DSNU1626I csect-name - system-utility SYSTEM 0 (informational)
UTILITY FAILED BECAUSE RESTORE
SYSTEM IS ALREADY RUNNING OR
DSNU1628I csect-name - RESTORE SYSTEM PHASE
ANOTHER TASK IS PROCESSING IN
LOG APPLY COMPLETED, ELAPSED
A MANNER THAT PREVENTS THIS
TIME = hh:mm:ss
TASK FROM SERIALIZING PROPERLY
Explanation:
Explanation:
The log apply phase of the RESTORE SYSTEM
The attempt to acquire the serialization lock failed. In
completed in the amount of time that was indicated.
the case of RESTORE SYSTEM, this can only occur if
RESTORE SYSTEM is already running. In the case of Severity:
BACKUP SYSTEM, this can occur if any of the
following events are in process: 0 (informational)
v System checkpoint
v Data set extensions DSNU1629I csect-name - DB2 PUT ONE OR MORE
OBJECTS INTO THE
v Writing 32K pages RECOVER-PENDING STATE,
v Writing close page set control log records (PSCRs) REBUILD-PENDING STATE, OR
v Creating data sets (for table spaces, indexes, and so LOGICAL PAGE LIST DURING THE
on) LOG APPLY PHASE.
v Deleting data sets (for dropping tables spaces, Explanation:
indexes, and so on)
During the log apply process, objects were put into one
v Renaming data sets (for online reorganizing of table of the exception states that is indicated in the message.
spaces, indexes, and so forth during the switch Before these objects can be used, they must be
phase) processed again after the Restore completes.
System action: System action:
The utility is terminated. None.
System programmer response: System programmer response:
If it is the RESTORE SYSTEM utility that is being Process those objects in the RECOVER-PENDING or
invoked, the only other utility that can be running is REBUILD-PENDING states with the REBUILD or
RESTORE SYSTEM. If it is the BACKUP SYSTEM RECOVER utilities as appropriate. See the Utility Guide
utility that is being invoked, any system activity that and Reference for further details.
provokes any of the processes listed in the Explanation
above could be the cause of the failure. If possible, To recover pages from the LPL, use the -START
determine which utility is responsible and resubmit this DATABASE command with the SPACENAM option,
job once that utility completes. You may also resubmit the RECOVER utility, or the LOAD utility.
your job at a later, less busy time.
Problem determination:
Severity:
Use the DISPLAY DATABASE command to identify
8 (error)
618 Messages
DSNU1630I • DSNU1632I
which objects are in the exception states indicated in | If you specified END FCINCREMENTAL, then remove
the message. | these keywords until the next backup version of the
| database copy pool to be taken is the version associated
Severity:
| with the persistent incremental FlashCopy relationship.
0 (informational) | END FCINCREMENTAL can only be specified to take a
| last incremental FlashCopy and withdraw the persistent
| incremental FlashCopy relationship when the backup
| DSNU1630I csect-name BACKUP SYSTEM UTILITY | version to be taken is the incremental FlashCopy
| FAILED, BECAUSE action | relationship.
| FCINCREMENTAL WAS SPECIFIED
| BUT THE INCREMENTAL | Severity:
| FLASHCOPY COULD NOT BE
| 8 (error)
| PROCESSED
| Explanation:
| DSNU1631I utility-name SYSTEM UTILITY FAILED
| This message is issued when all of the following | BECAUSE THE CALL TO DFSMSHSM
| conditions exist: | FAILED WITH RC=X’ rc’, REASON
| v The database copy pool has been defined with more | CODE=X’rsc’. PLEASE SEE THE HSM
| than one DASD version. | ACTIVITY LOG FOR HSM MESSAGES
| INDICATING THE CAUSE OF ERROR
| v A persistent incremental FlashCopy relationship
| already exists for the database copy pool. | Explanation:
| v The next version or backup of the database copy | The call to DFSMShsm to perform the backup or the
| pool to be taken is for a full FlashCopy rather than | restore of the copy pools failed with the return code
| an incremental FlashCopy. | and reason code indicated in the message.
DSNU1633I csect-name - BACKUP SYSTEM UTILITY | If you suspect a problem, run the DSN1LOGP
FAILED BECAUSE UNABLE TO WRITE | stand-alone utility to verify which objects were affected
BSDS RECORD DUE TO VSAM | by the RESTORE SYSTEM utility.
ERROR: RC = X’return code’, RSN =
| Severity:
X’reason code
| 0 (informational)
Explanation:
The attempt to update or insert the BACKUP SYSTEM
| DSNU1636I RESTORE SYSTEM UTILITY FAILED
history BSDS record failed due to an error during
| BECAUSE THE SPECIFIED
VSAM processing. The VSAM return and reason codes
| DUMPCLASS IS NOT KNOWN TO
are indicated in the message.
| DFSMSHSM
System action:
| Explanation:
The utility is terminated.
| The RESTORE SYSTEM Utility failed to restore the DB2
System programmer response: | database copy pool because the DFSMShsm dump
| pclass specified does not exist for the system-level
The return and reason code in the message will identify | backup. Specify the DFSMShsm dump class via the
the VSAM error that occurred when attempting to | RESTORE SYSTEM DUMPCLASS option or via install
write out the BSDS record. Correct the problem and | panel DSNTIP6 by specifying RESTORE/RECOVER
resubmit the job. | From dump => YES and DUMP CLASS NAME =>
Severity: | hsm-dumpclass-nm.
| Severity: | Severity:
| 8 (error) | 8 (error)
| DSNU1635I csect-name THE RBA RANGE FOR THE | DSNU1637I RESTORE SYSTEM UTILITY FAILED
| LAST CHECKPOINT ISSUED DURING | BECAUSE NO FLASHCOPY IS
| THE LOGAPPLY PHASE OF THE | AVAILABLE
| RESTORE SYSTEM UTILITY IS | Explanation:
| START_RBA = X’yyyyyyyyyyyy’
| END_RBA = X’zzzzzzzzzzzz’ FOR | The RESTORE SYSTEM Utility could not restore the
| MEMBER mmmm | DB2 database copy pool because the DASD version of
| the system-level backup is unavailable.
620 Messages
DSNU1638I • DSNU1702I
| System action: | complete faster than the background copy for a full
| copy.
| The RESTORE SYSTEM Utility terminates processing.
| System programmer response:
| System programmer response:
| You might have to take action if an incremental copy
| Issue the DFSMShsm LIST COPYPOOL command with
| was not expected. Run a LIST COPYPOOL command
| the ALLVOLS option for the DB2 database copy pool.
| and run the print log map (DSNJU004) utility.
| Run the Print Log Map Utility (DSNJU004) to print the
| system-level backup information. If data sharing, | Severity:
| ensure that the system-level backup information from
| all members is gathered. Locate the system-level
| 0 (informational)
| backup information in the DSNJU004 output and
| compare it with the output from the LIST COPYPOOL DSNU1640I csect-name - Z/OS DFSORT LOAD
| command. MODULE NOT LOADED.
| If the system-level backup has been dumped to tape, Explanation:
| then you can use either of these options to direct the
| utility to use the copy of the system-level backup on The required z/OS DFSORT load module was not
| tape: located in the system search order.
| DSNU1638I RESTORE SYSTEM UTILITY FAILED Verify that you correctly configured your system to
| BECAUSE NO FLASHCOPY IS allow DB2 to use DFSORT load modules. If DFSORT is
| AVAILABLE not installed as your primary z/OS sort product, refer
to the DB2 for z/OS Installation Guide’s section
| Explanation: regarding install panel DSNTIPW, for information on
| The DFSMShsm LIST COPYPOOL command issued by how to make the DFSORT SORTLPA and SICELINK
| the RESTORE SYSTEM Utility has failed. The libraries available for use by DB2 utilities.
| information from the LIST COPYPOOL command is Severity:
| required to correctly restore system-level backups that
| have been dumped to tape. 8 (error)
| System action:
| DSNU1702I csect-name - LOB PAGE TYPE
| The RESTORE SYSTEM Utility terminates processing. | MISMATCH. ROWID rowid VERSION
| System programmer response: | version PAGE page-number EXPECTED
| TYPE bit-value ACTUAL TYPE bit-value
| Refer to the DFSMShsm manuals using the return code
| and reason code to determine why the LIST | Explanation:
| COPYPOOL command failed and correct the problem. | A LOB page with page number page-number has an
| You can execute the RESTORE SYSTEM Utility again | unexpected page type specification. In the expected and
| after correcting the problem. | actual page types, bit-value is a 3-bit value. The
| Severity: | expected values can be B’100’ for a LOB map page or
| B’110’ for a LOB data page. The LOB page in error is
| 8 (error) | part of the LOB with the ROWID rowid and version
| version.
| DSNU1639I csect-name THE SYSTEM LEVEL | System action:
| BACKUP TAKEN IS AN
| INCREMENTAL FLASHCOPY OF THE | If SHRLEVEL REFERENCE was specified or defaulted,
| DATABASE COPY POOL | then the LOB table space status is set to CHECK
| Pending (CHKP). If SHRLEVEL CHANGE was
| Explanation: | specified, then the table space status remains
| This message indicates that the system level backup
| unchanged.
| that was created by the BACKUP SYSTEM utility is an | System programmer response:
| incremental FlashCopy of the database copy pool. This
| indicates that, in most cases, the background copy will | Notify IBM Software Support.
622 Messages
DSNU1710I • DSNU1718I
| DSNU1710I csect-name - LOB PAGE ALLOCATED | DSNU1714I csect-name - LOB MAP PAGE COUNT
| TO A DIFFERENT LOB. PAGE | INCORRECT. ROWID rowid VERSION
| page-number IS IN THE LOB MAP OF | version EXPECTED COUNT hex-value1
| ROWID rowid1 VERSION version1. | ACTUAL COUNT hex-value2
| LOW-LEVEL SPACE MAP INDICATES
| THE PAGE BELONGS TO ROWID
| Explanation:
| rowid2 VERSION version2 | The actual count of data pages, hex-value1, does not
| Explanation: | match the expected number of pages, hex-value2, that is
| specified in the LOB map page. The LOB in error is
| The LOB page with page number page-number, is in the | identified by ROWID rowid and version version.
| LOB map of the LOB with ROWID rowid1 and version
| version1. A low-level space map indicates that the page
| System action:
| belongs to different LOB with ROWID rowid2 and | If SHRLEVEL REFERENCE was specified or defaulted,
| version version2. The page can be a data page or a LOB | then the LOB table space status is set to CHECK
| map page. | Pending (CHKP). If SHRLEVEL CHANGE was
| System action: | specified, then the table space status remains
| unchanged.
| If SHRLEVEL REFERENCE was specified or defaulted,
| then the LOB table space status is set to CHECK
| System programmer response:
| Pending (CHKP). If SHRLEVEL CHANGE was | Notify IBM Software Support.
| specified, then the table space status remains
| unchanged. | User response:
| User response: | 4
624 Messages
DSNU1726I • DSNU1730I
| Explanation:
| A CANCEL command was issued for a job while a DB2
| utility was active. The job will terminate after all of its
| An attempt to read page number page-number failed | DB2 threads have terminated.
| with error code hex-value1 and reason code of
| hex-value2. The page belongs to the LOB with the | System action:
| ROWID rowid and version version. page-type specifies | All threads created by the utility will perform the
| the type of page that is expected: ’LOB MAP’ for an | rollback and deallocation processing that is required.
| expected LOB map, or ’LOB DATA/MAP’ for a page | When this is complete the job will terminate.
| that could be a LOB map or a data page.
| System programmer response:
| System action:
| Rollback processing might take a significant amount of
| If SHRLEVEL REFERENCE was specified or defaulted, | time, especially for a LOAD LOG YES utility. Under
| then the LOB table space status is set to CHECK | extreme conditions a FORCE command can be used to
| Pending (CHKP). If SHRLEVEL CHANGE was | immediately terminate the job, but this is not
| specified, then the table space status remains | recommended because it can cause the thread
| unchanged. | deallocation to abend.
626 Messages
DSNU3330I • DSNU3342I
| Severity:
DSNU3340I UTILITY PERFORMS DYNAMIC
| 0 ALLOCATION OF SORT DISK SPACE
Explanation:
DSNU3330I csect-name - The utility-name UTILITY IS
The utilities that invoke a sort will perform predictable
PART OF A SEPARATELY LICENSED
sort disk space dynamic allocation.
FEATURE WHICH WAS NOT FOUND
ON THIS SYSTEM. System action:
Explanation: Processing of the phase continues.
DB2 could not find the specified utility in the load Programmer response:
library concatenation specified in the submitted JCL.
No action is required.
The specified utility is part of an optional feature of
DB2. Severity:
System action: 0 (Informational)
Utility processing does not initiate.
User response:
| DSNU3341I CANNOT ALLOCATE SORT DATA
| SETS WITHIN 255 LIMIT
Obtain and install the optional utility feature
(JDB991K).
| Explanation:
Severity:
| When the utility performs dynamic allocation of sort
| datasets, the total number of datasets per phase must
8 (error) | be less than 255 data sets.
| System action:
| DSNU3333I LOAD MODULE module-name DID NOT
| LOAD CORRECTLY. THE utility-name
| Utility processing is terminated.
| UTILITY FUNCTION IS RESTRICTED | System programmer response:
| Explanation: | Provide more disk space for sort work datasets.
| The identified load module was found in the product | Programmer response:
| library, but could not be loaded into memory correctly.
| No action is required.
| System action:
| Severity:
| Utility processing continues but the identified utility
| has restricted function. It may only be executed against | 8 (error)
| objects in the DB2 catalog, the DB2 directory or the
| DB2 sample program. | DSNU3342I NUMBER OF OPTIMAL SORT TASKS
| User response: | = nnn, NUMBER OF ACTIVE SORT
| TASKS = nnn
| Notify the system programmer.
| Explanation:
| System programmer response:
| The first number indicates the optimal number of sort
| Make sure the identified load module is reenterable | tasks for the utility execution. The second number
| and reusable and that it is being loaded from an APF | show the maximum number of sort tasks possible for
| authorized library. This error is normally caused by | the utility execution.
| incorrectly copying a load module or its alias. Use only
| SMP/E APPLY or the IEWL program to create load | System action:
| modules and their aliases. If SMP/E has produced a | Processing of the phase continues.
| load module that is not reenterable and reusable notify
| IBM Software Support. | Programmer response:
| Severity: | No action is required.
| 4 (warning) | Severity:
| 0 (informational)
0 (informational)
DSNU3343I REAL-TIME STATISTICS
INFORMATION MISSING FOR obj-type
obj-qual.obj-name partition-information DSNU11193I csect-name SQLCODE = xxxx, INVALID
SQLCODE
Explanation:
Explanation:
The utility could not read necessary information from
real-time statistics tables for the specified index or table The SQL return code is not a valid value.
space. Partitioned objects will include the partition
number for which information is missing. System action:
The utility continues, but will use estimates based on User response:
RUNSTATS information for this object. Either the SQLCA area is invalid or the maintenance
System programmer response: was not coordinated correctly. As a result, the SQL
return code was added to the DB2 subsystem but not
Make sure that real-time statistics are enabled on the to the formatting routine. If the maintenance was not
system. Run the REORG or REBUILD INDEX utility on coordinated correctly, the DSNTIAM CSECT was
the specified object to set the base values in the probably not replaced in the current STEPLIB or
real-time statistics tables. JOBLIB.
Severity: Problem determination:
0 (informational) If DSNTIAM is current then this error is an internal
error.
DSNU11191I csect-name SQLCAID = xxxx, SQLCA Severity:
IDENTIFIER
0 (informational)
Explanation:
The SQLCA ID field (SQLCAID) is not the expected DSNU11194I csect-name SQLERRM = xxxx, SQLCA
value, C’SQLCA’. ERROR MESSAGE INSERTION TEXT
System action: Explanation:
Utility processing continues. This message results from an SQL return code that is
not recognized by DSNTIAR. SQLERRM contains error
User response:
message test.
The SQLCA area is invalid.
System action:
Problem determination:
Utility processing continues.
This error is an internal error.
User response:
Severity:
Either the SQLCA area is invalid or the maintenance
0 (informational) was not coordinated correctly. As a result, the SQL
return code was added to the DB2 subsystem but not
to the formatting routine. If the maintenance was not
DSNU11192I csect-name SQLCABC = xxxx, SQLCA
coordinated correctly, the DSNTIAM CSECT was
BYTE COUNT
probably not replaced in the current STEPLIB or
Explanation: JOBLIB.
The size of the SQLCA is not the expected value (136 Problem determination:
bytes).
If DSNTIAM is current then this error is an internal
System action: error.
628 Messages
DSNU11195I
The MVS service aid AMBLIST provides Linkage Editor System action:
module attributes in the summary section of the
This message is issued as information only. The
LISTLOAD function output.
message indicates that the -ARCHIVE LOG
MODE(QUIESCE) command has not completed, and the -DISPLAY THREAD command. Information
consequently, updates against DB2 resources have been provided is:
temporarily suspended. This may result in active
name A 1- to 8-character variable representing the
threads being suspended awaiting termination of the
’connection name’ used to establish the thread.
quiesce period. DB2 processing otherwise continues
For distributed database access threads, this
normally.
field contains the following:
v For threads using system-directed access
DSNV401I DISPLAY THREAD REPORT FOLLOWS and for threads using application-directed
- access from a DB2 Version 3 or later
Explanation: requester, this variable displays the
connection name of the thread at the
This message is always generated as the title for the requesting location.
DISPLAY THREAD command report output. It
v For threads using application-directed access
precedes the other messages generated by this
from a non-DB2 requester or from a DB2
command.
Version 2 Release 3 requester, this variable
System action: displays the constant SERVER.
632 Messages
DSNV404I
QD The thread is queued for termination from another location. The thread is
as a result of the termination of the suspended because the maximum
associated allied task. If this thread is number of active database access
also the last (or only) DB2 thread for threads (as described by the MAX
the address space, the associated REMOTE ACTIVE value of the
allied task is placed in a wait state. DSN6SYSP macro in the DB2 startup
parameter, usually DSNZPARM) was
QT The CREATE THREAD request was
reached. Database access agents
queued. The associated allied task is
(DBAAs) are queued until other
placed in a wait state.
DBAAs deallocate or go inactive,
| R2 A distributed thread is performing a providing an available slot. The
| remote access on behalf of a request DBAA resumes when a slot becomes
| from another location. The thread is available, and the DBAA is next in
| currently an inactive connection (type the queue. Alternatively, you should
| 2 inactive thread) and is waiting for consider increasing the MAX
| an agent to become available to REMOTE ACTIVE value.
| process.
RX The distributed thread is executing an
RA The distributed thread is performing XA transaction on behalf of a request
a remote access on behalf of a request from another location.
from another location.
SP A thread is executing within a stored
RK A distributed thread is performing procedure. This status is displayed
remote access on behalf of a request until the stored procedure terminates
from another location. The thread is and returns control to DB2.
performing an operation that invoked
SW A thread is waiting for a stored
Kerberos services. This status is
procedure to be scheduled. This
displayed until Kerberos services
status is displayed until the stored
returns control to DB2.
procedure begins execution.
RN A distributed thread is performing a
T An allied, nondistributed thread was
remote access on behalf of a request
established (plan allocated).
from another location. The request
actually accesses data at yet another | TD An allied thread was established
(DB2) location, so the thread was | (plan allocated), and the thread is
suspended because DB2 must first | currently not associated with any
connect to the partner location | TCB.
(establish DB2 system conversations
TN An allied thread was distributed to
with the partner).
access data at another DB2 location,
When another DB2 site is being but it was suspended because DB2
contacted for the first time using must first connect to the partner
system-directed access, DB2 must location (establish DB2 system
establish DB2 system conversations conversations with the partner).
with the partner location. A request is
When another DB2 site is being
presented to a DB2 DDF service task
contacted for the first time using
that establishes a system
system-directed access, DB2 must
conversation. The thread is
establish DB2 system conversations
suspended until the request is
with the partner location. A request is
processed. If the thread remains in
presented to a DB2 DDF service task
this status for an extended period of
that establishes a system
time, the DB2 service task that
conversation. The thread is
establishes the system conversations
suspended until the request is
might be busy processing other
processed. If the thread remains in
requests. The DB2 DISPLAY
this status for an extended period of
LOCATION command (’DISPLAY
time, the DB2 service task that
LOCATION(*) DETAIL’) shows you
establishes the system conversations
conversation activity for this DB2
might be busy processing other
system conversation (SYSCON-O)
requests. The DB2 DISPLAY
service task.
LOCATION command (’DISPLAY
RQ A distributed thread is performing a LOCATION(*) DETAIL’) shows you
remote access on behalf of a request
conversation activity for this DB2 requester, this variable displays the plan
system conversation (SYSCON-O) name being executed at the requesting
service task. location.
TR An allied thread was distributed to v For threads using application-directed access
access data at another location. from a non-DB2 requester or from a DB2
Version 2 Release 3 requester, this field
act-ind An asterisk if the thread is active within DB2; displays the constant DISTSERV.
blank otherwise.
req-ct A wraparound counter to show the number of For RRSAF connected threads that did not
DB2 requests. specify a plan name at connect time, the value
?RRSAF is displayed. If a thread was not
corr-id A 1- to 12-character variable representing the established, this field is blank.
recovery ’correlation-id’ associated with the
thread. If you receive a system plan in this field, see
For distributed database access threads, this the information about system plans in message
field contains the following: DSNT376I.
v While the thread is being created: asid A 1- to 4-character hexadecimal number
– ’028.DBAA nn’ - Where nn ranges from representing the ASID of the home address
01 to 99. This indicates that the DBAA is space.
in its connection processing, which token A 1- to 6-character number representing the
consists of establishing the DBAA thread, thread token assigned to the thread. For
and validating and verifying the user’s threads with a status value of ’N’, this value
ID. Refer to ″Controlling Access to a DB2 will be 0.
Subsystem″ in Administration Guide for
descriptions of the authorization checks The message number and subsystem recognition
that might be performed. character are not included in this message.
RACF requests are serialized on one of
the DB2 RACF service tasks, which might System action:
increase the validation time when Processing continues normally.
multiple DBAAs are being created
concurrently. System programmer response:
v After the thread is created: If you have active threads with QD or D status codes,
– For threads using system-directed access use the information in message DSN3201I to diagnose a
and threads using application-directed possible DB2 problem.
access from a DB2 requester, this variable
displays the correlation-id name of the DSNV405I DISPLAY ACTIVE REPORT
thread at the requesting location. COMPLETE
– For threads using application-directed
Explanation:
access from a non-DB2 requester, this
variable displays the first twelve This message follows messages DSNV402I through
characters in the DDM external name DSNV404I augmented by the series of messages
(EXTNAM) parameter of the DDM DSNV444I through DSNV448I when LOCATION
EXCSAT command received as part of and/or DETAIL keywords are used to show distributed
the SQL CONNECT. activity. It indicates that the -DISPLAY THREAD
TYPE(ACTIVE) report has completed successfully.
authorization ID
The authorization ID associated with a The message number and subsystem recognition
signed-on connection. If not signed-on, this character are not included in this message.
field is blank.
System action:
pname A 1- to 8-character variable representing the
plan name associated with the thread. For Processing continues normally.
distributed database access threads, this field
contains the following: DSNV406I INDOUBT THREADS-
v For threads using system-directed access
Explanation:
and threads using application-directed
access from a DB2 Version 3 or later This message precedes the listing of indoubt threads.
The series of messages DSNV406I through DSNV409I,
DSNV446I, DSNV449I through DSNV453I, DSNV457I
634 Messages
DSNV407I • DSNV408I
through DSNV464I, DSNV466I, DSNV467I provides TCP/IP port number for two-phase
theformatted report for the -DISPLAY THREAD commit resynchronization.
TYPE(INDOUBT) command when the status of indoubt v If the thread is distributed, message
threads is requested. DSNV467I is included in the display. This
System action: message shows the logical unit of work id
and the local token that identifies the
Processing continues normally. distributed thread.
status The status of the thread.
DSNV407I COORDINATOR STATUS RESET URID
AUTHID A status of ABORTED is not displayed unless
DB2 believes a participant using PN protocols
Explanation: might be indoubt. If the status of a thread for
This message displays the column headings for the list a logical unit of work at a participant is
of threads generated by the DISPLAY THREAD TYPE INDOUBT, COMMITTED-H, or ABORTED-H,
(INDOUBT) command, or for the list of Postponed and the coordinator is a DB2 location that has
Abort URs generated by the DISPLAY THREAD not cold started, then the lack of any
TYPE(POSTPONED) or DISPLAY THREAD TYPE(*) information about the thread in a DISPLAY
command. THREAD(INDOUBT) report indicates that the
decision at the coordinator was to abort the
The message number and the subsystem recognition logical unit of work. In all other cases, a
character are not included in this message. DSNV408I message for the thread is displayed.
System action: v INDOUBT: The thread is indoubt and
continues to appear in the display until all
Processing continues normally. indoubt resolution responsibilities are
complete. Additional detail lines that might
DSNV408I coordinator status reset urid authid appear in the report are:
– DSNV450I and DSNV446I: The names of
Explanation:
downstream participants who might be
This message lists status information on an indoubt indoubt.
thread or for a Postponed Abort UR. – DSNV452I or DSNV453I: A heuristic
coordinator action was taken at a downstream
The name of the two-phase commit participant. DSNV452I or DSNV453I
coordinator. continues to appear in the display until
DB2 resolves the indoubt status with the
v If the thread is an allied thread, the coordinator. If the coordinator decision is
coordinator name is either the IMS the same as the heuristic decision of the
connection name, the CICS connection partner, then the detail line is no longer
name, RRS (for Resource Recovery Services displayed. If the coordinator status is
attachment facility connected threads) or the COMMITTED and the heuristic decision
location name of the local DB2 (if it is not of the participant is ABORTED, then the
one of the above). DSNV449I is displayed if message continues to appear in the
the coordinator is IMS or CICS. display until it is deleted with the RESET
v If the thread is a database access thread, the INDOUBT command. The database
coordinator name takes one of four forms: administrators at all involved locations
– location:luname -- where ″location″ is the need to know that heuristic damage
coordinator’s relational database name occurred and at which location.
and ″luname″ is the coordinator’s SNA – DSNV466I: For a database access thread
LU name. participant, the elapsed time that the
– location:port -- where ″location″ is the thread was indoubt.
coordinator’s relational database name v COMMITTED: The thread is committed.
and ″port″ is the coordinator’s TCP/IP This status is displayed when DB2 is the
port number for two-phase commit coordinator and has downstream
resynchronization. participants that might be indoubt. The
– <luname>:luname -- where ″luname″ is thread appears in the display until all
the coordinator’s SNA LU name. downstream participants complete indoubt
resolution. Detail lines DSNV450I and
– nnn.nnn.nnn.nnn:port -- where
DSNV446I list the downstream participants
″nnn.nnn.nnn.nnn″ is the coordinator’s IP
that have pending resolution. Database locks
address and ″port″ is the coordinator’s
held for the thread were released.
If a participant resolved the indoubt thread and DSNV446I list the downstream
with a heuristic decision, and the decision participants that have pending resolution.
was ABORT (rollback), detail line DSNV453I Database locks held for the thread were
is displayed. This detail line contains the released.
name of the participant and the heuristic If a participant resolved the indoubt thread
decision that it made. Since the coordinator with a heuristic decision, and the decision
committed and the participant aborted, this was COMMIT, detail line DSNV452I is
indicates heuristic damage. This line displayed. This detail line contains the name
continues to appear in the display until it is of the participant and the heuristic decision
deleted with the RESET INDOUBT that it made. Since the coordinator aborted
command. The database administrators at and the participant committed, this indicates
all involved locations need to know that heuristic damage. This line continues to
heuristic damage occurred and at which appear in the display until it is deleted with
location. the RESET INDOUBT command. The
v COMMITTED-H: The indoubt thread was database administrators at all involved
heuristically resolved with the RECOVER locations need to know that heuristic
INDOUBT command. The thread continues damage occurred and at which location.
to appear in the display until the v ABORT-P: This line represents a Postponed
coordinator is informed of the heuristic Abort UR. Objects for which this UR has
decision, and all downstream participants, if backout work pending are inaccessible
any, complete indoubt resolution. Detail (Restart Pending) until the abort is
lines DSNV450I and DSNV446I list the completed (for example, by means of the
downstream participants that have pending -RECOVER POSTPONED command).
resolution. Additional detail lines that might
v ABORT-PSTRT: This line represents a
appear in the report are:
Postponed Abort UR that is currently
– DSNV451I is displayed if resolution with undergoing -RECOVER POSTPONED
the coordinator is not complete. All processing or automatic DB2 backout
database locks were released. processing (requested by restarting with
– DSNV461I is displayed if resolution with system parameter LBACKOUT = AUTO).
the coordinator completed and heuristic
damage was detected after the Additional detail lines might appear in an
coordinator aborted the logical unit of indoubt thread report, as follows:
work. This line continues to appear in the v Cold Start: When a coordinator cold starts,
display until it is deleted with the RESET indoubt participants cannot achieve
INDOUBT command. automatic resolution. A DB2 participant
v ABORTED-H: The indoubt thread was includes message DSNV463I in the display,
heuristically resolved with the RECOVER indicating coordinator cold start and
INDOUBT command. The thread continues requesting heuristic resolution. Message
to appear in the display until the DSNV458I is included in the display if the
coordinator is informed of the heuristic coordinator cold started. This message
decision. Additional detail lines that might contains information that can be used to
appear in the report are: identify the thread. This information is
– DSNV451I is displayed if resolution with provided by the coordinator. A DB2
the coordinator is not yet complete. All coordinator provides the connection-name
database locks were released. used to establish the thread at the DB2
coordinator and the correlation-id used by
– DSNV461I is displayed if resolution with
that connection.
the coordinator completed and heuristic
damage was detected after the When a participant cold starts, the
coordinator committed the logical unit of coordinator cannot fulfill its indoubt
work. This line continues to appear in the resolution responsibility. A DB2 coordinator
display until it is deleted with the RESET displays message DSNV462I indicating
INDOUBT command. participant cold start. The thread continues
to be displayed in the report, even after
v ABORTED: This is a coordinator status and
resolution with all other indoubt
DB2 has one or more downstream
participants, if any. The RESET INDOUBT
participants using the Presumed Nothing
command must be used to purge this thread
(PN) protocol that might be indoubt. The
from the report. The reason for this is that
thread appears in the display until all
the cold starting participant might have
downstream PN participants complete
been coordinating downstream participants
indoubt resolution. Detail lines DSNV450I
that are now indoubt. The database
636 Messages
DSNV409I • DSNV411I
Reenter the command specifying one of the required Command processing continues.
parameters. Operator response:
Prior to reentering the command, ensure that the
DSNV414I THREAD xxx COMMIT SCHEDULED network-id entered is in the correct format as specified
Explanation: on the -RECOVER INDOUBT command.
638 Messages
DSNV417I • DSNV424I
System action:
DSNV417I THREAD xxx NOT FOUND
Command processing continues.
Explanation:
In this message, ’xxx’ is the recovery identifier specified
DSNV420I NO INDOUBT THREADS FOUND
with the -RECOVER INDOUBT command to identify
the indoubt thread and is one of the following: Explanation:
ID= The recovery correlation-id specified with the The -DISPLAY THREAD command found no indoubt
command threads within the system. This message is generated
when the command requests information about all (*)
NID= The recovery network-id specified with the
threads currently residing within an indoubt state
command
(TYPE=INDOUBT) within the system, but no threads
LUWID = currently exist within this state.
The luwid or token specified with the
System action:
command
Command processing continues.
The -RECOVER INDOUBT command was unable to
locate the specified thread to be scheduled for recovery.
DSNV423I DISPLAY THREAD MESSAGE POOL
Either the thread identifier is incorrect, or the thread no
SIZE EXCEEDED
longer is in an indoubt state.
Explanation:
System action:
| The amount of CSA or ECSA virtual storage that was
Command processing continues.
| needed to generate a -DISPLAY THREAD response
Operator response: | display exceeded the maximum size of the message
| buffer pool.
Before reentering the command, ensure that the thread
still is in an indoubt state. | This can happen when there are many threads in DB2,
| and the pattern-matching character ’*’ is used in a
| -DISPLAY THREAD command. For example:
DSNV418I RECOVER INDOUBT REJECTED FOR
ID= correlation-id | -DISPLAY THREAD(*)
Determine the correct token of the thread you want to asid The MVS ASID of the address space where the
cancel and reissue the command. You can use the stored procedure is running. This field will
-DISPLAY THREAD command to display all thread contain 0000 until the stored procedure has
activity. been assigned to a specific stored procedure
address space.
wlmenv The name of the WLM application
environment where the stored procedure is
running.
System action:
640 Messages
DSNV431I • DSNV436I
Explanation: CANCELLATION
Indicates that the CANCEL option was
This message follows messages DSNV431I and specified on the RECOVER POSTPONED
DSNV408I and indicates that the -DISPLAY THREAD command and that the backout process will be
TYPE(POSTPONED) report was completed successfully, canceled.
or that the section of the -DISPLAY THREAD TYPE(*)
report for Postponed Abort URs has been completed System action:
successfully.
The command (or auto-resolution processing)
System action: completes normally.
642 Messages
DSNV443I • DSNV446I
644 Messages
DSNV449I • DSNV450I
646 Messages
DSNV458I • DSNV460I
DSNV462I V462-COLD START BY PARTICIPANT See message DSNL411I for more information.
AT LOCATION location
Explanation: DSNV464I V464-RESYNC PROTOCOL ERROR
WITH COORDINATOR
This message is a detail line which might be displayed
with a DISPLAY THREAD TYPE (INDOUBT) report. Explanation:
There was an indoubt thread at the participant whose This message is a detail line which might be displayed
’luwid’ is displayed in the preceding DSNV408I with a DISPLAY THREAD TYPE (INDOUBT) report.
message. DB2 has coordinator responsibility for the Manual resolution of an indoubt thread at this location
indoubt thread and the participant informed DB2 that it is required. A protocol error was detected during
performed a cold start operation and lost all knowledge attempted automatic indoubt resolution with the
of indoubt threads. There might be heuristic damage at coordinator. The ’coordinator’ and the ’luwid’ of the
the participant. The RESET INDOUBT command must thread that requires manual resolution are both
be used to purge this message from the indoubt report. displayed in the preceding DSNV408I message.
The reason for this is that the cold-starting participant
might have been coordinating downstream participants The message number and subsystem recognition
that are now indoubt. The database administrator at character are not included in this message. However,
these participants might need to know the status of the V464 is included in the message text to identify the
thread at the coordinator, so that correct heuristic message.
decisions can be made. System action:
| location Processing continues normally.
| The relational database name (location-name)
| where the cold start was performed. Operator response:
See message DSNL404E for more information.
The message number and subsystem recognition
character are not included in this message. However,
V462 is included in the message text to identify the
message.
System action:
648 Messages
DSNV465I • DSNV471I
hh:mm:ss
DSNV465I V465-THREAD HAS REMAINED IN A
The length of time the thread was indoubt
PREPARED STATE FOR hh:mm:ss
(expressed in hours, minutes and seconds).
Explanation: The maximum number of hours reported is
65535, which is roughly 7.5 years. After this
This message might be displayed with a DISPLAY
time period elapses, the count is reset to zero.
THREAD TYPE (ACTIVE) report. The thread was
’prepared’ for the specified period of time. This means
The following actions might be taken to resolve this
that DB2 is the participant in the logical unit of work
thread by manual means (that is, take heuristic action)
and completed the first phase of commit and is waiting
if it is necessary to release locks held by this thread.
for the commit or abort decision to be transmitted from
the coordinator for the specified period of time. The v Determine the proper decision (commit or abort) by
thread is identified in the preceding DSNV404I contacting the coordinator ’location’ shown in the
message. This message does not appear in a report display of indoubt threads.
until the thread was in the prepared state for 60 v Use the RECOVER INDOUBT command to
seconds. heuristically commit or abort the thread.
hh:mm:ss
The length of time the thread was prepared The message number and subsystem recognition
(expressed in hours, minutes and seconds). character are not included in this message. However,
The maximum number of hours reported is V466 is included in the message text to identify the
65535, which is roughly 7.5 years. After this message.
time period elapses, the count is reset to zero. System action:
The following actions might be taken to resolve this Processing continues normally.
thread by manual means (that is, take heuristic action)
if it is necessary to release locks held by this thread. DSNV467I V467-HAS LUWID luwid=token
v Use the -CANCEL DDF THREAD command to force
Explanation:
the thread from the prepared state to the indoubt
state. When the thread is indoubt, it appears in the This message is a detail line, which might be displayed
display generated by issuing the DISPLAY THREAD with a DISPLAY THREAD TYPE (INDOUBT) report.
command for type indoubt threads.
luwid=token
v Determine the proper decision (commit or abort) by The global logical unit of work id and the
contacting the coordinator ’location’ shown in the local token that identifies the thread.
display of indoubt threads.
v Use the RECOVER INDOUBT command to The message number and subsystem recognition
heuristically commit or abort the thread. character are not included in this message. However,
V467 is included in the message text to identify the
The message number and subsystem recognition message.
character are not included in this message. However,
System action:
V465 is included in the message text to identify the
message. Processing continues normally.
System action:
DSNV471I V471-luwid=token
Processing continues normally.
Explanation:
DSNV466I V466-THREAD HAS BEEN INDOUBT This message follows a DSNV404I message and
FOR hh:mm:ss indicates the agent is currently not associated with a
remote location. The agent is available to be assigned to
Explanation:
process;
This message is a detail line which might be displayed v the completion of a queued receive request on a type
with a DISPLAY THREAD TYPE (INDOUBT) report. 2 inactive thread, or
The thread entered the indoubt state at the specified
v a request that a new connection be established, after
time. This means that DB2 is the participant in the
MAX REMOTE ACTIVE has been reached.
logical unit of work and completed the first phase of
commit and is waiting for the commit or abort decision This message displays the logical-unit-of-work
to be transmitted from the coordinator. However, DB2 identifier assigned to the agent.
lost communications with the coordinator. The thread is
identified in the preceding DSNV408I message. luwid=token
The global logical unit of work id and the
local token that identifies the agent.
The message number and subsystem recognition found on member memname as the result of
character are not included in this message. However, SCOPE(GROUP) keyword.
V471 is included in the message text to identify the
Messages DSNV475I, DSNV403I, DSNV404I and
message.
DSNV425I provide the formatted report for the
System action: -DISPLAY THREAD TYPE(INACTIVE)
SCOPE(GROUP) when the status of inactive threads is
Command processing continues.
requested.
The series of messages DSNV444I through DSNV448I
DSNV473I ACTIVE THREADS FOUND FOR
augment the formatted report for the -DISPLAY
MEMBER: memname-
THREAD TYPE(INACTIVE) SCOPE(GROUP) when
Explanation: LOCATION, LUWID, or DETAIL keywords are used to
show idle distributed threads.
This message precedes the listing of active threads
found on another member of a data sharing group as memname
the result of the SCOPE(GROUP) keyword. Member name for which thread information is
being displayed.
Message DSNV473I and the series of messages
DSNV403I through DSNV405I provide the formatted System action:
report for the -DISPLAY THREAD TYPE(ACTIVE)
Processing continues normally.
SCOPE(GROUP) when the status of active threads is
requested.
DSNV476I POSTPONED ABORT THREADS
The series of messages DSNV444I through DSNV448I
FOUND FOR MEMBER: memname
augment the formatted report for the -DISPLAY
THREAD TYPE(ACTIVE) SCOPE(GROUP) when Explanation:
LOCATION, LUWID, or DETAIL keywords are used to
This message precedes the listing of Postponed Abort
show distributed activity.
units of recovery found on another member of a data
memname sharing group as the result of the SCOPE(GROUP)
Member name for which thread information is keyword.
being displayed.
Messages DSNV476I, DSNV403I, DSNV404I and
System action: DSNV432I provide the formatted report for the
-DISPLAY THREAD TYPE(POSTPONED)
Processing continues normally.
SCOPE(GROUP) command.
memname
DSNV474I INDOUBT THREADS FOUND FOR
Member name for which thread information is
MEMBER: memname-
being displayed.
Explanation:
System action:
This message precedes the listing of indoubt threads
Processing continues normally.
found on member memname as the result of the
SCOPE(GROUP) keyword.
DSNV478I SCOPE(GROUP) DISPLAY
Messages DSNV474I, DSNV403I, DSNV404I and
TERMINATED DUE TO IRLM
DSNV409I provide the formatted report for the
TRUNCATION
-DISPLAY THREAD TYPE(INDOUBT) SCOPE(GROUP)
command when the status of indoubt threads is Explanation:
requested.
This message displays as a result of the -DISPLAY
memname THREAD command when the SCOPE(GROUP)
Member name for which thread information is keyword is specified and IRLM has truncated the
being displayed. responses gathered from other members. This is a DB2
internal error.
System action:
System action:
Processing continues normally.
The -DISPLAY THREAD report is terminated and
processing abnormally terminates.
DSNV475I INACTIVE THREADS FOUND FOR
MEMBER: memname- Operator response:
Explanation: Notify the system programmer.
This message precedes the listing of inactive threads System programmer response:
650 Messages
DSNV479I • DSNV492I
If you suspect an error in DB2, refer to Part 2 of recovery of the RRS Unit of Recovery is required, the
Diagnosis Guide and Reference for information on outcome of the DB2 Unit of Recovery can determine
identifying and reporting the problem. whether to COMMIT or ROLLBACK the RRS Unit of
Recovery.
Problem determination:
The message number and subsystem recognition
This is an internal error.
character are not included in this message. However,
V481 is included in the message text to identify the
DSNV479I SCOPE(GROUP) DATA UNAVAILABLE message.
IRLM RETURN CODE: retcode IRLM
System action:
REASON DATA: reason
Command processing continues normally.
Explanation:
This message displays as a result of the -DISPLAY
| DSNV485I V485- TRUSTED CONTEXT=tcname,
THREAD command when the SCOPE(GROUP)
| SYSTEM AUTHID=authid, ROLE
keyword is specified and the IRLM NOTIFY to other
| =role-name
members has returned a bad return code.
| Explanation:
retcode Return code from IRLM on the Notify request.
| This message appears in the output of a DISPLAY
reason Reason code diagnostic information from
| THREAD report when a non-detail display is specified.
IRLM on the Notify request.
| If a trusted context is associated with the thread, this
| message is issued and identifies more specific
DSNV480I V480-DB2 IS PARTICIPANT FOR RRS | information regarding the trusted context.
URID=rrs-urid
| tcname The trusted context name.
Explanation:
| authid The system authorization ID associated with
This message is a detail line that could be displayed | the user in the trusted context.
with a DISPLAY THREAD TYPE(ACTIVE) report when
| role-name
the Recoverable Resource Services Unit of Recovery ID
| The role associated with the user in the trusted
(RRS URID) keyword is specified on the command. The
| context. If not defined for the trusted context,
RRS URID=rrs-urid identifies the RRS URID of the RRS
| this field contains an asterisk.
Unit of Recovery that this thread is a participant in.
The message number and subsystem recognition | Note: This message’s number and subsystem
character are not included in this message. However, | recognition character are not included in the message.
V480 is included in the message text to identify the | However, V485 is included in the message text in order
message. | to identify the message.
System action: | System action:
Command processing continues normally. | Command processing continues.
| use by IBM Software Support. | system threads for the named connection. This message
| is generated when the command that you issued
| This is an informational message.
| requests information about system threads with the
| System action: Processing continues. | given connection name but none currently exist.
| System action:
| DSNV495I SCOPE(GROUP) SUPPRESSED
| Command processing continues.
| DURING RESTART AND SHUTDOWN
| Explanation:
| DSNV500I NO SYSTEM THREADS FOUND
| You issued the -DISPLAY THREAD command during
| Explanation:
| restart or shutdown with SCOPE(GROUP) specified.
| The command will execute locally. | The -DISPLAY THREAD command found did not find
| any system threads that can be displayed.
| System action:
| System action:
| Command processing continues locally.
| Command processing continues.
| DSNV496I ONLY SYSTEM THREAD DATA
| AVAILABLE | DSNV501I COMMAND EXECUTING: command-text
| Explanation: | Explanation:
| You issued the -DISPLAY THREAD command during | The system thread identified in message DSNV404I,
| restart or shutdown, and specified a TYPE other than | which is issued before this message, is currently
| SYSTEM. This message indicates that only system | executing the command specified by the command-text.
| thread information is available during restart and
| shutdown.
| DSNV502I PLOCK ENGINE exit-name EXIT,
| System action: | RMID=service-rmid, FCODE=service-fcode
| optional-text-desc
| Command processing continues.
| Explanation:
| DSNV497I SYSTEM THREADS | The system thread identified in the DSNV404I message
| that is issued before this message, is currently
| Explanation:
| executing the DB2 exit that you specified. The rmid,
| You will receive this message prior to receiving a | fcode, and optional-text-desc provide informational data
| display of system thread information. | that you can use to service DB2.
| Explanation: | Explanation:
| The -DISPLAY THREAD command did not find any | The system thread identified in message DSNV404I,
652 Messages
DSNV505I • DSNV512I
654 Messages
Chapter 18. DSNW messages
Message identifiers that begin with DSNW communicate information about the
instrumentation facility.
Explanation: The specified operand was not one of the valid dump
control statement operands.
An invalid operand was found on the dump control
statement. The operand was not ’SG’, ’LG’, ’SA’, ’AA’, System action:
or ’ALL’. Control returns to AMDPRDMP or IPCS to terminate
System action: the exit.
656 Messages
DSNW016I • DSNW024I
658 Messages
DSNW037I • DSNW041I
660 Messages
DSNW053I • DSNW060I
If intervention is desired, notify the system failed to supply it. If you suspect an error in DB2, refer
programmer. to Part 2 of Utility Guide and Reference for information
on identifying and reporting the problem.
System programmer response:
If intervention is desired, the DB2 subsystem can be
DSNW055I FORMAT ROUTINE UNABLE TO
terminated by either an MVS CANCEL command or a
LOCATE SDWA
-STOP DB2 command. If you suspect an error in DB2,
refer to Part 2 of Utility Guide and Reference for Explanation:
information on identifying and reporting the problem.
The MVS Summary Dump Data Access Service Routine
Problem determination: (IEAVTFRD) was unable to locate the SDWA in the
summary data portion of the SYS1.DUMP data set.
The modules must reside in a DB2 program library
named on the execution procedure used to start a DB2 System action:
subsystem address space.
VRA report generation is terminated and dump format
The named modules prohibit the use of the DB2 dump processing continues.
formatting facility to format SVC dumps that occur
System programmer response:
during the current execution cycle of the DB2
subsystem. The named modules are not required for Take the appropriate action, as indicated in the next
DB2 execution. section. If an error is indicated, use the printout of the
dump for problem documentation.
DSNW053I VRA DIAGNOSTIC INFORMATION Problem determination:
REPORT
The SDWA is placed in the summary data portion of
Explanation: the SYS1.DUMP data set by AMDPRDMP or IPCS. It
indicates either CSA or Local Storage Residency.
All DB2 diagnostic information in the Variable
Recording Area (VRA) at the time of the error is If the SDWA is not in the dump data set, no error is
extracted and displayed in this report. indicated.
The address of the SDWA, the contents of SDWARA,
and SDWARA’s hexadecimal offset into SDWA are also DSNW056I VRA DIAGNOSTIC REPORT
displayed. Individual diagnostic entries are identified COMPLETE
by a hexadecimal VRA ’key’, followed by the length of
the subsequent data. Data fields are displayed in Explanation:
hexadecimal and EBCDIC formats. If you suspect an The VRA Diagnostic Report is done.
error in DB2, refer to Part 2 of Diagnosis Guide and
Reference for information on identifying and reporting System action:
the problem. Dump format processing continues.
System action:
Dump format processing continues. DSNW060I BEGIN SAVE AREA TRACE
Refer to Diagnosis Guide and Reference for information This message identifies the start of the DB2 register
on identifying and reporting the problem. Save Area Trace report which appears in the formatted
section of a DB2 SVC Dump. The save areas for the
current failing agent execution block (EB), and all
DSNW054I NO VRA DATA RECORDED IN SDWA associated Agent EBs, are traced from the point of error
Explanation: and displayed in order of invocation.
The SDWA obtained from the SYS1.DUMP data set The format of this report is as follows:
contained no diagnostic information in the VRA. Save Area Identification
System action: The address and contents of each save area is displayed
VRA report generation is bypassed, dump format and identified by the invoking module.
processing continues. Module-name Service-level-identifier
System programmer response: SA .... WD1 .... HSA .... LSA ....
RET .... EPA .... R0 ....
If an error is indicated, the printout of the dump
R1 .... R2 .... R3 ....
should be used for the problem documentation. If VRA
data is needed, the abending DB2 subcomponent has
662 Messages
DSNW063I • DSNW109I
not contain the address of a valid Agent execution Register save area trace format processing for the
block (EB). current save area chains is terminated. Subsequent save
area processing will vary depending on the specific
R6-contents:
control block or save area that was available, and the
The contents of register 6.
DB2 Agent execution environments at the time of the
System action: error.
save area trace format processing is terminated for the System programmer response:
current Agent EB, and all prior EBs.
Due to the execution structures and environmental
System programmer response: restrictions of selected DB2 and MVS control structures,
some control blocks and save areas associated with
The dump formatter expects the contents of register 6 these execution environments will not be included in
to contain the address of a valid EB. the dump data set.
Problem determination: Problem determination:
Register 6 does not contain the current EB address or a During MVS/RTM recovery processing, IFC Dump
prior EB address. Services attempts to include all control blocks (both
Refer to the abend reason and completion codes DB2 and MVS), and the pertinent DB2 save areas in the
associated with the original error to determine the use dump data set, regardless of the type of error. Control
of register 6 prior to the failure. blocks and save areas associated with the following
address spaces at time of error will be included in the
dump data set:
DSNW063I name (address) ASID (asid) NOT
v Primary, Secondary, and Home address spaces.
FOUND IN DUMP
v DB2 System Services and Database Services address
Explanation: spaces.
During dump formatter processing of the save area
trace report (DSNW060I), a control block or save area DSNW108I UNABLE TO AUTOMATICALLY
was not found in the dump data set. START type TRACE
Since the dump formatter utilizes the DB2 and MVS Explanation:
control blocks defined under the ’name’ field of this
message to locate individual register save areas, System parameters indicated that a DB2 trace should be
subsequent save areas located via the ’named’ control started automatically during DB2 subsystem
block or save area will not be displayed in the report. initialization, but the DB2 subsystem was unable to
start the trace. A nonzero return code was received
name Identifies the name of the control block or save from the -START TRACE command.
area that was not found in the dump data set:
System action:
SA Indicates a Save Area
Subsystem initialization continues.
ASCE DB2 Address Space Control Element
Operator response:
EB DB2 Execution Block
Start the trace via the -START TRACE command after
TCB MVS Task Control Block DB2 subsystem initialization is complete.
RB MVS Request Block
XSB MVS Extended Status Block DSNW109I TRACE INITIALIZATION
PARAMETERS UNAVAILABLE,
PSA MVS Prefix Save Area DEFAULTS ASSUMED
SDWA Explanation:
MVS System Diagnostic Work Area
The trace function was unable to access the trace
STSV MVS SRB Status Save Area initialization parameters defined by the DSN6SYSP
STKE MVS Cross Memory Stack Element macro. Default values as defined by that macro are
assumed for trace parameters.
address
The address of the ’named’ control block or System action:
save area. Subsystem initialization continues.
asid The address space identifier associated with Operator response:
the control block or save area.
Determine if the system parameters module
System action: DSNZPARM is missing or inaccessible. If not,
determine if the CSECT DSN6SYSP is missing. Trace specified. Refer to Command Reference for details about
can be started with the -START TRACE command. valid combinations of keywords and trace types.
Problem determination:
DSNW120I A SPECIFIED keyword VALUE IS
Obtain a copy of the system or terminal log to verify
INVALID FOR type TRACE
command entry.
Explanation:
A trace command has been entered, but a specified DSNW123I csect-name TRACE RECORDING HAS
keyword value is not valid for the trace type requested. BEEN RESUMED ON dest
System action: Explanation:
Processing for the TRACE command is terminated. ’dest’ destination resumes acceptance of trace data after
a failure.
Operator response:
System action:
If a -START TRACE command was entered, specify a
valid destination for the trace. Otherwise, issue a Data recording is resumed.
-DISPLAY TRACE command to determine what traces
are currently active.Refer to Command Reference for
DSNW124I csect-name type TRACE TERMINATED
details about valid destinations.
RC=code RMID=nn
Problem determination:
Explanation:
Obtain a copy of the system or terminal log to verify
During processing ’type’ trace, processing abended due
command entry.
to an error. A trace type of blank indicates all tracing
has stopped. ’RMID’, displayed in decimal, identifies
DSNW121I A SPECIFIED CLASS VALUE IS the resource manager. ’RC’, displayed in hexadecimal,
INVALID FOR type TRACE specifies the return/reason/abend code associated with
the action.
Explanation:
Further collection of the named trace is stopped. If it is
A trace command has been entered, but a specified
necessary to resume collection of the trace, a -START
class value is not valid for the trace type requested.
TRACE command may be issued. However if another
System action: failure is experienced, the problem should be resolved
before starting the trace collection again.
Processing for the TRACE command is terminated.
System action:
Operator response:
Processing for the named trace type is stopped. The
If a -START TRACE command was entered, specify a message is not externalized by the functional recovery
valid class for the trace. Otherwise, issue a -DISPLAY routine, but is outputted whenever a IFC event is
TRACE command to determine what options are driven at a later time. A trace type of blank indicates all
currently active. Refer to Command Reference for details tracing has stopped.
about valid classes.
Operator response:
Problem determination:
If necessary to collect the named trace, issue a -START
Obtain a copy of the system or terminal log to verify TRACE command to resume processing.
command entry.
User response:
DSNW122I THE KEYWORD keyword IS NOT Investigate the reasons for the failure.
VALID FOR type TRACE
Problem determination:
Explanation:
Obtain a copy of the system or terminal log. If a dump
A trace command has been entered, but ’keyword’ is was produced, have it printed. Print a copy of the
not valid for the trace type specified. contents of the SYS1.LOGREC for the time period
involved. Forward these items along with a copy of the
System action: system log to the system programmer.
Processing for the TRACE command is terminated.
Operator response:
Either the named keyword must be omitted from the
command, or a different type of trace must be
664 Messages
DSNW125I • DSNW130I
666 Messages
DSNW138I • DSNW142I
Processing for the -STOP or -DISPLAY TRACE Processing of the trace command is terminated before
command will continue. any trace functions are performed.
Operator response: Operator response:
You may wish to issue an unqualified -DISPLAY Investigate the reason for the problem by doing a
TRACE command to determine all the active trace display trace to analyze the active traces.
entries. If no traces are active then an unqualified
User response:
-DISPLAY TRACE command response message is a
DSNW137I message. Investigate the reason for the failure.
Problem determination:
DSNW138I IFCID ifcid-number IS INVALID
Analyze why all the OPn destinations are active after
Explanation: doing a display trace.
The specified IFCID number is outside the range of
valid IFCID numbers or is an IFCID number which is DSNW141I STORAGE NOT AVAILABLE FOR
not allowed on a trace command as specified in DB2 BUFFER SIZE size K BYTES
Performance Monitoring and Tuning Guide.
Explanation:
System action:
The request could not be processed because storage
Processing of the trace command is terminated before cannot be obtained for the OPn destination storage
any trace functions are performed. buffer.
Operator response: System action:
Investigate the reason for the problem. Processing of the trace command is terminated.
Problem determination: Operator response:
Refer to Command Reference for the range of valid IFCID Investigate the reason for the problem by doing a
numbers. display trace to analyze the active traces.
User response:
DSNW139I AUTHORIZATION FAILURE BECAUSE
authorization-privilege PRIVILEGE Investigate the reason for the failure.
REQUIRED Problem determination:
Explanation: The problem is caused either because one or more prior
The user of the command does not have the required start traces to an OPn destination used all the storage
authorization privilege to execute the command. in the IFC OPn storage pool or because ECSA
contiguous storage was not available. The IFC OPn
System action: storage pool limit is approximately 4 megabytes. When
a trace is stopped the buffer storage is not free. If
Command processing is stopped.
another start trace is issued to the same destination, the
Operator response: storage will be reused. If the requested storage is
greater than the current unassigned buffer, it is free and
Notify the security administrator.
a larger buffer is obtained. If the requested storage is
User response: less than the current unassigned buffer, the buffer is
reused. Fragmentation can occur if either application
Notify the security administrator. programs or an operator specify numerous start
Problem determination: commands for varying size buffers.
668 Messages
DSNW150I • DSNW157I
| Explanation:
| DSNW164I PACKAGE COLLECTION ID:
| This message is issued as part of the -DISPLAY TRACE | exclude-keywords
| output when DETAIL(2) is specified. This message will
| appear between a DSNW152I and DSNW153I message
| Explanation:
| if the trace number specified in the DSNW125I has a | This message is issued as part of the -DISPLAY TRACE
| userid-qualification. | output when DETAIL(2) is specified. This message will
| appear between a DSNW152I and DSNW153I message
| DSNW159I APPLICATION/TRANSACTION
| if the trace number specified in the DSNW125I message
| NAME: application/transaction-name-
| has exclude-keywords specified.
| qualification
| Explanation:
| DSNW165I RMID: rmid-qualifications
670 Messages
DSNW170I • DSNW179I
| entered that would result in greater than 16 appear between a DSNW152I and DSNW153I message
| qualifications for a trace entry. if the trace number specified in the DSNW125I message
has an XAPPNAME qualification.
| System action:
| Processing of the command is terminated. DSNW175I EXCLUDE WORKSTATION: xwrkstn
| Operator response: qual1,xwrkstn qual2,...,xwrkstn qual8
Explanation:
DSNW176I EXCLUDE PACKAGE LOC: xpkgloc
This message is issued as a part of the -DISPLAY qual1,xpkgloc qual2,...,xpkgloc qual8
TRACE output when DETAIL(2) is specified. This
message will appear between a DSNW152I and Explanation:
dSNW153I message if the trace number specified in the
This message is issued as part of the -DISPLAY TRACE
DSNW125I message has an XPLAN qualification.
output when DETAIL(2) is specified. This message will
appear between a DSNW152I and DSNW153I message
DSNW171I EXCLUDE AUTHID: xauthid if the trace number specified in the DSNW125I message
qual1,xauthid qual2,...,authid qual8 has an XPKGLOC qualification.
Explanation:
DSNW177I EXCLUDE PACKAGE COLLID: xpkgcol
This message is issued as a part of the -DISPLAY qual1,xpkgcol qual2,...,xpkgcol qual8
TRACE output when DETAIL(2) is specified. This
message will appear between messages DSNW152I and Explanation:
DSNW153I if the trace number specified in the
When you specify DETAIL(2), this message is issued as
DSNW125I message has an XAUTHID qualification.
part of the -DISPLAY TRACE output. This message will
appear between a DSNW152I and DSNW153I message
DSNW172I EXCLUDE LOCATION: xloc qual1,xloc if the trace number specified in the DSNW125I message
qual2,...,xloc qual8 has an XPKGCOL qualification.
Explanation:
DSNW178I EXCLUDE PACKAGE PROGNAME:
When you specify a DETAIL(2), this message is issued xpkgprog qual1,xpkgprog qual2,...,xpkgprog
as part of the -DISPLAY TRACE output. This message qual8
will appear between a DSNW152I and DSNW153I
message if the trace number specified in the DSNW125I Explanation:
message has an XLOC qualification.
When you specify DETAIL(2), this message is issued as
part of the -DISPLAY TRACE output. This message will
DSNW173I EXCLUDE USERID: xuserid qual1,xuserid appear between a DSNW152I and DSNW153I message
qual2,...,xuserid qual8 if the trace number specified in the DSNW125I message
has an XPKGPROG qualification.
Explanation:
This message is issued as part of the -DISPLAY TRACE DSNW179I EXCLUDE CONNECTION ID: xconnid
output when DETAIL(2) is specified. This message will qual1,xconnid qual2,...,xconnid qual8
appear between a DSNW152I and DSNW153I message
if the trace number specified in the DSNW125I has an Explanation:
XUSERID qualification.
When you specify DETAIL(2), this message is issued as
part of the -DISPLAY TRACE output. This message will
DSNW174I EXCLUDE APP/TXACT NAME: appear between a DSNW152I and DSNW153I message
xappname qual1,xappname qual2,...,xappname if the trace number specified in the DSNW125I message
qual8 has an XCONNID qualification.
Explanation:
When you specify DETAIL(2), this message is issued as
part of the -DISPLAY TRACE output. This message will
672 Messages
Chapter 19. DSNX messages
Message identifiers that begin with DSNX communicate information about the
relational data system.
This statement is bound dynamically on each execution Ensure that the required index on the indicated table in
of the statement. For better performance, rebind the the partitioned table space is created before the
application program after the appropriate authority is statement is executed. Otherwise, execution of this
granted to the invoker of the BIND subcommand statement results in an error. This statement is bound
against this application plan. dynamically on each execution of the statement. For
better performance, rebind the application program
after the required index is created.
DSNX102I bind-type SQL WARNING USING
authorization-id AUTHORITY
PLAN=plan-id DBRM=dbrm name DSNX103I bind-type SQL WARNING USING
STATEMENT=statement number THE authorization-id AUTHORITY
REQUIRED INDEX HAS NOT BEEN PLAN=plan-id DBRM=dbrm name
CREATED ON TABLE table name IN STATEMENT=statement number BIND
PARTITIONED TABLESPACE table ISOLATION LEVEL RR CONFLICTS
space name WITH TABLESPACE LOCKSIZE PAGE
OR LOCKSIZE ROW
Explanation:
Explanation:
There was an attempt to reference the table in the table
space (both specified in the message) when the Because of the possible inconsistency between the
required index was not yet created. isolation level of the application and the LOCKSIZE of
the table space, table space locking is used to protect
bind-type the integrity of the application.
Type of BIND subcommand that caused the
warning: BIND or REBIND bind-type
Type of BIND subcommand that caused the
authorization-id warning: BIND or REBIND
Authorization ID used during the bind
process. For a BIND subcommand, it is the | authorization-id
authorization ID of the plan owner. For a | Authorization ID used during the bind
REBIND subcommand, it is the authorization | process. For a BIND subcommand, it is the
ID of the owner specified by the subcommand, | authorization ID of the plan owner. For a
or the latest owner of the plan. If this is a | REBIND subcommand, it is the authorization
remote operation, and the OWNER was not | ID of the owner specified by the subcommand,
specified in the subcommand, then REMOTE | or the latest owner of the plan. If this is a
OWNER is output. Attention: If you are using | remote operation, and the OWNER was not
a trusted context, the token auth-id might | specified in the subcommand, then REMOTE
return a role instead of an authorization ID. A | OWNER is output.
role is returned if a role was in effect and the | Attention: If you are using a trusted context,
authorization checking is performed against | the token auth-id might return a role instead of
674 Messages
DSNX104I • DSNX105I
| an authorization ID. A role is returned if a role | a trusted context, the token auth-id might
| was in effect and the authorization checking is | return a role instead of an authorization ID. A
| performed against the role, rather than the | role is returned if a role was in effect and the
| authorization ID of the session, when the | authorization checking is performed against
| condition was encountered. Otherwise an | the role, rather than the authorization ID of
| authorization ID is returned. A role is returned | the session, when the condition was
| in the following format as a single token: | encountered. Otherwise an authorization ID is
| v ROLE: role-name | returned. A role is returned in the following
| format as a single token:
plan-id Name of the application plan specified in the
| v ROLE: role-name
BIND subcommand. If the application plan is
not specified, this field is blank. plan-id Name of the application plan specified in the
BIND subcommand. If the application plan is
dbrm name
not specified, this field is blank.
Name of the DBRM that contains the reference
to the indicated table. dbrm name
Name of the DBRM that contains the reference
statement number
to the indicated table.
Statement number of the SQL statement
referencing the indicated table. statement number
Statement number of the SQL statement
System action:
referencing the indicated table.
A valid plan is created if no errors are detected. Table
System action:
space locking is used. RR isolation level is preserved.
A valid plan is created if no errors are detected.
System programmer response:
If you do not want table space locking, use isolation
DSNX105I bind-type SQL WARNING USING
level UR, CS or RS.
authorization-id AUTHORITY
PLAN=plan-id DBRM=dbrm name
DSNX104I bind-type SQL WARNING USING STATEMENT=statement number
authorization-id AUTHORITY SQLCODE=sqlcode SQLSTATE=sqlstate
PLAN=plan-id DBRM=dbrm name TOKENS=token list
STATEMENT=statement number THE
Explanation:
RESULT OF DECIMAL
MULTIPLICATION MAY CAUSE An SQL warning code was generated while processing
OVERFLOW an SQL statement.
Explanation: bind-type
The type of subcommand that caused the
An arithmetic expression contains a decimal
warning: BIND or REBIND
multiplication that might cause an overflow condition
when the statement is executed. The problem can be | authorization-id
corrected by restructuring the arithmetic expression so | Indicates the authorization ID used during the
that decimal multiplication precedes decimal division | bind process. For a BIND subcommand, it is
or by changing the precision and scale of the operands | the authorization ID of the plan owner. For a
in the arithmetic expression. Refer to chapter 2 of SQL | REBIND subcommand, it is the authorization
Reference for the precision and scale of the decimal | ID of the owner specified by the subcommand,
multiplication and division results. | or the latest owner of the plan. If this is a
| remote operation, and the OWNER was not
bind-type
| specified in the subcommand, then REMOTE
Type of BIND subcommand that caused the
| OWNER is output.
warning: BIND or REBIND
| Attention: If you are using a trusted context,
| authorization-id
| the token auth-id might return a role instead of
| Authorization ID used during the bind
| an authorization ID. A role is returned if a role
| process. For a BIND subcommand, it is the
| was in effect and the authorization checking is
| authorization ID of the plan owner. For a
| performed against the role, rather than the
| REBIND subcommand, it is the authorization
| authorization ID of the session, when the
| ID of the owner specified by the subcommand,
| condition was encountered. Otherwise an
| or the latest owner of the plan. If this is a
| authorization ID is returned. A role is returned
| remote operation, and the OWNER was not
| in the following format as a single token:
| specified in the subcommand, then REMOTE
| OWNER is output. Attention: If you are using | v ROLE: role-name
sqlstate Explanation:
A common code which identifies the particular
An error has been detected while processing an SQL
SQL warning condition.
statement.
dbrm name
bind-type BIND | REBIND
Name of the DBRM that contains the problem.
indicates type of BIND subcommand that
statement number caused the error.
Statement number of the SQL statement
| authorization-id
containing the problem.
| indicates the authorization ID used during the
token list | bind process. For a BIND subcommand,
Sequence of one or more tokens separated by | indicates the authorization ID of the plan
blanks. Refer to Codes for an explanation of | owner. For a REBIND subcommand, indicates
tokens. | the authorization ID of the owner specified by
| the subcommand, or the latest owner of the
System action: | plan.
A valid plan is created if no errors are detected. | Attention: If you are using a trusted context,
System programmer response: | the token auth-id might return a role instead of
| an authorization ID. A role is returned if a role
Refer to Codes for the particular abend reason code | was in effect and the authorization checking is
issued. If the reason code is negative, this statement is | performed against the role, rather than the
bound dynamically on each execution of the statement. | authorization ID of the session, when the
For better performance, rebind the application program | condition was encountered. Otherwise an
after correcting this statement or after the required | authorization ID is returned. A role is returned
object is created or altered. | in the following format as a single token:
| v ROLE: role-name
DSNX106I ATTEMPTED REBIND OF PACKAGE
plan-id Name of the application plan specified in the
pkg-id RESULTED IN A TOTAL OF
BIND subcommand. Blank if the application
number ERRORS
plan is not specified.
Explanation:
sqlcode
Errors have been detected during the remote REBIND A product specific code which identifies the
process. Only the first REBIND error will produce a particular SQL error detected. The value and
specific message. Additional errors will simply be semantics of the code are the same as the SQL
totaled, and the number will be returned to the user. return codes documented in Codes.
pkg-id Name of the package specified in the sqlstate
subcommand. A common code which identifies the particular
SQL error detected.
number
Total number of errors in the remote REBIND dbrm name
Name of the DBRM that contains the error.
System action:
statement-number
The package was not rebound.
Statement number containing the SQL error.
System programmer response:
token list
See previously output message to determine the initial Optional sequence of one or more tokens
error that caused the subcommand to be terminated separated by blanks. These are the tokens that
unsuccessfully. are to be substituted into the text of the error
code as described at the beginning of Codes.
csect Name of the CSECT detecting the problem.
676 Messages
DSNX201I • DSNX203I
rds code
DSNX202I INVALID AMODE ATTRIBUTE
Unique code that identifies the location within
FOUND FOR DATE OR TIME
the CSECT when the problem is detected.
INSTALLATION REPLACEABLE EXIT
System action: ROUTINE module-name
System programmer response: During DB2 startup, the Relational Data System
subcomponent loads the Date (DSNXVDTX) and Time
Correct the SQL errors in the application program (DSNXVTMX) exit routines. These routines must have
associated with the indicated DBRM. Precompile the the link-edited attributes AMODE(31) and
application program, and reinvoke the BIND RMODE(ANY). The module listed in the message
subcommand. ’module-name’ did not have the correct addressing
attributes. If the date and time LOCAL installation
DSNX201I bind-type SQL ERROR USING option is specified, DB2 will be unable to execute the
authorization-id AUTHORITY date and time functions required by the exit routine
PLAN=plan-id DBRM=dbrm name that failed to load.
STATEMENT=statement number SQL System action:
CODE=sql code TOKENS=token list;
bind-type DBRM ERROR USING The load module is deleted. DB2 startup will continue.
authorization-id AUTHORITY
Operator response:
PLAN=plan-id DBRM dbrm name IS IN
AN INCONSISTENT STATE Notify the system programmer.
Explanation: System programmer response:
The content of a DBRM has been modified after the When DB2 is stopped, the date and time exit routine
precompilation process. must be link-edited again with the correct AMODE and
RMODE control statements. Refer to Appendix B of
bind-type
Administration Guide for more information on exit
Type of BIND subcommand that caused the
routines.
warning: BIND, REBIND
| authorization-id DSNX203I LOAD OF THE DATE OR TIME
| Authorization ID of the plan owner. Attention:
INSTALLATION REPLACEABLE EXIT
| If you are using a trusted context, the token
ROUTINE module-name FAILED WITH
| auth-id might return a role instead of an
MVS ABEND CODE = abend-code
| authorization ID. A role is returned if a role
REASON CODE = reason-code DB2
| was in effect and the authorization checking is
STARTUP WILL CONTINUE
| performed against the role, rather than the
| authorization ID of the session, when the Explanation:
| condition was encountered. The role is
During DB2 startup, the Relational Data System
| returned in the following format as a single
subcomponent loads the date (DSNXVDTX) and time
| token: ROLE: role-name.
(DSNXVTMX) exit routines. During the load of EXIT
plan-id Name of the application plan specified in the ROUTINE ’module-name’, MVS issued the abend code
BIND or REBIND subcommand (or blank if and reason code that would cause abnormal
the application plan is not specified). termination of the task, but the abend was suppressed.
If the date and time LOCAL option is specified, DB2
dbrm name
will be unable to execute the date and time functions
Name of the DBRM that is in error.
required by the exit routine that failed to load.
System action:
System action:
No application plan is created.
The load failed. DB2 startup will continue.
System programmer response:
Operator response:
Precompile the application program associated with the
Notify the system programmer.
indicated DBRM. Reinvoke the BIND subcommand.
System programmer response:
When DB2 is stopped, the date and time exit routine
must be link-edited correctly. For more information,
refer to Appendix B of Administration Guide.
678 Messages
DSNX207I • DSNX209E
680 Messages
DSNX211I • DSNX230I
routine will continue running until it | DB2 startup continues but the encryption/decryption
exceeds the abend tolerance limit. In | services are not available.
addition, the following will occur:
| User response:
– If the initialization reason_code was 16,
DB2 terminates. | Ensure that the ICSF SCSFMOD0 load module is in the
| LINKLIST for the z/OS system.
– If the initialization reason_code was not 16,
DB2 performs all subsequent
authorization checks. | DSNX230I A RESOURCE IS UNAVAILABLE
| WHEN TRYING TO BUILD THE
Operator response:
| TRUSTED CONTEXT CACHE
Notify the system programmer. | REASON=reason-code TYPE OF
| RESOURCE=resource-type RESOURCE
System programmer response:
| NAME=resource-name
Refer to the documentation of the access control
| Explanation:
authorization exit routine for an explanation of
reason_code. Correct the situation that caused the reason | During DB2 startup or at the first attempt to create a
code. | connection or at a commit related to the TRUSTED
| CONTEXT DDL statements, an error is encountered
If this message was issued because of an abend during
| while building the trusted context cache and accessing
exit routine processing, then search the system log to
| the catalog.
determine its cause and correct the situation.
| reason-code
If abend code 00E70016 was issued indicating that the
| The reason code returned by Data Manager
version of the exit routine is incompatible with this
| during DB2 catalog access.
version of DB2, install the correct version of the exit
routine. Refer to the documentation in the | resource-type
Administration Guide for information on the access | The resource type returned by Data Manager
control authorization exit. For information on the RACF | during DB2 catalog access.
access control module shipped with DB2 refer to the
| resource-name
RACF Access Control Module Guide.
| The resource name returned by Data Manager
If DB2 terminated, restart DB2. If DB2 did not | during DB2 catalog access.
terminate, you need to restart DB2 to reactivate the
exit. | An attempt to rebuild the trusted context cache will be
| made at the next DB2 startup, or during commit for the
Problem determination:
| TRUSTED CONTEXT related DDL statements or
Since the access control authorization exit routine is | attempt to establish a connection.
external to DB2, refer to the documentation of the exit
| System action:
routine for an explanation of return_code and
reason_code and a resolution to the problem. | The trusted context cache is not built and subsequent
If this message was issued because of an abend during
| connections are not trusted connections, until the
exit routine processing, then determine the cause of the
| problem is resolved. DB2 startup continues if the
abend from messages in the system log and address it.
| console message is issued during the startup. If the
Look for system messages that occurred at
| message is issued during a remote connect attempt to
approximately the same time to find more information
| use the trusted connection, SQLCODE +20360 is
about the abend.
| returned. If the message is issued when DSN ASUSER
| is specified, DSNE137I message is returned.
| abend messages in the console. If you suspect an error v Listing of SYS1.LOGREC data set, obtained by
| in DB2, refer to Part 2 of Diagnosis Guide and Reference executing IFCEREP1.
| for information on identifying and reporting the
| problem.
DSNX906I csect-name PROCEDURE OR
FUNCTION name TERMINATED
| DSNX231I THE TRUSTED CONTEXT CACHE ABNORMALLY. THE PROCEDURE
| BUILD PROCESS COMPLETED HAS BEEN STOPPED. ASID= asid
| SUCCESSFULLY WLM_ENV= wlmenv
| Explanation: Explanation:
| The trusted context cache is built successfully with A stored procedure terminated abnormally while
| trusted context entries in the DB2 catalog. DB2 uses the attempting to satisfy an SQL CALL statement for an
| trusted context cache to determine if a connection is SQL application.
| trusted or not.
name The name of the stored procedure or function
| System action: that terminated abnormally
| DB2 is ready for trusted context connections. asid The MVS ASID of the address space where the
stored procedure executed.
DSNX905I csect-name PROCEDURE OR wlmenv The name of the WLM application
FUNCTION name TERMINATED environment where the stored procedure
ABNORMALLY ASID= asid executed. If it executed in the DB2-established
WLM_ENV= wlmenv stored procedures address space, this field will
contain blanks.
Explanation:
System action:
A stored procedure terminated abnormally while
attempting to satisfy an SQL CALL statement for an The SQL CALL statement fails, and the SQL application
SQL application. is forced to roll back.
name The name of the stored procedure or function The abnormal termination count for procedure procname
that terminated abnormally. was reached. The procedure is stopped and further
requests for the procedure are rejected.
asid The MVS ASID of the address space where the
stored procedure executed. System programmer response:
wlmenv The name of the WLM application Correct the cause of the abnormal termination. If the
environment where the stored procedure correction requires the stored procedure to be
executed. If it executed in the DB2-established linkedited again, then it might be necessary to cause
stored procedures address space, this field will the corrected MVS load module to be reloaded.
contain blanks.
If it was run in a WLM-established stored procedures
System action: address space, issue the MVS VARY
WLM,APPLENV=name,REFRESH command.
The SQL CALL statement fails, and the SQL application
is forced to roll back. After the appropriate command has been issued to
refresh the stored procedure load module, use the
System programmer response:
-START PROCEDURE command to activate the stored
Correct the cause of the abnormal termination. If the procedure.
correction requires the stored procedure to be
Problem determination:
linkedited again, then it might be necessary to cause
the corrected MVS load module to be reloaded. Collect the following diagnostic items:
If it was run in a WLM-established stored procedures v Console output from the system on which the job
address space, issue the MVS VARY was run, and a listing of the SYSLOG data set for the
WLM,APPLENV=name,REFRESH command. period of time spanning the failure.
v SYSABEND, SYSUDUMP, or SYSMDUMP output.
Problem determination:
v Listing of SYS1.LOGREC data set, obtained by
Collect the following diagnostic items: executing IFCEREP1.
v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
v SYSABEND, SYSUDUMP, or SYSMDUMP output.
682 Messages
DSNX908I • DSNX940I
If the stored procedure is looping, correct the stored System programmer response:
procedure.
Use only WLM-managed stored procedures in V9. Do
If the stored procedure is performing correctly, increase not attempt to start an address space referencing
the ASUTIME value in the CREATE PROCEDURES DSNX9STP.
row associated with the stored procedure.
Problem determination: DSNX940I csect-name - DISPLAY PROCEDURE
REPORT FOLLOWS-
Collect the following diagnostic items:
v Console output from the system on which the job Explanation:
was run, and a listing of the SYSLOG data set for the This message is the title for the report output from the
period of time spanning the failure. DISPLAY PROCEDURE command. It precedes
v SYSABEND, SYSUDUMP, or SYSMDUMP output. messages DSNX941I and DSNX942I. Message
v Listing of SYS1.LOGREC data set, obtained by DSNX943I might also be displayed. The final message
executing IFCEREP1. for the report is DSNX945I.
System action:
The DISPLAY PROCEDURE command processing
continues.
684 Messages
DSNX943I • DSNX955I
DSNX943I PROCEDURES begin - end STOP (act) DSNX947I csect-name STOP PROCEDURE
SUCCESSFUL FOR token
Explanation:
Explanation:
This message indicates a STOP PROCEDURE command
was issued with an invalid procedure name, causing a The STOP PROCEDURE command completed
range of procedure names to be stopped. This message successfully.
follows the DSNX940I, DSNX941I, and any DSNX942I
token The procedure name supplied on the STOP
messages.
PROCEDURE command
begin The first procedure name in the range of
System action:
procedure names that are currently stopped
The STOP PROCEDURE command processing
end The last procedure name in the range of
continues.
procedure names that are currently stopped
act The action provided on the STOP
DSNX950I csect-name PROCEDURE HAS NOT
PROCEDURE command
BEEN ACCESSED OR IS NOT
System action: DEFINED
The DISPLAY PROCEDURE command processing Explanation:
continues.
The routine name supplied on the DISPLAY
PROCEDURE command either does not exist or has not
DSNX944I csect-name THE STORED PROCEDURE yet been accessed since DB2 started. The specific
FUNCTION IS NOT AVAILABLE procedure name might not be present in the
SYSIBM.SYSROUTINES catalog table.
| Explanation:
System action:
| This message is returned if stored procedure function is
| invoked when DB2 is started in ACCESS(MAINT) or Processing continues for any additional procedure
| RESTART LIGHT mode. names supplied on the command.
System action:
DSNX951I csect-name A STORED PROCEDURE
If a START, STOP, or DISPLAY PROCEDURE command
CANNOT ISSUE START/STOP
is in progress, the command terminates.
PROCEDURE COMMANDS
Explanation:
DSNX945I DISPLAY PROCEDURE REPORT
COMPLETE A stored procedure attempted to issue the START or
STOP PROCEDURE command. This is not allowed
Explanation:
because the START and STOP PROCEDURE commands
The output from the DISPLAY PROCEDURE command might cause the stored procedures address space tasks
is complete. This message follows the DSNX940I, to terminate.
DSNX941I, and any DSNX942I messages.
System action:
System action:
The START or STOP PROCEDURE command is
The DISPLAY PROCEDURE command processing rejected.
continues.
DSNX955I
DSNX946I csect-name START PROCEDURE
Explanation:
SUCCESSFUL FOR token
A blank line that appears in the DISPLAY
Explanation:
PROCEDURE or DISPLAY FUNCTION command.
The START PROCEDURE command completed
System action:
successfully.
The DISPLAY command processing continues.
token The procedure name supplied on the START
PROCEDURE command.
The START, STOP, or DISPLAY command continues. The address space attempting to process stored
procedures or functions terminates.
System programmer response: v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
Reissue the -DISPLAY PROCEDURE or -DISPLAY period of time spanning the failure.
FUNCTION SPECIFIC command, specifying a smaller
number of routines. This can be done by specifying a
list of routines, a schema qualifier, or a partial routine DSNX961I csect-name ATTEMPT TO PERFORM
name in the DISPLAY command rather than the default OPERATION operation FAILED FOR
(*.*). Alternatively, the command can be reissued from ROUTINE routine-name SSN=ssn
the DB2I Commands panel or from a batch job rather PROC=jclproc ASID=asid
than from the MVS console. CLASS=class-name METHOD=method-
name ERROR INFO=error-information
686 Messages
DSNX961I
| operation | CreateDebugJVM
The operation that failed. The following list | This operation indicates that the JVM could not be
contains the operations that could have failed: | created in debug mode. Debugging of Java stored
v CallStaticMethod | procedures can only be performed on routines
| running in a WLM-managed stored procedure
| v CreateDebugJVM
| address space whose NUMTCB value is 1.
v CreateJavaVM
CreateJavaVM
| v DEBUG_ROUTINE
| This operation indicates that the JVM could not be
v DestroyJavaVM | created. You must have the IBM Developer Kit for
v FindClass | OS/390, Java 2 Technology Edition, and the
v INTERNAL_ERROR | JAVA_HOME environmental variable in your
| JAVAENV dataset must reference its home
v JDBC Reset | directory.
| routine-name | DEBUG_ROUTINE
| The name of the routine that was invoked. | This operation indicates that the WLM-managed
ssn The name of the DB2 subsystem to which the | stored procedure address space could not establish
stored procedures address space is connected. | or maintain proper communication with a debug
| session. This message’s error-information describes
jclproc | how the operation failed and provides an
The name of the JCL procedure that was used to | associated reason code. For all cases except for
start the stored procedures address space. | ″ReservePort Failure: NO AVAILABLE PORT″
asid | record the information in this message’s
| The ASID of the address space in which operation | error-information and contact your IBM Support
| was performed. | Center for assistance. In the case of ″ReservePort
| Failure: NO AVAILABLE PORT″ either wait for the
class-name | simultaneous debugging activity to decrease or
The name of the class that contains the Java™ | increase the number of ports available to the
method to be invoked. | WLM-managed stored procedure address space.
method-name DestroyJavaVM
The name of the Java method to be invoked. | This operation indicates that the JVM could not be
error-information | destroyed without error.
The error information provided for this error. FindClass
System action: | This operation indicates that either a required
| system-provided class could not be found or an
| Either the CALL statement fails, or, in the case of | error occurred in accessing a system- or
| operations DEBUG_ROUTINE and CreateDebugJVM, | user-provided class. You need to take a specific
| the CALL statement executes but the Java stored | action based on what type of class could not be
| procedure cannot be debugged. | found or accessed:
System programmer response: | v For a system-provided class, check the settings
| for JAVA_HOME, and JCC_HOME in the
| Use the value of operation and this message’s | JAVAENV DD statement in the stored
| error-information to correct the problem. If the | procedures address space start-up procedure,
| WLM-managed stored procedure address space is | and ensure that they are set correctly.
| running with a //JSPDEBUG DD card, then, for further
| information about this error, check its output (typically,
| v For a user-provided class, check the settings for
| the WLM-managed stored procedure address space
| TMSUFFIX and CLASSPATH in the JAVAENV
| output) for information.
| DD statement in the stored procedures address
| space start-up procedure, and check the routine’s
Also, check the HFS directory identified as the home | use of an installed JAR. The JVM runtime loads
directory for the ID associated with the WLM-managed | all classes that are referenced in the identified
stored procedure address space for any dumps that the | class. Ensure that all referenced, user-provided,
JVM could have taken. Check either the /tmp/java | classes are in the CLASSPATH or TMSUFFIX, or
directory, or if WORK_DIR is specified then its | in a referenced installed JAR.
directory, for information that could have been written
INTERNAL_ERROR
to file server_stderr.txt.
| This operation indicates that an internal error has
CallStaticMethod | occurred. Record the following information and
| This operation indicates that an exception has taken | contact your IBM Support Center for assistance:
| place that was not a Java SQLException. | v Any information reported in this message’s
| error-information
688 Messages
DSNX967I • DSNX968I
Problem determination:
DSNX968I csect-name STORED PROCEDURE
Collect the following diagnostic items: ADDRESS SPACE IS UNABLE TO
v Console output from the system on which the job CONNECT TO WLM BECAUSE
was run, and a listing of the SYSLOG data set for the WLM_ENV = wlmenv IS STOPPED OR
period of time spanning the failure. QUIESCED
v SYSABEND, SYSUDUMP, or SYSMDUMP output. Explanation:
A DB2 stored procedures address space could not
DSNX967I csect-name ATTEMPT TO PERFORM connect to the Work Load Manager services of MVS
WLM FUNCTION func FAILED WITH because the WLM application environment was in a
WLM RC= rc RSN= rsn SSN= ssn stopped or quiesced state.
PROC= jclproc ASID= asid WLM_ENV=
wlmenv wlmenv The name of the WLM application
690 Messages
DSNX971I • DSNX978I
have waited for this function to be scheduled, token The function name supplied on the STOP
since the last START SPECIFIC FUNCTION FUNCTION SPECIFIC command.
command was issued for this function.
System action:
TIMEOUT
The STOP FUNCTION SPECIFIC command processing
The number of times an SQL statement timed
continues.
out while waiting for a function to be
scheduled since the last START SPECIFIC
FUNCTION command was issued for this DSNX975I csect-name - DISPLAY FUNCTION
function. SPECIFIC REPORT FOLLOWS-
FAIL The Number of times this function has Explanation:
abended since it was last started.
This message is the title for the report output from the
WLM_ENV DISPLAY FUNCTION SPECIFIC command. It precedes
The MVS Workload Manager environment messages DSNX969I and DSNX970I. Message
name for this function. DSNX971I might also be displayed. The final message
for the report is DSNX972I.
System action:
System action:
The DISPLAY SPECIFIC FUNCTION command
processing continues. The DISPLAY FUNCTION SPECIFIC command
processing continues.
DSNX971I FUNCTIONS begin - end STOP (act)
DSNX977I csect-name FUNCTION HAS NOT BEEN
Explanation:
ACCESSED OR IS NOT DEFINED
This message indicates a STOP SPECIFIC FUNCTION
Explanation:
command was issued with an asterisk (’*’) in the
function name, causing a range of function names to be The routine name supplied on the DISPLAY
stopped. This message follows the DSNX975I, PROCEDURE command either does not exist or has not
DSNX969I, and any DSNX970I messages. yet been accessed since DB2 started. The specific
function name might not be present in the
begin The first function name in the range of
SYSIBM.SYSROUTINES catalog table.
function names that are currently stopped
System action:
end The last function name in the range of
function names that are currently stopped Processing continues for any additional function names
supplied on the command.
act The action provided on the STOP SPECIFIC
FUNCTION command
DSNX978I DISPLAY TERMINATED DUE TO
System action:
INSUFFICIENT MESSAGE SPACE
The DISPLAY SPECIFIC FUNCTION command
Explanation:
processing continues.
The DISPLAY PROCEDURE command could not obtain
storage for additional messages. This should only
DSNX972I DISPLAY FUNCTION SPECIFIC
happen for a particularly long display request, such as
REPORT COMPLETE
one requesting all stored procedures that have been
Explanation: accessed by DB2 applications since DB2 was started.
The output from the DISPLAY FUNCTION SPECIFIC System action:
command is complete. This message follows DSNX975I,
The display is truncated.
DSN969I, and any DSNX970I messages.
System programmer response:
System action:
Reissue the -DISPLAY PROCEDURE command, and
The DISPLAY FUNCTION SPECIFIC command
specify a smaller number of procedures. This can be
processing continues.
done by specifying a partial procedure name in the
DISPLAY PROCEDURE command rather than the
DSNX974I csect-name STOP FUNCTION SPECIFIC default (*).
SUCESSFUL FOR token
Explanation:
The function name supplied on the STOP FUNCTION
SPECIFIC command completed successfully.
The DB2 stored procedures address space received an Correct the JCL parameter used to invoke the DB2
invalid value in the JCL parameter used to start the stored procedure address space.
address space. If MVS WLM is used to establish the stored procedure
parm The JCL parameter is specified incorrectly. address space, the MVS VARY
Possible values are: WLM,APPLENV=wlmenv,RESUME command might be
required to resume the WLM application environment
SUBSYS (wlmenv) associated with the stored procedures address
This parameter can be invalid for the space.
following reasons:
v The SUBSYS parameter is null. DSNX982I csect-neme ATTEMPT TO PERFORM
v The SUBSYS parameter is too long. RRS ATTACH FUNCTION func FAILED
v The SUBSYS parameter contained WITH RRS ATTACH RC= rc RSN= rsn
an invalid character. SSN= ssn PROC = jclproc ASID= asid
WLM_ENV= wlmenv
NUMTCB
This parameter can be invalid for the Explanation:
following reasons: A WLM-established stored procedures address space
v A comma was not present in the was unable to perform an RRS attach operation
parameter list to separate the required to communicate with DB2.
692 Messages
DSNX983I • DSNX986I
func The RRS attach function that failed. Possible Correct the DB2 library name in the STEPLIB for the
values are: JCL proc for the stored procedures address space. Make
v SPAS_ID the library name the same as the library name used for
the DB2 subsystem address spaces. If you suspect an
v SPAS_INIT_SP
error in DB2, refer to Part 2 of Diagnosis Guide and
v SPAS_TERM_SP Reference for information on identifying and reporting
ssn The name of the DB2 subsystem involved with the problem.
the RRS attach function. Problem determination:
jclproc The name of the JCL PROC used to start the Collect the following diagnostic items:
stored procedures address space.
v Console output from the system on which the job
asid The MVS ASID of the address space where the was run, and a listing of the SYSLOG data set for the
function was attempted. period of time spanning the failure.
wlmenv The name of the WLM application v SYSABEND, SYSUDUMP, or SYSMDUMP output.
environment where the function was v Listing of SYS1.LOGREC data set, obtained by
attempted. executing IFCEREP1.
System action:
DSNX984I csect-name ALL FUNCTIONS STARTED
The stored procedures service task that encountered the FOR THIS SCHEMA.
error terminates. If this is the last service task in that
address space, then that address space terminates. Explanation:
System programmer response: All functions are started for the schema listed in the
preceding DSNX956I message. This message is issued
If you suspect an error in DB2, refer to Part 2 of only when STOP FUNCTION SPECIFIC(*.*) was in
Diagnosis Guide and Reference for information on effect.
identifying and reporting the problem.
System action:
Problem determination:
The DISPLAY SPECIFIC FUNCTION command
Collect the following diagnostic items: processing continues.
v Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure. DSNX985I csect-name ALL PROCEDURES
STARTED FOR THIS SCHEMA.
v SYSABEND, SYSUDUMP, or SYSMDUMP output.
v Listing of SYS1.LOGREC data set, obtained by Explanation:
executing IFCEREP1. All procedures are started for the schema listed in the
preceding DSNX956I message. This message is issued
DSNX983I csect-neme DB2 STORED PROCEDURE only when a STOP PROCEDURE(*.*) was in effect.
SUPPORT CODE AND SUBSYSTEM System action:
CODE ARE NOT AT THE SAME
LEVEL SSN= ssn PROC = jclproc The DISPLAY PROCEDURE command processing
continues.
Explanation:
A DB2 stored procedures address space could not DSNX986I ATTEMPT TO func FAILED WITH RV =
connect to the DB2 subsystem. This occurred because rv RC = rc RSN = rsn SSN = ssn PROC =
the DB2 code in the stored procedures address space jclproc
was not at the same release level as the code in the
DB2 subsystem. Explanation:
ssn The name of the DB2 subsystem that the A WLM-established stored procedures address space
stored procedure address space was was unable to register itself to z/OS UNIX System
attempting to connect with. Services. z/OS UNIX System Services are not available
to stored procedures running in the address space.
jclproc The name of the JCL PROC used to start the
stored procedures address space. func The dub setting used by z/OS UNIX System
Services BPX1SDD callable service. This can be
System action: DUBPROCESS or DUBTHREAD.
The stored procedures address space terminates. rv The return value given by z/OS UNIX System
System programmer response: Services BPX1SDD callable service.
rc The return code given by z/OS UNIX System The DISPLAY SPECIFIC FUNCTION command
Services BPX1SDD callable service. processing continues.
rsn The reason code given by z/OS UNIX System
Services BPX1SDD callable service. DSNX989I csect-name ALL OTHER PROCEDURES
IN OTHER SCHEMAS STOPPED act
ssn The name of the DB2 subsystem to which this
stored procedure address space was connected. Explanation:
proc The name of the JCL PROC used to start this A STOP PROCEDURE(*.*) is currently in effect. Any
stored procedures address space. functions not listed in the preceding DSNX942,
DSNX943, and DSNX950 messages are stopped act.
System action:
act The action provided on the STOP
The stored procedure address space initialization
PROCEDURE command
continues. z/OS UNIX System Services callable
services’ return values, return codes, and reason codes System action:
are documented in z/OS UNIX System Services Messages
The DISPLAY PROCEDURE command processing
and Codes.
continues.
Problem determination:
Most failures are due to the user ID associated with the DSNX990E csect-name IMS ODBA
WLM-established stored procedures address space not INITIALIZATION FAILED BECAUSE
being RACF defined. If you suspect an error in DB2, THE CALLABLE INTERFACE CANNOT
refer to Part 2 of Diagnosis Guide and Reference for BE LOADED
information on identifying and reporting the problem.
Explanation:
It is also possible that the number of processes was
The IMS ODBA callable interface module cannot be
exceeded for the user ID. If the NUMBER OF TCBS is
loaded. No IMS database DL/I calls will be supported
set too high during install, NUMTCB may exceed the
from stored procedures. Ensure the load module named
value of the UNIX System Services MACPROCUSER
AERTDLI is located within the partitioned dataset
setting. Refer to z/OS UNIX System Services Messages
specified in the stored procedure address space startup
and Codes for more information.
procedure’s DFSRESLB dd card statement.
System action:
DSNX987I csect-name NAME schema-name INVALID,
COMMAND IGNORED. The stored procedure address space initialization
continues.
Explanation:
The function name or procedure name supplied on the
DSNX991I csect-name IMS ODBA
DISPLAY, START, or STOP, FUNCTION SPECIFIC or
INITIALIZATION COMPLETED
PROCEDURE command uses a invalid wildcard
schema name. The qualified routine name must specify Explanation:
a full schema name, ″*″, ″*.*″, or blanks.
The initialization of the IMS ODBA callable interface
schema-name has completed. Stored procedure applications may use
The schema name containing invalid DL/I calls to access IMS databases.
characters.
System action:
System action:
The stored procedure address space initialization
The START, STOP, or DISPLAY command is rejected. continues.
694 Messages
DSNX993I • DSNX994I
System action:
DSNY007I LOAD MODULE DSNHDECP DOES
NOT HAVE RMODE(24) ATTRIBUTE of recovery. If indoubt units of recovery exist, the DB2
member remains up and running in light mode so that
Explanation:
the indoubts can be resolved.
The named load module was not link-edited with the
required RMODE(24) attribute.
DSNY010I LOAD MODULE module name IS NOT
System action: AT THE CORRECT RELEASE/
VERSION LEVEL
DB2 startup is abended with reason code 00E80160.
Explanation:
Operator response:
The named load module is not at the correct
Notify the system programmer. release/version level for the version of DB2 that was
System programmer response: being started.
698 Messages
DSNY014I • DSNY026I
| Ensure that the required version of z/OS is enabled | DSNY024I facility INITIALIZATION IS STARTING
| before starting DB2.
| Explanation:
| DSNY014I n csect DB2 HAS BEEN STARTED | The facility that you specified is starting.
| WITH ACCESS(MAINT)
| facility is MSTR, DBM1, or DIST address spaces.
| Explanation:
| System action:
| This DB2 has been started with option
| The facility is starting.
| ACCESS(MAINT).
| System action:
| DSNY025I facility SHUTDOWN IS COMPLETE
| None.
| Explanation:
| Programmer response:
| The specified utility has completed shutdown
| None. | processing.
| Severity: | facility is MSTR, DBM1, or DIST address spaces.
| 0 (informational) | System action:
| The facility has stopped.
DSNY015I LIGHT(YES) ON START DB2
COMMAND WAS IGNORED, SYSTEM
IS NOT ENABLED FOR DATA
| DSNY026I csect-name ******** THIS DB2 PRODUCT
SHARING
| REQUIRES A ZNALC LPAR
Explanation:
| Explanation:
702 Messages
DSNZ014I • DSNZ016I
The value shown for ’severity’ is the value returned as the job-step condition code
from the job step in which the message is issued. If additional messages having
higher severity values are issued during the same job step, the higher value is
reflected as the job-step condition code.
8 (error)
DSN1110E LIMIT OF 50 STATEMENTS
EXCEEDED
DSN1112E TOKEN xx..xx EXCEEDS 64
Explanation:
HEXADECIMAL CHARACTERS
DSN1LOGP allows a total of 50 statements for a given
Explanation:
job.
The SYSIN input contains the character string ’xx..xx’.
System action:
This string is invalid.
Processing is terminated.
System action:
User response:
Processing is terminated.
Resubmit the job using no more than 50 statements.
User response:
Severity:
Resubmit the job with the specified token being no
8 (error) more than 64 hexadecimal characters in length.
Severity:
DSN1111E LIMIT OF 80 TOKENS EXCEEDED
8 (error)
Explanation:
DSN1LOGP allows a total of 80 keywords and DSN1113E VALUE FOR KEYWORD xxxxxxxx
corresponding value specifications. A keyword with its INVALID
value is considered two tokens.
Explanation:
System action:
The SYSIN input contains the keyword ’xxxxxxxx’. The
Processing is terminated. value specified for that keyword is not of the form ’(
value )’.
User response:
System action:
Resubmit the job using no more than 80 keywords.
Processing is terminated.
Severity:
User response:
DSN1117E csect-name keyword SPECIFIED WITH
Resubmit the job with the correct form of the keyword. NO VALUE OR INCORRECT VALUE
The problem might be that the closing parenthesis ’)’ is
Explanation:
missing or that an extra blank exists in the value.
The keyword must be followed by a correct value.
Severity:
System action:
8 (error)
Processing is terminated.
DSN1114E RBASTART MULTIPLY DEFINED User response:
Explanation: Resubmit the job providing a correct value for the
keyword.
The RBASTART parameter can be specified only once
for a given job. Severity:
System action: 8 (error)
Processing is terminated.
DSN1118E RBAEND > 12 HEX CHARACTERS
User response:
Explanation:
Resubmit the job using a single RBASTART value.
The maximum size of a log RBA in DB2 is 6 bytes
Severity:
(hence, 12 characters).
8 (error)
System action:
Processing is terminated.
DSN1115E csect-name KEYWORD keyword ALLOWS
ONLY number HEX CHARACTERS User response:
Explanation: Resubmit the job providing an RBAEND value that is
no more than 12 hexadecimal characters.
The value given for keyword is too long.
Severity:
System action:
8 (error)
Processing is terminated.
User response:
DSN1119E DBID MULTIPLY DEFINED
Resubmit the job providing no more than the
Explanation:
maximum number of characters allowed for the
keyword. The DBID keyword can be specified only once for a
given job.
Severity:
System action:
8 (error)
Processing is terminated.
DSN1116E csect-name keyword IS USED MORE User response:
THAN ONCE.
Resubmit the job providing a single DBID value.
Explanation:
Severity:
The keyword can be used only once in a single job.
8 (error)
System action:
Processing is terminated. DSN1120E DBID SPECIFIED WITH NO VALUE
User response: Explanation:
Resubmit the job providing a single keyword. The DBID keyword specifies a hexadecimal database
identifier and must be followed by a value.
Severity:
System action:
8 (error)
Processing is terminated.
User response:
Resubmit the job providing a DBID (value).
706 Messages
DSN1121E • DSN1127E
User response:
DSN1134E csect-name LIMIT OF number keywordS IS
Resubmit the job providing both an OBID (value) and a EXCEEDED
DBID (value).
Explanation:
Severity:
The keyword was specified more than the maximum
8 (error) number of times allowed in any given job.
System action:
DSN1131E OFFSET/VALUE PAIR NUMBER xx
CONTAINS INVALID HEX DATA Processing is terminated.
A hexadecimal specification is required. The value for Resubmit the job specifying this keyword no more than
the maximum number of times.
708 Messages
DSN1135E • DSN1141E
Severity:
DSN1138E csect-name keyword AND keyword
8 (error) CANNOT BOTH BE SPECIFIED
Explanation:
DSN1135E SUMMARY MULTIPLY DEFINED
You cannot specify both keywords in one job.
Explanation:
System action:
The SUMMARY option can be specified only once.
Processing is terminated.
System action:
User response:
Processing is terminated.
Resubmit the job specifying only one of the keywords.
User response:
Severity:
Resubmit the job using a single SUMMARY
8 (error)
specification.
Severity:
DSN1139E RID SPECIFIED WITH NO VALUE
8 (error)
Explanation:
The RID keyword specifies a 4-byte hexadecimal
DSN1136E SUMMARY SPECIFIED WITH NO
number, with the first 3 bytes representing the page
VALUE OR INCORRECT VALUE
number and the last byte representing the record ID. A
Explanation: value must be associated with the RID.
The permitted values for summary are YES, NO, ONLY, System action:
or FILTER.
Processing is terminated.
System action:
User response:
Processing is terminated.
Resubmit the job providing a RID (value).
User response:
Severity:
Resubmit the job providing a valid parameter for the
8 (error)
SUMMARY option.
Severity:
DSN1140E RID > 8 HEX CHARACTERS
8 (error)
Explanation:
The maximum size of a RID in DB2 is 4 bytes (hence, 8
DSN1137I csect-name FIRST PAGE SET CONTROL
characters).
RECORD AFTER RESTART LOG seq
nnnnnnnnnnnn System action:
Explanation: Processing is terminated.
This message shows the log sequence number of a User response:
record that serves as an implicit indication that a restart
Resubmit the job providing a valid RID value of no
occurred just prior to this point.
more than 8 hexadecimal characters.
seq RBA or LRSN
Severity:
nnnnnnnnnnnn
8 (error)
The log sequence number
System action:
DSN1141E RID WITHOUT DBID OBID
Processing continues.
Explanation:
Severity:
The DBID and OBID associated with the given RID
0 (informational) value must be specified.
System action:
Processing is terminated.
User response:
Explanation: Explanation:
The DATAONLY option limits the log records extracted This message indicates that the current log record has a
in the detail report to those that represent data timestamp that is less than the previous timestamp
modifications. This option can be specified only once. processed. This may be a potential problem.
Resubmit the job specifying DATAONLY once. Examine current log to determine whether multiple
processors are writing to the same log. (Data may be
Severity: being overwritten.) This may lead to data
8 (error) inconsistencies.
Severity:
DSN1143E DATAONLY SPECIFIED WITH NO 4 (warning)
VALUE OR INCORRECT VALUE
Explanation: DSN1147E SYSCOPY MULTIPLY DEFINED
The DATAONLY keyword must be specified with Explanation:
either a YES or NO value. Any other value (including
no value) is incorrect. The SYSCOPY option can only be specified once.
Resubmit the job specifying the correct value for the Refer to Diagnosis Guide and Reference for information
DATAONLY parameter. on identifying and reporting the problem.
710 Messages
DSN1148E • DSN1151I
luwid The logical unit of work identifier associated appears just as it does in message DSN1151I. If the UR
with the UR did not complete, the END RBA or LRSN values are
not printed.
name The name of the remote coordinator associated
with the UR. This is blank if the coordinator is
This message is followed by messages that identify the
the local DB2, IMS, or CICS.
page sets modified by the UR. Details of that are in the
list of participants explanation of message DSN1151I.
The names of all remote participants that
System action:
might have updated data in this UR.
Processing continues.
This message is followed by messages that identify the
Severity:
page sets modified by the UR. For each page set, a
single message is printed in the following form: 0 (informational)
DATABASE=dbid=dbname
PAGE SET=obid=psname
DSN1153I csect-name CHECKPOINT mbn
STARTRBA=ss ENDRBA=ee
Where: STARTLRSN=rr ENDLRSN=nn
dbid Internal database identifier DATE=yy.ddd TIME=hh:mm:ss
obid Internal page set identifier This message describes a complete checkpoint on the
log starting and ending RBA or LRSN for data sharing
psname Page set name corresponding to the OBID member mbn. If the information is available,
The dbname and psname fields might be absent DSN1LOGP also returns the date and time that the
if a full checkpoint was unavailable to checkpoint started.
DSN1LOGP or was caused by overlapped When this message follows message DSN1157I
processing of DB2 during a checkpoint. RESTART SUMMARY, it identifies the checkpoint that
would be used at restart. If no checkpoint is available,
If no data was modified by the UR (for example, message DSN1158I is printed instead.
certain URs might be created merely to track
information that is valid only for the life of the mbn MEMBER=membername, where membername is
application), the phrase NO DATA MODIFIED is the member of a data sharing group. This is
printed. printed only for a data sharing record.
Severity: Severity:
0 (informational) 0 (informational)
This message describes a unit of recovery (UR) for data DSN1LOGP also returns the date and time of that
sharing member mbn. The UR identifying information restart.
(**) described in message DSN1151I is unavailable.
System action:
mbn MEMBER=membername, where membername is
the member of a data sharing group. This is Processing continues.
printed only for a data sharing record.
Severity:
The remaining information (DISP, INFO, START, END, 0 (informational)
NID, LUWID, COORDINATOR and PARTICIPANTS)
712 Messages
DSN1155I • DSN1160I
714 Messages
DSN1172E • DSN1178E
System action: Provide a valid OFFSET for the given VALUE and
resubmit the job.
Processing terminates.
Severity:
User response:
12 (severe error)
Provide an associated VALUE (value) for the given
OFFSET and resubmit the job.
DSN1182E LIMIT OF 10 LUWIDs EXCEEDED
Severity:
Explanation:
12 (severe error)
A maximum of 10 LUWID keywords can be specified
in any given job.
DSN1179E VALUE SPECIFIED WITH NO
CORRESPONDING OFFSET OR System action:
SUBTYPE PARAMETER
DSN1LOGP processing is terminated.
Explanation:
User response:
The given VALUE has either no corresponding OFFSET
Resubmit the job providing no more than 10 LUWID
or SUBTYPE parameter specified.
keywords.
System action:
Severity:
Processing terminates.
8 (error)
User response:
Provide an associated OFFSET or SUBTYPE for the DSN1183E LUWID SPECIFIED WITH
given VALUE and resubmit the job. INCORRECT VALUE OR NO VALUE
Severity: Explanation:
12 (severe error) The LUWID consists of an LU network name, an LUW
instance number, and a commit sequence number. The
LU network name consists of a 1 to 8 character
DSN1180E VALUE SPECIFIED WITH NO VALUE
network ID, a period, and a 1 to 8 character network
OR INCORRECT VALUE
LU name. The LUW instance number consists of a
Explanation: period followed by 12 hexadecimal characters. The
LUW sequence number consists of a period followed
The given VALUE has no corresponding value given, by 4 hexadecimal characters.
an incorrect value is specified, such as specifying a
keyword in place of a value, or an uneven number of System action:
characters were specified.
DSN1LOGP processing is terminated.
System action:
User response:
Processing terminates.
Resubmit the job providing a valid LUWID value.
User response:
Severity:
Provide a valid value for the given VALUE and
8 (error)
resubmit the job.
Severity:
DSN1184E FILTER KEYWORD MULTIPLY
12 (severe error) DEFINED
Explanation:
DSN1181E VALUE SPECIFIED WITH NO
The FILTER keyword was specified more than once.
CORRESPONDING OFFSET
System action:
Explanation:
DSN1LOGP processing is terminated.
The given VALUE has no corresponding OFFSET
specified. User response:
System action: Correct the input to provide only one FILTER keyword
and resubmit the job.
Processing terminates.
Severity:
User response:
716 Messages
DSN1185E • DSN1196I
8 (error) | member
| The two-byte member ID of the DB2 member
| that wrote the log record. In non- datasharing,
DSN1185E FILTER KEYWORD SPECIFIED
| this value is zero.
WITHOUT SUMMARY KEYWORD
| prev-level
Explanation:
| Previous level of the page from the current log
The FILTER keyword was specified without an | record.
associated SUMMARY keyword.
| prev-update
System action: | The previous update to the page found during
| log processing.
DSN1LOGP processing is terminated.
| date The date portion of the current log record
User response: | LRSN value, in printable format.
Correct the input to include the SUMMARY keyword | time The time portion of the current log record
and resubmit the job. | LRSN value, in printable format.
Severity:
8 (error) | DSN1194I SUMMARY REPORT OF PAGE
| REGRESSION ERRORS
718 Messages
DSN1216E • DSN1219E
Processing terminates.
DSN1222E DSNJSLR ERROR RETCODE=xxxxxxxx
User response: REASON CODE=yyyyyyyy DYNAMIC
ALLOCATION INFORMATION
Resubmit the job with a SYSSUMRY DD statement CODE=aaaa ERROR CODE=bbbb
included in the JCL invocation.
Explanation:
Severity:
An error occurred while dynamically allocating a log
8 (error) data set. Information code ’aaaa’ and error code ’bbbb’
were returned by the dynamic allocation SVC and
DSN1220E ARCHIVE LOG TRUNCATED AT identify the nature of the error. The DSNJSLR return
xxxxxxxx - INVALID LOG RECORDS code xxxxxxxx, and reason code yyyyyyyy, included in
WERE READ the message are documented in Appendixes (Volume 2)
of Administration Guide. Refer to the appropriate MVS
Explanation: publication for an explanation of these codes.
At a restart of DB2, an archive log was truncated. This System action:
archive log data set could not be physically altered to
reflect this truncation, and invalid log records therefore Processing terminates.
still exist. DSN1LOGP has already reported this Severity:
information in the summary report, and cannot retract
it. Nor can it disregard the invalid log information 12 (severe error)
already read in order adequately to summarize what
has occurred. Therefore, all information up to this point
DSN1223E DSNJSLR ERROR RETCODE=xxxxxxxx
in the log will be summarized, and a new summary
REASON CODE=yyyyyyyy RDJFCB
report initiated. Consequently, the same UR may be
RETURN CODE=aaaa
reported twice with different dispositions and different
page sets modified. To avoid this condition, use the Explanation:
BSDS DD statement instead of the ARCHIVE DD
An error occurred while trying to read the job file
statement.
control block. The DSNJSLR return code ’xxxxxxxx’,
System action: and reason code ’yyyyyyyy’, included in the message
are documented in Appendices (Volume 2) of
Processing continues.
Administration Guide.
Severity:
The RDJFCB return code (aaaa), identifies the nature of
0 (informational) the error. Refer to the appropriate MVS publication for
an explanation of these codes.
720 Messages
DSN1300E • DSN1401I
| System action:
DSN1309E csect-name SPECIFIED END RANGE IS
| Processing continues. LESS THAN START RANGE
| Check that the specified start log record address (RBA The value specified for ENDLRSN or ENDRBA is less
| or LRSN) is required for the determination of the than the value of STARTLRSN or STARTRBA for a
| problem. Either correct the log range to the DSN1LOGP job.
| specification that you want, or provide the missing log
System action:
| data sets either in the ACTIVEn or ARCHIVE DD
| statements. Processing terminates.
| A common problem is to specify an excessively large User response:
| range to express that all available log records should be
Resubmit the job with correct start and end values.
| formatted. If all available log records should be
| formatted, simply omit the low and high limits to
| suppress this message. | DSN1400I DSN1SMFP ERROR: UNABLE TO
| OBTAIN THE EBCDIC CCSID
| Problem determination:
| SETTING FROM DSNHDECP
| Contact IBM Software Support for assistance.
| Explanation:
| Severity:
| DSN1SMFP was unable to load the DSNHDECP
| 4 (warning) | module or unable to determine the EBCDIC CCSID
| setting. The setting is required in order to convert
| Unicode-encoded trace fields to EBCDIC.
DSN1300E csect-name RBA RANGE CANNOT BE
USED TO PRINT LOG RECORDS | System action:
FROM MULTIPLE DB2 SYSTEMS
| Processing continues.
Explanation:
| Programmer response:
RBASTART and RBAEND cannot be used to define the
range when selecting log records from multiple DB2
| Ensure that the site-defined DSNHDECP module is
systems. LRSNSTART and LRSNEND should be used
| available to DSN1SMFP via the STEPLIB, JOBLIB or
instead.
| system link list. The site-defined DSNHDECP module
| typically resides in the prefix.SDSNEXIT library.
System action: | DSN1SMFP should use the same DSNHDECP module
| as the DB2 subsystem from which the SMF records
Processing terminates.
| were obtained.
User response:
| Severity:
Resubmit the job with either RBA values only or LRSN
| 12 (severe error)
values only.
System action:
| Programmer response:
Processing terminates.
| Increase the region size of the job or job step that
| executes DSN1SMFP. If the problem occurs during peak
User response: | system load, you might need to run DSN1SMFP at a
| different time.
Correct the DD statement and resubmit the job.
| Severity:
| 12 (severe error)
| 4 The length of the record did not meet the | See the preceding message for further information.
| minimum length for processing. | Severity:
| 5 The offset specified in the self-defining section | 4 (warning)
| for a data section exceeds the length of the
| input record.
| DSN1405I DSN1SMFP WARNING: EBCDIC
| 6 An unexpected number of items were found in | CCSID SPECIFIED FOR DSN1SMFP,
| the data section. | decp-ccsid:, DOES NOT MATCH THE
| EBCDIC CCSID OF THE CURRENT
| The record cannot be processed and is excluded from | IFCID 106 RECORD, ifcid-106-ccsid
| the output reports.
| Explanation:
| System action:
| The EBCDIC CCSID of the current IFCID 106 record
| DSN1SMFP processing continues with the next input | (identified in the subsequent DSN1404I message) does
| record. | not match the EBCDIC CCSID specified in the
| Programmer response: | DSNHDECP module loaded by DSN1SMPF at startup
| time. DSN1SMFP uses this setting to convert
| See the problem determination section. Remove the | Unicode-encoded trace data to EBCDIC so it can be
| corrupted record and try again. If the error persists | written to the output reports. If the CCSID is incorrect,
| then the input data set to DSN1SMFP is probably | then the results of converting such data are
| corrupted. | unpredictable.
| Problem determination: | System action:
722 Messages
DSN1406I • DSN1700E
Processing is terminated.
DSN1701E START TRACE MISSING
User response:
Explanation:
When you resubmit the job either:
The START TRACE command is required. The first
keyword record of the SDMPIN input does not contain v Specify a larger region size in the job control
a START TRACE command. language.
v Reduce the value of BUFSIZE on START TRACE.
System action:
Severity:
Processing is terminated.
8 (error)
User response:
Resubmit the job with START TRACE as the first
DSN1705E SYNTAX ERROR, LINE = ll, COLUMN
keyword record in the SDMPIN input.
= cc
Severity:
Explanation:
8 (error)
A syntax error was encountered in the SDMPIN input.
The location of the error is given by:
DSN1702E KEYWORD xxxxxxxx MULTIPLY
ll The line number within the input stream that
DEFINED
is in error.
Explanation:
cc The column number.
Keyword ’xxxxxxxx’ was specified multiple times in the
System action:
SDMPIN input. All keywords are allowed only once.
Processing is terminated.
System action:
User response:
Processing is terminated.
Correct the syntax error and then resubmit the error.
User response:
Severity:
Specify the keyword only once. Resubmit the job.
8 (error)
Severity:
8 (error)
DSN1706E INVALID ABEND CODE SPECIFIED
Explanation:
DSN1703E KEYWORD xxxxxxxx UNKNOWN
An invalid abend code was specified on the ACTION
Explanation:
keyword.
DSN1SDMP does not recognize the keyword
System action:
’xxxxxxxx’.
Processing is terminated.
System action:
User response:
Processing is terminated.
Allowable abend codes are 00E60100 through 00E60199.
User response:
Specify an allowable abend code and then resubmit the
Make sure that all keywords are valid and then job.
resubmit the job.
Severity:
Severity:
8 (error)
8 (error)
DSN1707E LIMIT OF 50 STATEMENTS
DSN1704E UNABLE TO OBTAIN RETURN-AREA EXCEEDED
STORAGE
Explanation:
Explanation:
DSN1SDMP allows a maximum of 50 statements for a
An error resulted when DSN1SDMP attempted to given job.
obtain storage for an instrumentation facility interface
System action:
(IFI) return area.
Processing is terminated.
System action:
724 Messages
DSN1708E • DSN1713I
User response:
DSN1711E START TRACE ERROR,
Use no more than 50 statements when you resubmit the REASON=xxxxxxxx
job.
Explanation:
Severity:
DB2 did not process the submitted START TRACE
8 (error) command. The reason code ’xxxxxxxx’ is returned from
the instrumentation facility interface (IFI).
DSN1708E TOO MANY SELECT CRITERIA System action:
VALUES
Processing is terminated.
Explanation:
User response:
DSN1SDMP allows a maximum of eight SELECT
Check the return area that follows message DSN1712I.
criteria values.
Possible problems are:
System action: v The syntax of the START TRACE command is
Processing is terminated. invalid. Correct the command and resubmit the job.
Do not include the subsystem recognition character
User response: before the command text.
Use no more than eight SELECT criteria values and v The user does not have authority to issue trace
then resubmit the job. commands. Obtain trace authority and resubmit the
job.
Severity:
Severity:
8 (error)
8 (error)
DSN1714I TRACE RECORDS WERE LOST DSN1SDMP issued the STOP TRACE command and
the return area resulting from the instrumentation
Explanation: facility interface (IFI) COMMAND call follows this
message. The return area contains DB2 command
DB2 trace records were lost and are not contained in
response messages.
the SDMPTRAC data set.
System action:
System action:
Processing continues.
Processing continues.
Severity:
User response:
0 (informational)
Possible reasons for lost trace records are:
v The OP buffer is not large enough. Specify a larger
BUFSIZE on the START TRACE command and then DSN1718E STOP TRACE ERROR,
resubmit the job. REASON=xxxxxxxx
v The trace data is too voluminous and buffer is Explanation:
overflowing before the data can be read. Specify a
more granular selectivity on the START TRACE DSN1SDMP attempted to submit a DB2 STOP TRACE
command and then resubmit the job. command at the end of its processing; however, the
command failed. The reason code returned from the
Severity: instrumentation facility interface (IFI) is ’xxxxxxxx’.
0 (informational) System action:
Processing is terminated.
DSN1715E UNABLE TO OBTAIN WORK SPACE
User response:
Explanation:
Check the return area that follows message DSN1717I.
An error resulted when DSN1SDMP attempted to One possible problem is:
obtain work area storage. v The trace has already been stopped from the
System action: operator’s console or by another application
program.
Processing is terminated.
Severity:
User response:
8 (error)
Specify a larger region size in the job control language
and then resubmit the job.
DSN1719I ACTIONS ARE COMPLETE
Severity:
Explanation:
8 (error)
All requested IFC selective dump actions finished. All
trace records have been written to the specified
DSN1716E UNABLE TO OPEN SDMPIN destination(s). If an abend action was requested, all
Explanation: abends have taken place.
726 Messages
DSN1720I • DSN1804I
The page is marked for output if the FORMAT/DUMP Correct the SYSUT1 DD statement and rerun the job.
option is in effect. Processing continues. Problem determination:
Problem determination: Checkable system table spaces must be referenced by a
728 Messages
DSN1811I • DSN1816I
Severity:
DSN1817I ARGUMENT arg-val OF THE MAP
COMMAND IS INVALID 0 (informational)
Explanation:
DSN1820I MAPPING OF map-opt (val1,val2) HAS
This message indicates that the argument ’arg-val’ of
STARTED
the MAP command is invalid.
Explanation:
System action:
This message indicates that mapping of the indicated
Processing terminates.
option ’map-opt’, which is either ANCHOR, HASH,
Problem determination: PAGE or RID, has started. The option’s arguments,
’val1’ and ’val2’ will also be mapped. Following this
Refer to Utility Guide and Reference for the correct
message will be the records of the chain.
syntax.
System action:
Examples of invalid arguments are:
v The offset value of the ANCHOR or HASH option is Processing continues.
neither zero (0) nor four (4). Severity:
v When the ANCHOR and RID option has been
0 (informational)
specified, the page number specified is less than two,
which would be a nondata page.
DSN1821I MAPPING OF ’map-opt’ (val1,val2)
Severity:
HAS COMPLETED
8 (error)
Explanation:
This message indicates that mapping of the indicated
DSN1818I IDMAP ENTRY entry-number IN PAGE
option ’map-opt’, which is either ANCHOR, HASH,
page-number IS BEING USED BY
PAGE, or RID, started. The option’s arguments, ’val1’
MULTIPLE CHAINS - ONE OF WHICH
and ’val2’, will also be mapped. Preceding this message
IS IN ERROR
will be the records of the chain.
Explanation:
System action:
This message indicates that a record is part of two
Processing continues.
different chains and therefore creates an invalid
structure within the table space. If using the MAP Severity:
option, the mapping of the chain stops since the path
back to the starting record is lost. 0 (informational)
System action:
DSN1822I DBID dbid HASHED TO AN EMPTY
Processing continues. ANCHOR POINT - NO ENTRIES FOR
THE GIVEN DBID ARE AVAILABLE
Problem determination:
IN THE TABLESPACE
Contact your IBM Support Center for assistance.
Explanation:
Severity:
DBID ’dbid’ hashed to an empty anchor point. An
4 (warning) anchor point with a value of 0 (empty) means that no
entries are available in the table space. Therefore, no
links are checked.
DSN1819I HASH VALUE FOR dbid
CORRESPONDS TO: PAGE = System action:
page-number AND ANCHOR POINT
Processing continues with the next set of parameters.
OFFSET = offset
Severity:
Explanation:
4 (warning)
This message indicates the hash values for the given
’dbid’, after applying the hash function, where
’page-number’ is the page and ’offset’ is the anchor DSN1823I INVALID SYNTAX, c EXPECTED
point.
Explanation:
System action:
This message indicates that an unexpected character
Processing continues.
730 Messages
DSN1824I • DSN1829I
was found while parsing the parmlist and that ’c’ was point to a valid record. Otherwise, contact your IBM
the expected character. Support Center for assistance.
System action: Severity:
Processing terminates. 4 (warning)
Problem determination:
DSN1827I THE SPECIFIED PAGE IS NOT A
Check Command Reference for the correct syntax.
HASHED DATA PAGE - THE
Severity: REQUESTED FUNCTION REQUIRES A
HASHED DATA PAGE.
8 (error)
Explanation:
DSN1824I INVALID HEX DATA: hex-data This message indicates that the HASH or ANCHOR
option of the MAP command was issued against a
Explanation: nonhashed data page (that is, a page with no anchor
This message indicates that the input value ’hex-data’ points).
is not a valid hexadecimal number. System action:
System action: Processing continues with the next set of parameters.
Processing terminates. Problem determination:
Problem determination: If using the ANCHOR function, examine the page-slot
Correct input value and rerun job. argument to ensure that the page value is correct. If
using the HASH function, ensure that the ’dbid’ value
Severity: is correct. Otherwise, examine the SYSUT1 DD
8 (error) statement to ensure that the table space is correct. If so,
use the RID or PAGE function to achieve the desired
mapping.
DSN1825I INPUT VALUE EITHER TOO LONG
OR OMITTED: in-val Severity:
Explanation: 4 (warning)
Processing terminates. This message indicates that the record with OBID
’rec-obid’ is invalid for the database currently being
Problem determination: processed.
Correct input value and rerun job. System action:
Severity: Processing continues with the next set of parameters.
8 (error) Problem determination:
If using the MAP command, insure that all user
DSN1826I RECORD WITH OBID = rec-obid IS supplied offsets actually point to valid data. If you
INVALID FOR THIS CHAIN suspect an error in DB2, refer to Part 2 of Utility Guide
Explanation: and Reference for information on identifying and
reporting the problem.
This message indicates that the record with OBID
’rec-obid’ is invalid for the chain currently being Severity:
processed, assuming the OBID of the parent or first 4 (warning)
record processed was not in error.
System action: DSN1829I MAPPING MUST STOP AT PARENT
Processing terminates. RECORD WHEN USING THE
BACKWARD POINTER
Problem determination:
Explanation:
If using the MAP function, make sure the given values
This message indicates that the requested mapping
DSN1831I END OF DATE REACHED, PAGE = A request for a page number from an anchor point or a
page-number IS OUT OF RANGE child pointer in a parent record is pointing beyond the
high used RBA of the data set. Either the rid is in error
Explanation: or the data set has been truncated.
This message indicates that page ’page-no’, specified as System action:
a parameter of the MAP option, caused the
END-OF-DATA condition to be reached. The page The page is marked for output if the FORMAT/DUMP
number is invalid for the table space being mapped. option is in effect. Processing continues.
Processing continues with the next set of parameters. Examine previous diagnostic and system messages,
correct problem if possible and rerun the job.
Problem determination: Otherwise, contact your IBM Support Center for
Correct the page parameter of the MAP option and assistance.
rerun the job. Severity:
Severity: 4 (warning)
4 (warning)
| DSN1930I csect-name THE INPUT PARAMETER
DSN1833I ANCHOR POINT IS NOT IN USE | xxxxxxxx CONFLICTS WITH THE
| HEADER PAGE FIELD HPGyyyy. THE
Explanation: | INPUT PARAMETER WILL BE USED
The anchor point to be mapped has a value of 0, which | Explanation:
means that it is not in use. Therefore, no links are
checked. | The specified parameter does not agree with the value
| of the related field in the header page. The utility will
System action: | continue the execution using the specified input
Processing continues with the next set of parameters. | parameter.
| System action:
732 Messages
DSN1931I • DSN1942I
| Severity:
DSN1942I csect-name ERROR WHEN BUILDING
| 8 (error) THE COMPRESSION DICTIONARY
Explanation:
| DSN1940I csect-name COMPRESSION REPORT
An internal error was encountered while building the
| Explanation: dictionary.
| DSN1COMP completed successfully. This report System action:
| contains the compression savings for every supported
| page size. For a sample of the report, see the Processing terminated.
| DSN1COMP utility in Utility Guide and Reference. System programmer response:
| The compression report returns the following statistics: Determine the failing environment. Refer to part 2 of
| v the number of leaf pages processed Diagnosis Guide and Reference for information on
| v the number of keys processed identifying and reporting the problem.
8 (error) Severity:
8 (error)
DSN1943I csect-name DICTIONARY PAGE
ENCOUNTERED
DSN1947I DSN1947I csect-name COMPRESSION
Explanation: UNAVAILABLE FOR INDEX SPACES
A dictionary page was encountered while processing Explanation:
the input data set. This indicates that the data is in
Index data was provided as input to DSN1COMP.
compressed format.
Compression is supported only for table space data.
System action:
System action:
Processing terminated.
Processing terminated.
User response:
User response:
Run DSN1COMP on a data set containing data that is
Provide DSN1COMP with data containing table space
not in a compressed format.
data.
Severity:
Severity:
8 (error)
8 (error)
734 Messages
DSN1951I • DSN1955I
736 Messages
DSN1962I • DSN1966I
System action:
| If DSN1COPY terminates and issues this message,
| DSN1COPY attempts to determine the correct target
Processing continues. | data set or data sets that affect the data set number.
| (The data set number is the last qualifier in the data set
User response:
| name. For example, the data set number in the data set
If the image copy data set name was invalid, look in | DSNCAT.DSNDBD.TESTDB.TS01.I0001.A002 is A002.)
SYSIBM.SYSCOPY for valid names. Resubmit the valid
| When DSN1COPY issues this message, odsname might
IMAGE COPY data set to the stand-alone utility. If the
| be different than the output data set defined by
IMAGE COPY data set had a valid name, use the
| SYSUT2. SYSUT1 can contain data that should be
REPAIR utility to replace the zero pages with valid
| copied to data sets other than the one specified by
data pages.
| SYSUT2. DSN1COPY does not define data sets, so the
Severity: | output data set must be defined before DSN1COPY is
| run.
4 (warning)
| System action:
DSN1964I NO VALUE HAS BEEN SPECIFIED | Processing is terminated.
FOR THE NUMBER OF PARTITIONS.
| User response:
Explanation:
| Use access method services to define odsname and any
No value was given for the number of partitions. This | other VSAM data sets that have not yet been defined.
value should follow the ’NUMPARTS’ parameter.
| Severity:
System action:
| 8 (error)
Processing will terminate.
User response:
Look in SYSIBM.SYSTABLESPACE for the correct
DSN1967I THE OBID ARRAYS ARE FULL DSN1970I DATA PAGE CONTAINING OBID xxxx,
HAS NO MATCHING VALUE IN THE
Explanation:
SYSXLAT FILE
More than 1000 records of OBIDs were specified in the
Explanation:
SYSXLAT file.
One of the OBID records of the SYSXLAT file contains
System action:
a source OBID value that does not match the OBID
Processing stops. value of the source system.
User response:
DSN1971I DBID xxxx NOT FOUND IN THE
Change the SYSXLAT file. SYSXLAT FILE. REPLACE SOURCE
Severity: DBID xxxx OF THE SYSXLAT FILE
WITH IT.
8 (error)
Explanation:
DSN1969I SYSXLAT FILE CAN NOT BE OPENED The first record of the SYSXLAT file has the incorrect
source DBID value.
Explanation:
System action:
The QSAM OPEN for the SYSXLAT file failed because
no DD statement was provided. Processing is terminated.
Processing is terminated. Provide the first record of the SYSXLAT file with a
source DBID value which matches the DBID value of
System programmer response: the source system.
Provide a SYSXLAT DD statement if OBID translate is Severity:
to be done. Otherwise, remove the SYSXLAT parameter
and rerun. 8 (error)
User response:
DSN1972I PSID xxxx NOT FOUND IN THE
Notify system programmer. SYSXLAT FILE REPLACE SOURCE
Problem determination: DBID xxxx OF THE SYSXLAT FILE
WITH IT
Follow standard QSAM diagnostic procedures.
Explanation:
Severity:
The second record of the SYSXLAT file has the incorrect
8 (error) source PSID value.
System action:
Processing is terminated.
User response:
738 Messages
DSN1973I • DSN1979I
Use either the RECOVER or REPAIR utility to correct Check the parameter list and make sure that there are
the broken page. If you suspect an error in DB2, refer no spaces between any of the parameters.
to Part 2 of Utility Guide and Reference for information Severity:
on identifying and reporting the problem.
8 (error)
Problem determination should have been done when
the dump associated with the setting of the broken
page bit was requested. DSN1983I csect-name DICTIONARY IS INVALID,
REASON= X’nnnn’
Severity:
Explanation:
4 (warning)
The dictionary found in the data set is invalid. A DB2
internal error occurred during the validation of the
DSN1981I INVALID PARAMETER FIELD: expansion dictionary.
bad-parameter
System action:
Explanation:
Processing terminates.
An invalid input parameter was detected on the EXEC
statement. The parameter is either not a valid keyword System programmer response:
or it has invalid subparameters associated with it.
Determine the failing environment. Refer to part 2 of
Examples of invalid subparameters are: Diagnosis Guide and Reference for information on
v The NUMPARTS subparameter was other than ’(nn)’. identifying and reporting the problem.
’nn’ is a decimal number. User response:
v The NUMPARTS subparameter was missing either a
Verify that the correct data set is specified. You can
left or right parenthesis.
delete the EXPAND option and resubmit the job.
v The PRINT subparameter was missing either a left or
right parenthesis. Problem determination:
v The PRINT subparameter specified a digit in a page The REASON identifies the nature of the error. The
number which was not hexadecimal.
740 Messages
DSN1984I • DSN1987I
REASON is used for diagnostic purposes by the IBM If the zero page is the result of segmenting, no action is
Support Center. necessary. Similarly, if the zero page is a valid zero
page that was introduced by DB2, no action is
Severity:
necessary as this page is free space and is used by DB2
8 (error) when needed. If the zero page is a valid zero page and
you want to remove it from the table space, run the
REORG utility.
| DSN1984I UNEXPECTED PAGE NUMBER,
| EXPECTING: expected-page-number To help determine if the zero page was validly
| FOUND: page-number-found introduced by DB2, run the CHECK INDEX utility. This
assumes that at least one index is defined on the
| Explanation: affected table space.
| This message indicates that an unexpected page If the zero page is determined to be invalid, you need
| number was encountered. This message might be to run the RECOVER utility.
| received if the input data set is an image copy but you
| did not specify the FULLCOPY or INCRCOPY User response:
| parameters. The page numbers displayed in
Notify the system programmer.
| hexadecimal format are the page numbers that are
| expected and found. After this message is issued five Severity:
| hundred times, it will stop being issued.
4 (warning)
| System action:
| Processing continues. DSN1986I NEITHER FULLCOPY NOR INCRCOPY
PARAMETERS MAY BE SPECIFIED
| System programmer response: WITH THE SEGMENT PARAMETER.
| If running DSN1COPY use DSN1PRNT to dump the
Explanation:
| table space or index space. Otherwise, analyze the
| DSN1PRNT output. If you suspect an error in DB2, The parameters SEGMENT, FULLCOPY, and
| refer to Part 2 of Utility Guide and Reference for INCRCOPY describe the type of input that SYSUT1
| information on identifying and reporting the problem. references. SEGMENT is only relevant when a table
space or index space is the input. FULLCOPY and
| User response: INCRCOPY are only relevant when a image copy is the
| Notify the system programmer. input. If the input data set is a segmented table space,
then the FULLCOPY or INCRCOPY parameters should
| Severity: not be specified. If the input data set is a full or
| 4 (warning) for DSN1PRNT or 8 (error) for DSN1COPY incremental image copy, then SEGMENT should not be
specified.
742 Messages
DSN1992I • DSN1997I
DSN1992I VSAM PUT ERROR, RPLERREG = DSN1995I VSAM GET ERROR, RPLERREG =
return-code, RPLERRCD = reason-code return-code, RPLERRCD = reason-code
Explanation: Explanation:
VSAM PUT failed with the indicated error code. VSAM GET failed with the indicated error code.
Follow standard VSAM diagnostic procedures. See z/OS Follow standard VSAM diagnostic procedures. See z/OS
DFSMS: Macro Instructions for Data Sets for more DFSMS: Macro Instructions for Data Sets for more
information on the standard VSAM procedures, the information on the standard VSAM procedures, the
RPL fields, and the VSAM control blocks. RPL fields, and the VSAM control blocks.
Severity: Severity:
8 (error) 8 (error)
Correct the previous error and resubmit the job. Follow standard VSAM diagnostic procedure. See z/OS
DFSMS: Macro Instructions for Data Sets for more
User response: information on the standard VSAM procedures and the
Examine the previous error message of the application VSAM control blocks.
program. User response:
Severity: Notify system programmer.
8 (error) Severity:
8 (error) if error is greater than or equal to 128;
DSN1994I DSN1COPY/DSN1PRNT/DSN1COMP otherwise, severity code is 4.
COMPLETED SUCCESSFULLY,
page-count PAGES PROCESSED
DSN1997I OUTPUT DSNAME = data-set-name,
Explanation: data-set-type
This message indicates that a stand-alone utility Explanation:
successfully completed processing. The page count is
displayed in decimal format. The indicated ’data set name’ is used for output. ’data
set type’ is either VSAM or SEQ (for sequential).
System action:
Severity:
0 (informational)
744 Messages
Chapter 23. DSN3 messages
Message identifiers that begin with DSN3 communicate information about the
subsystem support subcomponent.
System action:
DSN3001I csect-name ABNORMAL DISCONNECT
FROM SUBSYSTEM INTERFACE Resources held (locked) by these ’indoubt’ URs are
unavailable to any other work units until their status is
Explanation:
resolved.
This message indicates that ’csect-name’ detected that
System programmer response:
an online routine was still supporting SSI calls
(IEFSSREQ) even though DB2 was nearly done The system programmer and/or system administrator
terminating or no longer executing. This occurs with must determine the correct recovery action to resolve
’csect-name’ DSN3RS0Xwhen the service address space the ’indoubt’ situations. This involves either
has reached end-of-memory and neither normal ’ensure-commit’ or ’backout’ decisions for all ’indoubt’
termination nor online error recovery routines have URs.
successfully completed termination of the DB2
subsystem. This occurs with ’csect-name’ DSN3SSTM The -DISPLAY THREAD command should be used to
when this condition is discovered during online see the URs still indoubt. It may show that all indoubt
termination. URs have already been resolved. The -RECOVER
INDOUBT command should be used, either from an
System action: MVS console or through an attachment facility, to
resolve the indoubt URs and to release the resources
The connection is terminated. All IEFSSREQ requests
they hold.
are handled by the DB2 ERLY code until DB2 is
restarted. Problem determination:
Problem determination: This error is probably caused by a cold start after an
abnormal termination of either subsystem or by offline
An SVC dump is requested. This SVC dump and
alterations of the logs of either subsystem.
associated SYS1.LOGREC entries provide information
to determine which resource managers had not
removed their support of particular SSI function codes. DSN3004I DESCRIPTOR GET FAILURE RC=X
xxxxxxxx, REASON=X xxxxxxxx
For dumps requested by DSN3RS0X,all pertinent
control blocks and stack storage are dumped. The Explanation:
primary control block of interest is the SSVT for DB2.
The parameter list required to create the DB2 agents
For DSN3SSTM, the DB2 ’standard dump’ facility is under which IEFSSREQ calls are processed could not
used to dump the information necessary for problem be obtained from the subsystem support subcomponent
diagnosis. The primary control blocks of interest are the directory of internal parameters (DSN3DIR1). The RC
’active’ CONN blocks. indicates the return code received from the system
parameter manager and REASON indicates the reason
code (from register 0).
DSN3002I RECOVERY INCOMPLETE FOR
connection-name The return code is always 4 when this message is
presented, indicating that the IEFSSREQ descriptor was
Explanation:
not found in the subsystem support subcomponent
At least one DB2 unit of recovery (UR), related to an directory. This is a system error and results in
identified subsystem (’connection-name’), is still termination of the DB2 subsystem. The reason code is
’indoubt’ after restart synchronization has taken place. always 0.
(’Indoubt’ URs are those for which commit has been
System action:
voted by DB2 but which have not been acknowledged
by ’connection-name’.) Subsystem initialization is discontinued. Termination
occurs.
This message may appear if the ’connection-name’
subsystem has begun to do new work before having System programmer response:
resolved all indoubt URs. The ’connection-name’
subsystem may be in the process of resolving the Repair the master directory (DSNZPARM) and/or the
indoubt URs. DB2 program libraries, and restart the DB2 subsystem.
Problem determination:
DSN3008I csect-name ABNORMAL DISCONNECT
If the problem persists, use any dumps and the console FOR PROGRAM REQUEST
log to diagnose the problem. If you suspect an error in HANDLER(S)
DB2, refer to Part 2 of Utility Guide and Reference for
Explanation:
information on identifying and reporting the problem.
This message indicates that ’csect-name’ has discovered
that one or more resource managers are still supporting
DSN3006I xxxx SSI FUNCTION WAS ALREADY
application program calls through their program
ACTIVE WHEN ACTIVATE WAS
request handler, even though DB2 was almost done
ATTEMPTED
terminating or was no longer executing. This occurs
Explanation: when the system services address space has gone to
end of memory and neither normal termination nor
An initialization sequence error has occurred. The online error recovery routines have successfully
subsystem support for SSI services resource manager completed termination of the DB2 subsystem.
(SSSS) has discovered during its initialization that
another resource manager (’xxxx’) has already activated System action:
the EOM or FEOT SSI call by calling DSN3AC0X. If
The program request handler (PRH) connection is
this occurs, the error is a serious one.
terminated. All application program support requests
System action: are rejected with an indication that DB2 is not up.
746 Messages
DSN3011I • DSN3014I
unit of recovery. Subsequent DSN3017I, DSN3018I or DB2 is the commit coordinator for one or more indoubt
DSN3019I messages describe the status of each unit of units of recovery. DB2 is unable to connect to RRS to
recovery and contain the RRS URID for each. resolve these indoubt units of recovery.
System action:
DSN3011I csect-name COORDINATOR RRS IS
Processing continues.
COLD STARTING AND HAS LOST
ITS LOG. INDOUBT DB2 THREADS Operator response:
NEED MANUAL RESOLUTION.
Use the RRS IPCS interface to determine the correct
Explanation: system and restart DB2 on that system.
DB2 has participant responsibility for indoubt threads.
RRS, the commit coordinator, has informed DB2 that it DSN3013I csect-name DB2 WAS RESTARTED ON
lost all knowledge of DB2 indoubt threads. The indoubt THE WRONG SYSTEM AND CANNOT
threads at this DB2 must be manually resolved with the CONNECT TO RRS. THERE ARE
RECOVER INDOUBT command. UNRESOLVED UNITS OF RECOVERY
WHERE DB2 IS A PARTICIPANT.
System action:
Explanation:
Processing continues.
DB2 has one or more indoubt threads and is unable to
System programmer response:
connect to RRS to resolve these indoubt units of
Contact the database administrator. recovery.
Database Administrator Action: DB2 is a participant System action:
with one or more indoubt threads. The coordinator is
Processing continues.
RRS. RRS has lost knowledge of the indoubt DB2
threads. A list of indoubt threads where RRS is the Operator response:
coordinator can be displayed using the DISPLAY
THREAD command for indoubt type threads by Use the RRS IPCS interface to determine the correct
specifying RRSAF as the connection name. A DSNV408I system and restart DB2 on that system.
message with coordinator = RRSAF identifies a thread
of this type. The DSNV449I message in the DISPLAY DSN3014I csect-name DB2 HAS NO KNOWLEDGE
THREAD report that follows contains the RRS unit of OF RRS URID=rrs_urid. THE RRS UR
recovery ID (URID) that identifies the RRS unit of IS INDOUBT. THE DB2 URID
recovery in the NID field. RECORDED BY RRS=db2_urid.
The heuristic decision (that is, to commit or abort the Explanation:
logical unit of work) should be coordinated with any
other participant RRS Recoverable Resource Managers. DB2 is restarting with RRS where DB2 is a participant
The existence of other participants might not be easy to and RRS is the coordinator. RRS has a unit of recovery
determine. The information might be available in the that DB2 should be a participant in, but DB2 has no
MVS/RRS recovery log even though information has knowledge of the RRS unit of recovery. The RRS unit of
been lost. recovery ID is ’rrs_urid’. RRS has recorded the DB2
unit of recovery ID as ’db2_urid’.
At this DB2, all indoubt threads coordinated by the
RRS must be resolved with the RECOVER INDOUBT System action:
command. Locked data remains unavailable until Restart with RRS continues.
resolution. Threads that were already resolved with this
command are discarded. Threads not yet resolved are Operator response:
discarded after resolution with the command. Notify the database administrator.
The commit or abort decision provided using the Database Administrator Action: This message might
RECOVER INDOUBT command for a logical unit of indicate a DB2 or RRS problem, or it might be
work are propagated to all downstream participants, if produced normally because one of the following prior
any. actions:
v A DB2 conditional restart was performed that
DSN3012I csect-name DB2 WAS RESTARTED ON resulted in the loss of part or all of the DB2 log. This
THE WRONG SYSTEM AND CANNOT conditional restart might have happened at any time
CONNECT TO RRS. THERE ARE in the past.
UNRESOLVED UNITS OF RECOVERY v The DB2 RECOVER INDOUBT command was used
WHERE DB2 IS THE COORDINATOR. to resolve the DB2 unit of recovery with URID
Explanation: ’db2_urid’.
748 Messages
DSN3018I • DSN3019I
v An RRS cold start was performed that resulted in the v The RRS ISPF interface might have been used to
loss of the RRS log. In this case, message DSN3010I heuristically commit or roll back the UR.
should have been produced.
v RRS might have had a partial loss of log data during If any of the above are true, the message can be
restart. In this case, message DSN3016I should have ignored. If not, there might be a DB2 or an RRS
been produced. problem.
v The RRS ISPF interface might have been used to Problem determination:
heuristically commit or roll back the UR.
Refer to Diagnosis Guide and Reference for information
on identifying and reporting the problem.
If any of the above are true, the message can be
ignored. If not, there might be a DB2 or an RRS Collect the following diagnostic items:
problem. v Console output from the system on which the job
Problem determination: was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
Refer to Diagnosis Guide and Reference for information
v Listing of DB2 log output.
on identifying and reporting the problem.
v DB2 log output, including any DB2 recovery log
Collect the following diagnostic items: archive tapes.
v Console output from the system on which the job v Copy of the log for this period, so that additional
was run, and a listing of the SYSLOG data set for the DSN1LOGP reports can be produced for problem
period of time spanning the failure. determination.
v Listing of DB2 log output.
.
v DB2 log output, including any DB2 recovery log
archive tapes.
DSN3019I csect-name RRS HAS NO KNOWLEDGE
v Copy of the log for this period, so that additional
OF DB2 URID=db2_urid. THE DB2 UR
DSN1LOGP reports can be produced for problem
WAS ROLLED BACK. THE RRS URID
determination.
RECORDED BY DB2=rrs_urid.
.
Explanation:
DB2 is restarting with RRS where DB2 is the
DSN3018I csect-name RRS HAS NO KNOWLEDGE
coordinator and RRS is a participant. DB2 has a unit of
OF DB2 URID=db2_urid. THE DB2 UR
recovery that RRS should be a participant in, but RRS
WAS COMMITTED. THE RRS URID
has no knowledge of the DB2 unit of recovery. The DB2
RECORDED BY DB2=rrs_urid.
unit of recovery ID is ’db2_urid’. DB2 has recorded the
Explanation: RRS unit of recovery ID as ’rrs_urid’.
DB2 is restarting with RRS where DB2 is the System action:
coordinator and RRS is a participant. DB2 has a unit of
Restart with RRS continues.
recovery that RRS should be a participant in, but RRS
has no knowledge of the DB2 unit of recovery. The DB2 Operator response:
unit of recovery ID is ’db2_urid’. DB2 has recorded the
RRS unit of recovery ID as ’rrs_urid’. Notify the database administrator.
Refer to Diagnosis Guide and Reference for information Database Administrator Action: If possible, insure that
on identifying and reporting the problem. the DB2 UR is resolved to abort. If this is done, there
will be no heuristic damage. If the DB2 UR is resolved
Collect the following diagnostic items:
to commit, heuristic damage will have occurred since
v Console output from the system on which the job RRS rolled back the same UR.
was run, and a listing of the SYSLOG data set for the
period of time spanning the failure.
DSN3022I csect-name HEURISTIC DAMAGE HAS
v Listing of DB2 log output.
OCCURRED. RRS HAS COMMITTED
v DB2 log output, including any DB2 recovery log THE UR WITH RRS URID=rrs_urid,
archive tapes. AND DB2 HAS ROLLED BACK THE
v Copy of the log for this period, so that additional SAME UR. THE DB2 URID=db2_urid
DSN1LOGP reports can be produced for problem
Explanation:
determination.
DB2 is restarting with RRS and has a unit of recovery
.
(UR) with DB2 URID=db2_urid that was rolled back.
DB2 is the commit coordinator for the UR and RRS is a
DSN3020I csect-name POSSIBLE HEURISTIC participant. RRS has committed the same UR. The RRS
DAMAGE. RRS HAS COMMITTED URID=rrs_urid.
THE UR WITH RRS URID=rrs_urid.
System action:
THE DB2 UR WITH DB2
URID=db2_urid IS INDOUBT. Restart with RRS continues.
Explanation: Operator response:
DB2 is restarting with RRS and has a unit of recovery Notify the database administrator.
(UR) DB2 URID=db2_urid that is indoubt. DB2 is the
Database Administrator Action: Heuristic damage has
commit coordinator for the UR and RRS is a
occurred since DB2 rolled back the UR and RRS has
participant. RRS has committed the same UR. The RRS
committed the same UR. Correct the damage. This is
URID=rrs_urid.
not an easy task. Knowledge of the application is
System action: required to determine which Recoverable Resource
Managers are involved in the UR. Since the time of the
Restart with RRS continues.
heuristic action, the data that was updated might have
Operator response: been used by many applications - read and/or write.
Correcting the damage might involve reversing the
Notify the database administrator. effects of these applications as well. Tools available are:
Database Administrator Action: If possible, insure that v The RRS ISPF functions can provide assistance in
the DB2 UR is resolved to commit. If this is done, there determining the set of resource managers involved
will be no heuristic damage. If the DB2 UR is resolved and what action they took.
to abort, heuristic damage will have occurred since RRS v The DB2 DSN1LOGP utility provides a summary
committed the same UR. report that identifies the table spaces modified by the
unit of recovery.
DSN3021I csect-name POSSIBLE HEURISTIC
DAMAGE. RRS HAS ROLLED BACK Contact your IBM Support Center for further
THE UR WITH RRS. URID=rrs_urid. assistance.
THE DB2 UR WITH DB2
URID=db2_urid IS INDOUBT.
DSN3023I csect-name HEURISTIC DAMAGE HAS
Explanation: OCCURRED. RRS HAS ROLLED BACK
THE UR WITH RRS URID=rrs_urid,
DB2 is restarting with RRS and has a unit of recovery AND DB2 HAS COMMITTED THE
(UR) DB2 URID=db2_urid that is indoubt. DB2 is the SAME UR. THE DB2 URID=db2_urid
commit coordinator for the UR and RRS is a
participant. RRS has rolled back the same UR. The RRS Explanation:
URID=rrs_urid.
DB2 is restarting with RRS and has a unit of recovery
System action: (UR) with DB2 URID=db2_urid that was committed.
DB2 is the commit coordinator for the UR and RRS is a
Restart with RRS continues. participant. RRS has rolled back the same UR. The RRS
Operator response: URID=rrs_urid.
750 Messages
DSN3024I • DSN3026I
Restart with RRS continues. v The DB2 DSN1LOGP utility provides a summary
report that identifies the table spaces modified by the
Operator response:
unit of recovery.
Notify the database administrator.
Contact your IBM Support Center for further
Database Administrator Action: Heuristic damage has
assistance.
occurred since DB2 committed the UR and RRS has
rolled back the same UR. Correct the damage. This is
not an easy task. Knowledge of the application is DSN3025I csect-name HEURISTIC DAMAGE HAS
required to determine which Recoverable Resource OCCURRED. COORDINATOR DB2
Managers are involved in the UR. Since the time of the HAS ROLLED BACK THE UR WITH
heuristic action, the data that was updated might have DB2 URID=db2_urid, AND RRS HAS
been used by many applications - read and/or write. INDICATED THE OUTCOME WAS
Correcting the damage might involve reversing the MIXED. THE RRS URID=rrs_urid.
effects of these applications as well. Tools available are:
Explanation:
v The RRS ISPF functions can provide assistance in
determining the set of resource managers involved DB2 is the commit coordinator and RRS is a
and what action they took. participant. DB2 rolled back the UR with URID =
db2_urid and RRS has indicated that one or more
v The DB2 DSN1LOGP utility provides a summary
Recoverable Resource Managers that participated in the
report that identifies the table spaces modified by the
RRS UR with URID = rrs_urid has committed the same
unit of recovery.
UR.
Contact your IBM Support Center for further System action:
assistance.
Processing continues.
Operator response:
DSN3024I csect_name HEURISTIC DAMAGE HAS
OCCURRED. COORDINATOR DB2 Notify the database administrator.
HAS COMMITTED THE UR WITH
DB2 URID=db2_urid, AND RRS HAS Database Administrator Action: Heuristic damage has
INDICATED THAT THE OUTCOME occurred since DB2 rolled back the UR and at least one
WAS MIXED. THE RRS URID=rrs_urid. RRS Recoverable Resource manager has committed the
same UR. Correct the damage. This is not an easy task.
Explanation: Knowledge of the application is required to determine
which Recoverable Resource Managers are involved in
DB2 is the commit coordinator and RRS is a
the UR. Since the time of the heuristic action, the data
participant. DB2 committed the UR with URID =
that was updated might have been used by many
db2_urid and RRS has indicated that one or more
applications - read and/or write. Correcting the
Recoverable Resource Managers that participated in the
damage might involve reversing the effects of these
RRS UR with URID = rrs_urid has rolled back the same
applications as well. Tools available are:
UR.
v The RRS ISPF functions can provide assistance in
System action: determining the set of resource managers involved
Processing continues. and what action they took.
v The DB2 DSN1LOGP utility provides a summary
Operator response:
report that identifies the table spaces modified by the
Notify the database administrator. unit of recovery.
committed the UR but has indicated that at least one | state of the global transaction. The requested recover
RRS Recoverable Resource manager has not completed | action action-1 is being changed to action-2 to preserve
commit processing for the RRS UR with | the integrity of the global transaction. URID is the
URID=rrs_urid. | beginning RBA of the UR. The combination of
| Connection Name, Correlation ID, and LUWID identify
System action:
| the thread associated with the UR.
Processing continues.
| System action:
Operator response:
| The indoubt Unit of Recovery is resolved to action-2.
Notify the database administrator.
Database Administrator Action: If possible, insure that | DSN3029I csect-name RRS ATTACH PROCESSING
the RRS Recoverable Resource Manager commits the | IS AVAILABLE.
RRS UR. If this is done, there will be no heuristic
| Explanation:
damage. If the RRS UR is rolled back by the RRS
Recoverable Resource manager, heuristic damage will | RRSAF has finished synchronizing with z/OS RRS and
have occurred since DB2 committed the same UR. | is now available to process application calls.
| System action:
DSN3027I csect-name POSSIBLE HEURISTIC
| Processing continues.
DAMAGE. COORDINATOR DB2 HAS
ROLLED BACK THE UR WITH DB2 | Operator response:
URID=db2_urid, AND RRS HAS
INDICATED THAT THE OUTCOME IS | Applications that require RRSAF services can be
PENDING. THE RRS URID=rrs_urid. | started.
Explanation:
DSN3100I csect-name SUBSYSTEM ssnm READY
DB2 is the commit coordinator for the DB2 UR with FOR START COMMAND
URID=db2_urid and RRS is a participant. RRS has also
rolled back the UR but has indicated that at least one Explanation:
RRS Recoverable Resource manager has not completed | The ’ssnm’ in the message is the name of the
roll back processing for the RRS UR with | subsystem that issued the message. This error occurs
URID=rrs_urid | during MVS IPL processing. Message DSN3104I is also
System action: | issued during this processing.
752 Messages
DSN3102I • DSN3105I
string must be between 3 and 10 characters long, and processing load module named in the first parameter
the next to the last character must be a ’,’. The passed to DB2 subsystem IPL initialization. ’ssnm’ is
parameters were obtained from the parameter fields of the name of the DB2 subsystem undergoing IPL-time
a record defining a DB2 subsystem in member initialization.
IEFSSNxx of SYS1.PARMLIB.
Either the load module name was specified incorrectly
The subsystem recognition character is not inserted in or the load module does not reside in a library
this message as it is not yet known. ’ssnm’ is the name included in the MVS linklist.
of the DB2 subsystem undergoing IPL-time
System action:
initialization.
DSN3UR00 abends with code X’04E’ and reason code
System action:
X’00F30103’. The DB2 subsystem with the indicated
The DB2 subsystem with the indicated name is not name is not available for this IPL of MVS.
available for this IPL of MVS.
Operator response:
Operator response:
Notify the system programmer.
Notify the system programmer.
System programmer response:
System programmer response:
Identify the cause of the error. Either correct the early
Correct the parameter fields in the record of processing load module or take the necessary steps to
SYS1.PARMLIB member IEFSSNxx, and re-IPL MVS. include the module in a link-listed library. Re-IPL MVS.
Refer to Part 2 of Installation Guide for the format of an Refer to Part 2 of Installation Guide for the format of an
IEFSSNxx record which defines a DB2 subsystem. IEFSSNxx record which defines a DB2 subsystem. Refer
to the appropriate MVS publication for MVS linklist
requirements.
DSN3102I csect-name INVALID SUBSYSTEM
RECOGNITION CHARACTER IN Problem determination:
PARMLIB RECORD. ssnm IS NOT
An entry is made to SYS1.LOGREC. No SVC dump is
AVAILABLE
taken.
Explanation:
CSECT DSN3UR00 detected that the subsystem DSN3104I csect-name - TERMINATION
recognition character is invalid; it must be nonblank. COMPLETE
The subsystem recognition character is the last field of
Explanation:
the parameter string passed to DB2 IPL initialization. It
is obtained from a record for the named subsystem in This message indicates that a DB2 subsystem has
member IEFSSNxx of SYS1.PARMLIB. terminated. The actual MVS termination of the DB2
address space(s) may have completed earlier. This
The subsystem recognition character is not inserted in
message is presented for every termination, normal or
this message as it cannot be determined. ’ssnm’ is the
abnormal.
name of the DB2 subsystem undergoing IPL-time
initialization. Operator response:
System action: Issue a DISPLAY ACTIVE command to see if MVS has
completed termination processing of the address
The DB2 subsystem with the indicated name is not
space(s).
available for this IPL of MVS.
Operator response:
DSN3105I csect-name - UNABLE TO LOAD EARLY
Notify the system programmer. Correct the parameter PROCESSING MODULE ’DSN3EPX’
fields in the SYS1.PARMLIB record of member ssnm IS NOT AVAILABLE
IEFSSNxx, and re-IPL MVS. Refer to Part 2 of
Explanation:
Installation Guide for the format of an IEFSSNxx record
which defines a DB2 subsystem. CSECT DSN3UR00 is unable to load the early
processing module DSN3EPX required for MVS. The
name of the DB2 subsystem undergoing IPL-time
DSN3103I csect-name - UNABLE TO LOAD EARLY
initialization is ’ssnm’. Either the load module has been
PROCESSING MODULE SPECIFIED IN
inadvertently deleted, or does not reside in a library
PARMLIB RECORD. ssnm IS NOT
included in the MVS linklist.
AVAILABLE
System action:
Explanation:
DSN3UR00 abends with code X’04E’ and reason code
CSECT DSN3UR00 is unable to load the early
X’00F30105’. DB2 subsystem ’ssnm’ is not available for Enter the command from another console that has
this IPL of MVS. ’system’ authority.
Operator response: System programmer response:
Notify the system programmer. Verify that this console should be used for entering
DB2 commands. If so, authorize it for ’system’
System programmer response:
commands by using MVS services.
Identify the cause of the error. Either correct the early
processing load module or take the necessary steps to
DSN3108I csect-name COMMAND REJECTED.
include the module in a link-listed library. Re-IPL MVS.
COMMAND FACILITY PATH
Refer to Diagnosis Guide and Reference for information UNAVAILABLE
on identifying and reporting the problem.
Explanation:
Problem determination:
CSECT DSN3EC0X has discovered that the path from
An entry is made in SYS1.LOGREC. No SVC dump is MVS consoles to the DB2 command processor is
taken. Refer to MVS linklist requirements in MVS/ESA unavailable. It may still be possible to enter commands
JES2 Initialization and Tuning Guide. through one of the attachment facilities.
The command is not processed. In the message, ’nn’ is the return code from the
IEFSSREQ MVS service. ’ssnm’ is the name of the DB2
Operator response: subsystem undergoing IPL-time initialization.
Start the DB2 subsystem, then reenter the command. System action:
DSN3UR00 abends with completion code X’04E’ and
DSN3107I csect-name COMMAND REJECTED. reason code X’00F30104’. The DB2 subsystem with the
REQUESTER NOT AUTHORIZED indicated name is not available for this IPL of MVS.
Explanation: Operator response:
CSECT DSN3EC0X has discovered that the source of Notify the system programmer.
the command was a console that does not have
’system’ authority. System programmer response:
754 Messages
DSN3111I • DSN3113I
System programmer response: Your job or TSO session cannot be canceled. The PA1
key has no effect in this circumstance. To avoid long
The version of the DB2 early code that was loaded waits when your application program is canceled or
from the LINKLIST library is not compatible with the terminates abnormally, issue frequent commits.
release of MVS that you are using. Change the
concatenation order of the LINKLIST library so that a Problem determination:
compatible release of DB2 early code is used.
756 Messages
DSN3458I • DSN3581I
You can detect a deferred termination condition for a code of ’00F30580’ The DB2 subsystem terminates.
task by examining several indicators. Some or all of the
Operator response:
following might be present:
v The allied address space might be swapped out and Notify the system programmer.
appear to be in a never-ending WAIT condition. System programmer response:
v The MVS commands CANCEL and FORCE appear to
have no effect. Restart the DB2 subsystem.
An authorization exit load module was not link-edited csect The CSECT name of the DB2 module that
with the 31-bit addressing mode (AMODE) attribute. issued the message.
Either load module DSN3@ATH or DSN3@SGN is service The name of the service that failed.
specified by ’modname’.
saf-retc The SAF return code.
System action:
racf-retc
Subsystem startup is terminated. The RACF return code.
System programmer response: db2-retc
Relink-edit the authorization exit module specifying the The DB2-assigned reason code for the failure.
attributes AMODE(31), RMODE(ANY). DB2 associates the failure with a DB2 reason
Problem determination: code which may appear in other messages
associated with this failure.
Check the load module attributes used for the link-edit.
System action:
DSN3580I CONNECTION FOR [EOM | FEOT | The call fails. Other messages associated with this
IDEN] GAVE RC=X xxxxxxxx, feature may follow.
REASON=X xxxxxxxx Operator response:
Explanation: Notify the system programmer.
A nonzero return code has been returned to System programmer response:
DSN3AMI2 from the SSSS connect to subsystem
interface call. The variables in the message indicate The action to take depends on the service being used.
which SSI call is involved and the actual return and v R_ticketserv
reason codes associated with it.
DB2 requests this service to parse a Kerberos ticket
System action: received from a remote client. Refer to OS/390
Security Server (RACF) Callable services for an
The current task (TCB) is abended with a system explanation of the error.
completion code of X’04E’ and with an abend reason
758 Messages
Chapter 24. DSN5 messages
Message identifiers that begin with DSNQ5 communicate information about DB2.
System action:
DSN7000I csect-name REQUIRED CSECT
DSN6GRP COULD NOT BE FOUND DB2 startup continues normally. DB2 ignores the
IN SYSTEM PARAMETERS LOAD LIGHT(YES) specification.
MODULE.
Explanation: DSN7100I csect-name
The required CSECT DSN6GRP was not found in the Explanation:
system parameters load module.
This message indicates the beginning of the output
System action: from a DISPLAY GROUP command. It is the first line
of a multi-line message response.
The DB2 subsystem terminates with reason code
00F70001.
| DSN7101I *** BEGIN DISPLAY OF
Operator response:
| GROUP(group-name) GROUP LEVEL
Restart DB2 with the correct system parameters load | (group-level) MODE (nn)
module.
| Explanation:
System programmer response:
| This message is a line of output from a DISPLAY
Reassemble the system parameters load module and | GROUP command.
include the DSN6GRP macro.
| group-name
| The name of the data sharing group.
DSN7001I csect-name DATA SHARING SPECIFIED
IN SYSTEM PARAMETERS, BUT NOT
| group-level
RUNNING ON A MVS SYSTEM
| A string of three numeric characters:
LEVEL WHICH IS REQUIRED FOR | v Version
DATA SHARING. | v Release
Explanation: | v Modification level
A DB2 subsystem was started with the data sharing | nn Two characters that indicate the mode of the
option, but MVS is not at the required level. DB2 data | system and can have the following possible
sharing requires MVS Version 5 Release 1.0 or a later | values:
release. | C Conversion mode
System action: | E Enabling-new-function mode
The DB2 subsystem terminates with reason code | N New-function mode
00F70002.
| C* Conversion mode but the system
Operator response: | detects that it has been to a higher
Restart DB2 on MVS Version 5 Release 1.0 or a later | level
release. | E* Enabling-new-function mode but the
| system detects that it has been to a
DSN7002I LIGHT(YES) ON START DB2 | higher level
COMMAND WAS IGNORED, SYSTEM |
IS NOT ENABLED FOR DATA DSN7102I -----------------------------
SHARING
Explanation:
Explanation:
This message is a line of output from a DISPLAY
DB2 issues this message during DB2 startup if DB2 is GROUP command.
started with the LIGHT(YES) keyword and the system
is not enabled for data sharing.
SYSTEM NAME
DSN7103I DB2 DB2 SYSTEM IRLM
Name of the MVS system on which the data
Explanation: sharing member runs.
This message is a line of output from a DISPLAY IRLM SUBSYS
GROUP command. The accompanied IRLM’s subsystem name for
this DB2.
DSN7104I MEMBER ID SUBSYS CMDPREF IRLMPROC
STATUS LVL NAME SUBSYS The accompanied IRLM’s startup procedure
IRLMPROC name.
Explanation:
DSN7105I -------- --- ---- -------- -------- --- -------- ----
This message is a line of output from a DISPLAY
--------
GROUP command.
Explanation:
MEMBER
Name of the DB2 data sharing member. This message is a line of output from a DISPLAY
GROUP command.
ID Internally assigned ID for each data sharing
member.
DSN7106I member-name subsystem-name
SUBSYS
command-prefix member-status
Subsystem name of the data sharing member.
mvs-system-name irlm-subsystem-name
CMDPREF irlm-procedure-name
Command prefix of the data sharing member.
Explanation:
STATUS
This message is a line of output from a DISPLAY
State of the data sharing member, which can
GROUP command. member-status can be ACTIVE,
be ’ACTIVE’, ’AI’, ’FAILED’, ’QUIESCED’,
QUIESCED, or FAILED. member-status may also have
’QI’, ’QR’, ’QC’, ’QIC’, ’QIR’, or ’QICR’ where:
the string ’***’ as output if the member has not been
ACTIVE quiesced normally.
The member is currently up and
QUIESCED
running.
This is a normal quiesced state, as the result of
AI The member is active with additional a normal STOP DB2 command.
conditions. Indoubt or postponed
Q The member is quiesced, but with additional
abort units of recovery are
conditions. Q (quiesced) can be paired with
outstanding. This means retained
one or more of the following letters:
locks are held.
I Indoubt units of recovery (URs) are
FAILED
outstanding. This means retained
The member has terminated
locks are held.
abnormally.
C There was a castout error. The last
QUIESCED
updated of the page set or partition
The member is down normally.
could not write from the coupling
QI The member is down with indoubt facility to DASD.
URs.
Make sure there is connectivity from
QR The member is down with the coupling facility to DASD before
resynchronization responsibility. restarting DB2.
762 Messages
DSN7107I • DSN7111I
A The member is active, but with the additional DS SCA loss of connectivity, delayed action
conditions. A (active) can be paired with the started.
following letter:
DC SCA loss of connectivity, delayed action
I Indoubt or postponed abort units of completed.
recovery (URs) are outstanding. This
QS SCA rebuild quiesce function started.
means retained locks are held.
QC SCA rebuild quiesce function completed.
*** Usually issued if the member has not been
quiesced normally. The string ’***’ may also be CS SCA rebuild connect function started.
paired with the following:
CC SCA rebuild connect function completed.
**** Information unknown. This may
result if an unwanted member was OS SCA rebuild connect complete function started.
previously added to the group, and RS SCA rebuild resource manager invocation
continues to be named in other started.
locations.
RC SCA rebuild resource manager invocation
The subsystem-name, command-prefix, completed.
irlm-subsystem-name, and irlm-procedure-name show ’****’ OC SCA rebuild connect complete function
if this information is unknown. completed.
LS SCA rebuild cleanup function started.
DSN7107I PROTOCOL LEVEL(protocol-level)
GROUP ATTACH NAME(group-attach) US SCA rebuild resource manager invocation
started.
Explanation:
UC SCA rebuild resource manager invocation
This message is a line of output from a DISPLAY completed.
GROUP command.
LC SCA rebuild cleanup function completed.
group-attach is the group attach name for the data
sharing group. PS SCA rebuild process complete function started.
| protocol-level indicates the current locking protocol used PC SCA rebuild process complete function
| in the data sharing group. completed.
SS SCA rebuild stop function started.
DSN7108I NUMBER LOCK ENTRIES: SC SCA rebuild stop function completed.
nnnnnnnnnnn
ES SCA rebuild stop complete function started.
Explanation:
EC SCA rebuild stop complete function
This line of output from a DISPLAY GROUP command completed.
shows information about the LOCK1 coupling facility
structure. The maximum number of lock table entries is VS SCA volatility change function started.
displayed. VC SCA volatility change function completed.
TE SCA is in termination phase.
DSN7109I SCA STRUCTURE SIZE: nnnnnnn KB,
STATUS = xx, SCA IN USE: < nnn %
DSN7110I LOCK1 STRUCTURE SIZE: nnnnnnn KB
Explanation:
Explanation:
This message is a line of output from a DISPLAY
GROUP command. This line of output from a DISPLAY GROUP command
shows the size of the LOCK1 coupling facility structure.
If the % value is > 0 but < 1, then a ″<″ character is
shown before the 1 % value, e.g. ″< 1 %″. This can
happen if the shared communications area (SCA) DSN7111I NUMBER LIST ENTRIES: nnnnnnnnnnn,
structure is very large or if only a small number of LIST ENTRIES IN USE: < nnnnnnnnnnn
SCA entries are in use.
Explanation:
The SCA status can have following values:
This line of output from a DISPLAY GROUP command
IN SCA is in initialization phase. shows information about the LOCK1 coupling facility
structure. The maximum number of modify lock list
AC SCA is active. entries and the number of those entries currently in use
DSN7121I MEMBER COORDINATOR enable-newfunction indicates whether this table space has
ASSISTANT been converted to UNICODE during the enabling new
function mode process.
Explanation:
This message is a line of output from a DISPLAY DSN7401I csect-name INCONSISTENT DATA
GROUP command with the DETAIL option. SHARING PARAMETER DETECTED,
parameter-name IN DB2 SYSTEM
DSN7122I -------- ----------- --------- PARAMETERS (sysparm-parm) IS NOT
EQUAL TO PARAMETER IN THE DB2
Explanation: START-UP PROCEDURE (start-parm).
This message is a line of output from a DISPLAY Explanation:
GROUP command with the DETAIL option.
At least one data sharing parameter in the member’s
764 Messages
DSN7403I • DSN7407I
system parameters is not equal to the data sharing Investigate which unauthorized program joined the
parameter value passed on the DB2 start-up procedure. DB2 group and find its owner. This could indicate a
security violation.
System action:
The DB2 subsystem terminates with reason code
DSN7405I csect-name MEMBER(member-name)
00F70003.
UNABLE TO JOIN DATA SHARING
Operator response: GROUP(group-name), MVS IXCJOIN
RETURN CODE=xxxxxxxx, MVS
Restart DB2 with the correct system parameters load IXCJOIN REASON CODE=yyyyyyyy.
module or inform the system programmer to change
the DB2 start-up procedure. Explanation:
System programmer response: An unexpected error occurred when the data sharing
DB2 member attempted to join the MVS cross-system
Reassemble the system parameters load module. Make coupling facility (XCF) data sharing group.
sure that the group name and the member name match
the values in the DB2 start-up procedure, or correct the System action:
parameters on the DB2 start-up procedure.
The DB2 subsystem terminates with reason code
00F70408.
DSN7403I csect-name MEMBER(member-name) IS
Operator response:
ALREADY ACTIVE ON
SYSTEM(mvs-system-name). Issue an MVS ’DISPLAY XCF,GROUP’ command to
ensure that XCF is functional; then try to restart the
Explanation:
DB2 subsystem.
The started DB2 subsystem is already active on another
System programmer response:
MVS system.
Refer to MVS/ESA Programming: Sysplex Services
System action:
Reference for an explanation of the IXCJOIN return and
The DB2 subsystem terminates with reason code reason codes.
00F70003.
Operator response: DSN7406I csect-name UNABLE TO QUERY DATA
SHARING GROUP INFORMATION,
If you want the DB2 subsystem to run on this MVS MVS IXCQUERY RETURN
system, stop the DB2 subsystem on the other MVS. CODE=xxxxxxxx, MVS IXCQUERY
After the DB2 subsystem stops, restart the DB2 on this REASON CODE=yyyyyyyy.
MVS.
Explanation:
Explanation:
DSN7501A csect-name SCA STRUCTURE
DB2 encountered an error using the specified MVS sca-structure-name CONNECTIVITY
automatic restart manager (ARM) function. FAILURE.
DB2 continues. However, if DB2 abnormally terminates, The specified DB2 member lost connectivity to the
the MVS ARM cannot automatically restart DB2. shared communication area (SCA) structure.
Refer to MVS/ESA Programming: Sysplex Services The specified DB2 disconnects from the SCA and
Reference for the function, return code, and reason code terminates with reason code 00F70600.
from the IXCARM request.
Operator response:
Notify the system programmer.
DSN7408I csect-name ARM EVENT EXIT FAILED.
DB2 SUBSYSTEM ssnm NOT System programmer response:
RESTARTED. MVS IEFSSI RETURN
Find out why the link from this central processor
CODE = xxxxxxxx, MVS IEFSSI
complex (CPC) to the SCA structure was lost. After
REASON CODE = yyyyyyyy.
fixing it, restart DB2.
Explanation:
The DB2 ARM event exit encountered an error while DSN7502I csect-name SCA STRUCTURE
attempting to define the DB2 subsystem to MVS. sca-structure-name FAILURE, ATTEMPT
TO REBUILD IS IN PROGRESS.
System action:
Explanation:
The automatic restart of the DB2 subsystem is stopped.
The specified DB2 member detected the shared
System programmer response:
communications area (SCA) structure failure.
Refer to MVS/ESA Programming: Assembler Services
System action:
Reference for return and reason codes from the IEFSSI
request. If the IEFSSI return code and reason code are DB2 tries to rebuild the SCA structure on a coupling
0, look in the console log for previous messages that facility in the preference list for the coupling facility.
indicate why the definition of the DB2 subsystem
Operator response:
failed. You can manually start DB2 by using the
-START DB2 command on any system where the DB2 Wait for message DSN7503I or DSN7504A.
subsystem is defined.
766 Messages
DSN7505A • DSN7508I
its information in the shared communications area If you don’t do anything to reclaim space, message
(SCA). This message follows message DSN7502I. DSN7512A appears when the SCA is 90 percent full.
04 An operator requested to stop the rebuild
process. DSN7506A csect-name CONNECT TO THE SCA
STRUCTURE sca-structure-name FAILED.
08 A DB2 resource manager requested to stop the
MVS IXLCONN RETURN
rebuild process.
CODE=xxxxxxxx, MVS IXLCONN
12 The new SCA structure failed during the REASON CODE=yyyyyyyy.
rebuild process.
Explanation:
16 A DB2 member lost connectivity to the new
DB2 cannot connect to the shared communications area
SCA in the rebuild process.
(SCA) coupling facility structure.
20 An MVS service used during the rebuild
System action:
process failed. A message was issued from the
failed MVS service. DB2 startup terminates with reason code 00F70602.
System action: System programmer response:
This DB2 member terminates with reason code DB2 uses the MVS IXLCONN service to connect to the
00F70601. Other members can continue processing. SCA structure. Refer to MVS/ESA Programming: Sysplex
Services Reference for return and reason codes from the
System programmer response:
IXLCONN request.
See the termination code for more details.
DSN7507I csect-name SCA STRUCTURE
DSN7505A csect-name THERE IS A SHORTAGE OF sca-structure-name IS ALLOCATED IN A
FREE STORAGE IN SCA STRUCTURE VOLATILE STRUCTURE.
sca-structure-name
Explanation:
Explanation:
The shared communications area (SCA) structure is
The amount of free storage in the shared volatile.
communications area (SCA) coupling facility structure
System action:
is low. The SCA is 75 percent full. Because SCA storage
space is required by some DB2 commands and DB2 processing continues.
processes, the availability of those processes might be
System programmer response:
affected. Completely running out of SCA storage can
cause DB2 subsystem outages. One DB2 issues this message whenever the structure
has the volatile attribute. DB2 detects this either on the
This message stays on the MVS console and is
first connection to the SCA or on the attribute changes
highlighted.
later. DB2 always requests a nonvolatile SCA. If this is
System action: not what you want, change the MVS CFRM
administrative policy and request a rebuild of the SCA
DB2 processing continues.
with the MVS SETXCF START,REBUILD command.
This message might remain highlighted and might not
be automatically deleted in a pre SP5.2.1-JES3
DSN7508I csect-name ACCESS TO THE SCA
environment.
STRUCTURE sca-structure-name FAILED.
Operator response: MVS IXLLIST RETURN CODE =
xxxxxxxx, MVS IXLLIST REASON
If the message remains highlighted after the error CODE = yyyyyyyy.
situation is cleared up, manually delete the message
from the console. Explanation:
You can free SCA storage by removing exception DB2 terminates with reason code 00F70603.
conditions. Another thing you can do is issue START
System programmer response:
DATABASE commands with the SPACENAM option or
use the RECOVER utility to remove pages from the DB2 uses the MVS IXLLIST service to access the SCA
logical page list (LPL). structure. Refer to MVS/ESA Programming: Sysplex
DSN7511I csect-name RESPONSE TO MVS If your actions do not free up enough space, or if the
REBUILD COMPLETE OF SCA problem continues to occur, you have the following
STRUCTURE sca-structure-name FAILED. options, depending on what level of MVS and the
MVS IXLREBLD RETURN CODE = coupling facility control code you are running with:
xxxxxxxx, MVS IXLREBLD REASON v If all members of the group are running with MVS
CODE = yyyyyyyy. Version 5 Release 2 and with a coupling facility
Explanation: control code level greater than 0, issue the SETXCF
START,ALTER command to increase the size of the
DB2 encountered an error during the rebuild of the SCA. The size you specify must be less than or equal
shared communications area (SCA) structure. to the maximum size defined the CFRM policy for
the SCA structure.
System action:
If the maximum size (SIZE in the CFRM policy) is
DB2 stops. still not big enough, take the actions described below
System programmer response: for MVS Version 5 Release 1 systems.
v If any or all members of the group are running with
DB2 uses the MVS IXLREBLD service during the SCA
MVS Version 5 Release 1 or with a coupling facility
structure rebuild. Refer to MVS/ESA Programming:
control code level of 0, increase the storage for the
Sysplex Services Reference for return and reason codes
SCA in the CFRM policy. Then issue the MVS
from the IXLREBLD request.
SETXCF START,REBUILD command to rebuild the
structure.
768 Messages
DSN7513I • DSN7514I
If the error is unexpected, list the contents of the List the contents of the employee view, VEMP, and the
employee and department views VEMP and VDEPT to department view, VDEPT.
determine why the entry is missing.
DSN8006E csect EMPLOYEE DOES NOT EXIST,
DSN8002I csect EMPLOYEE SUCCESSFULLY ERASE NOT DONE
ADDED
Explanation:
Explanation:
The erase requested was not performed. The employee
Employee data was added as requested. number requested was not present in the table.
772 Messages
DSN8017E • DSN8025E
If the error is unexpected, list the contents of the If a ’higher’ department was not expected to be found,
department views VDEPT and VDEPMG1 and their continue processing.
underlying tables to determine why the entry is
Problem determination:
missing.
List the contents of the department views VDEPMG1,
VEMP, VASTRDE1, and VASTRDE2 and their
DSN8017E csect DEPARTMENT DOES NOT EXIST,
underlying tables.
UPDATE NOT DONE
Explanation:
DSN8021I csect ACTIVITY NOT FOUND
The update request found no department data which
Explanation:
matches your request.
No activities match the selection criteria.
System action:
System action:
No department data is updated.
No activity is listed.
User response:
User response:
See if the department data to be updated should exist.
If you did not enter the correct combination of search If no activity was expected to be found, continue
criteria and data, correct the entries and continue. processing.
Problem determination: Problem determination:
If the error is unexpected, list the contents of the List the contents of the activity views VPROJRE1,
department views VDEPT and VDEPMG1 and their VACT, and VPROJACT and their underlying tables.
underlying tables to determine why the entry is
missing.
DSN8022I csect ACTIVITY SUCCESSFULLY
ADDED
DSN8018I csect CURRENT DEPARTMENT NOT
FOUND Explanation:
If the ’current’ department was not expected to exist, An activity was erased as requested.
continue processing. System action:
Problem determination: The request was executed successfully.
List the contents of the department views VDEPMG1,
VEMP, VASTRDE1, and VASTRDE2 and their DSN8024I csect ACTIVITY SUCCESSFULLY
underlying tables. UPDATED
Explanation:
DSN8019E csect NO HIGHER DEPARTMENT
EXISTS An activity was updated as requested.
A request was made by a ’current’ department to The request was executed successfully.
reference a ’higher’ level of the department structure. A
’higher’ level does not exist for the requested ’current’ DSN8025E csect ACTIVITY EXISTS ALREADY,
department. ADD NOT DONE
System action: Explanation:
No department data is processed. The addition requested was not performed. The activity
User response: requested was already present.
Explanation:
DSN8035E csect PROJECT EXISTS ALREADY, ADD
The add or update was not performed. The activity NOT DONE
type entered was not found.
Explanation:
System action:
You requested that a new project be added, but the
No activity is listed. project exists already.
774 Messages
DSN8036E • DSN8042I
System action: ’higher’ project. The ’current’ project was not found.
The request was not executed successfully. System action:
User response: No project data is processed.
Display the existing project. If it is what you want, User response:
continue. If not, you can update this project or choose a
If the ’current’ project was not expected to be found,
new project id.
continue processing.
Problem determination:
Problem determination:
If the error was unexpected, list the contents of the
List the contents of the project views VPROJRE1,
project view VPROJ and its underlying tables to see if
VDEPT, VEMPPROJACT, VEMP, VSTAFAC1,
the data differs from what is expected.
VSTAFAC2, VPSTRDE1, and VPSTRDE2 and their
underlying tables.
DSN8036E csect PROJECT DOES NOT EXIST,
ERASE NOT DONE
DSN8039E csect NO HIGHER PROJECT EXISTS
Explanation:
Explanation:
The erase request found no project which matches your
A request was made by a ’current’ project to reference a
request.
’higher’ level of the project structure. A ’higher’ level
System action: does not exist for the requested ’current’ project.
No projects are erased. System action:
User response: No project data is processed.
See if the project to be erased should exist. Did you User response:
enter the correct combination of search criteria and
If a ’higher’ project was not expected to be found,
data? If not, correct the entries and continue.
continue processing.
Problem determination:
Problem determination:
If the error was unexpected, list the contents of the
List the contents of the project views VPROJRE1,
project view VPROJ and its underlying tables to
VDEPT, VEMPPROJACT, VEMP, VSTAFAC1,
determine why the entry is missing.
VSTAFAC2, VPSTRDE1, and VPSTRDE2 and their
underlying tables.
DSN8037E csect PROJECT DOES NOT EXIST,
UPDATE NOT DONE
DSN8041I csect STAFFING NOT FOUND
Explanation:
Explanation:
The update request found no project which matches
No project staffing matches the selection criteria.
your request.
System action:
System action:
No project staffing is listed.
No projects are updated.
User response:
User response:
If no project staffing was expected to be found,
See if the project to be updated should exist. If you did
continue processing.
not enter the correct combination of search criteria and
data, correct the entries and continue. Problem determination:
Problem determination: List the contents of the project activity views
VPROJRE1, VEMPPROJACT, VACT, and VEMP and
If the error is unexpected, list the contents of the
their underlying tables.
project view VPROJ and its underlying tables to
determine why the entry is missing.
DSN8042I csect STAFFING SUCCESSFULLY
ADDED
DSN8038I csect CURRENT PROJECT NOT
FOUND Explanation:
Explanation: A project staffing was added as requested.
A request was made by a ’current’ project to reference a System action:
The request was executed successfully. VPROJRE1, VEMPPROJACT, VACT, and VEMP and
their underlying tables.
DSN8043I csect STAFFING SUCCESSFULLY
ERASED DSN8047E csect STAFFING DOES NOT EXIST,
UPDATE NOT DONE
Explanation:
Explanation:
A project staffing was erased as requested.
The update was not performed because the project
System action:
staffing requested was not found.
The request was executed successfully.
System action:
No project staffing is updated.
DSN8044I csect STAFFING SUCCESSFULLY
UPDATED User response:
Explanation: Determine if the project staffing to be updated should
exist. Verify that the correct search criteria and data
A project staffing was updated as requested.
were entered. If appropriate, correct the entries and
System action: continue processing.
776 Messages
DSN8057I • DSN8066E
DSN8058I csect PRESS PA1 FOR NEXT PAGE / DSN8064E csect INVALID DL/I STC-CODE ON GU
ENTER FOR SELECTION MENU MSG: status-code
Explanation: Explanation:
Press the PA1 key to see the data on the next page or In attempting to get a message from IMS, an
press the ENTER key to return to the selection menu. unexpected status-code was received.
User response: System action:
Press the PA1 key or the ENTER key depending on the The application program is terminated.
function you want to perform.
Problem determination:
Refer to the messages and codes manual for IMS/VS to
DSN8060E csect SQL ERROR, RETURN CODE IS:
determine the reason for the unexpected status code.
sqlcode
Explanation:
DSN8065E csect INVALID DL/I STC-CODE ON
The SQL statement did not execute correctly. The ISRT MSG: status-code
’sqlcode’ can be found elsewhere in this manual. This
Explanation:
may be an SQL error or an SQL warning.
In attempting to insert a message for IMS, an
System action:
unexpected status-code was received.
The request was not executed successfully.
System action:
User response:
The application program is terminated.
Refer to Codes for more information about the error.
Problem determination:
Problem determination:
Refer to the messages and codes manual for IMS/VS to
Determine which SQL statement in the application determine the reason for the unexpected status code.
program caused the error and see if it is reproducible.
Follow the diagnosis approach suggested for the
DSN8066E csect UNSUPPORTED PFK OR LOGIC
sqlcode.
ERROR
Explanation:
DSN8061E csect ROLLBACK FAILED, RETURN
CODE IS: sqlcode The sample application found an unsupported program
function key or logic error while trying to execute a
Explanation:
request.
The SQL ROLLBACK statement was not executed
System action:
correctly.
The request was not executed successfully.
System action:
User response:
The request was not executed successfully.
Report the error in the application program.
User response:
Refer to Codes.
Problem determination:
Determine which SQL statement in the application
Explanation: You entered a number that is not in the list on the left
under the heading NO for line number. Enter a valid
The input must begin with ’L’ or ’U’. number.
System action: Problem determination:
The request is ignored. If the line number you entered is in the list on the left
under the heading NO for line number, then the error
User response:
is in the sample program.
Correct the input request.
DSN8073E csect SPECIFIED LINE-NUMBER NOT
DSN8069E csect NO VALID SELECTIONS FOUND IN PREVIOUS SCREEN
QUALIFY FOR THIS REQUEST
Explanation:
Explanation:
You gave an invalid line number.
You entered a search criteria value and a data values
System action:
that do not find any selections.
The request was not executed successfully.
System action:
User response:
The request was not executed successfully.
You entered a number that is not in the list on the left
User response:
under the heading NO for line number. Enter a valid
Enter new search criteria values. number. If the line number is in the previous screen,
then this is an error in the sample program. Report the
Problem determination:
error.
If the criteria values you entered are expected to
provide valid selections, check the contents of the view
DSN8074E csect DATA IS TOO LONG FOR
and the underlying tables to see if the data differs from
SEARCH CRITERIA
what is expected. If after checking the view and the
underlying tables, you find the search criteria values Explanation:
you entered should provide valid selections, the error is
You entered a data value that has too many characters
in the sample program. Report the error.
for the type of search criterion you selected. For
example, department ids have a maximum of 3
characters and most other ids have a maximum of 6
characters.
778 Messages
DSN8075E • DSN8082E
DSN8083E AN UNKNOWN SERVICE service WAS DSN8203E csect INVALID WORK DEPT,
REQUESTED EMPLOYEE NOT UPDATED
Explanation: Explanation:
The user is requesting an invalid service. The employee that is to be updated has a department
number that is not contained in the table DEPT. The
System action:
update cannot be completed.
The requested service was not executed.
System action:
System programmer response:
No employee data is updated.
The service request must be a valid call attachment
User response:
facility service. Ensure that the request is one of the
services supported by the call attachment facility. Ensure that the correct department number was
entered.
User response:
Problem determination:
Notify the system programmer.
List the contents of the employee table DEPT.
Problem determination:
There is an error in the Sample Application Program.
DSN8210I csect INVALID MGRNO,
DEPARTMENT NOT ADDED
DSN8200E csect INVALID DEPARTMENT
Explanation:
NUMBER, EMPLOYEE NOT ADDED
The department that is to be added has a manager
Explanation:
number that is not contained in the table EMP. The add
The employee number that is to be added refers to a cannot be completed.
department number that is not contained in the table
System action:
DEPT.
No department is added.
System action:
User response:
The employee number is not added.
Ensure that the correct manager number was entered.
User response:
Problem determination:
Ensure that the correct department number was
entered. List the contents of the employee table EMP.
Problem determination:
DSN8212E csect DEPARTMENT NUMBER HAS
List the contents of the department table DEPT.
DEPENDENT ROWS, NOT ERASED
Explanation:
DSN8202E csect EMPLOYEE NUMBER HAS
DEPENDENT ROWS, NOT ERASED The department number that is to be erased is the same
as a project department number in table PROJ. The
Explanation:
department cannot be erased.
The employee number to be erased is the same as a
System action:
responsible employee number in the table PROJ or an
employee number in the table EMPPROJACT. The No department data is erased.
employee number cannot be erased from the table EMP.
User response:
System action:
Ensure that the correct department number was
No employee data is erased. entered.
User response: Problem determination:
Ensure that the correct employee number was entered. List the contents of the project table PROJ.
Problem determination:
List the contents of the PROJ and EMPPROJACT tables.
780 Messages
DSN8213E • DSN8220E
DSN8213E csect INVALID ADMIN DEPT ID, DSN8216E csect DEPT NOT AT SPECIFIED
DEPARTMENT NOT ADDED LOCATION, EMPLOYEE NOT ADDED
Explanation: Explanation:
The department that is to be added has a department The employee number that is to be added refers to a
number that is not contained in the table DEPT. The department number whose LOCATION field in the
add cannot be completed. DEPT table is different from that specified for the
employee. The add cannot be completed.
System action:
System action:
No department is added.
No employee is added.
User response:
User response:
Ensure that the correct department number was
entered. Ensure that the correct department number was
entered.
Problem determination:
Problem determination:
List the contents of the employee table DEPT.
List the contents of the department table DEPT.
DSN8214E csect INVALID MANAGER ID,
DEPARTMENT NOT UPDATED DSN8217E csect DEPT NOT AT SPECIFIED
LOCATION, EMP NOT UPDATED
Explanation:
Explanation:
The department that is to be updated has a manager
number that is not contained in the table EMP. The The employee number that is to be updated refers to a
update cannot be completed. department number whose LOCATION field in the
DEPT table is different from that specified for the
System action:
employee. The update cannot be completed.
No department data is updated.
System action:
User response:
No employee data is updated.
Ensure that the correct manager number was entered.
User response:
Problem determination:
Ensure that the correct department number was
List the contents of the employee table EMP. entered.
Problem determination:
DSN8215E csect INVALID ADMIN DEPT ID,
List the contents of the department table DEPT.
DEPARTMENT NOT UPDATED
Explanation:
DSN8220E csect INVALID PROJECT NUMBER,
The department that is to be updated has a ACTIVITY NOT ADDED
administrative department number that is not in the
Explanation:
table DEPT. The update cannot be completed.
The activity that is to be added contains a project
System action:
number that is not contained in the table PROJ. The
No department data is updated. add cannot be completed.
Ensure that the correct department number was The activity is not added.
entered.
User response:
Problem determination:
Ensure that the correct project number was entered.
List the contents of the employee table DEPT.
Problem determination:
List the contents of the project table PROJ.
DSN8222E csect ACTIVITY HAS DEPENDENT DSN8231E csect INVALID RESPONSIBLE ID,
ROWS, NOT ERASED PROJECT NOT ADDED
Explanation: Explanation:
The activity that is to be erased from table PROJACT is The project that is to be added contains an employee
the same as the corresponding activity in the table number that is not contained in the table EMP. The add
EMPPROJACT. The activity cannot be erased from the cannot be completed.
table PROJACT.
System action:
System action:
No project is added.
No activity data is erased.
User response:
User response:
Ensure that the correct employee number was entered.
Ensure that the correct activity was entered.
Problem determination:
Problem determination:
List the contents of the employee table EMP.
List the contents of the PROJACT and EMPPROJACT
tables.
DSN8233E csect PROJECT NUMBER HAS
DEPENDENT ROWS, NOT ERASED
DSN8223E csect ACTIVITY HAS DEPENDENT
Explanation:
ROWS, NOT UPDATED
A project number in table PROJ is to be erased, but it is
Explanation:
the same as a project number in table PROJACT. The
A start date in table PROJACT is to be updated, but project cannot be erased from table PROJ.
there is a project staffing for this activity in table
System action:
EMPPROJACT. The start date in table PROJACT cannot
be updated. No project is erased.
System action: User response:
No activity data is updated. Ensure that correct project number was entered.
User response: Problem determination:
Ensure that the correct start date was entered. List the contents of the PROJ and PROJACT tables.
Problem determination:
DSN8235E csect INVALID MAJOR PROJECT ID,
List the contents of the project-activity-staffing table
PROJECT NOT ADDED
EMPPROJACT and project-activity table PROJACT.
Explanation:
DSN8230E csect INVALID DEPARTMENT The project that is to be added contains a major project
NUMBER, PROJECT NOT ADDED ID that is not contained in the table PROJ. The add
cannot be completed.
Explanation:
System action:
The project that is to be added contains a department
number that is not present in the table DEPT. The add No project is added.
cannot be completed.
User response:
System action:
Ensure that the correct major project number was
No project is added. entered.
User response: Problem determination:
Ensure that the correct department number was List the contents of the project table PROJ.
entered.
Problem determination: DSN8236E csect INVALID ASSOCIATE DEPT ID,
PROJECT NOT UPDATED
List the contents of the department table DEPT.
Explanation:
The project that is to be updated has a department
number that is not contained in the table DEPT. The
782 Messages
DSN8237E • DSN8243E
update cannot be completed. Ensure that the correct employee number was entered.
System action: Problem determination:
No project data is updated. List the contents of employee table EMP.
User response:
DSN8242E csect INVALID PROJECT ACTIVITY
Ensure that the correct department number was
DATA, STAFFING NOT ADDED
entered.
Explanation:
Problem determination:
The staffing that is to be added refers to a project
List the contents of the department table DEPT.
number, activity number, and start date that is not
present in table PROJACT. The add cannot be
DSN8237E csect INVALID RESPONSIBLE ID, completed.
PROJECT NOT UPDATED
System action:
Explanation:
No staffing is added.
The project that is to be updated has a employee
User response:
number that is not contained in the table EMP. The
update cannot be completed. Ensure that the correct project number, activity number,
and start date were entered.
System action:
Problem determination:
No project data is updated.
List the contents of the project table PROJACT.
User response:
Ensure that the correct employee number was entered.
DSN8243E csect INVALID START DATE,
Problem determination: STAFFING NOT UPDATED
The project that is to be updated has a major project No staffing data is updated.
number that is not contained in the table PROJ. The
User response:
update cannot be completed.
Ensure that the correct start date was entered.
System action:
Problem determination:
No project data is updated.
List the contents of the project-activity table PROJACT
User response:
and the project-activity-staffing table EMPPROJACT.
Ensure that the correct project number was entered.
Problem determination:
List the contents of the project table PROJ.
System action:
DSN9000I KEYWORD keyword-name APPEARS
MORE THAN ONCE Processing for the command is terminated.
Explanation: System programmer response:
The same keyword (specified in the messages as Correct the error, and reissue the command.
’keyword-name’) appears more than once in the
command. This message will be issued for each Problem determination:
occurrence of the keyword after the first. Obtain a copy of the system or terminal log to verify
System action: the command entry.
Processing for the command is terminated. Obtain a copy of the system or terminal log to verify
command entry.
System programmer response:
Refer to Command Reference to be sure that the DSN9008I KEYWORD keyword-name MAY NOT BE
command you are using allows a subset for the named NEGATED
keyword. Correct the error, and reissue the command.
Explanation:
Problem determination:
The negation characters (NO) appear in front of the
Obtain a copy of the system or terminal log to verify keyword (specified in the message as ’keyword-name’),
command entry. but negating this keyword is not allowed. As an
example, consider a keyword called PRINT that could
indicate that you want something printed. If you did
DSN9006I KEYWORD keyword-name ASTERISK (c)
not want the material to be printed, you might specify
INCORRECTLY USED
NOPRINT. This process of prefixing a keyword with
Explanation: the characters NO is called negation. While negation
may be meaningful on some keywords, it is not
For the keyword specified in the message (as
allowed on all keywords.
’keyword-name’), an asterisk (c) was used as the first
character of a parameter to specify ALL. However, the System action:
asterisk appears in a list, or the characters in
Processing for the command is terminated.
juxtaposition are not a blank, comma, equal sign, or
parentheses. System programmer response:
Examples of such errors are LINE(LINE1,*,LINE7), Reenter the command, but do not negate the named
NAME(**), and GROUP(PQR:*). keyword. Refer to Command Reference for further
information concerning this command.
Examples of correct specification are UNIT(*) and
LINE=* etc. Problem determination:
786 Messages
DSN9009I • DSN9013I
Obtain a copy of the system or terminal log to verify the one on which you entered it.
the command entry.
System action:
Processing for the command is terminated.
DSN9009I KEYWORD keyword-name IS MISSING
AND MUST BE SPECIFIED System programmer response:
Explanation: Correct the error, and reissue the command. Refer to
Command Reference for details on how to enter the
The keyword specified in the message (as
command.
’keyword-name’) must be present, but it was not
entered. This keyword must be present in order for the Problem determination:
command to process properly.
Obtain a copy of the system or terminal log to verify
System action: the command entry.
Processing for the command is terminated.
DSN9012I KEYWORD keyword-name
System programmer response:
PARAMETER(S) MUST BE
Enter the command again, and include the specified HEXADECIMAL
keyword.
Explanation:
Problem determination:
Parameter values for the keyword specified in the
Obtain a copy of the system or terminal log to verify message (as ’keyword-name’) must be hexadecimal
the command entry. values. The value must be specified as X’hex
characters’. Hexadecimal characters are defined as the
numeric digits 0 through 9 and the letters A through F.
DSN9010I REQUIRED PARAMETER FOR
Either uppercase or lowercase is acceptable for the
KEYWORD keyword-name IS MISSING
letters A through F.
Explanation:
As an example of this error, consider the keyword
A parameter must be specified for the keyword OFFSET, for which you are expected to enter a
specified in the message (as ’keyword-name’), but no hexadecimal value. If you enter OFFSET(X’2C’), it is
parameter was entered. acceptable. However, entering OFFSET(Jones) is not
acceptable.
As an example of this error, consider a keyword called
PRIORITY whose value can range from 0 to 9. System action:
Specification of PRIORITY(1) is acceptable, but, if you
Processing for the command is terminated.
specify PRIORITY with no parameter value, the
keyword is meaningless. System programmer response:
System action: Reissue the command, but ensure that the parameters
for the named keyword are hexadecimal values.
Processing for the command is terminated.
Problem determination:
System programmer response:
Obtain a copy of the system or terminal log to verify
Supply appropriate parameters for the specified
the command entry.
keyword and reissue the command. Refer to Command
Reference for valid parameter values.
DSN9013I KEYWORD keyword-name PARAMETER
Problem determination:
parameter value EXCEEDS ALLOWABLE
Obtain a copy of the system or terminal log to verify LENGTH OF nn
the command entry.
Explanation:
The parameter value (specified in the message as
DSN9011I PARAMETER(S) CANNOT BE
’parameter value’) exceeds the limit of ’nn’ characters
SPECIFIED FOR KEYWORD
in length.
keyword-name
As an example of this type of error, consider a
Explanation:
PRIORITY keyword whose value may range from zero
No parameter(s) can be specified for the keyword to nine. If you specify PRIORITY(21) or PRIORITY(006),
specified in the message (as ’keyword-name’). You may the value you have entered exceeds the limit of one
have misspelled the keyword-name, causing it to be character.
interpreted as a different keyword, or the parameter
System action:
may actually belong with another keyword instead of
Reissue the command, and enter no more than the Obtain a copy of the system or terminal log to verify
specified limit of parameters for the given keyword. If the command entry.
necessary, issue the command more than once to
process all the desired parameter values.For more
DSN9017I FAILURE WHILE PROCESSING
information, refer to Command Reference.
verb-name pkw-name COMMAND,
Problem determination: PROCESSING TERMINATED
788 Messages
DSN9018I • DSN9022I
Explanation: Explanation:
The command processor was unable to obtain sufficient Only one of the identified keywords can be specified at
storage to complete processing of any response the same time on this command.
messages generated by the invoked command.
System action:
System action:
Processing for the command is terminated.
Processing for the command is terminated abnormally.
System programmer response:
Operator response:
Identify the appropriate keyword from the list, include
Notify the system programmer before attempting to only that keyword, and reissue the command. Refer to
reissue the command. Command Reference for descriptions of the keywords.
Determine the reason for insufficient storage available Obtain a copy of the system or terminal log to verify
to the command. If a cursory examination of the system the command entry.
indicates that the region sizes for DB2 are sufficient,
and the current workload does not seem excessive, then
DSN9021I VERB verb-name REQUIRED KEYWORD
a MVS Console dump (MVS DUMP command) may be
IS MISSING
required.
Explanation:
Insure that any retry steps defined by the command are
performed prior to reissuing the command. The command specified in the message (as ’verb-name’)
was entered, but at least one required keyword is
Problem determination:
missing. The command processor was unable to
The invoked command had completed processing and determine which keyword or keywords were missing.
returned to the Command Preprocessor when an
System action:
attempt was made to obtain storage from the address
space from which the command was entered. Since Processing for the command is terminated.
sufficient storage was unavailable, no response
System programmer response:
messages from the invoked command are available.
Refer to Command Reference for the proper format of the
named command, and then reenter the command.
DSN9019I VERB verb-name IS NOT A KNOWN
COMMAND Problem determination:
Explanation: Obtain a copy of the system or terminal log to verify
command entry. If a failure is suspected, take a storage
The command represented by the verb specified in the
dump.
message is not known to the system; it is an undefined
command. A possible cause for this error is that you
made a spelling error while entering the command. DSN9022I csect-name verb-name pkw-name NORMAL
COMPLETION
System action:
Explanation:
Processing for the command is terminated.
All synchronous processing for the command specified
System programmer response:
in the message as ’verb-name pkw-name’ completed
Refer to Command Reference for the correct command successfully. Any tasks executing asynchronously for
format. the specified command might still be executing when
this message is displayed.
Problem determination:
System action:
Obtain a copy of the system or terminal log to verify
the command entry. Synchronous processing for the specified command is
complete. Subsequent system actions defined by the
command are documented in Command Reference.
The parameter of the keyword specified in the message | Reissue the command but ensure that the parameters
specifies a range using the colon operator, (for instance, | for the named keyword are of the required type.
1:3), but a range of values is not allowed.
| Problem determination:
As an example, consider a keyword called CLASS. You
| Obtain a copy of the system or terminal log to verify
might enter CLASS(1,2,3) to specify classes 1, 2, and 3,
| the command entry.
or you might enter CLASS(1:3). However, not all
commands allow you to specify a range of values.
DSN9027I KEYWORD keyword-name
System action:
PARAMETER(S) MUST BE
Processing for the command is terminated. ALPHAMERIC
Correct the keyword parameter, and reenter the Parameter values for the keyword keyword-name must
command. consist of all numbers and alphabetic characters.
keyword-name can consist of any combination of the 26
Problem determination: uppercase (A through Z) and 26 lowercase (a through
Obtain a copy of the system or terminal log to verify z) letters of the English alphabet, plus the three
command entry. characters reserved as alphabetic extenders for national
languages ($, #, and @), as well as numeric characters.
790 Messages
DSN9029I • DSN9032I
messages) must be of a specific type, such as all message identifies a subset using the asterisk operator
ALPHABETIC or all ALPHAMERIC / NATIONAL (for instance, ABC*, *ABC, or *ABC*DEF*), but using a
characters, or all NUMERIC values. subset is not allowed for this command.
As an example of this type of error, consider the As an example, consider a keyword called NAME, for
keyword NAME, where you are expected to enter a which you can specify people’s names. You might
person’s last name. If you enter NAME(Jones) it is specify NAME(ROBERT ROBERTS ROBERTSON) to
acceptable, but if you enter NAME(Jon4s), it is not enter three names, or you might specify NAME(ROB*)
acceptable. to indicate all names that begin with the characters
ROB. NAME(*BERT*) could also be specified to
As a second example, consider a keyword WEIGHT
indicate all names that contain the characters BERT
that specifies a numeric weight. Entering WEIGHT(47)
within the name. However, not all commands allow
is acceptable, but entering WEIGHT(4u) is not.
you to specify a subset of values in this way.
System action:
System action:
Processing for the command is terminated.
Processing for the command is terminated.
System programmer response:
System programmer response:
Reissue the command but ensure that the parameters
Correct the keyword parameter, and reenter the
for the named keyword are of the required type.
command.
Problem determination:
Problem determination:
Obtain a copy of the system or terminal log to verify
Obtain a copy of the system or terminal log to verify
the command entry.
command entry.
Obtain a copy of the system or terminal log to verify Obtain a copy of the system or terminal log to verify
command entry. Contact the system operator to make command entry.
sure that diagnostic information is forwarded to the
system programmer.
DSN9032I REQUESTED FUNCTION IS NOT
AVAILABLE
DSN9030I KEYWORD keyword-name PARAMETER
Explanation:
MAY NOT SPECIFY A SUBSET OF
VALUES An attempt was made to invoke a command processor
that was not loaded. An example of this is invoking
Explanation:
-START DDF or -STOP DDF when DDF is not loaded
The parameter for the keyword specified in the (not selected during the installation process).
System action:
| DSN9036I
The requested function is not performed.
| Explanation:
User response:
| This message underscores message DSN9035I and
Determine what function was requested. Do not invoke | separates the command output from another member
this function until DB2 is reinstalled and DDF is | of a data sharing group as the result of the
selected. | SCOPE(GROUP) keyword. The message number is not
| included in this message.
Problem determination:
| System action:
Look at the console log to determine which command
caused the error. | Processing continues normally.
Explanation: | Explanation:
When keyword ’name1’ is specified, keyword ’name2’ | This message follows messages DSN9035I, DSN9036I,
must also be specified. | and the command output from another member of a
| data sharing group as the result of the SCOPE(GROUP)
System action: | keyword and indicates that the output was generated
Processing for the command terminates. | successfully. The message number is not included in
| this message.
User response:
| memname
Resubmit the command with the missing keyword. | Member name for which command output is
Problem determination: | being displayed.
792 Messages
Appendix A. New, changed, and deleted messages
Messages might be added to, changed in, or removed from DB2 Version 9.1 for
z/OS.
New messages
These messages are new in DB2 Version 9.1 for z/OS.
Changed messages
These messages had significant technical changes in DB2 Version 9.1 for
z/OS.
Deleted messages
These messages have been deleted from DB2 Version 9.1 for z/OS.
New messages
These messages are new in DB2 Version 9.1 for z/OS.
DSL... messages
v DSL047I
DSNA... messages
| v DSNA320I
| v DSNA321I
| v DSNA606I
| v DSNA608I
| v DSNA609I
| v DSNA619I
| v DSNA627I
| v DSNA631I
| v DSNA632I
| v DSNA633I
DSNB... messages
| v DSNB544I
| v DSNB555I
DSNC... messages
| v DSNC101I
| v DSNC102I
| v DSNC103I
| v DSNC104I
| v DSNC105I
| v DSNC106I
| v DSNC107I
| v DSNC108I
| v DSNC109I
| v DSNC110I
| v DSNC111I
794 Messages
v DSNT727I
v DSNT555I
v DSNT557I
v DSNT558I
v DSNT570I
v DSNT571I
v DSNT740I
v DSNT741I
v DSNT742I
v DSNT743I
v DSNT744I
v DSNT745I
v DSNT746I
v DSNT747I
v DSNT748I
v DSNT749I
v DSNT750I
v DSNT751I
v DSNT752I
v DSNT753I
v DSNT758I
DSNU... messages
v DSNU021I
v DSNU186I
v DSNU395I
v DSNU435I
v DSNU436I
v DSNU447I
v DSNU448I
v DSNU449I
v DSNU485I
v DSNU632I
v DSNU634I
v DSNU636I
v DSNU696I
v DSNU697I
v DSNU698I
v DSNU699I
v DSNU758I
v DSNU767I
v DSNU778I
v DSNU820I
v DSNU821I
v DSNU822I
v DSNU823I
796 Messages
v DSNV490I
v DSNV495I
v DSNV496I
v DSNV497I
v DSNV498I
v DSNV499I
v DSNV500I
v DSNV501I
v DSNV502I
v DSNV503I
v DSNV504I
v DSNV505I
v DSNV506I
DSNW... messages
v DSNW150I
v DSNW151I
v DSNW152I
v DSNW153I
v DSNW154I
v DSNW155I
v DSNW156I
v DSNW157I
v DSNW158I
v DSNW159I
v DSNW160I
v DSNW161I
v DSNW162I
v DSNW163I
v DSNW164I
v DSNW165I
v DSNW166I
v DSNW167I
v DSNW168I
v DSNW169I
v DSNW170I
v DSNW171I
v DSNW172I
v DSNW173I
v DSNW174I
v DSNW175I
v DSNW176I
v DSNW177I
v DSNW178I
v DSNW179I
v DSNW180I
Changed messages
These messages had significant technical changes in DB2 Version 9.1 for z/OS.
Messages that had minor technical changes, editorial changes, and changes to
informational links are not included in this list.
DSN... messages
v DSN1984I
DSNB... messages
| v DSNB250E
| v DSNB402I
DSNE... messages
| v DSNE615I
| v DSNE345I
| v DSNE346I
DSNH... messages
| v DSNH034I
| v DSNH408I
798 Messages
| v DSNH527I
| v DSNH628I
| v DSNH901I
| v DSNH902I
| v DSNH4702I
DSNJ... messages
| v DSNJ407I
DSNL... messages
| v DSNL004I
| v DSNL017I
| v DSNL083I
| v DSNL084I
| v DSNL202I
| v DSNL206I
| v DSNL512I
| v DSNL521I
DSNT... messages
| v DSNT264I
| v DSNT265I
| v DSNT387I
| v DSNT389I
| v DSNT416I
| v DSNT518I
| v DSNT519I
| v DSNT556I
| v DSNT706I
| v DSNT707I
| v DSNT708I
| v DSNT712I
| v DSNT713I
| v DSNT714I
| v DSNT719I
| v DSNT720I
DSNU... messages
| v DSNU053I
| v DSNU070I
| v DSNU074I
| v DSNU100I
| v DSNU105I
| v DSNU180I
| v DSNU269I
| v DSNU283I
| v DSNU298I
| v DSNU310I
800 Messages
| v DSNY003I
| v DSNY011I
| v DSNY012I
DSN7... messages
v DSN7101I
Deleted messages
These messages have been deleted from DB2 Version 9.1 for z/OS.
DSNH... messages
| v DSNH700I
| v DSNH701I
| v DSNH702I
| v DSNH703I
| v DSNH704I
| v DSNH705I
| v DSNH706I
| v DSNH707I
| v DSNH708I
| v DSNH709I
| v DSNH710I
| v DSNH711I
| v DSNH712I
| v DSNH713I
| v DSNH714I
| v DSNH715I
| v DSNH716I
| v DSNH717I
| v DSNH718I
| v DSNH719I
| v DSNH720I
| v DSNH721I
| v DSNH722I
| v DSNH723I
| v DSNH724I
| v DSNH725I
| v DSNH726I
| v DSNH727I
| v DSNH728I
| v DSNH729I
| v DSNH730I
| v DSNH731I
| v DSNH732I
| v DSNH733I
| v DSNH734I
802 Messages
DSNU... messages
| v DSNU388I
| v DSNU389I
| v DSNU1123I
| v DSNU1605I
DSNW... messages
| v DSNW144I
| v DSNW145I
| v DSNW146I
DSNX... messages
| v DSNX952I
| v DSNX953e
| v DSNX954I
| v DSNX964I
| v DSNX965I
Functional recovery routines used by DB2 run MVS and z/OS services to provide
diagnostic information for assistance in problem determination. The following MVS
services provide diagnostic information:
SVC dumps
The DB2 abend completion code X’04E’ uses the MVS SDUMP service to
create SVC dumps. The content and storage areas associated with these
dumps vary depending on the specific error and the state of the DB2
subsystem at the time the error.
SYS1.LOGREC entries
Entries are requested in the SYS1.LOGREC data set at the time of the error
using the MVS SETRP service. The following are also recorded in
SYS1.LOGREC:
v Subsystem abnormal terminations
v Secondary abends that occur in a recovery routine
v Recording requests from recovery routines percolated to by the recovery
termination manager.
Variable recording area (VRA) data
Data entries are added to the VRA of the SDWA by using an MVS VRA
defined key. VRA data includes a series of diagnostic data entries common
to both DB2 abend completion codes. Additional information is provided
by the invoking subcomponent recovery routine during initial error
processing or recovery termination manager percolation.
During DB2 operation, an abend can occur with an MVS system completion code.
If you receive an MVS abend during DB2 operation, refer to the appropriate MVS
publication.
The following table describes the type of resource associated with the type codes.
The abbreviations in the “Name, Content, Format” column are explained in the
second table, Table 4 on page 810.
Table 3. Resource Types
TYPE Code Type of Resource Name, Content,
Format
00000100 Database DB
00000200 Table space DB.SP
00000201 Index space DB.SP
00000202 Table space RD.DB.TS
00000205 Compression Dictionary DB.SP
00000210 Partition DB.SP.PT
00000220 Data set DSN
00000230 Temporary file SZ
00000240 Database procedure DBP
00000300 Page DB.SP.PG
00000301 Index minipage DB.SP.PG.MP
00000302 Table space page DB.SP.PG
00000303 Index space page DB.SP.PG
00000304 Table space RID DB.SP.RID
00000305 Index access/table space RID DB.SP.RID
00000306 Index access/table space page DB.SP.PG
00000307 Index space EOF DB.SP.01
00000400 ICF catalog IC
00000401 Authorization function
00000402 Security Server SAF/RACF
return/reason codes
00000500 Storage group SG
00000600 EDM pool space
00000602 EDM DBD Space
00000603 EDM DYNAMIC STATEMENT Space
00000700 Buffer pool space BP
00000701 Group buffer pool GBP
00000800 Plan PL
00000801 Package COLLECTION.
PACKAGE.
CONTOKEN
808 Messages
Table 3. Resource Types (continued)
TYPE Code Type of Resource Name, Content,
Format
00001003 CNOS processing LU. MODE. RTNCD.
FDBK2. RCPRI.
RCSEC. SENSE
00001004 CDB (Communication database) LOCATION.
AUTHORIZATION
ID. PL
00001005 DB access agent LOCATION
00001007 TCP/IP domain name LINKNAME.
DOMAIN. ERRNO
00001008 TCP/IP service name LOCATION.
SERVICE. ERRNO
00001102 Bootstrap data set (BSDS) MEMBER
00002000 Table space CS-claim class DB.SP
00002001 Table space RR-claim class DB.SP
00002002 Table space write-claim class DB.SP
00002003 Index space CS-claim class DB.SP
00002004 Index space RR-claim class DB.SP
00002005 Index space write-claim class DB.SP
00002006 Table space partition CS-claim class DB.SP.PT
00002007 Table space partition RR-claim class DB.SP.PT
00002008 Table space partition write-claim class DB.SP.PT
00002009 Index space partition CS-claim class DB.SP.PT
00002010 Index space partition RR-claim class DB.SP.PT
00002011 Index space partition Write-claim class DB.SP.PT
00002100 Table space DBET entry DB.SP
00002101 Index space DBET entry DB.SP
00002102 Table space partition DBET entry DB.SP.PT
00002103 Index space partition DBET entry DB.SP.PT
00002104 DBET hash chain lock timeout INTERNAL LOCK
NN
00002105 Logical partition DBET entry DB.SP.PT
00002200 Routine Parameter Storage DBP
00002201 Debug Agent Storage DBP
00002300 ICSF encryption and decryption facilities
00003000 Code (release maintenance_level or system REL, APAR, ZPARM
parameter)
00003002 Number of Stored Procedures
00003072 Index
00003073 Index
00003328 Release dependency
00003329
00003330 OBID limit exceeded
| The following table contains the definitions for the acronyms provided for the
| “Name, Content, Format” column of the preceding table, Table 3 on page 807.
| Table 4. Definitions for resource type name, content, and format
| Where Stands for
| AI Hash anchor ID
| ALIAS Alias owner
| APAR APAR number
| AUTHORIZATION ID DB2 authorization identifier
| BP Buffer pool identifier
| CN Column name
| COLLECTION Collection-ID of the package
| COLN Column number within the base table of the
| LOB column that has been marked invalid.
| CONTOKEN Consistency token of the package
| CR Creator of the object
1
| DB Database name
| DBP Database procedure name
| DI DBID in decimal of resource
| DIX DBID in hexadecimal
| DSN Data set name
| FDBK2 VTAM secondary return code
| GBP Group buffer pool name
| IC ICF catalog alias name
| IX Index name
| LOCATION Location in which the specified resource is
| not available
| LU Logical unit name
| MEMBER Group member name
| MODE Logical unit mode name
| MP Hexadecimal mini-page number
| NN Decimal number of the hash chain
| OI OBID in decimal of resource
| OWNER Alias owner
| PACKAGE Package identifier
| PG Hexadecimal page number
| PIX PSID in hexadecimal
| PL Plan identifier
| PT Decimal partition number
810 Messages
| Table 4. Definitions for resource type name, content, and format (continued)
| Where Stands for
| RCPRI APPC primary return code
| RCSEC APPC secondary return code
2
| RD DB2 release dependency mark
| REL DB2 release name
| RELDEP DB2 release dependency mark
| RID Record Identifier
| RTNCD VTAM primary return code
| SENSE SNA sense codename
| SG Storage group name
™
| SP Space name
| SZ Temporary file page size
| TB Table name
| TS Table space name
| VW View name
|
| Notes:
| 1. DB can also refer to DI. SP, TS, and TB can also refer to OI. DB2 sometimes
| does not have access to resource names, and uses DBID or OBID instead.
| 2. RD can be represented as a white space or blank to indicate no release
| dependency, or Y or N to indicate whether it is IBMREQD.
Disclaimer: Any Web addresses that are included here are accurate at the time this
information is being published. However, Web addresses sometimes change. If you
visit a Web address that is listed here but that is no longer valid, you can try to
find the current Web address for the product information that you are looking for
at either of the following sites:
v http://www.ibm.com/support/publications/us/library/index.shtml, which lists
the IBM information centers that are available for various IBM products
v http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/
pbi.cgi, which is the IBM Publications Center, where you can download online
PDF books or order printed books for various IBM products
The primary place to find and use information about DB2 for z/OS is the
Information Management Software for z/OS Solutions Information Center
(http://publib.boulder.ibm.com/infocenter/imzic), which also contains information
about IMS, QMF, and many DB2 and IMS Tools products. The majority of the DB2
for z/OS information in this information center is also available in the books that
are identified in the following table. You can access these books at the DB2 for
z/OS library Web site (http://www.ibm.com/software/data/db2/zos/library.html)
or at the IBM Publications Center (http://www.elink.ibmlink.ibm.com/public/
applications/publications/cgibin/pbi.cgi).
Table 5. DB2 Version 9.1 for z/OS book titles
Available in Available in
Publication information Available in BookManager® Available in
Title number center PDF format printed book
DB2 Version 9.1 for z/OS SC18-9840 X X X X
Administration Guide
DB2 Version 9.1 for z/OS Application SC18-9841 X X X X
Programming & SQL Guide
DB2 Version 9.1 for z/OS Application SC18-9842 X X X X
Programming Guide and Reference for
Java
DB2 Version 9.1 for z/OS Codes GC18-9843 X X X X
DB2 Version 9.1 for z/OS Command SC18-9844 X X X X
Reference
DB2 Version 9.1 for z/OS Data Sharing: SC18-9845 X X X X
Planning and Administration
DB2 Version 9.1 for z/OS Diagnosis LY37-3218 X X X
Guide and Reference 1
DB2 Version 9.1 for z/OS Diagnostic LY37-3219 X
Quick Reference
In the following table, related product names are listed in alphabetic order, and the
associated Web addresses of product information centers or library Web pages are
indicated.
Table 6. Related product information resource locations
Related product Information resources
C/C++ for z/OS Library Web site: http://www.ibm.com/software/awdtools/czos/library/
814 Messages
Table 6. Related product information resource locations (continued)
Related product Information resources
CICS Transaction Server for Information center: http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/index.jsp
z/OS
COBOL Information center: http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp
These resources include information about the following products and others:
v DB2 Administration Tool
v DB2 Automation Tool
v DB2 DataPropagator™ (also known as WebSphere® Replication Server for z/OS)
v DB2 Log Analysis Tool
v DB2 Object Restore Tool
v DB2 Query Management Facility
v DB2 SQL Performance Analyzer
DB2® Universal Database™ Information center: http://www.ibm.com/systems/i/infocenter/
for iSeries®
Debug Tool for z/OS Information center: http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp
Enterprise COBOL for Information center: http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp
z/OS
Enterprise PL/I for z/OS Information center: http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp
IMS Information center: http://publib.boulder.ibm.com/infocenter/imzic
IMS Tools One of the following locations:
v Information center: http://publib.boulder.ibm.com/infocenter/imzic
v Library Web site: http://www.ibm.com/software/data/db2imstools/library.html
These resources have information about the following products and others:
v IMS Batch Terminal Simulator for z/OS
v IMS Connect
v IMS HALDB Conversion and Maintenance Aid
v IMS High Performance Utility products
v IMS DataPropagator
v IMS Online Reorganization Facility
v IMS Performance Analyzer
Information resources for DB2 for z/OS and related products 815
Table 6. Related product information resource locations (continued)
Related product Information resources
PL/I Information center: http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp
816 Messages
Table 6. Related product information resource locations (continued)
Related product Information resources
z/OS Library Center site: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
This resource includes information about the following z/OS elements and components:
v Character Data Representation Architecture
v Device Support Facilities
v DFSORT
v Fortran
v High Level Assembler
v NetView®
v SMP/E for z/OS
v SNA
v TCP/IP
v TotalStorage® Enterprise Storage Server®
v VTAM
v z/OS C/C++
v z/OS Communications Server
v z/OS DCE
v z/OS DFSMS
v z/OS DFSMS Access Method Services
v z/OS DFSMSdss
v z/OS DFSMShsm
v z/OS DFSMSdfp™
v z/OS ICSF
v z/OS ISPF
v z/OS JES3
v z/OS Language Environment
v z/OS Managed System Infrastructure
v z/OS MVS
v z/OS MVS JCL
v z/OS Parallel Sysplex®
v z/OS RMF™
v z/OS Security Server
v z/OS UNIX System Services
z/OS XL C/C++ http://www.ibm.com/software/awdtools/czos/library/
The following information resources from IBM are not necessarily specific to a
single product:
v The DB2 for z/OS Information Roadmap; available at: http://www.ibm.com/
software/data/db2/zos/roadmap.html
v DB2 Redbooks® and Redbooks about related products; available at:
http://www.ibm.com/redbooks
v IBM Educational resources:
– Information about IBM educational offerings is available on the Web at:
http://www.ibm.com/software/sw-training/
Information resources for DB2 for z/OS and related products 817
– A collection of glossaries of IBM terms in multiple languages is available on
the IBM Terminology Web site at: http://www.ibm.com/software/
globalization/terminology/index.jsp
v National Language Support information; available at the IBM Publications
Center at: http://www.elink.ibmlink.ibm.com/public/applications/publications/
cgibin/pbi.cgi
v SQL Reference for Cross-Platform Development; available at the following
developerWorks® site: http://www.ibm.com/developerworks/db2/library/
techarticle/0206sqlref/0206sqlref.html
The following information resources are not published by IBM but can be useful to
users of DB2 for z/OS and related products:
v Database design topics:
– DB2 for z/OS and OS/390 Development for Performance Volume I, by Gabrielle
Wiorkowski, Gabrielle & Associates, ISBN 0-96684-605-2
– DB2 for z/OS and OS/390 Development for Performance Volume II, by Gabrielle
Wiorkowski, Gabrielle & Associates, ISBN 0-96684-606-0
– Handbook of Relational Database Design, by C. Fleming and B. Von Halle,
Addison Wesley, ISBN 0-20111-434-8
v Distributed Relational Database Architecture (DRDA) specifications;
http://www.opengroup.org
v Domain Name System: DNS and BIND, Third Edition, Paul Albitz and Cricket
Liu, O’Reilly, ISBN 0-59600-158-4
v Microsoft® Open Database Connectivity (ODBC) information;
http://msdn.microsoft.com/library/
v Unicode information; http://www.unicode.org
818 Messages
How to obtain DB2 information
You can access the official information about the DB2 product in a number of
ways.
v “DB2 on the Web”
v “DB2 product information”
v “DB2 education” on page 820
v “How to order the DB2 library” on page 820
Stay current with the latest information about DB2 by visiting the DB2 home page
on the Web:
www.ibm.com/software/db2zos
On the DB2 home page, you can find links to a wide variety of information
resources about DB2. You can read news items that keep you informed about the
latest enhancements to the product. Product announcements, press releases, fact
sheets, and technical articles help you plan and implement your database
management strategy.
The official DB2 for z/OS information is available in various formats and delivery
methods. IBM provides mid-version updates to the information in the information
center and in softcopy updates that are available on the Web and on CD-ROM.
Information Management Software for z/OS Solutions Information Center
DB2 product information is viewable in the information center, which is
the primary delivery vehicle for information about DB2 for z/OS, IMS,
QMF, and related tools. This information center enables you to search
across related product information in multiple languages for data
management solutions for the z/OS environment and print individual
topics or sets of related topics. You can also access, download, and print
PDFs of the publications that are associated with the information center
topics. Product technical information is provided in a format that offers
more options and tools for accessing, integrating, and customizing
information resources. The information center is based on Eclipse open
source technology.
The Information Management Software for z/OS Solutions Information
Center is viewable at the following Web site:
http://publib.boulder.ibm.com/infocenter/imzic
CD-ROMs and DVD
Books for DB2 are available on a CD-ROM that is included with your
product shipment:
v DB2 V9.1 for z/OS Licensed Library Collection, LK3T-7195, in English
The CD-ROM contains the collection of books for DB2 V9.1 for z/OS in
PDF and BookManager formats. Periodically, IBM refreshes the books on
subsequent editions of this CD-ROM.
© Copyright IBM Corp. 1983, 2008 819
The books for DB2 for z/OS are also available on the following CD-ROM
and DVD collection kits, which contain online books for many IBM
products:
v IBM z/OS Software Products Collection , SK3T-4270, in English
v IBM z/OS Software Products DVD Collection , SK3T–4271, in English
PDF format
Many of the DB2 books are available in PDF (Portable Document Format)
for viewing or printing from CD-ROM or the DB2 home page on the Web
or from the information center. Download the PDF books to your intranet
for distribution throughout your enterprise.
BookManager format
You can use online books on CD-ROM to read, search across books, print
portions of the text, and make notes in these BookManager books. Using
the IBM Softcopy Reader, appropriate IBM Library Readers, or the
BookManager Read product, you can view these books in the z/OS,
Windows, and VM environments. You can also view and search many of
the DB2 BookManager books on the Web.
DB2 education
IBM Education and Training offers a wide variety of classroom courses to help you
quickly and efficiently gain DB2 expertise. IBM schedules classes are in cities all
over the world. You can find class information, by country, at the IBM Learning
Services Web site:
www.ibm.com/services/learning
IBM also offers classes at your location, at a time that suits your needs. IBM can
customize courses to meet your exact requirements. For more information,
including the current local schedule, contact your IBM representative.
www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi
From the IBM Publication Center, you can go to the Publication Notification
System (PNS). PNS users receive electronic notifications of updated publications in
their profiles. You have the option of ordering the updates by using the
publications direct ordering application or any other IBM publication ordering
channel. The PNS application does not send automatic shipments of publications.
You will receive updated publications and a bill for them if you respond to the
electronic notification.
You can also order DB2 publications and CD-ROMs from your IBM representative
or the IBM branch office that serves your locality. If your location is within the
United States or Canada, you can place your order by calling one of the toll-free
numbers:
v In the U.S., call 1-800-879-2755.
v In Canada, call 1-800-426-4968.
820 Messages
Be prepared to give your customer number, the product number, and either the
feature codes or order numbers that you want.
| If you are new to DB2 for z/OS, Introduction to DB2 for z/OS provides a
| comprehensive introduction to DB2 Version 9.1 for z/OS. Topics included in this
| book explain the basic concepts that are associated with relational database
| management systems in general, and with DB2 for z/OS in particular.
The most rewarding task associated with a database management system is asking
questions of it and getting answers, the task called end use. Other tasks are also
necessary—defining the parameters of the system, putting the data in place, and so
on. The tasks that are associated with DB2 are grouped into the following major
categories.
Installation
If you are involved with DB2 only to install the system, DB2 Installation Guide
might be all you need.
If you will be using data sharing capabilities you also need DB2 Data Sharing:
Planning and Administration, which describes installation considerations for data
sharing.
End use
End users issue SQL statements to retrieve data. They can also insert, update, or
delete data, with SQL statements. They might need an introduction to SQL,
detailed instructions for using SPUFI, and an alphabetized reference to the types of
SQL statements. This information is found in DB2 Application Programming and SQL
Guide, and DB2 SQL Reference.
End users can also issue SQL statements through the DB2 Query Management
Facility (QMF) or some other program, and the library for that licensed program
might provide all the instruction or reference material they need. For a list of the
titles in the DB2 QMF library, see the bibliography at the end of this book.
Application programming
Some users access DB2 without knowing it, using programs that contain SQL
statements. DB2 application programmers write those programs. Because they
write SQL statements, they need the same resources that end users do.
The material needed for writing a host program containing SQL is in DB2
Application Programming and SQL Guide.
| The material needed for writing applications that use JDBC and SQLJ to access
| DB2 servers is in DB2 Application Programming Guide and Reference for Java. The
| material needed for writing applications that use DB2 CLI or ODBC to access DB2
| servers is in DB2 ODBC Guide and Reference. The material needed for working with
| XML data in DB2 is in DB2 XML Guide. For handling errors, see DB2 Messages and
| DB2 Codes.
If you will be working in a distributed environment, you will need DB2 Reference
for Remote DRDA Requesters and Servers.
DB2 Performance Monitoring and Tuning Guide explains how to monitor the
performance of the DB2 system and its parts. It also lists things that can be done to
make some parts run faster.
If you will be using the RACF access control module for DB2 authorization
checking, you will need DB2 RACF Access Control Module Guide.
If you are involved with DB2 only to design the database, or plan operational
procedures, you need DB2 Administration Guide. If you also want to carry out your
own plans by creating DB2 objects, granting privileges, running utility jobs, and so
on, you also need:
v DB2 SQL Reference, which describes the SQL statements you use to create, alter,
and drop objects and grant and revoke privileges
v DB2 Utility Guide and Reference, which explains how to run utilities
824 Messages
v DB2 Command Reference, which explains how to run commands
If you will be using data sharing, you need DB2 Data Sharing: Planning and
Administration, which describes how to plan for and implement data sharing.
Diagnosis
Diagnosticians detect and describe errors in the DB2 program. They might also
recommend or apply a remedy. The documentation for this task is in DB2 Diagnosis
Guide and Reference, DB2 Messages, and DB2 Codes.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered marks of
International Business Machines Corporation in the United States, other countries,
or both. These and other IBM trademarked terms are marked on their first
occurrence in this information with the appropriate symbol (® or ™), indicating
828 Messages
trademarks that were owned by IBM at the time this information was published. A
complete and current list of IBM trademarks is available on the Web at
http://www.ibm.com/legal/copytrade.shtml
Notices 829
830 Messages
Glossary
The glossary is available in several locations.
v The Glossary topic in the Information Management Software for z/OS Solutions
Information Center.
v In most printed product manuals and the corresponding PDFs.
v In the BookManager edition of the Administration Guide.
Printed in USA
GC18-9849-03
Spine information: